5.1 Acceptance Testing & Commissioning Sequence

5.1 Acceptance Testing & Commissioning Sequence

Quick Answer: Commissioning proves the installed fire alarm system matches the approved design and works end-to-end. Use a pre-test checklist, verify circuits and devices progressively as areas become ready, then perform final acceptance testing—typically 100% of devices and required functions for new systems—document results, and correct defects before AHJ witness and owner turnover. NFPA 72 Chapter 14 treats acceptance of new/modified work differently from periodic ITM of systems already in service.

Installation domain 2.1.4 is where rough-in, programming, and interfaces become a documented, code-compliant system. At NICET Fire Alarm Systems Level II you are expected to participate in commissioning under limited supervision: prepare the system, run tests methodically, recognize failures, and leave records that support the Record of Completion and AHJ approval.

Acceptance vs Periodic Testing (NFPA 72 Chapter 14)

Chapter 14 organizes inspection, testing, and maintenance. Two buckets matter constantly on the exam and in the field:

Exam trap: Treating a brand-new install like a five-year periodic sample test. Acceptance is not “test a few devices and call it good.” New work is verified comprehensively so defects are found before the building depends on the system. Periodic testing later uses defined intervals and methods for ongoing assurance—not as a substitute for never having fully accepted the install.

Reacceptance concepts also appear when significant changes are made after original acceptance: added circuits, replaced control equipment, major reprogramming, or substantial device additions may require retesting of affected portions (and related documentation updates), not only a casual “it still sounds.”

Pre-Test Checklist (Before You Call Anyone)

Do not schedule the fire marshal or owner walkthrough until the system is actually ready. A Level II pre-test mindset includes:

Documentation readiness

• Approved shop drawings (or controlled field markups destined for as-builts) available on site
• Sequence of operation / cause-and-effect matrix matching intended programming
• Battery calculations and voltage-drop calculations reflecting as-built loads and cable lengths (or a clear plan to finalize them from measured loads before sign-off)
• Product cut sheets and listing data for installed equipment
• Programming point lists, zone maps, and software/revision identifiers

Hardware and circuit readiness

• FACU, power supplies, and boosters energized on the correct dedicated circuits with proper grounding/bonding as designed
• All field devices installed, addressed (if addressable), and free of construction dust bags where final testing will occur
• SLC, IDC, NAC, speaker, and network pathways continuous with intended supervision (EOL devices installed where required; no permanent temporary jumpers)
• Primary AC and secondary (battery) power present; batteries installed, connected, and of the calculated capacity type
• Initiating, notification, and interface circuits free of unexplained troubles, grounds, and opens

Building and interface readiness

• Elevator contractor available or elevator interface pre-verified with temporary safety controls understood
• HVAC ready for duct detector and shutdown tests without damaging equipment or violating owner operating constraints
• Sprinkler system charged where waterflow/tamper tests require water movement or valve operation under controlled conditions
• Supervising station account active (or local-only tests planned if monitoring is intentionally delayed—never assume “monitor later” if code/occupancy requires it at acceptance)
• Impairment tags, fire watches, and occupant notifications arranged when testing will create alarms or take systems offline in occupied buildings

Progressive Testing During Install vs Final Acceptance

Smart crews test progressively so final acceptance is confirmation, not first discovery of hundreds of defects.

Progressive (in-process) testing

As floors or areas finish:

1. Pathway continuity and supervision — Confirm Class A/B/X (or other specified class) behavior at a basic level: opens report trouble; return paths exist where required; isolators segment as designed.
2. Device presence and address mapping — Walk the floor plan against the panel point list; fix double addresses, missing devices, and wrong room labels early.
3. Local device function — Smoke entries, pull stations, and notification appliances exercise in limited areas after dust control allows.
4. Partial interface dry-runs — Where safe, verify module wiring polarity and coil operation before full building recall/shutdown tests.

Progressive testing reduces punch-list chaos, but it does not replace final acceptance. Labels change, software is revised, and late trades damage devices. Final acceptance re-proves the complete system in its intended configuration.

Final acceptance testing concepts

For new systems, the working field and exam expectation is comprehensive verification:

