What evidence does an OEM warranty claim need?

Typically cell-level voltage histograms, the last 90 days of temperature and SoC traces, all relevant BMS fault events, and SoH versus the contracted curve. Capturing this continuously — not reconstructing it after the fact — is what makes a claim defensible.

Can good data also work against me?

It can surface that your own dispatch caused the degradation (e.g. high-SoC dwell or C-rate exceedances). That’s exactly why operators want to see it first — to fix dispatch before it becomes the OEM’s defence.

BESS metric

Warranty as a data product

Turning operating data into a defensible — or contestable — warranty position.

Quick answer

Treating the BESS warranty as a data product means continuously measuring the operating conditions and degradation the contract actually cares about — SoH curve, energy throughput, SoC/temperature windows, C-rate — so that a claim is backed by evidence and an exclusion can be contested rather than assumed.

Definition

BESS warranties hinge on two limits (capacity retention and energy throughput) plus operating-window conditions whose violation voids cover. Most operators discover where they stand only when a dispute arises. As a data product, the warranty position is computed continuously from SCADA/BMS data and kept claim-ready.

Typical range

Warranty floors: ≥70% SoH at 10 years (or ≥60% at 20), plus an energy-throughput cap in MWh/EFC. Exclusions commonly cover SoC-window, temperature-window, cycles/day, and C-rate violations.

Why it matters

Warranty disputes are won or lost on data. If you can show degradation exceeding 2× the contracted curve while staying inside every operating window, you have a claim. If the OEM can show a temperature- or SoC-window violation, they have a defence. Whoever holds the better-instrumented record wins.

How NuraVolt tracks it

NuraVolt continuously tracks SoH against the contracted curve, accrues EFC against the throughput budget, and logs every SoC-, temperature-, and C-rate-window event with the cell-level evidence (voltage histograms, 90-day temperature and SoC traces, BMS fault logs) that an OEM claim requires.

Methodology & sources: public/data/manuals/seed/synthetic/bess-warranty-and-degradation.md

Frequently asked questions

See this on your own plants

NuraVolt turns your SCADA and BMS data into early fault detection, degradation-aware BESS analytics, and audit-ready reporting. A fixed-scope audit shows you what we’d find on your portfolio.

Book an audit Try the live demo