Power & energy

Measurement boundary

A measurement boundary is the point in the power path where a quantity is defined and metered: the cell terminals, the DC bus at the rack, the AC terminals of the PCS, the medium-voltage side of the transformer, or the point of interconnection. Every power, energy, efficiency, and availability figure in a BESS datasheet, performance guarantee, or market settlement is attached to one of these buses, whether the document says so or not.

The same hardware reads differently at each: a round-trip efficiency in the mid-90s at the DC bus becomes 85 to 90 percent net AC at the POI once PCS, transformer, and auxiliary losses are counted. Comparing two numbers quoted at different boundaries is comparing different quantities — which is why the first question to ask of any figure is where it was measured.

Reviewed August 2026 by Sergey Syrvachev

New to BESS? Start free with the 7-email fundamentals course — no cost, no account.

What it is (precise)

Follow the energy on the one-line diagram and the candidate boundaries appear in order: cell terminals, then the DC bus where racks land on the PCS, then the PCS AC terminals at low voltage — typically in the 400-800 V range — then the medium-voltage side of the step-up transformer, then the collection system, and finally the point of interconnection with its revenue meter.

Each is a legitimate place to define power, energy, or efficiency, and none of them is 'the' number. A megawatt at the PCS terminals is not a megawatt at the POI: transformer and cable losses sit between them, and the auxiliary load that keeps the plant alive is fed from somewhere on that same chain.

Two rules make the concept operational. First, any ratio — round-trip efficiency, availability, a capacity-test result against a guarantee — needs its numerator and denominator on the same boundary, or the ratio is undefined in practice. Second, any comparison between two figures needs both on the same boundary, under stated conditions, before it says anything about the equipment.

What changes between buses is specific and countable: PCS conversion loss, transformer no-load and load losses, and auxiliary consumption, whose effect depends on whether station service is fed upstream or downstream of the meter that produces the number.

The concept travels under aliases. Contracts and test protocols call it the guarantee boundary or the test boundary; interconnection agreements define it implicitly by naming the POI; settlement systems call it the revenue meter. These are all the same question — which bus — and a project is internally consistent only when every document answers it the same way.

Why it matters in a real grid-scale project

The size of the effect is not subtle. For modern LFP systems, DC round-trip efficiency is commonly quoted near 92 to 96 percent, AC RTE at the PCS terminals near 88 to 93 percent, and net AC RTE at the POI near 85 to 90 percent. Each step down the chain strips roughly one to three points off the headline figure, so a DC number and a net-AC-at-POI number for identical hardware can differ by five or more points. A bid that looks two points better than a rival often just drew its boundary two buses earlier.

The loss chain multiplies through in a way you can check by hand: about 96 percent through the battery, roughly 98.5 percent through the PCS each way, about 99.5 percent through the transformer each way, and around 98 percent left after auxiliaries gives approximately 90 percent AC-to-AC. Slide each assumption toward its weaker end — a hotter climate, heavier HVAC duty, more idle standby — and the same plant lands closer to 86 to 88 percent. Every one of those factors lives between two boundaries, so the boundary you pick decides which of them your number includes.

The financial model inherits all of it. The effective charging cost is the market price divided by round-trip efficiency: at 91 percent, $50/MWh of charging energy costs about $55 per delivered MWh; six points lower and it is about $59. That is the mechanism by which an efficiency guarantee written at the wrong measurement boundary quietly moves levelized cost by dollars per MWh — the model assumes one bus, the guarantee protects another, and the gap between them is unhedged loss the owner simply eats.

One quantity, five boundaries, three quoted values — so a ratio is only comparable when its numerator and denominator land on the same one.
battery rackscells→ modulesDC busenclosurePCSDC → ACunittransformerLV → MVMV collectionfeeders + busmaintransformerMV → HVHV bay +gen-tiebreaker,disconnectsPOI + meterthe boundaryauxiliary + HVACa load between the buses, not astage of the chainLFP RTE, one quantity:123451cell terminals2~92–96%— DC bus at the rack3~88–93%— PCS AC terminals4unit-transformer MV terminals5~85–90% net AC— POI — the settlement boundaryenergy outenergy inboth at the PCS AC terminals — a round-trip efficiencyenergy outenergy inone at each end — a different quantity, not a round-trip efficiency

