Summary: An emergency response plan (ERP) for a commercial BESS is not a supplier brochure — it is a site-specific operating document that fire services, insurers, and facility staff will act on. The supplier provides the battery-specific technical input; the EPC or facility owner writes the site procedures; the local fire authority approves the final version. Buyers must verify the plan exists, covers the installed model, and names responsible people before commissioning — because most insurance claims and permit renewals fail on a missing or generic ERP.
Who actually writes each part
Three parties share responsibility, and buyers often misunderstand the split:
The BESS supplier provides the technical foundation:
- Battery chemistry and thermal runaway behavior data
- Gas release and venting characteristics
- Manufacturer's fire response recommendations
- Defect handling and isolation procedures
- Cut-off and de-energization instructions
The EPC / facility owner writes the site-specific plan:
- Site layout and access routes
- Evacuation procedures for staff
- Local fire service notification sequence
- Incident command roles and contact list
- Interaction with building systems (HVAC, gas detection, alarms)
The local fire authority reviews and approves:
- Whether the plan meets NFPA 855 (US) or local codes (EU markets use national fire codes plus IEC 62933 references)
- Required fire separation distances
- Whether the site's suppression system matches the battery's tested behavior
If a supplier claims "we provide the complete ERP with the system," that is only the technical section. A plan with no site evacuation procedures, no named roles, and no fire service sign-off is not an ERP — it is a data sheet.
What the plan must contain
A compliant ERP for a commercial BESS covers at least these sections:
| Section | What it must state |
|---|---|
| System description | Model, capacity, location, cell chemistry |
| Hazard identification | Thermal runaway, gas emission, electrical shock |
| Detection | BMS alarms, gas sensors, smoke detectors, temperature monitoring |
| Response steps | Who confirms, who calls, who evacuates |
| Suppression | Fire service access, water application guidance, stand-off distance |
| De-energization | How to isolate DC and AC, who is authorized |
| Communications | Fire service number, supplier 24h line, facility manager contact |
| Training | Who is trained, how often drills run |
Check that each section has a named owner, not just a generic statement.
What buyers must verify before purchase
Ask for these in the RFQ and verify before PO:
1. The model-specific data sheet, not a generic one. The supplier's technical input must match the exact model you are buying. A plan written for a different cabinet size or chemistry is worthless — the gas venting rate and fire behavior differ.
2. The 24-hour supplier emergency line. Who answers when the fire service calls at 3 AM? A real phone number with a named escalation path, not an email address.
3. Testing evidence behind the response guidance. The plan should cite the battery's fire test results (IEC 62619, UL 9540A or equivalent). If the suppression guidance says "flood with water," the test data should show that was validated — many LFP cabinets have specific water application rates.
4. Training material for facility staff. Does the supplier provide operator training slides and a drill script? Staff who have never practiced a thermal runaway response will not execute a written plan correctly.
5. Integration with the site's existing fire system. Will the battery alarms feed into the building's fire alarm panel? A standalone BESS alarm that nobody monitors is not a detection system.
The three verification steps after delivery
Step 1 — Read the plan against the installed model. Walk the site, open the cabinet door, and check the serial number and model match the plan's system description. Mismatch = plan invalid.
Step 2 — Test the escalation path. Call the supplier's 24-hour line during commissioning. Confirm the person who answers can pull up your site's system and knows the model. A phone number that goes to voicemail fails this test.
Step 3 — Run a tabletop drill. Simulate a battery alarm with the facility team: who receives the alert, who calls the fire service, who evacuates, who contacts the supplier. Time the sequence. If it takes longer than 10 minutes to escalate, the plan needs rework.
Common failures seen at site audits
- The ERP is a PDF from the manufacturer with the site name typed in. No evacuation routes, no local contacts, no fire service input.
- The plan names an employee who left the company. Contact lists are never updated.
- The suppression section says "refer to supplier manual." That is not a plan — the fire service needs the procedure at the site.
- The plan covers the wrong model. Site upgraded from a 100 kW cabinet to a 1 MW container, but the ERP still describes the old unit.
- No training record. The plan exists, but nobody has been drilled on it.
Any of these is a valid reason to delay commissioning until the plan is corrected.
What the buyer should include in the contract
Put ERP obligations in the supply agreement, not in an email:
- Supplier delivers the technical ERP section within 14 days of PO
- Supplier provides 24-hour emergency support with named escalation
- Supplier supplies operator training materials in the site's language
- Buyer (or EPC) completes site-specific sections before commissioning
- Fire authority review scheduled before first energization
Without these clauses, the ERP is whatever the supplier happens to send — usually late and generic.
Bottom line
The ERP is a deliverable, not a formality. Verify it covers the installed model, has named owners for every section, includes a working 24-hour supplier line, and has been drilled before the system goes live. A buyer who checks these three things at PO stage avoids the most common cause of insurance claim denials and permit delays.
Ruibit provides the technical ERP section for every Dawnice commercial cabinet we ship — model-specific gas and fire response data, 24-hour escalation, and operator training material — and we walk EPC partners through the site-specific sections before commissioning. Ask for the ERP outline in your RFQ; we send it with the quote.
FAQs
Q: Is an emergency response plan legally required for commercial BESS? In most jurisdictions, yes. US projects reference NFPA 855; EU projects must meet national fire codes and insurer requirements. A site without an approved ERP typically cannot obtain insurance or final commissioning approval.
Q: Does the supplier or the site owner write the ERP? Both. The supplier provides the battery-specific technical data; the EPC or facility owner writes site procedures; the fire authority approves the final document.
Q: What happens if the ERP is missing at commissioning? The authority having jurisdiction can refuse energization, and insurers may deny coverage. Fixing it after commissioning is more expensive than verifying it before.
Q: How often should the ERP be reviewed? Annually, plus after any equipment change (new battery model, layout change) or after an incident. Contact lists should be reviewed quarterly.
Q: Can I use the supplier's generic ERP template for my site? Only as the technical base. You must add site evacuation routes, local emergency contacts, fire service coordination, and training records. A generic template alone does not satisfy the permit or insurer requirements.
