1. What do YOU Really Need to Know?

2. Next Generation 9-1-1 Call Flow
NG9-1-1
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF
LVF SI
LIS– Location Information Server
ESRP– Emergency Services Routing Proxy
LVF – Location Validation Function
ECRF – Emergency Call Routing Function
CSP– Communications Service Provider i3
PSAP
GIS
SI – Spatial Interface
GIS DBMS
Simplified for presentation

3. Next Generation 9-1-1 - Call Flow
NG9-1-1
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF v1
Detailed Functional and Interface Specifications for NENA i3 Solution – Stage 3
v2 under development
REQ 002
NG9-1-1 Data Management
Public Review
LVF SI i3
PSAP
GIS
GIS DBMS
Simplified for presentation

4. 08-003 v1 Detailed Functional and Interface Specifications for NENA i3 Solution Stage 3
Describes how NG works after transition
Detailed functional and external interfaces to NG9-1-1 functional elements
Includes gateways for legacy wireline and wireless origination networks
V2 currently addressing all committee review
Revised Standard will use new NENA numbering schema STA-010

5. REQ-002 - NG9-1-1 Data Management
Guidelines for communicating issues or status of various elements
Issues related to GIS-related errors
Minimum report content requirements
Timeframe for error resolution timeframe
Discrepancy Report
Gap/Overlap in Boundary Layers
Performance Statistics
GIS Data Provisioning Performance Statistics Report

6. GIS Data ESRP CSP LIS ECRF LVF SI GIS GIS DBMS 02-014 v1
GIS Data Collections and Maintenance Standards v1
Synchronizing GIS Databases with MSAG and ALI
INF-014
Development of Site/Structure Address Point GIS Data for 9-1-1
STA-006
Standard for NG9-1-1 GIS Data Model
STA
Next Generation (NG9-1-1) United States Civic Location Data Exchange Format (CLDXF) Standard
NG9-1-1
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF
LVF SI i3
PSAP
GIS
GIS DBMS

7. 02-014 v1 GIS Data Collections and Maintenance Standards
Ensure the accuracy and integrity of the GIS data collected and maintained for use in PSAPs and data bases
Maintenance issues
Maintenance across data layers
GPS equipment recommendations (spatial accuracy)

8. 71-501 v1 Synchronization GIS database with - MSAG and ALI
Informational document
Ensure attribute accuracy for functions
Recommended analysis processes
Recommended error resolution process
98% synchronization between all databases for NG9-1-1 (MSAG, ALI, GIS)

9. INF-014 Development of Site/Structure Address Point GIS Data for 9-1-1
Workgroup completed – Published 9/30/2015
Address point placement methodologies for 9-1-1
Best practices
Takes into account NG9-1-1 functionality

10. STA-006 NG9-1-1 GIS Data Model
All Committee review comments
Support location information conveyed in the PIDF-LO
Support NG9-1-1 systems, databases, call routing, call handling, and related processes
Required layers
Authoritative Boundary
Road Centerline
Emergency Service Boundary(s)
PSAP Boundary(s)
Standardized data fields

11. STA CLDXF Standard
Set of core civic location data elements that support call routing and dispatch.
Profile between PIDF-LO and those same NENA core civic location data elements.
Provides illustrative examples of address parsing.
Defines civic location data elements corresponding to the Federal Geographic Data Committee, United States Thoroughfare, Landmark, and Postal Address Data Standard, Document Number FGDC-STD set of data elements
Sponsored by the Urban and Regional Information Systems Association (URISA) and the National Emergency Number Association (NENA).

12. Provisioning GIS Data STA-005
Standards for the Provisioning and Maintenance of GIS data to ECRF/LVF
Public Review
NG9-1-1
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF
LVF SI i3
PSAP
GIS
GIS DBMS

13. SI – Spatial Interface (Formally the Spatial Information Function)
Provisions Standardized GIS data into the ECRF and LVF
The SI could be
Built into a GIS system
A stand-alone element with propriety interfaces into GIS systems

14. Operational processes and procedures to support i3 ECRF and LVF
Standards for the Provisioning and Maintenance of GIS data to ECRF/LVF STA-005
Stable Form Notice
Operational processes and procedures to support i3 ECRF and LVF
GIS data requirements
QA/QC
Ownership, sharing and distribution
Provisioning Standardized GIS data to ECRF/LVF
Deployment considerations

