Fire Detection, Suppression & Life-Safety

Fire protection is the discipline where the data center industry's two cultures collide hardest. To the fire engineer, a data hall is a high-value, high-power, life-safety-occupied space governed by codes that predate the AI era. To the cluster owner, it is a machine that must not stop — and most legacy fire responses (dump the room, kill the power, soak the racks) are precisely the events the cluster is engineered to avoid. The job of this chapter is to resolve that collision at design time, because the alternative is resolving it during an insurer's review after the slab is poured, when every option is expensive and some are impossible.

The consequences here are non-linear and partly out of your hands. A mis-chosen cooling fluid does not just cool poorly; it can fail an FM Global approval and strand the entire cooling scheme. A battery chemistry picked for energy density can fail a thermal-runaway test and force a re-siting of the energy-storage room. And the most expensive surprise in the 2026 era is discovering that the property insurer whose approval your lenders made a condition of funding adds binding design conditions alongside the adopted fire code.

Every defensible fire strategy is four layers, and the design error is treating any one of them as the whole answer. Prevent is the layer most operators skip and the cheapest to own: arc-flash-safe power design, qualified-worker programs, clean cabling and firestopping, and — at the extreme — oxygen-reduction that makes ignition thermodynamically hard. Detect is the layer AI density stresses hardest, because residual air heat, rack-fan behavior, containment, and the return path determine where smoke travels. Suppress is the layer with the most contested fork — water vs clean agent vs mist vs none — and the one most entangled with insurability. Contain is the architectural layer that decides what a fire can't do regardless of whether detection or suppression works: compartmentation, smoke control, egress, and firefighter access.

The cascade runs the other way from how budgets are usually allocated. Money flows to suppression hardware because it is visible and biddable; but the layers that actually bound your worst day are prevention (which removes ignition sources) and containment (which caps the loss when the other three fail). A hall with immaculate clean-agent coverage and poor compartmentation is a hall that has bought a fast first response and an uncapped maximum loss. Fund the four layers as a portfolio, weighted to prevention and containment.

Point smoke detectors at the ceiling assume smoke rises and accumulates. In a liquid-cooled AI hall, the selected rack's residual air heat and fan behavior, the containment, and the supply/return path determine whether smoke reaches the ceiling or is entrained into the return. Obtain those inputs and use transport analysis plus witnessed smoke testing to select, locate, and commission the detection system. The guide recommends layered, very-early-warning aspirating (VESDA-class) detection for this airflow boundary: get the earliest possible alarm so a human can investigate and intervene before any suppression event is needed. Chapter 6.1 owns the hall geometry that the sampling network must follow.

The decision inside ASD is where to sample and at what sensitivity, and it is genuinely hard in a high-airflow hall. Sampling at the ceiling alone misses smoke that the airflow has already entrained; the contemporary practice is to sample where the air actually goes — in the hot-aisle / return path and ceiling return plenum, where the room's airflow concentrates the products of combustion before exhaust. Under-floor sampling matters far less in a slab-and-liquid hall than it did in a raised-floor air hall. Sensitivity is the hard part: set it too sensitive and a dusty commissioning period or a normal hot-spot off-gas event nuisance-trips a live cluster; set it too coarse and dilution defeats the entire premise. The resolution is cascaded alarm thresholds (Alert / Action / Fire) tied to airflow-aware sensitivity, validated by real smoke testing during commissioning, not a datasheet number.

Suppression is where the chapter has its sharpest decision, and where the wrong choice is most visible in the loss column. There are four families, and they trade equipment safety, life safety, re-occupancy time, water/collateral damage, and insurability against each other. No option wins on every axis; the right answer is a function of density, fluid choice, the insurer, and whether the room is occupied.

Water (wet-pipe, or — the data-center reflex — pre-action / double-interlock). Sprinklers remain a design candidate under the selected NFPA 75 edition, adopted code and insurer’s conditions; the AHJ must accept the actual IT-room basis. Adding a clean-agent system does not itself remove an applicable sprinkler obligation. A double-interlock pre-action system keeps the pipe dry until both a detection event and a sprinkler-head fusing occur, which is what makes water tolerable over live electronics: it dramatically reduces the inadvertent-discharge risk that makes operators fear water in the first place. The cost is paid twice: collateral damage if it ever does discharge, and delayed water delivery from a more complex, more often impaired system — which is why FM 5-32 ranks wet, non-interlocked and single-interlocked systems ahead of double-interlock, and why fire growth during the delay belongs in the trade beside inadvertent discharge. Then there is the physics that water and energized racks do not coexist gracefully — which is precisely why detection-driven power interlocks matter.

