17.1 Acceptance Testing and Commissioning

The New York Department of State Security or Fire Alarm Installer written exam treats testing as a field skill, not a paperwork afterthought. Module 5.II of the 81-hour qualifying course is Testing and Troubleshooting (7 hours). Troubleshooting methods are Chapter 18; this chapter is acceptance testing, periodic inspection, testing, and maintenance (ITM) frequencies, and records. Module 5.V also lists maintenance, inspection, and false-alarm reporting; false-alarm detail is Chapter 19.

The New York Uniform Fire Prevention and Building Code (Uniform Code) points to NFPA 72, National Fire Alarm and Signaling Code, for fire alarm systems. The exam bulletin describes code questions as based on the Uniform Code and NFPA standards. This Independent OpenExamPrep section teaches commonly taught NFPA 72 Chapter 14 ITM concepts used in installer courses. It does not reprint copyrighted NFPA tables, and it does not invent New York-only test intervals. The authority having jurisdiction (AHJ) and the adopted edition control the exact table row.

Why acceptance testing exists

A system that looks finished can still have reversed polarity on a notification appliance circuit (NAC), a silent strobe circuit, a communicator that never registered on the account, or an elevator-recall relay that was never landed. Acceptance testing (often called commissioning in the field) is the witnessed proof that the installed system performs the approved sequence of operation before occupants, insurers, and the fire department rely on it.

NFPA 72 also distinguishes reacceptance after a modification from first-time acceptance. If you add devices, change software, or retarget monitoring, you test what changed and enough of the surrounding system to prove supervision, programming, and interfaces still work. You do not treat a four-device add as an excuse to skip a live monitoring test if the communicator or account was touched.

One hundred percent — the rule of thumb for new systems

Commonly taught NFPA 72 Chapter 14 practice for a new fire alarm system is a 100 percent functional test: every initiating device, every notification appliance, every emergency-control function, and the off-premises signals the design documents require. Sampling belongs to some periodic ITM or limited reacceptance situations, not to first occupancy of a new building system.

If the job added 40 smoke detectors, 12 manual stations, 80 strobes, and elevator recall, the acceptance test exercises all of them with a listed method. A green fire alarm control unit (FACU) LED is not a substitute for device-by-device proof.

Passing a pretest is not occupancy. Deficiencies found at acceptance go on a punch list, get corrected with listed compatible parts, and get retested. Partial function is still a deficiency: a speaker that plays the wrong message, a strobe that flashes at the wrong candela, or a duct detector that trips a fan but never reports at the FACU has not passed.

Commissioning workflow (commonly taught field sequence)

1. Notify the supervising station, occupants, and the AHJ or fire department as required so test signals are not treated as emergencies.
2. Place the system in test (or equivalent) status and tag impairments. Dispatch handling and false-alarm reporting are Chapter 19; the testing point is: do not create an avoidable response.
3. Compare the installation to the approved drawings: device locations, addresses, candela ratings, circuit class, and power supplies.
4. Verify primary power, disconnect it, and confirm secondary power actually carries the system. Battery calculations were Chapter 9; at acceptance you prove the installed batteries and charger work under load.
5. Functionally test 100 percent of initiating devices with a listed method (listed aerosol for smokes, listed heat source for restorable heats, mechanical operation for manual stations, actual or listed simulated flow for waterflow).
6. Operate NACs — audible and visible — and confirm temporal pattern and visible coverage against the design documents.
7. Prove emergency control functions (elevator recall, HVAC shutdown, door release, suppression release) at the interface. Application detail is Chapter 15; acceptance still requires the interface to operate.
8. Perform a live central-station or remote-station account test: alarm, supervisory, trouble, and restore as the account is programmed — not merely a communicator LED.
9. Complete the Record of Completion, deliver as-built (record) drawings, manuals, and site-specific software documentation.
10. Demonstrate the system to the AHJ, including any local fire-marshal inspection required under General Business Law (GBL) §69-z.
11. Restore the system, remove test mode, notify monitoring that the system is in service, and leave completion documents at the FACU or other approved location.

GBL §69-z and the local fire marshal

GBL §69-z is the applicability section of Article 6-D. Two exam-tested ideas sit in it.

First, the statewide installer license does not wipe out local inspection of fire alarms. Local law governs inspection of fire alarms by a fire marshal or any other person designated under such local law. A Department of State license lets a firm engage in the business of installing, servicing, or maintaining systems; it is not a substitute for the municipal fire-alarm inspection, permit, or witnessing process the AHJ uses.

Second, except for the New York City home-improvement-contractor authority preserved in §69-z(1), local governments generally may not require a separate fee or license for installing, servicing, or maintaining security or fire alarm systems beyond Article 6-D. Students mix these up: “no local installer license” is not “no local fire-marshal inspection.”

New York City Fire Department Certificates of Fitness are a different credential family from this Department of State exam (Chapter 2). For acceptance day, remember: you may need both the licensed-installer package and the local inspection the fire marshal requires.

Record of Completion and as-builts

Commonly taught NFPA 72 Chapter 7 closeout includes:

• Record of Completion — system type, responsible parties, circuits and pathways, device inventory, power, sequence of operation, interfaces, and test results
• Record (as-built) drawings — what was actually installed, including approved field changes
• Owner’s operating instructions and product manuals
• A copy of site-specific software where the system is software-driven
• A revised Record of Completion after later modifications and programming changes

If a device moved during construction and the as-built still shows the old location, the next ITM technician and the AHJ are working from fiction. That is a documentation failure, not a cosmetic drawing issue. Programming, access codes, bypass, and hours of operation as license-scope terms are Chapter 19; at acceptance, the practical rule is: whatever you programmed, write it down on the completion record and the as-built package.

In practice

You finish a new office system on a Friday. The panel is green, the communicator shows a check-in, and the general contractor wants a certificate of occupancy. The fire marshal, acting under local law as GBL §69-z contemplates, asks for a witnessed 100 percent test and a live alarm to the listed central-station account. The correct path is to schedule that demonstration, complete the Record of Completion, and hand over as-builts — not to argue that a Department of State license already “covers” inspection.

On the exam

Expect items that swap pretest for acceptance, that offer 10 percent sampling on a brand-new system, or that claim a statewide license bars the fire marshal from inspecting. Choose 100 percent for new systems, written completion documents, a live account test, and GBL §69-z local inspection.