National Emergency Number Association

NENA Operations Standards & Documents

Documents are attached at the bottom of individual standards for download.

Technical – General
Operations – General

  • 00-001 v16 Master Glossary

    The NENA Master Glossary is a guide for readers of NENA publications and a tool for members of the NENA committees that prepare them. It defines the terms, acronyms and definitions associated with the 9-1-1 industry. Intended users of this document are any person needing NENA’s definition/description of a 9-1-1 related term.

    Technical – General
    Operations – General

Operations – General

  • 51-001 Operations Committee Organization & Process

    The purpose of this document is to describe the Operations Committee, delineate its organization, and define the processes required for the Committee operations and document development.

    This document was revised May 4, 2010, to add detail for the Operations Committee use of Operations Reference Documents (ORD).

    Operations – General

Operations – Accessibility

  • 52-001 TTY Training Standard

    With an estimated 54 million people in the United States who have disabilities, over 28 million have hearing loss or speech impairment and may utilize TTYs for telecommunications. This document is a tool for PSAPs to use in the development of TTY training programs. It outlines the recommended elements to be contained within a training program to assist PSAPs with compliance of Title II of the Americans with Disabilities Act.

    Operations – Accessibility

  • 52-002 Managers Guide to the ADA

    The Managers Guide to the ADA: Title II, Direct Access standard is a tool designed to assist managers in bringing PSAPs into compliance with the ADA. Utilizing this standard will enhance the quality of service provided to the public, including the estimated 28 million people in the United States who have hearing loss.

    Operations – Accessibility

  • 52-003 TTY Call Taker Proficiency & Quality Assurance

    The purpose of this document is to provide recommendations toward the  implementation of a comprehensive Quality Assurance Program which includes training of call takers, conducting random, unannounced test calls, completing documentation of training and test calls, and conducting remediation activities to address identified deficiencies and equipment malfunctions.

    Operations – Accessibility

  • 52-501 TTY Phone Pal Program

    This Operational Information Document (OID) introduces a program that will assist PSAP managers in their efforts to ensure equipment functionality and enhance call taker proficiencies where it concerns utilizing TTYs (also known as TDD – Telecommunications Device for the Deaf). In addition, this document provides the framework and outline format for establishing this type of program.

    Operations – Accessibility

  • 52-502 Video & IP Relay Service / PSAP Interaction

    This NENA Video Relay Service (VRS) and Internet Protocol Relay Service (IP Relay) PSAP Interaction OID is intended to provide guidelines for PSAPs and recommendations to the FCC for:

    • Emergency calling to 9-1-1 using Video Relay and IP Relay services
    • Relay of such calls to the appropriate Public Safety Answering Point (PSAP)(?)
    • Interaction between the caller, the video relay interpreter (VI) or communications assistant (CA) and telecommunicator

    Operations – Accessibility

