Sign in
← Articles
comms rooms data centres cooling load psychrometrics gas suppression redundancy

Comms Rooms: A Building Services Engineer's Guide

A few things about Comms room.


When we design mechanical systems for IT spaces, we are not simply cooling a room. We are protecting the backbone of the digital infrastructure that keeps an entire building connected. Every decision we make about airflow, pipework, and equipment sizing must follow the physics of data transmission and the real thermal behaviour of the hardware. Let us walk through the key principles so you can see exactly how architecture, networking, and mechanical engineering lock together.

1. Room Hierarchy and Spatial Constraints

The first thing we must understand is the architectural hierarchy of IT spaces. This hierarchy dictates where we place cooling plant and how we route services.

  • Main Comms Room (MDF / MER / BD) This is the network core. It carries the highest continuous heat loads and runs 24 hours a day, every day of the year. We therefore provide precision cooling with N+1 redundancy and gas fire suppression.

  • Floor Comms Room (IDF / SER / FD) These rooms distribute data to local zones on each floor. Architects usually stack them vertically to create a continuous IT riser. That vertical alignment helps us route mechanical pipework and electrical risers cleanly.

There is one absolute physical limit that overrides almost every other consideration: the 90-metre rule for permanent copper links. Beyond 90 metres, copper data signals degrade to the point where the connection becomes unreliable. This physics constraint fixes the location of every IDF. We cannot simply move a comms room closer to a plant room to shorten chilled-water pipework. The cooling infrastructure must follow the IT demarcation points, not the other way around.

1Interactive model

The copper fixes the room. The pipework has to follow.

Move the comms room toward the plant room and the chilled-water run gets shorter, which is what every services engineer wants. Watch what happens to the copper links while you do it.

Links beyond 90 m
0
all inside the limit
Longest routed run
59 m
includes 12 m of drop, rise and slack
Chilled water run
66 m
plant room to comms room

Drag it into the bottom-right corner. The pipe run roughly halves, and the far side of the floor goes out of reach. There is no setting where you buy shorter pipework without breaking links, which is why this constraint is settled before any mechanical layout begins.

Inside these rooms the hardware itself imposes further spatial rules.

  • An enclosed cabinet (rack) forces strict front-to-back airflow. We must deliver cool air to the front doors and extract hot air from the rear.
  • One rack unit (1U or 1RU) measures exactly 44.45 mm. A typical 42U or 47U cabinet stands roughly 2.2 m high. All high-level mechanical services, cable trays, and pipework must be coordinated in section drawings so they never clash with these cabinets.
Fig. 1 — Front-to-back airflow and the section it demands
soffitcable traypipeworkcontainmentcabinet2.2 mcool air infront doorhot air outrearfinished floor1U = 44.45 mm
Cool air enters the front door, leaves at the rear, and the cabinet reaches roughly 2.2 m. Everything above it has to be coordinated in section.

2. Hardware Anatomy and Thermal Profiles

Not every rack produces the same heat. We treat each rack according to its actual thermal profile rather than applying a single average figure.

  • Server racks typically dissipate 3.0 to 10.0 kW. Their load is highly dynamic and peaks with compute demand. We therefore design for variable air volume and a high temperature difference.
  • Network racks produce 0.5 to 3.0 kW of steady heat, driven largely by Power over Ethernet. Constant-volume airflow with a strong wash across the front of the equipment works best.
  • CCTV and storage racks run almost flat at 1.0 to 3.0 kW with a near 100 percent duty cycle. We apply a diversity factor of 1.0.
  • AV racks generate 0.5 to 2.0 kW of intermittent heat. We size cooling on the 1/8th power rule rather than the nameplate rating.
  • Controls racks stay below 0.5 kW and can usually rely on ambient room cooling alone.
2Interactive model

Not every rack produces the same heat

Each row shows the range that rack type draws, with the live bar moving at its own duty. The server rack swings with compute demand and the AV rack barely wakes up, while network, CCTV and controls sit flat. Add and remove racks to build a room.

