|
The Core Services Committee is focused on 9-1-1 Authority responsibilities related to development and management of systems operations and system administration functions, including data definition and management, business rules, validation (LVF), routing (ECRF, ESRP, PRF), Location services (Legacy ALI, LIS), and any ancillary data services (e.g., wireless, wireline and VoIP data). This Committee is focused on management and administrative oriented subject matter, and also addresses service contracts (e.g., SLA’s, etc.) that may be technically or operationally focused.
Sub-Committees- Data Structures - Co-Chairs, Jason Horning and Matt Serra, ENP
Incorporates MSAG and GIS formats, ALI and PIDF-LO formats, Federal Geographic Data Committee (FGDC) integration, NIEM conformance, alignment with other stakeholder organizations (NIMS, US Fire Administration, NCIC, NTSB), etc.
- Workgroups
- XML Schema: Addresses data formats and protocol technical issues that impact data elements as part of the overall 9-1-1 architecture. This subcommittee has overall responsibility for the Data Technical Standards document 02-010 and all XML schemas.
- Civic Location Data Exchange Format: Maps IETF PIDF-LO to the FGDC United States Thoroughfare, Landmark, and Postal Address Data Standard, FGDC-STD-016-2011.
- Geospatial for NG9-1-1: Responsible for all GIS data formats and processing standards.
- NG9-1-1 Additional Data: Identifies data associated with the caller (medical info), a location (building data) and the call (legacy non-location data).
- NG Data Management - Co-Chairs, Kathy Liljequist and Ira Pyles, ENP
Develops all implementation and maintenance processes for NG9-1-1 data management. - Workgroups
- NG9-1-1 Data Management: Developing processes & procedures for data management in NG9-1-1.
- Provisioning and Maintenance of GIS data to ECR/LVF
- Policy Routing Rules: Developing a minimum set of policy rules that will be required and some optional suggestions.
- Site/Structure Address Points: Creating a NENA Information Document identifying methods for placing site/structure address points.
|
| The button to the left will take you to a form where you may volunteer to serve on this Committee. Become part of the solution and join NENA's Committee work today!
|
Standards & Documents for this Committee
Documents in this section are joint Data Technical and NGI Operations.
|
70-001 v1 - NENA Registry System
PDF (170.65 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
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.
|
|
71-001 v1 - NG9-1-1 Additional Data
PDF (105.99 KB)
[ more ]
[ hide ]
|
Administration
|
11/8/2011
|
|
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-501 v1 - Synchronizing GIS with MSAG & ALI
PDF (266.27 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
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.
|
|
71-502 v1 - Overview of NG9-1-1 Policy Rules
PDF (158.76 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
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.
|
The Data Structures subcommittee 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.
|
02-010 v9 - Data Formats for ALI, MSAG & GIS Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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.1 - 9-1-1 Data Management Link
[ more ]
[ hide ]
|
Administration
|
5/12/2012
|
|
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-011 SUPP 9-1-1 Database Administration Software Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 http://www.om2tech.com/downloads/nena_app.asp at no charge.
|
|
02-013 v3 - MSAG Files to VDB/ERDB Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
This document provides general system and process requirements for the VDB, ERDB, and 9-1-1
Administrator to maintain the MSAG and the alternate address records required to perform their
prescribed functions in the i2 architecture. This document also provides related technical and
operational policy information from NENA to facilitate implementation of the i2 architecture.
|
|
02-014 v1 - GIS Data Collection and Maintenance Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
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.
This standard also provides information on data collection to meet accuracy requirements for wireless and Voice over Internet Protocol (VoIP) 9-1-1 technologies that use x, y, z coordinates to provide location of the 9-1-1 caller.
|
|
02-015 v1 - Resolving ANI/ALI Discrepancies NRFs Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document provides national NENA best practice recommendations on wireless E9-1-1 ALI data content, ALI field usage, and data relationships, such that the E9-1-1 calltaker receives complete data with a maximum of clarity and with consistency of data elements and meaning across all carriers and their vendors.
|
|
02-502 v3 - Company ID Registration Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document sets forth recommended NENA standards for all Local Service Providers involved in providing dial tone to end users.
|
|
06-002 v2 - ALEC Service Initiation Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document will cover what is needed from all players – ALECs, ILECs and 9-1-1 Administrators to successfully implement 9-1-1. This is not an all-encompassing document and other NENA standards should be referenced.
|
|
06-003 v2 Private Switch 9-1-1 Database Standard Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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-502 v1 MLTS E9-1-1 Caller Location & Reporting Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
Identifying the location of individual callers during an emergency is a challenge that involves the individual, the organization, the governmental organizations responsible for providing public safety services and other third-party entities including those delegated various responsibilities by the government.
The purpose and scope of this document is to help policy officials as well as MLTS Operators/Managers to understand the issues related to identifying the location of users of the system during emergencies. The document points out a number of methods of dealing with this challenge giving reasons to implement and pointing out the benefits of implementing the suggested methods.
|
|
06-750 v3 MLTS Model Legislation Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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.
|
|
|
