Slide 1

ASAP to the PSAP: Reducing 9-1-1 Processing Time by Minutes for Alarm Notifications Between Alarm Monitoring Companies & 9-1-1 PSAPs

Presentation to the Alarm Industry Communications CommitteeMarch 6, 2014Bill Hobgood, Project Manager, City of Richmond, DIT Public Safety TeamEd Bonifas, Vice-PresidentAlarm Detection Systems, Inc.

BillAutomated Secure Alarm Protocol (ASAP)Agenda

The ASAP StandardHow it WorksPSAP ExperiencesCentral Station ImplementationsCurrent StatusQuestions & Answers

BillAutomated Secure Alarm Protocol (ASAP)Acronyms and DefinitionsAPCO - Association of Public Safety Communications OfficialsASAP Automated Secure Alarm ProtocolCSAA Central Station Alarm AssociationNIEM National Information Exchange ModelNLETS The International Justice & Public Safety Sharing NetworkPSAP Public Safety Answering Point

Bill

These are some acronyms used throughout this presentation: APCO Association of Public Safety Communications Officials, ASAP The Automated Secure Alarm Protocol, CSAA Central Station Alarm Association, NIEM National Information Exchange Model, NLETS The International Justice & Public Safety Sharing Network (formerly known as the National Law Enforcement Telecommunications System), and PSAP Public Safety Answering PointAutomated Secure Alarm Protocol (ASAP)4NIEM Examples of What It Does at a High LevelVehicle MakeNCIC:Vehicle Make = Message Key VMAExample: VMA/FORD

GJXDM:Example: FORD

NIEM Core:Example: FORD5NIEM Examples of What It Does at a High LevelVehicle ColorNCIC:Vehicle Color = Message Key VCO Example: VCO:BLK/WHI GJXDM: Example: BLK/WHI NIEM Core: Examples: WHI BLK GRNCase Study The Automated Secure Alarm Protocol (ASAP) The Birth of an American National Standard

Official ANS Name: APCO/CSAA 2.101.1-2008 ANS Alarm Monitoring Company to PSAP CAD External Alarm Interface Exchange

Adoption Date: January 15, 2009

Standards-BasedXMLConverted from Custom Template to GJXDM then to NIEM

No Longer a Pilot; in full production

Rebranded [April 2011]: The Automated Secure Alarm Protocol (ASAP)

Bill

This presentation evolves around a new American National Standard adopted on January 15, 2009 commonly called the External Alarm Interface Exchange ANSI. This new standard is available to alarm monitoring companies, 911 centers. software companies that write software for alarm monitoring companies, and Computer-Aided Dispatch providers.Automated Secure Alarm Protocol (ASAP)By The NumbersPSAPs 6,500 primary & secondaryPolice/Fire/Med Agencies 20,000+Central Station Dispatches 22,800,000 annually115,000 to Richmonds 9-1-1 PSAP150,000 to the Houston Emergency CenterPSAPs Call Volume 250,000,000 annually

1 Source: Security Industry Alarm CoalitionThere are roughly 6,500 PSAPs in the United States. There are more than 20,000 Law Enforcement, Fire and EMS agencies in the US The number of households that rely on wireless cell service only as their method to make phone calls is currently at 35% and climbing The number of alarm notifications made annually to 9-1-1 PSAPs by alarm monitoring companies is 22,800,000. The number was 32,000,000 5 years ago which demonstrates that False Alarm Reduction efforts really are working!!!Of the 22,800,000, 15,000 are relayed to Richmonds 9-1-1 center and 150,000 are relayed to the Houston Emergency Center Finally, the estimated call volume to all PSAPs in 2010 was 250 millionAutomated Secure Alarm Protocol (ASAP)Automated Secure Alarm Protocol - PurposeTo provide a standard data exchange for electronically transmitting information between an Alarm Monitoring Company and a Public Safety Answering Point (PSAP).

Generic Explanation: The exchange replaces the telephone calls between the Alarm Monitoring Company operator and the 911 PSAP call-taker.

Bill

