Compliance Surfaces · Inspection Route

The Nine Compliance Surfaces One Route Has to Cover

A data center does not answer to a single rulebook: it answers to nine distinct areas of concern. Each area carries its own underlying standard and its own strict expectation of evidence. These are not nine different buildings. They concern the very same rooms and mostly the identical equipment.

That shared physical reality is exactly why a single inspection route can produce the records for all nine areas. By designing observation around the facility itself rather than around individual standards, one walk delivers unified documentation.

Historically, facilities run these as nine completely separate programs. Each compliance surface tends to arrive with its own dedicated contractor, an independent calendar, and an isolated folder of reports. These pieces are assembled at completely different times by entirely different people.

Individually, each isolated program is perfectly fine. Collectively, they duplicate site visits and leave massive operational gaps between them. Standards apply where adopted by a jurisdiction, permit, authority having jurisdiction, insurer or contract, and OSHA applies as federal law. Managing them in silos leaves a director unable to answer a simple question about the facility without opening nine different places.

NFPA 70B: electrical equipment maintenance

This standard concerns the ongoing upkeep of electrical systems. A facility is expected to show a documented history of visual and thermal inspections confirming equipment remains in safe working condition.


ASHRAE 180 and IMC: cooling and mechanical

These guidelines focus on the condition and operation of cooling infrastructure. A site is expected to keep clear records showing continuous physical observation of air handlers, pumps, and cooling units over time.


NFPA 110 and NEC 702: emergency and standby power

This surface addresses the physical readiness of backup power systems. Facilities are expected to show, through logged physical checks, that generators and transfer switches are visually intact and ready.


IFC and ICC: fire, life safety and egress

These codes deal directly with the physical paths out of a building. A facility is expected to show that corridors stay clear, doors close as intended, and nothing obstructs a safe exit route.


NFPA 75, 2024 edition: IT equipment fire protection

This document targets fire risks specific to computing spaces. Sites are expected to document the physical environment around servers, proving aisles are clear and combustible materials are kept safely away.


NEC, NFPA 70: installed electrical

This standard governs the safe physical installation of electrical infrastructure. Evidence should show that panels remain accessible, clearances are maintained, and original installations have not been physically compromised over time.


OSHA 1910: workplace safety

This covers a safe environment for personnel on the floor. A facility is expected to keep routine observations showing that walking surfaces are clear, hazards are managed, and worker safety is maintained.


NFPA 855: energy storage, where present

This standard focuses on the condition of large battery systems. Sites are expected to keep track of the condition of energy storage installations so early signs of physical distress are caught.


SOC 2, ISO 27001 and PCI DSS: audit and contract evidence

These frameworks provide assurance to clients regarding security and reliability. Facilities are expected to present a consistent, traceable history of physical observations to verify that stated operational controls are actually in place.


The same pass in front of a switchboard, a battery cabinet, a CRAC unit, or an egress door answers very different questions depending on which surface is asking. It is still just one physical observation captured once.

The visual and thermal condition of a single electrical termination serves the electrical compliance surfaces. At the same time, a single walk past a propped open door serves fire, egress, and workplace safety requirements all at once.

A consistent, timestamped, and precisely located series of visual captures is exactly the shape that audit and contract evidence expects. We document conditions. A qualified person and the authority having jurisdiction determine compliance. The route is built around the physical building, and the nine surfaces simply draw their evidence from that single pass.


What does the robot do on a pass?

A FacilityOps robot physically walks the designated route and stops at the exact same checkpoints in the identical order every single time. A FacilityOps robot captures the visual and thermal condition of the critical equipment situated directly in front of its sensors. The FacilityOps sensor hub it carries also takes acoustic, ultrasonic and gas readings at each stop, so one pass serves several surfaces at once.

Every single capture is permanently bound to a specific run and checkpoint so it can be reliably traced later by your staff. These new readings are then directly compared against the previous pass. Anything that has physically changed is raised immediately as an exception to be reviewed, rather than being buried deep inside a static report.


Why use a robot instead of a person with a clipboard?

The primary reason to use a FacilityOps robot is consistency. You get the exact same route, the identical checkpoints, and the exact same framing on a quiet week as you do on a bad one.

A FacilityOps robot executes this at three in the morning as readily as at ten in the morning. That repeatability is what makes one pass directly comparable to the last. Comparability is exactly what turns passing observations into hard evidence. This consistency is the reason the ninth surface gets the identical quality of record as the first.


What won't the robot do?

A FacilityOps robot opens absolutely nothing. It performs no electrical work, it replaces no licensed contractor, and it certifies no compliance.

Raised exceptions always go directly to a qualified person. We document conditions, and the authority having jurisdiction decides what the documented evidence actually means in terms of final compliance.


What do you end up with?

You are left with one FacilityOps robot route producing the necessary records across all nine compliance surfaces. This vital data lives in one single place.

It is securely held in a form that an auditor, a customer, or an insurer's risk engineer can easily follow. This is the kind of history an insurer's risk engineer reviews. One FacilityOps robot route produces the records across all nine compliance surfaces.

If you want to see how one pass produces records across more than one surface, 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.