01

What the evidence says

DOE policy supports systematic ESS integration, but it does not turn a vendor warranty into proof that a particular project will deliver its business case.

Nominal DC capacity, usable DC energy and AC energy delivered after auxiliaries are different quantities. The contract must define which one is guaranteed, where it is measured and under what conditions.

Augmentation can preserve a contracted output, but its timing, supplier, compatibility, space, downtime, price, tax, disposal and warranty effect must be allocated before award.

Practical decision guide

Turn the warranty into a measurable operating obligation

Start with the service the facility must receive, not the cycle count printed on a battery brochure. A Philippine factory may need a battery to cap a grid-demand peak, carry a critical bus during generator start, absorb solar that would otherwise be curtailed, or reserve power for a grid service. Those duties impose different power, energy, response, state-of-charge and availability requirements. Write an annual operating envelope with expected dispatch frequency, depth of discharge, charge and discharge power, idle periods, temperature range, reserve, grid outages and simultaneous services. Then ask the supplier to warrant performance inside that envelope. A promise based on one laboratory cycle profile cannot be assumed to cover a hotter room, different C-rate, long high-SOC periods or a dispatch schedule that stacks several revenue and resilience duties.

Define the measurement boundary before negotiating a percentage. Nominal cell or rack capacity is not the same as usable DC energy, and usable DC energy is not the same as AC energy delivered to the owner after PCS losses, HVAC, controls, pumps and transformer losses. State the authoritative meters, time resolution, calibration, data owner, auxiliary treatment, allowable SOC window, preconditioning, ambient conditions and whether charge energy is included. Specify guaranteed kW separately from guaranteed kWh and state whether the commitment applies at beginning of life, each contract year or the end of warranty. If a seller quotes round-trip efficiency, identify the start and end states and meter points; an efficiency test that finishes at a different SOC is not a closed energy balance. Use the same boundary in the financial model, acceptance test and warranty claim.

Treat the degradation curve as a conditional model, not a calendar prophecy. Request the year-by-year guaranteed energy and power at the defined boundary together with every assumption: throughput, equivalent cycles, depth of discharge, C-rate, average and maximum temperature, SOC dwell, calendar time, cell balancing, maintenance and permitted downtime. Clarify which limit governs when calendar ageing and cycle ageing interact, how partial cycles are counted, whether charging for backup readiness consumes throughput and what happens after an operating excursion. Require continuous access to raw meter, BMS, PCS, temperature, alarm and dispatch data in a portable format. A dashboard state-of-health value is a model output; it is not an independent capacity measurement. Trend module voltage spread and thermal exceptions as diagnostic evidence, but use an agreed reference test to decide a contractual shortfall.

Make availability a formula, not a slogan. Define the numerator, denominator, reporting interval, minimum capable power and energy, response time, SOC readiness and the meter or status that determines whether the BESS was available. Allocate planned maintenance, grid outages, owner curtailment, force majeure, communication loss, auxiliary failure, derating, safety shutdown, spare-parts delay and partial rack availability. A system may be online yet unable to deliver the contracted duration; another may be offline because the owner instructed it to preserve emergency reserve. Those conditions should not be hidden inside one uptime percentage. Set notice and restoration times, evidence for each exclusion and a cap on excluded hours. Tie service credits or other remedies to the duty that failed rather than accepting an availability definition that can remain high while the business service is unavailable.

Write one repeatable reference performance test before signing. Establish the safe starting condition, stabilization period, ambient correction if any, charge protocol, rest time, discharge power, termination condition, treatment of auxiliaries, meter accuracy, data sample rate, tolerances, witness rights and restoration to service. Use the same procedure at commissioning and scheduled intervals so results can be compared. Decide whether testing itself consumes contractual throughput, who pays for lost operation and what happens if the system cannot safely complete a full test. Preserve signed raw data and configuration records, not only a vendor PDF. IEC 62933-2-1 and IEC 62933-3-1 provide relevant performance and planning frameworks, but the project parties must still convert them into a site protocol. Philippine requirements and responsible-engineer decisions remain separate.

Price augmentation and remedy before the original cells age. State whether additional modules are mandatory to maintain the guaranteed output or optional owner investment; who supplies them; when the decision is triggered; and who pays for cells, racks, PCS headroom, cooling, transport, duties, tax, installation, testing, lost operation and disposal. Reserve physical space and electrical capacity, and address future compatibility if the original cell or firmware is no longer available. A free replacement cell is not a complete remedy when labor, shipping, site mobilisation or downtime exceed its value. Check the identity and credit strength of the party giving the warranty, claim jurisdiction, security, assignment, parent support, response deadlines and rights if the integrator or OEM changes ownership. Model base, downside and delayed-augmentation cases without assuming the warranty will pay.

S3’s free initial BESS warranty-readiness screen asks for the use case and dispatch profile, offered kW and kWh, one-line diagram, cell/rack/PCS identifiers, thermal design, degradation curve, throughput and temperature assumptions, availability definition, draft warranty, performance-test procedure, metering and data architecture, augmentation plan, remedies, counterparties and decision deadline. We return a bounded gap map distinguishing a verified term, vendor assertion, modelling assumption and issue requiring Philippine legal, tax, insurance, finance or licensed-engineering advice. It is not a warranty opinion, bankability certificate, capacity test or approval. A later paid scope can focus only on the highest-value gap: duty-cycle translation, boundary and formula review, degradation model, data rights, test specification, augmentation economics or technical schedules for procurement.

IEC 62933-3-1:2025 — EES planning and performance assessment

Discuss the engineering scope →
02

What a business should do next

  1. Convert the intended duty cycle into year-by-year energy, power, SOC, temperature, throughput and availability obligations at a named meter boundary.
  2. Require a repeatable reference performance test, raw-data access, tolerances, exclusions, notice periods, cure steps and a remedy that remains valuable after transport, labor and downtime.
  3. Request a free S3 BESS warranty-readiness screen to identify the boundary, curve, test, augmentation or counterparty gap most likely to change the purchase decision.