SCADA Battery Alarm Mapping for BESS Safety

A battery enclosure can move from a minor internal cell fault to a thermal runaway event far faster than an operator can interpret a vague “fault active” notification. Effective SCADA battery alarm mapping gives early-warning signals a clear operational meaning: what has changed, how serious it is, who must respond, and which protective actions must follow.

For BESS operators, EPCs and facility managers, this mapping is not simply an HMI configuration task. It is a critical layer between early detection of hydrogen and electrolyte vapours and a controlled response that protects people, equipment and site continuity.

Why SCADA battery alarm mapping matters

Lithium-ion battery failures often develop through stages. A degrading cell may begin releasing hydrogen, VOCs and electrolyte vapours before visible smoke, flame or a rapid temperature rise occurs. These early indicators provide valuable time, but only if the control system presents them accurately and operators understand what to do next.

A detector connected to SCADA but mapped as a generic common fault may create little practical benefit. Conversely, every minor sensor change mapped as a high-priority shutdown can produce nuisance alarms, unnecessary outages and a loss of operator confidence. The objective is proportionate escalation.

Well-designed mapping separates device health issues from developing battery hazards. It also distinguishes a local indication requiring inspection from an event that requires isolation, emergency response or evacuation under the site’s approved emergency plan.

Start with the battery risk and operating philosophy

Before assigning tags, colours or alarm priorities, define the site’s battery safety philosophy. The design should account for the battery chemistry, enclosure layout, ventilation arrangement, fire strategy, occupancy, operational criticality and the actions available to the control system.

A containerised BESS at a remote solar farm may have different escalation logic to a UPS battery room in a data centre. In the first case, remote verification, site access delays and protection of adjacent assets may drive the design. In the second, continuity requirements and coordination with building management systems may be more significant. Neither approach should be copied blindly from another installation.

The key question is straightforward: what must occur when the system detects evidence of abnormal battery off-gassing? Document the answer before configuring SCADA. This should identify who assesses the event, what can be done remotely, when equipment is isolated, when personnel are excluded from the area, and when emergency services procedures are initiated.

Map conditions, not just devices

An off-gas detector may provide analogue values, relay outputs and communications data through Modbus RTU. Rather than treating each output as an isolated point, map them into recognisable operating conditions.

For example, a normal state confirms healthy communications and values within the expected operating range. An advisory state may identify a gradual change in humidity or a low-level gas reading that warrants trend review. An alarm state signals an abnormal condition requiring prompt investigation. A critical state indicates a level or combination of indicators that activates the site’s defined protective response.

This condition-based approach makes the HMI more useful during an incident. Operators see the developing risk, not a confusing list of register names and individual contact states.

Build an alarm hierarchy operators can use

Alarm priority must reflect consequence and required response time, not merely the type of device generating the signal. A detector communication loss is important, particularly in an unoccupied BESS enclosure, but it is not automatically equivalent to a confirmed high off-gas event.

A practical hierarchy often includes four levels:

• Information or maintenance for calibration reminders, sensor service status, configuration changes or restored communications.

• Advisory for conditions requiring review, such as a persistent low-level reading or an environmental trend outside normal expectations.

• High alarm for an off-gas condition requiring immediate operator assessment and attendance according to site procedures.

• Critical alarm for confirmed or escalating conditions requiring predefined protective actions, escalation and possible emergency response.

The labels can differ between organisations. What matters is that each level has an unambiguous response expectation. If an operator cannot tell the difference between an advisory and a high alarm within seconds, the hierarchy needs revision.

Avoid relying on colour alone. Use clear descriptions, priority banners, audible annunciation where appropriate, timestamps and event acknowledgement. Alarm text should name the asset and location, such as “BESS 02 - Container 4 - Early Off-Gas High”, rather than “AI_104 alarm”.

Include the signals that reveal a developing event

Early-warning detection is strongest when SCADA shows the relevant evidence together. Hydrogen and electrolyte vapours may indicate abnormal battery conditions before conventional smoke detection operates. Temperature and humidity changes can provide useful context, particularly where ventilation performance or local environmental conditions affect interpretation.

The HMI should therefore display current values, alarm thresholds, detector status and trends for each monitored zone. A short trend window can help an operator determine whether a reading is stable, intermittent or rising quickly. Rate of change may be operationally significant even before a final alarm threshold is reached.

Where multiple detectors protect a larger enclosure, map the physical location clearly. Zone-level alarms allow responders to understand whether the event is localised or distributed. This is particularly useful in containerised systems, battery rooms and constrained electrical spaces where safe access must be planned carefully.

Do not omit detector health. Sensor fault, loss of power, communication failure, calibration due status and out-of-range values should be visible as separate conditions. A failed detection pathway should not be hidden behind a common “system healthy” indication.

Define actions without creating unsafe automation

SCADA mapping should support decisive action, but automatic controls require careful engineering. Depending on the approved site design, a high or critical alarm may initiate ventilation, inhibit charging or discharging, isolate selected equipment, notify a control room, activate local warning devices or trigger escalation workflows.

The right action depends on the installation. Immediate total shutdown may be appropriate in some settings but can introduce separate operational or electrical risks in others. Ventilation logic must also align with the enclosure design and fire engineering strategy. It should never be assumed that switching fans on is universally safe or sufficient for a battery incident.

Use a cause-and-effect matrix to document each alarm condition, its delay or persistence requirement, the automatic output if any, the required human response and reset conditions. This matrix should be agreed by the asset owner, battery integrator, controls engineer and safety stakeholders before commissioning.

Critical protective actions should not rely solely on a SCADA workstation or a non-deterministic network path. Hardwired relay outputs can provide an independent interface for selected local functions, while Modbus RTU supports detailed monitoring, trending and annunciation. The final architecture should be designed around failure modes, not convenience.

Test the mapping under realistic conditions

A point-to-point test only proves that a tag changes state. It does not prove that the alarm is understandable, prioritised correctly or connected to the right operating response.

Commissioning should verify the complete chain: detector indication, relay operation where used, Modbus value and status transfer, PLC logic, SCADA display, alarm priority, notification routing, historian records and documented response actions. Test communication loss and power restoration as well as alarm activation. Confirm that alarm suppression, shelving and maintenance bypasses are controlled, visible and removed when work is complete.

Operators should participate in scenario testing. Present a simulated early off-gas event and ask whether they can identify the affected enclosure, understand the severity, access the current trend and follow the required procedure without searching through engineering screens. Their feedback often exposes alarm text and navigation problems that factory testing misses.

Keep alarm performance under review

Battery safety monitoring is not set-and-forget. Review alarm histories after commissioning and after any material change to battery operation, ventilation, enclosure configuration or SCADA software. Repeated advisories may point to a threshold that needs engineering review, a local environmental issue or a developing equipment concern. They should not simply be normalised because they occur often.

NexaGuard’s early off-gas detection approach is designed to provide warning before smoke and fire occur. The value of that warning is realised when the SCADA system turns it into a visible, trusted and rehearsed operational response.

The best mapping gives operators time to make sound decisions under pressure. Treat every alarm point as part of a response pathway, and early warning becomes a practical protection for people, critical assets and continuity of service.