15. ESRP checks Policy Routing prior to sending to PSAP
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF
STA
NG9-1-1 Policy Routing Rules
INF
Policy Routing Rules Operations Guide
LVF SI i3
PSAP
GIS
GIS DBMS

16. STA-003.1.1- 2014 NG9-1-1 Policy Routing Rules
Allows a variety of Policy Rules for call routing
Backup PSAP Overflow Call Queue
Time of Day Language Off Line Default
INF
Policy Routing Rules Operations Guide
Assist Authorities in development and use of PRR

17. Additional Data 71-001 v1 NG9-1-1 Additional Data Standard Device
Call (i3)
ESRP
CSP
ESInet
LIS
ECRF v1
NG9-1-1 Additional Data Standard
Device
Caller
Location
LVF SI i3
PSAP
GIS
GIS DBMS
Simplified for presentation

18. 71-001 v1 NG9-1-1 Additional Data Standard
Three types of data
Device
Caller
Location
Accessible existing data
GIS support data

19. NG9-1-1 Call Flow Pageant

20. ACRONYMS!

21. NG9-1-1 & GIS 9-1-1 Authority GIS Data ESInet Border Control Function
Location Information Server
(LIS)
Location Validation Function
(LVF)
Spatial Interface
(SI)
Legacy Network Gateway
(LNG)
Emergency Call Routing Function (ECRF)
ESInet
Border Control Function
(BCF)
Emergency Services Routing Proxy
(ESRP)
PSAP
Mapping
PRF

22. Service Uniform Resource Name
nena:service:sos

23. Presence Information Data Format – Location Object
<civicAddress xml:lang=”en-US” xmlns=”urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr”>
<country>US</country>
<A1>TX</A1>
<A3>Austin</A3>
<A6>Main</A3>
<STS>Street</STS>
<HNO>911</HNO>
</civicAddress>

24. Location-to-Service Translation
<?xml version="1.0" encoding="UTF-8"?> <findService xmlns="urn:ietf:params:xml:ns:lost1" recursive="true" serviceBoundary="value"> <location id="627b8bf819d0bcd4d" profile="civic"> <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> <country>US</country> <A1>TX</A1> <A3>Austin</A3> <RD>Main</RD> <STS>Street</STS> <HNO>911</HNO> </civicAddress> </location> <service>urn:service:sos</service> </findService>

25. Route Uniform Resource Identifier

26. Act I: GIS Data Provisioning
Here’s your GIS Data
GIS Data is created and maintained at the local level
BCF
ESRP
LVF
PSAP
ECRF
Map
Local Government/ Authority GIS Data
Spatial Interface (SI)
SI – Spatial Interface
Provides an interface between an authoritative copy of GIS data and Functional Elements within the ESInet
Nearly all location related data is derived from the SI. SI supplies data for the ECRF/LVF and map views for alternate PSAPs
Provisioned by the Authority, or other government agencies
Two primary things done by the Spatial Interface:
Projection – WGS 84
Layer replication – WFS + ATOM GeoRSS feed

27. Act II: Location Validation
Location Information Server
(LIS)
Location Validation Function
(LVF)
Spatial Interface
(SI)
9-1-1 Authority
GIS Data
Is this a valid location in GIS?
YES or NO
Emergency Call Routing Function (ECRF)
LVF – Location Validation Function
Pre-validation, validates before loading to the LIS database
Similar to MSAG, verifies that the civic location matches a known address in the Authorities service area
Able to validate to an address, not just address range
Receives as input: PIDF-LO and service URN – Returns: location validation
Queried by LoST protocol
LIS – Location Information Server
Calling devices query the LIS
Civic addresses are validated prior to being stored in the LIS by the LVF – validated against the GIS
Returns a PIDF-LO (Presence Information Data Format – Location Object) – can be a civic address or a geo-coordinate