The official purpose of this new standard is to provide a data exchange for transmitting information electronically between an Alarm Monitoring Company and a Public Safety Answering Point. Generically speaking, the new standard replaces the telephone calls between the Alarm Monitoring Company operator and the 911 PSAP call-taker.Automated Secure Alarm Protocol (ASAP)How ASAP Works

Initial Notification of New Alarm EventThree Primary Uses Central Station initiates notification of new alarm eventCentral Station Incident Number Sent to PSAP

Bill

ASAP has three primary uses First, the new alarm event is sent electronically from the alarm monitoring company to the 9-1-1 centers Computer-Aided Dispatch System (CAD) once the central station operator concludes that the event must be handed off the 9-1-1 PSAP for dispatch to public safety resources. It is important to mention that ASAP in no way changes the steps that an alarm operator must take before notifying the PSAP. For example, if call verification or enhanced call verification is required, the alarm operator still performs these procedures prior to notifying the PSAP through the use of ASAP. The data that is sent to the PSAP includes all data about the premises monitored by the alarm system; e.g. address, event type, directions to the location (for rural areas), alarm trigger points, contact information, permit info, etc. Data transmitted also included information about the alarm monitoring central station; e.g. name of the company, operator ID, contact information, alarm service company info, etc.

Automated Secure Alarm Protocol (ASAP)How ASAP Works

Three Primary Uses Acknowledgement by PSAP that notification has been Accepted or Rejected PSAP Incident Number Returned to Alarm Company

PSAPs Response & Acknowledgement Bill

Next, the 9-1-1 PSAPs CAD system with the appropriate Accept or Reject message and a PSAP incident number if the event has been accepted. Two things are required from the alarm monitoring company by the PSAP: a valid address within the jurisdiction and a valid event type such as Burglary, or Holdup, etc. There is a standardized event type list with the ASAP standard. Failure to transmit a valid street address or a valid event type will result in the CAD system sending a Reject message back to the alarm operator. Keep in mind, that the CAD system is performing these steps automatically without any 9-1-1 staff intervention and without a telephone call.

Automated Secure Alarm Protocol (ASAP)How ASAP Works

Three Primary UsesUpdates from Alarm CompanyKey-holder informationRequest to cancel dispatchResponse to PSAP questions

Bi-Directional Status & Response UpdatesUpdates from the PSAPResources dispatchedResources arrived on sceneCall closure with dispositionRequest for information Bill

Likewise, the CAD can send updates to the alarm company when emergency responders are dispatched, arrive on the scene, and clear from the scene along with disposition information.If the radio dispatcher or even a field resource has a question for the alarm operator, they too can send the question to the alarm operator as an UPDATE and ask their question. Examples could include: Do you have an ETA for the key-holder?, What is the key-holders name and what will they be wearing?, etc.Automated Secure Alarm Protocol (ASAP)Automated Secure Alarm Protocol - Goals Goal #1

Eliminate the telephone calls between the Alarm Monitoring Company and the 9-1-1 PSAP

Telephone Call VolumeFrom Alarm Companies

Alarm Monitoring CompanyPublic Safety PSAPBill

The first primary goal is to reduce the number of telephone calls from alarm monitoring companies to 911 call centers. What you just heard are the telephones ringing in the 9-1-1 PSAPs from alarm monitoring companies that use the telephone to notify the PSAP of an alarm event. PSAPs hate to hear telephones ringing, but love ASAP. Automated Secure Alarm Protocol (ASAP)Automated Secure Alarm Protocol - Goals Eliminate miscommunication between the Alarm Monitoring Company operators and the9-1-1 PSAP call-takers

I cant understand you.How do you spell that street?I cant hear you, call back.Mistakes& MiscommunicationGoal #2Bill

The next goal is to eliminate the miscommunication and mistakes made that could occur during the traditional handoff ofinformation verbally between the alarm monitoring company operator and the 911 call-taker.

Persons speaking different languages, overseas monitoring (just a continent away ), even differing accents in the United States, or anything that breaks down the communications barrier is eliminated with the ASAP program.Automated Secure Alarm Protocol (ASAP)Automated Secure Alarm Protocol - Goals Goal #3

