- 1.0.0 Version
- 6574 Download
- 2.47 MB File Size
- 1 File Count
- January 31, 2012 Create Date
- February 17, 2012 Last Updated
In 2005, APCO International and the Central Station Alarm Association (CSAA) partnered to develop an exchange that will be consistently used by CAD providers and central station alarm companies for PSAPs to increase efficiency and decrease errors. The first beta site for the initial test project was York County, Virginia, Dept. of Fire and Life Safety, Emergency Communications Division. Vector Security participated in the electronic alarm exchange. The first data template was successfully completed October 2004. An Alerts Working Team was formed in 2006 to begin the External Alert 2.0 IEPD Development. This team was formed by the IJIS Public Safety Technical Standards Committee (IPSTSC) to create external alerts and requests-for-service IEPD using the GJXDM standard.
Following a two year development effort which included extensive testing, the Alarm Interface Alarm Exchange went live in July 2006. The City of Richmond's Police Division of Emergency Communications authorized a development partnership with York County. In July 2008, the data requirements for Alarm 3.0 IEPD were finalized and in August the IEPD was completed. Mappings were changed from GJXDM to NIEM 2.0. This effort to upgrade the IEPD was sponsored by the Public Safety Data Interoperability (PSDI) Program, funded by the Bureau of Justice Assistance (BJA) and co-managed by APCO International and IJIS Institute. The document was then submitted by the APCO Data Transfer Committee through the APCO ANS process and approved by ANSI January 15, 2009.
For the IEPD details, click here.
To download the schema, click here
The purpose of this ANS, also known as Alarm 3.0, is to provide a standardized data exchange for the electronically transmitted alarm information between an alarm monitoring company and a PSAP. There are three primary uses for this Information Exchange Package Document (IEPD):
- Initial notification of an alarm event
- Bi-directional update of status between an alarm monitoring company and the PSAP
- Bi-directional update of other events between an alarm monitoring company and a PSAP
To view frequently asked questions (FAQs) about this ANS,click here.
To view a fact sheet about this ANS, click here.
For further information on implementing this standard, please email email@example.com.