28. Act III: Geospatial Call Routing
Location Validation Function
(LVF)
ESRP – Emergency Services Routing Proxy
Call routing engine
Closest thing to a selective router in NG9-1-1
Uses the ECRF(GIS) to choose how to route a call
Spatial Interface
(SI)
9-1-1 Authority
GIS Data
Emergency Call Routing Function (ECRF)
ECRF – Emergency Call Routing Function
Provides GIS based Next Generation call routing
Replaces legacy selective router databases
Allows for alternate dynamic call routing
Receives as input: PIDF-LO and service URN– returns –route URI
Queried by LoST protocol
Emergency Services Routing Proxy
(ESRP)
PSAP
Mapping
PRF
Route to PSAP A
Where do I route the call?

29. Discussion – Questions – Concerns

30. How to Cover Your Attributes

31. GIS Data Model Issues

32. GIS Data Stewardship WG

33. Today
Background
Purpose
Goal
Topics

34. GIS and NG9-1-1
It’s not just about map display anymore

35. GIS in NG9-1-1 recap Location Validation Geospatial Call Routing
Confirming/validating emergency caller’s location
Display emergency caller’s location on a map
Provide vehicular routing

36. GIS Data provisioned by the Spatial Interface
Road Centerline - Required
Emergency Services Boundaries- Required
Authoritative Boundary- Required
Address Points – Strongly Recommended
Optional GIS Dataset for ECRF/LVF – can be useful to particular ECRF/LVF implementations to facilitate the URI mapping of invalid or incomplete civic location
States or Equivalents – Strongly Recommended
Counties or Equivalents – Strongly Recommended
Municipal Boundary – Strongly Recommended

37. NENA GIS Documents
~20Published GIS related Documents or documents that mention GIS
Recently Published: Site/Structure Address Point
4 in Workgroup Development
GIS Data Model
ECRF/LVF Provisioning of data
Version 2 of i3 document

38. DATA STRUCTURES & MANAGEMENT DOCUMENTS (including NG9-1-1)
Category
Doc Number
Doc Name
Committee
Approved Date
DATA STRUCTURES & MANAGEMENT DOCUMENTS (including NG9-1-1)
Legacy
02-010
Standard Legacy Data Formats For Data Exchange GIS Mapping
Core Services
3/28/2011
02-014
GIS Data Collection and Maintenance Standards
6/17/2007
71-501
Synchronizing Geographic Information System Databases with MSAG & ALI Information Document
9/8/2009
NG9-1-1
NENA-STA
NENA Next Generation United States Civic Location Data
3/23/2014
Exchange Format (CLDXF)
NG9-1-1 TRANSITION PLANNING DOCUMENTS
NENA-INF (originally )
NG9-1-1 Transition Plan Considerations Information Document
NG Transition Planning
11/20/2013
NEXT GENERATION (NG9-1-1) DOCUMENTS
08-003
Detailed Functional and Interface Standards for the NENA i3 Solution
Interconnection & Security
6/14/2011
08-751
NENA i3 Requirements Document
9/28/2006
08-752
Location Information to Support IP-Based Emergency Services Requirements Document
12/21/2006
NENA-INF
NG9-1-1 Planning Guidelines Information Document
NG Project Lead Team
1/8/2014
NENA-INF
Requirements for a National Forest Guide Information Document
8/14/2014
PSAP OPERATIONS - CONTINGENCY PLANNING
53-001
Communications Center/PSAP Disaster and Contingency Plans Model Recommendation & Evacuation Checklist
PSAP Operations
6/7/2005
PSAP OPERATIONS - STANDARD OPERATING PROCEDURES
56-007
Pipeline Emergency Operations Standard/Model Recommendation
11/11/2010
56-503
Wide Area / Statewide Emergency Notification Systems Information Document
6/6/2006
56-507
Railroad & PSAP Interaction Information Document
4/28/2009
WIRELESS INTEGRATION DOCUMENTS
57-001
Wireless E9-1-1 Overflow, Default and Diverse Routing Standard & A PSAP Managers’ Guide to GIS & Wireless 9-1-1
11/18/2004
57-002
E9-1-1 Wireless Maintenance Call Routing & Testing Validation Standard including Call Routing & Testing Validation Worksheet & Sample Non-Disclosure Agreement
6/9/2007
57-501
Wireless Phase I & II Features and Functions Information Document
1/20/2003
57-502
Wireless Phase I/II Planning and Implementation Checklist and Modules Information Document including Service Agreements
5/24/2004
60-601
Model Baseline Guidelines for Drafting Statutes or Rules Associated with Prepaid Wireless Service and Emergency Service Fees Information Document
Regulatory/ Legislative
9/24/2008

