Emergency Power · NFPA 110

Emergency and Standby Power: Why NFPA 110, Not the Fire Code

Emergency power tends to come up during fire safety reviews, so it is easy to assume the fire code covers it. In practice, the fire code treats emergency power as something the building needs. NFPA 110 is the standard that sets out how an emergency or standby power supply system should perform and be maintained, where it is adopted.

Why is the confusion so common?

Generators sit at the edge of fire and life safety. Exit lighting, alarms and other life safety loads may depend on them, so they show up on fire inspections.

But the fire code is not written around the generator itself. The condition of the engine, the transfer switch, the fuel and the batteries that start it is a separate concern, with its own standard.


Which standards apply to what?

NFPA 110 covers the emergency power supply system: the generator, the transfer switches and the equipment that supports them. NFPA 37 covers how the engine is installed.

Data center UPS and battery systems often serve optional standby loads rather than emergency loads. For those, NEC Article 702, the manufacturer's requirements and NFPA 70B usually set the expectations instead. Which applies at your site is for a qualified person and the authority having jurisdiction to confirm.


Where does the record usually thin out?

The formal tests get recorded. What gets lost is everything in between: the condition of the unit, the transfer switch, the fuel system and the starting batteries during the weeks nobody is testing.

Records also split across teams. The generator contractor holds one file, the electrical team another, and nobody holds the picture of the whole path from utility to load.


How does FacilityOps capture it?

A FacilityOps robot walks the route through generator, transfer switch and battery spaces, stopping at the same checkpoints on every pass. The FacilityOps sensor hub it carries captures thermal and visual condition, reads local displays and gauges, and takes acoustic and gas readings at each stop.

Each capture is bound to its run and checkpoint, so the condition of the whole emergency power path between formal tests is a matter of record. The robot runs no tests and operates nothing. Anything unusual goes to a qualified person, who decides what happens next. One FacilityOps robot route produces the records across all nine compliance surfaces.

If you want to see what the months between formal tests look like as 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.