Degradation-Aware BESS Dispatch: How State-of-Health Accuracy Changes Your Revenue Stack

Singapore's ancillary services market — specifically Primary Reserve (PR), Contingency Reserve (CR), and Regulation services under the Energy Market Authority's (EMA) USEP framework — has been the primary revenue driver for the wave of BESS deployments commissioned between 2020 and 2024.

For generators holding BESS assets and trading into this market, the revenue model is straightforward in theory: commit capacity, deliver response within specification, collect payment. In practice, the profitability of BESS dispatch is governed almost entirely by how accurately you know your asset's true State-of-Health — and most operators don't.

The BMS SoH → Revenue Pipeline

Your dispatch software relies on BMS-reported SoH to calculate the usable energy window for each trading interval. If your 20 MWh BESS reports 85% SoH, your dispatch engine treats it as having 17 MWh usable capacity. That determines:

• Regulation bid volume — how many MW of regulation up/down you commit to EMA
• Dispatch depth — how aggressively you cycle in energy arbitrage windows
• State-of-charge management — where you park the battery between dispatch events

When BMS SoH is wrong — and for assets 2+ years old, it typically is — every downstream calculation in your dispatch stack inherits the error.

Scenario A: BMS Overestimates SoH

This is the more dangerous case. BMS reports 85% SoH, actual capacity is 74%.

Regulation bids: You commit 8 MW regulation capacity. When a regulation-up event requires sustained discharge, your asset reaches its physical lower SoC limit before the event window closes. You fail to deliver — costing you the regulation payment for that interval and potentially triggering a non-compliance flag under EMA rules.

Energy arbitrage: You schedule a full charge from 0900–1200 during low USEP price window, intending to discharge 1400–1700 during peak. But actual capacity is lower — your projected discharge falls short of the contracted volume.

Degradation acceleration: Dispatch software calculates charge rate based on usable window duration. If it believes usable capacity is 17 MWh but actual is 14.8 MWh, it charges at effectively higher C-rate to fill the assumed window — directly accelerating capacity fade and lithium plating risk.

Scenario B: BMS Underestimates SoH

Less dangerous, but expensive. BMS reports 72% SoH, actual capacity is 81%.

Stranded capacity: You're holding 1.62 MWh/GWh of usable capacity in reserve that your dispatch engine doesn't access. For a 20 MWh BESS at an arbitrage delta of S$80/MWh, this is S$130/day in unrealized revenue — S$47k/year.

Conservative cycling: If your SoC management is set to protect a "degraded" asset, you operate at shallower depth of discharge than necessary — further reducing dispatch yield.

Both scenarios are common. In our audit experience across Singapore-region BESS assets, BMS SoH errors of ±8–14 percentage points are typical in assets operating for 24+ months.

Frequency Regulation: Where SoH Errors Are Most Expensive

Singapore's ancillary services require fast response — Primary Reserve requires injection within 30 seconds of a frequency event. For BESS, this is trivially achievable mechanically. The challenge is capacity reservation: EMA requires that reserved capacity be continuously available.

This creates the reservation-versus-dispatch tension:

If your BMS overstates SoH:

• You reserve more capacity than physically exists
• A severe frequency event requiring maximum injection cannot be fully delivered
• Non-delivery under ancillary service contract terms triggers financial penalties

If your SoH is correct:

• You reserve precisely the capacity you can deliver
• You release the remaining SoC window for energy arbitrage
• Dispatch software runs a tighter, more profitable intraday stack

The Singapore electricity market has deepened: USEP spreads have widened, and the number of BESS bidders has not grown proportionally with overall renewables capacity. Operators with accurate SoH have a structural advantage in frequency regulation bidding — they can commit closer to actual capacity, win more allocation, and deliver reliably.

The Degradation-Aware Dispatch Framework

Correcting for SoH error in your dispatch stack requires three components:

1. Physics-Based SoH Baseline (Oxaide Verify)

A one-time forensic audit of your full cycling history produces a calibrated SoH baseline and degradation mode classification. This replaces BMS SoH as the initial operating point in your dispatch model.

Typical engagement: 5 business days, S$4,800.

2. SoH Trajectory Model (Oxaide Horizon)

Once you have a calibrated baseline, real-time SoH tracking through Oxaide Horizon's streaming analytics engine maintains accuracy across future cycling. The model updates dynamically as each cycle completes:

• Adjusts usable SoC window as capacity changes
• Detects when cycling protocol is accelerating degradation vs. baseline trajectory
• Triggers operational alerts when lithium plating risk score increases

3. Dispatch Integration

Horizon exposes a lightweight API that your Energy Management System or trading platform can query for:

• Current True SoH (float, 0-1)
• Usable energy window (MWh)
• Recommended SoC ceiling/floor for protective operation
• Thermal risk flag (boolean + risk score)

For most commercial dispatch software stacks, integration is a configuration change — not a development project.

Revenue Impact Quantification

Based on typical 10 MW / 20 MWh BESS assets operating in Singapore's ancillary services market:

Error Type	SoH Gap	Annual Revenue Impact
BMS overestimate (non-delivery penalties)	+10 percentage pts	S$85k–160k losses
BMS overestimate (accelerated degradation cycle cost)	+10 percentage pts	S$60k–120k degradation cost
BMS underestimate (stranded capacity)	-8 percentage pts	S$35k–55k unrealized revenue

Correcting a +10 point SoH overestimate through physics-informed dispatch removes S$145k–280k in annual risk exposure for a standard 10 MW asset. The Verify audit + Horizon annual subscription is materially lower than any of these figures.

Singapore Regulatory Context

EMA's Market Rules require BESS operators to maintain accurate metering and capacity declarations. Incorrect capacity bids resulting from BMS SoH errors are not a regulatory defence — the asset owner is responsible for the accuracy of their declarations.

As EMA increases BESS penetration targets and ancillary services procurement — the Authority's Forward SG grid plan projects significantly higher BESS capacity by 2030 — enforcement of declaration accuracy is expected to tighten. Operators relying on uncalibrated BMS SoH figures face both financial and compliance risk.

---

The BESS operators who outperform in Singapore's electricity market in the next 5 years will be those who manage assets based on physics, not BMS approximations. State-of-Health accuracy is not a back-office data quality question — it sits directly in your revenue P&L.

Commission a SoH Calibration Audit → | Explore Horizon Real-Time Monitoring