Decrease processing & response times to alarm-related calls-for-service with an increase in law enforcement apprehensions made, fires more quickly extinguished, and lives saved.

Processing & Response Times

Bill

The final goal is to experience a decrease in 9-1-1 processing time which equate to a reduction in response times by emergency responders and get the first responders to the alarm event site faster.

This decrease in 9-1-1 processing time and reduction in response times sets the stage for an increased likelihood in law enforcement apprehensions made, fires more quickly extinguished, and lives saved.

Several documented cases where the Richmond & Houston Police Departments have arrived on the scene quickly and in time to apprehend the suspect(s)

Automated Secure Alarm Protocol (ASAP)ASAP to the PSAP Comparative Analysis Traditional Delivery Versus Use of ASAP

Alarm Co ProcessesTelephone CallRingingGather Information Dispatch UnitsWithout ASAP: Delivery via TelephoneAlarm Co ProcessesNo Phone CallNo Gathering Information Process Data Dispatch UnitsWith ASAP..1 - 3 minutes or more

15 seconds or less

Bill

This slide is an excellent demonstration showing the significant reduction in processing and response times using ASAP for alarm handoffs to 911 by alarm companies compared to the traditional method of delivery via telephone.

Upon receipt of an alarm signal by the alarm company, after routine verification procedures have been completed, the difference in the traditional method using the telephone versus using the new alarm exchange standard becomes apparent very quickly.

Watch carefully, at this comparison.Automated Secure Alarm Protocol (ASAP)ASAP Outcomes in VirginiaRichmonds and York Countys Experiences22,000+ total alarm exchanges transmitted:No telephone call; No call-taker involvementSpelling mistakes & accidental transposition of street address numbers eliminatedNo low volume headset issuesNo need to try to interpret accentsWorks efficiently regardless of how inundated 9-1-1 call takers may beWas1 min - average process time w/o repetitionup to 3 min (sometimes more) process time for some alarm callsAlarm operators sometimes placed on hold for 8 10 minutesThe worst call in the PSAPNow15 sec or less - average turnaround time via the interfaceThe most accurate and concise call in the PSAP

Bill

The outcome of this project at the City of Richmond and York County Virginia has been a huge success, resulting in several thousand alarm events transmitted electronically to Richmonds 911 center while the 911 center itself had several thousand less telephone calls to handle.

Since the implementation of the alarm standard in Richmond, not a single mistake has occurred and processing time has been reduced to less than 15 seconds.

Works efficiently regardless of how inundated 9-1-1 call takers may be: during storms, call-takers are inundated with 9-1-1 calls, and resources to answer the 7 digit lines are often lacking. With ASAP, there is no delay and no dependency waiting on a call-taker to answer the telephone.

Telephone calls from alarm operators to the PSAP was indeed the worse call in the PSAP, but the most accurate and concise call in the PSAP when ASAP is used.Automated Secure Alarm Protocol (ASAP)ASAP Outcomes in Houston, TexasHoustons Experience Since April 28, 2011Demographics634 square miles (10 times larger than Richmond, Va)2.3 million people (4th most populous city in the U.S.)4th largest 9-1-1 PSAP in the United StatesConsistent 13% Drop in the Number of Police Alarms Handled by a Call-taker :Houston receives more than 2,600 police alarms weekly43,000 alarm systems monitored by 3 participating alarm companiesNon-Emergency Telephone Call Volume Reduced by 15%Potential Savings of $1 - $2 million annuallyDemographics about Houston 634 square miles 2.3 million people 4th largest PSAP in the United States Houston went live with ASAP on April 28, 2011 Receives more than 2,600 police alarm weekly; has experienced a consistent 13% drop in the number of police alarm handled by call-takers 43,000 alarm systems in Houston are monitored by the 3 alarm companies currently participating with ASAP Non-emergency telephone call volume has been reduced by 15% Potential savings of $1 - $2 million annually. Houston has staff dedicated to answering non-9-1-1 lines. As Houstons non-emergency call volumes drop, some of these staff can be reassigned to other departments and agencies within Houstons government.

Automated Secure Alarm Protocol (ASAP)Houstons Emergency Center