Clean agent (FK-5-1-12 / Novec 1230, HFC-227ea / FM-200, or inert gases IG-55/IG-541). Clean agents flood the room and extinguish open flame without water damage, then leave no residue — ideal for a sealed IT room where re-occupancy speed and zero collateral damage are worth a premium. The catch is that an agent dump protects against an open-flame event in a sealed enclosure; it does nothing for a re-igniting energy source, it requires room integrity (a failed door-fan test means the agent leaks out before it works), and the discharge itself has caused hard-drive damage from acoustic over-pressure. And it does not arrest a lithium-ion thermal runaway. Agent choice now carries a supply and regulatory dimension alongside fire performance. 3M's exit from PFAS manufacturing at the end of 2025 ended Novec 1230 production, but FK-5-1-12 itself is a generic agent that several manufacturers still supply with UL-listed and FM-approved hardware — specify a listed system and a qualified fill, not a brand that has left the market. Europe is where the timing bites: Regulation (EU) 2024/573 has prohibited placing on the market fire-protection equipment that contains or relies on Annex I F-gases, HFC-227ea among them, since 1 January 2025 (Article 11 with Annex IV point 11(c)), except where safety requirements at the site of operation demand it — a first-placement restriction, not a ban on operating or servicing equipment already lawfully placed. ECHA's SEAC opinion on the wider PFAS restriction, which decides whether fire suppression keeps a derogation, is due by the end of 2026. Choose HFC-227ea for a new European installation only on that safety exception, and price refill and retrofit exposure into any agent you select today.

Water mist. Fine-droplet mist suppresses by cooling and local oxygen displacement with one to two orders of magnitude less water than sprinklers, bridging the gap between water's reliability and clean agent's gentleness. Its cooling action suits high-density halls, and mist has approved battery applications — but there is no generic mist-over-sprinkler ranking for lithium. FM's data sheet excludes approval of mist for Li-ion UPS cabinets while permitting other mist applications, so what decides is the configuration, the tested protection objective (cooling an exposure and limiting propagation is not arresting a cell), and the approval that actually covers the installation you are building. The cost is system complexity (high-pressure pumps, fine nozzles, water quality) and a smaller installed base of approvals to lean on.

Oxygen-reduction / hypoxic (continuous prevention, not suppression). The most architecturally radical option lowers the hall's oxygen concentration permanently to ~15–17% (vs 20.9% ambient) by injecting nitrogen-enriched air. EN 16750 frames performance as tested ignition prevention for the named fuels at the design oxygen level; it does not make the room incapable of fire. When those tested fuels do not ignite, the design avoids an agent discharge and its associated collateral damage and re-occupancy delay. A lithium cell’s internal runaway can continue without ambient oxygen, so any rack BBU or facility ESS retains the configuration-specific controls described below. The costs are real and recurring: continuous nitrogen-generation energy (a PUE/opex hit), occupational-health and respiratory-protection requirements for oxygen-deficient entry, sealing requirements, and AHJ unfamiliarity in some jurisdictions. Choose oxygen reduction where the test basis covers the actual fuel package and the avoided discharge justifies the continuous operating cost; it cannot replace battery hazard controls.

The table's rightmost two columns carry the decisions. The lithium-runaway column kills the lazy assumption that a clean-agent hall is also a protected battery room — it is not, and conflating the two is a recurring and dangerous error. The insurability column is the one that quietly overrides everything else, and it deserves its own treatment.

The national fire code (NFPA in North America, EN-aligned national codes in Europe) sets the floor — the minimum to obtain a certificate of occupancy. But the body that actually governs the design of a hyperscale or institutionally-financed AI data center is usually the property insurer, because the lenders behind the project make a specific insurer's approval a condition of funding, and that insurer's standards exceed code. In North America the instrument written into those conditions is typically FM Global's Approval Standards and Data Sheets, which add contract-specific property-protection requirements without replacing adopted law. Elsewhere the roles separate rather than substitute: VdS (Germany) is an insurer-backed approval body, LPCB (UK/Red Book) is a third-party product and system certification scheme whose listings an insurer or AHJ may require, and FM Global is also present. Four actors decide and none of them replaces another: the AHJ enforcing adopted law, the property insurer setting policy conditions, the certification body that lists the specific product or system, and the owner/lender contractual criteria. Chapter 2.6 owns the insurability economics; this chapter owns what it does to the engineering.

