5.3 Functional Verification of Interfaces

5.3 Functional Verification of Interfaces

Quick Answer: Functional verification proves that fire alarm inputs drive the correct building outputs per the approved sequence of operation. Test elevator recall (primary and alternate), HVAC shutdown, waterflow alarms, tamper supervisories, door holders, suppression release/abort paths, and supervising-station receipt of alarm, supervisory, and trouble. Use a cause-and-effect matrix so every required row is demonstrated and documented—not assumed.

Devices that alarm at the FACU but fail to recall elevators, shut fans, or reach the supervising station are incomplete systems. Level II commissioning spends heavy time on interfaces—the wired and programmed bridges between fire alarm and other building systems. (Design details of elevator and HVAC rules deepen in Chapter 6; this section focuses on how you verify them at acceptance.)

Matrix / Cause-and-Effect Testing

Most projects document interfaces in a sequence of operation table (matrix):

• Rows: initiating or system events (manual pull, smoke detector, waterflow, tamper, duct smoke, abort switch, AC fail, etc.)
• Columns: outputs (general notification, selective voice page, elevator primary recall, alternate recall, AHU shutdown, door release, releasing circuit, supervisory LED, off-premises alarm/supervisory/trouble)

Method:

1. Place the system in a controlled test mode with occupant and trade notifications as required.
2. Initiate one input at a time (or the minimum combination the design requires for that function).
3. Observe every required output for that row—on-premises and off-premises.
4. Reset fully before the next row so latched outputs do not falsify results.
5. Record pass/fail, time, witnesses, and corrective actions.
6. After programming fixes, retest the row and any related rows that share logic.

Exam trap: “Panel showed alarm” ≠ “interface passed.” Always ask what the building did.

Elevator Recall — Primary and Alternate

Elevator Phase I Emergency Recall Operation is a classic acceptance item where fire alarm interfaces with elevator control.

What to verify (functional concepts)

• Primary recall: Initiation from the designated lobby/detector group causes cars to return nonstop to the primary designated level (often the lobby level serving the main exit level—as designed and elevator code coordinated).
• Alternate recall: When the initiating condition is at the primary level (for example, smoke detection at the primary recall floor lobby), cars recall to the alternate designated level so passengers are not discharged into the fire floor.
• In-car firefighter Phase II features are elevator-system functions; fire alarm testing coordinates so recall signals are correct and elevator personnel can complete their portions safely.
• Visual/pilot indicators and related signals operate per the approved design where provided.

Commissioning tips

• Schedule the elevator contractor for joint testing; do not jump elevator safety circuits to force motion.
• Confirm which detectors/modules feed primary vs alternate inputs—swapped wires are a frequent defect.
• Retest after any FACU program change affecting elevator points.
• Document car numbers, designated levels, and which initiating devices were used.

Scenario: Lobby smoke correctly lights an FACU elevator LED, but the elevator controller input was landed on the alternate terminal only. Cars always go to Floor 2. Matrix testing that watches car destination, not only the LED, catches the defect.

HVAC Shutdown & Duct Smoke

Duct smoke detectors and related fire alarm outputs protect against smoke spread through air-handling systems.

Verification points

• Correct AHU (or fan) shuts down—or other listed control action occurs—per matrix (shutdown is common; some designs use dedicated smoke control sequences).
• Signal type matches design: many duct detectors are arranged to cause supervisory conditions with equipment shutdown, while others are part of alarm strategies—follow the approved sequence, not a generic habit.
• Shutdown wiring is supervised or arranged per listing/design so faults do not silently disable the interface.
• Access to the detector remains possible after ceilings close; sampling tubes oriented correctly (order of operations with HVAC trade).

Coordinate with building engineers: unexpected shutdowns can damage processes or strand occupants in special environments. Test during agreed windows.

Waterflow → Alarm and Tamper → Supervisory

Sprinkler monitoring is among the most tested interface pairs.

Waterflow

