Beyond the 98%™Solving the GIS Puzzle in NG9-1-1

When seconds matter to you, data matters to us!

2

Our GOAL is to get the conversation started about GIS.

• The Basics of 9-1-1 and GIS terms and concepts.

• What are the standards and what’s your role?

• Best practices in getting ready for NG9-1-1 GIS.

• Introduction to validations that get “Beyond the 98%”

• Look at next steps you can take…

What’s on the Agenda?

3

PSAP

• Public Safety Answering Point

ESInet

• Emergency Service IP-Network

NGCS• Next Generation Core Services

ECRF

• Emergency Call Routing Function

LVF

• Location Validation Function

Acronym Definitions

MSAG

• Master Street Address Guide

ALI

• Automatic Location Information

LIS• Location Information Server

SI

• Spatial Interface

NENA

• National Emergency Number Association

4

• 9-1-1 Centers are also called Public Safety Answering Points (PSAP)

• Introduced in 1968• Enhanced 9-1-1 (E9-1-1) introduced in the early 1990s, and location

information began being delivered with the call using a database of Automatic Location Information (ALI) and its associated Master Street Address Guide (MSAG).

• Location identification is still heavily dependent upon the caller’s ability to verbally communicate where they were to the 9-1-1 calltaker.

• The ALI and MSAG remain the key element address verification, though the data in the two databases have known inaccurate and incomplete information.

• Next Generation 9-1-1 (NG9-1-1) will transition the ALI database and place the responsibility for maintenance and coordination of the MSAG on the 9-1-1 Authority (PSAP).

Important facts about 9-1-1

5

GIS Basics

6

The deliciousness lies in the way the

flavors work together!

Top Bun: BoundariesCucumbers: AnnotationVeggies: WaterwaysMeat: Address PointsSauces: StructuresVeggies: RoadsPickles: ParcelsBottom Bun: Aerial Photo

7

“A system designed to capture, store, manipulate, analyze, manage, and present all types of geographical data.”

• Key word is Geography – Meaning some portion of the data is spatial.

• In other words, data that is in some way referenced to locations on the earth.

What is a Geographic Information System or GIS?

8

• Spatial Data - data that is in some way referenced to locations on the earth.

• “Layers” which is a point, line, or polygon.

What’s the difference between spatial and non-spatial data?

GIS technologies are unique in their capability to

combine the two data sets

9

MSAG is a legacy 9-1-1 database defined by NENA 01-002 Master Glossary 02-03 as:

"a database of street names and house number ranges within their associated communities defining Emergency Service Zones (ESZs) and their associated Emergency Service Numbers (ESNs) to enable proper routing of 9-1-1 calls."

While the database includes location based information (address ranges, directional, street name, etc.), it DOESN’T include any spatial data.

Well what about my Master Street Address Guide (MSAG)???

10

ALI is a legacy 9-1-1 database defined by NENA 01-002 Master Glossary 02-03 as:

"The automatic display at the PSAP of the caller’s telephone number, the address/location of the telephone and supplementary emergency services information of the location from which a call originates.“

While the database includes location based information (house number, directional, street name, etc.), it DOESN’T include any spatial data.

Well what about my ALI (Automatic Location Information)???

CON

FIDE

NTI

AL

CON

FIDE

NTI

AL

11

• GIS has not been a core technology (i.e. mission critical) for public safety systems in the past

• Between new CAD technology and Next Generation 9-1-1 GIS will be mission critical

• Public Safety Systems supported by GIS• CAD• NG9-1-1 Call Routing• Situational Awareness Mapping Apps• Other operational apps (AVL, Crime Analysis, Warrant

Support, Predictive Analysis, etc.)

GIS in Public Safety

“You are hereby deputized as a member of the public safety community. We’ll be getting

you a vest soon!”

- Ty Wooten, NENA Director of Education

12

Next Generation 9-1-1

13

What does Next Generation 9-1-1 mean to you?

14

“Before she was fatally shot in a murder-suicide in front of the Plantation Police Department in April, Olidia Kerr Day called 9-1-1 from her cell phone and immediately reached a 9-1-1 operator – in the wrong city”.

