7.4 EVACS, Elevator & Special Function Tests

7.4 EVACS, Elevator & Special Function Tests

Quick Answer: Special functions are why buildings evacuate, speak, recall elevators, stop fans, and release agents. Periodic ITM must prove building outputs, not only FACU LEDs. Test EVACS messages and intelligibility concepts, firefighter telephones, elevator Phase I recall (and related interfaces per plan), HVAC shutdown, and releasing/emergency control functions on Chapter 14 schedules—commonly annual functional patterns—using the sequence of operation and multi-trade coordination.

If Section 7.2 was device-centric and Section 7.3 was sprinkler-centric, this section is cause-and-effect centric. Level II technicians who only “test smokes and pulls” leave the highest-risk interfaces unverified.

EVACS — Voice Messaging and Intelligibility Rechecks

Emergency Voice/Alarm Communications Systems (EVACS) notify occupants with voice instructions, not only Temporal-3 horns. Periodic testing concepts include:

Circuit and appliance operation

• Operate speaker circuits so messages play on the correct floors/zones
• Verify amplifier/backup amplifier behavior as designed
• Confirm message content and routing match the approved sequence (evacuation vs relocation vs stay-in-place instructions where used)
• Check for shorts, grounds, and supervision on speaker circuits after repairs

Intelligibility recheck concepts

At acceptance, voice systems are evaluated for intelligibility—can occupants understand the words in the acoustical environment? Over years, furniture layouts, finishes, damaged speakers, failed amps, and “temporary” volume changes degrade performance.

Periodic ITM should include recheck concepts appropriate to the system and Chapter 14/design program:

• Listen/verify message clarity in representative spaces (and formal measurements where the program/AHJ requires STI/CIS or equivalent methods)
• Investigate occupant complaints of unintelligible messages as life-safety defects, not audio preferences
• Do not “solve” complaints by arbitrarily lowering volume below design without analysis—whispered instructions fail in fire

Trap: Marking EVACS “tested” because a chime pre-alert tone was heard in the FACU room while remote floors remained silent on failed circuits.

Common frequency pattern: Voice/notification system functional tests often ride the annual notification appliance/control function rhythms—confirm tables and the owner’s EVACS ITM plan for intelligibility sampling.

Firefighter Telephone (Two-Way Communications) Tests

Many high-rises and special buildings provide firefighter telephone systems: handsets and jacks so incident commanders can talk between the fire command center and remote locations.

Periodic functional concepts

1. Inspect handsets, cords, jacks, cabinets, and labels.
2. Plug in at representative (or required percentage/all) telephone jacks and establish communication with the control console.
3. Verify audio quality, correct circuit selection, and trouble supervision for opens/removals where designed.
4. Repair dead jacks, broken handsets, and mislabeled locations—firefighters will not debug your as-builts during a fire.
5. Document which jacks were tested and results.

Exam angle: Two-way firefighter telephone testing is not satisfied by one-way EVACS speaker tests. Different system, different method.

Elevator Phase I Recall — Functional Test

Chapter 6 explained Phase I (recall) vs Phase II (in-car firefighter operation). Periodic ITM of the fire-alarm side of the interface focuses on proving detection/control outputs still cause correct elevator behavior.

What “functional” means here

1. Coordinate with the elevator contractor and building management—cars will move; entrapment and service interruptions are real risks without a plan.
2. Initiate the designed recall input (for example, elevator lobby smoke test method, machine room smoke, or manual recall key/switch as the test plan specifies).
3. Observe actual car movement to the designated level (doors open behavior per elevator code/FEO), not only a relay LED in a fire-alarm can.
4. Test alternate/secondary recall level logic when the designated level detector/input is the one in alarm (primary vs alternate paths from Chapter 6).
5. Verify hat indicators/flashing fire helmet signals where provided by design.
6. Reset detection and restore elevators to normal service only through the proper elevator/fire-alarm reset sequence—do not leave cars trapped in Phase I after you leave the site.
7. Document which elevator groups, which initiating devices, and primary vs alternate results.

Shunt trip note: If shunt trip heat detection is part of the installation (machine room/hoistway protection concepts from Section 6.2), its periodic testing is a separate, high-hazard procedure requiring elevator/electrical coordination—never casually energize shunt trip on a live elevator without the right people and locks/tags.

Common frequency pattern: Elevator recall interface tests are commonly taught on an annual functional cadence—confirm Chapter 14 emergency control function rows.

