Downloaded 12 times
Uploaded byMark Fletcher, ENP
Dec 2014 One 2 One JAX Keynote
The document discusses the critical issues surrounding emergency call systems, highlighting a tragic incident involving a failed 911 call due to outdated technology. It emphasizes the need for advancements in emergency communications, particularly the transition to Next Generation 911 (NG911) systems, which can integrate enhanced data for better response outcomes. The presentation outlines the limitations of the current 911 infrastructure and advocates for the adoption of new technologies to improve public safety communications.
More Related Content
Similar to Dec 2014 One 2 One JAX Keynote
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Dec 2014 One 2 One JAX Keynote
- 1. ESInets and FirstNet On Ramps and Off Ramps for Critical Enterprise Data Mark J. Fletcher, ENP Chief Architect Worldwide Public Safety Solutions December 3, 2014 Photo Copyright © 2014, M. Fletcher
- 2. December 1, 2013– Kari Hunt died because of a single digit Kari met her estranged husband in a Marshall, Texas hotel for visitation with their 3 children Allegedly, her ex-husband brutally attacked and stabbed her multiple times Her 9 year old daughter tried to call 911 In fact, she tried to call 4 times, but the calls failed She was able to rush her 2 siblings to safety Kari Hunt died from her injuries before help could arrive Why did the calls fail? You needed to dial 9-911 from the hotel room But that’s not what we teach our children © 2014 Avaya Inc. All rights reserved. 2
- 3. HOMEWORK ASSIGNMENT Readabout Kari’s Law If you agree, sign the petition http://No9Needed.com © 2014 Avaya Inc. All rights reserved. 3
- 4. The Emergency CommunicationsTechnology Journey….. Location Based E911 Selective Routing 911 Access Police Box Direct Dial Next Generation 911 Services Circa 1880 1968 Circa 1985 Circa 1990 2011 Avaya – Confidential & Proprietary. Use pursuant to your signed agreement or Avaya Policy 4
- 5. Emergency Services Technology INFLECTION POINT 134 Years of Communications Technology Innovation 50 Years of Public Safety Technology Stagnation 1860 1880 1900 1920 1940 1960 1980 2000 2020 2040 Avaya – Confidential & Proprietary. Use pursuant to your signed agreement or Avaya Policy 5
- 6. The problem 9-1-1 is based on 1970’s technology: – Telephone Number (TN) presentation to the network for routing instructions Citizen 555-1234 Public Safety Agency “A” Public Safety Agency “B” Telecom Provider Public Safety Agency “C” SRDB* 555-1234 = Agcy A 555-4567 = Agcy B 555-6789 = Acgy C *Selective Router Data Base Citizen 555-4567 Citizen 555-6789 © 2014 Avaya Inc. All rights reserved. 6
- 7. Telecom Provider CLocDB* 555-1234 = Addr A 555-4567 = Addr B 555-6789 = Addr C The problem 911 is based on 1970’s technology: – Telephone Number (TN) presentation to the network for routing instructions – TN Presentation to the 9-1-1 Center for incident location reference – Registered name – Registered address – While this is typically sufficient for a Citizen 555-1234 residential citizen, individuals at work have additional challenges due to: – Large Campuses with multiple buildings – Unclear street addresses or no address – Buildings with access control and multiple floors Public Safety Agency “A” SRDB 555-1234 = Agcy A 555-4567 = Agcy B 555-6789 = Acgy C 555-1234 David Smith 3324 Arch St *Caller Location Data Base © 2014 Avaya Inc. All rights reserved. 7
- 8. Enhanced On SiteNotification with ADDITIONAL DATA Correlation of Information • Screen Pop Alert Clients can be anywhere • Detailed Floor Plans / Video • Integrations with Smart Building Data • Mobile apps, Web based or Reader boards By empowering the Enterprise with information about the incident they can contribute additional data simplifying the call for help. A hang up call now becomes a hang up with high temperature readings in the area. © 2014 Avaya Inc. All rights reserved. 8
- 9. User Level Identification User Identity inforamtion Specific opt-in data Cable Mgmt PBX User Data Enviro Info WLAN User Data Collecting Enterprise Location Data Device Level Identification Device ID Device Type / Location LDAP Active Directory Smart Building Medical interactio n Info ADLR Additional Data Location Repository © 2014 Avaya Inc. All rights reserved. 9
- 10. Getting Additional Datato the PSAP NETWORK LINK UP LDAP DATA STORE CM/PBX CONFIG CABLE PLANT WIREMAP WIRELESS AP ASSOC ADDITIONAL DATA REPOSITORY INTERNET WEB SERVICES RESPONDING TO HELD / DATA QUERIES PUBLISH URL / URI TO EXISTING DB ADDITIONAL DATA CORRELATION PSAP CPE QUERY PSAP CPE QUERY PUBLIC SAFETY DATABASE ANI / ALII © 2014 Avaya Inc. All rights reserved. 10
- 11. Next Generation PublicSafety Solutions WHAT’S CHANGING? © 2014 Avaya Inc. All rights reserved. 11
- 12. Yesterdays network wascumbersome and complex Enterprise Location Database Emergency call with 908-848-2602 as CLID / ANI SRDB MSAG Databases Calltaker ANI/ALI Screen Pop ANI ALI Databases PHONE NUMBER QUERY 908-848-2602 CUBE 2C231 © 2014 Avaya Inc. All rights reserved. 12
- 13. While extremely profitable,the legacy network model cannot survive new customer technology and market demands for affordable Emergency Call Handling in the Enterprise NG911 is here now, and Legacy E911 is dying on the vine © 2014 Avaya Inc. All rights reserved. 13
- 14. Tomorrows network issleek and rich with user data from the source Emergency SESSION with PIDF-LO Information Elements Next Generation 911 ESINet Enterprise Location Database Calltaker Screen Pop 908-848-2602 CUBE 2C231 Got anything else? Like a floor plan maybe? SURE DO! HERE IT IS . . . © 2014 Avaya Inc. All rights reserved. 14
- 15. Summary Current Demographicsand Behaviors are Changing Routing of Information is becoming the critical capability in a PSAP Current and Emerging Technologies can enhance public safety TODAY © 2012 Avaya Inc. All rights reserved. 19
- 16. The Avaya PodcastNetwork Available on iTunes and SoundCloud http://SoundCloud.com/AvayaPodcast http://SoundCloud.com/Fletch911 http://www.avaya.com/APN http://www.avaya.com/Fletcher © 2012 Avaya Inc. All rights reserved. 20
- 17. © 2014 AvayaInc. All rights reserved. 21
Editor's Notes
- #3 Kari met her estranged husband in a Marshall, Texas hotel for visitation with their 3 children Her ex-husband brutally attacked and stabbed her 49 times in front of her children Her 9 year old daughter tried to call 911 In fact, she tried to call 4 times, but the calls failed Finally, she rushed her 2 siblings to safety Kari Hunt Dunn died from her injuries before help could arrive Why did the calls fail? You needed to dial 9-911 from the hotel room But that’s not what we teach our children This is why Avaya in cooperation with Hank Hunt is promoting the No 9 Needed campaign, to raise awareness and fix this simple problem.
- #7 The problem today is that emergency call routing is based on a few basic principals. The first is the telephone number being presented to the network for routing. It assumes that each address has a unique telephone number, therefore making the phone number the database key for the emergency call routing entity in the network. The database manages the proper mapping of telephone number to the proper agency for called delivery.
- #8 While this is typically sufficient for residential citizens, individuals within a corporate enterprise have additional challenges due to large campuses with multiple buildings. These may have no, or unclear, street addresses as they are on private property, and secure buildings may have access control requirements and multiple floors serviced by various entrances. Enterprise users are typically not afforded the same level of location granularity, and while technology is available, it is often too confusing or expensive to deploy. Because of this, Enterprise Public Safety issues are often pushed to the side or forgotten about, until a tragedy happens.
- #9 Inexpensive, yet highly functional software modules are that provide verbose notification to emergency call events on the network. 1st Responder clients can be anywhere on the network that has connectivity to the enterprise will. This would include remote branch offices or VPN users. In addition to providing local on-site responders with critical information the server also acts as an integration point for the conveyance of rich location data to public safety.
- #10 while this level of information certainly adds relevant data to the question of location, it by itself is not typically enough to provide discrete information to specifically locate an individual. Fortunately corporate enterprise networks contain additional data resources that can be utilized and queried. Information from LDAP and active directory can provide details on the individual. The user themselves may even contribute additional personal or medical information that they have opted in for. Relevant data points from the wireless LAN infrastructure or the ML TS PBX itself can provide visibility into the device that was used to place an emergency call. That information, correlated with cable management records can be utilized to fine tune the location. And finally, critical environmental information from smart buildings or HVAC systems can provide important clues such is ambient temperature or smoke conditions in the origination area of the emergency call. When looking at an emergency call hangups, this additional information can be critical in determining real calls from hoax calls. This model also will neatly packages this information for retrieval or transmission to public safety entities, once a next generation emergency services network infrastructure is put in place.