A new Message Broker server managed by the Central Station Alarm Association (CSAA) will become operational soon. The Message Broker is a combination of hardware and software intended to perform a middleware function between Nlets and the alarm monitoring companies that want to take advantage of the Automated Secure Alarm Protocol (ASAP). The Message Broker will perform error checking and ensure that transmissions from the alarm monitoring companies are properly formatted before sending the message to Nlets for subsequent forwarding to the appropriate state control point and ASAP-participating PSAP. Conceivably, 75-150 alarm monitoring companies (including ADT) could become operational with the ASAP program over the course of the next few months. Hundreds more are likely to sign up over the next 2-5 years.

For the PSAPs already using ASAP, the thought of more alarm monitoring companies coming on board is welcome news. These PSAPs know very well the benefits of using ASAP to receive alarm notifications. Getting more alarm companies on board with ASAP cannot come too soon for these PSAPs. Some localities have been very clear in making it known in advance of their ASAP implementation that all alarm notifications to their PSAP will be required via ASAP and not via telephone.

Alarm monitoring automation providers given Message Broker specification

Most alarm monitoring companies use an automation product from one of the half dozen major automation providers. One automation provider has successfully tested its interface product with the Message Broker and the city of Richmond’s PSAP. During the month of February, the remaining automation providers are being given the specification to develop their interface product with the Message Broker by the CSAA/APCO Technical Committee. Because ASAP is an American National Standard, automation providers need only develop their product once but can market the product unlimited to their customers: the alarm monitoring companies. The specification also includes updates to the technical schema and new fields. Included is the alarm confirmation link discussed in past articles that will eventually allow PSAPs and field resources to see the same video that the alarm company operator can see to verify an actual alarm event.

New schema available for computer-aided dispatch providers

CAD providers must develop an interface to process messages bi-directionally between the CAD system and the alarm monitoring companies using the ASAP schema, but have no need to develop an interface solution to communicate directly with the Message Broker. The CAD providers simply facilitate communications between the CAD system and the state control point. Most CAD providers already know how to do this through existing interfaces to the state networks. The CAD providers must keep track of which message switch is used by each state and the protocol required to communicate to each state control point. Roughly two-thirds of the state control points have programmed their switches to allow the ASAP traffic to pass by adding the ALQ and ALR message keys. All ASAP traffic originating from alarm monitoring companies carries an ALQ message key whereas the ASAP traffic originating from the CAD system contains an ALR message key. CAD providers that already have an ASAP interface solution should conform to the 3.3 schema as-soon-as-possible.

In contrast to roughly a dozen or more tier one CAD companies and eight times as many tier two CAD companies, the number of CAD providers with a solution available today is two. Three other CAD providers are actively testing their ASAP interface product which should be operational within the next 30 – 60 days in Arizona and Virginia. A sixth CAD provider is actively developing their product. Each of these CAD providers is a tier one CAD company. Other CAD providers, tier one and tier two companies, have been provided information about the ASAP program but have not developed an ASAP interface product yet.

What PSAPs can do

When some CAD providers were asked why they have not developed an ASAP interface product, many replied that none of their customers have requested it. When PSAPs were asked why they had not embarked down the ASAP path, several mentioned that they didn’t think that their CAD provider offered the interface and the PSAP was waiting to be contacted by their CAD provider when a solution became available. Other PSAPs, understandably, were planning to upgrade or change their CAD system in the near future and do plan to take advantage of ASAP when the time is right.

PSAPs that have an interest in the ASAP program should do two things: (1) contact their CAD provider account manager and make it known that the agency has an interest in the PSAP program, and (2) contact the author to be added to the list of 100+ agencies that have already expressed interest in ASAP.

Pilot PSAPs needed

Because approximately two-thirds of the state control points have programmed their switches to accommodate ASAP traffic, volunteer PSAPs are needed to conduct ASAP testing with the state control point and one alarm monitoring company. An immediate need exists for PSAPs to volunteer in California, Colorado, and Oregon to be pilot sites. A less urgent but important need exists for volunteer PSAPs throughout the rest of the U.S. Interested PSAPs should write to the author.

About the Author

Bill Hobgood is a project manager for the city of Richmond’s DIT Public Safety Team, with 40 years of experience in public safety. He is also a project coordinator for APCO’s Comm Center & 9-1-1 Services Department and a subject matter expert on the ASAP project. Contact Bill via e-mail. [email protected]