Server
Highly dynamic, peaks with compute demand. High temperature difference.
2
Network
Steady, driven by PoE. Strong wash across the front.
2
CCTV and storage
Near 100 percent duty cycle, almost flat.
1
AV
Intermittent. Size on 1/8th power, not the nameplate.
1
Controls
Stays below 0.5 kW. Ambient room cooling is usually enough.
1
Racks in the room
7
across five profiles
Sum of maxima
31.5 kW
if everything peaked at once
At each rack's duty
23.8 kW
the figure to design on

Load the room with AV racks and the two totals pull far apart, because the 1/8th power rule applies to that row and to no other. Load it with CCTV and they converge, because that row runs at a diversity factor of 1.0 and never idles.

Now let us look at the network hardware that lives inside these racks.

Patch panels are completely passive. They terminate the solid-core horizontal cables and generate zero heat. Short stranded patch cords then connect the panel to the switch. This arrangement protects the permanent cabling from wear and makes changes simple.

Access switches (Layer 2) do the real work. They route traffic according to MAC addresses and also supply Power over Ethernet to cameras, wireless access points, and other field devices. Power is therefore drawn both by the switch’s own electronics and by the devices it feeds.

Data flow follows a clear pattern. Twenty-four horizontal copper cables typically feed into twenty-four switch ports. The switch buffers and aggregates that traffic, then sends it upstream through two to four high-speed fibre uplinks to the core (Layer 3). The system relies on a contention ratio, often around 20:1, because not every device transmits at peak rate at the same moment.

Copper is used for the final field runs under 90 metres because it can carry both data and power. Fibre is used for risers and uplinks. Fibre carries photons, so it is immune to electromagnetic interference, supports far higher bandwidth over long distances, and keeps containment sizes small.

3Interactive model

Twenty-four copper links, two fibre uplinks, and why that works

Packets rise from the horizontal copper, buffer at the switch, and leave on the fibre. The uplink is far narrower than the sum of the ports because not every device transmits at peak rate at the same moment. Raise the activity and watch the buffer fill.

Sum of the ports
24 Gb
if all transmitted at once
Uplink capacity
20 Gb
2 × 10 Gb fibre
Contention ratio
1.2:1
design guideline is 20:1
Offered right now
2.4 Gb
10 % of ports active
Uplink state
Comfortable
uplink keeping up
Guideline uplink
1.2 Gb
what 20:1 would call for

Drop the uplinks to one at 1 Gb and the ratio goes past the guideline, the buffer fills, and the switch starts holding traffic it cannot forward. None of this changes the heat in the room. The switch draws what it draws whether the uplink is busy or idle, which is the point of the next model.

The physics of heat generation is straightforward once you see it. Switches and servers perform no mechanical work. Their power supplies convert 230 V AC into low-voltage DC. As those DC electrons move through the silicon lattice of the microchips, they collide with silicon atoms. The collisions transfer kinetic energy and cause the atomic lattice to vibrate. Those vibrations are what we experience as sensible heat. In practical terms, virtually 100 percent of the electrical power that enters the equipment leaves as heat.

4Interactive model

Where the electricity actually goes

Electrons drift through the lattice and collide with the silicon atoms. Each collision hands over kinetic energy and the atom vibrates harder. That vibration is the sensible heat. Raise the drift and watch the lattice get louder.

Electrical power in
300 W
230 V AC to low-voltage DC
Mechanical work done
0 W
nothing moves, nothing lifts
Sensible heat out
300 W
virtually 100 percent

This is why an IT load is simpler to size than almost anything else in a building. There is no fan doing work on air, no pump lifting water, no chemical change storing energy. Whatever you meter at the socket is what you have to take back out of the room.

3. The Nameplate Fallacy: Real Power versus Electrical Schedules

If we size cooling plant from electrical nameplates or fuse ratings, we almost always oversize the system. Oversizing wastes capital, increases energy use, and often causes the cooling equipment itself to fail.

Consider a server fitted with two 1000 W power supplies. In normal operation the server may draw only 300 W in total (150 W from each supply). If one supply fails, the remaining supply simply takes the full 300 W. The heat load is therefore 300 W, not 2000 W.

5Interactive model

Two supplies do not make two loads

