Technical Committee – Data

The Data Technical Committee (DTC) is responsible for developing standards for all E9-1-1 Data issues related to existing and new 9-1-1 products and services. The committee’s goal is to develop data standards that can be forwarded to regulatory and industry standard organizations in order to ensure companies adherence.  The standards also provide guidance to 9-1-1 agencies and service providers.

Scroll Down or Click to Go To:

The committee is currently working on NG9-1-1(?) data and database issues jointly with the Operations PSAP Operations & Next Generation Integration Committee. The current working groups are

  • NG Data Development, including additional data providers
  • NG Business Rules
  • NG Preparation: Synchronization of MSAG, ALI, and GIS Data
  • NG LVF/ECRF – Data Creation & Maintenance, including NG9-1-1 Data Discrepancies

There are a few working groups that are currently finalizing documents that are in the NENA approval process.  The documents are 02-011 and 02-015 and address these issues:

  • Number Portability
  • Miscellaneous Data Base Issues 
  • Standards for Reporting ANI/ALI Discrepancies and No Record Founds for Wireline, Wireless and VoIP Technologies

The Data Exchange Formats/XML working group’s goal is to address database management technical issues that impact data elements as part of the overall E9-1-1 architecture. This working group has overall responsibility for the Data Technical Standards document 02-010 and all NENA XML schemas.

Any NENA member interested in joining any Data or NG Data Development Working Groups, please review the Scopes & Goals at the bottom of the page and then contact the Committee Chair or Vice Chair to be added to a specific working group.

Delaine Arnold, ENP

Independent Consultant





Delaine Arnold, ENP, has 29 years experience in the telecommunications industry and has been in the field of Enhanced 9-1-1 database management as well as a NENA member since 1989. She is an industry recognized 9-1-1 database expert who has represented NENA by making regular database standards presentation at State and National NENA conferences. Since retiring from Verizon (GTE) in 2003, she has worked as an Independent Consultant providing 9-1-1 database expertise to private and government entities.  She has been an active member of the Data Technical Committee since 1995 and has chaired many Data working groups and the Database Management Subcommittee prior to being appointed Data Technical Committee Chair in January 2004.  She also is an instructor for the NENA Database Advanced course. Delaine received her BSBM in May 2004 and her ENP in October 2004. 

Erica Aubut, ENP
State of Vermont

Erica Aubut, ENP, is the State 9-1-1 Database Administrator for the Vermont Enhanced 9-1-1 Board. Since April 1996 she has overseen the development and maintenance of Vermont’s Enhanced 9-1-1 ALI and GIS databases.  She also participated in the deployment of mapping at each of Vermont’s PSAP’s.  She has been an active member of the Data Technical Committee since 1997 and has chaired a couple of  data working groups prior to being appointed Data Technical Committee Vice-chair in September 2007.  She is currently the Chair of the NENA GIS Mapping Working Group, and Chair of the NENA Data Base Management Subcommittee.  She has been a NENA member since June 1996.  She received her ENP certification in October 2003.             Return to Top

Data Committee Links of interest

                                                                                                                    Return to Top

