Quick answer
The supporting infrastructure and works within a defined power-plant scope. In solar contracts, balance of plant may include civil, electrical, control and interconnection packages; exact inclusions and boundaries must be stated.
Answer: Balance of plant, or BOP, refers to the supporting infrastructure and works within a defined power-plant scope. In solar projects it can include civil works, electrical collection, substations, controls and interconnection facilities. The term has no single contract boundary: specify what is included, who owns each interface, and where the contractor’s responsibility ends before comparing costs or bids.
BOP and BOS: define the boundary first
Balance of system, or BOS, is also used for supporting PV components and costs. BOS is not restricted to residential projects, and BOP is not automatically a fixed superset that excludes modules, inverters, racking and labor in every context.
DOE’s PV cost model uses structural and electrical BOS categories for utility-scale, commercial and residential benchmark systems, with inverters and fieldwork separately categorized. That is a disclosed cost-model boundary, not a definition every EPC contract must follow. DOE PV cost benchmark methodology.
For a BOP tender, list inclusions and exclusions explicitly. A civil BOP package and an electrical BOP package may have different contractors and acceptance requirements. The plant capacity alone does not tell you which work belongs to either package.
Common packages to consider
| Package | Possible scope | Interface to resolve |
|---|---|---|
| Civil works | Grading, roads, drainage, erosion control, fencing and foundations | Geotechnical assumptions, equipment access, drainage crossings and environmental conditions |
| Electrical collection | Conductors, transformers, switchgear, protection and grounding | Equipment terminals, design responsibility, testing and energization boundaries |
| Substation and connection | Substation equipment, metering and connection facilities | Utility versus developer ownership, study requirements and accepted connection point |
| Controls and communications | SCADA, plant control, weather instrumentation, networks and data systems | Required telemetry, protocols, settings, cybersecurity responsibilities and operational access |
These are possible inclusions, not a universal equipment schedule. Voltage, relay functions and communication protocols depend on the actual network requirements and plant design.
A documented contract example: IFC’s Dama Solar PV disclosure describes a proposed separate BOP and high-voltage electrical construction contract for substations and interconnection, alongside separate PV EPC contracts and sponsor-procured modules. The disclosure describes an intended contracting arrangement; it does not establish that every project uses that structure or that the contracts were completed. IFC Dama Solar PV disclosure.
Estimate from scoped quantities, not a residual percentage
A formula such as “total EPC cost minus modules, inverters, racking and labor” only gives a meaningful BOP cost if those deductions and the residual match the agreed, nonoverlapping scope. Labor often belongs inside a construction package; deducting all labor can remove work that the BOP contractor must perform.
Build an estimate from measured quantities, supplier quotations, construction assumptions, interface costs and stated exclusions. Record currency, price date, taxes, contingency treatment and whether the capacity denominator is DC or AC. Site terrain, cable routes, geotechnical findings and interconnection work can change quantities substantially; no universal BOP percentage or per-watt price follows from the term.
Hypothetical quote reconciliation: assume a $2 million civil package, $3 million electrical package and $1 million controls package. If each of the latter two includes the same $100,000 communications item, simply adding the quotes gives $6 million with a double count. Remove one duplicate only after confirming which contractor retains the complete scope: the reconciled sum is $5.9 million, before any other exclusions or adjustments. These figures are illustrative, not a market price benchmark.
Practical project handoffs
- Design: coordinate array blocks, routes, roads, drainage and substations. Shortening a route can help, but compare constructability, constraints and the actual electrical design rather than minimizing distance alone.
- Procurement: track supplier-specific lead times and evidence, not a fixed generic transformer delivery range. Confirm scope, warranties, spares, testing responsibilities and interfaces before award.
- Construction: coordinate trenching, road surfaces and equipment delivery. The detailed sequence depends on the site and contract; all civil work need not universally finish before any electrical work starts.
- Commissioning: use the approved testing, safety and utility coordination plan. A general glossary cannot prescribe feeder energization or protection procedures.
- Operations: hand over asset identifiers, surveyed underground routes, settings, manuals, maintenance requirements and as-built drawings. Include the agreed upkeep and replacement scope in the operating budget.
For project context, see utility-scale solar and substations. To discuss the layout and information handoffs your team needs, book a SurgePV demo.
Frequently asked questions
Does BOP always exclude inverters?
No. Check the contract or cost-model definition. Terminology alone does not establish an inclusion or exclusion.
Is BOP only used above 10 MW?
There is no universal capacity threshold imposed by the term. Use the scope defined for the project.
What is electrical BOP?
It is the electrical infrastructure package defined in the relevant scope, which may include collection, transformers, switchgear, controls or interconnection. Identify the exact boundaries.
Does a BOP quote include grid upgrades?
Only if the scope includes them. Resolve utility-owned upgrades, connection facilities, fees and third-party work explicitly rather than assuming they are part of the plant contractor’s price.
Related Glossary Terms
About the Contributors

CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.

Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.