• Operate the flow switch by actual waterflow method required for the test (inspector’s test connection or approved equivalent), not only a dry electrical short of the switch leads if the acceptance goal is to prove the mechanical switch and retard timing.
• FACU receives alarm (not merely supervisory) when that is the design/code expectation for waterflow.
• Notification appliances and off-premises alarm transmission follow the matrix.
• Retard time (if used) prevents nuisance alarms from pressure surges yet still initiates within required limits—verify behavior is intentional, not stuck open.

Tamper (control valve supervisory)

• Move the supervised valve toward closed per test method; FACU shows supervisory.
• Off-premises supervisory is received when monitoring is required.
• Restoring the valve clears supervisory after reset/restore logic as designed.
• Do not accept a tamper that triggers full occupant evacuation notification unless the design explicitly requires that unusual behavior.

Swapping waterflow and tamper wiring or programming is a high-frequency acceptance failure: the building either evacuates for a closed valve or fails to evacuate for a flowing sprinkler system.

Door Holders and Magnetic Release

Smoke/fire doors held open on magnets typically release on alarm (and often on power loss—fail-safe behavior):

• Initiate the correct alarm zone or general alarm per design.
• Confirm doors close fully and latch; note hang-up from carpet, air pressure, or misaligned hardware (a door hardware issue still fails the life-safety outcome).
• Confirm circuits are arranged so a fault or power loss does not leave doors improperly held open when release is required.
• Retest a sample of doors on secondary power if the design depends on release timing during AC fail scenarios.

Suppression Release and Abort

Special hazard releasing systems (clean agent, pre-action, deluge interfaces, kitchen hoods as applicable) demand careful functional checks:

Release path

• Verify the fire alarm or releasing panel logic arms only under the required detection combination (single vs cross-zone as designed).
• Confirm solenoids/actuators operate in a safe test mode (agent cylinders locked out, abort active, or mechanical isolation per manufacturer and owner safety rules). Never dump agent for a casual demo.
• Time delays and predischarge notification (horns/strobes/voice) operate per matrix before release impulse.

Abort path

• Operate abort stations during a simulated release sequence; confirm release is interrupted or delayed per listing and design.
• Confirm abort does not silently disable detection supervision.
• Document that abort devices are accessible and correctly identified.

Safety note: Coordinate with suppression specialists. Level II fire alarm techs verify the electrical/sequence interface; agent cylinder work follows manufacturer and specialty procedures.

Supervising Station Receipt: Alarm, Supervisory, Trouble

Protected premises systems that report off-premises must prove the path:

1. Alarm receipt at the supervising station (correct account, reasonably correct zone/point text).
2. Supervisory receipt distinguishable from alarm.
3. Trouble receipt (for example, AC fail or open circuit) distinguishable from alarm/supervisory.
4. Timeliness consistent with applicable transmission requirements (designers and Chapter 26 concepts address path performance; at commissioning you verify real messages arrive).
5. Restore and reset so the station sees clear/restore where the service requires it.

Call the supervising station before testing; use test mode or running tests per their procedures to avoid unnecessary emergency dispatch. After testing, ensure the account is returned to active service—not left in test forever.

Scenario: Local horns work, but the communicator SIM failed and no alarm reached the station. Occupant warning without monitoring may be incomplete for the required system type. Matrix testing includes the off-premises column.

Putting Interfaces on the Acceptance Schedule

Suggested order within the interface block:

1. Supervisory and trouble paths (lower disruption) after basic panel health
2. Door release zones
3. HVAC shutdowns (engineering window)
4. Waterflow/tamper with sprinkler contractor
5. Elevator recall with elevator contractor
6. Suppression sequences in safe mode with specialty tech
7. Full off-premises alarm demonstration near the end when other results are clean

Failures trigger repair + retest of the failed matrix row and any dependent rows. Update the Record of Completion and sequence documents when logic changes.

Exam Focus

Stems that say a device “worked” but elevators, fans, valves, doors, agent release, or the supervising station misbehaved are interface failures. Choose answers that test end-to-end outputs, distinguish alarm vs supervisory, include primary and alternate recall, and document matrix results—not FACU LEDs alone.