The consequence is direct and expensive: the required FM product approval and insurer acceptance can gate the named cooling-fluid system and battery installation. A dielectric or coolant that lacks the right approval, an immersion fluid that fails a flammability or materials-compatibility criterion, a BESS that has not passed the runaway-propagation tests the insurer recognizes — any of these can be vetoed not by an engineer's judgment but by the absence of a certificate. This is the channel by which the two-phase immersion fluids (3M's Novec family) that stalled on PFAS health and liability concerns also became an insurability problem, and why single-phase direct-to-chip became the 2026 default for reasons that are partly fire-and-fluid, not just thermal. The fluid and chemistry decisions made in Chapter 5.4 and Chapter 5.5 are, in effect, co-signed here.

The AI build introduced a fire problem the legacy data center never had at scale: large lithium-ion energy storage, both as rack-level battery backup units (BBUs) and as facility-scale BESS for ride-through and power-transient absorption. The electrical role of that chain is owned by Chapter 4.5; the fire consequence is owned here. A lithium cell in thermal runaway is an internal exothermic reaction that can continue without ambient oxygen, so removing room oxygen does not establish cell-runaway arrest; control heat and propagation separately. Smothering the external flame does not remove the cell’s internal heat. Worse, runaway propagates cell-to-cell and emits a flammable, toxic off-gas (hydrogen, CO, electrolyte vapors) before visible fire, creating an explosion hazard distinct from the fire hazard.

NFPA 855 does not assign one generic battery-room prescription to every installation; the control stack splits three ways. Rack-level BBUs inside an occupied data hall. Keep them within the applicable stored-energy thresholds and the listed rack or UPS configuration, with the monitoring and isolation required by that listing and its tested installation. Chapter 7.13's NVL72 side pocket cannot become a dedicated deflagration-vented room; if the quantity or listing basis is exceeded, move the energy storage out of the occupied hall. Facility ESS in dedicated indoor rooms. Use rated compartmentation and separation, module thermal and off-gas detection, ventilation, explosion control where the gas-hazard analysis requires it, water-based fire control and cooling, and fire-service access. Outdoor listed ESS enclosures. Use the listed cabinet or container with site and unit separation, enclosure gas management and explosion control as tested, exposure protection and water supply, and fire-service access; do not import an indoor-room detail into an outdoor enclosure.

The chemistry choice remains a fire decision: LFP (lithium iron phosphate) runs cooler and is more abuse-tolerant than NMC, which is one reason it dominates facility BESS. UL published the 9540A Test Method’s sixth edition in March 2026. The sixth edition adds intentional vent-gas ignition and installation-level large-scale testing. UL has announced a January 2027 transition; verify which report edition the installation requires. The installation-level result supplies configuration-specific fire, gas, heat-release, and propagation evidence that the designer and AHJ use to determine or justify spacing, enclosure/venting, and suppression under the adopted code and listed-system conditions; evidence for one of the three configurations does not establish the basis for the other two.

Containment is the layer that decides the size of your worst day, and it is set architecturally — in Chapter 6.1's layout and Chapter 6.3's envelope — long before any suppression hardware is specified. Compartmentation subdivides the hall into rated fire compartments so that a fire (or an agent dump) is bounded to one zone rather than the whole facility; the larger and denser the hall, the more this matters, because the value-at-risk per compartment is enormous. The tension with cluster design is real: a tightly-coupled training cluster wants one large contiguous hall for fabric reasons, and compartmentation cuts against that. Resolving it is a genuine cross-discipline fork between fire containment and network topology.

Smoke control and egress are life-safety obligations that the density ramp complicates. A hall with hot-aisle containment, high airflow, and an oxygen-reduced or clean-agent atmosphere is a difficult environment to evacuate and a difficult one to ventilate post-event; smoke-control design must account for the same airflow that challenges detection. Egress paths must remain valid as racks get heavier and aisles get plumbed — a move route or escape path that worked for 5 kW racks can be obstructed by the manifolds and CDUs of a liquid retrofit (the rigging and floor-loading interactions are owned by Chapter 6.7).

The firefighter-access problem is the under-appreciated one. Responders entering a dense, energized, liquid-cooled hall face hazards a legacy hall never presented: hundreds of kilowatts per rack, lithium energy storage that re-ignites, dielectric and glycol coolants, and DC-shock risk from 800 VDC distribution. Manual firefighting may be neither safe nor effective, which shifts the entire strategy toward early detection, automatic suppression, and orderly power isolation — and toward giving responders the information (zone status, power state, battery-room status) to make a stay-out decision safely. This is where detection, suppression, power, and the BMS must speak one language.

