
A BESS emergency plan often fails at the information boundary. The equipment supplier has product data, the EPC has site drawings, the owner has contacts, the fire engineer has the response strategy, and local responders have their own procedures. If these records are not combined and maintained, the team arriving at an alarm may not know the affected enclosure, remaining electrical hazards, safe approach, isolation limits or who can provide technical support.
The emergency response information pack is the controlled subset of project information needed before, during and immediately after an incident. It is not a replacement for local emergency plans, trained responders or authority decisions. It gives those parties verified, configuration-specific facts in a form that remains usable when normal systems or personnel are unavailable.
EPA’s current BESS installation and incident-response resource identifies challenges including fire control, emissions, re-ignition and damaged-battery handling. Buyers should translate these broad concerns into site-specific drawings, contacts, actions and evidence before commercial operation.
Define the Audience and the Decisions They Must Make
Prepare different views for control-room operators, site security, maintenance, owner management, external fire service, medical responders, environmental specialists, equipment suppliers and recovery contractors. They share core facts but need different depth and authority. A firefighter should not need a BMS service manual to identify remaining DC hazards; a service engineer needs more detail than an evacuation card provides.
List the decisions each role may make: sound an alarm, evacuate, isolate remotely, restrict access, call external responders, provide equipment status, authorize specialist entry, establish environmental monitoring, quarantine damaged equipment or approve return to service. State decisions that remain exclusively with public authorities or qualified electrical personnel.
The U.S. Fire Administration’s lithium-ion battery community-education resources include emergency-response awareness for energy storage systems. Projects need their own legal and responder review, but the underlying lesson is useful: emergency information must support named actions and people, not sit as an unassigned appendix.
| Audience | Immediate information | Nicht annehmen |
|---|---|---|
| Control-room operator | Alarm source, equipment state, remote actions and escalation | Dashboard status proves physical isolation |
| Site security | Exclusion area, access route, muster and responder entry | Normal gate route remains safe |
| Fire service | Layout, hazards, isolation limits, water and contacts | Emergency stop removes all battery energy |
| Electrical maintenance | Sources, boundaries, verification points and work authority | Visible damage is the only electrical hazard |
| Environmental team | Potential materials, runoff paths, monitoring and waste contacts | Fire extinguishment closes environmental duties |
| OEM specialist | Asset identity, logs, configuration and safe remote access | Remote reset is an acceptable first response |
| Recovery contractor | Condition classification, lifting, temporary storage and transport limits | Damaged batteries follow normal logistics |
Provide a One-Page Site and Energy Map
The first drawing should show the site boundary, BESS enclosures, battery blocks, PCS, transformers, switchgear, fire equipment, emergency stops, access gates, hydrants or approved water sources, drainage, nearby buildings, overhead or underground hazards, muster points and responder staging areas. Use equipment tags that match labels, SCADA and the detailed single line.
Add an energy-state diagram. Show AC, DC and auxiliary sources, isolation points, automatic actions, stored energy that remains after shutdown, and feedback available to operators. Note that the final determination of a safe electrical condition follows qualified procedures; a map is not permission to operate a device.
Prepare a controlled offline copy and a protected remote copy accessible to authorized incident roles. A QR code on a gate is not sufficient if internet service, credentials or the target page fail. Test access from the alternate command location and preserve current printed copies where the approved plan requires them.
State What Every Emergency Control Actually Does
For each emergency stop, breaker, disconnect, fire-panel control and remote command, state the equipment affected, required prerequisites, achieved state, feedback and remaining hazards. Avoid labels such as “master shutdown” unless every relevant source and auxiliary function is included. Identify controls that responders should not operate without an OEM or site electrical authority.
Describe automatic fire and gas actions in plain language and reference the controlled cause-and-effect. Include ventilation, suppression, contactors, PCS, switchgear, alarms and failed-action escalation. The code and testing distinctions in the UL 9540, UL 9540A und NFPA 855 Leitfaden help buyers separate product, test and installation duties.
State how controls behave when communications or auxiliary power is lost. A plan that depends on a remote screen must identify the local alternative and the person authorized to use it. The BESS remote-access policy should include emergency roles without creating permanent uncontrolled accounts.

