In this article
Whether energy storage is delivered turnkey or by separate contractors, start by allocating responsibility. The client must establish who designs the installation, procures equipment, ensures compatibility and confirms results through testing. The contract name alone does not define work boundaries, warranties or costs.
The contract model affects the number of agreements, the authority of your team and how issues between contractors are resolved. Select it together with the technical brief and schedule. The project stages explain the overall preparation and launch sequence; here the focus is contractual boundaries.
EPC, EPCM or a combined model
EPC is a comprehensive contract covering design, procurement and construction within the agreed scope. The client works with a contractor responsible for that package. This can simplify control of schedules and performance, but review exclusions: external connection, land preparation or specific approvals may remain outside the price.
EPCM provides management of design, procurement and construction, often with the client contracting suppliers and contractors directly. The manager coordinates within delegated authority. This does not automatically transfer all supply and compatibility risks. The client needs a team capable of managing multiple contracts.
| Model | Organization | Key check |
|---|---|---|
| EPC contract | One contractor is responsible for the agreed package. | Does it cover the complete required result and what is excluded? |
| EPCM management | A coordinator manages work while the client signs separate agreements. | Who resolves contractor mismatches and pays for corrections? |
| Combined model | An equipment package is combined with separate grid and construction work. | Where are supply boundaries and who integrates the system? |
Potentially cheaper direct procurement does not guarantee a lower total budget. Include coordination, compatibility checks and schedule reserve. A higher EPC price may include risks assumed by the contractor. Compare the same result, exclusions and confirmed obligations.
Assess your management resources. Who will make technical decisions, review changes and approve results? If a consultant performs those functions, define authority and responsibility boundaries. Even a comprehensive contract needs timely client decisions and oversight.
Define work boundaries before agreeing the price
Build a responsibility matrix around specific deliverables: inputs, design, foundation, battery, converter, transformer, cables, protection, metering, communications and tests. For each, identify the contractor, approving party, needed inputs and completion document. "Performed jointly" without an owner leaves a gap.
Separate physical and information interfaces. Cabinet supply may end at its terminals while another contractor installs the cable to the transformer. For data exchange agree protocols, signal lists and who configures them. Compatibility should be a testable result, not a verbal promise.
Hypothetical example: the client buys the battery, a local contractor builds the grid section and an integrator configures controls. If the system cannot perform the intended mode, agree a joint diagnosis process. Specify in advance who collects event logs, organizes checks and coordinates correction. This illustrates task allocation, not a completed project.
Also check responsibility for documents and site readiness. A contractor agreement does not replace rights and approvals procedures. Compare the matrix with design, permits and acceptance. Show client actions and dependencies on other participants in the schedule.
Prepare one technical specification
The specification describes the installation's purpose, operating modes, grid parameters and site conditions. For the battery define nominal and usable capacity, permitted charge modes, cooling and expected capacity decline. For the converter specify active and reactive power, permissible overloads and behavior during grid disturbances.
Do not confuse device-level characteristics with whole-facility performance. Converter-terminal power and net power at the connection point differ because of losses and auxiliary use. Before comparing offers, clarify power and energy capacity, the measurement point and operating conditions.
Control systems also belong in the specification. Agree battery control, energy management, supervisory control and archiving functions. The storage glossary explains abbreviations and their differences. Add access, event-log and settings-handover requirements for operations staff.
The equipment catalog can support an initial comparison but does not replace the agreed project specification. Fix the configuration and substitution process in a contract appendix. An alternative model needs assessment of compatibility, dimensions, cooling, protection and guaranteed performance.
Develop safety requirements for the actual configuration. Agree early event detection, ventilation, safe disconnection and emergency-service actions. Allocate supply and site integration of these systems in the contract. One detector does not establish readiness of the complete protection system.
Make warranties measurable obligations
Each measure needs a value, test conditions, permitted tolerances and consequences of failure. The agreed list may include usable capacity, net power, round-trip efficiency, response time, auxiliary use and noise. It depends on the task; universal figures without measurement conditions are not suitable for comparison.
A capacity-retention warranty should account for calendar aging, cycle count and depth, and energy throughput. Align permitted operation with the financial model. If the calculation assumes more intensive use than the warranty permits, resolve the mismatch before procurement.
Distinguish a component warranty, a whole-system performance obligation and service response. A battery meeting its datasheet does not establish performance at the connection point. Define who handles claims, diagnoses the cause, arranges repair and retests. Agree specific remedies in the contract.
Review exclusions including temperature, operation and maintenance requirements against actual business use. Record what data is needed for a claim and who retains it. Without event logs, determining a cause can be harder.
Agree schedule, changes and payments
Link the calendar to prerequisites: design approval, foundation readiness, delivery, grid access and testing. Each milestone needs a deliverable and supporting document. Container arrival is not readiness of the whole installation. Identify how one contractor's delay affects others.
Define the change process: who proposes it, how price, schedule and performance impacts are assessed, and who approves it. Update every related contract when the specification changes. Otherwise a builder may use old dimensions while a supplier prepares a different configuration.
Relate payment milestones to verifiable work. Define documents for each, how comments are handled and final payment conditions. Advances, security, penalties and reserves are not universal; agree them after technical and legal review.
Provide a joint acceptance program
Factory component checks do not replace testing of the assembled system on site. The acceptance program should cover agreed modes, protection, communications, controls and guaranteed characteristics. Define participants, measurement instruments, conditions and report format in advance, including the retest process.
- Agree criteria
Define measures, methods, responsibilities and test prerequisites.
- Test the system
Record results, nonconformities and agreed corrective actions.
- Hand over
Complete acceptance, documentation, training and data access.
Long-period operational availability cannot be confirmed by one short test. Agree the formula, observation period and treatment of downtime for such an obligation. Acceptance checks functional readiness; subsequent warranty monitoring follows defined conditions.
Hand over as-built documents, passports, reports, warranties, instructions and spare-parts lists with the equipment. Define training, software updates and access to operational data. The client needs to know how to support the system after the construction contract ends.
The service appendix should explain response times, spare-parts availability, scheduled work and emergency repair. Clarify whether "response" means acknowledging a request, remote diagnosis or an on-site visit. Agree the restoration process and responsible party.
Review the package before signing
Combine the commercial offer, technical specification, responsibility matrix and calendar into one consistent package. Review appendices too, as they often define supply boundaries, exclusions and acceptance criteria. Keep unresolved issues in a separate list rather than hiding them behind a general promise to agree later.
- Is the full scope and every exclusion described?
- Who owns the equipment, grid and control interfaces?
- Are performance measures aligned with their test methods?
- How are changes, comments and retests handled?
- Which documents, access rights and service obligations does the client receive?
If storage will operate with a solar plant, agree boundaries for the solar portion separately. ONG's solar power design page describes that service. Storage design, integration and warranties must be agreed for your facility separately.
For an initial discussion, prepare installation parameters, site details, contract model and contractors already involved. With that information you can discuss the technical task with ONG Solar and clarify the next scope of work. This helps compare offers by the obligations they contain.