Create a versioned reference package: design criteria, geotechnical assumptions, module and racking configuration, foundation schedule, bill of materials, labor plan, freight/packaging, equipment, testing/QA, permits, exclusions, contingency, schedule and energy model. State whether the denominator is total system, structural package, watt, module, pile, table, tonne or another unit.
| Baseline question | Required answer |
|---|---|
| What is in scope? | Supply, freight, foundations, erection, QA, spares, tax/duty and interfaces named explicitly |
| What is fixed? | Loads, performance requirements, code basis, owner requirements and approved design stage |
| What can change? | Named variables with approval authority and downstream dependencies |
| How will success be measured? | Same currency/date, quantities, escalation, schedule and energy assumptions |
2. Build a bottom-up installed-cost model
NREL describes its solar cost benchmarking as a bottom-up aggregation of system and project costs. Use the same principle at project scale: quantities multiplied by transparent rates, with separate indirect and risk lines. NREL's solar cost analysis also connects installed cost with LCOE and supply-chain questions rather than treating CAPEX alone as the outcome.
- Structural supply: posts/piles, rails or purlins, braces, fasteners, coatings, fabrication and spares.
- Foundations and civil: testing, refusal/remediation, concrete, earthwork, drainage and restoration.
- Field installation: crew hours, equipment, access, rework, weather and learning curve.
- Logistics: packaging density, freight, unloading, storage, handling and damage.
- Soft costs: engineering, permitting, procurement, inspections, commissioning, overhead and financing/schedule exposure.
- Lifecycle interface: energy effect, inspection access, replacement method, warranty and O&M consequences.
Use a comparable formula: net project value change = installed-cost change + schedule/financing change + modeled energy-value change + lifecycle-cost change. Keep the signs, time basis and uncertainty range explicit.
3. Use an opportunity register, not a savings promise
| Opportunity | Evidence to request | Guardrail |
|---|---|---|
| Structural/member optimization | Updated calculations, drawings, BOM and connection/coating review | No load-path, serviceability or durability downgrade |
| Foundation optimization | Site test data, geotechnical basis, refusal/remediation plan | Include installation risk and quantity variability |
| Standardization/preassembly | Pilot installation, packing study, time observation | Include factory work, freight volume and field exceptions |
| Logistics/packaging | Container/truck plan, unload and handling steps, damage data | Do not trade freight savings for field sorting or damage |
| Installation workflow | Representative work sample and normalized crew-hours | Separate learning, weather and site-access effects |
| Scope/soft-cost clarity | Responsibility matrix, permit/inspection path, document schedule | Do not hide exclusions that return as change orders |
Community discussions often flag structural and electrical surprises, optimistic financial models and supplier-driven redesign. Treat those as discovery prompts. DOE's procurement guidance warns that an inadequate scope can lead to change orders and renegotiation; that is stronger evidence for making scope and version control part of cost reduction.
4. Validate one controlled change at a time
- Identify the highest material cost driver in the baseline and name the proposed variable.
- Update every affected calculation, drawing, quantity and interface; do not price an orphan concept.
- Test constructability on a representative location or pilot where practical. Record normalized labor and exceptions.
- Re-run energy, schedule, financing and lifecycle consequences using the same assumptions.
- Record evidence quality: measured/project-specific, supplier-verified, analogous, or assumption.
- Accept, reject or pilot; assign the next evidence owner and rollback trigger.
NREL's Annual Technology Baseline utility-PV methodology shows why LCOE depends on CAPEX together with performance, O&M, lifetime and financing. A lower steel or labor line does not automatically produce a lower lifecycle cost.
5. Change control prevents false savings
DOE's PV procurement lifecycle guidance recommends carrying technical requirements through award, construction and commissioning and preparing O&M during design. Maintain a change log linking request, reason, affected documents, cost, schedule, energy, warranty, approval and effective date.
Hold or reject the proposal when
- the saving is quoted against a different scope, quantity, currency date or design revision;
- updated calculations, drawings, BOM or interface checks are missing;
- field-productivity claims lack a representative work sample;
- cost is shifted to civil, electrical, QA, O&M or the owner without being shown;
- the option depends on an unapproved product substitution or supplier change;
- the rollback trigger, decision owner or evidence confidence is absent.
FAQs
How much can mounting CAPEX be reduced?
There is no reliable universal percentage. Measure it against one controlled baseline and show scope and lifecycle consequences.
What should be optimized first?
The largest evidenced cost driver after the reference design and scope are frozen.
Is lowest purchase price lowest project cost?
Not necessarily; foundations, freight, field work, schedule, energy and O&M can reverse the comparison.
When should an option be rejected?
When its updated engineering, quantities, interface impacts, owner or rollback criteria are missing.
Sources and related guides
Research basis: DOE solar soft-cost and procurement lifecycle guidance plus NREL cost-model and LCOE methodology linked above. Project quotes and stamped design documents control project decisions.