Fire Alarm Releasing Device
Turning Detection into Suppression
When a detection circuit decides a fire is real, a listed releasing device drives the solenoid, valve, or actuator that delivers suppression. Pre-action sprinklers, clean agent, CO₂, and kitchen hood systems all rely on the same class of FA output. Here is how cross-zoning, abort sequencing, and UL 864 UOJZ listings fit together.
What Releasing Means
In fire alarm language, releasing is the act of driving a solenoid, valve, or actuator that delivers a suppression agent — water, clean agent, CO2, wet chemical, dry chemical, or foam. NFPA 72 §23.8 governs the releasing service class of fire alarm circuits; NFPA 2001, 12, 13, 14, 17, and 17A govern the specific suppression systems that consume these outputs.
A releasing output is not a regular notification appliance circuit. It sources DC current into a solenoid coil (typically 24 VDC at 0.5–2 A peak, depending on the valve) for a defined duration, then either latches or drops out according to the suppression sequence. The panel must verify the solenoid coil is continuous before the alarm (pre-discharge supervision) and must monitor the discharge event (post-discharge confirmation). This is why releasing service requires a specifically listed panel category (UL 864 UOJZ) rather than a generic FACP relay output.
Systems That Use Releasing Devices
Pre-Action Sprinklers
Detection opens the pre-action valve to fill the pipe; sprinklers still operate individually by fusing. Common in data centers and archives.
Deluge
Detection opens the deluge valve; all open sprinklers flow simultaneously. Aircraft hangars, transformer bays, flammable liquid storage.
Clean Agent
FM-200, Novec 1230, Inergen, FK-5-1-12. Detection triggers cylinder valves; pre-discharge alarm gives occupants ~30 sec to exit.
CO₂ Flood
High hazard, total flooding. Pre-discharge alarm is mandatory, evacuation before flood, lockout during occupied hours.
Kitchen Hood
Electric fusible link option: FA releases wet chemical cylinder. NFPA 17A + UL 300.
Foam
AFFF or AR-AFFF systems in high-hazard chemical or flammable-liquid areas. FA releases foam-water deluge.
Cross-Zoning — Why It Exists
Suppression discharge is destructive. A pre-action release wets down a data center; a clean-agent release costs $30–60k per refill; a CO2 release in an occupied space can kill. To reduce the risk of a single stray detector triggering an expensive or dangerous discharge, cross-zoning is standard: the releasing circuit does not fire until two independent detection zones are both in alarm.
Three cross-zone configurations are common:
- Cross-zone detection. Two separate detection zones must both alarm; either alone produces only an alarm signal, not a release.
- Two-out-of-two (2oo2). Two detectors within the same zone must both alarm. Used where a separate zoning architecture is impractical.
- Counting zone. A single zone with ≥2 detectors on it must see two alarms before release (panel counts detector addresses on the SLC).
Cross-zoning is not required by NFPA for every releasing application, but it is universally required by data-center operators, clean-agent manufacturers, and reputable AHJs.
Pre-Discharge Sequence
For clean agent, CO2, and some deluge systems, a pre-discharge alarm gives occupants time to exit before the suppression fires. The standard sequence:
- First alarm (detector 1). Pre-alarm horns. No countdown yet. Occupants alerted to a developing condition.
- Second alarm (detector 2). Pre-discharge sequence begins. Pre-discharge alarm tone (different from pre-alarm), countdown timer starts — typically 30 seconds but up to 60 seconds per design.
- Discharge. At countdown completion, releasing solenoid energizes. Suppression agent flows.
- Post-discharge. Continuous alarm; lockout on mechanical systems (HVAC shutdown, door release, sometimes elevator recall). Post-discharge alarm continues until manually reset.
A manual abort switch (see FAQ) can hold the countdown during steps 2. A manual release station can force discharge immediately, bypassing cross-zoning. Both are required on clean-agent and CO2 systems per NFPA 2001 and 12.
ITM & Re-Discharge Testing
- Annual functional test. Simulate cross-zone alarm, verify pre-discharge sequence, abort function, manual release, countdown timing, HVAC shutdown, solenoid supervision. Solenoid is disarmed for functional testing — never actually discharge agent on annual.
- 5-year or 10-year full discharge test. Clean-agent rooms and CO2 systems require a periodic room-integrity test (door-fan test) to verify agent holds at the design concentration for the required hold time. NFPA 2001 §8.2 requires every 12 months.
- Refill after discharge. Any actual release (test or real) requires the suppression system to be returned to service within 30 days.
- Solenoid continuity supervision. The panel must continuously verify the solenoid coil and wiring are intact. Disconnected coil must register as trouble.
Frequently Asked Questions
What does a releasing device actually release?
What is cross-zoning?
Is a releasing panel different from a regular FACP?
What is the abort switch for?
References
1. NFPA 72 (2022), §23.8 — Releasing service.
2. NFPA 2001 (2022) — Clean Agent Fire Extinguishing Systems.
3. NFPA 12 (2022) — Carbon Dioxide Extinguishing Systems.
4. NFPA 13 (2022), §7.3 — Pre-action systems, §7.4 — Deluge systems.
5. UL 864 (10th Edition) — Listing category UOJZ for releasing-service control panels.
Was this article helpful?
Rate this article to help us improve
Discussion (2)
People forget that the releasing circuit supervision is not the same as a normal notification appliance supervision. The code requires the solenoid drive current to be monitored — you cannot just put an EOL resistor and call it a day. If the solenoid coil opens, the panel must generate a trouble before the alarm, not after.
We had a FM-200 room where the abort button was installed six feet from the door. During a real alarm, the first person out the door hit the abort by reflex — classic muscle-memory. Moved the abort to the side wall with a clear flip-up cover and the problem stopped. Think about where the abort goes during design, not after.