For central stations wondering if they’ll ever be part of ASAP to PSAP, there was good news from ESX 2012: Progress continues to be made.
Show attendees got an update on the protocol at a seminar led by Mark McCall of United Central Control, Glenn Schroeder of the Security Network of America, Pam Petrow and Anita Ostrowski of Vector Security, and Melissa Courville of DICE Corp.
While ASAP might not be advancing fast enough to satisfy everyone in the industry, the panelists in Nashville listed a number of bullet points that detailed the gains. Among them:
—A CSAA-owned message broker is up and running at the National Law Enforcement Telecommunications System (Nlets) facility in Arizona. The server acts as a scrubber for transmissions being forwarded from monitoring companies to public safety answering points.
—A trademark process has been completed to certify the ASAP name and logo.
—ANSI version 3.3 of the protocol is currently live in Richmond, Va., and it is scheduled to go online in other pilot project locations by the end of the year.
—ASAP leaders have expanded their outreach to the PSAP community in 2012, with presentations to groups including the Texas Police Chiefs Association and the Los Angeles Sheriff’s Department.
The three municipalities involved in the pilot project—Richmond, Va., York County, Va., and Houston—are scheduled to be joined soon by Tempe, Ariz., and James City County, Va. On the monitoring side, Alarm Detection Systems and ADT are in line to join pilot participants Vector Security, UCC and Monitronics.
McCall, director of information technology and facility security officer at UCC, told the seminar audience that central stations planning to become part of ASAP may find that the requirements “are a little bit more than what your operation is used to now.”
“Remember what we’re connecting to,” he said, referring to Nlets. “We’re connecting to the same network that every police department, every fire department and every emergency agency is connected to. Nlets is responsible for the integrity of that network, and for us as an industry to play in their sandbox, we have to meet their security requirements.”
On the plus side, most of those concerns were alleviated with the deployment of the message broker, McCall said. Other ASAP issues involving the preparation of automation vendors and CAD providers are being addressed, and the CSAA is creating a new website—www.asaptopsap.org—to keep interested parties informed.
“The materials are continually being added to and the CSAA will let everyone know when [the information] is ready for public consumption, as it will be sending out ASAP-dedicated email blasts to confirmed charter members at that time,” said Courville, co-chairwoman of the ASAP to PSAP Outreach Committee.
In the interim, she said inquires about the protocol should be addressed to Becky Lane (firstname.lastname@example.org) or Monique Talbot (email@example.com) at the CSAA.