Battery augmentation on a 200 MW BESS portfolio is a capital event that most operators treat as inevitable — a fixed cost of running storage assets through their warranty period. One operator decided to test whether it was inevitable, or just a consequence of letting cell imbalance and thermal anomalies go unmanaged. By deploying OxMaint's cell balancing trending and thermal anomaly alert workflows across their 200 MW fleet, they extended average battery state of health by 2.1 years against the original augmentation schedule — deferring a nine-figure capital outlay and recovering margin that had been quietly disappearing cycle by cycle. Here is the technical picture of how that result was achieved, and what any BESS O&M team can implement today. Start tracking your BESS fleet's SOH trajectory in OxMaint.
Case Study · BESS · Battery Life Extension
BESS Operator Extends SOH by 2.1 Years on a 200 MW Portfolio With Predictive Cell Balancing
How cell voltage imbalance trending and thermal anomaly alerts in OxMaint deferred battery augmentation and recovered fleet capacity that was degrading faster than it should have.
SOH Trajectory — 200 MW Fleet
Reactive path
OxMaint path
SOH extension
+2.1 years
2.1 yrs
Battery SOH extension achieved vs original augmentation forecast
200 MW
Portfolio size — grid-scale BESS with multiple container installations
14 days
Lead time OxMaint thermal alerts gave before hot-spot events escalated to container-level risk
$40M+
Estimated augmentation CapEx deferred by 2.1 years of additional SOH life
Why BESS SOH Degrades Faster Than It Should
01
Cell Voltage Imbalance — The Accelerant
Manufacturing variation means no two cells in a BESS pack are identical. Over charge and discharge cycles, small differences in internal resistance and capacity compound into measurable cell voltage spread. Cells at the high end of the spread hit the upper voltage limit before the rest of the string — forcing early charge cutoff and robbing the string of usable capacity. Cells at the low end hit the lower limit first on discharge — causing the BMS to protect them by cutting depth of discharge for the whole string. Both effects reduce effective capacity independently of any chemical degradation. Unmanaged imbalance is the single largest avoidable cause of premature SOH decline in grid-scale BESS.
02
Thermal Anomalies Left Unresolved
Temperature is the most powerful driver of lithium-ion degradation. A cell operating 10°C above its optimal range degrades at roughly twice the rate. Hot spots caused by cooling system failures, blocked airflow paths, or HVAC degradation go undetected between periodic walkdowns — accelerating localised cell degradation that spreads to adjacent modules before the next inspection reveals it.
03
SOH Trajectory Not Tracked Per String
Most BESS operators know their system-level SOH. Few know which strings are degrading faster than the fleet average — and therefore which containers will breach the 70% SOH augmentation threshold years ahead of the rest. Without string-level SOH trending, augmentation decisions are reactive and fleet-wide rather than targeted and planned.
What OxMaint Tracks — and What Each Signal Prevents
| Signal Tracked | What OxMaint Monitors | What It Prevents | Alert Threshold |
|---|---|---|---|
| Cell Voltage Imbalance | Max–min cell voltage spread per string per cycle, trended over time | Premature capacity fade from unbalanced depth of discharge across cells | Alert: spread >25mV sustained over 5 cycles |
| Rack Zone Temperature | Temperature per rack zone at each inspection interval, trended against baseline | Hot-spot formation and localised degradation from cooling system degradation | Alert: >5°C above zone baseline or >35°C absolute |
| SOH Trajectory Per String | Capacity retention per string across charge cycles, forecast to 70% threshold | Unplanned augmentation events — enables 90-day planned replacement window | Alert: 70% SOH forecast within 90 days |
| HVAC Runtime and Fault Events | Cooling system PM compliance, fault event count, and filter replacement records per container | Thermal runaway risk from cooling system degradation going undetected between inspections | Alert: HVAC fault count >3 in 30 days or PM overdue >14 days |
| SOC Deviation Across Strings | State of charge spread across parallel strings at rest — deviation from expected balance | Accelerated capacity fade from strings operating outside their safe charge window | Alert: SOC deviation >8% between parallel strings at rest |
Your BESS Is Degrading Faster Than It Needs To — And the Data to Prove It Already Exists.
OxMaint connects cell imbalance trending, thermal anomaly alerts, and SOH trajectory forecasting into a single BESS health platform — giving your O&M team 90 days of planning lead time instead of 90 days of emergency procurement.
How the 2.1-Year Extension Was Achieved — Phase by Phase
Phase 1 · Months 1–3
Fleet-Wide Cell Imbalance Baseline
All 200 MW of BESS containers registered in OxMaint with string-level asset records. BMS data exports used to establish per-string cell voltage spread baselines. First balancing alert generated in week 3 — 14 strings showing voltage spread above the 25mV sustained threshold. Balancing interventions scheduled and completed within 21 days.
Outcome: Fleet imbalance index reduced 34% within 90 days of first balancing campaign.
Phase 2 · Months 4–7
Thermal Anomaly Detection Network
Thermal inspection checklists digitalised into OxMaint mobile app. Temperature readings recorded per rack zone at each walkdown and trended against per-zone baselines. First thermal alert raised in month 5 — three containers with HVAC filter blockage causing zone temperature rise of 8°C above baseline. HVAC maintenance completed 12 days before projected thermal event threshold breach.
Outcome: Zero thermal events requiring container shutdown in the 18 months following HVAC PM compliance enforcement via OxMaint.
Phase 3 · Months 8–12
SOH Trajectory Forecasting and Augmentation Planning
With 8 months of capacity retention data per string in OxMaint, the operations team ran the 90-day SOH forecast for every string in the fleet. Result: 6 strings projected to breach the 70% SOH threshold within 14 months — previously invisible. Planned replacement ordered at standard lead times rather than emergency premium. Remaining fleet showed SOH trajectory 2.1 years ahead of original augmentation plan.
Outcome: 6 targeted string replacements at planned cost. Fleet-wide augmentation deferred from Year 8 to Year 10.1 of operations.
Before vs After — What Changed for the Operations Team
Without OxMaint
Cell voltage imbalance data in BMS — no system trending it over weeks or triggering action
Thermal inspections on paper walkdown sheets — no trend comparison, anomalies missed between visits
SOH known at system level only — no string-level trajectory, no augmentation forecast lead time
HVAC filter replacements tracked in spreadsheets — missed PMs not visible until equipment fault
Augmentation planned reactively — emergency procurement premium, compressed installation schedule
With OxMaint
Cell voltage spread trended per string — balancing intervention triggered automatically on threshold breach
Thermal readings trended per rack zone — HVAC work orders raised 14 days before anomaly becomes risk
String-level SOH forecast updated each inspection cycle — 90-day augmentation planning window maintained
HVAC PM compliance tracked per container — overdue maintenance visible before it affects temperature
Augmentation planned 90 days in advance — standard procurement lead time, no emergency premium
Frequently Asked Questions
How does OxMaint get cell voltage and temperature data from our BMS?
OxMaint supports structured data import via CSV export from BMS systems, as well as manual data entry from handheld instruments via the mobile app. The operator in this case study used weekly BMS CSV exports. For sites with historian connectivity, OxMaint's API integration routes data automatically. Book a demo to discuss the integration pathway for your BMS.
At what point in a BESS asset's life does deploying OxMaint deliver the most benefit?
The earlier OxMaint is deployed, the more accurate the SOH trend baseline. Deploying in years 1–3 of operations gives the clearest trajectory forecast by year 5. That said, the operator in this study deployed OxMaint at year 6 of an 8-year augmentation forecast and still pushed the augmentation date to year 10.1 — demonstrating significant benefit even mid-asset-life. Start building your BESS baseline in OxMaint today.
Does OxMaint work with containerised BESS installations from multiple manufacturers?
Yes. OxMaint's asset register is manufacturer-agnostic. Each container is registered as an asset with its own BMS data source, string count, rack layout, and HVAC configuration. PM templates are configured per container type — meaning a mixed-fleet portfolio runs all assets under one system.
How is the 2.1-year SOH extension calculated — is it conservative?
The 2.1-year figure is the difference between the original augmentation date (year 8) projected from pre-OxMaint degradation rates, and the updated augmentation date (year 10.1) projected from the fleet's actual capacity retention trajectory 12 months after OxMaint deployment. The calculation uses measured capacity retention data per string, not modelled assumptions.
Make Augmentation a Planned Event, Not a Crisis
2.1 Years of Extra Battery Life Is Already Inside Your BESS Fleet. OxMaint Helps You Find It.
Cell balancing trending, thermal anomaly alerts, and string-level SOH forecasting — all in a CMMS built for grid-scale BESS operations. Start deferring augmentation CapEx with data, not guesswork.