Document Size
20110530_DTC-NGDD_Scopes-Goals-Status.pdf 28.87 KB
NENA Technical Standards & Documents
  • 00-001 v15 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.

  • 01-001 v4.1 Organization & Document Approval Processes

    This document is written for NENA Technical Committee leadership and members. A requirement for participating in the Technical Committee process is to adhere to all procedures outlined in this document.

  • 02-010 v9 Data Formats for ALI, MSAG & GIS

    This document sets forth NENA standard formats for Automatic Location Identification (ALI) related data exchange between Service Providers and Data Base Management System Providers, a GIS data model, a Data Dictionary, and formats for data exchange between the ALI Database and PSAP Controller equipment.

  • 02-011 v7 9-1-1 Data Management

    This document sets forth NENA standards for all Service Providers (SPs) involved in providing dial tone to end users whether or not they are the 9-1-1 Database Management System Provider (DBMSP) or a SP in an Enhanced 9-1-1 area. It includes Database Maintenance, Quality measurements, INP, LNP and Number Pooling standards to be utilized for any 9-1-1 system that provides information for data display. It defines measurements that support meaningful computations to allow for a better understanding of database quality and timeliness of database updates.

  • 02-011A Excerpt: 9-1-1 Database Administration Software

    This is a portion of NENA 02-011 that has been excerpted to make this section more accessible and to assist users requiring the ability to get MSAG Updates, ANI/ALI trouble resolutions and additional information to their 9-1-1 Database Management System Provider. The associated software may be downloaded at at no charge.

  • 02-013 v3 Provisioning & Maintenance of MSAG Files to VDBs and ERDBs

    Voice over Internet Protocol (VoIP) is poised to become the predominant technology used in the telecommunications industry. As the public adopts VoIP, E9-1-1 calls will increasingly originate from VoIP users. Some VoIP telecommunications service provider networks, however, are not natively compatible with the existing E9-1-1 infrastructure. NENA is developing a view of migratory (i2) and long-term (i3) solutions that will continue to support location-based routing of E9-1-1 calls and delivery of location-related information to PSAPs.

  • 02-014 v1 GIS Data Collection & Maintenance

    This document is the NENA recommended standard for GIS data collection and GIS data maintenance. This document is meant to provide PSAP management, vendors, and other interested parties necessary guidelines for collecting and maintaining GIS data. Collection and maintenance of GIS data is most reliably accomplished by qualified, trained individuals or vendors that have received formal GIS training and instruction.

  • 02-015 v1 Resolving ANI/ALI Discrepancies & NRFs

    This NENA document sets forth standards for PSAP jurisdictions, Access Infrastructure Providers (AIP), Service Providers and Data Base Management System Providers (DBMSPs) in reporting and resolving discrepancies that occurred during a 9-1-1 call. These processes are meant to standardize ANI/ALI Trouble and “No Record Found” reporting to facilitate their timely resolution. An ANI/ALI Trouble is defined as a wrong ANI, no ANI or an ALI Discrepancy, which includes “No Record Found”. This document takes into account all the technologies available for 9-1-1 calls to date. Due to the various ways these technologies deliver 9-1-1 calls to PSAPs, there are various timelines for resolution of discrepancies.

  • 02-501 v1 Wireless ALI Data Content

    There has been a growing concern, among public safety administrators in various states and other interested parties, about the increasing degree of inconsistency in the use of specific E9-1-1 data fields for varying types of ALI-related data items. While this has provided a degree of customization to support varied PSAP data processes, it also has driven a large set of variations in SCP and MPC programming, and in ALI server data handling, along with expensive customizing of CAD and Mapping system software.

    As in other aspects of 9-1-1 data handling, what might be considered a positive situation – a high degree of flexibility – also can carry a high degree of complexity, when the national level view is considered. As a result, a balance between flexibility and complexity usually provides necessary real service capabilities with simplification and overall cost savings, due to lessened complexity.

  • 02-502 v3 NENA Company ID Registration

    This “NENA Company ID Registration Service Technical Information Document” defines the Company ID program and provides instructions for companies to register their company identification.

  • 02-503 v1 XML Namespaces

    This document dedicated to namespaces as used in XML technologies. It is intended to provide a non technical introduction to the concept of namespace and a relatively complete overview of the specific characteristics of XML namespaces.

  • 06-001 v2 Local Service Provider Interconnection Information Sharing

    This document sets forth recommended NENA standards for all Local Service Providers involved in providing dial tone to end users.

  • 06-002 v3 ALEC Service Initiation

    The purpose of the Service Initiation Guidelines is to provide guidance for 9-1-1 service initiation, as well as define the needs of the ALECs, ILECs and 9-1-1 Administrators. When an ALEC enters into a new service area, they may not know the appropriate contacts in order to obtain the required information for a successful 9-1-1 implementation. On the same note, 9-1-1 administrators/entities need notification of ALECs who will be serving customers in their jurisdiction.

  • 06-003 v2 Private Switch (PS) E-9-1-1 Database

    Recent technical developments make it possible for Private Branch Exchange Telephone Systems (PBX) to provide Telephone Station level Automatic Number Identification (ANI). This NENA Technical Reference defines the requirements and methods to accomplish the provisioning of Private Switch 9-1-1 (PS/911) data in conjunction with the use of a Multi Line Telephone System (MLTS) or Private Branch Exchange (PBX) telephone system. For the purpose of this document and to be consistent with other NENA documents, a Private Branch Exchange telephone system or PBX will be referred to as a Multi-Line Telephone System or MLTS.

  • 06-501 v2 (Converted to TRD 06-750) MLTS Model Legislation

    Converted to TRD 06-750 February 19, 2009.

  • 06-502 v1 MLTS E9-1-1 Caller Location Discovery and Reporting

    Recent technology innovations have made it critically important for organizations to address the challenge of identifying the location of the users of communications systems during emergencies in the Multi Line Telephone System1 (MLTS) environment. This paper and the accompanying diagrams will discuss many of the issues related to the location of individuals during emergencies in the MLTS environment. It will further outline the current suggested methods of dealing with the challenge using commonly available technology as recommended in this document by NENA.

  • 06-750 v3 (Previously TID 06-501) MLTS Model Legislation

    Recent technology innovations have made it important to update the MLTS Model Legislation recommended in 2000.  The following revised Policy document reflects changes in IP technology; Implementation & Testing; Training and the use of building code Fire Zones to facilitate the creation of the Emergency Response Location.

  • 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.

  • 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.  


  • 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.

  • 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.


  • 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.

  • 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.