Fire Protection Water Storage Tank For A Data Centre: Sizing, Compliance And Integration

Fire Protection Water Storage Tank For A Data Centre: Sizing, Compliance And Integration

A data centre fire reserve is sized from the NFPA 13 demand: the design density and area of the most demanding space times the required duration, plus any hose stream allowance, built on the tank's usable volume rather than its nominal volume. The site Tier rating drives redundancy and monitoring around the supply, not a larger tank, and the reserve is integrated with the NFPA 20 pump set and protected within the site water balance.

Introduction

A data centre fire reserve is sized by the same code logic as any fire water tank, but the layout, the hazard density and the stakeholder expectations change the numbers and the documentation. You size it from the NFPA 13 hazard and density for the spaces served, the duration the system and the insurer require, and the redundancy the site classification implies; then you integrate it with the fire pump set and reconcile it against the site water balance so it neither starves other uses nor gets starved by them.

This guide works through that sequence: what is different about a data centre reserve, how the demand and density are built up from the actual layout, how duration and site tier interact, how the tank meets the pump set, and what the authority and the insurer expect at compliance and handover. The through-line is traceability from hazard to tank to pump, so every volume in the specification can be defended.

What makes a data centre fire reserve different

A data centre concentrates high-value, high-availability load in a building whose fire protection is reviewed by both the authority having jurisdiction and the insurer, often to a stricter expectation than the code minimum. The reserve is usually a single large volume serving sprinklers across multiple halls, so the demand is driven by the largest simultaneous area and its density rather than by a small, isolated hazard.

The owner also expects the reserve to be monitored and the supply to be dependable, because an outage affects a large, continuous operation. The engineering difference is therefore less in the tank itself than in the demand basis, the integration with the pump set, and the documentation the insurer reviews. The tank construction can be a standard bolted or welded fire water tank; what changes is everything around it.

The reserve is also a long-life asset reviewed years after the project team has left, so the documentation has to survive a change of ownership and an insurer's renewal audit, not only the initial permit. That durability is part of what makes the data centre case different from a one-off industrial tank, where the same people often hold the drawing and the operating record.

Demand and density for the data centre layout

The demand basis starts with NFPA 13: the hazard classification of each space, the design density (water per unit area) and the design area over which that density acts. You build the data centre demand by taking the area and density of the most demanding space, typically the white space or the battery and electrical rooms, and adding any hose stream allowance the standard requires.

The tank volume then follows from that demand multiplied by the required duration. The point a reviewer checks is that the density and area are taken from the actual layout and its hazards, not from a generic figure, because the white space, the support rooms and the battery rooms carry different densities. A reserve sized from an assumed uniform density will be wrong for the space that actually drives the system.

Duration and the Tier requirement

The duration is set by NFPA 13, the water-supply duration for the system, together with any additional duration the insurer or owner requires. The classification that rates data centre infrastructure from Tier I to Tier IV speaks to infrastructure redundancy and availability, not to a mandated fire water volume; what rises at the higher tiers is the expectation of redundant pumps, diverse power and monitored makeup, not a larger tank.

So you size the volume from the NFPA 13 duration plus the insurer's requirement, and you address the site tier through redundancy and monitoring of the supply rather than by inflating the reserve. A larger tank does not by itself meet a Tier IV availability expectation; a second pump and a monitored, diverse supply path do, and those are documented separately from the volume.

Integration with the fire pump set

The tank feeds the fire pump set governed by NFPA 20. The connection is a gravity or suction tank arranged so the pump takes a full, vortex-free stream: an anti-vortex device or a downturned suction, with the outlet set above the tank floor and the suction piping sized and supported so it does not trap air or restrict flow.

The tank's effective, or usable, volume, the volume between the normal operating level and the low-level alarm that protects the pump from running dry, is the number the pump set actually draws on, and it is smaller than the nominal volume. You reconcile the tank outlet, the pump suction and the level control so the available drawdown matches the duration calculation, or the pump will reach the low-level alarm before the required duration is met.

The low-level alarm setpoint is a design value, not a field adjustment. It is set from the drawdown curve of the chosen tank so the pump trips before air reaches the suction, and it is verified during the acceptance test rather than assumed from the nameplate. A drawdown that is available on paper but not protected by an alarm remains a risk the pump set can walk into during a fire.

The site water balance

A data centre site often carries other water uses, cooling makeup, humidification and reject handling, so the fire reserve has to be defined against the site water balance. The fire volume is a dedicated, non-potable reserve that must not be drawn down by process or cooling demand, and the makeup source that refills it must be sized to restore the required volume within the time the design basis allows without competing with those other uses.

