Contract energy

What it is (precise)

Contract energy is fixed by three coordinates, and an MWh figure missing any of them is not yet a contractual quantity. The meter: the physical measurement point where the energy is counted — normally the revenue meter at or near the point of interconnection, occasionally a different defined bus, and the choice moves the number by the whole loss chain between buses.

The conditions: the temperature, discharge rate or duration, state-of-charge window, rest periods and auxiliary-load treatment under which the demonstrating test runs, because measured capacity shifts with all of them. The year: whether the figure is a beginning-of-life value or a guarantee that must still hold in year 10, 15 or 20, stated either as one constant number or as a year-by-year schedule.

The same commercial quantity lives in more than one document, and the documents do not automatically agree. The offtake or tolling agreement states the MWh the plant must deliver per dispatch and backs it with availability terms and liquidated damages. The capacity warranty in the supply or long-term service agreement states a retention curve against nameplate, at its own measurement point.

Capacity-market and resource-adequacy rules add a third framing — commonly crediting storage against a 4-hour sustained-discharge requirement. Each document defines its own test, and reconciling the three definitions before signing is cheaper than reconciling them during a dispute.

Against its neighbours in the chain: nameplate is the manufacturer's rated DC capacity at beginning of life, a datasheet ceiling; usable energy is what the EMS will actually cycle inside the SOC window, the quantity warranties are written against; contract energy is what a counterparty can enforce at a meter. Nameplate belongs to the vendor, usable to the engineer, contract energy to the lawyers and the lenders — and it is by design the smallest of the three.

Why it matters in a real grid-scale project

Contract energy is where sizing starts, and the design runs backwards from it. Take the guaranteed MWh in the worst contracted year — usually the last — and walk up the chain: gross it up for the losses between the revenue meter and the racks, widen it past the SOC window, then add the degradation margin so the faded fleet still clears the number at end of term.

That walk is why usable AC energy commonly lands around 85-92% of nameplate DC after efficiency and operating-window deductions, and why projects carry a DC overbuild of roughly 10-25% at beginning of life versus the contracted energy. The distance between nameplate and contract energy is the overbuild-and-augmentation margin, and it drives container count, land area, collection-system design and the largest lines of the capex budget.

The same number carries the financing. Lenders size debt against contracted revenue, and contracted revenue assumes the plant clears its capacity tests; a shortfall triggers remedies — liquidated damages, added racks, restored capacity — depending on which document caught it.

The choice between the two contract structures shapes the whole operating life: under a declining guaranteed curve the buyer oversizes on day one and lets the plant fade to its contracted floor, while under a fixed guaranteed MWh the supplier or owner augments over time to hold the number constant. If the offtake fixes the quantity while the warranty assumes a declining curve, the gap between them is an augmentation obligation someone has to fund — better discovered in diligence than in year 8.

How it is proven — the capacity test

Contract energy exists operationally as a test result. At commissioning, a capacity test executes the contractually defined charge-discharge profile and establishes the baseline; through operations, periodic Reference Performance Tests at a contractually defined temperature, C-rate and SOC window generate the compliance record.

Test methodology for ESS performance is standardized in the IEC 62933 series, which many contracts reference, but the binding document is the contract's own test protocol: it names the meter, the corrections for ambient temperature and rate, the rest periods, and whether auxiliary consumption during the test is netted out. Two parties with the same plant and different protocols will produce different, equally defensible MWh figures.

The meter itself is specified to a revenue-accuracy class — commonly class 0.2S/0.5S under IEC 62053-22 or class 0.2/0.5 under ANSI C12.20 — because at contract scale a fraction of a percent of measurement error is real money. The EMS executes the discharge profile that proves the contracted energy and logs the throughput, temperature and SOC history that decide whether a later warranty claim survives its envelope check.

Ask early who performs and witnesses the tests, how disagreements over corrections are resolved, and whether degradation between scheduled tests is interpolated or ignored — each is a standard dispute generator with a cheap contractual fix.

How it shows up in specs, studies and contracts

On a datasheet you will not find contract energy at all — you find nameplate DC MWh at reference conditions, often 25 C and a stated C-rate, which is an engineering input to it. In the interconnection study the plant is mostly MW and MVA; energy enters through duration-linked resource-adequacy accounting.

In the contract stack, the quantity appears in the offtake's delivery obligation, the warranty's retention schedule, and the capacity-test exhibit — read all three against each other, checking that the meter, the SOC window, the auxiliary treatment and the guaranteed year line up. A contract that states an MWh without fixing those is a dispute waiting for its first capacity test.

The structural question to settle is fixed versus declining. A fixed contracted quantity converts capacity fade into a scheduled augmentation program, which in turn reserves footprint, DC bus headroom and PCS margin from day one — year-8 racks still have to connect somewhere. A declining contracted quantity keeps the plant's fade inside the deal but pushes the sizing risk to the buyer's own revenue model. Neither is wrong; what is wrong is pricing one and operating the other.

Common pitfalls

The classic trap is reading the datasheet MWh as the deliverable. A "400 MWh project" can mean nameplate DC at the racks, usable energy in the SOC window, delivered AC at the POI, or contracted energy at the revenue meter — four different numbers, each smaller than the last, and vendor comparisons quietly become apples to oranges when two bids quote different links.

The related trap is accepting a guarantee at the wrong bus: the same MWh promised at the DC terminals is materially weaker than at the POI, because everything between the two — PCS and transformer losses, auxiliary load — becomes the buyer's problem.

Year and baseline errors are quieter but just as expensive. Quoting a beginning-of-life figure where the contract requires guaranteed energy in the final year understates the DC overbuild the project actually needs; conversely, a warranty measured against nameplate when the commissioning test came in above nameplate hands the supplier free degradation headroom.

And because the offtake and the warranty each define their own test, a plant can pass its warranty check and still miss its delivery obligation — or the reverse — whenever the two documents put the number at different meters or under different conditions. Treat contract energy as one quantity with one definition, written identically everywhere it appears.