120 likes | 181 Views
Explore the timeline and significance of GIS in NG9-1-1 systems, emphasizing interoperability, data accuracy, and scalability for improved emergency response. Learn about standards and frameworks shaping the future of emergency services.
E N D
9-1-1 System – Timeline 1980s–90s: • Enhanced 9-1-1: • Calls are routed based on local jurisdictions 1968: VoIP Today: • NG9-1-1: • Any Device, Anytime, Anywhere 1990s – 2000s: • Basic 9-1-1: • Copper Land Line • Callers and PSAPs are fixed locations • Wireless 9-1-1: • Callers are nomadic and must first be located
Background / 9-1-1 Today • Existing 9-1-1 infrastructure was initially designed to do one thing – process emergency calls from a fixed location • Majority of calls for emergency service today are nomadic, from several different devices • NG9-1-1 environment cannot be reliant upon the legacy infrastructure
What is NG9-1-1? • Current 9-1-1 system is reliable, but based on antiquated technology • Limited ability to transfer and not designed for moving the data that is now a daily part of communications, such as text and images • NG9-1-1 is often considered a network, but it doesn’t stop there – it is the culmination of converging many applications into a common platform • NG9-1-1 is best described as an open-standard-based, robust system of systems, that allows the public to use any device to request help • It allows access from the legacy 9-1-1 system while allowing for greater interoperability • NG9-1-1 does not have a “chosen” or preferred entry point
GIS in NG9-1-1 • GIS plays crucial role in NG9-1-1 call routing • Routing database is GIS data centric • Accuracy of GIS data is paramount • Shared data – coordination • 9-1-1 authority is responsible for the data • Location is delivered with call • Location is pre-validated using GIS data (LVF)
GIS in NG9-1-1 • NG9-1-1 will require scalability for more data • Additional fields in database design • Structures: Floor, Room, Seat • Roads: More jurisdictional boundary fields, classifications, routing • Additional layers: Neighborhoods, unincorporated communities, more classifications for common places, parcels • More potential for interoperability with other systems • Healthcare, emergency management, industrial sites (HAZMAT) • Facility plans, large campuses
NG9-1-1 Improved Data Interoperability • Common Operation Picture (COP) Systems • Sensors, Cameras, Photos – all with location tags • 9-1-1 Centers, Emergency Operation Center, First Responders all using same GIS data • Improved data interoperability across local, state and federal agencies during large incidents • GIS Data Redundancy and Backup • Access to data outside of your jurisdiction • Other PSAPs can access your GIS data for dispatch during high call volume
Approach • Central 9-1-1 GIS Repository • Enable PSAPs to share GIS information • Establish MOAs • Set standards for GIS data entry • Set standards for regular maintenance plan • Future framework for NG9-1-1 database • Statewide SCL’s • Statewide PSAP Boundary Layer • Validation of GIS with MSAG, ALI
NENA Standards – GIS and NG9-1-1 • NENA – i3 Technical Specifications • NENA – GIS Data Model 2.0 • NENA – Synchronizing your GIS with MSAG and ALI • NENA – Provisioning GIS Data for ECRF/LVF • NENA – Site Structure Point Development
Questions Questions ?? Josh Clemente – PMP/ENP josh.clemente@lrkimball.com 814-574-9535 Mark Holmes – GISP/ENP mark.holmes@lrkimball.com 814-421-2210