# Presentation: 091693

## FCC Speaker Series

- U.S. Department of Transportation
- 9-1-1 Programs & Projects
- Laurie Flaherty
- October 22, 2008

## 9-1-1:  Why DOT?

- 40 Year history of Federal support for Emergency  	Medical Services (EMS) and 9-1-1
- 2002 – Secretary Norman Y. Mineta
-   E9-1-1 Steering Council
-   Priority Action Plan
-   Technology Innovation Roundtable
-   Genesis for NG9-1-1 Initiative
- 2004 - ENHANCE 9-1-1 Act
- National 9-1-1 Office  [P.L. 108-494]

## The Current 9-1-1 Network

## Problem Statement

**Problem Statement**

**Notes:**
In today’s world of emergency communications, first responders often don’t have the information they need.

Starting with the first 9-1-1 call for help, there is useful, actionable information that is not transmitted 
(e.g., location – rural, we don’t know a crash has occurred; urban, we get 50 calls for the same crash)

Whether it’s a natural disaster, a bridge collapse, or an everyday occurrence like a car crash, the result is the same:  responders are going in uninformed, and it takes more time to assess, to act and to clear these incidents.

## NG9-1-1 Initiative

** **

**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 Internet Protocol (IP)-based device, to the PSAP, and enable data sharing with the emergency communication network.
**Major Milestones:****	**
- National architecture and high-level design for NG9-1-1 System
- Proof of Concept Demonstration
- Transition plan for NG9-1-1 implementation

**Notes:**
[read goal and major milestones.]

The NG9-1-1 Initiative will provide a blueprint and a plan for deploying advanced technology in delivery of 9-1-1 calls

The scope of this project is the delivery of the 9-1-1 call to the PSAP. Does not involve transmission of information beyond the PSAP.
(NOT a deployment project...not an FOT . . .). 
Three major portions to the Next Generation 9-1-1 Initiative:

## Intelligent Transportation SystemJoint Program Office

- Located in the U.S. Department of Transportation’s Research and Innovative Technology Administration (RITA), the Intelligent Transportation Systems (ITS) program researches ways that communication and electronic technologies can improve surface transportation safety and mobility and contribute to America’s economic growth.
- The Federal ITS Joint Program Office (JPO) supports the overall advancement of ITS through investments in major initiatives, exploratory studies and a deployment support program.

## NG9-1-1 Initiative

** **

| Today’s 9-1-1 | Next Generation 9-1-1  |
| --- | --- |
| Primarily voice calls via telephones | Voice, text, or video information, from many types of communication devices |
| Minimal data available | Advanced data sharing is automatically performed |
| PSAP services – access, transfer, backup – are local only | Enhanced “long distance” capabilities; physical location of PSAP becomes immaterial |
| Limited capability for emergency notification | Location-specific emergency alerts possible for any networked device |

**Notes:**
This table compares today’s 9-1-1 with the Next Generation of 9-1-1:

Today, all information is transmitted by voice, from the caller to the call-taker.
In NG9-1-1, it is possible to transmit voice, text messages, photos, and video.
Today, there is minimal ability to transmit data.
In NG9-1-1, it is possible to transmit data sets, e.g,. Telematics data, to the PSAP and on to first responders.
Today, PSAPs are local operations with very little ability for backup, for either overload or a nonfunctioning PSAP (as a result of natural or man-made disaster)
In NG9-1-1, PSAPs can transfer calls to a another PSAP, if they’re overloaded with calls, or become nonfunctional for whatever reason.
Today, there is little or no capability for emergency notification.
In NG9-1-1, location-specific emergency alerts are possible, for incidents like hazmat situations or evacuation because of weather.

## NG9-1-1 Initiative Roadmap

**Proof-of-Concept**

**Transition Plan**

**Stakeholder Engagement**

**Preliminary Engineering**

**System Architecture**

**Preliminary**
**Transition Plan **

**Tech Transfer**

**NG9-1-1 Initiative Roadmap**

**FY07**

**FY08**

**FY09**

**Notes:**
This slide depicts all of the activities included in the NG9-1-1 Initiative.  USDOT activities are in blue.  The green boxes depict the contractor tasks which will complete the milestones and achieve the ultimate goal of the initiative.

Stakeholder Engagement – This project has expressly solicited the input of a variety of stakeholders from the beginning.  We’ve branded it and spent the last two years reaching out to any and all appropriate stakeholders.
Several reasons for this:  1) We’re not starting from scratch.  A lot of work has been done in both the public and private sectors in the area of emergency communications and specifically 9-1-1.  One of our goals has been to include and leverage NG9-1-1 work that has already been done previously by USDOT, by FCC, private sector, and in local pockets, 2) To leverage previous USDOT 9-1-1 and telematics relationships, and 3) To make sure that the design and the transition plan make sense and get buy-in from the stakeholders who will ultimately deploy this network.  A later slide will describe who the stakeholders are, 4) To make sure we are coordinating efforts.

Preliminary Engineering:  US DOT did an RFI, to ask stakeholders what should be included in this project.  Next, we developed a preliminary Concept of Operations document, to describe the Next Generation of 9-1-1 from the 50,000 foot level.  Last, we completed a competitive RFP, and a contract was awarded to the BAH team on December 4th of 2006 and the kick-off meeting for the project was conducted on December 19th.

The Team is headed by the firm of Booz Allen Hamilton, and also includes the National Emergency Number Association (describe NENA as an org.), the L Robert Kimball company (ditto) and Texas A& M.  This team is responsible for the tasks in green. 

As you can see, the timeline for this project is very ambitious.  The contract requires all deliverables to be completed by the end of the 2008 calendar year.  We are half-way thru the period of performance.

## The Stakeholders