A server with two 1000 W supplies reads as 2000 W on an electrical schedule. It draws 300 W, shared between them. Pull one supply and the survivor takes the whole 300 W. The heat in the room never changes, because the redundancy sits in the supply path, not in the work being done.

Schedule figure
2.00 kW
two supplies added together
Real draw
300 W
what the machine actually uses
Per live supply
150 W
shared between two
Survivor loading
15 %
of its own rating
Heat load
300 W
unchanged by the failure
Real ÷ schedule
15 %
the sizing error you avoid

The same gap opens across every class of equipment. Servers commonly run at 30 to 50 percent of nameplate, network switches at 40 to 60 percent, and AV amplifiers reject heat at roughly one-eighth of their peak rated output.

In practice, servers commonly operate at 30 to 50 percent of their nameplate rating. Network switches typically run at 40 to 60 percent. AV amplifiers reject continuous sensible heat at roughly one-eighth of their peak rated output.

The mechanical consequences of oversizing are serious. An oversized direct-expansion unit short-cycles its compressor, destroying the bearings. Even when the thermal load is low, the fans still push the design mass flow rate. The temperature difference across the coil collapses according to the familiar equation:

Q=m˙CpΔTQ = \dot{m} \cdot C_p \cdot \Delta T

When ΔT\Delta T becomes too small, return air temperatures can drop low enough to freeze the cooling coil. The only reliable approach is to design from manufacturer-calculated thermal dissipation data, never from electrical schedules.

6Interactive model

Oversize it and the temperature difference collapses

The fans keep pushing the design mass flow whatever the load does. Drop the actual load below the design figure and watch the air-side temperature difference shrink, the return air fall toward the supply, and the coil head for freezing while the compressor hunts.

Oversized by
3.3 ×
design against actual
Air-side ΔT
3.6 K
design is 12 K
Mass flow
553 L/s
unchanged, the fan does not know
Supply air
22.4 °C
return is 26.0 °C
Evaporating temp
-3.8 °C
below freezing
Compressor
Short cycling
destroying its bearings

Set the design load to 8 kW against a real 2.4 kW, which is roughly what sizing from an electrical schedule gives you. The temperature difference falls to about a quarter of design, and the unit spends its life starting and stopping. Nothing about that failure is visible on the drawing that caused it.

4. Cooling Strategies and Psychrometrics

Main Comms Rooms (MDFs) need precision close-control units (CCUs or CRAHs). The reason is the sensible-heat-ratio problem. Comms rooms produce almost no moisture, so the sensible heat ratio is essentially 1.0. A standard comfort-cooling coil that evaporates at around 6 °C will strip moisture from the air, drive relative humidity down, and create a serious risk of electrostatic discharge damage to silicon.

We solve this by raising the chilled-water temperature (for example to 14 °C) so that the coil surface stays above the room dew point. Raising the water temperature, however, reduces the log-mean temperature difference:

Q=UAΔTLMTDQ = U \cdot A \cdot \Delta T_{\text{LMTD}}

Close-control units compensate for the lower ΔTLMTD\Delta T_{\text{LMTD}} by using very large cooling coils (high surface area AA) and high-volume EC plug fans (high mass flow m˙\dot{m}). The result is 100 percent sensible cooling while the central chillers run at a much higher coefficient of performance and enjoy many more free-cooling hours.

7Interactive model

Raise the water, keep the coil dry, then pay for it

A comms room makes almost no moisture, so the sensible heat ratio is essentially 1.0. Push the chilled water up until the coil surface clears the room dew point and the process line goes flat. Watch what happens to the log-mean temperature difference at the same time.

Room dew point
12.9 °C
at 24 °C, 50 % RH
Coil surface
15.0 °C
flow temperature plus 1 K
Coil condition
Dry
100 percent sensible
LMTD
4.00 K
comfort baseline 9.87 K
Coil area needed
× 2.47
to hold the same duty
Airflow needed
× 1.67
EC plug fans earn their keep

The line is flat and the coil is dry, so the whole duty is sensible. The price is on the right: the coil has to be about 2.5 times the surface area and move about 1.7 times the air of a comfort selection. That is exactly why a close-control unit is mostly coil and fan.