Describe Observable Conditions without Prescribing Universal Tactics
List signs that require escalation: abnormal temperature, off-gas or smoke indication, hissing, popping, odor, visible vapor, flame, deformation, pressure-panel activation, coolant release, damaged enclosure, insulation alarm, repeated electrical trip or loss of monitoring. Connect each sign to the site alarm stage and contact route.
Do not turn the information pack into unqualified firefighting instruction. Strategy and tactics belong to the authority and trained responders using current conditions and approved plans. Provide product test data, hazards, isolation facts, expected automatic systems, water or agent compatibility information where supported, and the manufacturer’s emergency contact.
A DOE-filed project example contains BESS pre-incident and emergency response planning. It remains a project-specific reference, not a template. Use such examples to see the level of coordination that may be needed, then obtain acceptance from the actual local responders and authorities.
Make Contacts Functional, Not Decorative
List roles, primary and alternate numbers, hours, language capability and the information each contact needs. Include site command, electrical authority, fire service, emergency medical, utility, OEM, system integrator, environmental authority or consultant, insurer, security, recovery contractor and damaged-battery logistics as applicable.
Test the contact chain outside normal working hours. A general sales mailbox or departed commissioning engineer is not an emergency path. Call or exercise each external number under an agreed test, confirm escalation and record response. Review contacts after personnel or service-contract changes.
Define the incident data package for remote specialists: asset and firmware identity, alarm sequence, temperatures, state of charge, contactor and PCS state, insulation status, photos from safe locations and actions already taken. Preserve the original records through the BESS alarm-triage workflow.
Plan for Damaged Equipment after the Immediate Event
Emergency stabilization is not the end of the event. Batteries can require continued monitoring, restricted access, weather protection, temporary power, environmental controls, specialist assessment and a controlled destination. Define who assumes custody and who can declare equipment safe to move.
Do not transport damaged or suspect batteries under ordinary shipping assumptions. PHMSA’s 2024 interpretation on damaged and defective lithium batteries explains specific U.S. transport treatment for batteries with potential dangerous heat, fire or short-circuit behavior. Other jurisdictions have their own rules; obtain qualified classification, packaging, carrier and receiving-facility advice after condition is known.
Prepare a temporary-storage concept with separation, monitoring, access, drainage, fire precautions and security. Record serial or batch identity, condition, exposure, isolation, custody and photographs. Keep undamaged equipment separate from suspect equipment where the approved plan requires it.
| Incident phase | Erforderliche Informationen | Responsible decision |
|---|---|---|
| Alarm recognition | Source, zone, confidence and automatic actions | Escalate, evacuate or investigate under procedure |
| Initial isolation | Controls, feedback and remaining energy | Establish the permitted operating/access state |
| Responder arrival | Site map, conditions, occupants and hazards | Transfer command information |
| Active response | Product data, tests, monitoring and utilities | Authority selects tactics |
| Stabilization | Temperature, gas, electrical and structural condition | Define exclusion and monitoring |
| Recovery assessment | Identity, damage, logs and exposure | Repair, quarantine, removal or replacement route |
| Transport/storage | Classification, packaging, carrier and destination | Qualified parties approve movement |
| Rückkehr in den Betrieb | Cause, repair, tests, settings and authority approval | Release unaffected or corrected equipment |
Protect Evidence and Maintain a Single Incident Timeline
Assign a record owner who gathers control-system events, BMS and PCS logs, fire-panel history, access logs, video, weather, communications, witness notes, response actions and configuration. Preserve native data and document time zones and clock quality. Do not let separate contractors build incompatible timelines without a controlled source set.
Limit access to sensitive or investigative information while ensuring authorized safety, regulatory, insurer and technical teams can use it. Record every remote session and settings change during response. If equipment must be moved before investigation is complete, preserve identity and custody.
EPA’s 2025 lithium-ion battery wildfire fact sheet warns against touching or restarting fire-damaged energy storage equipment in that specific emergency context. The transferable point is to treat damaged BESS as potentially active until qualified assessment supports the next step.
Exercise the Pack before Energization
Agree how command transfers when public responders arrive. The site team remains the best source of equipment and operating information, while the incident commander directs emergency tactics under local arrangements. The pack should identify the owner representative who briefs responders, records plant actions and maintains contact with the OEM without creating competing command channels.
Practice a shift change during an extended event. The incoming team should receive current conditions, confirmed isolations, unavailable systems, exclusion boundaries, monitoring results, contacts engaged and decisions pending. Use a written handover form so fatigue and staff rotation do not erase the reasoning behind an earlier action.
Include neighboring facilities or occupants where the approved plan requires notification, shelter or access control. Define who issues public information and how technical facts are reviewed. Operators and suppliers should not publish unverified causes while response and evidence collection are still underway.
Run a tabletop with operators, security, owner management, OEM support and local responders where available. Use a scenario that includes a failed communication path, an unavailable contact and conflicting information. Ask participants to find the affected unit, remaining hazards, safe route, current contacts and approved actions using only the issued pack.
Follow with safe functional drills: alarm notification, evacuation, worker accounting, gate access, alternative command point, data export and contact escalation. Product functions should already be verified through the BESS FAT and SAT process. Do not simulate hazardous battery behavior outside an approved test plan.
Record time to locate information, missing pages, ambiguous tags, failed access, obsolete contacts and decisions lacking authority. Correct the pack and repeat critical steps. A drill is a document acceptance test, not a performance for observers.

