Learning Hub
Alarm Integration
Glossary
PSAP: Refers to Public Safety Answering Points (PSAP) which are communications centers chartered with taking emergency calls for service from police, fire and medical agencies, i.e. Dispatch Centers within police agencies.
ASAP: Refers to the Alarm Secure Automation Protocol (ASAP) which is the APCO/CSAA/ANSI Standard for defining the electronic interchange between alarm central stations and PSAP CADs.
Central Stations: Staffed communications center where alarms are monitored. Serves as the originating end point for all ASAP messages that will be passed to a PSAP. Not all alarm companies have central stations but all central stations are alarm companies.
Automation System/Platform: Refers to an alarm central station’s software, or hybrid CAD system, which functions as a computer assisted call taking system. The automation system is the Central Station’s method of communicating with the ASAP Service.
What is the ASAP-to-PSAP Service?
ASAP to PSAP Service: Facilitates ANSI/ASAP alarm messages between central stations to PSAPs.
TMA & APCO Serve as Governing Organizations: The ASAP-to-PSAP Services was developed in conjunction by The Monitoring Association (TMA) (https://tma.us/), the industry trade association, and LLC, that represent the central station’s interests and positions; and The Association of Public Safety Communications Officials (APCO) (https://www.apcointl.org/?s=asap) who created the ASAP protocol which is the standard for the ASAP to PSAP Service.
CommSys Manages the ASAP- to-PSAP Service: Under the direction of TMA, CommSys architected, managed development and, today, manages the ASAP–to–PSAP Service
Fulfills Public Safety Need: TMA, APCO & CommSys created the ASAP to PSAP service to:
- Reduce PSAP workload by automating the calls from commercial alarm companies
- Eliminate dispatch delays due to human error and miscommunication
- Improve Public Safety/Law Enforcement Response Time
Results: Today, ASAP has proven to dramatically decrease response time.
Why is there a need for the ASAP-to-PSAP Service?
Emergency Communications Overload: Alarm company notifications represent the single largest volume of calls.
Dispatch Delays due to Inefficiencies: Alarm calls are answered on non-emergency Lines resulting in lost time for:
- Longer hold times
- Human error and miscommunication
- Lengthy address validation
- Multiple phone calls
Factors Adding to Overload: Cell phone saturation & IoT
Is the ASAP-to-PSAP Service available nationally? What alarm companies are participating?
ASAP Readiness: Visit the link below for ASAP-to-PSAP Readiness by State, PSAPs & Alarm Companies/Monitoring Centers
What Issues can Impact Alarm Integration Development?
Not a Typical CAD to CAD Interface: ASAP-to-PSAP requires automation to :
- Call for Service integration focused only on Alarms
- Pre-validation of alarm codes & addresses
- Accept/reject decisioning
- Routing to Dispatch
- 2 Way Real-Time “Chat” Communication & updates
- Certification by TMA
How ASAP-to-PSAP Works: Required Protocol-defined message workflows include:
- Call for Service integration focused only on Alarms
- Address Verification
- Alarm
- Update
- CAD Update
Typical Alarm Workflow: Required Protocol-defined message workflows include:
- Normal central station processing of Alarm Messages – ECV, etc.
- CS Operator initiated sending alarm to PSAP
- PSAP Accepts (or Rejects, ending workflow)
- PSAP Dispatch sends “chat” or update message to central station
- Central station replies via update
- PSAP CAD can automatically report dispatch and close-out via CAD Update
Consulting Services are Available to Expedite Development: CommSys offers a variety of Consulting Services from project management to certification.
Glossary
PSAP: Refers to Public Safety Answering Points (PSAP) which are communications centers chartered with taking emergency calls for service from police, fire and medical agencies, i.e. Dispatch Centers within police agencies.
ASAP: Refers to the Alarm Secure Automation Protocol (ASAP) which is the APCO/CSAA/ANSI Standard for defining the electronic interchange between alarm central stations and PSAP CADs.
Central Stations: Staffed communications center where alarms are monitored. Serves as the originating end point for all ASAP messages that will be passed to a PSAP. Not all alarm companies have central stations but all central stations are alarm companies.
Automation System/Platform: Refers to an alarm central station’s software, or hybrid CAD system, which functions as a computer assisted call taking system. The automation system is the Central Station’s method of communicating with the ASAP Service.
What is the ASAP-to-PSAP Service?
ASAP to PSAP Service: Facilitates ANSI/ASAP alarm messages between central stations to PSAPs.
TMA & APCO Serve as Governing Organizations: The ASAP-to-PSAP Services was developed in conjunction by The Monitoring Association (TMA) (https://tma.us/), the industry trade association, and LLC, that represent the central station’s interests and positions; and The Association of Public Safety Communications Officials (APCO) (https://www.apcointl.org/?s=asap) who created the ASAP protocol which is the standard for the ASAP to PSAP Service.
CommSys Manages the ASAP- to-PSAP Service: Under the direction of TMA, CommSys architected, managed development and, today, manages the ASAP–to–PSAP Service
Fulfills Public Safety Need: TMA, APCO & CommSys created the ASAP to PSAP service to:
- Reduce PSAP workload by automating the calls from commercial alarm companies
- Eliminate dispatch delays due to human error and miscommunication
- Improve Public Safety/Law Enforcement Response Time
Results: Today, ASAP has proven to dramatically decrease response time.
Why is there a need for the ASAP-to-PSAP Service?
Emergency Communications Overload: Alarm company notifications represent the single largest volume of calls.
Dispatch Delays due to Inefficiencies: Alarm calls are answered on non-emergency Lines resulting in lost time for:
- Longer hold times
- Human error and miscommunication
- Lengthy address validation
- Multiple phone calls
Factors Adding to Overload: Cell phone saturation & IoT
Is the ASAP-to-PSAP Service available nationally? What alarm companies are participating?
ASAP Readiness: Visit the link below for ASAP-to-PSAP Readiness by State, PSAPs & Alarm Companies/Monitoring Centers
What Issues can Impact Alarm Integration Development?
Not a Typical CAD to CAD Interface: ASAP-to-PSAP requires automation to :
- Call for Service integration focused only on Alarms
- Pre-validation of alarm codes & addresses
- Accept/reject decisioning
- Routing to Dispatch
- 2 Way Real-Time “Chat” Communication & updates
- Certification by TMA
How ASAP-to-PSAP Works: Required Protocol-defined message workflows include:
- Call for Service integration focused only on Alarms
- Address Verification
- Alarm
- Update
- CAD Update
Typical Alarm Workflow: Required Protocol-defined message workflows include:
- Normal central station processing of Alarm Messages – ECV, etc.
- CS Operator initiated sending alarm to PSAP
- PSAP Accepts (or Rejects, ending workflow)
- PSAP Dispatch sends “chat” or update message to central station
- Central station replies via update
- PSAP CAD can automatically report dispatch and close-out via CAD Update
Consulting Services are Available to Expedite Development: CommSys offers a variety of Consulting Services from project management to certification.