There is a day in every generator project when the equipment is set, the fuel is in, the wiring is terminated, and the paperwork says "installation complete." None of that makes the system real. What makes it real is the acceptance test: the completed installation demonstrating, on site and under load, that it does what the design promised, before anyone is allowed to depend on it.
This guide covers what acceptance testing is, when it applies, who stands around the machine while it runs, how it differs from commissioning and from the testing that follows for the rest of the system's life, and the record it has to leave behind.
What acceptance testing is
Acceptance testing is the proving run for a completed emergency power supply system. It is conducted after installation is finished, with all accessory and support equipment in place and operating (transfer switches, fuel systems, controls, ventilation) because the point is to prove the system as it will serve, not the generator as it left the factory.
The factory test proved the engine and alternator could make rated power on a dyno floor. The acceptance test proves something different: that this unit, on this pad, with this fuel supply, this ventilation path, this transfer equipment, and this building's load, performs as a system. Installation is where the surprises live (an undersized louver, a transfer switch wired to the wrong priority, a fuel line that draws air) and the acceptance test exists to surface them while they are still the contractor's problem.
The general shape of the test
The exact procedure, durations, and loading come from the adopted edition of the governing standard, the job specification, and the AHJ. The shape, though, recurs:
- Simulated failure of the normal source. Power to the facility (or the test boundary) is interrupted on purpose, often at the primary breakers in a new and unoccupied building, so the system sees a real loss instead of a button press.
- Automatic start and transfer. The system must start on its own, come to rated conditions, and transfer the load automatically, with start and transfer times recorded against what the system's type designation promises.
- A sustained run under load. The system carries load for a defined period (building load, a load bank, or both, per the spec) while readings are taken at interval. The load bank disciplines from periodic testing apply here without change.
- Functional and safety checks. Controls, alarms, shutdowns, and the transfer equipment get exercised per the procedure, and every anomaly is written down with its time.
- Retransfer and cooldown. The load returns to the normal source, the unit cools down and shuts down clean, and the system goes back to automatic, ready in principle for its first real outage.
Plan the witness first
Acceptance vs. commissioning vs. routine testing
Commissioning
Commissioning is the project-level practice: a process, often led by a commissioning agent, that verifies design intent across building systems and produces its own documentation. On projects with formal commissioning, the generator's acceptance test tends to happen inside that process, but the two are governed by different documents, and passing one does not by itself discharge the other.
Acceptance testing
The emergency-power standard's own proving test for the completed system, described above. It is a gate: before it passes, the system is not in service.
Routine and periodic testing
Everything after. Once the system enters service, the life-cycle testing regime begins: routine inspection, operational tests on their cadence, periodic load testing. The acceptance record is the baseline those later results get compared against, which is one more reason it needs to be thorough.
Why service shops should care about a contractor's milestone
Acceptance testing looks like the installing contractor's problem, and mostly it is. But for a service shop it is also the single best moment to enter a unit's life:
- The acceptance record is the first entry in the unit's permanent history. The shop that produces a clean one is holding the baseline data (nameplate, transfer times, readings at load) that every future PM and test refers back to.
- The owner is standing right there, watching their new system get proven, thinking for the first time about who maintains it. A well-run acceptance test sells the maintenance agreement without a pitch.
- Deficiencies surfaced at acceptance become the first corrective-work quotes: scoped, documented, and attached to evidence the owner watched get collected.
The free load bank test log at the end of this page (printable PDF and Excel) covers the sustained-run portion: planned profile, readings at interval, observations, and sign-offs, including a line for the witness.
Where PowerOps fits
PowerOps is built for exactly what the acceptance test starts: a per-unit, append-only history. The acceptance results — who ran it, who witnessed it, transfer times, readings, deficiencies — become the unit's baseline record, attributed and server-timestamped, and every later PM, load bank, and repair stacks on top of it. Years later, when an inspector asks how the system performed on day one, the answer is on file instead of in a binder nobody can find.