ASAP to PSAPs

How the CSAA’s Automated Secure Alarm Protocol program is ushering technology into central stations


It has been a slow progression, but finally central stations are benefiting from the plethora of technology that is commonly available. Mobile apps now enable consumers to arm/disarm their alarm panels, cancel dispatches via text and initiate chat sessions with operators.

Of even greater significance is our reaching the tipping point for addressing that one area of monitoring that has defied the adoption of technology — the transmission of alarm data to the responding agency. With more than 100 central stations contracted to participate in the Automated Secure Alarm Protocol (ASAP) program from the Central Station Alarm Association (CSAA); and new Public Safety Answering Points (PSAPs) either adding the capabilities to existing computer-aided dispatch (CAD) systems or providing specifications in new RFPs, we have the momentum to change the very foundation of how central stations communicate.

 

The Latest Status of the Program

For the last several years, ASAP has battled the “chicken and the egg syndrome,” with new PSAPs unwilling to invest because there were not enough connected alarm companies. As this article is printed, Protection One and Diebold will both either be live or within days of having live connections and transmitting on the ASAP network; while, in the background, both ADT and Tyco have initiated internal testing in anticipation of connecting in 2014. This major thrust from national companies provides the necessary volume to gain significant inroads with PSAPs that are looking for an ROI on their CAD investment. This is great news for smaller alarm companies that have been waiting for PSAP adoption in their geographic areas.

 

Are You Connected and Involved?

If you still aren’t, now is the time to get involved. All major software vendors have either built the ASAP interface or are in the final phase of testing. MAS, Bold, SGS and DICE have software offerings that have been tested and are in release; SIMS and IBS are developing software and preparing to test.

Typically, testing involves validating the connections with an existing ASAP-ready PSAP such as in Houston; York County, James City County and Richmond, Va.; Washington, D.C.; and Tempe, Ari. Once we have successfully connected with an experienced PSAP — ensuring that signals and responses are being sent and received appropriately — then testing can be done with a new one. Technical documentation exists for software vendors to participate in the program.

The CSAA’s ASAP Outreach Committee, co-chaired by Joe Carr (UCC) and Kathleen Schraufnagel (Monitronics), is working on a “hot list” of PSAPs that are currently on the existing CAD platforms that support ASAP connectivity. They need your help to effectively reach PSAPs across the United States. This is a large volunteer effort that needs local presence to be effective.

The team has developed extensive material to train and market the ASAP program. Having local alarm companies present the business case to drive acceptance in their area is the most effective marketing approach. The Alabama Alarm Association (Kristi Jennings of ESC Central) has taken on the challenge of working on ASAP acceptance on a statewide basis.

Be the champion for your state association — areas with active alarm companies gain the fastest adoption!

 

What About Your Data?

Yes, CAD system acceptance is dependent on an exact match between the alarm company and the CAD database. If in the past your operator verbally relayed a street address as 104 Center Avenue, and the Call Taker put into their CAD system 104 Centre Avenue, everyone was happy. Now, you will need to have the exact spelling to get a clean transmission. This is accomplished by completing a database validation. Alarm companies coordinate — with the receiving PSAP or a third party — a database scrub to authenticate address information. Once completed on the existing database, this becomes a procedure that is done regularly as part of your data entry process through a script provided by your automation vendor. This validation process/tool allows for confirmation of correct dispatch jurisdictions at the time the customer is added, eliminating what many central stations handle manually or leave to the chance. No more calling the dispatch number to be told an address is not in their response area.

This content continues onto the next page...