Equivalent full cycle EFC

What it is (precise)

The arithmetic is one division: EFC = cumulative energy throughput ÷ rated usable capacity. A 100 MWh system that discharges 50 MWh in the morning and 50 MWh in the evening has performed one EFC, not two cycles — partial charge and discharge events are summed by the energy they move and normalized to a full capacity's worth.

For irregular state-of-charge traces there are two scoring methods: simple throughput division, and rainflow counting, an algorithm borrowed from fatigue analysis that decomposes the trace into equivalent full and half cycles. They agree on steady daily duty and diverge on jagged profiles, which is exactly where the choice starts to matter — and the warranty annex, not a standard, picks the method.

The denominator and the metering point are choices too, and each one changes the count. Most warranty frameworks normalize to beginning-of-life usable energy at the DC terminals — usable, because the BMS operating window makes usable capacity smaller than nameplate; beginning-of-life, because capacity fades.

A counter normalized instead to the current, State of Health-adjusted capacity reports more EFC from the same throughput as the asset ages: a plant delivering a fixed daily MWh block registers a constant EFC rate against the BOL reference and a rising one against as-measured capacity. Metering at the PCS AC terminals or the point of interconnection instead of DC changes the numerator, because conversion losses and auxiliary loads sit between those points. Same operation, three defensible counts — which is why the definition has to be written down.

Why it matters in a real grid-scale project

EFC is the currency the warranty budget is spent in. Supplier warranties commonly permit around one cycle per day — about 365 EFC per year — or an equivalent annual MWh throughput, and guarantee retained capacity on the assumption that the cap is respected. What a breach costs is asymmetric: run past the cap and the energy-retention guarantee weakens or falls away for the excess period, while the fade those extra cycles caused stays on the asset — the owner keeps the wear and loses the remedy.

The friction is that markets count events while warranties count energy: a trading schedule showing two dispatches a day may be spending anywhere from a fraction of an EFC to two, depending on depth. How dispatch is managed against that budget day to day belongs to the Cycle entry.

EFC also puts a price on the marginal cycle. A serviceable estimate is replacement cost divided by warranted cycle life: at a ~$70/kWh future pack price and ~10,000 warranted EFC for a modern LFP pack, each EFC costs about $7 per MWh discharged in future capacity loss. One EFC already moves a full rated capacity's worth of energy, so lifetime throughput is simply warranted EFC times rated energy — depth of discharge belongs in that arithmetic only when the vendor rated the cycles at partial depth.

A trading spread that does not clear the marginal cycle cost is not profit, and the annual EFC assumption feeds everything downstream of it: the bankable degradation model, the augmentation schedule, and the LCOS, where the same capital spread over 200 versus 365 cycles a year roughly doubles the cost per discharged MWh.

Typical values and standards

Duty profiles translate to EFC burn rates. Daily energy arbitrage books roughly one EFC per day, about 300-365 per year. Frequency regulation produces hundreds of shallow swings a day whose throughput sum usually lands far below the event count.

Stacked merchant assets commonly run around 250-400 EFC per year, and tolling agreements cap the offtaker's duty at roughly 250-450 EFC per year for a one-cycle-per-day profile, with heavier duty negotiated and priced separately. Cycle life is denominated in the same unit: LFP cells are typically rated on the order of 6,000-10,000+ EFC to a ~70% retention threshold under lab conditions at 25 C, NMC roughly 3,000-5,000 under comparable conditions.

On standards: IEC 62933-2-1 covers unit parameters and test methods for electrical energy storage systems, and IEC 61427-2 defines on-grid duty-cycle test regimes — useful for capacity tests, but no standard scores field usage for a warranty. How partial swings are decomposed, which capacity reference the division uses, and where the energy is metered are all set in the warranty annex, contract by contract. Two projects can log the same dispatch year and book materially different EFC totals — the definition, not the duty, is the difference.

How it shows up in specs, studies and contracts

In the warranty annex, the EFC definition is a checklist worth walking line by line: the counting method (throughput division or rainflow), the capacity reference (BOL usable, nameplate, or SOH-adjusted), the metering point (DC terminals, PCS AC, or POI), whether unused annual budget rolls over, what happens to the retention guarantee if the cap is exceeded in one year, and whose meter and logs govern at claim time.

Periodic capacity tests spend throughput too — a witnessed full charge-discharge test is by definition about one EFC — so test frequency is itself a negotiated number that comes out of the same budget.

In operations, the EMS cycle counter must implement the annex definition exactly — same method, same denominator, same metering point. A counter that differs on any of the three produces a discrepancy that nobody sees until a capacity claim is denied on logged throughput. And in the revenue model, compare the assumed duty against the warranted duty explicitly: a merchant case built on 400 EFC a year against a warranty written at 365 is a gap someone pays for, either in a negotiated heavier-duty warranty up front or in augmentation later.

Common pitfalls

The central one: EFC is an accounting unit, not a physics model. Two 50% swings book the same EFC as one full cycle but generally cause less wear, while the same throughput delivered hot and fast causes more. Calendar fade accrues regardless of the counter — an asset running below roughly 100 EFC per year is calendar-dominated: time, not the counter, sets its end of life. Bankable degradation models track depth, temperature, C-rate and resting SOC alongside the EFC count; an EFC total alone under-specifies wear.

Two accounting traps recur. First, double-counting depth: one EFC already represents a full capacity's worth of throughput, so multiplying warranted EFC by rated energy gives lifetime throughput directly — dividing again by usable depth double-counts it, unless the cycle rating was explicitly quoted at partial depth of discharge.

Second, comparing vendor quotes across incompatible bases: a 10,000-cycle claim at 80% depth to a 60% retention threshold normalizes to about 8,000 EFC to a laxer end condition, so convert every bid to EFC at a stated threshold and temperature before ranking. The unit exists to make throughput comparable — but only after the definitions are aligned.