New Mexico Administrative Code
Title 10 - PUBLIC SAFETY AND LAW ENFORCEMENT
Chapter 6 - LOCAL GOVERNMENT LAW ENFORCEMENT AGENCIES
Part 2 - ENHANCED 911 REQUIREMENTS
Section 10.6.2.10 - DATABASE DEVELOPMENT REQUIREMENTS

Universal Citation: 10 NM Admin Code 10.6.2.10

Current through Register Vol. 35, No. 18, September 24, 2024

A. Database:

(1) The grantee and its designated agents shall work with the telecommunication company(s) to verify street names, address number ranges, and emergency service zones (ESZ), postal community and other information needed to create MSAG. These same agents shall also work to assign and/or verify the 9-1-1 address associated with each landline telephone number within the PSAP's geographic boundary. All database information shall be provided to the telecommunication company(ies) in the format specified by the telecommunication company(ies) for the initial load of these databases. All road name and community database information shall be submitted and maintained in format and content compliant with the USPS Publication 28.

(2) The E911 coordinator, as defined by Subsection D of 10.6.2.11 NMAC, or his/her appointed MSAG coordinator(s), shall ensure that changes and additions to road network and the emergency service boundaries (ESZ) in the geographic boundary of the PSAP are communicated to the telecommunications company(ies) in the form of MSAG updates on a continuous and timely basis. The telecommunications company(ies) shall dictate the format and transmission method of these MSAG updates. The E911 coordinator or his/her appointed MSAG coordinator(s) and the telecommunications company shall ensure that all submitted changes, deletes and additions to the master street address guide (MSAG) are changed, deleted or added in the loaded MSAG maintained by the telecommunications company(ies). The E911 coordinator or his/her appointed MSAG coordinator(s) shall thoroughly review the loaded MSAG periodically, no less frequently than once a month, to ensure that submitted changes, deletes and additions have been properly made and entered by the telecommunications company(ies).

(3) All PSAPs shall conduct a yearly review of the MSAG, ALI and GIS databases to ensure the data in these documents is accurate and synchronized. The review shall:
(a) include the following information requested by each PSAP from the serving telecommunications company(ies) and database provider(s):
(i) complete MSAG extract for entire PSAP boundary area;

(ii) complete ALI extract for entire PSAP boundary area, to include SAUs, if any;

(iii) complete 701/709 error reports from all serving local exchange providers (telecommunications company(ies));

(iv) number of landline phones within PSAP boundaries;

(v) road centerline layer(s); and

(vi) ESZ layer(s);

(b) include output that documents a 96% or higher MSAG accuracy rate:
(i) the process used shall determine the number of accurate ALI records, after adjustment for SAUs, by comparison of a new MSAG extract to a new ALI extract; the house number, road name and ESN for each ALI record must match a corresponding MSAG record; the accuracy formula is the number of accurate ALI records found in this comparison divided by the total number of landline access numbers; this rate must equal 96% or higher;

(ii) list of SAUs found in the MSAG and ALI extracts with a timeline for correction of SAUs;

(iii) list of roads/road segments that appear in the MSAG that do not appear in the GIS; and

(iv) list of roads/road segments that appear in the GIS but that do not appear in the MSAG;

(c) be submitted annually to the division and shall be shared with E911 coordinator and GIS providers; the E911 coordinator and/or his/her designated agents, together with the GIS providers, shall work to correct these errors and inconsistencies and distribute the corrections to the appropriate telecommunications agencies, as indicated.

(4) The division requires that all municipal and county public safety answering points (PSAPs) maintain accurate MSAG, ALI and GIS databases. Except as provided for in Paragraph (5) of Subsection A of 10.6.2.10 NMAC, beginning on December 31, 2006 the MSAG and ALI must be maintained at 96% or higher accuracy. This means 96% of all landline telephone numbers in the PSAP area must be matched with MSAG-valid 9-1-1 addresses and these addresses must be loaded in the ALI database. PSAPs shall meet the required accuracy levels as a precondition to applying for and receiving funding for E911 equipment upgrades from the fund.

(5) Exceptions to Paragraph (4) of Subsection A of 10.6.2.10 NMAC may be requested in writing to the secretary of the department of finance and administration by submittal of a written plan detailing how the PSAP shall achieve the accuracy rate of 96%.
(a) The plan shall include the tasks to be completed, completion dates, individuals or entities involved and shall designate one person responsible for successful and timely execution of the plan.

(b) The secretary's decision on granting or denying an exception to Paragraph (4) of Subsection A of 10.6.2.10 NMAC is final and not appealable.

(c) The division shall continue to work with PSAPs that are denied an exception to Paragraph (4) of Subsection A of 10.6.2.10 NMAC to develop an acceptable plan.

(6) All telecommunication companies shall update the "selective routing database", MSAG and ALI within 48 hours of completion of a service order by the telecommunication company. Telecommunication companies shall ensure that all submitted changes, deletes and additions have been applied to the telecommunication databases in a timely manner. If required by telecommunication companies, the E911 coordinator or his/her appointed MSAG coordinator(s) will provide a yearly summary of changes submitted in the past year to the telecommunication company(ies).

B. ALI:

(1) Every telecommunication company providing ALI shall present uniform data, as defined by the NENA standards.

(2) The ALI shall be displayed and printed or archived immediately in the database when the 911 call is made.

(3) Each ALI data set shall include as a minimum:
(a) area code and telephone number;

(b) class of service;

(c) time in a 24-hour format (may be printed and not displayed);

(d) date (may be printed and not displayed);

(e) subscriber name or designation of non-published number;

(f) house (building) number;

(g) house number (building) suffix;

(h) directional prefix (NE, NW, SE, SW);

(i) street name including type;

(j) emergency service number location;

(k) community name;

(l) the state name;

(m) emergency service number;

(n) pilot number;

(o) emergency service number translation;

(p) any comments present;

(q) emergency response names of law enforcement, fire and EMS.

(4) ALI information shall use conventional English or NENA standard abbreviations where necessary and shall not use single letter or digit codes.

C. Database development of physical addresses: Addressing guidelines in addition to the requirements of this rule shall be established by the division. These guidelines must be followed by grantees that seek reimbursement for costs from the fund.

D. Other classes of service:

(1) The wireless working group shall advise the division on the development of procedures for:
(a) the delivery of cellular / wireless service to the 911 service area, and;

(b) the establishment of a statewide standard PSAP screen display format for the phase I and phase II information.

(2) Personal communications networks and any other future mobile and/or personal communications systems shall also be required to adhere to Subsection D of 10.6.2.10 NMAC above.

(3) Effective May 28, 2004, all new or upgraded customer owned or leased private branch exchanges (PBX) will incorporate a software package that when 911 is dialed from any extension, the extension number, name of the extension user, building address, room number and building floor, is passed through to the proper PSAP handling the call

(4) Effective May 28, 2004, the owner or lessee shall remit to the department of taxation and revenue the E911 surcharge for each activated telephone extension on the PBX.

Disclaimer: These regulations may not be the most recent version. New Mexico may have more current or accurate information. We make no warranties or guarantees about the accuracy, completeness, or adequacy of the information contained on this site or the information linked to on the state site. Please check official sources.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.