Carry the passive-fire design as an assembly schedule: required rating and supporting construction, doors and hardware, penetrations, movement joints and any ducts or dampers. Match each installation to its tested/listed system, including permitted substrates, annular space, insulation and movement. Mark concealed inspections before closure and maintain a penetration register for later cable and pipe changes.

Coordinate fire-service approach, appliance setup, hydrants, fire connections, control-room information and safe isolation with the authority and responders. The heavy-haul corridor in 6.3 is not automatically the approved fire-apparatus route. Submit its usable width, loading, turns, gradients, overhead clearance and all-phase obstructions against the adopted access criteria.

The interlock matrix is where fire-safety stops being a set of independent systems and becomes a control problem — and it is the layer most likely to either save the cluster or take it down unnecessarily. The protective actions include detection → power isolation and detection → the approved suppression sequence; required water protection must not wait indefinitely for the IT breaker to confirm open. In an AI hall every one of those links is fraught.

Detection → power. The approved sequence coordinates power isolation with water or agent protection, while required sprinkler/preaction functions remain independent of an IT-breaker acknowledgment; a nuisance trip that de-energizes a live training cluster is a multi-hour, multi-million-dollar goodput loss (the goodput-vs-availability framing lives in Chapter 12.2). The design answer is cascaded, confirmed alarms (Alert/Action/Fire) and zoned isolation that drops the smallest possible domain, not the hall. Detection → cooling. Liquid cooling complicates the picture: shutting pumps in a thermal event can be exactly wrong (you may want to keep cooling, or specifically cool a battery), and a coolant leak is itself a detected event with its own interlock (leak detection → CDU isolation), distinct from fire. The cooling interlocks coordinate with Chapter 5.6's CDU/secondary-loop logic. Everything → BMS. The building management system is the integration point that must present a coherent state — fire zone, power state, cooling state, battery-room state — to the human responder while required fire and life-safety logic runs on its approved controls independently of ordinary BMS availability. A fire strategy whose interlocks are not modeled, tested, and tuned against the live cluster's failure modes is a strategy that will eventually trip the cluster for the wrong reason or fail to trip it for the right one.

Trace what the report actually covers. First, identify the cabinet, cells, modules, quantities, ventilation, spacing and protection being purchased. Second, compare those fields with the supplied report and listing. A cell-level test does not establish cabinet-to-cabinet propagation or the installation’s gas hazard, and a UL 9540A report is distinct from a UL 9540 system listing. Third, compare the proposed location with the adopted installation requirements and FM contract conditions. The submitted cell report closes neither the cabinet configuration nor the room controls: HOLD the in-hall substitution.

Keep the independent battery-room design while procurement obtains the missing evidence; accept no cabinet delivery that silently spends occupied-hall space, egress width or separation. This preserves the hall’s layout at the cost of retaining the dedicated room and its detection, ventilation and applicable fire/explosion controls. The flip is evidentiary: the in-hall option becomes eligible only when the same supplied configuration meets every applicable listing, quantity, separation, protection and authority condition. An extra report for a different cell or enclosure does not cross that boundary.

The fire-panel cause-and-effect test then challenges the actual boundary. Inject the approved alarm condition in an isolated test scope, with the ordinary BMS link unavailable and IT-breaker feedback withheld. Required sprinkler/preaction functions must proceed through their approved fire controls; failed breaker feedback produces a fault and escalation, not an indefinite veto on required water protection. Trace the isolation command to every AC feed and UPS output in the affected zone, keeping required fire and life-safety supplies available. Cooling follows its approved hazard-specific sequence; a leak valve closure and an ESS fire-cooling demand are different actions. The cause-and-effect matrix fails if either protective action depends on a BMS acknowledgment.

UL Solutions distinguishes test evidence, system certification and the sixth-edition transition. FM 5-32 addresses configuration-specific protection and power isolation. This chapter owns the fire decision; Chapter 13.6 witnesses integrated acceptance and Chapter 6.9 authorizes de-energized maintenance.

Select protection for the actual room, battery and fluid, then prove its independent alarm, water and isolation actions. A missing listing or a breaker-feedback veto holds release; buying the equipment first makes that unresolved boundary a costly room redesign.