Flagship Product

SHIELD Contract Risk IntelligenceEARLY ACCESS

Am I signing a bad BESS contract? SHIELD answers the questions your legal team can't — because they're technical, not legal.

?Where is OEM risk transfer incomplete?
?Which terms are outside market standard?
?Where am I exposed on throughput, augmentation, warranty, and interface scope?
85+
Risk Parameters
16
Quality Gates
21
Cert. Checks
25
Acceptance Tests
6
LD Risk Areas

Availability Risk Exposure

97% availability sounds standard — until you read the fine print. How is it calculated? Are planned outages excluded? Is it measured at the container, system, or POI level? Does the LTSA tie availability guarantees to O&M fee escalation — or does coverage weaken as the asset ages? A 3% gap in definition can mean weeks of uncompensated downtime.

SAT — Are You Testing What Matters?

Are you measuring usable energy at the BESS meter or at the DC terminal? Is RTE measured AC-AC or DC-DC? Is power tested at 51°C ambient or lab conditions? Does your SAT cover fire suppression system activation, FACP response, and chiller performance under peak ambient — or just the battery? The wrong measurement point or missing test can lock in years of underperformance you can't claim against.

FAT — Evidence, Not Declarations

Repairing at site is a mess — logistically, commercially, and contractually. FAT is where you catch defects before they become site-level problems: DCIR variance, capacity shortfalls, cell age, thermal non-uniformity, BMS communication faults, and chiller/FACP integration gaps. And vendor declarations are not bankable — lot-wise capacity and DCIR distributions as raw data, batch traceability from cell to container, and cell-age limits at dispatch are. Evidence packages belong at FAT, not at warranty-claim time.

Warranty Enforceability & the PBG Cliff

A 20-year warranty on the cover page is a commercial wrapper — what matters is whether it pays out. What backs your recourse when the performance bank guarantee steps down? On many contracts, post-year-five recovery collapses to the annual LTSA fee — a fraction of the exposure. Does dispatch variation void the warranty, or is throughput flexibility locked to an agreed SOC, DoD, C-rate, and temperature envelope? If the OEM discontinues the cell line, is there an equivalence clause — or does the warranty hollow out with it? SHIELD maps enforceability year by year against your actual exposure.

Cell, Thermal & Fire Safety Gaps

High DCIR means faster degradation and thermal runaway risk. High cell-to-cell variance means your weakest cell limits the entire rack. But beyond cell quality — does your contract specify fire safety scope clearly? UL 9540A testing, NFPA 855 compliance, deflagration venting, and gas detection obligations are often assumed but not contractually assigned. SHIELD identifies where quality and safety thresholds are missing, too loose, or ambiguously scoped.

LDs, Exclusions & Interface Scope

Are your liquidated damages actually protective — or just decorative? SHIELD stress-tests your LD structure across 6 categories and identifies where caps are too low, where remedies don't bite, and where carve-outs quietly void the guarantees you thought you had. It also maps the interface scope: where does the OEM's obligation end and yours begin? In multi-vendor builds, ambiguity at the BMS–PCS–EMS boundaries is the most common cause of grid-connection delay — and where most post-COD disputes originate.

Commercial and technical risk intelligence for energy contracts. Beyond benchmarking, SHIELD identifies where risk transfer is incomplete, where you are exposed, and what best-in-class terms look like globally — clause by clause, against how your asset will actually operate.

FAQ

Common questions

What does SHIELD actually review?

More than 85 risk parameters across the contract stack: availability definitions and measurement points, FAT and SAT scope, warranty enforceability and the PBG step-down schedule, liquidated damages structure, interface scope between BMS, PCS and EMS, and fire safety obligations.

When should a SHIELD review run?

Before signature, when negotiating leverage is highest. It is also used ahead of FAT, before COD, and when planning augmentation, where integration rights and non-obstruction clauses decide what is possible.

Our lawyers review every contract. Why SHIELD?

SHIELD complements legal review. The exposures it maps are technical: how availability is measured, what a SAT actually tests, whether a warranty pays out in year six. These read as technical specifications, not legal clauses, and rarely surface in a legal pass.

What is the deliverable?

A clause-level risk map of the contract, benchmarked against best-in-class terms globally, with negotiation priorities ranked by exposure and the language needed to close each gap.

Get in Touch

Let's Talk

Whether you're optimizing dispatch, sizing a bid, or evaluating vendors — we'd like to hear from you.

info@elarispower.com