- Broward County, Florida April 25, 2008

2008: Broward County, Florida

15

2018: Marjory Stoneman Douglas High School

“A cell tower stands in the middle of a city park, just across the street from the high school where 34 people were shot one year ago.”

“Every single 9-1-1 call from Majory Stoneman Douglas High School on February 14, 2018 went to Coral Springs Police. But Coral Springs does not provide police services to Parkland, and dispatchers transferred multiple calls for help to Broward County 9-1-1.”

- Broward County, Florida February 14, 2018

16

Location data is sourced from telecommunications companies.

Current State: 9-1-1 Today

17

Routing 9 -1-1 calls to appropriate public safety answering points (PSAPs) currently

does not use spatial data.

Current State: 9-1-1 Today

18

98% GIS data synchronization is deemed “acceptable.”

Current State: 9-1-1 Today

19

Represents a complete overhaul and redesign of the legacy 9 -1-1 system.

Future State: NG9-1-1

20

Shifts stakeholders from telecommunication companies to the 9 -1-1 authority, addressing authority( ies)

and GIS data providers.

Future State: NG9-1-1

21

Based on standardized and open databases and technology (i3 architecture).

Future State: NG9-1-1

22

Requires GIS data synchronization Beyond the 98%™

Future State: NG9-1-1

23

“Put simply, NG911 is an Internet Protocol (IP)-based system that allows digital information (e.g., voice,

photos, videos, text messages) to flow seamlessly from the public, through the 911 network, and on to

emergency responders”. US DOT

AT&T wrote a letter to FCC asking for

permission to phase out their analog landline service

Analog systems becoming under

utilized & expensive to

manage

Changing expectations of

public

Changing landscape of

communication devices

Why Next Gen?

Existing system is over 40 years old

Pieces & Parts: Legacy 9-1-1

Pieces & Parts: NG9-1-1

via SI

26

The NG9-1-1 Core Services Environment

Emergency Service IP Network (ESInet) – the network• ESInets are networks managed by local, regional, and/or state

entities• Networks can be multi-purpose, secure, and support extended