• 100% device test concepts — Every required initiating device and notification appliance (and other required devices) is functionally tested as applicable to its type—not a random sample chosen for convenience. Methods follow Chapter 14 and manufacturer instructions (for example, listed aerosol or test magnet for smokes where permitted; actual waterflow for flow switches when that is the acceptance method; measured candela/placement checks against the design where visual verification is part of the inspection).
• Control unit and power supply tests — Primary power failure transfer to secondary, trouble on loss of AC, battery supervision, ground-fault detection where provided, and correct operation under secondary power for required loads.
• Notification performance — Temporal patterns, voice messages/intelligibility checks where EVACS is provided, and appliance operation on the correct circuits.
• Off-premises signaling — Alarm, supervisory, and trouble receipt at the supervising station when the system is required to report.
• Interface and sequence tests — Elevator, HVAC, door release, suppression, and other outputs per the approved sequence of operation (detailed in Section 5.3).

Scenario — progressive vs final: Floor 3 was tested in March; in April the programmer renumbered SLC addresses and the drywall crew painted ten smokes. Final acceptance in May must still prove Floor 3 devices and labels—not rely on the March notebook alone.

AHJ Witness Tests

The authority having jurisdiction (AHJ)—often the fire department or building official—may witness acceptance tests in whole or in part. Level II behavior:

• Schedule only when pre-tests pass and documentation is in hand.
• Walk the test plan: order of devices, who initiates, who watches elevators/HVAC, who calls the supervising station, who silences/resets.
• Failures are normal; correct and retest affected functions. Do not argue the AHJ into accepting a known wrong sequence.
• Record witnessed results for the Record of Completion and project closeout.

The AHJ is verifying life-safety performance and code compliance, not whether your crew is busy. Incomplete programming, missing EOL devices, or “we’ll finish batteries Monday” are reasons to stop the witness test, not to partial-sign a required system.

Programming Download Verification

Modern FACUs are software-driven. Commissioning includes proving the loaded program matches design intent:

1. Confirm the correct project file/revision is in the panel (date, revision ID, checksum or manufacturer equivalent where used).
2. Spot-check critical points: pull station → correct zone/label; duct detector → correct AHU shutdown; elevator lobby smoke → correct recall floor group.
3. Verify password/access levels so only authorized persons can change life-safety logic after turnover.
4. Save and archive the final program with the owner documentation package (see Section 5.2).
5. After any “quick fix” edit during testing, re-verify related cause-and-effect rows—small edits create large side effects.

Trap: Assuming a successful device test means programming is complete. A smoke can alarm locally while elevator recall still points to the wrong floor because the matrix was never fully loaded.

Battery Calculation Verification at Acceptance

Battery calculations are not only a submittal exercise. At acceptance:

• Confirm installed battery capacity (AH) meets or exceeds the approved calculation for required standby plus alarm duration (commonly 24 hours standby plus 5 minutes alarm, or 15 minutes for emergency voice/alarm communications systems where that requirement applies—always per the adopted code, design, and system type).
• Confirm the calculation used as-built device counts and realistic loads (notification appliance current, module loads, network cards), including the required aging factor (commonly 20% additional capacity in standard sizing practice for secondary supplies).
• Verify charger operation and that batteries are listed for the application and connected with correct polarity and supervision.
• If field adds increased NAC load or device count after original calcs, revise calcs before sign-off; do not accept undersized batteries because “the old PDF is still in the submittal.”

Voltage-drop calculations for NACs/speaker circuits likewise should reflect final cable lengths and loads so appliances still operate above minimum listed voltage at the end of line under alarm.

Recommended Commissioning Sequence (Field Order)

Use this order as a default mental model (project procedures may refine it):

1. Visual inspection against drawings (device type, location, mounting, clearances)
2. Power supply and battery checks; AC fail / secondary operation
3. Circuit integrity and supervision (opens, grounds, class performance samples)
4. Initiating device functional tests (100% concept for new work)
5. Notification appliance and EVACS tests
6. Interface and sequence-of-operation matrix tests
7. Supervising station receipt tests
8. Final programming archive, documentation package, owner training handoff
9. AHJ witness of required demonstrations
10. Close residual punch items and update as-builts

Exam Focus

When a stem mixes “new install,” “sample testing,” and “annual inspection,” choose answers that apply acceptance-level completeness to new work, Chapter 14 periodic rules to in-service systems, and a readiness checklist + retest after repairs mindset for AHJ day. Programming revision control and battery capacity against as-built loads are part of commissioning, not optional paperwork.