Automated Secure Alarm Protocol (ASAP)PSAP Challenges That ASAP Can HelpPSAP telephone call taking process Call-takers must place priority in answering 9-1-1 calls Alarm companies call on 7-digit numbers; frequent answer delaysPSAP resources often limited; staffing shortages; overtimeNG9-1-1 to allow citizens to send texts, pictures, and video: PSAP resources to be stretched even furtherComputer-Aided Dispatch (CAD) providers Dozens of CAD providers versus 5 - 6 alarm automation providersSix CAD tier one providers have or developing a solutionMany others have expressed interest but waiting on PSAPs to come forwardOutreach efforts must continueASAP is an ANSI-standard based on open standardsOne size fits all no matter how small or large the agencyCAD providers can develop interface once and market many timesNon-vendor specific

Bill

Call-takers must place priority in answering 9-1-1 calls first. Alarm companies often encounter delays in reaching the PSAP PSAP staffing levels sometimes at critical minimum manning levels; Next Generation 9-1-1 may stretch PSAP resources even further Whereas there are only 6-7 alarm automation providers, the people that write the alarm monitoring software application for alarm monitoring companies, the number of CAD providers not proportionate. There are perhaps 14-15 tier one CAD companies, 75-100 tier two CAD providers, and many more their three. Only four CAD providers currently have a solution or are in the process of developing a solution. Why not more interest by CAD providers? Many have been waiting on PSAPs to request an ASAP interface while the same PSAPs have been waiting on the CAD providers to offer it. Once size fits all: ASAP will work for a PSAP that receives one alarm per day, and it will work for New York City. CAD providers (and automation providers) need only develop ASAP once and remarket it many times. Automated Secure Alarm Protocol (ASAP)Alarm Industry Challenges/ResponsibilitiesAddresses must sync to PSAPs address file (MSAG/Geo-file)Bulk address validations From new participating alarm company to PSAPs already participating with the ASAP programTo new participating PSAP from alarm companies already participating with the ASAP programAddress validations confirm that address is correct within the participating jurisdiction onlyDoes not account for addresses assigned to the wrong PSAP in the alarm companys DBAlarm companies will be responsible for using a 3rd party service for ESN resolution New account address validationsPerformed automatically by alarm companys automation software when new account addedAlarm monitoring companies must use event types from standardized listPSAP decides up front which alarm types it will receive (e.g. law, fire, and/or EMS)PSAP decides how to translate each alarm event type

Bill

Addresses must sync to PSAPs address file Bulk address validations New account validations

Event type listAutomated Secure Alarm Protocol (ASAP)Current Status - ASAP Operational PSAPsCity of Richmond (VA) City of Houston (TX)Washington DC Tempe (AZ) PDJames City County (VA)

And many more in development

Bill

The three participating alarm companies have a direct connection to Nlets A new CSAA Message Broker is operational: Vector Security and Richmond are in production with the Message Broker Planning to migrate all ASAP traffic through the Message Broker has been completed & work is in progress (Late summer target implementation) Operational PSAPs The City of Richmond (Intergraph CAD) York County (VA) (transitioning to a Motorola Premier One CAD in June) Houston (Northrop Grumman CAD) Tempe Arizona Police Communications (Versaterm) James City County (VA) is undergoing testing and should be in production this month (Sungard/OSSI) More the 100 other PSAPs have shown strong interest in the project: (Washington DC, Boston, Chicago, NYC, Charlotte, many others) Central Stations UTCFS has incorporated ASAP into their MASTERMIND product (used by Vector, Monitronics, ADT, many others) Dice has incorporated ASAP in their product (used by UCC, many others) Other companies developing a solution (Bold, IBS, others) Nearly 100 charter alarm companies that supported the development of the CSAA Message Broker will be engaged with ASAP over the next several months Other central stations can participate after the charter companies have had an opportunityAutomated Secure Alarm Protocol (ASAP)CAD Providers with an ASAP Interface SolutionIntergraph Northrop Grumman Versaterm SunGard Public SectorAnd many more in developmentBill

