10.3 Central Stations, Signal Types, and Path Supervision

Why the receiver end of the path is a licensing topic

Module 2.III is not finished when the DACT kissoffs. Someone has to observe, record, and dispatch. Independent OpenExamPrep teaching for the New York DOS Security or Fire Alarm Installer exam uses the definition DOS actually printed. 19 NYCRR 195.1(b) (January 2023 DOS compilation of GBL Article 6-D and Part 195) defines central station as follows, in substance:

An off-premises monitoring facility with special receiving equipment, in communication with the transmission equipment for a subscriber’s protected premises. The transmission equipment for the subscriber’s protected premises may be owned by the central station, the subscriber, or any other person. Personnel are generally in attendance on a continuous basis to observe, record, and dispatch personnel to investigate various alarms or trouble signals. They may report alarm signals to police, fire, or other agencies. Central stations may also provide response services to a protected premises with security personnel or with technicians to check and service the system.

Memorize the hinges, not a paraphrase that drops them:

• Off-premises — a FACU in the electrical room is not a central station.
• Special receiving equipment — an after-hours voicemail box is not a DACR.
• Communication with the subscriber’s transmitter — ownership of that transmitter is flexible.
• Continuous attendance — generally, people are there to watch the signals.
• Observe, record, dispatch — three operator verbs.
• May report to police or fire — retransmission is contemplated.
• Security personnel or technicians — two different response models; 195.18 splits them.

NFPA 72 uses supervising station as the broader technical term (central station, remote station, proprietary supervising station). Chapter 15 returns to occupancy and system types. This section stays on what 195.1(b) named and what the communicator actually sends.

Signal types — alarm, supervisory, trouble, restore

The FACU does not have one yellow light called “something is wrong.” Off-premises reporting uses four families you must not collapse.

A closed sprinkler valve is the classic supervisory item. The building is not reporting a fire. It is reporting that a suppression system is impaired. Dispatching engines as if smoke were showing is the wrong mental model; logging it as a “panel trouble” so nobody calls the owner is also wrong.

A cut NAC is trouble. The horns may not work. That is a system impairment. It is not waterflow.

A waterflow switch is alarm (fire). Water is moving in the sprinkler system. That is not a supervisory valve event.

Restore is how the station knows the valve was reopened or the communicator test succeeded. Programming restores off, or mapping restores into a different account, is how a building stays in perpetual alarm in the automation software.

Fire versus burglary versus panic

The same 195.1(a) alarm-system definition covers intrusion, break-in, theft, movement, sound, fire, heat, smoke, explosion. The communicator still must label the event so the operator does the right thing.

Panic that sounds a siren can turn a holdup into a hostage problem. Fire that is programmed as burglary sends the wrong agency. Burglary that is programmed as fire sends engines to a door contact. Those are protocol errors under 195.1, not “monitoring preferences.”

Security opening/closing (arm/disarm) reports are not fire alarms. They are commonly Contact ID 400-family events. A missed opening can be a security supervisory-style event for the subscriber. It is still not waterflow.

Path supervision at the station — missed tests

Section 10.2 taught the timer. This section teaches the human. If the 60-minute single-path check-in, the 6-hour multiple-path test, or the DACT daily/6-hour test does not arrive, the DACR / automation must show a failure to test or communications trouble. 195.1(b) says personnel observe alarms or trouble signals. A missed test is a trouble signal. It is not optional wallpaper.

The licensed installer/service company is who fixes the path. The operator is who notices it. Programming the account to suppress fail-to-test, or telling the subscriber “we turned off the timer because the cell path was noisy,” takes the premises off the supervised path. That programming is 195.1 servicing.

Runner service versus technician-only — 19 NYCRR 195.18

195.1(b) allows a central station to send security personnel or technicians. Those are not the same license stack.

19 NYCRR 195.18 special licensure under Articles 7 and 7-A:

• (a) A business licensed under Article 6-D that employs security guards as defined in GBL Article 7-A must also be licensed under Article 7 (Private Investigator, Watch, Guard or Patrol Agency) and must comply with Article 7-A security-guard registration. The regulation’s own example: the use of security personnel to respond to an alarm and secure a protected premises.
• (b) A licensed alarm business that does not provide security response and does not otherwise employ security guards, but provides response with technicians only to check or service the alarm system, does not require Article 7 licensure for that model.

Exam application:

• Runner / guard who arrives, locks doors, walks out loiterers, holds the scene — that is securing the premises. Article 7 and 7-A are in play. Alarm-installer IDs under Part 195 are not a guard card.
• Technician who arrives, silences, resets, tests the communicator, replaces a battery, reports the FACU clear — that is checking or servicing the alarm system. Article 6-D covers it. Article 7 is not required by 195.18(b) for that technician-only response.
• A technician who is told to “just stay until the owner gets there and keep people out” has been turned into a guard. The job description, not the van logo, decides.

Chapter 3 already treated discipline and Article 7/7-A as a business-practice overlay. This section is the transmission reason it appears: central stations dispatch people, and DOS drew a bright line between securing premises and servicing systems.

Putting the whole path on one drawing

Closed-book, walk the chain:

1. An initiating device (smoke, valve, door contact, holdup button) changes state.
2. The FACU or security control processes it as alarm, supervisory, trouble, or restore.
3. The communicator (DACT, IP, cellular, or dual-path) seizes a path and delivers Contact ID or another listed format.
4. The DACR / supervising-station automation handshakes, records, and kissoffs.
5. The operator observes and records, then dispatches the right agency and/or the right runner or technician.
6. A restore or a successful test closes the event. A missed test opens a trouble.

Ownership of the box on the wall does not remove the need for a licensed installer to program it. 195.1 still includes communication equipment and system protocol whether the central station, the subscriber, or “any other person” owns the transmitter.

Exam traps

• Calling the FACU a central station because it has a communicator card.
• Treating supervisory valve-off-normal as a fire alarm or as a wiring trouble.
• Sending panic to the fire service, or waterflow to a burglary call list.
• Claiming technician-only service response requires an Article 7 guard license.
• Claiming guard/runner “secure the building” work is only Article 6-D.
• Inventing a New York-only operator stopwatch (for example a unique DOS 90-second dispatch minute). Fire alarm retransmission is commonly taught NFPA 72 as immediate to the communications center; do not replace that with a fabricated statewide second-count.

When you can quote 195.1(b), split alarm/supervisory/trouble/restore, split fire/burg/panic, and split 195.18 runners from technicians, you have finished Module 2.III alarm transmission. Fire-technology chapters later reuse these signal types on detectors, waterflow, and notification. Service chapters reuse fail-to-test as a maintenance complaint.