1 / 72

2014 NENA Critical Issues Forum

2014 NENA Critical Issues Forum. NG9-1-1 – Are We There Yet? NENA: The 9-1-1 Association. Access to CIF PPTs and Notes. nena.org/ cif /notes WiFi : NENA2014 Code: ndccif14. The Journey to Next Generation 911. John Chiaramonte, ENP , PMP

felix-noble
Télécharger la présentation

2014 NENA Critical Issues Forum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2014 NENA Critical Issues Forum NG9-1-1 – Are We There Yet? NENA: The 9-1-1 Association

  2. Access to CIF PPTs and Notes • nena.org/cif/notes • WiFi: NENA2014 Code: ndccif14

  3. The Journey to Next Generation 911 John Chiaramonte, ENP, PMP Sr. Program LeaderMission Critical Partners

  4. A journey of a thousand miles must begin with a single step. -- Lao Tzu

  5. Where We’ve Been • 1900’s – Emergency calling started with “street boxes”, then became operator-assisted • 1968 – First 911 call made in Haleyville, Alabama • Late 1970’s – “Enhanced 911” (ANI with selective routing) debuts • March 1998 – First Phase I wireless call • October 26, 1999 – “911” is designated as the universal emergency telephone number • 2001 – NENA’s 9-1-1 Future Path Plan is released • 2003 – NENA begins NG9-1-1 architecture and project • Dec. 2004 – US DOT begins the NG911 Initiative

  6. Where We Are Today • Nearly 6,000 PSAPs across the U.S. • Handling ~240M calls per year (?) • 98% of PSAPs provide some Phase II • > 335M wireless devices in the U.S. • > 400K wireless 911 calls per day • Over 39% of households are wireless only • Nearly two-thirds of adults aged 25–29 (65.7%) are wireless only • Several states have established state or regional ESInets

  7. Comparing E911 and NG911 * These services require next generation originating networks as well as NG911

  8. Why Is NG911 Important? • Changing consumer habits and expectations • Eliminating limitations existing in today’s 911 • Efficiencies in 911 technology, ops, funding • Migration away from TDM to IP networks / eventual PSTN retirement • Ensuring equal access for all 911 callers • Improving responder safety / access to data • Enhancing resiliency, reliability, survivability, and flexibility for PSAPs

  9. Current Advancements in 911 • Text-to-911 • Telematics / sensors • State-level call routing • Regional ESInets • GIS technologies / data • “i3-ready” components • Data analytics • NG911 planning / cost efficiencies

  10. “Near” Future for 911 / NG911 • Full i3-compliant components / implementations • Policy Routing Function (PRF) • Caller Information Database (CIDB) • Real-Time Text (RTT) • Migration of tabular MSAGsto a geospatial address validation process (LVF) • All-IP communications (caller to PSAP to first responders and beyond) • Increased interoperability – RoIP/ FirstNet

  11. Beyond NG911 • “Technically nothing” • Enhanced state and national situational awareness through real-time analytics • Full use of additional data • National and international interoperability • Full integration with n-1-1 services, poison control, ITS systems

  12. The road to NG911 will be long, but fruitful -- anonymous

  13. NENA NG9-1-1: What Do I Definitely Need Now? Nate Wilcox

  14. All kinds of stuff to pick from • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  15. Initial questions to ask (Asked after setting reliability and security standards for the system) • Where am I getting my calls from? • Will I be using NG capable PSAP CPE? • How good is my GIS data? • What can I afford? • What kind of talent do I have on staff?

  16. Where am I getting my calls from? Legacy SR.. • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  17. Will I be using NG capable CPE? Yes • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  18. How good is my GIS data? Crappy • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  19. What can I afford? Not a lot • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  20. What kind of talent do I have on staff? IT talent • BCF • SBC • Firewall • LNG • PIF • LIF • NIF • ESRP • PRF • ECRF • LVF • LPG • PIF • LIF • NIF • LIS • LSRG • PIF • LIF • NIF • GISData Provisioning • Geocoded • Point data • Transport • Existing • New • Staff • Existing • Contractor

  21. Additional questions • How many PSAPs will be on the system? • What sort of data requirements will my PSAPs need? • How progressive are the telecom service providers in my area? • What do I want to do in the future? • Why am I really moving to NG9-1-1?

  22. NENA NG9-1-1Standards Roger Hixson

  23. The Operational Impacts (So Far) Bob Gasper, Tech Support Mgr.State of Maine

  24. Maine Overview • 1.25 Million Population • Statewide 911 system (since 2001) • 26 PSAPs • 4 State • 14 County • 8 Municipal/Regional

  25. Maine Overview • State staff of 9 • 911 Advisory Council • Surcharge 45¢ per month for wireline, wireless and VoIP; 45¢ point of sale prepaid per transaction • 911 contract, training, EMD and state admin staff • NG911 Project cost: $32 million over 6½ years

  26. Next Gen Data Preparation • 1995 – 911 Addressing at State level • 2006 – MSAG/GIS SAG Compare • 2009 – GIS served up to PSAPs for mapping • 2009 – Transferred MSAG change control to GIS from 911 database provider • Participated in GIS standards development and built adjusted data layers accordingly • 2013 – Centralized GIS services within the State

  27. Next Generation Planning • Jan 2011 – Developed “Plan for Next Generation 911” • Aug 2011 – Issued an RFP for Statewide NG911 • Feb 2013 – Signed a contract with FairPoint Communications(begin 18 mos)

  28. Maine NG 911 Project • End-to-end replacement of State’s E911 system • Existing equipment at end of useful life • Prime contractor, FairPoint, responsible for all components of the system from the CPE through the core, training, system monitoring and 24x7 repair • Based on NENA i3 standards • Contract requires all PSAPs (26) converted by August 2014 (18 months)

  29. Overall System Design • Fairpoint Communications • PM and IT Design/Data Center Services • Primary Support and Training • Partnered with: • Solacom – LSRG, ESRP/PRF and PSAP CPE • 9-1-1 Datamaster – ALI/LIS • GeoComm – GIS, ECRF, LVF & PSAP Mapping

  30. Migration Steps and Timeline • Turn-up, test and accept core network – 6 months • Core network includes: • Data centers housing the ESRP/PRF(s), ECRF/LVF(s), LSRG(s), BCF(s) and ALI/LIS(s) • Migrating all PSAPs to a new legacy ALI platform (ALI/LIS) • Building out core network between data centers • Turning up the training center at Vassalboro (14 positions) • Commence building out network (complete network build out took approximately 11 months)

  31. Migration Steps and Timeline • Continued testing and “soak” – 2 months +/- • Build-out, testing/transition & training for all PSAPs • Final system soak – 30 days +/-

  32. GIS Transition to NG911 • 1999 – RCL maintenance • 2004 – PSAP mapping support • 2012 – Address point development • NG Analysis • Analysis • NG Attribute development

  33. New Roles for GIS Personnel • Higher degree of maintenance requirements • Criticality of edits • Web based Change Request and editing • Criticality of discrepancy report process • Change Requests • Municipal and PSAP • Provisioning – Daily • QC Processes • Discrepancy reports • Updated Daily (per business day)

  34. Call Taker Training • Fairpoint responsible for transition training • Built a PSAP to be used exclusively for training; takes live calls of all different types • 475 call takers will go through one day of transition training • 2/3 day Solacom Guardian • 1/3 day GeoComm GeoLynx • Training required to deliver within 2 weeks of PSAP conversion

  35. Impact on Call Takers Legacy System NG911 Map provides the selective transfer information based on the location of the caller Core services means less local customization; more global settings Calls will roll to another PSAP based on a global time setting or if all call takers are logged out or not ready Speed can be done globally and locally • Map was static – provided location of callers • Functionality could be customized for PSAPs • Speed dials and call taker logins managed locally • Calls did not roll from one PSAP to another; busy out needed to be done by service response center

  36. Impact on State Staff Defining new roles and responsibilities Legacy E911 Database Manager Service provider changes Adding new call taker log ins Paperless location error reporting Reviewing automated error logs • GIS Staff moved to ESCB last year • GIS is not a project but a critical component • GIS used to be a daytime job but now needs to be on call – cultural shift

  37. Central Core Approach • Facilitates standardization (consensus on desktop layout) • Problem discovery is quicker (pattern recognition, everybody has same problem) • Problem resolution is quicker • Implementation of system patches or updates is quicker • Less need for LEC technicians at the PSAP • Ability to attach call recording to the call record in MIS system • Much lighter backroom space/equipment req’ts

  38. Other Considerations • VoIP calls sound different (no side tone) • Wireless Phase I calls will increase • Rolling Profiles for Call takers • Consider Administrative remote access • GIS driven system allows Selective Transfer capability on Wireless Phase 2 calls (COF value is critical) • System redundancy • Continue to hold PSAP meetings to solicit feedback

  39. Next Steps • Just the first step!!! • Last PSAP migrated to NG911 system on July 23rd • Long term - Migrate service providers from LNG to IP connections • Test and accept new technologies as they become available • Pass call record data onto responder(s) • Stay informed about i3 standards development

  40. PSAP Call taker Screen

  41. PSAP Call taker Map

  42. PSAP Mouse and Genovation Pad

  43. PSAP Back Room Equipment

  44. NENA NG9-1-1Progress Roger Hixson

  45. 2014 NENA Critical Issues Forum David Holl Deputy Director for Operations Pennsylvania Emergency Management Agency

  46. NENA 2014 CIFWireless Indoor Location John Snapp VP, Senior Technical Officer Intrado Inc

  47. Texting to 9-1-1 Experience Paul McLaren Director of Support EngineeringIntrado

  48. Deployment Experience • Initial trial in Blackhawk County, Iowa with iWireless – July 2009 • Architecture adopted by ATIS asJ-STD-110 • Launched live trials with Verizon Wireless using automatic Location • Trialed carrier aggregation in Vermont with AT&T, Sprint and VZW

  49. Deployment Process Decide on deployment approach • Deploy and conduct public education • Soft launch - deploy do not announce to public Choose initial technology • Integrated with CPE • Browser Based • SMS to TTY

More Related