39. Description of Problem or Opportunity
The GIS data and functionality requirements for Next Generation are qualitatively different than those needed for paper maps or for digital map displays. NENA’s current GIS standards document (NENA – NENA GIS Data Collection and Maintenance Standards) does not provide sufficient guidance on how to create and maintain GIS data for Next Generation processes and functionality. While it is likely that NENA may be useful for Enhanced environments, we propose that NENA form a workgroup to develop a new document that focuses on GIS data requirements for Next Generation and the practices needed to satisfy those requirements.

40. Expected Outcome /Proposed Solution
Create a workgroup to develop an informational document that provides guidance on GIS Stewardship with a clear and specific focus on GIS data that will be used by NG9-1-1 Core Services to validate and route calls.

41. GIS Data Stewardship
Deals with establishing requirements and assessing the data fitness for use
Ensure that data meets process needs
Ensures data documentation - metadata

42. Potential Topics to Include
GIS Database Development
Quality Assurance/Quality Control
GIS Data Maintenance and Stewardship

43. GIS Database Development
GIS Database Development – layers to be provisioned by the Spatial Interface for geospatial call routing and location validation
Best Management Practices for GIS layer development
Topological relationships
Accuracy and Precision recommendations for GIS feature development
Source data considerations for data development

44. QA/QC Quality Assurance/Quality Control
GIS Data Development and Management
NG9-1-1 Discrepancy and Error Reporting

45. GIS Data Maintenance GIS Data Maintenance and Stewardship
Jurisdictional boundary concerns and implications
Completeness and timeliness of data
Guidelines for gap/overlap detection
Roadmap for process improvement

46. Correcting the Gap: The Discrepancies of NG9-1-1 Data Management

47. NG9-1-1 Discrepancy Report Turn-around Times
Resolution
LIS validating records against the Location Validation Function (LVF)
3 Business
Days
Spatial Interface (SI) Operator to Authority on provisioning Geographic Information Systems (GIS) data
ECRF/LVF Operator to SI Operator on GIS data provisioning
1 Business
Day
ECRF/LVF Operator to Discrepancy Report (DR) Subscribers on GIS gaps and overlaps

48. NG9-1-1 Discrepancy Report Turn-around Times
Resolution
PSAP/Entity to Authority on misroute to their PSAP/Entity
1 Business Day
PSAP/9-1-1 Authority to the GIS Provider when issues found in the map display
Based on Criticality
Forest Guide Operator to Contributing ECRF Node Operator on provisioning coverage data
3 Business
Days

49. Discrepancy Report Required Content
Common descriptive elements (aka its “prolog”)
Time Stamp of Discrepancy Submittal
Discrepancy Report ID
Discrepancy reporting agency domain name
Discrepancy reporting agent user ID
Discrepancy reporting agency contact info
Service or Instance in which the discrepancy exists
Additional notes/comments
Discrepancy Service or Database specifics
Reporting Agency’s assessment of severity (as noted in STA-010)

50. Discrepancy Report Required Content
Additional content about the discrepancy
Query that generated the discrepancy
Full response of the query that generated the discrepancy (Message ID, Result Code, etc.)
What the reporting agency thinks is wrong
What the reporting agency thinks is the correct response, if available

51. Example: Service Boundary Gaps and Overlaps

52. ECRF/LVF Gap/Overlap Discrepancy Report Example Content
Time Stamp of Discrepancy Submittal
T12: :00
Discrepancy Report ID
a56e556d871
Discrepancy reporting agency domain name
N/A – the ECRF/LVF is an element
Discrepancy reporting agent user ID
Discrepancy reporting agency contact info
vCard of contact about this report
Service or Instance in which the discrepancy exists
ecrf.state.pa.us
Additional notes/comments
During GIS data provisioning, the ECRF detected an overlap between Zone 45 and Zone 46.
Discrepancy Service or Database specifics
GIS features that overlap including a polygon representation of the overlap
Reporting Agency’s assessment of severity
High