Trap: “Panel showed elevator recall output active” without watching cars. Outputs can be wired to the wrong bank, wrong floor, or an open circuit at the elevator controller.

HVAC Shutdown Tests

Duct smoke detectors and associated control functions exist to stop smoke distribution.

Periodic method concepts

1. Identify each AHU/RTU and its duct detector or shutdown interface from as-builts and the sequence of operation.
2. Coordinate with facilities so shutdown will not damage equipment or violate critical environmental needs (data centers, labs) without a plan.
3. Functionally test the detector with a listed method appropriate to duct detectors.
4. Verify the correct unit stops (or dampers operate) per design—watch the mechanical equipment, not only the FACU point.
5. Confirm supervisory/alarm signal types match design (duct detectors may alarm or cause supervisory depending on programming/codes/design—follow the approved matrix).
6. Restore the detector and restart equipment through the proper reset sequence; ensure fans do not remain off indefinitely after a “successful” test without owner awareness.
7. Document unit IDs, results, and any devices that shut down the wrong equipment (classic miswire/misprogram finding).

Common frequency pattern: HVAC shutdown / duct detector functional tests often fall on annual rhythms with other initiating/interface tests—confirm tables.

Releasing Service Interfaces

Releasing systems (pre-action, deluge, clean agent, some special hazards) use fire-alarm control energy to operate solenoids or releasing modules. Periodic testing is essential and dangerous if done casually.

Safety-first periodic concepts

• Follow manufacturer and design test without dump procedures when available (abort, disconnect solenoids with listed supervision maintained as required, use test switches designed for the system).
• Never “just energize the release circuit” on a charged clean-agent system to see what happens.
• Verify detection matrix, release countdown/abort, mechanical ventilation interlocks, and door-closing as applicable without unintended agent or water release.
• After any maintenance that breaks releasing circuits, ensure circuits are restored and supervised before leaving—open release circuits can be catastrophic impairments.
• Secondary power for releasing systems often has enhanced duration expectations (installation chapters taught 24 h + 15 min style concepts vs general 24 h + 5 min)—periodic power tests should respect the system type.

Other Emergency Control Functions

The sequence of operation may also require periodic proof of:

• Smoke control / stair pressurization start signals
• Door unlock/release for egress
• Magnetic door holder release on alarm
• Elevator hoistway vent controls where fire-alarm initiated
• Shutdown of hazardous processes or fuel sources when designed
• Notification to mass-notification or networked systems

Test plan rule: every output row in the matrix that is required for life safety should appear in periodic ITM at the interval the tables and AHJ/owner program require—not only the initiating devices that are easy to reach.

Coordination, Impairments, and Occupied Buildings

Special function tests create real operational impacts:

Use impairment procedures (Chapter 8) when functions must be disabled for repair. Retest after restoration.

Documentation and Retest

For each special function:

• Cite the sequence-of-operation row tested
• Record initiating device or control switch used
• Record observed building result (car floor, fan status, message heard on floor X, phone audio OK)
• Record failures, corrections, and retest of the affected function
• Update drawings if jack numbers, AHU tags, or elevator group wiring changed

Practical Multi-Function Annual Scenario

Building: 12-story office with EVACS, firefighter phones, two elevator banks, duct detectors on four AHUs, and a pre-action computer room.

Level II-led plan sketch:

1. Morning: FACU/power/battery checks; place monitoring on test with supervising station.
2. EVACS: play evacuation message floor-by-floor; note weak floors for intelligibility follow-up; test firefighter phones on odd floors this year / even floors next if a documented sampling plan is allowed—otherwise meet the full requirement.
3. Midday: elevator contractor on site; primary and alternate Phase I tests both banks.
4. Afternoon: duct detector tests with facilities; confirm each AHU stops.
5. Late day: pre-action vendor performs releasing interface test with solenoids safed per procedure; restore all circuits.
6. Close: restore monitoring, deliver deficiency list, schedule repairs and retests, file report.

That is periodic ITM at Level II depth—not a five-minute “panel silence check.”

Exam Focus

Special-function stems punish LED-only thinking. Prefer answers that require observed elevator movement, correct AHU shutdown, voice on the right floors, phone talk paths, and safe releasing procedures. Frequency answers again go to Chapter 14 tables (often annual functional patterns for these emergency control functions). Link failures to correction + retest, and remember Phase I recall testing is not the same as Phase II in-car operation testing owned primarily by elevator service.