If you service standby generators, "NFPA 110" comes up constantly — in specs, in contracts, in what an auditor asks for. It is worth knowing exactly what it is, what it asks for, and, just as important, what it does not pin down on its own.
Here is the short version: NFPA 110 sets the framework for emergency and standby power. But the exact intervals, durations, and classifications are not a single number you can memorize. They come from the edition your jurisdiction adopted and from the authority having jurisdiction. This guide explains how the pieces fit so you can have an accurate conversation with a facility owner or an inspector — and confirm the specifics where they actually live.
What NFPA 110 is
NFPA 110 is the National Fire Protection Association standard for emergency and standby power systems. It covers the engine-generator set and the surrounding equipment — the prime mover, the alternator, the fuel and starting systems, the transfer equipment, and the controls and accessories that make up a standby power system.
The standard addresses how those systems are installed, maintained, operated, and tested. In other words, it is not only about how the equipment goes in — it is about keeping it ready to work and proving that it will.
Editions and adoption: why there is no single answer
NFPA 110 has multiple editions. Which one applies to a given facility is determined by the codes the jurisdiction has adopted and by the authority having jurisdiction (AHJ).
This matters more than it sounds. A standard such as NFPA 110 has legal force only where it has been adopted, and adoption can vary by jurisdiction. Two buildings in two states — or two occupancy types — can be held to different editions and different specifics. That is why a responsible answer to "what does NFPA 110 require here?" always ends with: confirm the governing edition with the AHJ.
The honest framing
How NFPA 110 classifies systems: level, class, and type
NFPA 110 classifies emergency and standby power systems using three concepts: level, class, and type. You will see these on spec sheets and in contracts, so it is worth understanding what each one describes.
Level
Level relates to how critical the connected loads are — broadly, how directly the system relates to protecting life. The more directly the loads tie to human safety, the more demanding the requirements.
Class
Class relates to the minimum time the system is expected to run at rated load without refueling or recharging. It is a measure of endurance: how long the system has to keep carrying the load on its own.
Type
Type relates to how quickly power must be available after normal power is lost. It is the response-time dimension — how long the load can sit without acceptable power before the standby source has to be there.
The precise categories, definitions, and values for level, class, and type are defined in the adopted edition of the standard. The point to carry forward is structural: a system's classification drives the testing and performance requirements it is held to. Get the classification right and the rest of the requirements follow from it.
The shape of NFPA 110 testing
NFPA 110's testing expectations are generally structured around three kinds of activity: routine inspection, operational testing, and periodic load testing. Think of them as a cascade — frequent and light, to less frequent and more demanding.
Routine inspection
Routine inspection involves regular hands-on checking of the equipment — fluids, batteries, connections, and components. It is the walk-the-machine work that catches small problems before they become no-starts.
Operational testing
Operational testing involves running the system on a regular cadence to confirm it starts, runs, and that the transfer sequence works. For many systems this is frequently described as monthly — but the exact frequency depends on the system classification, the adopted edition, and the AHJ, so confirm it there rather than assuming.
Periodic load testing
Periodic load testing is a less frequent, more demanding test where the system is exercised under load, often on a longer cycle than the routine operational test. Where a real load is not available, supplemental load testing — such as a load bank — commonly enters the picture, on terms defined by the governing edition and the AHJ.
Confirm the specifics
The permanent record is the deliverable
NFPA 110 expects permanent records of inspection, testing, and maintenance to be kept. The maintained record is what an AHJ or auditor asks to see — a test you ran but cannot prove you ran does very little for you when someone comes asking.
A defensible NFPA 110 record generally identifies:
- The equipment tested by identity — make, model, serial, and location.
- When the work was performed.
- Who performed it, as a named person.
- The readings and results.
- Any deficiencies found and corrected.
The exact contents are governed by the edition and the AHJ, but those elements are the backbone of a record that holds up. The through-line: a record is only as good as its attribution. A reading with no named person, no timestamp, and no equipment identity is hard to defend.
Healthcare and other life-safety occupancies may be held to stricter or additional requirements, and additional governing standards or accrediting bodies may apply on top of NFPA 110. If you service hospitals, surgical centers, or similar facilities, do not assume the commercial baseline carries over.
Setting a default cadence on your agreements
Most service shops put a default test cadence in their service agreements so the schedule is clear before the first visit — then adjust per site to match the governing edition and the AHJ. Stating your default plainly keeps customer expectations and your dispatch calendar aligned.
Operator input — SME-1
Where PowerOps fits
PowerOps does not set test intervals or system classification — the governing edition and the AHJ do. What PowerOps does is make the record defensible. Completed PMs, load bank results, and transfer tests become attributed, timestamped records written by a named, authenticated technician at sign-off — not a checkbox someone can backfill later.
Field readings, photos, and serials are captured in the field rather than retyped at the office. And the canonical data — customer, site, the equipment list, access notes, prior findings — auto-flows from one visit to the next, so technicians are not re-entering it every time. The result is the kind of permanent, attributable record NFPA 110 expects you to keep: a named person, a timestamp, the equipment identity, the readings, and the deficiencies — the record an AHJ or auditor actually asks to see.