Control Revisions throughout the Project Life
Use Incident Tiers without Delaying Escalation
A tier system can organize response, but it should never require an operator to prove the final severity before calling for help. Define tiers around observable conditions and available authority. An equipment advisory may remain within routine service; confirmed off-gas, smoke, fire, explosion, significant electrical damage or loss of critical monitoring may trigger higher protective actions under the approved plan.
For each tier, list minimum notifications, exclusion, operating state, evidence capture, command structure and escalation trigger. State that uncertainty can justify escalation. A missing sensor or failed communication can increase risk because the team knows less, even if no flame is visible.
Do not let commercial labels control public emergency decisions. Terms such as minor, warranty event or contained event may have contract meanings but should not replace conditions communicated to authorities. Report what is observed, what systems acted, what remains energized and what information is unavailable.
Include downgrade and closeout criteria. An alarm clearing or temperature falling does not by itself end monitoring, access restrictions or re-ignition concern. The responsible authority should record the evidence, observation period and party accepting transition to recovery.
Keep the Pack Usable during Nights, Outages and Network Failure
Test the response arrangement when normal office staff are unavailable. The night operator or security guard should reach the current escalation list, site map and quick-reference card without an engineer’s laptop. Alternate contacts need authority and access to the same controlled information.
Provide copies at approved locations outside the immediate hazard zone. If the main control room, gate or network is inaccessible, responders need an alternative command point. Identify how printed copies are updated and how electronic copies are authenticated after offline use.
Prepare for partial telemetry. The pack should explain local indicators and safe observation points, while forbidding unqualified approach or enclosure opening. State what cannot be confirmed remotely and which conservative action applies until qualified personnel restore visibility.
Include communications alternatives appropriate to the site: landline, radio, mobile network, satellite or runner procedures as approved. Protect emergency channels from dependence on the same switch, power supply or building affected by the event. Test them during drills rather than listing equipment that no one has used.
Record clock time and communication method for every critical instruction. When systems recover, merge handwritten, radio and electronic records into the controlled incident timeline without overwriting original notes.
Update after augmentation, equipment replacement, firmware changes affecting alarms, revised fire controls, site-layout changes, new neighboring hazards, contact changes and lessons from drills or incidents. State the pack owner, review triggers, distribution list and method for withdrawing obsolete copies.
The DOE Energy Storage Safety Strategic Plan emphasizes safety through all lifecycle phases. Treat emergency information as an operating asset with configuration control, not as a permitting file frozen at construction.
Use an RFQ Deliverable Index
| Pack section | Minimum content | Verifikation |
|---|---|---|
| Quick-reference card | Alarm, evacuation, contacts and prohibited actions | Operator scenario |
| Site and energy maps | Zones, access, utilities, controls and remaining hazards | Field walkdown |
| Product hazard summary | Battery, coolant, gases, electrical and test evidence | OEM/fire-engineer review |
| Control descriptions | Each emergency device, achieved state and feedback | Functional SAT |
| Contact and escalation list | Roles, alternates, hours and required incident data | Call-chain exercise |
| Responder information | Approved site facts, drawings and support path | Local consultation |
| Recovery and logistics | Monitoring, quarantine, assessment and transport route | Tabletop exercise |
| Evidence and custody | Logs, timeline, configuration and access control | Sample export |
| Revision control | Owner, triggers, distribution and obsolete-copy removal | Annual/change review |
Connect the pack to the kommerzielle BESS-Beschaffungscheckliste so bidders price drawings, tests, training, responder coordination and lifecycle updates. State document formats and delivery stages before award.
The Readiness Decision
Do not declare emergency readiness because an incident plan exists. Declare it when the pack matches the installed plant, authorized users can obtain it during system and network failures, contacts work, responders have been consulted, drills expose no critical information gap and revision ownership has transferred to operations.
The useful pack answers four urgent questions with verified evidence: what happened, where it happened, what energy and hazards remain, and who is authorized to decide the next action.