## NG9-1-1 Initiative Status 

**NG9-1-1 Initiative Status**** **

**Task 1: System Architecture Development**
- Revised Concept of Operations (ConOps)
- Define functional requirements (High-level & Detailed)
- Architecture design
**Task 2: Transition Analysis**
- 	Cost / benefit analysis
- 	Identification of critical system deployment issues
**Task 3: Design and Demonstration of “Proof-of-Concept”**
- 	Design, develop, and demonstrate “Proof-of-Concept”
**Task 4:  Completion of Transition Plan and Final Architecture****	****	**

## Tasks of the NG9-1-1 Project  Status

**Task 1: System Architecture Development**
- Revised Concept of Operations (ConOps)
- Define functional requirements
- High-level architectural design
**Task 3:  Proof of Concept (POC)   **

## Proof of Concept

## 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 (landline, wireless, IP)
- Transmitting telematics data (Advanced Automatic Crash Notification) like speed, vehicular rollover, crash velocity
- Call routing and transfer
- IP networking and security

## 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 results.
- Simple pass/fail system used to test functional requirements
- A total of 116 functional requirements were tested using use case scenarios.
- In all, the project conducted 320 individual tests in the laboratories and PSAP facilities, with 280 (87.5 percent) successfully passing the test 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 sent to live 9‐1‐1 systems.

## Slide 15

| POC Functional Component | POC Findings |
| --- | --- |
| 
  Ability to send & receive voice, video,        text (Instant Messaging [IM], SMS), 
and data. | Successfully Tested.  Location data for SMS-based call is not currently commercially available.  There is no method for guaranteed message delivery and some SMS failed to be delivered.  Initially, issues arose with bandwidth and video streaming methods that caused video-based calls to fail.  |
| Increased deaf/hearing-impaired accessibility | Successfully Tested.  Upgrades and technological improvements will be needed at multiple levels.   |
| Caller’s location identification | Successfully tested for wireline, wireless and IP-based calls.  A number of acquisition and identification processes were used to demonstrate functional capabilities to locate emergency callers.   |
|   Call routing based on caller’s location | Successfully tested use of an ESRP and LoST servers, along with a Business Rules database.   |
| Transmitting telematics data  | Successfully Tested.  Demonstrated the ability to easily and automatically transfer important data associated with a vehicle crash. |
| IP networking and security | Successfully Tested.  Work is still needed to ensure the integrity of the network and system |

## Human Machine Interface

**Measures of Interest:  **
- Placement of Data on the Screen
- Navigation Complexity
- Screen Aesthetics
- Data Format
- Business Rule and Information Sharing Procedures
- Information Management

## Tasks of the NG9-1-1 Team:  Project Status

**Task 2: Transition Analysis**
- Preliminary Analysis of Cost, Value & Risk
- Report on Critical Deployment Issues
**Task 4:  Final Transition Plan**

## NG9-1-1 Initiative Documents Available

**NG9-1-1 Initiative Documents Available**

- Revised Concept of Operations
- Functional Requirements
- Architecture Design
- Preliminary Analysis of Cost, Value and Risk
- Transition Issues Report
- 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 Report:  coming soon!
- _[http://www.its.dot.gov/NG911](http://www.its.dot.gov/NG911)__ _

## 
Requirements
Standards
Transition Plan
Acquisition Tools

**Requirements**
**Standards**
**Transition Plan**
**Acquisition Tools**

**National**

**Office**

***After November 2008...***

**  ****DOT / DOC – Joint Program**
**  ****Housed @ US DOT / NHTSA**

**Notes:**
The three things coming out of the NG9-1-1 Initiative that will be most useful to the 
9-1-1 community in deploying NG9-1-1 are the requirements, the standards, and the transition plan.  These 3 documents will “live on” as the legacy of this initiative.

In addition, we plan to develop some acquisition tools and engage in technology transfer, both of which are described in greater detail on the next slide.

NHTSA, co-lead on the NG9-1-1 Project, is also charged with establishing a National 
9-1-1 office with the coordinated efforts of the NTIA (Department of Commerce). Those efforts are currently underway.  
[describe the 3 major responsibilities of the National 9-1-1 Office]

At the conclusion of the NG9-1-1 Project, the results of the initiative will transition to the National 9-1-1 Office. The office will continue to promote the results of the NG9-1-1 initiative as it provides support to PSAPs in their migration to Next Generation 9-1-1 solutions.

## 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
- Provide a Federal focus for 9-1-1
- Promote and support 9-1-1 services

**Notes:**
Clearinghouse on “information concerning practices, procedures, and technology used in the implementation of E9-1-1 services.

## National 9-1-1 Office:  Projects

- Model State 9-1-1 Plan
- National Data Set
- PSAP Benchmarking Data Set
- Technical Assistance Center
- National NG9-1-1 Migration Plan
- P.L. 110-283
- Federal 9-1-1/Medical Communications Committee (FICEMS)
- Regulations for Grant Program
- NPRM in Federal Register:  October 3

## 

http://www.its.dot.gov/ng911
Laurie Flaherty
laurie.flaherty@dot.gov

http://www.e-911ico.gov
 Phone:  (202) 366-3485
Email:  nhtsa.national911@dot.gov

- _[http://www.its.dot.gov/ng911](http://www.its.dot.gov/ng911)_
- Laurie Flaherty
- _[laurie.flaherty@dot.gov](mailto:laurie.flaherty@dot.gov)_
- _[http://www.e-911ico.gov](http://www.e-911ico.gov/)_
-  Phone:  (202) 366-3485
- Email:  _[nhtsa.national911@dot.gov](mailto:nhtsa.national911@dot.gov)_

- Would you like to be added to our Email Distribution List?