Data Center Fire Safety Compliance in India: Codes, Suppression and Design Checks

· 5 min read · By Verify AI

India's data center capacity is growing fast, and data centers are some of the most demanding buildings to get through fire approval. They combine very high electrical loads, dense cabling, large battery installations and equipment that water can damage, all in a building that is expected never to go offline.

This guide covers the codes that usually apply, the main design decisions, and the checks worth running early.

Which codes and standards apply

A data center in India is typically reviewed against a combination of national rules and international standards:

Source What it covers
NBCS 2026 Part F (formerly NBC 2016 Part 4), as adopted by your state Building-level fire and life safety: egress, compartmentation, fire protection systems
State fire rules and local bye-laws What is actually mandatory for your project, and the fire NOC process
NFPA 75 Fire protection of information technology equipment and IT rooms
NFPA 76 Fire protection of telecommunications facilities
NFPA 2001 Clean agent fire extinguishing systems
NFPA 72 Fire alarm and detection, including aspirating smoke detection
NFPA 855 Stationary energy storage systems, relevant to large battery installations

Note that the national code changed in 2026: fire and life-safety provisions moved to Part F of NBCS 2026 and became guidance for states to adopt. See NBC 2026 explained. International standards such as NFPA are generally adopted by reference in the project specification or accepted by the authority, so agree the basis of design early.

Detection: find the fire before it spreads

Data halls have high airflow, which dilutes smoke and delays conventional detectors. Common practice is:

  • Aspirating smoke detection (ASD), often referred to by the brand name VESDA, which samples air continuously and detects smoke at very low concentrations.
  • Detection in underfloor voids, ceiling voids and in the containment, not only at ceiling level.
  • Staged alarms so operators can investigate an early warning before suppression discharges.

Suppression: protect people and equipment

Most data centers use more than one system:

  • Clean agent systems (halocarbon agents such as FK-5-1-12, or inert gases) designed to NFPA 2001 for total flooding of data halls and electrical rooms. They extinguish without water or residue. The room must be tight enough to hold the design concentration for the required time, which is why room integrity matters.
  • Pre-action sprinklers, where the pipes stay dry until detection confirms a fire, reducing the risk of accidental water damage.
  • Water mist in some designs, particularly for specific hazards.

The choice depends on the authority's requirements, the insurer, the operator's standards and the building design, and is often a combination.

Battery and UPS rooms

Lithium-ion batteries in UPS and energy storage systems introduce the risk of thermal runaway, where a failing cell heats its neighbours, releases flammable gas and can re-ignite after it appears to be extinguished. Design checks usually include:

  • Separating battery rooms from data halls with fire-rated construction.
  • Off-gas detection and ventilation or explosion control where required.
  • Suppression suited to the hazard, and access for firefighters.
  • Following the battery manufacturer's installation requirements alongside NFPA 855 where it is adopted.

Building-level checks that often get missed

Specialist suppression gets the attention, but many data center comments are about the building itself:

  • Compartmentation. Data halls, electrical rooms, battery rooms, generator rooms and fuel storage need appropriate fire separation.
  • Penetrations. Dense cable and duct penetrations through rated walls and floors must be fire-stopped.
  • Fire dampers wherever ducts cross rated elements, coordinated with clean agent room integrity.
  • Egress. Large, unmanned or lightly staffed floors still need compliant exits and travel distances.
  • Smoke control and ventilation after a clean agent discharge.
  • Emergency power for life-safety systems, routed so one fire cannot take out both supply and backup.
  • Fire tender access to the building and to generator and fuel areas.

These are exactly the MEP and fire interfaces described in MEP coordination and fire compliance, and in a data center there are far more of them.

A practical workflow

  1. Agree the basis of design early with the authority, the insurer and the operator: which edition of the national standards, which NFPA standards and which state rules apply.
  2. Model the fire strategy in the coordinated BIM model, not just on separate drawings.
  3. Run compliance checks on each model update so separation, penetrations and clearances are verified continuously.
  4. Keep an evidence trail of test reports and design decisions, especially for performance-based choices.
  5. Plan for the final fire NOC from the start, including commissioning and integrated testing of detection, suppression and ventilation.

How Verify AI helps

Verify AI reads coordinated IFC models and checks fire, electrical, HVAC and plumbing systems together, including rated separations, dampers, penetrations, panel clearances, egress and emergency power routing, and reports each issue with its location and clause. For data centers, where the number of interfaces is very large, that turns a manual hunt into a reviewable list. Talk to the founder about running it on a data center project.

Sources

This article is general guidance, not a design specification. Requirements vary by state, authority, insurer and operator; confirm the basis of design with the authority having jurisdiction.

← All articles · Try Verify AI