BESS Warranties, LTSA/O&M & Performance Testing.
A reported number below a stated floor is not yet a warranty finding. This course teaches the engineering that decides whether a plant actually delivers what was sold — the guarantees, the measurement boundaries, the acceptance tests, the availability accounting, and the claim and remedy that follow.
One disputed test, followed for four hours.
The course opens on Copper Ridge, a fictional 100 MW / 400 MWh project whose Year-3 capacity test reports 365 MWh against a stated floor of 380. The owner calls it a breach. The supplier calls the run invalid. You vote before you see the evidence.
Then six facts appear: an auxiliary feeder outside the meter boundary, an 11-second clock mismatch, an unreconciled temperature record, utility curtailment during the run, a firmware change after commissioning, and a correction neither party approved.
Every unit returns to that same disputed result and changes what the evidence permits you to decide. By lecture 13.5 you issue the Copper Ridge determination — one page — and explain exactly which evidence changed your original vote.
Six blocks. One weak block breaks the chain.
A warranty is not a percentage — it is a conditional measurement-and-remedy system. The course applies the same six-block review to every promise, and the six initials spell B-METER, because a strong method cannot rescue the wrong meter boundary, and a sound result cannot reach an obligor if responsibility is missing.
- Boundary & baseline Where does the quantity live, and against what reference?
- Metric & method What exactly is calculated, and how?
- Envelope & exclusions Which operating conditions and causal limits apply?
- Term & triggers Which clock runs — calendar, throughput, or the earlier of both?
- Evidence & endpoints Which data, instruments, states and approvals close the test?
- Remedy & responsibility Who must act, who bears which cost, and what happens next?
From the guarantee on paper to the test that proves it.
13 units and 49 lectures across four acts: decode the promise, design the proof, interpret the evidence, recover the value. Each unit ends with a working artefact, not a summary slide.
01 The Year-3 test that “failed” Can a number be below the guarantee and still be inconclusive? Output: promise inventory and a first claim vote.
- 1.1 The Year-3 test that “failed” 4 min
- 1.2 A warranty is a risk map, not a brochure 4 min
- 1.3 How the course and case file work 4 min
02 The warranty stack and risk ownership Which document and which company actually stand behind the promise. Output: document stack and responsibility matrix.
- 2.1 Where the warranty actually lives 6 min
- 2.2 Four different promises 6 min
- 2.3 When coverage starts and who can enforce it 6 min
03 Definitions that decide money What MW, MWh, RTE and availability actually mean in this contract. Output: boundary drawing and definition register.
- 3.1 Draw the boundary before you quote the number 7 min
- 3.2 Which MWh? 7 min
- 3.3 Operating vocabulary that burns warranty 6 min
04 Degradation, operating envelope and augmentation What operating history the guarantee assumes — and what happens when the project departs from it.
- 4.1 Why warranty curves are conditional 7 min
- 4.2 The allowed operating envelope 6 min
- 4.3 Oversize, augment, or replace? 5 min
- 4.4 Mini-case: build the throughput budget 4 min
05 Write the test constitution before the purchase order Where FAT, SAT and commissioning sit, and whether two competent teams would reach the same decision. Output: readiness and validity checklist.
- 5.1 The test lifecycle matrix: type evidence, FAT, SAT, commissioning, acceptance 6 min
- 5.2 Readiness gate and preconditions 6 min
- 5.3 Instrumentation and evidence 6 min
- 5.4 Decision rules, invalid tests, and retests 4 min
06 Usable energy and capacity testing How a discharge trace becomes an accepted MWh result. Output: capacity test sheet and calculation template.
- 6.1 Energy is not amp-hours 5 min
- 6.2 Step-by-step usable-energy test 7 min
- 6.3 Valid, invalid, or diagnostic? 4 min
- 6.4 Quick calculation and sanity check 2 min
07 Round-trip efficiency and the loss boundary How two different RTE values can both be correct. Output: RTE boundary diagram and energy ledger.
- 7.1 One ratio, many boundaries 5 min
- 7.2 Close the energy state 5 min
- 7.3 Worked energy balance 4 min
08 Power, P-Q capability, response and availability Which promises are momentary tests and which need an event history. Output: capability matrix and event-code ledger.
- 8.1 Active power and rated duration 5 min
- 8.2 P-Q and MVA capability 5 min
- 8.3 Response, ramp, tracking, and interconnection 4 min
- 8.4 Availability is an event-accounting problem 4 min
09 Safety and certification evidence vs performance proof What a safety report proves — and what must still be tested at the project. Output: evidence applicability map.
- 9.1 What safety evidence proves — and does not 6 min
- 9.2 Performance and interconnection standards map 4 min
- 9.3 Change control and applicability 2 min
10 LTSA and O&M warranty architecture Which promise sits in the supply warranty, which duty sits in the LTSA, and where the interface still fails.
- 10.1 From BSA warranty to LTSA service obligation 5 min
- 10.2 Coverage timeline and trigger stack 5 min
- 10.3 Preventive, corrective, consumables, and spares 6 min
- 10.4 Scope gaps, exclusions, and data rights 4 min
11 Annual testing procedures under the LTSA How a commissioning test becomes a repeatable annual test. Output: run sheet, validity decision and retest rule.
- 11.1 From installation to COD — and back every year 4 min
- 11.2 Readiness, preconditioning, and witnessing 5 min
- 11.3 Capacity and RTE test walkthrough 7 min
- 11.4 Second tests, retests, and annual acceptance 4 min
12 Availability warranty design and accounting Unavailable, undispatched, derated, excluded — or simply unproven? Output: event ledger, clock map and claim decision.
- 12.1 Three availability promises 5 min
- 12.2 The clock, the data, and the work order 5 min
- 12.3 Formula, event taxonomy, and annual roll-up 6 min
- 12.4 Availability claim and remedy 4 min
13 Claims, remedies, bankability and the capstone Can the evidence and remedy restore value, not merely prove disappointment? Output: a one-page determination.
- 13.1 Build the claim evidence pack 5 min
- 13.2 Notice, cure, root cause, and retest 4 min
- 13.3 Remedies that actually restore value 5 min
- 13.4 Bankability and the end-of-warranty cliff 4 min
- 13.5 Capstone: the Copper Ridge determination 4 min
- 13.6 Final quiz and five non-negotiables 2 min
49 lectures across 13 sections. Every section is listed here in full — nothing is hidden until purchase.
All 13 units are scripted; SME and legal review come before recording. Get the publish date →
Everyone who ends up in the same room after a disputed test.
The case is deliberately argued from four sides at once, because that is who the argument involves. It is pitched at an intermediate technical-commercial level: you need to be comfortable with MW, MWh and a one-line diagram, not with contract law.
- Owners and asset managersprotecting the value that was promised, and deciding when a number is actually claimable.
- Integrators and supplierstesting whether obligation and evidence line up before a claim lands.
- Independent engineersasked what the data genuinely supports — and what it does not.
- Operators and O&M teamswhose dispatch history, work orders and event ledger become the evidence.
- Commercial, contract and finance leadswho need the technical basis behind a remedy, a cap or a bankability review.
It does not make you a lawyer, and it does not draft contract language. It gives you the engineering basis to instruct the people who do.
A 15-tool warranty & testing control pack.
The point is not fifteen attractive templates. It is one traceable path from the promise to the meter, from the meter to an accepted decision, and from the decision to an action with an owner and a date.
- Promise inventory and first-pass claim vote
- Warranty document stack and responsibility matrix
- Measurement-boundary drawing and definition register
- Duty-cycle, throughput and excursion budget
- Test readiness and validity checklist
- Capacity test sheet and calculation template
- RTE boundary diagram and energy ledger
- Capability matrix and availability event-code ledger
- Standards and evidence applicability map
- LTSA coverage, service-scope and responsibility matrix
- LTSA annual-test run sheet, validity decision and retest rule
- Availability event ledger, clock map and claim decision
- Claim evidence index and remedy matrix
- Bankability scorecard
- One-page capstone determination
Five questions before you trust a percentage.
If one answer is blank, the promise is not claim-ready. Don't fill the blank with a vendor graphic, a dashboard label or a familiar industry practice — mark it, assign an owner, and close it through the actual project documents.
- What exactly is promised?
- Where is it measured?
- Under what conditions?
- How is failure proven?
- What remedy follows?
Not out yet — the foundation course covers the basics today.
This acceptance-engineering deep dive is in production — join the waitlist to hear the day it publishes. Meanwhile the complete Grid-Scale BESS course already covers degradation, capacity warranties and commissioning at foundation level.
Related deep dives: BESS Engineering Foundations for the loss chain behind an RTE guarantee, and Fundamentals of Fire Safety for the evidence lane Unit 9 keeps separate from performance proof. How a Battery Gets Paid covers the revenue these guarantees are written to protect.