In a room full of electronics the fire is rarely the most expensive thing that happens. A sprinkler discharge over a rack, or a powder unit let off by somebody trying to help, can finish equipment the fire had barely reached, and the outage lasts as long as the procurement. So the design question is not how to put out a fire but how to stop one while leaving the hardware usable, which is why these rooms get very early detection and a gaseous agent rather than water, and why the room itself becomes part of the system.
What the design usually is, and why
Three layers. Very early smoke detection, often an aspirating system drawing air continuously through pipework so it samples the room rather than waiting for smoke to reach a ceiling detector, because the airflow in a server room moves smoke away from where a point detector sits. A gaseous agent, either a chemical clean agent or an inert gas mixture, that stops combustion without residue and at a concentration people can be in for the short time it takes to leave. And a control sequence that shuts down what needs shutting down and holds the room closed. The cylinders are the cheap part of that list.
Server room fire suppression and room integrity, which is measured rather than assumed
A gaseous system works by holding a concentration in the room for a stated hold time, so the enclosure has to be tight enough to keep it there. That is proven by a fan pressurisation test, the door fan test, which measures leakage and predicts the hold time, and it is repeated when the room is altered. This is the single commonest failure in practice, and it is nearly always caused by later work nobody told the fire contractor about: a new cable route through a wall, a removed ceiling tile, a grille fitted for cooling. A system commissioned as compliant three years ago can fail its retest for a hole the size of a fist.
The shutdown sequence, and the second common failure
Air handling is the one that catches people. If the cooling keeps running when the agent releases, the agent leaves through the ducts while the fire is still burning, so the sequence has to stop the fans and close the dampers as well as releasing the gas, and the commissioning test has to prove it did. The other interlocks worth naming in the specification are the power to the room or to specific racks, the door releases, the alarm to whoever is on call, and the manual hold that lets somebody who is in the room stop the discharge while they leave.
What a quote should say, and what happens after a discharge
Which standard the design is to, who signs it, what the detection is and what it triggers, what the hold time is and what door fan test result supports it, what the service regime is including cylinder weighing, and what the recharge costs. That last one is worth knowing in advance: a discharge means the agent is gone, the room needs ventilating, the cylinders need refilling or replacing and the system needs recommissioning before it protects anything again, and none of that is usually inside the service contract.
Fire suppression system installation, and the order the work happens in
The sequence is fixed and skipping a step shows up at commissioning. First the design: the hazard, the enclosure, the agent and the standard the system is designed to, signed off with the insurer where they have an interest, because an insurer's requirement discovered late changes the whole specification. Then first fix: containers, pipework and nozzles, with the room's own openings identified. Then the enclosure itself, which is the step most often underestimated on a gas system, because the agent only works if the room holds it: dampers, door closers, sealing of cable and pipe penetrations, and a fan integrity test to prove the hold time. Then detection and the panel, with the interlocks that shut down air handling and, where required, power. Then commissioning against the design, including the discharge alarms, the delay and the manual release. Then the handover pack and a maintenance contract, because a suppression system that nobody services is a pressurised cylinder with a label on it.
Questions people ask about data center fire suppression
Are sprinklers ever right in a server room?
Sometimes, and usually because the building rather than the room demands them. Where sprinkler protection is required across a floor, a pre action system is the common answer: the pipework stays dry until detection operates, so a damaged head does not flood the room, and a second event is needed before water is released. That reduces the accidental discharge risk, which is the main objection. Where the room can be treated separately, a gaseous system and no water in the room is still the preference of most operators, with the sprinkler protection outside the enclosure.
What is fire suppression doing that detection alone does not?
Acting. Detection tells people and it does not stop anything, which is enough where people are present and can act, and not enough in a room that is usually empty and holds a fire risk in an enclosure of its own. Suppression puts something on the fire in the seconds after detection, with nobody there. It is worth the money where the contents are expensive, the room is unmanned, and an outage matters more than the equipment: which is the argument for it in a data centre and against it in a stationery store.
How often is a gaseous system serviced?
To the manufacturer's and the standard's schedule, which typically means a service twice a year, a weight or pressure check of the cylinders on their own interval, and a repeat of the room integrity test whenever the enclosure is altered and periodically in any case. Add one item to the regime that nobody writes down: a change control that tells the fire contractor before anybody drills a wall, routes a cable or fits a grille in that room, because that is what actually invalidates the system between services.