Operations – Contingency Planning

  • 53-001 PSAP Disaster and Contingency Plans

    The purpose of the NENA Model Recommendation for Disaster and Contingency Plans is to provide general guidelines for circumstances that may adversely impact the Communications Center/PSAP personnel to receive, process, dispatch and monitor emergency calls for assistance.

    Operations – Contingency Planning

  • 53-001A Evacuation Checklist

    Sample “Evacuation Checklist” for use in disaster recovery planning.

    Operations – Contingency Planning

  • 53-002 Mutual Aid

    The purpose of the NENA Model Recommendation for Mutual Aid is to provide general guidelines for the development, promulgation and implementation of agreements between public safety communications agencies to assure adequate resources during disaster.

    Operations – Contingency Planning

  • 53-501 Hazard and Vulnerability Analysis

    This document is provided to assist Public Safety Answering Points (PSAPs) with the development of Hazard and Vulnerability Analyses. These analyses are essentially audits that provide planning tools to prevent, prepare for, respond to and recover from incidents that have the potential to adversely affect the PSAPs ability to perform its critical functions. Every PSAP is unique and this document should be used as a starting point in disaster planning.

    Operations – Contingency Planning

  • 53-502 Resource Analysis Operations Information

    This document is intended as a guide for PSAP staff to review the many components of their system and as a starting point for evaluating hazards and their individual vulnerability to the hazards, which may adversely impact their ability to serve their communities. This document is not intended as a template, but as a process guide.

    Operations – Contingency Planning

  • 53-503 PSAP Survivability

    This document is intended as a guide for PSAP staff to review the many components of their system continuity and disaster plans. It is also intended as a guide for training, testing and reevaluating the PSAPs ability to react to a disaster situation, which may adversely impact their ability to serve their communities. It is recommended that all contingency plans be coordinated with appropriate Emergency management authorities. This document is not intended as a template, but as a process guide.

    Operations – Contingency Planning

  • 53-504 Drills and Exercises

    This document is intended as a guide for PSAP staff to develop a drill and exercise program to test the effectiveness of the contingency plan. Drills and exercises are tools to enhance contingency planning and to better prepare for issues which may impact service. This document is not intended as a template, but as a process guide.

    Operations – Contingency Planning

  • 53-505 Service Capability Criteria Rating Scale

    APCO and NENA have jointly developed this document to assist PSAP Managers and their Governing Authorities to identify their current level of service capability. A self-evaluation assessment tool is provided to facilitate an objective review of the current capabilities of the PSAP against models representing the best level of preparedness, survivability and sustainability amidst a wide range of natural and man-made events.

    Operations – Contingency Planning

  • 53-506 Intra-Agency Agreements

    This document is provided as a Model Recommendation for the development of Mutual Aid Agreements and Memorandums of Understanding (MOUs) between Public Safety Answering Points and affiliated or support organizations. The documents discussed and attached should be modified to meet the unique requirements of individual States and Municipalities.

    Operations – Contingency Planning

  • 53-507 Virtual PSAP Management

    This document is intended as a guide for PSAP staff and policy makers to evaluate and consider the opportunities and challenges presented with the Next Generation 9-1-1(?) systems as they relate to personnel and PSAP management. Specifically, what considerations might be necessary for employing virtual workers for the traditional PSAP environment?

    Operations – Contingency Planning

Operations – Human Resources

  • 54-001 PSAP Daily Personnel Operations

    This document is provided as a Model Recommendation for the creation of the Daily Personnel Operations section of a Standard Operating Procedure (SOP) for use by Communications Centers and/or PSAPs as guidance in the formulation of an agency SOP.

    Operations – Human Resources

  • 54-002 Hearing Standards for Telecommunicators

    This Hearing Standards for Public Safety Telecommunicators standards document is a tool for PSAP managers to use in the development of minimum hearing standards for public safety telecommunicators. It defines standard hearing requirements and audiology necessary to perform the basic functions of the telecommunicator position.

    Operations – Human Resources

  • 54-501 Human Resources Resource List

    This “NENA Human Resources Subcommittee Resource/Information List” is a tool for PSAP managers and administrators to use as a resource for locating information on various Human Resources related information.

    Operations – Human Resources

  • 54-501A PSAP Staffing Guidelines Report

    L. Robert Kimball & Associates, Inc. and 9-1-1 SME Consulting have performed a PSAP Staffing Survey and Analysis Study for the National Emergency Number Association (NENA) SWAT Team Operations Group. The objectives of the study were to develop staffing and budget models from data collected from existing PSAPs with which those approximately 432 counties in the United States without Enhanced 9-1-1 can project staffing and associated budgetary needs to implement Enhanced 9-1-1 service. This report presents the findings of the study and the guidelines for optimizing the use of the data.

    Operations – Human Resources

  • 54-750 v1 HMI & PSAP Display Requirements

    NENA and APCO have jointly developed this document for the purpose of prescribing requirements for the human machine interface (HMI) display for the Next Generation 9-1-1(?) (NG9-1-1(?)) System. The ubiquitous access to 9-1-1 emergency services needed in today’s world of evolving technology is driving the need to introduce a broader array of interconnected networks that would comprehensively support emergency services.

    Operations – Human Resources

