Presentation is loading. Please wait.

Presentation is loading. Please wait.

Presentation to the Alarm Industry Communications Committee

Similar presentations


Presentation on theme: "Presentation to the Alarm Industry Communications Committee"— Presentation transcript:

1 Presentation to the Alarm Industry Communications Committee
ASAP to the PSAP: Reducing Processing Time by Minutes for Alarm Notifications Between Alarm Monitoring Companies & PSAPs Bill Hobgood, Project Manager, City of Richmond, DIT Public Safety Team Ed Bonifas, Vice-President Alarm Detection Systems, Inc. Bill Presentation to the Alarm Industry Communications Committee March 6, 2014

2 Central Station Implementations Current Status Questions & Answers
Agenda The ASAP Standard How it Works PSAP Experiences Central Station Implementations Current Status Questions & Answers Bill

3 Acronyms and Definitions
APCO - Association of Public Safety Communications Officials ASAP – Automated Secure Alarm Protocol CSAA – Central Station Alarm Association NIEM – National Information Exchange Model NLETS – The International Justice & Public Safety Sharing Network PSAP – 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 Point

4 NIEM – Examples of What It Does at a High Level
Vehicle Make NCIC: Vehicle Make = Message Key VMA Example: VMA/FORD GJXDM: <VMACodeType> Example: <VMACodeType>FORD</VMACodeType> NIEM Core: <VehicleMakeCode> Example: <VehicleMakeCode>FORD</VehicleMakeCode>

5 NIEM – Examples of What It Does at a High Level
Vehicle Color NCIC: Vehicle Color = Message Key VCO Example: VCO:BLK/WHI GJXDM: <VCOCodeType> Example: <VCOCodeType>BLK/WHI</VCOCodeType> NIEM Core: <VehicleColorPrimaryCode> <VehicleColorSecondaryCode> <VehicleColorInteriorText> Examples: <VehicleColorPrimaryCode>WHI</VehicleColorPrimaryCode> <VehicleColorSecondaryCode>BLK</VehicleColorSecondaryCode> <VehicleColorInteriorText>GRN</VehicleColorInteriorText>

6 Case Study – The Automated Secure Alarm Protocol (ASAP)
The Birth of an American National Standard Official ANS Name: APCO/CSAA ANS Alarm Monitoring Company to PSAP CAD External Alarm Interface Exchange Adoption Date: January 15, 2009 Standards-Based XML Converted 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.

7 PSAPs – 6,500 primary & secondary Police/Fire/Med Agencies – 20,000+
By The Numbers PSAPs – 6,500 primary & secondary Police/Fire/Med Agencies – 20,000+ Central Station Dispatches 22,800,000 annually1 15,000 to Richmond’s PSAP 150,000 to the Houston Emergency Center PSAPs Call Volume 250,000,000 annually 1 Source: Security Industry Alarm Coalition There 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 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 Richmond’s center and 150,000 are relayed to the Houston Emergency Center Finally, the estimated call volume to all PSAPs in 2010 was 250 million

8 Automated Secure Alarm Protocol - Purpose
To 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.

9 Initial Notification of
How ASAP Works Initial Notification of New Alarm Event Three Primary Uses Central Station initiates notification of new alarm event Central 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 center’s Computer-Aided Dispatch System (CAD) once the central station operator concludes that the event must be handed off the 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.

10 PSAP’s Response & Acknowledgement
How ASAP Works Three Primary Uses Acknowledgement by PSAP that notification has been Accepted or Rejected PSAP Incident Number Returned to Alarm Company PSAP’s Response & Acknowledgement Bill Next, the PSAP’s 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 staff intervention and without a telephone call.

11 Bi-Directional Status & Response Updates
How ASAP Works Three Primary Uses Updates from Alarm Company Key-holder information Request to cancel dispatch Response to PSAP questions Bi-Directional Status & Response Updates Updates from the PSAP Resources dispatched Resources arrived on scene Call closure with disposition Request 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-holder’s name and what will they be wearing?”, etc.

