The thermal envelope is the service level.

A colocation customer checks one number against their contract: the air arriving at their racks. Everything else — containment, chilled water, UPS autonomy — is judged by whether it holds that number. So is the platform.

What the floor actually argues about

Recommended envelope
18–27 °C at the inlet. Equipment keeps running into the allowable range, but ride-through margin goes with it
Containment differential
Pressure difference across containment, evaluated against the commissioned design. Changes can indicate leakage or recirculation
PUE
Total facility energy divided by IT equipment energy over the same period. Interpret changes alongside IT load, weather and cooling conditions
Ride-through
Measured UPS autonomy to generator start and load acceptance. Decays quietly with battery age
Hot aisle / cold aisle
The separation the whole thermal design rests on, and the first thing a propped-open door defeats
N+1
Redundancy that is only real while the spare unit is actually available, which is a monitoring question

ASHRAE TC9.9 and EN 50600

TC9.9 sets the thermal guidelines for data processing environments — the recommended and allowable envelopes that classes A1–A4 are defined against. EN 50600 covers facility and infrastructure design, including the availability classes that an outage budget is drawn from.

Neither is a certification this platform grants. What it does is state, on every alert, which published limit the threshold came from — so an operator argues with the number rather than guessing where it came from. Rack inlet alerts cite the TC9.9 recommended upper limit. PUE trends cite ISO/IEC 30134-2.

Uptime Institute Tier topology is used here as a design vocabulary, not as a claim of certification.

What a containment failure costs before anyone sees a temperature

A hall running hot despite available cooling capacity may have an airflow or containment problem. The differential drops first, the inlet follows, and by the time the inlet alarms the equipment has already been outside its envelope for a while — spending the component life and the ride-through margin that were supposed to cover a real event.

A rising PUE can prompt investigation, but it does not identify a fault by itself. Review IT load, weather, cooling demand and the measurement boundary together.

Mission-critical facility builds

Build, commission and hand over

Review commissioning records, equipment documentation and outstanding issues across cooling, power and rack infrastructure. Keep evidence attached as systems move into operation.

Operate and maintain

Connect rack inlet temperatures, cooling performance, UPS headroom and Power Usage Effectiveness (PUE) with maintenance history.

Systems in scope: DCIM, BMS, electrical monitoring and historians. Integration scope depends on the installed system, available interfaces and agreed access. Explore the terminology.

Configure the platform around your equipment.

Start with a relevant industry pack, then tailor its equipment points, monitoring rules and alerts to your specifications. Combine it with compatible custom models and map checks to the standards and procedures your team works to.

See how industry packs adapt

Bring your own historian.

Bring data from your historian, such as AVEVA PI System, Honeywell Uniformance, Siemens WinCC or AVEVA Historian. We will validate the available interface, tag mapping and access for your installation.