14.3 Protected Premises vs Supervising Station Roles

14.3 Protected Premises vs Supervising Station Roles

Quick Answer: The protected premises fire alarm control unit (FACU) detects, annunciates, notifies occupants, and controls building fire-safety functions. The supervising station receives transmitted alarm, supervisory, and trouble signals and processes/retransmits them (for example, to the fire department) under Chapter 26 service rules. Level II techs install and verify communicator modules and shared premises path equipment that bridge those roles—without confusing local horns with retransmission or mixing signal types.

Sections 14.1–14.2 covered service types and path performance. This section is the responsibility map used on sequence-of-operation matrices, risers, and field wiring.

Two Control Domains, One Life-Safety Outcome

Think in swim lanes:

Exam trap: “The supervising station will sound the building horns.” No—the premises system sounds horns. The station may call the fire department or owner; it does not replace NAC design.

Opposite trap: “If the station got the signal, elevator recall must have happened.” Not necessarily—recall is a premises emergency control function. Transmission and control outputs are related by SOO design, but they are different mechanisms.

What the FACU Does Locally

At the protected premises, the FACU (and associated power supplies, modules, and appliances):

1. Monitors initiating devices and modules (SLC/IDC)
2. Annunciates alarm, supervisory, and trouble locally (panel LEDs/LCD, remote annunciators)
3. Activates notification appliance circuits and voice messages
4. Executes emergency control functions (elevator recall, HVAC shutdown, door release, suppression releasing interfaces—as designed)
5. Supervises premises wiring and power (ground fault, open, battery, charger, etc.)
6. Hands off selected events to the communicator for off-premises transmission

Level II installation work lives mostly in this lane: devices, pathways, interfaces, programming under design, acceptance testing of local functions (Ch 2–6).

What the Supervising Station Does

The supervising station (central, remote, or proprietary):

1. Receives signals from many premises (or from the owner’s portfolio)
2. Displays/logs account, signal type, and time
3. Follows procedures for alarm, supervisory, and trouble handling
4. Retransmits fire alarm signals to the public fire service when that is the service model
5. Notifies designated premises contacts per run cards/contracts
6. Supports runner/response elements when the service type includes them (14.1)
7. Monitors communications path health from the station side

Level II techs rarely staff the station, but they create the signals the station trusts. Bad point mapping, wrong event codes, or untested paths make the station act on garbage.

Retransmission vs Local Notification

Retransmission means the supervising station (or service) forwards the fire alarm information to the fire department or other emergency forces per procedure. It is a communications/service action.

A system can fail retransmission while local horns work (path/account failure). A system can retransmit successfully while local notification fails (NAC fault). Acceptance testing must exercise both lanes when both are in scope.

Scenario: Waterflow alarm sounds throughout the building and the station receives “Alarm – Waterflow.” The fire department is notified by the station operator. Premises did local notification; station handled retransmission. The Level II tech’s communicator wiring and programming made that chain possible—but the tech did not “become” the fire department.

Alarm vs Supervisory vs Trouble Off-Premises

Sequence of operation and monitoring programming must keep signal classes honest.

Level II programming/wiring discipline:

• Waterflow is typically a fire alarm input for monitoring purposes when it indicates sprinkler activation—confirm project SOO
• Valve tamper is typically supervisory, not alarm
• Loss of phone/cellular/IP path is trouble (comm fail), not alarm
• Do not parallel a tamper and a waterflow onto one undifferentiated “zone 1 alarm” legacy input without design approval—signal discrimination is life-safety information

Exam stem pattern: “Which signal should the supervising station receive when the DACT phone line is cut?” → Trouble (communications failure), not fire alarm.

Level II Tech Work: Communicator Modules and Premises Paths

Under design direction, Level II technicians commonly:

1. Mount listed communicators or enable onboard FACU communicators
2. Land tip/ring pairs, Ethernet, or antenna leads per listing and drawings
3. Provide dedicated jacks/pathways labeled for fire alarm—not random spare pairs
4. Connect trigger inputs (alarm/supervisory/trouble or data bus) per manufacturer wiring diagrams
5. Coordinate account numbers, receiver formats, and test codes with the monitoring entity
6. Verify 90-second alarm delivery and path supervision during acceptance
7. Document as-built path IDs, SIM/ICCID notes (as allowed), antenna locations, and network ports

Wiring and install pitfalls

Shared Premises Equipment Boundaries

Shared premises equipment is hardware at the protected premises that exists primarily to support supervising-station transmission or that is shared between premises and station functions (communicators, premises radio boxes, network interfaces, sometimes shared pathway gear).

Boundary rules Level II should respect:

Scenario: A monitoring vendor swaps a cellular communicator without telling the FA contractor. Point maps change; tampers now report as alarms. Boundary control and change management would have required coordinated retest and SOO update.

Putting It on the Sequence of Operation

A reviewable SOO row set for monitoring might look like:

If the SOO only says “all signals to central station,” rewrite it until classes and actions are explicit.

Coordination With Submittal and Maintenance Chapters

• Ch 10–12: Show communicator on plans/risers; cut sheets; SOO; notes for path type
• Ch 13: Include communicator load in secondary power when premises-powered
• Ch 5 / Ch 7: Test off-premises delivery and path supervision, not only local devices
• Ch 8: Impairments that kill monitoring require tagging, notifications, and often fire watch/AHJ rules when protection is reduced

Exam Focus

Choose answers that:

• Assign local control and notification to the premises FACU
• Assign receipt, processing, and retransmission to the supervising station/service
• Keep alarm / supervisory / trouble categories clean off-premises
• Treat communicator install as Level II pathway/module work with listing and test obligations
• Document shared premises equipment boundaries on drawings

Reject options that make the station sound the building horns, that treat path failure as a fire alarm, or that claim monitoring eliminates the need for a protected premises system. Chapter 14’s layout knowledge closes Domain 2.3’s supervising-station gap so your submittals describe a system that still works when the building is empty at 2 a.m.