12 Automated Secure Alarm Protocol - Goals
Alarm Monitoring Company Public Safety PSAP Telephone Call Volume From Alarm Companies Eliminate the telephone calls between the Alarm Monitoring Company and the PSAP Bill 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 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.

13 Automated Secure Alarm Protocol - Goals
I can’t understand you. How do you spell that street? I can’t hear you, call back. Mistakes & Miscommunication Eliminate miscommunication between the Alarm Monitoring Company operators and the 9-1-1 PSAP call-takers Bill The next goal is to eliminate the miscommunication and mistakes made that could occur during the traditional handoff of information 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.

14 Automated Secure Alarm Protocol - Goals
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 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 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)

15 ASAP to the PSAP – Comparative Analysis
Traditional Delivery Versus Use of ASAP Without ASAP: Delivery via Telephone Alarm Co Processes Telephone Call Ringing Gather Information Dispatch Units 1 ½ - 3 minutes or more With ASAP……….. Alarm Co Processes No Phone Call Process Data No Gathering Information Dispatch Units 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. 15 seconds or less

16 ASAP – Outcomes in Virginia
Richmond’s and York County’s Experiences 22,000+ total alarm exchanges transmitted: No telephone call; No call-taker involvement Spelling mistakes & accidental transposition of street address numbers eliminated No low volume headset issues No need to try to interpret accents Works efficiently regardless of how inundated call takers may be Was… 1½ min - average process time w/o repetition up to 3 min (sometimes more) – process time for some alarm calls Alarm operators sometimes placed on hold for 8 – 10 minutes The worst call in the PSAP Now… 15 sec or less - average turnaround time via the interface The 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 Richmond’s 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 call takers may be: during storms, call-takers are inundated with 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.

17 ASAP – Outcomes in Houston, Texas
Houston’s Experience Since April 28, 2011 Demographics 634 square miles (10 times larger than Richmond, Va) 2.3 million people (4th most populous city in the U.S.) 4th largest PSAP in the United States Consistent 13% Drop in the Number of Police Alarms Handled by a Call-taker : Houston receives more than 2,600 police alarms weekly 43,000 alarm systems monitored by 3 participating alarm companies Non-Emergency Telephone Call Volume Reduced by 15% Potential Savings of $1 - $2 million annually Demographics 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 lines. As Houston’s non-emergency call volumes drop, some of these staff can be reassigned to other departments and agencies within Houston’s government.

18 Houston’s Emergency Center

19 PSAP Challenges That ASAP Can Help
PSAP telephone call taking process Call-takers must place priority in answering calls Alarm companies call on 7-digit numbers; frequent answer delays PSAP resources often limited; staffing shortages; overtime NG9-1-1 to allow citizens to send texts, pictures, and video: PSAP resources to be stretched even further Computer-Aided Dispatch (CAD) providers Dozens of CAD providers versus alarm automation providers Six CAD tier one providers have or developing a solution Many others have expressed interest but waiting on PSAPs to come forward Outreach efforts must continue ASAP is an ANSI-standard based on open standards One size fits all no matter how small or large the agency CAD providers can develop interface once and market many times Non-vendor specific Bill Call-takers must place priority in answering calls first. Alarm companies often encounter delays in reaching the PSAP PSAP staffing levels sometimes at critical minimum manning levels; Next Generation 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 tier one CAD companies, 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.

20 Alarm Industry Challenges/Responsibilities
Addresses must sync to PSAP’s address file (MSAG/Geo-file) Bulk address validations From new participating alarm company to PSAPs already participating with the ASAP program To new participating PSAP from alarm companies already participating with the ASAP program Address validations confirm that address is correct within the participating jurisdiction only Does not account for addresses assigned to the wrong PSAP in the alarm company’s DB Alarm companies will be responsible for using a 3rd party service for ESN resolution New account address validations Performed automatically by alarm company’s automation software when new account added Alarm monitoring companies must use event types from standardized list PSAP 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 PSAP’s address file Bulk address validations New account validations Event type list

21 Current Status - ASAP Operational PSAPs
City of Richmond (VA) City of Houston (TX) Washington DC Tempe (AZ) PD James 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 opportunity