You state the fire volume as a separate, protected quantity in the balance, with its own makeup path and backflow protection, so an operator cannot inadvertently deplete the reserve to serve cooling. The reconciliation is a single line in the site balance that an operator and an auditor can both read, rather than a footnote buried in the mechanical spec.

Cooling systems draw the most water during a heatwave or a chiller upset, exactly when the fire reserve should be least disturbed, so the two demands are deliberately decoupled in the balance and any shared makeup is metered and alarmed so a cooling draw never silently reduces the fire volume. The reserve stays whole because the balance was designed to keep it whole, not because an operator remembered.

Compliance documentation for the data centre

The authority reviews the tank against NFPA 22 and the demand against NFPA 13 and NFPA 20; the insurer reviews the same plus the redundancy and monitoring it expects for a high-value, high-availability site. The documentation that satisfies both is the hydraulic demand basis, the tank volume statement distinguishing nominal from usable volume, the coating and construction identification, the pump-set interface, and the monitoring and alarm description.

Present it as one reconciliation so a reviewer can trace the volume from hazard to tank to pump without a gap. A submittal that hands over the tank drawings, the hydraulic calculation and the pump schedule as three unrelated files invites the exact question the reviewer is paid to ask: do these three actually agree?

Where the reserve sits in the site water balance

Place the reserve so its dedicated makeup does not contend with cooling or humidification demand during a refill event, and so process upsets cannot pull from it. A common arrangement keeps the fire tank on its own supply main with backflow protection, separate from the process and cooling mains, and meters or alarms any crossover.

The reserve's volume is reported in the site water balance as a protected static store, distinct from circulating or consumed volumes. That keeps the fire capacity auditable and stops it being counted twice or borrowed for a cooling top-up, which is the failure that turns a paperwork problem into a protection problem.

A reserve reported only as a total site volume hides this separation, which is why the fire store is itemised on its own line and the cooling and process volumes are shown alongside it. An operator reading the balance then sees three distinct quantities, not one, and the fire capacity is auditable at a glance rather than reconstructed after an incident.

Acceptance and handover

At handover the authority wants evidence the NFPA 22 acceptance tests, Chapter 17, were completed and the inspection programme, Chapter 18, delivered, and the insurer wants the demand reconciliation and the monitoring evidence. The deliverables are the as-built tank and nozzle schedule matching the approved drawings, the coating records, the pump-set interface verification, the acceptance test records and the inspection and monitoring programme.

Hand these over as one package with the volume reconciliation, so the operating team inherits a reserve whose capacity, suction arrangement and alarms are documented and checkable rather than assumed. The tank is the visible part; the record behind it is what keeps the reserve valid through the years after the project team has moved on.

Data Centre Fire Reserve Demand Basis (NFPA 13 Build-Up)

Demand Component

Basis

Source

Effect On Volume

Design density

Water per unit area for the space hazard

NFPA 13

Sets the flow rate

Design area

Most demanding space area (white space / battery room)

NFPA 13

Sets the flow rate

Duration

System water-supply duration plus insurer requirement

NFPA 13 / insurer

Multiplies flow into volume

Hose stream allowance

Where the standard requires it

NFPA 13

Adds to total demand

Usable versus nominal volume

Drawdown between operating level and low-level alarm

NFPA 20 / NFPA 22

Tank sized on usable volume

Compliance And Handover Evidence For A Data Centre Reserve

Requirement

Governing Reference

Document To Provide

Reviewed By

Demand reconciliation

NFPA 13

Density x area x duration calculation

Authority and insurer

Tank volume statement

NFPA 22

Nominal and usable volume, drawdown

Authority and insurer

Construction and coating

NFPA 22 (Chapter 5 or 6) with AWWA

Construction standard and coating records

Authority

Pump-set interface

NFPA 20

Suction arrangement, available suction head, anti-vortex

Authority and insurer

Monitoring and alarms

NFPA 22 Chapters 15 and 16, owner specification

Alarm points, panel interface

Insurer

Acceptance and inspection

NFPA 22 Chapters 17 and 18

Test records, inspection programme

Authority and insurer

 

About Center Enamel

Center Enamel (Shijiazhuang Zhengzhong Technology Co., Ltd.) designs and fabricates bolted steel storage tanks, welded steel tanks, fusion-bonded epoxy tanks, galvanized tanks, stainless steel vessels, pressure vessels, aluminum geodesic dome roofs and floating roofs. The company has more than 30 years of production experience and has supplied equipment to projects in more than 100 countries. Aluminum geodesic dome roofs are designed and fabricated to API 650 Appendix G, AWWA D108, the Aluminum Design Manual, ASCE 7 and IBC, and the company developed and exported a 72 m diameter aluminum dome roof in 2023. Engineering, fabrication, coating, quality control and site service are handled as one scope, which is why the drawings, the calculation basis and the delivered hardware can be reconciled against each other.

