Skip to main content

Facilities Management

How is data center facilities management different from office FM?

They differ by the number being optimized. An office FM contract is written for cost per square foot. In a data hall, the only number that matters is if the load stays up, and a schedule tuned for the first will quietly trade away the second. We run it the other way around and let cost follow from efficiency rather than from deferral.

On this page

The buildings look similar on a scope document. Both have electrical distribution, mechanical plant, fire, and life-safety systems, security, and a vendor list. The difference is not in the equipment. It is in the number the contract is written to optimize.

An office facilities contract is written for cost per square foot. That is a reasonable target for a building whose worst realistic day is an uncomfortable one. Applied to a data hall, the same instinct defers the work that protects redundancy, and it does it quietly, because a deferral has no line item and an outage does.

Where the scope diverges

In an office, maintenance is an expense line to compress. In a critical facility it is the mechanism that keeps a system redundant, and redundancy is the product.

So the scope changes shape. Preventive work is tuned against the load curve rather than against the calendar. Efficiency work is allowed only where it cannot trade away headroom. Life-safety and electrical systems are maintained to the standard that keeps them redundant rather than to the standard that keeps them legal.

Where the schedule diverges

An office schedule can absorb a slipped task. A data hall schedule cannot absorb a slipped task on a system carrying load, and the only way to know which tasks those are is a criticality rank on every asset.

That is why a contract ported from a commercial portfolio underperforms even when every task in it gets done. The tasks are the wrong tasks, in the wrong order, at intervals set by a building type this one is not.

Where the vendor model diverges

An office building can treat vendors as suppliers of individual services. A data hall cannot, because the failure modes cross vendor boundaries and the handoffs are where they hide.

One operating standard covers every system and every vendor who touches it, and the oversight runs around the clock rather than during business hours. That includes the vendors who were already on site when we arrived, who keep their contracts and start working to the standard.

What we do with an inherited office contract

We read the scope against the building's actual load and risk profile and come back with what it does not cover. That comparison is usually the fastest argument anyone has made for changing it.

In practice

Three things that change when the number changes

The equipment list is close to identical. Everything about how it is held is not.

  • The schedule follows the loadPreventive work is tuned against the load curve rather than the calendar, and efficiency work never trades away headroom.
  • Redundancy is the productElectrical, HVAC, fire and life-safety systems maintained to the standard that keeps them redundant, not the one that keeps them compliant.
  • One standard over every vendorFailure modes cross vendor boundaries, so oversight is round the clock and covers the vendors who were already on site.
58%Fewer critical incidents, one portfolio, nine months after rollout
Still your question

Ask it about your own building.

A general answer is a starting point. If the question is about the site you run, it needs the site in front of it, and you will get a person who runs facilities rather than a form.