nena ng9-1-1 planning guidelines information document · nena-inf-006.1-2014 01/08/2014 initial...
TRANSCRIPT
NENA
NG9-1-1 Planning Guidelines
Information Document
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014
DSC Approval: 09/24/2013
PRC Approval: 12/13/2013
NENA Executive Board Approval: 01/08/2014
Prepared by:
National Emergency Number Association (NENA) NG9-1-1 Transition Planning Committee based
upon content developed by the NENA NG9-1-1 Project Lead Team
Published by NENA
Printed in USA
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 2 of 15
NENA
INFORMATION DOCUMENT
NOTICE
This Information Document (INF) is published by the National Emergency Number Association (NENA)
as an information source for the designers, manufacturers, administrators and operators of systems to be
utilized for the purpose of processing emergency calls. It is not intended to provide complete design or
operation specifications or parameters or to assure the quality of performance for systems that process
such equipment or services.
NENA reserves the right to revise this Information Document for any reason including, but not limited
to:
• Conformity with criteria or standards promulgated by various agencies,
• Utilization of advances in the state of the technical arts,
• Or to reflect changes in the design of equipment, network interfaces or services described herein.
This document is an information source for the voluntary use of communication centers. It is not
intended to be a complete operational directive.
It is possible that certain advances in technology or changes in governmental regulations will precede
these revisions. All NENA documents are subject to change as technology or other influencing factors
change. Therefore, this NENA document should not be the only source of information used. NENA
recommends that readers contact their 9-1-1 System Service Provider (9-1-1 SSP) representative to
ensure compatibility with the 9-1-1 network, and their legal counsel to ensure compliance with current
regulations.
Patents may cover the specifications, techniques, or network interface/system characteristics disclosed
herein. No license expressed or implied is hereby granted. This document shall not be construed as a
suggestion to any manufacturer to modify or change any of its products, nor does this document
represent any commitment by NENA or any affiliate thereof to purchase any product whether or not it
provides the described characteristics.
This document has been prepared solely for the use of 9-1-1 System Service Providers, network interface
and system vendors, participating telephone companies, 9-1-1 Authorities, etc.
By using this document, the user agrees that NENA will have no liability for any consequential,
incidental, special, or punitive damages arising from use of the document.
NENA’s Committees have developed this document. Recommendations for change to this document
may be submitted to:
National Emergency Number Association
1700 Diagonal Rd, Suite 500
Alexandria, VA 22314
202-466-3911
© Copyright 2014 National Emergency Number Association, Inc.
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 3 of 15
ACKNOWLEDGEMENTS
The National Emergency Number Association (NENA) Next Generation 9-1-1 (NG9-1-1) Transition
Planning Committee developed this document based upon content developed by the NENA NG9-1-1
Project Lead Team.
NENA recognizes the following industry experts and their employers for their contributions in
development of this document.
Executive Board Approval Date 01/08/2014
Members (NG9-1-1 Project Lead Team) Employer
Roger Hixson, ENP - Task Force Chair NENA
Pete Eggimann, ENP - DSC Co-Chair Metropolitan Emergency Services Board-St. Paul
Tony Busam, ENP - DSC Co-Chair RCC Consultants, Inc.
Tom Breen, ENP - Technical Editor AT&T
Jim Goerke, ENP – NGTPC Co-Chair Texas 9-1-1 Alliance
Robert Cobb, ENP NENA
Robert (Bob) Sherry, ENP– NGTPC Co-
Chair
Intrado
Ty Wooten, ENP NENA
Robert (Bob) Gojanovich, ENP Telecommunications Systems Inc.
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 4 of 15
Table of Contents
1 EXECUTIVE OVERVIEW .............................................................................................................................. 5
2 INTRODUCTION .............................................................................................................................................. 5
2.1 OPERATIONS IMPACTS SUMMARY ......................................................................................................................... 5 2.2 TECHNICAL IMPACTS SUMMARY........................................................................................................................... 5 2.3 SECURITY IMPACTS SUMMARY ............................................................................................................................. 5 2.4 DOCUMENT TERMINOLOGY .................................................................................................................................. 5 2.5 REASON FOR ISSUE/REISSUE ................................................................................................................................. 6 2.6 RECOMMENDATION FOR ADDITIONAL DEVELOPMENT WORK .............................................................................. 6 2.7 DATE COMPLIANCE .............................................................................................................................................. 6 2.8 ANTICIPATED TIMELINE ........................................................................................................................................ 6 2.9 COST FACTORS ..................................................................................................................................................... 6 2.10 COST RECOVERY CONSIDERATIONS ................................................................................................................. 6 2.11 ADDITIONAL IMPACTS (NON COST RELATED) ................................................................................................... 6 2.12 INTELLECTUAL PROPERTY RIGHTS POLICY ...................................................................................................... 6 2.13 ACRONYMS/ABBREVIATIONS, TERMS AND DEFINITIONS ................................................................................. 7
3 PLANNING FOR NG9-1-1 TRANSITION ..................................................................................................... 8
4 RECOMMENDED READING AND REFERENCES .................................................................................. 14
5 EXHIBITS ........................................................................................................................................................ 15
6 APPENDIX ....................................................................................................................................................... 15
7 PREVIOUS ACKNOWLEDGMENTS .......................................................................................................... 15
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 5 of 15
1 Executive Overview
The purpose and scope of this document is to provide guidance to help 9-1-1 Authorities create a
smooth, timely and efficient transition plan to accomplish implementation of NG9-1-1.
While the development of technical standards and related information is still ongoing, there are
many actions that 9-1-1 Authorities should consider in preparing for transitioning to an NG9-1-1
environment. These actions relate mostly to the preparation necessary to lay the proper foundation
for this transition. At a high level, this process is relatively logical, and involves efforts to identify
and organize the following Project Management actions:
• Initiatives: Education, governance, scope & goals
• Drivers: cost factors, emergency event response, institutional, statutory, geo-political situations,
opportunities and constraints
• Constraints: Identify the bounds within which the initiative will need to exist
• Requirements: What kind of service environment is called for
• Inventory: What is already in place and what is missing
• Partnerships: Build Inter-local/inter-authority relationships and communication channels, including
the current provider of emergency services
• Specific Actions: Establish coordination of roles and responsibilities, Funding sources,
Documentation, and Performance Measurement Metrics
• Planning: Technological and Operational deployment, training, communication, testing, and go-live
plans and procedures
More specific details for each of these Project Management actions are provided herein.
2 Introduction
2.1 Operations Impacts Summary
Transition to NG9-1-1 has wide-ranging Operational impacts, and they are addressed in this
document, as well as in related NENA Transition Planning Committee documentation.
2.2 Technical Impacts Summary
This document’s focus does not directly introduce technical impacts.
2.3 Security Impacts Summary
This document’s focus does not directly introduce security impacts.
2.4 Document Terminology
The terms "shall", "must", "mandatory", and "required" are used throughout this document to
indicate normative requirements and to differentiate from those parameters that are
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 6 of 15
recommendations. Recommendations are identified by the words "should", "may", "desirable" or
"preferable".
2.5 Reason for Issue/Reissue
NENA reserves the right to modify this document. Upon revision, the reason(s) will be provided in
the table below.
Doc # Approval Date Reason For Changes
NENA-INF-006.1-2014 01/08/2014 Initial Document
NENA-INF-006.1.1-2014 05/30/2015 Update web page links
2.6 Recommendation for Additional Development Work
NENA standards have already been, or are being developed for NG9-1-1 Transition
2.7 Date Compliance
All systems that are associated with the 9-1-1 process shall be designed and engineered to ensure
that no detrimental, or other noticeable impact of any kind, will occur as a result of a date/time
change up to 30 years subsequent to the manufacture of the system. This shall include embedded
application(s), computer-based or any other type application.
2.8 Anticipated Timeline
The content of this document is immediately applicable to NG9-1-1 Transition Planning. It is
recognized that Public Safety Authorities will transition to NG9-1-1 at their pace. This document
provides guidance to help plan and establish individual timelines.
2.9 Cost Factors
The content of this document proposes activities that will help avoid unnecessary costs and work
effort while implementing NG9-1-1.
2.10 Cost Recovery Considerations
Normal business practices shall be assumed to be the cost recovery mechanism for transition to
NG9-1-1. NENA cannot predict whether the transition to NG9-1-1 will provide either short or long
term cost savings.
2.11 Additional Impacts (non-cost related)
The content of this document, in conjunction with other NG9-1-1 planning material, will assist in
establishing a smooth, timely and efficient transition plan to accomplish implementation of
NG9-1-1. Other documentation speaks directly to additional impacts that for brevity are not listed
here. Such documentation includes (but is not limited to) the Recommended Reading and References
listed in Section 4 of this document.
2.12 Intellectual Property Rights Policy
NENA takes no position regarding the validity or scope of any Intellectual Property Rights or other
rights that might be claimed to pertain to the implementation or use of the technology described in
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 7 of 15
this document or the extent to which any license under such rights might or might not be available;
nor does it represent that it has made any independent effort to identify any such rights.
Consistent with the NENA IPR Policy, available at www.nena.org/ipr, NENA invites any interested
party to bring to its attention any copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement this standard.
Please address the information to:
National Emergency Number Association
1700 Diagonal Rd, Suite 500
Alexandria, VA 22314
202-466-3911
2.13 Acronyms/Abbreviations, Terms and Definitions
Some acronyms/abbreviations, terms and definitions used in this document may have not yet been
included in the master glossary. After initial approval of this document, they will be included. See
NENA 00-001 - NENA Master Glossary of 9-1-1 Terminology located on the NENA web site for a
complete listing of terms used in NENA documents. All acronyms used in this document are listed
below, along with any new or updated terms and definitions.
The following Acronyms are used in this document:
Acronym Description (N)ew
(U)pdate
ALI Automatic Location Identification
CAD Computer Aided Dispatch
CPE Customer Premises Equipment
ESInet Emergency Services IP Network
GIS Geographic Information System
MSAG Master Street Address Guide
NG9-1-1 Next Generation 9-1-1
PSAP Public Safety Answering Point
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 8 of 15
3 Planning for NG9-1-1 Transition
While the development of technical standards and related information is still ongoing, there are
many actions that 9-1-1 Authorities should consider in preparing for transitioning to an NG9-1-1
environment. These actions relate mostly to the preparation necessary to lay the proper foundation
for this transition. At a high level, this process is relatively logical, and involves efforts to identify
and organize the following Project Management actions:
• Initiatives: Education, governance, scope & goals
• Drivers: cost factors, emergency event response, institutional, statutory, geo-political situations,
opportunities and constraints
• Constraints: Identify the bounds within which the initiative will need to exist
• Requirements: What kind of service environment is called for
• Inventory: What is already in place and what is missing
• Partnerships: Build Inter-local/inter-authority relationships and communication channels, including
the current provider of emergency services
• Specific Actions: Establish coordination of roles and responsibilities, Funding sources,
Documentation, and Performance Measurement Metrics
• Planning: Technological and Operational deployment, training, communication, testing, and go-live
plans and procedures
More specifically, the following is a more detailed list of these action items:
Note: The Reference numbers shown are linked to their respective entry in Section 4 -
Recommended Reading and References. Ctrl+Click each Reference number to go to the linked
location in Section 4.
• Self-education- Educate the 9-1-1 Authority core planning team to understand what NG9-1-
1 involves and its impacts across Emergency Services Internet Protocol networks (ESInet),
NG9-1-1 services (applications & databases), roles, responsibilities and operational
procedures.
References: 1, 2, 3, 4, 5, 6, 14, 16, 17, 18, 19, 20, 21, 22
• Governance – Establish a service management (governance) structure with the authority to
engage in the project. Recognizing that NG9-1-1, by nature, reflects layered, interconnected
systems, initial transition steps will in many cases occur at local and regional 9-1-1 Authority
levels. Those activities, in turn, may progressively link together into larger regional NG9-1-1
systems. That, then, leads to a logical role for states to deploy resources to help support
and/or ensure statewide connectivity. Governance structures will need to be established to
manage these intergovernmental arrangements, unless such mechanisms already exist.1
1 Among other things, agreements governing such arrangements will address relative management
roles, responsibilities, and cost sharing.
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 9 of 15
Ultimately, there is no single answer to how these systems will interconnect, and how related
governance systems will evolve. Factors that will impact this include things like:
- Local, regional, and state emergency event response considerations
- Historical institutional, statutory, geo-political culture, arrangements and related environment
- Joint service environment (both existing and proposed)
- Resource and cost sharing opportunities, factors and constraints
Note: Whatever intergovernmental arrangements are put in place to explore, coordinate
and plan for these matters may not necessarily reflect the long-term arrangement
necessary to oversee and manage the system(s) involved.
References: 2, 4, 5, 15, 20, 23
• Communications Plan – Devise a matrix of stakeholders and determine how best to open
lines of communications throughout the life of the project. This may require several different
sets of contacts depending upon scope, nature and responsibilities of the stakeholders
involved. Review regularly to ensure completeness and continued accuracy.
References: 5
• Statement of Documentation – Establish a library function to memorialize the project.
Pertinent documents and communications should be assembled in a formal manner to allow
audit and remedial processes. Ensure that all terms used in Project related documents are
very clear to all users of the documents, even those who may have a less active role,
especially those in control of providing the necessary funding. Utilize document
management tools wherever possible including standardized file name structures and
metadata tagging.
References: 7, 15, 23
• Estimated Scope and Project Timelines– This is an early statement of expectations. At a
minimum the agencies expected to have access to the NG9-1-1 system should be identified.
The scale of the project, such as regional or state level, must be considered (see Governance).
If the network is intended to transport more than 9-1-1 calls, (e.g., NCIC, IP radio, Poison
Control), specify exactly what other emergency services applications are intended to be
supported on the network. This helps establish the network engineering criteria for the
systems involved. Resource and cost sharing may occur at basic network levels, and must be
factored into this analysis.
When scope and governance are identified, a project definition and timeline should be
initiated, to be expanded as items below are defined.
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 10 of 15
References: 2, 5, 14, 19
• Budget & Funding – Create an early budget based upon preliminary costs, available funds,
new funding sources and any anticipated stakeholder contributions. Essentially you want to
create a funding statement from which further financial information can be estimated.
References: 9, 5, 18
• Functional Requirements – Building upon the “Estimated Scope” and expected funding
determine from NENA sourced documents which functions you reasonably expect to deploy
initially, eventually or not at all. This document should be kept open for review and
modification for the life of the project.
References: 2, 14, 16, 17, 18, 20, 21, 22
• Data Inventory & Standardization – Identify sources of data you will target for use in the
development of this project. For example, while the Master Street Address Guide (MSAG) is
required as a data source, this project will require migration from tabular data to a
combination of tabular and spatial data. A clear understanding of the source of all required
data, including spatial/mapping data stored in a Geographic Information System (GIS),
ownership, responsibility and maintenance must be established.
References: 9, 10, 14 17, 18, 19, 21, 25
• Establish Performance Measurement Metrics - Determine the methodology you will use
to ensure that network and system operation and reliability meet acceptable and adopted
standards. Solutions should provide the capability to monitor, record, and analyze system
performance data against predefined metrics (i.e., establish system norms and flag
exceptions).
“This activity supports the monitoring, recording, maintenance, and improvement of system
performance data in accordance with adopted standards and best practices. The activity
includes, but is not limited to, network component monitoring, coupled with the development
and maintenance of operational resource utilization databases and documentation in aid of
minimizing congestion and maximizing performance. Performance trend analysis enables
system administrators to determine whether system components are adequate or decreasing
in service capability.” (quote taken from Reference 13, page 7-34)
References: 13, 14, 20, 22
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 11 of 15
• Socialization and Education – Once the steps above have matured to a point where they can
be expressed in common language, use your “Communications Plan” to begin the process of
describing the project its current state and estimated timelines to your stakeholders. Keep in
mind an important part of this process is answering the question of “what’s in it for me” from
the perspective of all stakeholders.
References: 5
• Network Analysis – For the geographic area being served, an analysis of existing broadband
infrastructure must be developed. The analysis should be as complete as possible and include
both private and public facilities. Record both the network architecture design and signaling
used for each identified source of bandwidth and associate each with the user-stakeholder
location. Where possible note areas that lack physical diversity, so they can be analyzed
further for possibly remedies to lessen the risk of service failures. Consider how this area
will interconnect with adjoining networks. Assess the need to interconnect with the E9-1-1
SSP for routing and bridging of 911 calls. This may be needed when originating carriers
remain supported by the legacy SR and the appropriate Public Safety Answering Points
(PSAPs) have transitioned to the NG9-1-1 system. It may also be necessary if calls may be
bridged between PSAPs supported by the NG9-1-1 system and those remaining on the legacy
emergency system.
References: 5, 12, 14, 20, 22, 24
• PSAP Inventory – If there is no central repository for information regarding the equipment
and software inventories within the PSAP community, one must be assembled. Going beyond
just 9-1-1 Customer Premises Equipment (CPE), this inventory should be as granular as
reasonably possible, and may include items such as types of Computer Aided Dispatch
(CAD), other public safety applications, mobile data applications, control of radio consoles
and related administrative communications, used in the PSAP operational environment.
These documents must be kept open for updates on a regular basis. This activity supports
overall planning, and includes identifying opportunities to share resources, and assists in
ensuring interoperability.
References: 16, 17
• Refinement of Scope – Using input from the former tasks, develop a refined, realistic scope
for the project. Specificity and clarity are required of this step and it is urged that the entire
stakeholder community be aware of the scope.
References: 2, Error! Reference source not found., 14, 19
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 12 of 15
• Financial Forecasting – Create a realistic fiscal plan for the project in terms of both startup
and ongoing obligations. Perhaps nowhere else in this process does the stakeholder
community play such a helpful role. Outreach and coaching from the commercial
stakeholders can greatly assist in developing this forecast.
References: 13, 14
• Deployment and Testing Planning – Creation of a plan for deploying and testing even if
incomplete must begin prior to the “Acquisition” phase of the project. Reasonably estimate
the amount of effort not only for the public agencies including central 9-1-1 Authority
groups, but the provider community as well. Assess the interaction and testing that may be
required with the E9-1-1 SSP (there may be more than one). Use a methodical approach to
deployment and expect a thorough test period prior to going live with any installation. This
plan, including specific test scripts must be in written form. Initially the test scripts might be
high level. But before testing begins, those high level scripts will need to be detailed and
shared with all impacted stakeholders. Everyone involved in testing must understand their
role and responsibility.
Reference: 20
• Acquisition – Develop, issue, grade and award the project. Usually done as a Request for
Proposal (terms may differ), acquisition may be done as a single provider solution or be
provided by more than one source. Regardless of how the solution is let for bid, local and
state laws will dictate much of the process.
References: 3, 5
• Training – Expect and plan for training of call taking, technical and administrative
personnel. It is extremely important to include those “back room” workers who will be called
upon to perform maintenance of the system once it is up and running.
References: 2, 3, 5, 16, 18
• Testing – Never go live without a thorough test of each installation. Using the testing
processes developed during the “Deployment and Testing Planning” step, apply the tests, as
appropriate, and document their results for each installation.
References: 16, 20, 21, 22
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 13 of 15
• Go-Live – Each implementation has its own unique go-live experience. Regardless of what
the calendar says go-live can only move forward after training and testing have been
completed as agreed upon in the contract(s). Do not permit artificial deadlines to drive a
project into “go live” before all required testing has been performed, and results indicate the
system is ready to use.
References: 3
• Management and Maintenance – As an ongoing element of the project both the provider
and public stakeholder will have a role in continual management and maintenance of the
NG9-1-1 system and its components. Maintenance becomes an active part of the” Statement
of Documentation” process and will remain an active role throughout the life of the network
and system.
References: 2, 3, 4, 5, 17, 21
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 14 of 15
4 Recommended Reading and References
1. NENA NG9-1-1 Tutorial
2. The USDoT 911 Initiative Transition Plan Document
3. The USDoT 911 Initiative Procurement Toolkit
4. Next Generation 9-1-1 Transition Policy Implementation Handbook (March 2010)
5. NASNA Model State Plan
6. National 9-1-1 Resource Center – use keyword: “transition”
7. NENA Master Glossary of 9-1-1 Terms
8. NENA Report -Funding 9-1-1 Into the Next Generation
9. NENA White Paper - A PSAP Managers’ Guide to Geographic Information Technology
10. Overview of Policy Rules for Call Routing and Handling in NG9-1-1 NENA 71-502 v1
11. FCC’s National Broadband Plan – results of state infrastructure availability (A very large file)
12. US DoT Final Analysis of Cost, Value, and Risk Executive Summary document
13. USDoT 911 Initiative System Description & Requirements Document (A very large file)
14. NG9-1-1 Transition Planning Considerations – NENA-INF-008.2-2013 (previously 77-501)
15. NENA Inter-Agency Agreements Model Recommendations - NENA-INF-012.2-2015
(originally NENA 53-506)
16. Virtual PSAP Management NENA 53-507
17. NG9-1-1 Additional Data NENA 71-001v1
18. Synchronizing GIS with MSAG and ALI NENA 71-501v1
19. USDoT NG9-1-1 POC Test Plan The reader should note that the USDoT POC test plan document provides information that
can help organize system testing, but the Proof Of Concept tests represented only part of the
overall NG9-1-1 system as applicable to the specific POC objectives.
20. NENA Security for Next-Generation 9-1-1 Standard (NG-SEC) NENA 75-001v1
21. NENA NG9-1-1 System and PSAP Operational Features and Capabilities Requirements NENA 57-
750v1
22. NENA Mutual Aid Standard/Model Recommendation - NENA-STA-009.2-2015 (originally
NENA 53-002)
23. Detailed Functional and Interface Specification for the NENA i3 Solution – Stage 3
(NOTE: This NENA standard intentionally describes “end-state” NG9-1-1 architecture,
rather than an immediate “build-to” specification for a complete NG9-1-1 system. Transition
will be targeted at that end state design.)
24. NENA Emergency Services IP Network Design for NG9-1-1 (ESIND) – NENA 08-506
NENA NG9-1-1 Planning Guidelines Information Document
NENA-INF-006.1-2014, January 8, 2014
01/08/2014 Page 15 of 15
25. NENA Provisioning and Maintenance of GIS Data to ECRF/LVF - NENA-STA-005.1-201X
(As of the date of publication, this document is in the final approval stages. It is expected to
be publicly available in 4Q2015.)
26. NENA NG9-1-1 Civic Location Data Exchange Format Standard - NENA-STA-004.1-2014
27. NENA Standard for NG9-1-1 GIS Data Model - NENA-STA-006.1-201X (As of the date of publication, this document is in the final approval stages. It is expected to
be publicly available in 4Q2015.)
28. NENA Requirements for NG9-1-1 Data Management - NENA-REQ-002.1-201X
(As of the date of publication, this document is in the final approval stages. It is expected to
be publicly available in 4Q2015.)
5 Exhibits
N/A
6 Appendix
N/A
7 Previous Acknowledgments
N/A – Original Document