The primary objective of the NGTPC is to identify technical and operational gaps in the transition to NG9-1-1 and make recommendations on how to mitigate those gaps These recommendations are targeted at Public Safety Authorities and other stakeholders to assist them in moving from each 9-1-1 system and service environment starting point to NG9-1-1. These recommendations include the related development actions needed to enable transition to a fully capable NG9-1-1 service.
NG9-1-1 is defined as the next evolutionary step in the development of the 9-1-1 emergency communications system known as E9-1-1 that has been in place since the 1970s. NG9-1-1 is a system comprised of managed IP-based networks and elements that augment present-day E9-1-1 features and functions and add new capabilities. NG9-1-1 will eventually replace the present E9-1-1 system. NG9-1-1 is designed to provide access to emergency services from all sources, and to provide multimedia data capabilities for PSAPs and other emergency service organizations. There will be a multi-year transition to NG9-1-1. Work has already begun in some regions that are putting in place IP infrastructures. In order to begin transition planning the NGTPC has published the first version of a Transition Plan. The Transition Plan includes the beginning points (i.e. the legacy environment) and the ending points (i.e. the NG9-11 environment and recommendations for transition to NG9-1-1.
- NG9-1-1 Transition Planning Committee, Co-Chairs Jim Goerke and Bob Sherry: The NGTPC is defining transition plans for the migration from the legacy E9-1-1 environment to Next Generation 9-1-1 systems supporting emergency services.
- Monitoring & Managing NG9-1-1, Co-Chairs Michael Smith and Rick Blackwell: The Monitoring and Managing NG9-1-1 Working Group meets on Wednesdays from 2-3PM Eastern time. The group is tasked with creating a NENA document that addresses specific operational topics and makes general recommendations on operational procedures associated with the transition to monitoring and managing NG9-1-1 software functions and infrastructure. The output is targeted to those personnel who develop and manage PSAP processes and procedures, and to those responsible for ESInet, NG9-1-1 Core Services, and PSAP infrastructure. The effort will identify and describe what needs to be monitored and how that is different than current practices within E9-1-1, including the acquisition and provisioning of the capacity involved. The level of detail will be sufficient to identify areas that should be considered in RFPs and Service Level Agreements. Expertise Needed: Subject Matter Experts that have been involved in monitoring and managing large, complex systems and networks, or that have been involved in writing and negotiating SLAs for them are invited to join the working group in this important effort.