Public Safety communications services in addition to 9-1-1.• NG9-1-1 assumes that ESInets are hierarchical, or a `network of

networks’ in a tiered design approach to support local, regional, state and national emergency management authorities.

Location Information Server (LIS) – the subscriber database• an element maintained by originating service providers• functions similar to the ALI database to provide the location of the

911 caller

NG9-1-1 SystemsPieces & Parts: Next Generation Core Services (NGCS)

Location Validation Function (LVF) – pre-validates static location of the caller

• Valid “locations” are pre-verified against the GIS. Location errors are reported to the data authority for analysis and update.

• Will generate a discrepancy report for more than one unique location “found”

Emergency Call Routing Function (ECRF) – “Where do I send this call?”

• Determines the correct 911 call center to which the call is routed.• Spatial query on PSAP boundaries• “Validates” locations differently than LVF but uses same data.

• Road Cetnerlines• Address Points

Pieces & Parts: Next Generation Core Services (NGCS)

29

Pieces & Parts: How Core Service Use GIS Data

LVFAll LIS features must have a valid geospatial location

Only one unique representation of a civic location may be contained in address points or centerlines; no duplicates

Results in discrepancy reports

Forklift (no change detection), thus no persistent unique ID needed

ECRFUses GIS data in attempt to identify location of civic address

Can use business rules in a “policy store” to bypass addressing anomalies

Forklift (no change detection), thus no persistent unique ID needed

30

31

Be a Data Steward: identify and reduce silos

32

Be a Data Steward: create crosswalks

33

Be a Data Steward: create crosswalks

Address requested that’s

out of range

Research discrepancy and

determine on MSAG update

Make additions and updates as

needed

Adds new streets and

addressing into GIS

Updates addressing data as corrections are received

Sends updates and additions

to stakeholders

MSAG Coordinator workflow:

GIS Coordinator workflow:

34

It adds to the list of “who” the public safety stakeholders are in each locality.

NG9-1-1 is a Catalyst

Public Safety

Stakeholder

Fire

Police

EMS

9-1-1Public Works

Planning

GIS

IT

Public Safety

Stakeholder

Fire

Police

EMS

9-1-1

Roles & Responsibilities in NG9-1-1

Public Safety/9-1-1

* Primary PSAP* Responsible

Party

Addressing Authority

* Assigns addresses

GISData

Providers* Maintains GIS

Data

Public Safety GIS: Roles & Responsibilities

To Achieve Success, We Help Build CrosswalksIn most cases, the people that will be working together to achieve GIS readiness for NG9-1-1 are only barely aware of each other!

Public Safety GIS: Roles & Responsibilities

In some cases, the GIS and Addressing Authorities are working together but public safety and 9-1-1 are off to themselves

To Achieve Success, We Help Build CrosswalksPublic Safety GIS: Roles & Responsibilities

But these group must work together in order for NG9-1-1 to become a reality!

This requires experts who have exposure in all of these areas to help build crosswalks

This is where we bring the most value!

To Achieve Success, We Help Build CrosswalksPublic Safety GIS: Roles & Responsibilities

39

NG9-1-1: A Network of Networks

International

National

State

Regional

Sub-Regional/

Local

• Interconnected networks serve as redundant backups and cross-connection

• Provisioned spatial data will be rolled up at each level in order to route calls in case the sub-network failover

• Data maintenance and provisioning occurs at the most local level

40

PSAP-based• Self-contained• PSAP fills all 3 roles

Enterprise• 9-1-1 = PSAP• Adressing = Planning, Building, etc.• GIS = GIS, ISD, PW, etc.

Regional• Shared governance• Common aggregation platform

OR

NG9-1-1: Cooperation & Regionalization

41

GIS Data Implications

42

In 2009, NENA published an Information Document titled, Synchronizing Geographic Information System Databases with MSAG & ALI [71-501], • Designed to help agencies undertake synchronization of legacy

9-1-1 databases and GIS data for i2 architecture• A good starting point…• Does not produce NG9-1-1 ready GIS data

98% Synchronization as a measure?

43

We must move “Beyond the 98%”• Develop data towards i3 architecture• Address dimensions of data quality

beyond synchronization• Develop new layers (i.e. provisioning boundary, etc.)• Regionalize data governance and management

Error Resolution• NENA requires data error resolution within 3 business days• What does this mean for you?

98% Synchronization as a measure?

44

• Delays result from incorrect 9-1-1 call routing, difficulties in location verification and are life-threatening

• With NG9-1-1:• 98% synchronization accuracy in NENA’s recommendation for MSAG and

ALI databases alone does not produce “public safety grade” GIS data, but a start.

• At only 98% synchronization accuracy, errors may include:• PSAP boundary gaps and overlaps.• Missing road centerline breaks.• Duplication of address points.

• GIS data synchronization for NG9-1-1 must go beyond 98% for proper call routing.

• More in-depth spatial comparisons such as fish bone analyses are required for the NGCS (Next Generation Core Services).

Reconciliation of GIS Data is Life-Critical

45

Is data available?

Is all necessary data present?

Does data reflectthe real world?

Is the data available when it’s needed?

Is data consistent between systems? Records duplicated?

Dimensions of Data Quality

Minimum Spatial Data Required to Support ECRF/LVF in i3 NG9-1-1 Architecture* PSAP Boundaries

Road Centerlines

Emergency Services Boundaries

Address Points

Provisioning Boundaries

Source: “The 9-1-1 Authority is responsible for coordinated with local addressing authorities and GIS data providers for the provisioning of address data in a GIS format to the ECRF/LVF (ESInet).” NENA STA-005.11

Footprint: each PSAP needs access to a seamless, normalized and highly accurate footprint of data from any jurisdiction it shares a boundary with.

Update: new data and data errors should be updated in the GIS within a 3 business day cycle.

Accuracy: Each source entity is responsible for the accuracy (both spatial and attribution) of each dataset. This results in the need for coordination amongst neighboring jurisdictions as there are no allowable gaps, overlaps or redundancies in any of the datasets.

Required Datasets: Road Centerlines

• Required

• Edge-matched

• Split at PSAP Boundary

• No gaps, overlaps or duplicate centerlines

• Required

• Most precise call and resource routing

• Structure-based, sub-addresses where useful

• Includes non-addressed dispatchable locations

Required Datasets: Address Points

• Required

• Primary PSAP• Need footprints for

neighboring primary PSAPs

• No gaps, overlaps or duplicate polygons

Required Datasets: PSAP Boundary

• GIS data provider boundaries

• Geofence in Spatial Interface

Required Datasets: Provisioning Boundary

• Fire, Police, EMS Layers

• Not ESZ Layer• No gaps, overlaps or duplicates

Required Datasets: Emergency Service Boundaries

The Need for Order

The Need for Order• Ensure that road centerline can answer

the questions your MSAG can• If you trust your MSAG data, it can identify,

and provide, missing road information

The Need for Order• PSAP Boundaries: primary PSAP only,

“Where do you want the call routed?”• Emergency Service Boundaries: used

for secondary transfers, separate layer for Law, Fire, EMS, etc.

The Need for Order• Performs GIS data quality assurance• Considers GIS holistically: spatial

relationships between address points, road centerlines and boundaries

56

Location Data Validation: Fishbone Analysis

• Compares the “placed” address point with the geocoded address location by creating line geometry that connects the two

• This gives a rich data set for analysis. By analyzing for intersections with either other fishbone lines or intersecting road centerlines we find anomalies that reveal problem areas that may need remediation.

57

• Compares placed address point location to it’s geocoded position• Allows for an intersection analysis

• If another fishbone is intersected a placement or addressing issue likely exists

• If a street centerline is intersected a placed address is on the wrong street centerline

• The effort provides a valuable source of data to do other analysis

Location Data Validation: Fishbone Analysis

58

• Should not be necessary when subaddress information is added

• Maybe an indicator of problematic addressing, not just a GIS issue

Location Data Validation: Address Point Duplication

59

• Mismatched street name fields in both address points and road centerline

• This occurs due to: • street misspellings, • inconsistent directional, • inconsistent street types, or • potentially missing roads.

• It is important to have consistency between the centerline file and address point file before provisioning the data to an NG9-1-1 system.

Location Data Validation: Address Point Not Reflected in RCL

60

• Must determine if the addressing is accurately reflected in GIS

• Sometime the addressing is bad and the only fix is to change it…as if!

Location Data Validation: Address Point Misordered Along RCL

61

• In most cases direction of digitization wasn’t an important factor when GIS data was created

• In NG9-1-1 it’s critical because of the way an ECRF geocodes locations to determine routing, especially in boundary areas

Location Data Validation: RCL Digitized Direction

62

• Road Centerlines must reflect what routes out of MSAG today while accurately representing the real world

• Sometimes this indicates an MSAG fix, sometimes a GIS fix and other time both need fixing

Location Data Validation: MSAG Has No Matching RCL

The Need for Order• Your GIS should answer the questions

your ALI does currently• Identify and provide missing information

The Need for Order• Address and road data can change frequently• Data must be re-evaluated for data quality on

a purposeful cycle to ensure no errors are introduced and new data is entered properly

65

GIS Data Validation Considerations

66

Location Data Validation: Fishbone Analysis

67

• Road Centerline and Address Point parsing is based on the Civic Location Data eXchange Format (CLDXF) Standard [NENA-STA-004.1.1-2014]

• The CLDXF document was developed to: • Provide a definitive set of core civic location data elements that support

emergency call routing and dispatch. • Map a profile between Presence Information Data Format-Location

Object (PIDF-LO) and those same NENA core civic location data elements.

• Map those civic location data elements to the corresponding FGDC “United States Thoroughfare, Landmark, and Postal Address Data Standard” (FGDC-STD-016-2011) set of data elements, which was sponsored by the URISA and NENA.

• Provide illustrative examples of address parsing.

• Defines the detailed data elements needed for address data exchange.

NG9-1-1 GIS Data Model: Location Data Parsing Requirements

68

• Street Name Pre Modifier (e.g., “Alternate” in Alternate Route 8)

• Street Name Pre Directional (e.g., “North” in North Fairfax Drive)

• Street Name Pre Type (e.g., “Avenue” in Avenue A; “County Route” in County Route 88)

• Street Name Pre Type Separator (e.g., “of the” in Avenue of the Americas)

• Street Name (e.g., “Fairfax” in North Fairfax Avenue)

• Street Name Post Type (e.g., “Avenue” in North Fairfax Avenue)

• Street Name Post Directional (e.g., “East” in Seventh Street East)

• Street Name Post Modifier (e.g., “Extended” in East End Avenue Extended)

NG9-1-1 GIS Data Model: Location Data Parsing Requirements

8 Street Name Elements in NENA CLDXF Standard (Section 3.3)

69

• Address Number Prefix (alphanumeric prefix)

• Address Number (integer to support address sorting, parity definition and in/out of address range tests)

• Address Number Suffix (alphanumeric suffix, e.g., “1/2” in 119 ½ Elm St.)

• Optional: Milepost may be given in place of or in addition to the address number

NG9-1-1 GIS Data Model: Location Data Parsing Requirements

4 Address Number Elements in NENA CLDXF Standard (Section 3.4)

70

• Building (e.g. "Building A" in 456 Oak Street, Building A, Apartment 206)

• Additional Location Information (e.g. “West Wing” in 1600 Pennsylvania Avenue NW, West Wing)

• Floor (e.g. “Mezzanine” in 800 Jefferson Street, Mezzanine)

• Unit (e.g. “Suite 3103” in 4300 Flamingo Avenue, Suite 3103)

• Room ("Room 450F" in 1440 Market St., Room 450F)

• Seat (e.g. “Cubicle 23” in 2500 Seventh Street, Room 105, Cubicle 23)

NG9-1-1 GIS Data Model: Location Data Parsing Requirements

6 Subaddress Elements in NENA CLDXF Standard (Section 3.6)

71

This is an URGENT need!

• NG9-1-1 implementation is here, don’t let GIS data be the hold up!

• In a mature state NG9-1-1 system location data will be maintained in GIS!

• The 9-1-1 Authority is RESPONSIBLE to coordinate the maintenance and provisioning of locally-maintained, high-quality GIS data for call routing!

72

Development of Site/Structure Address Point GIS Data for 9-1-1[NENA-INF-014.1-2015]

NG9-1-1 GIS Data Model [NENA-STA-006.1-2018]

Provisioning and Maintenance of GIS data to ECRFs and LVFs [NENA-STA-005.1-2017]

NG9-1-1 Emergency Incident Data Document (EIDD) [APCO / NENA 2.105.1-2017]

United States Civic Location Data Exchange Format (CLDXF) Standard [NENA-STA-004.1.1-2014]

References

73

Florida E9-1-1 Revenue

Florida Rural County Grant Process

Florida State Grant Process

NTIA/NHTSA 911 Grant

F.S. 365.172 (10b) Rule 60FF1-5.002 Rule 60FF1-5.002 CDFA 20.615, 911 Grant Program

“GIS system and software

equipment”

Eligible expenses in accordance with F.S.

365.172 (10)

Eligible expenses in accordance with F.S.

365.172 (10)

State of Florida is expected to be awarded

$5,834,259

“Geographical data position, and

technical system maintenance,

database”

Section 6.3.2:“eligible mapping maintenance and warranty costs…”

Priority 4: Mapping system and services for

GIS (RCL and AP) and GIS data support

DMS has identified GIS as the grant scope of work –discussion has included a statewide GIS database

“Next generation E911 database

services”

Priority 5: GIS Centerline, point generation and map

services

Priority 6: NG9-1-1 Equipment and Services

Grant requires 40% state match which was

approved by the Senate

Funding Window:County Fiscal Year

Budget Process

Funding Window:April 1, 2020

October 1, 2020

Funding Window:TBA

Funding Window:Ongoing – Awaiting More

Information from DMS

In Florida: How do we fund these initiatives?

74

75

THANK YOU!!

Drew Fioranelli, GISP Drew.Fioranelli@mbakerintl.com

540-661-9307

Robert Murphy, ENP RPL Robert.Murphy@mbakerintl.com

412-512-4407