The Alignment Gap in System-Integrator Selection for Battery Storage Projects

Signals to watch

• cross-functional misalignment
• scope fragmentation
• evidence gaps

Composite industry case. This page describes a reusable operating problem and decision method. It does not represent a named customer, real conversation, contract, revenue result or testimonial.

Battery storage projects look like equipment procurement but behave like systems integration. The container, the power conversion system, the battery management system, the fire detection and suppression loop, the grid interconnection relay, the SCADA handshake — each component comes from a different supply chain, and the integrator is expected to weld them into one warrantied, code-compliant, dispatchable asset.

When a program lead opens an integrator selection process, the RFQ typically covers technical specifications, commercial terms, delivery milestones, and warranties. What it rarely covers is a single question: Who, exactly, owns each unresolved risk at the moment of commercial operation?

The Six Gaps That Appear After Contract Award

Experience across early-stage storage programs reveals a pattern. Six ownership questions are regularly misaligned at shortlist stage. They surface — always — during detailed design or commissioning, when change orders are expensive and schedules are tight.

Use-case ownership. The integrator supplies a dispatch algorithm, the energy-marketing team defines the trading strategy, and the grid-connection agreement imposes ramp-rate and reactive-power constraints. When the asset fails a market test, each party points at the other’s inputs. The program lead has no single document that maps every operational scenario to a responsible party.

Grid-connection ownership. The utility’s interconnection study presumes a certain fault-current profile and protection scheme. The integrator’s equipment has different characteristics. Some programs assign a third-party consultant to manage the gap; most assume it will be resolved during commissioning. It never resolves without a formal gap register.

Fire-safety ownership. The local authority having jurisdiction approves the fire-mitigation plan. The integrator supplies the detection and suppression hardware. The EPC contractor installs the conduit and cabling. The certificate of occupancy requires all three to agree on a single sequence of operations for thermal runaway. This sequence is rarely written before the equipment is on site.

Controls-system ownership. The storage plant controller, the utility’s remote-terminal-unit protocol, and the owner’s monitoring platform must exchange a defined set of points. Each vendor has a standard point list. The integrated point list — the one that ensures every alarm reaches the right operator — is almost never a deliverable in the integrator scope.

Warranty-claim ownership. The battery warranty excludes thermal-management failures. The thermal-management warranty excludes control-system faults. The integrator warranty excludes acts of grid. When a capacity-test failure occurs, the program lead discovers that every party’s warranty starts with the same phrase: “This warranty does not cover conditions caused by…”

Delivery-ownership fragmentation. Civil works, container transport, grid-connection testing, and commissioning are often split across three contracts. The integrator’s schedule assumes the site is ready. The site-prep contract assumes the integrator will manage contingencies. The gap appears as a standby-cost claim.

A Human Review That Any Program Lead Can Run Today

The root cause of these gaps is not incompetence. It is that selection criteria reward coverage — did the integrator respond to every RFQ line item — rather than ownership clarity. Teams treat the RFQ as a specification document when it should be treated as a risk-register prompt.

The method is a six-column review run before the shortlist is finalized.

Column one — the gap. State each unresolved ownership question identified above. Add any that are specific to the project site or regulatory context.

Column two — the evidence. For each gap, point to the specific document or clause that exposes the ambiguity. A draft interconnection agreement. A warranty-data sheet. A controls-system scope-of-work excerpt. If no document exists, the gap is by definition unresolved.

Column three — the owner. Assign a named party — integrator, EPC, third-party consultant, or owner team. Do not assign “TBD.” An unassigned owner guarantees the gap will be rediscovered during commissioning.

Column four — the decision window. Identify the last point at which the gap can be resolved without a change order. The grid-connection gap must be closed before the interconnection application is filed. The fire-safety gap must be closed before the building permit is submitted.

Column five — the escalation path. Name the person on each side who has authority to approve the resolution. Engineers can identify the gap; they rarely have budget authority to close it.

Column six — the review date. Set a calendar date for the next review. Do not tie it to a milestone. Tie it to a date, because milestones slip and the gap does not.

The output is a single table — one row per gap, six columns. It is not a dashboard. It is a human review action with an owner, evidence, and a decision window.

What the Program Lead Does Next

Share the table with the integrator shortlist candidates as a pre-bid clarification document. Ask each candidate to fill their assigned rows and return the table with their proposal. The responses do not disqualify a candidate; they reveal which candidates have already thought through each gap and which are seeing it for the first time.

Use the table as the agenda for the pre-award clarification meeting. Do not discuss price or schedule until every row has a name next to it. If a candidate cannot name a single owner for each gap, the program lead knows — before award — where the change orders will come from.

What Automation Cannot Replace

Continuous signal discovery tools can surface these gaps earlier — by scanning interconnection study comments, warranty-data-sheet cross-references, and controls-system point-list discrepancies before a human reads them. Evidence organization platforms can keep the six-column table alive through detailed design, commissioning, and operations, attaching documents and decisions to each row as they occur. Automated reminders can flag a decision window that is about to close.

None of those replace the human judgment of assigning an owner, writing the escalation path, and setting a review date. The machine finds the pattern. The program lead makes the call. The table makes that call visible, repeatable, and tied to a date on the calendar.

Frequently asked questions

What is the single most common mistake teams make during integrator selection?

Treating technical qualification as a binary checklist instead of surfacing which party owns each unresolved risk at contract signature.

Does this method require a specific software platform?

No. The six-column review works in a shared spreadsheet. The article explains how continuous signal discovery and evidence organization tools can support the workflow at scale, but the core method is independent of any tool.