5.3 Periodic Testing Workflow

Plan Scope and Notify First

Periodic testing is a Level I task in the NICET outline; at higher levels it becomes a coordination and documentation problem. Start with scope — which devices, circuits, interfaces, notification appliances, control functions, and reporting paths are included, and which are excluded. A wrong answer often reaches outside the scope or ignores a listed exclusion.

Then control communications. Testing can trigger alarms, troubles, supervisory signals, elevator recall, door release, smoke-control sequences, suppression releasing, and off-premises reporting. NFPA 72 and good practice require notifying the supervising/monitoring station and the building's responsible parties before testing begins and again when it ends, and placing affected points out of service so test signals are not dispatched as real emergencies. An answer that notifies the monitoring company only after testing is a classic trap.

Test Methods by Device Type

NFPA 72 prescribes how each function is exercised, not just how often:

• Smoke detectors — functional test by introducing smoke or a listed aerosol/smoke simulant into the sensing chamber to confirm alarm; magnet/test-switch checks alone are not a full functional test. Sensitivity is verified separately against the listed range using a calibrated method or the manufacturer's instrument.
• Heat detectors — restorable fixed-temperature and rate-of-rise units are tested with a heat source; non-restorable (fusible) heat detectors are NOT heat-tested (that destroys them) — they are mechanically/electrically loop-tested and replaced per their listing/expiration.
• Manual fire alarm boxes (pull stations) — operated mechanically per the manufacturer (key/tool reset) to confirm the alarm initiates.
• Waterflow and supervisory devices — flow or valve operation confirms the alarm/supervisory signal and verifies any required time delay.
• Notification appliances — audible output verified for the required pattern (temporal-three for evacuation) and audibility; visible (strobe) appliances verified for operation and synchronization.
• Secondary (standby) power — disconnect primary power and verify the system carries its full standby load for the required period and still produces alarm. Protected-premises systems are sized for 24 hours of standby followed by 5 minutes of alarm; certain supervising-station/emergency-communication arrangements use longer windows (verify the specific application).
• Ground-fault / open-circuit monitoring — introduce a fault on a monitored pathway and confirm the FACU annunciates a trouble signal; restore and confirm the trouble clears.

Think in Loops, Then Restore

For NICET scenarios, think in loops. A pull station is operated, the FACU receives the signal, notification operates per its sequence, and the result is recorded. If the panel does not respond, the loop changes: stop calling it a pass, protect the area per site procedure, troubleshoot or replace within authority, retest, and document the final condition.

A practical execution list:

1. Confirm device identity before operating it.
2. Confirm the expected response before judging the result.
3. Tie notes to device labels, locations, and circuit/point IDs.
4. Do not mark a device passed because a nearby device worked.
5. Retest after any correction that affects the tested function.
6. Return disabled points, bypasses, and service modes to normal before closeout.

Time and Trap Management

Level I has 85 questions in 110 minutes; Level II has 110 questions in 155 minutes — do not overbuild a scenario. Identify scope, notification, test result, correction, restoration, and record, then pick the answer that completes the current step. The most common traps are (1) marking a deficiency corrected with no retest and (2) deferring monitoring-station notification until after the test.

Verifying Notification Output

A functional test is not finished when the initiating device alarms — the output must be verified too. For audible appliances, confirm the evacuation signal sounds the temporal-three pattern (three half-second pulses, then a pause, repeated) where general evacuation is intended, and that audibility meets the design (public mode generally requires audibility at least 15 dBA above average ambient sound or 5 dBA above the maximum 60-second sound level).

For visible appliances, confirm strobes operate and that synchronization holds where multiple strobes are visible from one location, because unsynchronized strobes can trigger photosensitive reactions. NICET frames these as "did the system actually notify" questions, so an answer that confirms only the panel signal and ignores the appliance output is incomplete.

Off-Premises and Interface Verification

Where the system reports to a supervising station, the periodic test must confirm the alarm, supervisory, and trouble signals are received and correctly identified at the receiving end — not just generated at the FACU. This is exactly why pre-test notification matters: the station must be expecting test signals so it neither dispatches responders nor records a genuine event.

Interface functions — elevator recall (Phase I), elevator shunt trip, HVAC/smoke-control shutdown or activation, magnetic door holders releasing on alarm, and suppression releasing circuits — each have an expected sequence of operations that the test must reproduce and the technician must verify against the approved sequence-of-operations matrix.

A Realistic Test Run

Picture an annual visit: the technician pulls the device list and sequence matrix, calls the supervising station to place the account on test, exercises each device by its intended input, watches the FACU annunciate the correct point, confirms NAC output and interface actions, logs pass/fail per point, retests failures within authority, returns bypassed points to normal, takes the account off test, and signs the Inspection and Testing Form. Skipping the off-test step or the retest turns a passing visit into a documented impairment.