53. ECRF/LVF Gap/Overlap Discrepancy Report Example Content
Query that generated the discrepancy
N/A – since it occurred during provisioning
Full response of the query that generated the discrepancy
What the reporting agency thinks is wrong
An overlap of square meters exists between urn:nena:service:sos.psap Zone 46 (feature and Zone 45 (feature
What the reporting agency thinks is the correct response
Eliminate the overlap

54. Extra Slides that may be used in development discussions

55. NENA 2008 Breakout Session Template
What is Next Generation 9-1-1
Procedures
+ Databases
+ Spatial Routing
+ i3 Architecture
+ ESInet
= NG9-1-1

56. Next Generation 9-1-1 ESInet SI LVF BCF LIS ECRF BCF i3 PSAP ESRP GIS
Originating
Networks
GIS Data Management
LVF SI
GIS
GIS
VoIP
Cellular
PSTN
Enterprise
ESInet
GIS
BCF
LIS
ECRF
BCF
E9-1-1
Gateway i3
PSAP
ESRP SR
Gateway
Legacy
PSAP
Gateway
Legacy
PSAPs
Legacy E9-1-1
Networks
Legacy
Selective
Router
This figure is simplified for illustrative purposes

57. NENA 2008 Breakout Session Template
NG9-1-1 Call flow
1) LIS location sent to ECRF:
354 W 44th St, Houston, TX
2) ECRF finds address point of:
354 W 44th St, Houston, TX
3) ECRF determines Location is within the Houston PSAP
ECRF
4) ECRF sends Houston PSAP URI to the ESRP
psap.houston.tx.us 3
Location + PSAP URI
Location + Service Identifier URN
dial 9-1-1
PIDF-LO + URN: urn:service:sos
PIDF-LO + PSAP URI 4
ESRP
Voice
Text
Video

58. NENA 2008 Breakout Session Template
Spatial Interface- SI
Certain GIS data layers will become the core databases within NG9-1-1
These core GIS data layers will be provisioned into the LVF to provide location validation
These same GIS data layers are also provisioned to the ECRF and routing of 9-1-1
This GIS data layers must meet the highly standardized data requirements and strict data integrity and data quality demands
The Spatial Interface is the NG9-1-1 functional element responsible for validating these needs and the provisioning of the GIS data into the LVF and ECRF

59. Discrepancy Reporting
LIS – Record invalid against the LIS / SP incorrectly provisioning records
LVF – Validations, partial validation and invalid records by SP
ECRF – Same as LVF / Gaps and Overlaps in provisioned data / garbled queries from ESRP
ESRP – BFC handoff issue, ECRF input / return issues/ PRG issues
PRF – Malformed Policies / Illogical Policies
BCF - invalid, unusual, inconsistent, or improper incoming data
SI – Authority improperly provisioning data
Legacy recorders support limited input types: telephone and radio inputs, and limited data inputs like ANI/ALI. Some support TTY/TDD, screen capture, and video feeds. All have proprietary interfaces for search, retrieval, and reproduction.
An NG Logging Service supports many input types. Most are delivered via SIP. All significant processing events are delivered via Web Service interface (routing decisions, location queries/responses, etc.). All inputs within scope of NG are delivered over IP. Out-of-scope inputs may be delivered via traditional means (legacy radio/telephone, admin phones, agency s, etc.)

60. Discrepancy Reporting – Minimum Contents
Time Stamp of Discrepancy Submittal
Discrepancy Report ID
Discrepancy reporting agency domain name
Discrepancy reporting agent user ID
Discrepancy reporting agency contact info
Additional Information
Service or Instance in which the discrepancy exists
Discrepancy Service or Database specifics Additional Info
Additional notes/comments
Query that generated the discrepancy
Full response of the query that generated the discrepancy (Message ID, Result Code, etc.)
What the reporting agency thinks is wrong
What the reporting agency thinks is the correct response, if available
Legacy recorders support limited input types: telephone and radio inputs, and limited data inputs like ANI/ALI. Some support TTY/TDD, screen capture, and video feeds. All have proprietary interfaces for search, retrieval, and reproduction.
An NG Logging Service supports many input types. Most are delivered via SIP. All significant processing events are delivered via Web Service interface (routing decisions, location queries/responses, etc.). All inputs within scope of NG are delivered over IP. Out-of-scope inputs may be delivered via traditional means (legacy radio/telephone, admin phones, agency s, etc.)

61. NENA 2008 Breakout Session Template