The three participating alarm companies have a direct connection to Nlets A new CSAA Message Broker is operational: Vector Security and Richmond are in production with the Message Broker Planning to migrate all ASAP traffic through the Message Broker has been completed & work is in progress (Late summer target implementation) Operational PSAPs The City of Richmond (Intergraph CAD) York County (VA) (transitioning to a Motorola Premier One CAD in June) Houston (Northrop Grumman CAD) Tempe Arizona Police Communications (Versaterm) James City County (VA) is undergoing testing and should be in production this month (Sungard/OSSI) More the 100 other PSAPs have shown strong interest in the project: (Washington DC, Boston, Chicago, NYC, Charlotte, many others) Central Stations UTCFS has incorporated ASAP into their MASTERMIND product (used by Vector, Monitronics, ADT, many others) Dice has incorporated ASAP in their product (used by UCC, many others) Other companies developing a solution (Bold, IBS, others) Nearly 100 charter alarm companies that supported the development of the CSAA Message Broker will be engaged with ASAP over the next several months Other central stations can participate after the charter companies have had an opportunityAutomated Secure Alarm Protocol (ASAP)Current Status ASAP Operational Alarm Central StationsVector Security (Ranked #9)*United Central ControlNational Monitoring CenterRapid Response Monitoring Monitronics (Ranked #5)*SafeGuard (Ranked #34)*AffiliatedAlarm Detection Systems (#24)*American Alarm (#39)*RFI

* Source: SDM Magazine 2013Bill

The three participating alarm companies have a direct connection to Nlets A new CSAA Message Broker is operational: Vector Security and Richmond are in production with the Message Broker Planning to migrate all ASAP traffic through the Message Broker has been completed & work is in progress (Late summer target implementation) Operational PSAPs The City of Richmond (Intergraph CAD) York County (VA) (transitioning to a Motorola Premier One CAD in June) Houston (Northrop Grumman CAD) Tempe Arizona Police Communications (Versaterm) James City County (VA) is undergoing testing and should be in production this month (Sungard/OSSI) More the 100 other PSAPs have shown strong interest in the project: (Washington DC, Boston, Chicago, NYC, Charlotte, many others) Central Stations UTCFS has incorporated ASAP into their MASTERMIND product (used by Vector, Monitronics, ADT, many others) Dice has incorporated ASAP in their product (used by UCC, many others) Other companies developing a solution (Bold, IBS, others) Nearly 100 charter alarm companies that supported the development of the CSAA Message Broker will be engaged with ASAP over the next several months Other central stations can participate after the charter companies have had an opportunityAutomated Secure Alarm Protocol (ASAP)Current Status Central Stations That Have Signed Contract to Participate in ASAPAcadianAckermanADS Security(Nashville) (#26)*ADT (Ranked #1)*Alarm Center, Inc. Alarm Central Station ASG (Ranked #11)*CentraLarmCheckpointCMSCOPSDevcon (Ranked #20)*DGA

Diebold (Ranked #8)*DMC SecurityGuardian Security (Ranked #10)*iWatchMACEMonitoring AmericaPeak Alarm (Ranked #68)*Protection One (Ranked #6)*Stanley (Ranked #3)*Tyco (Ranked #2)*Vivint (Ranked #4)*Washington Alarm (Ranked #80)*Wayne Alarm* Source: SDM Magazine 2013 24Automated Secure Alarm Protocol (ASAP)This Project is an Award Winning ProjectAwards2009 Governors Technology Award for Innovation in Local GovernmentInaugural IJIS Institutes Innovation Award (2009)American City & County Magazines 2009 Crown Community Award for Excellence in Local GovernmentCenter for Digital Governments 2009 Digital Government Achievement Award Accepted into the 2009 City Showcase Sponsored by the National League of CitiesAlliance for Innovation 2010 Award for Innovation in Local Government 2013 Computerworld Honors Laureate Award Safety & Security2013 Governors Technology Award for IT as an Efficiency Driver, Government to Business2013 Government Computer News (GCN) Award for Outstanding Information Technology Achievement in Government2013 Best of NIEM award and induction into the NIEM Hall of Fame

Automated Secure Alarm Protocol (ASAP)Current Project StatusCSAA approved as a Nlets Strategic Partner Organization (May, 2011)CSAA implementing a CSAA managed message broker server at NletsTesting has been completedUpdated IEPD & schema 3.3 released to Automation and CAD ProvidersAlarm companies, both CSAA & Non-CSAA members can participate75+ charter alarm companies to come on board first (including ADT)Likely to swell to 300 alarm companies over next 2 - 3 yearsPotential participation by up to 600 alarm companies over next 5 -10 yearsNlets has assigned two new Message Keys for alarm trafficALQ = Alarm Data Sent by the Alarm Company to the PSAPALR = Responses from the PSAP to the Alarm CompanyORIs & Unique CSAA IDs used for routing messagesBill

CSAA approved as a Nlets Strategic Partner Organization (May, 2011)CSAA implementing a CSAA managed message broker server at NletsTesting has been completedUpdated IEPD & schema 3.3 released to Automation and CAD ProvidersAlarm companies, both CSAA & Non-CSAA members can participateNearly 100 charter alarm companies to come on board first (including ADT)Likely to swell to 300 alarm companies over next 2 - 3 yearsPotential participation by up to 600 alarm companies over next 5 -10 yearsNlets has assigned two new Message Keys for alarm trafficALQ = Alarm Data Sent by the Alarm Company to the PSAPALR = Responses from the PSAP to the Alarm CompanyORIs & Unique CSAA IDs used for routing messages

Automated Secure Alarm Protocol (ASAP)What is Nlets?Standards Based Hardware and Network SolutionProvides information services and support for justice-related agencies applicationsRedundancy and HOT Dr site in KYServes all U.S. states and territories, Federal agencies with a justice component, and select regional and international agencies including CanadaDelivering the right information at the right timeInnovative solutions driven by end user needsEducation on available services

SteveAutomated Secure Alarm Protocol (ASAP)System & Network StatisticsOn track for 1.5 BILLION Transactions in 2012System UptimeYTD: 99.94%Network UptimeYTD: 99.98%Avg. Round Trip Message Response TimeYTD: 1.51 secondsTop Message KeysRQ, DQ, IPQ, CR, AMTop UsersCBP, TX, IP, CA, MI

(From June Monthly Statistics)28Automated Secure Alarm Protocol (ASAP)Nlets Information ExchangesDriver and vehicle registrationCriminal history recordsState wanted persons dataSex offender registryProbation and parole registryConcealed carry databasesState warrant recordsDriver license and corrections imagesInterpolData from Canada and Mexico Homeland Alert messagesLEO Flying ArmedINS databases at LESCAmber Alerts Severe weather warningsAircraft registrationsGSA federal/diplomatic platesAnd hundreds more!Legacy Services forand Access ToSteveAutomated Secure Alarm Protocol (ASAP)Nlets ProjectsDL & Corrections Interstate Photo SharingProactive AlertingLicense Plate Reader National IndexTribal Nation SharingBulk Cash SmugglingGeo-spatial MappingAutomated Secure Alarm Protocol (ASAP)Whats Next?SteveAutomated Secure Alarm Protocol (ASAP)Nlets & ASAP to the PSAPNlets- Is The Preferred Transport for ASAP Traffic

Infrastructure is in place.

Safe and secure Communications

Intelligent Routing Scheme

In operation to Thousands of PSAPs

Trusted by PSAPs

Preferred by the Central Station Alarm Association

SteveAutomated Secure Alarm Protocol (ASAP)Nlets CSAA High Level Design NletsCSAA High Level DesignXML Firewall housed within Nlets facility.Secure Certificate Authenticated hardware based VPNs to Central StationsCSAA Message Broker Server to consolidate Central Station traffic housed within Nlets siteCSAA/Nlets routing wrappers

SteveAutomated Secure Alarm Protocol (ASAP)Nlets & ASAP to the PSAPFor Nlets this is a fairly simple pass through via the secure Nlets system and network to the states then via the state network to the local PSAPsThis is going to take off fast!

PSAPs are anxious to reduce call time and save valuable resources

CAD system vendor partners are modifying their software updates to support these transactions!Talk to your CAD provider today! SteveAutomated Secure Alarm Protocol (ASAP)Expanding the ASAP ASAP Phase II (Schema 3.3)ASAP ANS up for review in CY2013Additional fields have been added to the schemaVideo confirmation link for PSAPs and field respondersAlarm service organizationX/Y coordinates in decimal degreesUniform list of information messages Reject messages from the Message Broker or the PSAPAccept message from the PSAPFields can be used before next release of ANSOnly Schema 3.3 will work with the Message BrokerBillAutomated Secure Alarm Protocol (ASAP)Automated Secure Alarm Protocol History2004 2005 2006 2007 2008 2009 2010 2011 2012 2013Aug,04APCO & CSAA kickoff project to create and test a data exchange between a central station alarm monitoring company and a 911 PSAP; York Co., VA and Vector Security are selected; York Co. uses a copy of Richmonds CAD; Vector Security uses GEJan,05APCO and CSAA formerly partner to develop an exchange that will be consistently used by CAD providers and Central Station Alarm Companies for PSAPs to increase efficiency and decrease errorsJul,06The Alarm Interface Exchange 2.0 goes live at York Co. VA; includes only Burglar and Hold-up alarms

Aug,06APCO requests the City of Richmond to join the pilot to generate additional volumes of alarm exchanges; City of Richmonds interface goes live within 24 hours of the request

Oct,06The alarm exchange pilot is expanded to include Fire and Medical alarms

Sep, 07The City of Richmond implements new Intergraph CAD System

Jan, 08The Public Safety Data Interoperability (PSDI) project is launched;

Apr, 08The PSDI steering committee holds first meeting; among the decisions made is to upgrade the External Alarm Interface Exchange to NIEM 2.0

Jun, 08IJIS issues an RFP to upgrade the alarm exchange IEPD to NIEM 2.0

Jul, 08IJIS awards IEPD contract to Waterhole Software

Aug, 08The External Alarm Interface IEPD is completed using NIEM 2.0

Sep, 08The IEPD is published on www.niem.gov; the External Alarm Interface Exchange is submitted to the APCO ANS process as a proposed ANSI

Jan, 09 APCO publishes APCO/CSAA ANS Standard 2.101.1-2008

Apr, 09Enhancements implemented:Bi-directional update messages implementedAutomatic address validations initiated by MasterMind

Automated Secure Alarm Protocol History2004 2005 2006 2007 2008 2009 2010 2011 2012 2013Jan, 10The CSAA and Nlets sign the short term MOU to conduct proof of concept: allows 2 more alarm companies & 3 PSAPs Feb, 10Nlets assigns ALQ and ALR message keys for alarm exchange traffic Jun, 10Nlets inspects Vector Securitys facility and performs auditJul, 10Nlets approves Vector Security for connectivity to Nlets message switch Aug, 10Vector and the City of Richmond go live using ORIs for routing and the use of Nlets message keysApr, 11Houston goes live with ASAPMay, 11CSAA becomes a SPO / Message Broker Development Begins

Apr, 12City of Richmond & Vector Security go-live on new Message Broker

Oct, 12Washington DC goes live with ASAP

Automated Secure Alarm Protocol History2004 2005 2006 2007 2008 2009 2010 2011 2012 2013Questions & Thank You for Attending!!! For More Information: APCO: www.apco911.org email: asap@apcointl.org External Alarm Interface Exchange ANSI, Fact Sheet, FAQs, IEPD http://www.apco911.org/resources/asap.html IEPD available at www.niem.gov (Tools > Work with IEPDs > Search for IEPD (Keyword Alarm) Central Station Alarm Association: www.csaaual.org Nlets: www.nlets.org CSAA: psap@csaa-asap.org

Bill Hobgood, Project Manager, Public Safety TeamCity of Richmond, Dept. of Information Technology900 E. Broad St., Room G-2Richmond, Va. 23219(804) 646-5140Cell (804) 240-0744Bill.Hobgood@Richmondgov.com

Bill

Automated Secure Alarm Protocol (ASAP)