Study guide
10.2 Mass Notification, Audio Comms, Consoles & Central Stations
ASIS Physical Security Professional PSP
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current PSP Exam Facts 1.2 Eligibility, Fees, Scheduling & Recertification 1.3 Experience-Based Testing, References & Study Approach
2 Assessment Planning & Methods
2.1 Assessment Plan, Stakeholders, Budget & Resources 2.2 Inside-Out, Outside-In, Site-Specific & Functional Models 2.3 Qualitative vs Quantitative Assessment Methods 2.4 Standards, Regulations, Codes & Where to Find Them
3 Asset Identification & Valuation
3.1 Asset Types, Terminology, Value, Criticality & Loss Impact 3.2 Valuing Tangible and Intangible Assets for Operations 3.3 Criticality, Key Areas & Loss-Impact Prioritization
4 Threats, Hazards & Operating Environment
4.1 Criminal, Terrorist, Insider & Sociopolitical Threats 4.2 Natural Disasters, Accidental & Cyber-Physical Hazards 4.3 Geography, Crime, Socioeconomics & Existing Countermeasures 4.4 Neighbors, Competitors, Legal, Reputation & Supply Chain
5 Vulnerability Assessment & Surveys
5.1 Surveys, Interviews, Incident Data, Crime Stats & Benchmarking 5.2 Evaluating Technology, Personnel & Procedures 5.3 Plans, Schematics & Environmental/Site Factors
6 Risk Analysis & Countermeasure Selection
6.1 Risk Analysis Strategies, Principles & Data Interpretation 6.2 Threat/Hazard–Vulnerability Pairing & Loss Event Profiles 6.3 Matching Countermeasures to Specific Risks 6.4 ROI, Total Cost of Ownership, Privacy, PII & Life Safety
7 Performance Requirements & Security Concepts
7.1 Design Constraints & Incorporating Risk Analysis 7.2 CPTED, Defense-in-Depth, 4 Ds & Security Terminology 7.3 Operational, Functional, Performance Requirements, Codes & Metrics
8 Structural Measures & CPTED Application
8.1 Fences, Gates & Perimeter Barriers 8.2 Blast Mitigation, Ballistic Protection & Hostile Vehicle Mitigation 8.3 Lighting, Locks, Doors, Windows & Glazing 8.4 Applying CPTED to Site Planning & Landscaping
9 Electronic Security Systems
9.1 Electronic Access Control Architecture & Credentials 9.2 Biometrics, Electrified Locks, Anti-Passback & Mantraps 9.3 Video Surveillance Design, Storage & Analytics 9.4 Intrusion Detection Sensors & Alarm Communications
10 Screening, Communications, Power & Networks
10.1 Personnel, Package & Vehicle Screening and Visitor/Vendor Policy 10.2 Mass Notification, Audio Comms, Consoles & Central Stations 10.3 Data Storage, Retention, PII & Physical Network Security 10.4 Primary/Backup Power and Copper, Fiber & Wireless Transmission
11 System Design & Project Documentation
11.1 Pre-Design, Schematic, Construction Docs, Calculations & Drawings 11.2 CSI MasterFormat, Owner Standards & AIA MasterSpec 11.3 Systems Integration, Scheduling, Cost Estimation & Value Engineering
12 Pre-Bid Meetings & Solicitation Packages
12.1 Site Visits, RFIs, Substitution Requests & Pre-Bid Meetings 12.2 RFP, RFQ, IFB & Sole Source 12.3 SOW, Timelines, Costs, Personnel & Documentation 12.4 Evaluation Criteria, Technical Compliance & Contracting Ethics
13 Procurement Planning & Vendor Selection
13.1 Procurement Process for Security Goods & Services 13.2 Interviews, Due Diligence, References & Selection 13.3 Project Management Functions in Procurement
14 Installation, Commissioning & Acceptance
14.1 Installation & Inspection Techniques 14.2 Commissioning & Implementation-Phase Integration 14.3 FAT, SAT & Final Acceptance Testing Criteria 14.4 Punch Lists, As-Builts, Config Management & End-User Training
15 Security Personnel Requirements
15.1 Roles, Limits, Proprietary vs Contract Staffing 15.2 Recruiting, KPIs, Discipline & Professional Development 15.3 Post Orders, Uniforms/Equipment & Non-Security Awareness
16 Lifecycle Maintenance & Program Evaluation
16.1 Preventive/Corrective Maintenance, Calibration, Service Agreements & Warranties 16.2 Upgrade Training, System Evaluation & Replacement
10.2 Mass Notification, Audio Comms, Consoles & Central Stations
Key Takeaways Explain This Topic AI
Mass notification is a priority, intelligible, multi-path emergency system; a music-capable public-address speaker is not automatically that system.
Security audio includes radio, telephone, intercom, and IP paging, each with different power, licensing, and network dependencies.
An on-site security operations console is not the same as a listed central monitoring station with dual communications, staffing, and contracted response.
Alarm floods, poor display layout, and single-sensor dispatch create missed events; dual authentication of alarms is a human-performance control.
Two-way intercom at doors, parking, and vestibules supports both operations and emergency talk-back that one-way paging cannot provide.
Last updated: September 2026
Emergency notification is a life-safety and security interface
When Domain 2 asks for emergency notification systems , the exam examples are mass notification , public address , and two-way intercom . Those three are related and not interchangeable. If you specify a ceiling speaker that plays lobby music and assume you have mass notification, you have specified a convenience system and hoped it will become an emergency system under stress.
Mass notification is the capability to deliver a recognized emergency message to people in and around a facility with enough intelligibility that they can act—evacuate, shelter, avoid an entrance, or stay out of a parking structure. In U.S. practice, fire-alarm and emergency-communications codes (notably NFPA 72 mass-notification provisions) treat in-building systems, wide-area “giant voice,” and distributed-recipient paths (SMS, email, desktop pop-up, mobile app) as layers, not as three brands of the same loudspeaker. Priority matters: an emergency page must seize the circuit over background music and routine paging. Hearing-impaired occupants need a visual counterpart (strobes, text displays, desktop alerts), not a louder horn. Live microphone capability for an evolving active-threat or weather message sits beside pre-recorded templates so an operator is not composing policy during the first thirty seconds.
Public address (PA) is often one-way audio for routine and emergency voice. A PA can be part of mass notification when it is designed for intelligibility, backup power, priority, and coverage in the rooms people actually occupy—including restrooms, stairwells, and parking. A PA that only covers the atrium will not move people on the loading dock. Measure speech intelligibility (commonly discussed as STI or CIS in specifications) instead of specifying wattage and hoping.
Two-way intercom is the talk-back path: vestibule stations, parking emergency callboxes, gate houses, elevator communications (which also have their own life-safety rules), and door stations tied to the security operations center. Two-way audio lets an operator challenge a visitor, coach someone who pulled a duress button, and confirm that a “forced door” is a delivery driver with a stuck badge rather than an intrusion. Recording intercom audio is a policy and privacy decision; if you record, disclose it and retain it with the same discipline as other security data.
A PSP-style design question often asks which layer is missing. Outdoor assembly areas with no wide-area voice, a beautiful in-building PA with no SMS path for people in cars, or mass SMS with no intelligible interior voice for occupants who do not have phones in hand, are incomplete notification concepts.
Radio, telephone, intercom, and IP audio
Security audio communications in the Body of Knowledge include radio, telephone, intercom, and IP audio . Treat each as a different failure mode.
Radio is still the officer’s primary mobile path when the phone is busy or the network is down. Simplex channels work nearby; a repeater extends a campus. Digital systems (for example P25 or DMR) add talkgroups and encryption options that analog open channels lack. Licensing, in-building dead spots (basements, vaults, MRI suites), and battery discipline belong in the design, not in a footnote. Interoperability with public-safety radio is an authority-having-jurisdiction and spectrum issue; do not assume the security talkgroup can reach the police dispatcher without a documented patch. Earpieces and discreet mics are an operations choice where officers should not advertise every transmission in a lobby.
Telephone remains relevant even in an IP building. Elevator phones, fire-fighter communications, and some alarm communicators still depend on a circuit that must work when the corporate LAN does not. A VoIP handset on the console is only as good as Power over Ethernet, the call manager, and the WAN. If the after-hours duress path is “call the SOC,” test that path on backup power.
Intercom was covered as two-way notification; operationally it is also how a gate house talks to a driver in diesel noise. Specify noise-cancelling stations, weather ratings, and a console that can queue calls so one parking box does not hide a vestibule duress.
IP audio (networked amplifiers, SIP speakers, paging over VLANs) scales well and fails like a network. Put paging on a dedicated VLAN with quality-of-service markings, keep it off guest Wi-Fi, and put the amplifier and PoE switches on backup power. A “free” software page to desktop speakers is not a listed mass-notification path unless the whole chain—client, server, authentication, and power—was designed for emergency use.
Path Direction Typical use Design dependency to name on the exam
Mass notification One-way to many, often with confirmation layers Evacuate, shelter, avoid, reunify Priority, intelligibility, visual/text paths, backup power
Public address Usually one-way Routine page plus emergency voice if specified Coverage where people are, not only the atrium
Two-way intercom Bidirectional Vestibules, parking, gates, challenge/response Console queuing, privacy/recording policy
- Radio Bidirectional among officers Patrol, incident, loss of LAN Licensing, repeaters, dead spots, batteries
- Telephone / VoIP Bidirectional SOC, elevator, vendor calls Analog survivability vs PoE/WAN dependence
- IP audio One-way or talk-back Campus paging, SIP speakers VLAN, QoS, UPS, not guest wireless
- Consoles versus listed central monitoring stations
Systems monitoring and display splits into control centers/consoles and central monitoring stations . Mixing those words is a common exam trap.
An on-site security operations center (SOC) or proprietary console is where this organization’s operators sit: video wall, alarm queue, access-control events, intercom, radio base, mass-notification microphone, and often building-automation views. The job is local assessment and dispatch of officers, and coordination with facilities and public safety. The room needs dual authentication to enter, lighting that does not wash the wall, acoustics, 24/7 ergonomics, and enough operators for the alarm rate you actually have at 02:00—not the rate in the sales demo.
A listed central monitoring station is a supervised alarm-monitoring facility (commonly discussed against UL 827 central-station service and related automation listings) that receives signals over supervised communications, staffs to listing rules, keeps records, maintains backup power and alternate communications (for example IP plus cellular), and often provides runner or contracted response . Insurers and some authorities ask for a certificate of the listed service. A proprietary SOC can still forward signals to a listed station for after-hours, holidays, or overflow. That hybrid is normal. What is not normal is calling a receptionist with a 19-inch monitor a “central station” and expecting listed response.
Remote supervising stations and subsidiary stations have still other NFPA 72 meanings. For PSP, keep the operational contrast clear: local console = owner’s operators and displays; listed central station = listed monitoring service with communications, staffing, and response obligations.
Human factors: floods, layout, dual authentication
Technology that the operator cannot use is not a countermeasure.
Alarm floods happen when weather shakes outdoor contacts, a fire drill forces a hundred doors, or a misconfigured panel retries. Fatigue follows. Post orders need a flood mode: acknowledge with reason, shelve nuisance points with supervisory approval, restore after the event, and never “silence all” as a lifestyle. Maintenance must fix the noisy device; the SOC is not a trash can for chronic false alarms.
Display layout should put the unacknowledged alarm queue in the primary visual field, maps next, and video as a tool to assess a selected event—not sixteen equal tiles that train the eye to see nothing. Ambient light, font size, and sitting-to-standing options are security design, not furniture leftover.
Dual authentication of alarms means two independent confirmations before you treat an event as a valid intrusion and launch police or armed response: for example a door contact plus interior motion, an alarm plus video of an unauthorized person, or two operators concurring. Single-zone dispatch on a noisy overhead door is how you train police not to come. Video verification policies must still respect privacy and must not delay a life-safety fire or duress event that codes require you to treat immediately.
Put the pieces together: a listed station that dual-authenticates burglary, an on-site SOC that owns mass notification and radio, and a PA that can be seized for emergency voice. If any one of those is “the receptionist will figure it out,” the supporting system is incomplete.