22 CAD Providers with an ASAP Interface Solution
Intergraph Northrop Grumman Versaterm SunGard Public Sector 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 opportunity

23 Current Status – ASAP Operational Alarm Central Stations
Vector Security (Ranked #9)* United Central Control National Monitoring Center Rapid Response Monitoring Monitronics (Ranked #5)* SafeGuard (Ranked #34)* Affiliated Alarm Detection Systems (#24)* American Alarm (#39)* RFI 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 opportunity * Source: SDM Magazine 2013

24 Current Status – Central Stations That Have Signed Contract to Participate in ASAP
Acadian Ackerman ADS Security(Nashville) (#26)* ADT (Ranked #1)* Alarm Center, Inc. Alarm Central Station ASG (Ranked #11)* CentraLarm Checkpoint CMS COPS Devcon (Ranked #20)* DGA Diebold (Ranked #8)* DMC Security Guardian Security (Ranked #10)* iWatch MACE Monitoring America Peak 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

25 This Project is an Award Winning Project
Awards 2009 Governor’s Technology Award for Innovation in Local Government Inaugural IJIS Institute’s Innovation Award (2009) American City & County Magazine’s 2009 Crown Community Award for Excellence in Local Government Center for Digital Government’s 2009 Digital Government Achievement Award Accepted into the 2009 City Showcase Sponsored by the National League of Cities Alliance for Innovation 2010 Award for Innovation in Local Government 2013 Computerworld Honors Laureate Award – Safety & Security 2013 Governor’s Technology Award for IT as an Efficiency Driver, Government to Business 2013 Government Computer News (GCN) Award for Outstanding Information Technology Achievement in Government 2013 – Best of NIEM award and induction into the NIEM Hall of Fame

26 Current Project Status
CSAA approved as a Nlets Strategic Partner Organization (May, 2011) CSAA implementing a CSAA managed message broker server at Nlets Testing has been completed Updated IEPD & schema 3.3 released to Automation and CAD Providers Alarm companies, both CSAA & Non-CSAA members can participate 75+ charter alarm companies to come on board first (including ADT) Likely to swell to 300 alarm companies over next years Potential participation by up to 600 alarm companies over next years Nlets has assigned two new Message Keys for alarm traffic ALQ = Alarm Data Sent by the Alarm Company to the PSAP ALR = Responses from the PSAP to the Alarm Company ORIs & Unique CSAA IDs used for routing messages Bill CSAA approved as a Nlets Strategic Partner Organization (May, 2011) CSAA implementing a CSAA managed message broker server at Nlets Testing has been completed Updated IEPD & schema 3.3 released to Automation and CAD Providers Alarm companies, both CSAA & Non-CSAA members can participate Nearly 100 charter alarm companies to come on board first (including ADT) Likely to swell to 300 alarm companies over next years Potential participation by up to 600 alarm companies over next years Nlets has assigned two new Message Keys for alarm traffic ALQ = Alarm Data Sent by the Alarm Company to the PSAP ALR = Responses from the PSAP to the Alarm Company ORIs & Unique CSAA IDs used for routing messages

27 What is Nlets? Standards Based Hardware and Network Solution
Provides information services and support for justice-related agencies applications Redundancy and HOT Dr site in KY Serves all U.S. states and territories, Federal agencies with a justice component, and select regional and international agencies including Canada Delivering the right information at the right time Innovative solutions driven by end user needs Education on available services Steve

28 System & Network Statistics
On track for 1.5 BILLION Transactions in 2012 System Uptime YTD: 99.94% Network Uptime YTD: 99.98% Avg. Round Trip Message Response Time YTD: 1.51 seconds Top Message Keys RQ, DQ, IPQ, CR, AM Top Users CBP, TX, IP, CA, MI (From June Monthly Statistics)

29 Nlets Information Exchanges
Legacy Services for… …and Access To Interpol Data from Canada and Mexico Homeland Alert messages LEO Flying Armed INS databases at LESC Amber Alerts Severe weather warnings Aircraft registrations GSA federal/diplomatic plates And hundreds more! Driver and vehicle registration Criminal history records State wanted persons data Sex offender registry Probation and parole registry Concealed carry databases State warrant records Driver license and corrections images Steve

30 DL & Corrections Interstate Photo Sharing Proactive Alerting
Nlets Projects DL & Corrections Interstate Photo Sharing Proactive Alerting License Plate Reader National Index Tribal Nation Sharing Bulk Cash Smuggling Geo-spatial Mapping Automated Secure Alarm Protocol (ASAP) What’s Next? Steve

31 Nlets & ASAP to the PSAP Nlets- 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 Steve

32 Nlets – CSAA High Level Design
XML Firewall housed within Nlets’ facility. Secure Certificate Authenticated hardware based VPN’s to Central Stations CSAA Message Broker Server to consolidate Central Station traffic housed within Nlets site CSAA/Nlets routing wrappers Steve

33 Nlets & ASAP to the PSAP For 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 PSAPs This 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! Steve

34 Expanding the ASAP – ASAP Phase II (Schema 3.3)
ASAP ANS up for review in CY2013 Additional fields have been added to the schema Video confirmation link for PSAPs and field responders Alarm service organization X/Y coordinates in decimal degrees Uniform list of information messages Reject messages from the Message Broker or the PSAP Accept message from the PSAP Fields can be used before next release of ANS Only Schema 3.3 will work with the Message Broker Bill

35 Automated Secure Alarm Protocol – History
Aug,04 APCO & 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 Richmond’s CAD; Vector Security uses GE Jan,05 APCO 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 errors Jul,06 The Alarm Interface Exchange 2.0 goes live at York Co. VA; includes only Burglar and Hold-up alarms Aug,06 APCO requests the City of Richmond to join the pilot to generate additional volumes of alarm exchanges; City of Richmond’s interface goes live within 24 hours of the request Oct,06 The alarm exchange pilot is expanded to include Fire and Medical alarms Sep, 07 The City of Richmond implements new Intergraph CAD System

36 Automated Secure Alarm Protocol – History
Jan, 08 The Public Safety Data Interoperability (PSDI) project is launched; Apr, 08 The PSDI steering committee holds first meeting; among the decisions made is to upgrade the External Alarm Interface Exchange to NIEM 2.0 Jun, 08 IJIS issues an RFP to upgrade the alarm exchange IEPD to NIEM 2.0 Jul, 08 IJIS awards IEPD contract to Waterhole Software Aug, 08 The External Alarm Interface IEPD is completed using NIEM 2.0 Sep, 08 The IEPD is published on the External Alarm Interface Exchange is submitted to the APCO ANS process as a proposed ANSI Jan, 09 APCO publishes APCO/CSAA ANS Standard Apr, 09 Enhancements implemented: Bi-directional “update” messages implemented Automatic address validations initiated by MasterMind

37 Automated Secure Alarm Protocol – History
Jan, 10 The CSAA and Nlets sign the short term MOU to conduct proof of concept: allows 2 more alarm companies & 3 PSAPs Feb, 10 Nlets assigns ALQ and ALR message keys for alarm exchange traffic Jun, 10 Nlets inspects Vector Security’s facility and performs audit Jul, 10 Nlets approves Vector Security for connectivity to Nlets message switch Aug, 10 Vector and the City of Richmond go live using ORIs for routing and the use of Nlets message keys Apr, 11 Houston goes live with ASAP May, 11 CSAA becomes a SPO / Message Broker Development Begins Apr, 12 City of Richmond & Vector Security go-live on new Message Broker Oct, 12 Washington DC goes live with ASAP

38 Questions & Thank You for Attending!!!
For More Information: APCO: External Alarm Interface Exchange ANSI, Fact Sheet, FAQs, IEPD IEPD available at (Tools > Work with IEPDs > Search for IEPD (Keyword “Alarm”) Central Station Alarm Association: Nlets: CSAA: Bill Hobgood, Project Manager, Public Safety Team City of Richmond, Dept. of Information Technology 900 E. Broad St., Room G-2 Richmond, Va (804) Cell (804) Bill


Download ppt "Presentation to the Alarm Industry Communications Committee"

Similar presentations


Ads by Google