Floor Comms Rooms (IDFs) are different. Heat loads are lower and more constant, space is tight, and the equipment is more resilient. Standard fan-coil units or DX split systems are usually acceptable. Although the coil still operates below dew point, severe over-drying is prevented by two natural mechanisms:

  1. Moisture infiltrates from the surrounding occupied offices and equalises vapour pressure.
  2. Two-way pressure-independent control valves modulate. As load falls the valve closes, coil temperature rises above dew point, and latent cooling stops.

We still apply strict rules: size the unit on sensible capacity only, provide gravity-drained deep secondary drip trays, and feed the unit from a true 24/7 cooling source (dedicated DX or a continuous chilled-water loop).

5. Redundancy, Resilience, and Maintainability

Cooling failure in a densely loaded room can produce thermal runaway within 5 to 15 minutes. We therefore design to the N+1 principle. N is the capacity required to meet the peak load. N+1 means that capacity plus one complete standby unit.

Eliminating single points of failure requires attention to every system:

  • Pipework: N+1 close-control units connected to a single header still form an N-level system. We use dual-path (A/B) headers or isolation ring mains.
  • Electrical: Redundant cooling units must be fed from separate distribution boards and separate generator paths.
  • Controls: Units operate on local, hardwired master/slave networks. The central building management system monitors only; it never controls the cooling sequence.
8Interactive model

N+1 on a single header is still N

Two units is not redundancy until every path they share has been broken. Break each one in turn, then fail Unit A and see whether the room survives. While any single dependency is still common, the failure simply crosses to the standby.

Shared paths left
3
single points of failure
Configuration
N in practice
two units, one fate
Room state
Cooled
both units healthy

Start with all three shared, which is the common as-built condition, and fail Unit A. The standby follows it down every time. Concurrent maintainability asks a harder version of the same question: can you isolate any one valve, fan, compressor or pump during working hours and still hold the room inside the ASHRAE limits?

Concurrent maintainability is equally important. We must be able to isolate and replace any single component (valve, fan, compressor, or pump) during normal working hours without the room temperature exceeding ASHRAE recommended limits.

6. Fire Detection and Suppression Interfaces

Water sprinklers destroy IT equipment, so comms rooms use gas suppression. The mechanical engineer largely decides whether that suppression system succeeds or fails.

  1. Detection must use aspirating smoke detection (ASD or VESDA). These systems sense the earliest off-gassing from overheating cables. Ordinary point detectors are almost useless in the high-airflow environment of a modern IT room.

  2. On second-stage fire alarm a hardwired interlock must instantly cut power to every cooling unit in the room and close all motorised fire and smoke dampers. If plug fans continue to run they will dilute and disperse the suppression gas, preventing extinguishment.

  3. Gas discharge creates a rapid pressure rise. Counter-weighted pressure-relief dampers sized for the discharge volume must open to protect the room structure, then snap shut again to retain the gas.

  4. The room must maintain the required gas concentration for a full ten minutes. Every mechanical penetration (duct, pipe, or cable tray) must be hermetically fire-stopped.

  5. After discharge a dedicated mechanical extract system, started manually from outside the room, purges the toxic by-products and residual gas directly to atmosphere.

9Interactive model

Cut the fans, hold the gas, and start a different clock

The interlock stops every fan so the discharge is not diluted, which is correct. It also removes the only thing taking heat out of a room full of running IT. The ten-minute hold and the thermal runaway run against each other, and coordinating them is the mechanical engineer's job.

Hold time required
10 min
every penetration fire-stopped
Thermal runaway
1.6 min
fans off, IT still running
Which arrives first
The heat
room cooks before the hold ends

Turn the interlock off and watch the racks stay cool while the agent concentration never builds. That is the trade in one picture: the fans that keep the room alive are the same fans that would disperse the gas and prevent extinguishment. There is no setting where both are true at once.

When we follow these principles, the mechanical systems become a quiet, reliable partner to the IT infrastructure rather than a source of risk. The physics of data transmission, heat generation, and airflow never change. Our task is simply to respect that physics at every stage of design.