Operations – Standard Operating Procedures

  • 56-001 Minimum Response To Wireless 9-1-1 Calls

    This document has been developed to serve as a model standard operating procedure for those Public Safety Answering Points (PSAPs) that receive wireless 9-1-1 calls.

    Operations – Standard Operating Procedures

  • 56-002 NORAD/FAA Notification: Airborne Events

    This document has been developed to serve as a model standard operating procedure for Public Safety answering Points (PSAPs) to notify the North American Aerospace Defense Command (NORAD) or the Federal Aviation Administration (FAA) of certain air events that may require a response from an appropriate national agency

    Operations – Standard Operating Procedures

  • 56-003 Standards for Emergency Notification Systems

    Emergency Telephone Notification Systems (ETNS) are fast becoming a necessary tool for public safety agencies nationwide. Large metropolitan areas and communities of all sizes have installed these systems to provide essential emergency information to their citizens. The National Emergency Number Association (NENA) believes acquisition and deployment of these emergency notification systems will only increase with today’s homeland security and domestic protection concerns.

    Operations – Standard Operating Procedures

  • 56-004 TTY/TDD Communications SOP

    This document has been developed to serve as a model standard operating procedure for handling TTY/TDD Communication within Public Safety Answering Points (PSAPs).

    Operations – Standard Operating Procedures

  • 56-005 9-1-1 Call Answering Standard

    This document has been developed to serve as a model standard operating procedure for the calltaking function within Public Safety Answering Points (PSAPs).

    Operations – Standard Operating Procedures

  • 56-006 Emergency Call Processing Protocol

    This standard provides emergency communication processing centers with a framework from which agencies can define appropriate emergency communication protocol requirements and recommendations for day-to-day operations and for disaster/major event scenarios.

    Operations – Standard Operating Procedures

  • 56-007 NENA Pipeline Emergency Operations Standard/Model Recommendation

    This Standard is intended to aid Public Safety Answering Points (PSAP) in the development and implementation of emergency communications protocols pertaining to pipeline emergencies.  It addresses common situations involving pipelines carrying non-toxic natural gas and hazardous liquid petroleum products.  It does not address the release of toxic chemicals or other hazardous materials such as hydrogen sulfide.  The release of these substances will require a more detailed analysis and are beyond the general recommendations contained in this Standard.

    Operations – Standard Operating Procedures

  • 56-501 Silent or Hang-Up 9-1-1 Calls

    This Operations-Focused Study is published by the National Emergency Number Association (NENA) as a guide and fact-finding tool to 9-1-1 agency administrators, communications center managers and supervisors, and public and private sector designers and manufacturers of public safety answering point (PSAP)(?) technology solutions used for the purpose of processing emergency (E/9-1-1) calls for service.

    Operations – Standard Operating Procedures

  • 56-502 Rail & Highway Milepost Markers

    The purpose of this Operational Information Document is to provide a recommendation regarding the development of a national database to include milepost information and other data for highways and railways within the United States.

    Operations – Standard Operating Procedures

  • 56-503 Emergency Notification Systems

    This document is intended to be an informative guide and resource for the public and private sector in understanding the nuances and challenges of wide area/large area emergency notification systems and their various uses. It serves to provide information on the differences in the range of these increasingly popular emergency notification systems as a key public safety, emergency communications and emergency management information tool. It is also intended to provide substantive information on the goals and objectives of these systems, and the importance of clearly understanding how these systems may be used, as well as identify (often) overlooked responsibilities of the host agency/system administrator in appropriately specifying, using and managing these systems.

    Operations – Standard Operating Procedures

  • 56-504 VoIP 9-1-1 Deployment and Operational Guidelines

    This document has been developed as a best practice for the deployment of VoIP E9-1-1 service. As such, its primary goal is to set expectations and improve communications among the parties involved in the deployment process. The intent of this document is to offer guidance to VoIP Providers, 9-1-1 Governing Authorities and PSAP Managers/Administrators prior to and during the process of VoIP E9-1-1 deployment. This document specifically addresses VoIP E9-1-1 deployments using dynamic ALI. It does not cover static VoIP using traditional wireline ALI.

    Operations – Standard Operating Procedures

  • 56-505 Handling Calls Regarding Missing & Exploited Children

    This document describes guidelines that, if applied in 9-1-1 Centers, can help to swiftly recover missing children and may protect children from exploitation. 9-1-1 Centers should use these guidelines to issue their own policies and procedures for handing calls related to missing and exploited children (MEC).

    Operations – Standard Operating Procedures

  • 56-506 Public Safety Answering Point Site Selection

    The typical useful life of a public safety answering point (PSAP)(?) in the United States is between twenty (20) and fifty (50) years. As with any fixed asset whose ability to support people, organizations and their operations has diminished, the decision to replace it or upgrade it may eventually have to be made. Research has shown that building or renovating a PSAP is a major undertaking and is often a first-time experience for most executives and administrators.

    Operations – Standard Operating Procedures

  • 56-507 Railroad & PSAP Interaction

    This document describes a protocol for communicating between railroads and emergency response agencies to make the process of getting assistance to incidents along rail lines as efficient and effective as possible.

    Operations – Standard Operating Procedures

  • 56-508 Protocol for Handling Calls of Human Trafficking

    This document describes guidelines that, if applied in 9-1-1 Call Centers, can help to swiftly rescue human trafficking victims. 9-1-1 Call Centers should use these guidelines to issue their own policies and procedures for handing calls related to human trafficking situations.

    Operations – Standard Operating Procedures

  • 56-509 v1 Providing EMD Services
    A considerable number of PSAPs in the United States, Canada, and other nations provide emergency medical dispatch (EMD) service to their callers. EMD is a recognized structured system used to determine the nature and severity of a medical problem, prioritize it so the appropriate level of Emergency Medical Services is dispatched safely, and provide the caller with instructions on how to assist the patient until Emergency Medical Services arrive. However, not all Public Safety Answering Points provide this service.
     
    There are EMD Service Providers who directly deal with members of the public that have recognized this limitation and have initiated steps to provide this service. They include, but are not limited to organizations such as automotive companies, alarm services and technology services. These EMD Service Providers may choose to provide emergency medical dispatch services directly for their clients.
     
    This document is intended to serve as a model best practice guide to both EMD Service Providers and for the Public Safety Answering Points that receive third party calls from the EMD Service Providers and dispatch the appropriate First Responders. 
     

    Operations – Standard Operating Procedures

