8.1 Commissioning Readiness and Systematic Startup

Commissioning Begins Before the Acceptance Test

NICET places commissioning (often abbreviated Cx) across multiple levels of the Fire Alarm Systems (FAS) outline. Level II installation tasks include performing commissioning, Level III tasks include overseeing commissioning, and Level IV includes managing the commissioning process within installation, planning, and maintenance. Candidates should therefore see commissioning as both hands-on field verification and a managed technical process, not a single test event.

Commissioning is the systematic verification that the installed system performs exactly as the approved documents require. The reference document for that performance is the sequence of operation and its companion cause-and-effect matrix — the table that lists every input (initiating device, zone, supervisory point) against every required output (notification, elevator recall, HVAC/smoke-control action, door release, suppression release, off-premises signal).

NFPA 72 and NFPA 3/4 commissioning practice require that the cause-and-effect matrix be produced, reviewed, approved, and then verified by functional test, with every documented relationship demonstrated at least once.

Confirming Readiness With Evidence

Commissioning readiness starts with one question answered by evidence, not confidence: is the system actually ready to be verified? The team confirms that devices are installed and addressed, terminations are complete, circuits are identified and class-correct, power supplies (primary and secondary) are connected, programming reflects the approved sequence, integration interfaces are coordinated, and known troubles are resolved or formally documented.

Systematic Startup Separates Problem Classes

A disciplined startup separates four problem classes so they are not confused on the witnessed test day: installation defects (loose terminations, wrong wire, missing EOL devices), programming issues (wrong address, wrong zone mapping, missing cause-and-effect logic), power problems (primary loss behavior, battery condition, charger fault), and integration coordination issues (an elevator, damper, or suppression interface that another trade has not made ready).

Battery readiness is part of the same check: the secondary-power calculation must apply the NFPA 72-2022 1.25 derating/safety factor to the computed amp-hours — a value the commissioning technician confirms against the calculation sheet and battery label.

Applied NICET FAS scenario guidance: a Level II item may describe a newly installed wing with several devices still in trouble and a request to schedule acceptance tomorrow. The best answer is to complete systematic checkout first, correct or document deficiencies, verify cause-and-effect, then coordinate readiness before inviting the AHJ or owner.

A Level III version may ask what the lead technician does when separate crews report different startup results — standardize the commissioning checklist, review trouble logs, confirm drawings and programming, assign corrections, and require documented retesting. A Level IV version asks about improving the commissioning process across projects: procedures, training, resource planning, and review checkpoints.

Exam trap: acceptance testing is not the first time the contractor learns whether the system works. If a choice says to save all verification for the AHJ visit, it is usually weak. Build a study order: install, address, power, program, pre-test, correct, document, then coordinate witnessed testing and close out. Real projects overlap, but exam answers reward a logical path that controls risk and communicates clearly.

Pre-Test (Pretest) Versus the Witnessed Acceptance Test

Candidates should hold two distinct ideas apart. The pre-test (sometimes written pretest) is the contractor's own complete dry run: the installing technician operates devices, watches the panel, exercises every cause-and-effect relationship, corrects what fails, and retests until the system is clean. The acceptance test is the later, witnessed event where the AHJ and owner observe a system the contractor already knows works.

NFPA 3 and NFPA 4 frame this larger discipline as integrated testing and commissioning, where the fire alarm is one of several life-safety systems whose interactions are verified together. When the fire alarm must drive an output owned by another system — a damper, a recall, a door release, a suppression release — the commissioning agent confirms not only that the fire alarm sends the command, but that the receiving system performs the physical action and reports back.

Pretesting those handoffs is exactly what prevents an embarrassing, schedule-wrecking failure during the witnessed test.

A second commissioning discipline is baseline capture. Detector sensitivity readings, measured NAC end-of-line voltages, battery voltage and charging current, and ground-fault-free pathway readings recorded at startup become the reference numbers a future technician compares against. A detector reading drifting out of its listed sensitivity window two years later is meaningful only because the commissioning baseline existed.

This is why NICET ties commissioning to the full life of the system: the data gathered at startup is the same data periodic inspection, testing, and maintenance depends on, and it is part of what the owner receives at turnover. Treating commissioning as a one-time hurdle, rather than as the origin of the system's permanent record, is the conceptual mistake the higher-level exam questions are written to catch.