Fire Alarm Interfaces: Elevator Recall, Doors, HVAC

This article builds the mental model. The exam itself, its domains and its reference list are in the I&T Level II guide, which this piece supports. For a longer runway on the rest of Level II, see the Fire Alarm Systems Level II 60-day plan.

What an interface is

The fire alarm control unit does two jobs: it detects and reports, and it commands. An interface is the command side. When an initiating device activates, the control unit follows its programmed sequence and sends an output to another system, usually through a relay, a module or a network connection.

Four interface types come up most often:

• Elevator recall. An alarm sends the cars to a designated landing so firefighters control them and passengers are not carried to a floor in trouble. The fire alarm side signals the elevator controller, and the elevator side decides how the cars respond.
• Door release. Doors held open by magnetic holders drop closed when the alarm system removes power or signals release. Others unlock to allow exit. Same pattern: the alarm gives the command and the door hardware acts.
• HVAC shutdown. Air handlers and fans stop or change mode so smoke does not spread through ductwork. A duct detector or a panel output signals the equipment (see duct smoke detectors explained). Smoke control is a related but separate design, where fans run on purpose to manage smoke, and it is covered by a different reference.
• Suppression release. A releasing system starts discharge, and the fire alarm reports its status or receives its signals.

The pattern is always the same: initiating action, panel logic, output, connected equipment response, and restoration.

Who owns what at an acceptance or periodic test

Interfaces are where responsibilities cross. The fire alarm technician owns the alarm system's output, meaning the panel programming, the relay or module and the wiring to the connection point. The elevator contractor, the HVAC controls contractor, the door hardware installer or the suppression contractor owns the other side.

A clean test depends on settling this before anyone touches a device:

• Who operates the connected system? The alarm tech does not run elevators or reset suppression equipment.
• Who is present? For recall, the elevator contractor is typically on site to confirm cars respond. The building owner's representative should know the building is about to be tested.
• Who restores? Every disabled function needs a named person and a check that it is back in service.

Add a coordination step with the monitoring station and the people in the building, as the testing and maintenance guide describes. The exam asks about this ownership logic as much as it asks about wiring.

Trace the signal from input to output

When you see an interface question, or plan a real test, trace the path in six steps. Write them in plain words:

1. Initiating action. What activates: a lobby detector, a duct detector, a waterflow switch, a manual station?
2. Panel response. What does the programmed sequence say should happen, and on which output?
3. Output device. Which relay, module or circuit carries the command?
4. Connected equipment. What receives it, and what is its expected response?
5. Observation. What do you see, hear or read that proves the response happened?
6. Restoration. What is reset, re-enabled or returned to normal, and who confirms it?

Use an invented example to practice. A detector in an elevator lobby on the third floor activates. The sequence of operations calls for an output at the recall module. The module signals the elevator controller. Cars should return to the designated landing. You observe the cars and the indicator, record the result, then restore the panel and confirm the elevator contractor has returned the cars to normal service. Every step has a person and a record.

Now change one fact: the lobby detector is on the designated landing itself. That can send the cars to a different landing, which is why the sequence of operations matters more than memory. Read it, then predict the response.

What to document

A good interface record separates four things:

• The plan: scope, sequence of operations, participants and access needs.
• The inspection: what you found installed, labeled and connected.
• The functional result: the stimulus applied, and the response observed.
• The restoration: what was disabled, what was re-enabled and who confirmed it.

Finding a connection is not the same as showing it works, so keep inspection evidence and functional evidence in separate lines. If part of the interface could not be tested because the other trade was unavailable, say so and list it as open.

Where I&T Level II tests this

The interface and specialty equipment domains of Level II cover elevators, smoke control, suppression interfaces, emergency communications and networked controls. The functional testing domain is the heaviest. Expect to choose the right reference, identify who is responsible and sequence a test.

For code navigation, start with NFPA 72 Chapter 21 for emergency control function interfaces, then confirm the applicable section for the connected system in your own copy. Smoke control also involves NFPA 92. The on-screen reference guide has a routine for moving between references.

The common miss is elevator behavior. Elevator recall and shutdown rules come partly from ASME A17.1, which is not on NICET's I&T reference list. The fire alarm references cover the alarm side, so study the alarm interface next to the documented elevator sequence and settle who is responsible for what before you plan a test. The I&T Level II guide links NFPA's committee record on that cross-code relationship.

If you are unsure whether this track fits your work, the I&T vs Fire Alarm Systems comparison explains the difference.

Check whether you can trace a signal

Interface misses are the gap in Level II. Take the free 10-question I&T Level II check to see whether you can trace a signal and name the responsible party. It shows exactly which areas to study first, and it takes no signup. Then drill your weakest interface group one at a time, writing the six-step trace for each.

FAQ

What is elevator recall?

Elevator recall is the fire alarm system sending a signal that returns elevator cars to a designated landing, so passengers are not carried to a hazard and firefighters can take control. The alarm system sends the command, and the elevator controller carries it out.

Who tests the interface?

Both sides take part. The fire alarm technician operates the initiating device and the alarm output, and the other trade confirms its equipment responded. Agree on this before the test, and name who restores each system afterward.

Do interfaces differ by building?

Yes. The sequence of operations, the connected systems and the adopted code edition set what each building needs. Read the sequence for the building in front of you instead of assuming a standard design.

Which NFPA references apply?

NFPA 72 Chapter 21 is the starting point for emergency control function interfaces, and NFPA 92 applies to smoke control. NICET's I&T Level II list provides both on screen. Locate the exact sections in your own copy of the listed edition.