Operations – Next Generation Integration – NGI

  • 57-001 Wireless 9-1-1 Overflow, Default and Diverse Routing

    The NENA Wireless Overflow, Default and Diverse routing recommendations document was developed to provide guidance in the routing development associated with wireless Phase I and Phase II deployment efforts. This document provides recommended terminology definitions, describes each call routing scenario, and associated routing recommendations.

    Operations – Next Generation Integration – NGI

  • 57-001A Nondisclosure Agreement (Sample Form)

    Operations – Next Generation Integration – NGI

  • 57-001B PSAP Guide to Geographic Information Technology

    This paper includes information on how to best deal with wireless information coming into the Public Safety Answering Point (PSAP)(?). Any PSAP that is now, or will be, receiving wireless calls will find this paper useful. This focus of this paper is how to best utilize Geographic Information Systems (GIS) in dealing with wireless calls in the PSAP.

    Operations – Next Generation Integration – NGI

  • 57-002 Wireless Call Routing & Testing Validation

    This Standard is to provide a common format and rules for the submission of wireless maintenance cell data for call routing and ALI display review and approval by the 9-1-1 Governing Authority in existing E9-1-1 Service deployments.

    Operations – Next Generation Integration – NGI

  • 57-501 Wireless 9-1-1 Features & Functions

    The purpose of this Operational Information Document is to define how E9-1-1 Phase I and Phase II should work in a best practice operational environment, given the current technology limitations

     

    Operations – Next Generation Integration – NGI

  • 57-502 Wireless Phase I/II Planning & Implementation

    This document is intended to act as a best practice for the deployment of wireless E-911 Phase I and Phase II. As such, its primary goal is to set expectations and improve communications among the many parties involved in the deployment process. Many early deployments were delayed by the lack of an understood process. The lines of communications are extremely important during the deployment of Phase I and II service.

    Operations – Next Generation Integration – NGI

  • 57-502A Wireless Phase I & Phase II Agreements

    Operations – Next Generation Integration – NGI

  • 57-503 Notification of ERDB & VPC Operators of ESN Changes

    This document was developed as a recommendation for distribution of ESN changes and additions initiated by 9-1-1 Administrators to ERDB, VPC and ESGW operators in the i-2 VoIP environment, which assumes the use of wireline ESNs for the routing of VoIP calls. Its primary goal is to set expectations and improve communications amongst the parties involved to facilitate the timely implementation of VoIP ESN changes and additions, thereby facilitating the proper routing of VoIP E9-1-1 calls. It also makes recommendations as to how to provide the GIS files that reflect the ESN addition or changes requested. This procedural recommendation will involve technical development work. As such, a short term recommendation is also outlined.

    Operations – Next Generation Integration – NGI

  • 57-750 v1 NG9-1-1 System & PSAP Operational Features & Capabilities

    Operations – Next Generation Integration – NGI

