the need for ng9-1-1

U.S. DOT Next Generation 9-1-1 Project: A National Framework and Deployment Plan

May 2009

Today’s 9-1-1 System – Timeline

2

Today’s 9-1-1 versus NG9-1-1

Today’s 9-1-1 Next Generation 9-1-1

Virtually all calls are voice callers via t l h l li

Voice, text, or video information, from t f i ti d itelephones over analog lines. many types of communication devices,

sent over IP networks

Most information transferred via voice Advanced data sharing is automatically f dperformed

Callers routed through legacy selective routers, limited forwarding / backup ability

Physical location of PSAP becomes immaterial, callers routed automatically based on geographic locationbackup ability based on geographic location, enhanced backup abilities

Limited ability to handle overflow situations, callers could receive a

PSAPs able to control call congestion treatment, including dynamically

33

situations, callers could receive a busy signal

treatment, including dynamically rerouting callers

USDOT NG9-1-1 Project

B k dBackground:Research and development project, funded by the USDOT’s Intelligent Transportation Systems (ITS) Joint Program Office (JPO), to define a NG9-1-1 system architecture and develop a transition planto define a NG9-1-1 system architecture and develop a transition plan that considers responsibilities, costs, schedule and benefits for deploying Internet Protocol (IP)-based emergency communications.

Long Term Goal:To enable the general public to make a 9-1-1 “call” (any real-time communication – voice, text, or video) from any wired, wireless, or co u cat o o ce, te t, o deo) o a y ed, e ess, oIP-based device, and allow first responders to take advantage of advanced real-time call delivery and data functions through new internetworking technologies based on open standards.

44

The Need For NG9-1-1

• Today’s 9-1-1 system is being outpaced by emerging technologies

– Constant adaptation of old 9-1-1 infrastructure is expensive and slowNew communications technologies need “plug and play” access– New communications technologies need plug and play access and interfaces

– Growing data rich environment – 9-1-1 can’t handleN d d t b d idth d i d t k (IP) t d d– Need data bandwidth, modernized network (IP), open standards

5

The Need For NG9-1-1, (con’t.)

• Today’s 9-1-1 system is being outpaced by emerging technologies

– Need a more flexible and easily controlled 9-1-1 system– Need nationwide and beyond intercommunication, including other

emergency services (transportation operations, emergency management, etc.)

– Post transition, NG9-1-1 can be significantly more efficient (and likely less expensive to implement new features)

6

Consensus within the 9-1-1 Community

Leveraged stakeholders throughout the community to build consensus

Capitalize on advances in technologies that provide:

Quicker and more accurate information Better and more useful forms of information (real-time text, images, video, and other data)More flexible, secure and robust Public Safety Answering Point (PSAP) operations

fIncreased sharing of data, resources, procedures, and standards Promotion of increased coordination and partnerships

77

NG9-1-1 Project Successes

System Architecture DevelopmentConcept of Operations Define functional requirementsDefine functional requirementsHigh-level architectural designProof of Concept (POC)Demonstration of selected requirements

Transition Analysis and PlanningPreliminary Analysis of Cost, Value and RiskTransition Issues ReportTransition Issues ReportFinal DocumentsArchitectureTransition Plan

8

Final Analysis of Cost, Value and Risk

Scope of the Proof of Concept

• Testing of Selected Requirements– Ability to receive voice, video, text (IM, SMS) and data– Support for deaf/hearing-impaired accessibility– Caller’s location identification– Transmitting telematics data– Transmitting telematics data

(Advanced Automatic Crash Notification) like speed, rollover status crash velocityrollover status, crash velocity

– Call routing based on caller’s location

9

– IP networking and securityAt NO time during the POC were 'live' calls used.

Proof of Concept: Results

• After separate testing in the laboratory and PSAPs, the total system was tested.

• Calls were processed through the complete system, recording the p g p y , gresults.

• Simple pass/fail system used to test functional requirements• A total of 116 functional requirements were tested using use case q g

scenarios. • In all, the project conducted 320 individual tests in the laboratories

and PSAP facilities, with 280 (87.5 percent) successfully passing the t t it itest criteria.

• All tests used POC equipment, systems, and test data, and at no time were live 9 1 1 calls handled on the POC system or test calls

10

time, were live 9-1-1 calls handled on the POC system or test calls sent to live 9-1-1 systems.

Human Machine Interface

Measures of Interest:

•Placement of Data on the Screen•Placement of Data on the Screen•Navigation Complexity •Screen Aesthetics•Data Format•Business Rule and Information Sharing

11

•Business Rule and Information Sharing Procedures

•Information Management

Transition Plan

• Cost, Value & Risk

• Transition IssuesF di • Strategies– Funding

– Operations– Standards & Technology

Strategies

• Options

Models– Governance & Policy– Education

D l t A h

• Models

• Deployment Approaches– Independent, Unilateral

(bottom up)

12

– Coordinated, Intergovernmental (top down)

NG9-1-1 Initiative Documents Available

http://www.its.dot.gov/NG911• Revised Concept of Operations• Functional RequirementsFunctional Requirements• Architecture Design• Preliminary Analysis of Cost, Value and Risk• Transition Issues Reportp• Human Machine Interface Display• Proof of Concept Deployment Plan• NG9-1-1 Transition Issues Report• Data Acquisition and Analysis Plan• Preliminary Transition Plan• Proof of Concept Testing Report

Fi l A l i f C t V l d Ri k

13

• Final Analysis of Cost, Value and Risk• Final Transition Plan

Additional Tasks

• Acquisition Tools• “What’s Next?” Forum• Big Cities Forum• Plugfest

Will be completed by Fall 2009

14

Results and Conclusions

• Substantial body of knowledge on the issues and associated strategic options that can be implemented

• An agenda for action and a foundation for the 9 1 1 community in• An agenda for action and a foundation for the 9-1-1 community in planning and deploying NG9-1-1

• The potential to provide significantly greater value than current 9-1-1 technology over the next 20 years1 technology over the next 20 years

• Many of the challenges are operational and logistical in nature, requiring a more open and collaborative relationship between stakeholdersstakeholders

• SO, with the end user (you) in mind -- what do you want?

15

After November 2008...

Requirements NationalRequirements

Standards

National

Transition Plan

Acquisition ToolsOfficeOffice

1616

• DOT / DOC – Joint Program

• Housed @ US DOT / NHTSA

Goals of National 9-1-1 Office

• Facilitate coordination among public and private stakeholders at local, State and Federal/national levels,

• Serve as an information clearinghouse• Administer grant program for the benefit of PSAPs

– $43.5 Million

P id F d l f f 9 1 1• Provide a Federal focus for 9-1-1• Promote and support 9-1-1 services

17

Contact Information:

NHTSA Contact:Laurie Flaherty

laurie.flaherty@dot.gov

NTIA Contact:Thomas Hardy

THardy@ntia.doc.govlaurie.flaherty@dot.gov(202) 366-2705

THardy@ntia.doc.gov(202) 482-1948

USDOT’s NG9-1-1 website: http://www.its.dot.gov/ng911/

National E-911 ICO website: http://www.e-911ico.gov

E-911 ICO Contact:nhtsa.national911@dot.gov

18

@ g(202) 366-3485