12.3 Reacceptance Testing After Hardware and Software Modifications

12.3 Reacceptance Testing After Hardware and Software Modifications

Core Overview: Acceptance testing happens once. Reacceptance testing happens every time anyone touches the system afterward — and it is where Level III technologists carry direct professional liability. NFPA 72 (2022) Section 14.4.2 defines exactly how much of a modified system must be retested, and the answer is never "just the device I replaced." This section covers the hardware rule, the site-specific software rule, the 10 percent sampling allowance and its 50-device cap, the 2022 remote-programming requirement, and the Record of Completion revision that closes the loop.

---

1. Why Reacceptance Exists

A fire alarm system is a single integrated machine, not a collection of independent devices. Swapping one addressable smoke detector changes the loop's electrical loading. Editing one line of cause-and-effect logic can silently strand an elevator recall output. NFPA 72 therefore treats modified equipment as never having been tested, and requires the modifying contractor to prove the system still performs its approved sequence of operations.

For the NICET Level III candidate this maps directly onto two published work elements — 3.1.3 oversee system commissioning and 3.2.2 resolve impairments/deficiencies — and onto performance measure 0303-5108, which requires the candidate to plan and oversee a complete and successful system commissioning including documentation of test completion.

+-------------------------------------------------------------------------+
|              ACCEPTANCE  vs.  REACCEPTANCE                              |
|                                                                         |
|  ACCEPTANCE (new system)   ===> 100% of devices, 100% of functions      |
|                                 No sampling. No exceptions.            |
|                                                                         |
|  REACCEPTANCE (modified)   ===> Everything changed + everything the     |
|                                 change could affect + a defined sample  |
+-------------------------------------------------------------------------+

---

2. The Hardware Rule (NFPA 72 14.4.2)

When initiating devices, notification appliances, or control equipment are added, replaced, relocated, or removed, the modified equipment is tested as new equipment, and so is everything the change could have affected.

[!IMPORTANT] Adding appliances is an electrical change, not just a device change. Hanging two more horn/strobes on an existing NAC changes total load, end-of-line voltage, and battery standby and alarm demand. Reacceptance for that change includes reworking the voltage-drop and secondary-power calculations, not merely watching the new horns sound.

---

3. The Site-Specific Software Rule and the 10 Percent Sample

Site-specific software is everything the installing technician programs into the panel for this building: device addresses and custom labels, zone assignments, input/output logic, timers, alarm verification settings, notification groups, elevator recall matrices, door release, fan shutdown, and off-premises routing.

When any of that changes, NFPA 72 requires:

1. 100 percent of the functions known to be affected by the change shall be tested.
2. Plus an additional 10 percent of initiating devices that are not directly affected by the change, not to exceed 50 devices.
3. The Record of Completion shall be revised to reflect the change.

Three Misreadings That Fail Candidates

Worked Example: Rezoning a Six-Story Office

A technologist edits the cause-and-effect matrix so that floors 4, 5, and 6 now sound on a common alarm group instead of individually, and adds a duct detector on the fifth floor to shut down AHU-3. The building has 420 initiating devices total.

STEP 1: Functions known to be affected -> test 100%
        - New duct detector: alarm response + AHU-3 shutdown
        - Floors 4, 5, 6 notification grouping (all appliances on those floors)
        - Any annunciator text or off-premises point tied to those zones

STEP 2: Additional sample of UNAFFECTED initiating devices
        10% of 420 = 42 devices
        42 < 50  ->  the cap does not bind; test 42 devices
        Select randomly, at least one per initiating device circuit

STEP 3: Revise the Record of Completion and the as-built drawings

Had the building held 900 initiating devices, 10 percent would be 90 — but the cap limits the additional sample to 50. The affected-function testing in Step 1 is unchanged and uncapped.

---

4. The 2022 Remote Programming Requirement

Off-site programming of control equipment is now routine. The 2022 edition of NFPA 72 responded by clarifying that where programming is performed remotely, a qualified representative must be on-site at the protected premises to perform the reacceptance testing that follows the site-specific software revision. A technician logging in from the office cannot self-certify a remote software change; somebody has to stand in front of the panel and prove the affected functions still operate.

---

5. Sequencing Reacceptance on a Live Building

Reacceptance is performed on an occupied, protected building, which changes the choreography completely compared with new construction.

1. Notify before you touch anything. The supervising station, the building owner or designated representative, and the AHJ where required. A reacceptance test that trips a central-station dispatch is a preventable and expensive error.
2. Place the affected portion on impairment and follow the impairment procedures — tagging, coordinator notification, and fire watch where the impairment exceeds the code threshold.
3. Pre-test your own work before anyone witnesses it. Field-verify the changed devices and functions, then run the affected-function list end to end.
4. Restore and confirm. Return the system to normal, verify no trouble or supervisory conditions remain, and confirm signal receipt with the supervising station before releasing the impairment.
5. Document. Revise the Record of Completion, update the as-builts and the sequence of operations matrix, archive the revised site-specific software to non-volatile media, and issue the test record.

---

6. Realistic Exam Traps

1. "Only the new device needs testing." The most common wrong answer on the exam. The code scope is the modified equipment plus everything the modification could affect.
2. Conflating the three different 10 percent rules. Site-specific software reacceptance sampling, executive (manufacturer) software changes, and the circuit-integrity test method in the testing table each have their own 10 percent framework. They are not interchangeable, and exam distractors deliberately swap them.
3. Forgetting the Record of Completion revision. Reacceptance is not complete when the devices test good; it is complete when the documentation matches the installed system.
4. Treating a battery swap as paperwork-free. Replacing a battery set changes secondary power capacity. The replacement is tested, dated, and recorded.
5. Skipping the supervising station call. Unannounced testing generates a false dispatch, which in many jurisdictions is a fineable offense against the building owner your company works for.