Energy storage project roles: client, designer, integrator and operator

Energy storage project participants must agree who defines requirements, performs work, integrates systems and confirms results. Company and job titles alone are insufficient: specific scope, authority, documents and responsibility handoffs are needed. One organization may perform several functions, but each must remain defined.

This article helps clients form a team and identify gaps between contracts. It covers design, supply, integration, operations and market roles. The table is a working example to adapt to the facility, contracts and applicable requirements.

The client defines the result and decision process

The client defines the task: required loads or market operations, site constraints, budget and desired outcome. Inputs include consumption profiles, existing diagrams, permitted modes and conditions for using the facility. Mark unverified assumptions rather than passing them to contractors as confirmed facts.

The project manager coordinates schedules, dependencies, documents and open issues within delegated authority. A client representative or external team may perform this role. Define who approves changes and expenses, accepts results and can issue binding instructions to contractors.

Record contractual responsibilities. "Turnkey" alone does not reveal every exclusion. If supply, construction and controls are procured separately, agree how they interact and who owns the overall result.

An engaged technical consultant may review offers and results. The team needs to understand the review scope and approval authority. Advice alone does not amend contracts or replace required approvals.

Maintain one decision register. A verbal request, technical comment and approved change have different statuses. Record the initiator, description, effect on related work, authorized decision and document version. This helps the team use consistent inputs.

The designer relates requirements to site conditions

The designer develops solutions from the agreed brief, inputs and actual configuration. Battery, converters, electrical networks, protection, communications, auxiliaries and placement must be coordinated. A manufacturer's standard diagram does not prove suitability of the complete solution at a particular site.

Define design boundaries early: what the main team develops, what the manufacturer supplies and which related solutions another organization prepares. Handoffs need a current version, assumptions and agreed connection points. Changing an equipment model may require review of related decisions.

For a project with solar generation, solar design may be a separate package. Agree the boundary between solar and storage with those responsible for integration. That service scope does not automatically cover every task for an independent storage installation.

Agree who addresses comments and keeps documentation current. Installation and future operations teams should receive coordinated changes rather than different versions of one diagram.

Supplier and installer deliver different results

The supplier confirms its equipment's scope, characteristics, completeness, documentation and support terms. Check storage components: a battery package may exclude an external transformer, cables, communications or some site work. Assign an owner to each exclusion.

The construction or installation contractor performs the agreed scope using appropriate documentation. Before work starts, agree foundation readiness, access, logistics, equipment handover and conditions for related operations. Delivery is not installation completion, and installation does not prove all systems work together.

Hand over results with required checks and as-built documents. Comments need a description, owner and closure criterion. If a nonconformity appears, check facts and work boundaries first rather than assigning blame solely by contractor title.

Agree resources for commissioning, including manufacturer representatives, configuration, documents and equipment access. Physical readiness may otherwise not coincide with readiness for integrated tests.

The integrator owns agreed system interaction

The system integrator connects equipment and controls within a defined brief. This may be part of a comprehensive contract or a separate package. Specify interfaces, configuration and tests it provides, and who confirms overall system characteristics.

The battery management system (BMS) monitors battery condition and protective limits. The energy management system (EMS) plans operating modes. SCADA provides monitoring, events, archiving and data exchange. These functions are related but distinct. Software does not replace the organization responsible for decisions and changes.

Agree storage controls and data access: sources, command lists, user permissions, logs and updates. Settings must reflect permitted modes and the specific solution's technical constraints.

Hypothetical example: equipment is installed but the control system does not receive the agreed power value. The supplier checks whether its device supplies the signal, the communications owner checks transmission and the integrator organizes interaction testing. Participants follow agreed boundaries and the test program.

Working individual components alone do not close the issue. Evidence of the required result, a recorded comment and a decision by the authorized party are needed. The example illustrates handoffs; it does not establish the fault cause or automatic legal liability.

For an algorithm change, identify who requests it, assesses compatibility, approves deployment and verifies the result. Keep the settings version and test report. A commercial objective does not justify bypassing protection limits or permitted modes.

Distinguish technical operation and market roles

Technical operation includes agreed actions to maintain functionality: condition monitoring, inspections, event response and service coordination. Define the people, authority and access for the specific site. A service contractor does not automatically become a market participant by performing repairs.

An energy storage operator is a distinct market role. Owning a battery alone does not automatically confer that status. Transmission and distribution system operators have different functions for their respective networks. A job title "operator" in an internal schedule does not establish legal status or authority.

Allocate commercial metering and registration work separately: who prepares data, checks it and sends it to the relevant party. This boundary needs agreement between technical staff and commercial participants.

Consider trader and aggregator roles for the chosen model. Commercial teams arrange market actions under their contracts; technical teams ensure permitted modes can be performed. Including an installation in aggregation does not itself transfer storage operator status to the aggregator.

Create a register of deliverables and owners

For each package, record the result, contractor, required inputs and the party that reviews or accepts it within its authority. Coordinate the project schedule so the handoff reflects actual work dependencies.

This table does not assign universal contractors or create legal status. Add organizations, contacts, approvers and a dispute-resolution process. Identify functions everyone assumes belong to someone else before ordering work.

For a complex interface, record what information the next participant expects and when. For example, agreed control parameters must be available to those preparing integrated tests. A document list without a handoff owner does not resolve that dependency.

Hand over the system with documents and access

Agree testing and acceptance before final work. Distinguish who performs tests, who evaluates results and who will operate the installation. Criteria and evidence must match actual scope and applicable requirements.

Before handover check:

• Current diagrams, instructions and equipment list.
• Test reports and status of open comments.
• Training, access rights and how to change them.
• Service contacts and event response process.
• Warranty documents and claims owners.

Clarify warranties, degradation and storage service. For a project with solar, solar service and storage support may differ in scope. Agree the boundary so no component or control channel lacks an owner.

1. Define the result. Agree requirements and package boundaries.
2. Assign handoffs. Name contractors, reviewers and evidence.
3. Keep information current. Update the register after changes and operational handover.

A coordinated team needs more than a participant list. It needs a decision route: who receives an issue, who resolves it and what confirms completion. Maintain that route throughout the installation's operating life.