Operations – VoIP

Technical – Data
Operations – Next Generation Integration – NGI

  • 70-001 v1 NENA Registry System

    When developing and deploying technical standards which employ enumerations, or lists of values, where the enumeration or lists can reasonably be expected to change over time as new technology, vendors, service providers or other stakeholders evolve, a known stable way to maintain the current acceptable values in the enumeration or list is required. The values in the enumeration or list are called a registry. This document describes how registries are created and maintained in NENA.

    Technical – Data
    Operations – Next Generation Integration – NGI
  • 70-DRAFT Provisioning and Maintenance of GIS data to ECRF/LVF

    NOTE:  NENA XX-XXX, Version 1, is continuing to be developed by the NGDD ECRF/LVF WG.

    This document defines operational processes and procedures necessary to support the i3 Emergency Call Routing Function (ECRF) and Location Validation Function (LVF). Additionally, this document identifies ECRF/LVF performance and implementation tradeoffs for 9-1-1 Authorities’ consideration.

    The roles and responsibilities of 9-1-1 Authorities vary depending on jurisdictional hierarchy, resource availability, capabilities, service arrangements, and regulations and statutes. As such, 9-1-1 Authorities are expected to work with ECRF/LVF operators to further clarify and/or identify additional services prior to development and implementation of ECRF and LVF. 
     
    Although this document contains references to 9-1-1 authorities’ Geographic Information System (GIS), Public Safety Answering Point (PSAP)(?)(?) equipment and mapping applications, access and call network providers Location Information Servers (LIS), and other core functions of the NG9-1-1(?) system, their functionality and operations are out of scope for this document. NENA 08-003 contains definition of data structures and detailed functional and interface standards that are referenced in this document.  
     

     

    Technical – Data
    Operations – Next Generation Integration – NGI
  • 71-001 v1 NG9-1-1 Additional Data

    With the implementation of NG9-1-1(?) there will be many forms of additional data available to emergency responders. This document covers the use of additional data associated with a call, a location, a caller and a PSAP. Together with the SIP Invite and PIDF-LO, additional data associated with a call has the ability to look at other data sources; i.e., Vehicle Emergency Data Set (VEDS) to assist in determining the appropriate call routing and handling.

    Technical – Data
    Operations – Next Generation Integration – NGI
  • 71-002 DRAFT Civic Location Data Exchange Format (CLDXF)

    NOTE:  NENA 71-002, Version 1, is being worked by the NGDD CLDXF WG.

    NENA Joint Data/Next Generation Integration Committees, Next Generation Data Development Working Group (NGDD), has created the Next Generation 9-1-1(?) (NG9-1-1(?)) Civic Location Data Exchange Format (CLDXF) Standard as one component of a larger suite of NG9-1-1 standards. The NG9-1-1 standards are intended to provide a common and mutually-understood means for PSAPs to exchange 9-1-1 call location information.

    The NENA NG9-1-1 CLDXF standard supports the exchange of United States civic location address information about 9-1-1 calls, both within the US and internationally. The NENA NG9-1-1 CLDXF standard covers civic location addresses within the United States, including its outlying territories and possessions. The NENA NG9-1-1 CLDXF standard defines the data elements needed for address data exchange, and provides an XSD for implementing the standard. As a data exchange standard, the NENA NG9-1-1 CLDXF is not intended to support civic location address data management. It is assumed that address information will be transmitted call by call, as part of the call record, and that any local address data repository would be external to the call information. Therefore the standard does not provide for an address identifier, address metadata, or address data quality tests.

    Concurrently with the NGDD WG’s development of the CLDXF, the Address Standard Working Group (ASWG) has been developing an address standard for the U.S. FGDC. The FGDC draft standard is intended to support address data management. The FGDC draft defines address data content, attributes, and metadata; address classes; address data quality tests; and an XSD for address data exchange. The Joint Data Technical/Next Generation Integration Committees, Next Generation Data Development Working Group, has worked closely with the Address Standard Working Group to prepare a profile of the NENA and FGDC draft standards that details the precise relationship between them. Pending formal adoption of the separate standards by NENA and FGDC, the profile will be included as an informative annex to both standards.

     

    Technical – Data
    Operations – Next Generation Integration – NGI
  • 71-501 v1 Synchronizing GIS with MSAG & ALI

    This document is the NENA information document for the synchronization of certain Geographic Information Systems (GIS) database layers with the Master Street Address Guide, the Automatic Location Information data, and optionally the site / structure locations.

    This document is meant to provide PSAP management, vendors, and other interested parties necessary guidelines for synchronizing GIS data with existing 9-1-1 databases. The synchronization process of the GIS data is most reliably accomplished by qualified, trained individuals or vendors that have received formal GIS training and instruction.

    Technical – Data
    Operations – Next Generation Integration – NGI
  • 71-502 v1 Overview of NG9-1-1 Policy Rules

    This document is an overview of what policy rules are, how policy is defined, and the ways that they may be used. Policy rules influence the delivery of calls to a PSAP and, how these calls are handled based on call taker skill sets and other criteria. Policy Rules are defined and implemented by the governing 9-1-1 Authority.

     

    Technical – Data
    Operations – Next Generation Integration – NGI

