Every BESS contract is written against the capacity the battery will have at year ten, not the capacity it has on day one. A 100 MWh system can lose up to 5% of its capacity in the first year alone, and by year fifteen that fade can reach 40%. The battery isn't failing — it's ageing exactly as the chemistry predicts. The question is whether the O&M program caught the fade early enough to augment before a capacity contract, not after one is missed. Sign up to track cycle count, SOH, and augmentation triggers against every rack in one CMMS.
Why It Matters
State of Health isn't a single number that drifts down smoothly — it follows a bathtub curve, with faster fade early, a stable middle life, and accelerated loss once SOH drops toward the 80% threshold most projects treat as end of life. A BMS dashboard reporting an average SOH can still hide individual cells or racks that have fallen well below that average. Augmentation and repower programs exist to catch that gap between what the dashboard shows and what the asset can actually deliver, before a capacity market or long-term offtake contract is put at risk.
The Three Numbers That Drive Every Augmentation Decision
Augmentation isn't a calendar event — it's a response to measured degradation. Three tracked metrics tell the O&M team when the moment has arrived.
State Of Health
Usable capacity against original nameplate. Most projects treat 80% SOH as the end-of-life trigger for first-life applications.
Cycle Count
Full and partial cycles logged against depth-of-discharge, since fade tracks cycling and calendar age at the same time, not one alone.
Contract Threshold
The minimum capacity a Capacity Market or offtake agreement requires the asset to still deliver, often for up to fifteen years.
SOH tells the team how much capacity has already been lost, cycle count explains why the fade is happening at the rate it is, and the contract threshold sets the deadline by which augmentation has to be complete.
The BESS Lifecycle From Commissioning To Repower
| Stage |
Typical SOH |
O&M Focus |
| Commissioning |
100% |
Baseline SOH, thermal, and BMS calibration records for every rack |
| Early Life |
95-98% |
Fast initial fade tracked closely against the manufacturer's degradation curve |
| Stable Mid-Life |
85-95% |
Routine cycle logging and thermal monitoring at a steady fade rate |
| Augmentation Trigger |
Approaching 80% |
DC or AC-coupled repower planning begins before the contract threshold is breached |
Catch Capacity Fade Before The Contract Does
Oxmaint logs SOH, cycle count, and thermal readings against every rack, so a fading cell shows up as a scheduled task, not a missed Extended Performance Test. Sign up for a free trial to run it on your own fleet, or book a demo to see it configured for your site.
Where Augmentation Programs Fall Behind
Fleet-Average SOH Only
Dashboard shows a healthy average while individual racks sit well below it
Linear Fade Assumed
Planning against a flat 2% per year when real degradation accelerates near end of life
Cycle Data Not Logged
Partial cycles and depth-of-discharge never recorded, so fade rate can't be explained
Augmentation Planned Too Late
Repower procurement started only after a capacity test has already been failed
Thermal Records Incomplete
Temperature history missing for cells now suspected of accelerated calendar aging
Warranty Evidence Scattered
SOH history split across BMS exports and spreadsheets when a claim needs proof
Frequently Asked Questions
Q
What's the difference between BESS augmentation and repowering?
The terms are largely used together — augmentation adds new battery capacity to an existing system to restore or exceed its original nameplate output, while repowering describes the broader project of integrating that new capacity, either within the existing DC architecture or alongside it on the AC side.
Q
Why does average SOH from the BMS understate the real risk?
Degradation isn't uniform across racks — once average SOH drops below roughly 80%, fade tends to accelerate, meaning many individual cells can already be lower than the reported average. A single fleet-wide number hides which specific racks need attention first.
Q
Why does capacity fade matter for Capacity Market contracts specifically?
Capacity Market agreements are written against end-of-life capacity, not nameplate, and batteries often have to prove via Extended Performance Tests that they can still deliver contracted capacity for up to fifteen years — falling short risks termination of the contract itself.
Turn Degradation Into A Scheduled Task, Not A Surprise
Oxmaint keeps SOH history, cycle counts, thermal records, and augmentation timelines tied to their evidence in one auditable log, so proving contract compliance doesn't mean pulling exports from five BMS dashboards. Sign up for a free trial to run it on your own fleet, or book a demo to see it configured for your team.
.png)