Frequently Asked Questions

How much fire water does a data centre need?

The volume follows the NFPA 13 demand: the design density and area for the most demanding space, usually the white space or the battery and electrical rooms, times the required duration, plus any hose stream allowance. The tank's usable volume, the volume between the normal level and the low-level alarm that protects the pump, is what the pump draws on, and it is smaller than the nominal volume. There is no single figure for every data centre; it is built from the actual hazard, density, area and duration, so it varies by layout.

What is the difference between data centre and ordinary fire water demand?

The tank is the same kind of storage, but the demand basis is usually larger and more thoroughly documented. A data centre serves multiple halls from one reserve, so you take the most demanding space and its density rather than a single small hazard, and the insurer reviews the basis to a stricter expectation than the code minimum. The engineering difference is in the demand build-up, the pump-set integration and the compliance evidence, not in the tank construction itself.

How does the data centre Tier rating affect the fire reserve?

The data centre infrastructure classification, from Tier I to Tier IV, addresses infrastructure redundancy and availability, not a mandated fire water volume. A higher tier raises the expectation of redundant pumps, diverse power and monitored makeup around the fire supply, but it does not by itself enlarge the tank. You size the volume from the NFPA 13 duration plus any insurer requirement, and you meet the tier through redundancy and monitoring of the supply rather than by increasing the stored volume.

How does the fire reserve interact with the site water balance?

The fire volume is a dedicated, protected reserve that must not be consumed by cooling makeup, humidification or process demand. Its makeup source is sized to refill the required volume within the design-basis time without contending with those other uses, and it is reported in the site water balance as a separate static store with its own supply main and backflow protection. That keeps the fire capacity auditable and prevents it being borrowed or double-counted.

What compliance evidence does a data centre insurer expect?

Beyond the NFPA 22, NFPA 13 and NFPA 20 basis the authority reviews, the insurer expects the redundancy and monitoring appropriate to a high-value, high-availability site: the demand reconciliation, the nominal-versus-usable volume statement, the pump-set interface and available suction head, and the alarm and monitoring evidence. Present it as one traceable package so the volume can be followed from hazard to tank to pump without a gap.

How should the fire tank be integrated with the pump set?

Feed the fire pump set under NFPA 20 with a full, vortex-free stream: an anti-vortex device or downturned suction, the outlet above the tank floor, and suction piping sized and supported to avoid air traps or restriction. Size the connection to the pump demand and reconcile the usable drawdown with the duration calculation, so the volume the pump can actually draw matches the design. The coating and construction follow the chosen tank standard referenced by NFPA 22.

Does the fire reserve count in the site water balance?

Yes, as a protected static store, but it is not a circulating or consumed volume. It appears in the balance as a dedicated reserve with its own makeup path and backflow protection, separate from cooling and process mains, and any crossover is alarmed. Counting it as a working volume would overstate available water and risk the reserve being drawn down for other uses, so it is reported distinctly and protected from borrowing.

What is accepted at handover?

The authority wants the NFPA 22 Chapter 17 acceptance test records and the Chapter 18 inspection programme; the insurer wants the demand reconciliation and monitoring evidence. The handover package is the as-built tank and nozzle schedule matching the approved drawings, coating records, pump-set interface verification, acceptance test records and the inspection and monitoring programme, delivered with the volume reconciliation so the operating team inherits a documented, checkable reserve.

A data centre fire reserve is an exercise in traceability: from the NFPA 13 hazard and density of the most demanding space, through the duration and the insurer's requirement, to a tank volume stated on its usable drawdown and a pump set that can actually draw it. The site tier changes the redundancy and monitoring around that supply, not the volume itself.

Close the loop by integrating the tank with the NFPA 20 pump set, protecting the reserve within the site water balance, and handing over one package of demand reconciliation, volume statement, pump-set interface and acceptance records. Send us the layout, the hazard densities, the adopted duration and the site water balance, and we will return a fire reserve specification that an authority and an insurer can both trace from hazard to tank to pump.

Talk To Our Engineering Team

Send the duty, the volume basis, the governing code and the site constraints, and our engineering team will come back with a specification that a supplier can price and a reviewer can approve. We will also tell you plainly when a different tank type or a different scope is the better answer.

Chat with us