Each boundary down the chain costs a point or a few: PCS conversion loss, transformer no-load and load losses, then auxiliary and HVAC consumption. Comparing two numbers quoted at different boundaries compares two different questions. The contract aliases — guarantee boundary, test boundary, revenue meter — are different documents asking the same one, and merchant revenue and charging cost are both metered at the POI. For any figure at all: which boundary, what C-rate, what temperature, what depth of discharge, auxiliaries included?

Key facts
The recurring boundaries
Cell terminals, DC bus at the rack, PCS AC terminals, MV transformer, POI / revenue meter
Same hardware, different numbers
LFP round-trip efficiency: ~92-96% DC, ~88-93% at PCS AC terminals, ~85-90% net AC at POI
Cost of each step
Each boundary down the chain strips roughly one to three points off an efficiency figure
What sits between buses
PCS conversion loss, transformer no-load and load losses, auxiliary/HVAC consumption
The ratio rule
Numerator and denominator of any ratio — RTE, availability, test vs guarantee — must be on the same boundary
Contract aliases
Guarantee boundary, test boundary, revenue meter — different documents, same question
The settlement boundary
Merchant revenue and charging cost are both metered at the POI revenue meter
Default questions for any figure
Which boundary, what C-rate, what temperature, what depth of discharge, auxiliaries included?

How it shows up in specs, studies and contracts

On a datasheet, vendors quote the flattering boundary by default: a container sheet showing 95 percent efficiency almost certainly means DC-side without HVAC. The counter is a fixed set of questions asked of every figure — measured at which boundary, at what C-rate, at what ambient temperature, at what depth of discharge, and with auxiliaries included or metered separately. Usable energy deserves the same scrutiny as efficiency, because a DC nameplate MWh and the energy actually deliverable at the POI are separated by the whole loss chain.

Studies and grid codes fix their own boundaries. Interconnection studies, reactive-capability requirements, and power-factor obligations are defined at the POI; capacity-market qualification and merchant settlement happen at the revenue meter. Commissioning is where the boundary stops being abstract: the capacity test discharges between defined endpoints under a witnessed procedure at a defined bus, and the measured energy — not the nameplate — becomes the contractual baseline that degradation guarantees are tracked against for the next fifteen to twenty years.

In contracts, the usable-energy guarantee, the RTE guarantee, the availability guarantee, and the augmentation plan must be written on one measurement boundary, or the contract quietly contradicts itself — a plant can meet a DC-side energy guarantee while missing the POI obligation the offtake agreement actually pays against. Where scope is split between an EPC contract and a battery supply agreement, establish which guarantees sit at which boundary against whose balance sheet, and check that nothing the owner owes its offtaker falls between the two.

Common pitfalls

The classic error is crediting the technology for the boundary. A supplier quoting DC-side RTE or nameplate energy will look several points better than a POI-basis competitor while offering the same or worse hardware; a 95 percent figure and an 87 percent figure can describe the very same system. Before comparing bids, restate every number on one boundary — net AC at the POI is the defensible choice, because it is the bus the project is paid at.

Auxiliary power is the recurring ambiguity. Some suppliers meter station service separately and exclude it from the guarantee entirely, so the guaranteed number and the settled number diverge by the HVAC load. The same trap appears in operations: idle-day auxiliary consumption dragged into a fleet-RTE calculation can make performance look catastrophic when every piece of equipment is exactly on spec — the window and the boundary of the calculation changed, not the plant.

The most expensive version is the unsigned boundary: a capacity or efficiency guarantee executed without the measurement boundary defined gets audited by reality at commissioning, when the witnessed test must happen at some specific meter and each party discovers which bus it thought it had agreed to. The fix costs nothing at signing — mark the guarantee boundary on the single-line diagram, name the meter, and carry the same bus through the financial model, the test protocol, and every guarantee in the stack.

Common misconception

The measurement boundary is a metering detail — the numbers are roughly the same wherever you read them.

In reality: A guarantee, a financial model, and a commissioning test each written on a different boundary can all be individually 'met' while the project misses its revenue forecast — on identical hardware, the gap between buses is that large. The boundary is not a detail of the number; it is part of the number's definition.

Go deeper

Measurement boundary, in context.

The Grid-Scale BESS course covers measurement boundary — and the rest of the system — from the ground up, the way it actually gets deployed.

Browse the course