Cooling and Mechanical: ASHRAE 180 and the Loads Nobody Owns
The cooling that serves the data hall gets watched closely, because everyone agrees it matters. The rest of the mechanical plant in the same building often has no clear owner at all.
ASHRAE 180 is concerned with the inspection and maintenance of building HVAC systems, and with keeping a record of the condition of that equipment. It applies only where a jurisdiction, a permit, the authority having jurisdiction, an insurer or a contract has adopted it.
In a data center, the hard part is rarely the equipment everyone watches. It is the equipment nobody has claimed.
Which loads nobody owns
Start with the cooling for the electrical rooms and the UPS space. It is critical, and it is not in the data hall.
Then there is comfort cooling for the offices, the NOC and the security desk. There are split units added years ago for one specific room and never folded into anyone's programme.
There is rooftop and outdoor equipment that nobody passes on a normal day. There is exhaust and ventilation for storage and plant spaces.
Each one is somebody's responsibility in principle. On any given Tuesday, it is nobody's.
Why the gap forms
The gap is structural. The data center team owns what the racks depend on, the building team owns the building, and these units sit in the overlap between the two.
Both teams are doing their jobs. The overlap is simply a place that the usual way of staffing a building does not cover well.
These units also rarely fail loudly. A split unit slowly losing capacity in an electrical room does not alarm anything until the room is already warm.
What a record of these spaces gives you
A record means the same points revisited, so the condition of the equipment is known before it becomes a problem. Filter and coil condition, visible leaks or staining, the thermal condition of the unit, and the conditions in the room it serves.
That series is what lets anyone argue for a repair or a replacement with evidence rather than a hunch. It is also what an auditor, or an insurer's risk engineer, expects and reviews when asking how the plant is maintained.
A record documents conditions. A qualified person and the authority having jurisdiction determine compliance.
Where FacilityOps fits
On every pass, a FacilityOps robot walks the route through mechanical and support spaces as well as the data hall. It captures condition at the same checkpoints every time, each capture bound to its run and checkpoint, and raises exceptions to a qualified person who makes the call.
This is where a robot earns its keep. The equipment nobody owns is also the equipment nobody walks past, and a route does not care whether a room is interesting. The FacilityOps robot stops there anyway, every pass.
The same walk that documents the data hall documents the unowned loads. They stop being invisible without anyone having to be assigned to them.
One FacilityOps robot route produces the records across all nine compliance surfaces.
If you want to see how the unglamorous rooms show up in a record, we can send you a sample inspection record.
Everything in this piece, as a checklist you can take on your rounds
Turn the key points from this article into a practical inspection checklist.