Energy throughput
Energy throughput is the running total of energy that has passed through a battery system since commissioning, measured in MWh — the odometer of the asset. Power says how hard the plant is working right now and cycle count scores the work in normalized units; throughput is the raw total underneath both, and cycle aging scales with the megawatt-hours moved, not with the number of dispatch events.
It is also the quantity battery warranties actually meter: annual and lifetime throughput caps sit alongside cycle limits in most supply agreements, logged by the EMS and produced as evidence when a capacity claim is tested. And like any odometer reading, the number means nothing until you know where it was measured — DC terminals or AC — and which direction of flow it counts.
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)
Throughput is the integral of energy flow through the battery over time — a flow quantity, where capacity is a stock. The definition sounds complete until you try to meter it, and then two conventions have to be pinned down before any two documents can be compared. Direction first: some contracts count discharge energy only, others sum charge and discharge, and because charge energy roughly mirrors discharge energy plus losses, the two conventions differ by roughly a factor of two on the same operation.
Boundary second: DC at the battery terminals and AC at the PCS output or point of interconnection are different numbers separated by the whole loss chain, and battery warranties are usually written against DC energy throughput at reference conditions while revenue is settled on AC at the POI. Before comparing any two throughput figures, pin both conventions: which directions were summed, and at which bus.
Throughput and cycle count are the same running total in different units. Equivalent full cycles are cumulative MWh throughput divided by rated usable energy, so one full cycle per day accumulates about 365 EFC a year — and the reference capacity behind that division (beginning-of-life usable energy in most warranty frameworks, not the faded as-measured value) decides how fast the counter runs as the asset ages.
Partial and irregular operation is scored either by simple throughput division or by rainflow counting over the SOC trace, and the two methods diverge exactly on the jagged profiles where the choice matters. The mechanics of all of this live under Cycle; the point here is that whichever counting method applies, the underlying meter is energy moved.
Why it matters in a real grid-scale project
Throughput is the input variable of cycle aging. Each megawatt-hour pushed through the cells advances particle fatigue and SEI regrowth, with depth of discharge, C-rate and temperature shaping how much damage each MWh does — which is why warranty degradation models are parameterized on cumulative throughput under a stated operating envelope rather than on calendar time alone.
The complement is just as important: calendar aging accrues regardless of use, and a system cycling once per day at 0.25C often loses more capacity to time than to throughput. So a low throughput total is not proof of a young battery, and two assets with identical throughput totals but different resting SOC and temperature histories are not equally aged.
Commercially, every MWh of energy revenue is throughput spent from a finite budget. The supplier warranty states that budget as an annual figure — MWh, EFC per year, or cycles per day — and the cumulative total in the BMS and EMS logs is the draw against it, readable month by month like any other metered allowance.
Run two full cycles a day against an allowance priced for one and the draw rate doubles: half the annual budget is gone by July. Operators who manage this well put a number on the marginal cycle — commonly a few dollars to a few tens of dollars per MWh cycled — and ask whether the trade in front of them clears it.
Warranties usually meter this on the DC side from BMS and EMS logs, a different boundary from the POI settlement meter and sometimes counting charge as well as discharge. A plant can read comfortably inside its cap on settlement data while the odometer the claim is scored on has already crossed it — reconcile the two routinely, not at claim time.
- Definition
- Cumulative MWh through the battery since commissioning — a flow, not a stock (capacity)
- Link to cycles
- Equivalent full cycles = MWh throughput ÷ rated usable energy; 1 cycle/day ≈ 365 EFC/yr
- Warranty basis
- Usually DC energy throughput or cycle count at reference conditions; annual cap EMS-metered and logged
- Scale check
- 100 MW / 400 MWh at 1 cycle/day ≈ 146,000 MWh discharged/yr; on the order of 2.9 TWh over 20 years
- Charge vs discharge
- AC energy in exceeds AC energy out by roughly 9-16% at 86-92% AC round-trip efficiency
- Typical warranty cycling assumption
- Commonly 300-365 EFC/yr at a defined depth of discharge, over 15-20 year horizons
- Auxiliary share
- Commonly ~1-3% of annual throughput (climate-dependent), purchased but never sold
- Marginal cycle cost
- Degradation commonly priced at a few $ to a few tens of $ per MWh cycled when dispatch decisions are made
Typical values and standards
The arithmetic is worth internalizing on the canonical plant. A 100 MW / 400 MWh 4-hour system running one full cycle per day discharges 400 MWh × 365 = 146,000 MWh a year — 365 EFC against its beginning-of-life rating — and on the order of 2.9 TWh over a 20-year life at constant duty, though the deliverable number shrinks as capacity fades unless augmentation restores it.
Warranty cycling assumptions sit right around this duty: commonly 300 to 365 equivalent full cycles per year at a defined depth of discharge, over horizons of 15 to 20 years, with calendar and cycle fade warranted together through a single retention curve backed by the annual throughput cap.
The charge side of the ledger is always larger than the discharge side. At the canonical 86-92 percent AC round-trip efficiency, AC energy in exceeds AC energy out by roughly 9-16 percent, and auxiliary consumption — HVAC, controls, BMS — commonly adds another 1-3 percent of annual throughput depending on climate and thermal design.
Both wedges are real energy purchased and never sold, so a revenue model built on discharge throughput alone misses the cost of the difference. Verification leans on the same instruments as the capacity warranty: a Reference Performance Test at contractually defined temperature, C-rate and SOC window, with test methodology for ESS performance standardized in the IEC 62933 series, and the BMS/EMS throughput logs as the running record between tests.
How it shows up in specs, studies and contracts
In the warranty exhibit, throughput appears as the operating envelope's energy line: an annual MWh cap, an EFC-per-year figure, sometimes a lifetime total — frequently alongside a separate cycle cap, and the practical question is which binds first under the intended dispatch.
The EMS meters cumulative throughput against the cap, and its logs — with the BMS temperature and SOC history — are the evidence a claim survives or dies on: exceed the contracted annual throughput and the supplier can void or pro-rate the energy-retention guarantee. Degradation reports from independent engineers plot measured fade against cumulative throughput to test whether the fleet is tracking the warranted curve, which makes the odometer a bankability document, not just an operations counter.
Reading any throughput clause, pin down four things. The metering point — DC terminals or AC, and whose meter governs. The direction basis — discharge only, or charge plus discharge. The normalization reference for EFC — beginning-of-life usable energy or the current, State of Health-adjusted capacity, which diverge more every year.
And the scoring method for partial cycles — throughput division or rainflow, stated in the contract rather than assumed. Then reconcile the revenue model's dispatch profile against the answer: the profile the model monetizes and the envelope the warranty permits are separate documents, and projects get burned where they disagree.
Common pitfalls
The recurring boundary error is tracking warranty position on the wrong meter. The POI revenue meter reads AC, net of PCS, transformer and auxiliary losses; the warranty counter usually runs DC at the battery terminals, and may be summing both directions of flow. The two drift apart by design, so a plant can look comfortably inside its cap on settlement data while the DC log the claim will be scored on is already over.
The companion error is treating the cycle cap and the throughput cap as redundant statements of one limit — they are linked through a reference capacity that fades, so an asset can be inside one and outside the other, and the contract decides which one voids the guarantee.
The quieter leak is throughput that never earned revenue. SOC restoration after frequency events, rack balancing, commissioning and Reference Performance Test discharges, and availability-driven maintenance cycling all advance the total; whether they count against the cap is a drafting question, so check what the contract exempts rather than assuming the meter only runs when the market pays.
And resist the shallow-duty complacency read: a regulation-heavy asset with few visible full discharges is still accruing real MWh through the cells, and its throughput budget is consumed by energy moved, not by how dramatic any single dispatch looked.
The revenue meter at the POI tells you where the plant stands against its warranty throughput cap.
In reality: Most warranties meter throughput on the DC side at the battery terminals, from BMS and EMS logs — a different boundary from the POI meter, separated by PCS, transformer and auxiliary losses. The contract may also count charge as well as discharge energy, and normalize equivalent full cycles to beginning-of-life capacity while the meter sees faded reality. A plant can read comfortably inside its cap on settlement data while the odometer the claim will be scored on has already crossed it. Reconcile the two meters routinely, not at claim time.
Energy throughput, in context.
The Grid-Scale BESS course covers energy throughput — and the rest of the system — from the ground up, the way it actually gets deployed.