Technical – VoIP/Packet
Operations – VoIP

  • 73-501 Non-Voice-Centric Emergency Services

    The Emergency Services community has a desire to have multimedia emergency services supported with the same general characteristics as emergency voice calls. As a result, there is a need to communicate with emergency services using mechanisms that are not primarily voice.

    Non-Voice -Centric (NVC) Emergency Services are intended to support (human) end user to authority communication. NVC Emergency Services may support the following examples of non-verbal communications to an emergency services network:

    1. Text communication between end users and emergency services
    2. Multi-media (e.g., pictures, video clips) transfer to emergency services during a voice or NVC session with emergency services.
    3. Real-time video session with emergency services
    4. Text communication with supplementary media (such as background audio and/or video)

    NVC Emergency Services as defined in this document focuses on Next Generation Network (NGN) technology and does not include legacy messaging services, such as Short Messaging Service (SMS) . In addition, NVC Emergency Services does not include support of calls from non-human initiated devices (e.g., fire alarms).

    There will be significant impacts to the entire emergency services system resulting from the changes in networks and devices as described in this document. It is expected that end user devices and origination networks will ultimately evolve, and that the next generation emergency services solution will allow this evolution to take place over time. Many systems in the emergency services network must eventually change. New end-to-end messaging relationships must be established.

    In addition to supporting the general public, this capability facilitates emergency communications by individuals with disabilities (e.g., persons who are deaf, deaf-blind, hard of hearing, or have a speech disability).

     

     

     

     

     

    Technical – VoIP/Packet
    Operations – VoIP

Technical – CPE
Operations – Next Generation Integration – NGI

  • 75-001 v1 NENA Security for Next-Generation 9-1-1 Standard (NG-SEC)

    The purpose of this document is to establish the minimal guidelines and requirements for the protection of NG9-1-1(?) assets or elements within a changing business environment. This document:

    • Identifies the basic requirements, standards, procedures, or practices to provide the minimum levels of security applicable to NG9-1-1 Entities.
    • Provides a basis for auditing, and assessing levels of security and risk to NG9-1-1 Entities, assets or elements, and exception approval / risk acceptance process in the case of non-compliance to these guidelines.

    This document is applicable to all NG9-1-1 Entities including, but not limited to:

    • Public Safety Answering Points
    • NG9-1-1 “ESINet”
    • NG9-1-1 Service Providers
    • NG9-1-1 Vendors
    • Any Contracted service that perform functions or services that require securing NG9-1-1 assets. 
    • Those who use, design, have access to, or are responsible for NG9-1-1 assets (includes computers, networks, information, etc.).

    This document will impact the operations of 9-1-1 systems and PSAPs as standardized security practices are implemented where they have not been in place before. NG9-1-1 Entities will be required to understand, implement and maintain new security solutions, mechanisms and processes.

    Technical – CPE
    Operations – Next Generation Integration – NGI

Joint – NG Transition Planning

  • 77-501 v1 NG9-1-1 Transition Planning Considerations

    The public safety community has recognized the need to evolve legacy emergency services networks to next generation concepts which may facilitate new capabilities and services. As such there are numerous industry associations and Standard Development Organizations (SDOs) that are defining architectures and protocols for these next generation networks. The public safety community desires to take advantage of this work and address the challenge it represents to emergency communications. To this end, work is progressing in other NENA committees to define the specific emergency services architectures and protocols involved. The transition of emergency services addressed by this document relies upon this collective work.

    Joint – NG Transition Planning