Division of Responsibilities DOR

What a row has to say

One noun is not a row. "Grounding — EPC" allocates nothing, because grounding is six activities that routinely land on different parties: supplying the conductor, laying and welding it, measuring resistance before backfill, accepting that measurement, bonding across the ownership boundary at the substation, and maintaining the result for twenty years. Decompose each row by verb — supply, deliver and offload, install, terminate, test, witness, approve, document, own and maintain after COD — and the allocation becomes checkable.

The same object splits across parties as a matter of course: the integrator supplies the enclosure, the constructor sets and terminates it, the integrator commissions it, the owner witnesses, the authority having jurisdiction approves the installation around it, and after commercial operation the LTSA maintains the battery system while the O&M agreement maintains everything surrounding it.

The balance-of-plant entry's three-way test applies to every row: is there a drawing that shows the boundary, is there a tag or equipment number that identifies it, and is there a test whose result proves the item on that side works. Rows that fail all three fail silently, until the week two packages have to be bonded together. Draw each line at a physical termination somebody can point at — a lug in a named enclosure, a tag-numbered terminal block, a flange, a manhole, a chainage on a route drawing.

Several rows are meaningless without a date column. Utility witness-test attendance is booked rather than requested. Owner-furnished delivery has a nominated date and a nominated delivery point. The SCADA point list has a freeze date, after which changes are a variation rather than a submittal.

The interfaces that go unassigned on a battery project

The medium-voltage cable is the canonical orphan. Who supplies the cable, who pulls it, who terminates it at the enclosure gland plate and who terminates it at the switchgear, who supplies the termination kits and lugs, who performs the withstand test and who witnesses it — six answers that are often given as one.

The enclosure vendor's scope tends to end at the gland plate and the constructor's to begin at the lug, and the kit in between belongs to whoever wrote its name in the matrix. Station service is the other recurring gap, and it inverts intuition: auxiliary power has to be live before the battery system can be commissioned, so an auxiliary board parked in a later civil package puts the whole commissioning programme behind a scope nobody had on the critical path.

Data and protection produce the disputes that surface after energisation. The SCADA point list needs an owner, a publisher, a party that maps scaling and engineering units, a governing time base, and a named signatory for the point-to-point check.

Protection settings at the boundary are approved by the interconnecting utility whichever party owns the relay, so the row is not "who sets the relay" but who produces the coordination study, who submits it, who loads the file, who holds the relay credentials, and who retrieves event records after a trip — the high-voltage-scope entry works through that boundary in detail. The plant model needs the same treatment: who builds it for the interconnection studies, who validates it against the as-built during grid-code compliance testing at the POI, and who reruns it when firmware changes.

Safety evidence and spares are the two columns most often left blank on a first draft. Who authors and stamps the hazard mitigation analysis, and who furnishes the UL 9540A reports for the cell revision actually shipping, are scope questions with permit dates attached; an unowned HMA is a classic schedule hole.

On spares, the row has to answer where the item physically sits, who owns it, who insures it, who is authorised to release it and who replenishes after a draw. The spare main transformer is the sharpest version of that, because its replacement lead time is long enough to end a revenue year — which makes storage location, balance-sheet ownership and whether the insurer credited it in the business-interruption assessment part of the same row rather than an afterthought.

RACI columns and hardware columns are not the same table

RACI — responsible, accountable, consulted, informed — is a management convention rather than a standard, and it allocates decision rights over an activity or a document. On the deliverables layer that is genuinely useful: who drafts the hazard mitigation analysis, who approves it, who is consulted on the explosion-control strategy, who is told when the AHJ accepts it. On hardware it is close to useless. "Responsible for grounding" does not say who supplies the conductor, who welds it, who measures the resistance before backfill or who signs the number.

A working matrix carries both layers: RACI columns for documents, approvals and decisions, and supply / install / terminate / test / own columns for physical scope. A row with an R and nothing else is where the argument starts. So is a row with an A but no contract — every row has to resolve to an actual agreement, whether EPC, supply, LTSA, O&M, utility-built or owner-retained. Rows landing in the owner's column by deliberate choice are a decision. Rows landing there by omission are the expensive kind.

Owner-supplied equipment: the rows that move with it

Owner-furnished equipment is the structural reason most BESS projects need a formal matrix at all. Buying the battery system directly under a supply agreement — and sometimes the PCS, sometimes the main transformer — moves the purchase out of the constructor's scope without moving any of the work. Somebody still receives it, inspects it on arrival, stores it, sets it, terminates it and stands behind the integrated result. Each of those is a row, and a vague one gets priced by the constructor as a risk rather than absorbed.

Three consequences deserve their own lines. Delivery: in most construction forms a late owner-furnished delivery is an owner-caused delay event, giving the contractor time and commonly prolongation cost, so the row needs a date and a nominated delivery point, and the specific entitlement is whatever that contract says rather than a general rule. Title and damage: who inspects on arrival, who signs the delivery note, when risk of loss passes, and who owns a transit damage claim.

And the warranty clock, which runs on calendar time regardless of the project — equipment delivered early and left idle can drift outside conditions its own supplier attached to the term, and cells degrade in storage between factory test and energisation, so a capacity guarantee referenced to nameplate can fail at the COD test unless the contract states where that fade sits.

Turnkey or split: the matrix does not shrink

A full wrap internalises most interfaces inside one contractor, which is precisely what the premium buys. It does not remove the matrix. The utility-facing rows, the AHJ submissions, any owner-furnished items and the operating-phase seam between the LTSA and the O&M agreement all cross the wrap, and the owner is the only party on both sides of them. In a split structure the matrix stops being a coordination aid and becomes the owner's principal risk-control instrument, because the seam a wrap would have carried is now the owner's and this is the only document where it is written down.

Issue the matrix with the request for proposal rather than negotiating it after award. The commercial asymmetry is the reason to move early: liquidated damages from a contractor are payable to the project company and do not satisfy a utility milestone, so a contractor can be fully liable, fully solvent and paying while the project still loses its interconnection position. Allocating the utility-facing rows before notice to proceed is the cheapest schedule insurance available on a battery project.