10.6.2.1 Issuing Agency: Department of Finance and Administration, Local Government Division.
[10.6.2.1 NMAC – Rp, 10.6.2.1 NMAC, 05-15-2006]
10.6.2.2 Scope: The state, counties, and incorporated cities, towns, and villages.
[10.6.2.2 NMAC – Rp, 10.6.2.2 NMAC, 05-15-2006]
10.6.2.3 Statutory Authority: This rule is established under the authority granted in Section 63-9D-8.1 NMSA 1978 and is deemed necessary to implement the Enhanced 911 Act, Sections 63-9D-1 et seq. NMSA 1978.
[10.6.2.3 NMAC – Rp, 10.6.2.3 NMAC, 05-15-2006]
10.6.2.4 Duration: Permanent.
[10.6.2.4 NMAC – Rp, 10.6.2.4 NMAC, 05-15-2006]
10.6.2.5 Effective Date: May 15, 2006, unless a later date is specified at the end of a section.
[10.6.2.5 NMAC – Rp, 10.6.2.5 NMAC, 05-15-2006]
10.6.2.6 Objective: The purpose of Part 2, Chapter 6 is to implement the Enhanced 911 Act. These regulations are designed to support the development, operation, and maintenance of a dependable, standardized E911 system. This legislation establishes a program for the procurement, leasing, installation, and upkeep of E911 equipment, telecommunicator training, database preparation, database updates, adherence to Federal Communications Commission (FCC) guidelines for phase I and phase II wireless E911 service, and E911 network expenses as required for an E911 system.
[10.6.2.6 NMAC – Rp, 10.6.2.6 NMAC, 05-15-2006]
10.6.2.7 Definitions:
A. 701/709 Error Report: This is a report from local exchange carriers serving a Public Safety Answering Point (PSAP) area, detailing phone numbers that failed to load into the 911 Automatic Location Identification (ALI) database due to a Master Street Address Guide (MSAG) or other error. A 701 error indicates a house number outside the MSAG range, while a 709 error signifies a street not found in the MSAG.
B. 911 Emergency Surcharge: This refers to the uniform monthly fee applied to each access line in the state and each active number for commercial mobile radio service subscribers with a billing address in New Mexico.
C. 911 Line/Trunk: A line/trunk accessed by dialing 911, terminating at a PSAP. In basic 911 systems, these lines are one-way incoming. Outgoing calls are limited to conferencing or transferring to another location while an incoming 911 call is active.
D. 911 PSAP Equipment: This includes equipment at the Public Safety Answering Point (PSAP) directly related to E911 system operation. Examples include Automatic Number Identification (ANI) displays, Automatic Location Identification (ALI) displays, controllers, combined ANI/ALI displays, printers, generators, Uninterruptible Power Supply (UPS), Telecommunications Device for the Deaf (TDD) for hearing impaired, 24/7 continuous logging recorders, workstations, wireless phase I and/or II mapping equipment, associated software, telephones, and other necessary equipment for dispatching emergency E911 calls.
E. 911 Service Area: The area designated to receive enhanced 911 service by the fiscal agent, local governing body, or the division.
F. Access Tandem: The device that routes 911 calls to the appropriate PSAP.
G. ADA: Americans with Disabilities Act of 1990.
H. Alternate Routing: An optional feature that automatically redirects 911 calls to a pre-set alternate location if all 911 trunks from a central office or PSAP are out of service.
I. Answering Position: A station within a PSAP equipped with an ANI and/or ALI display, printer or electronic storage, telephone, and/or wireless call map display used to receive and process incoming E911 calls.
J. Automatic Location Identification (ALI): An E911 feature displaying the physical address of the phone number used to make the call. It uses a data storage and retrieval system to link phone numbers to physical addresses. ALI information can include address details (including room or floor), responsible law enforcement, fire, and medical agencies, service type (e.g., residence, PBX, Centrex, coin), and the name associated with the phone number.
K. Automatic Number Identification (ANI): An E911 feature, also found in basic 911, that automatically displays the caller’s phone number at the PSAP. While typically the caller’s number, it may differ in older PBX systems where the main system number is displayed, regardless of the extension used.
L. Basic 911 Service: A telephone service that connects a person dialing 911 to a PSAP through standard telephone facilities.
M. Board: The state board of finance.
N. Called Party Hold: A basic 911 feature allowing a PSAP telecommunicator to maintain control of a 911 call even if the caller hangs up.
O. Central Office (CO): Telephone company equipment providing service to the public. An E911 service area may contain multiple COs.
P. Continuous Logging Recorder: A device recording date, time, voice, TDD/TTY communications, and other transaction data related to PSAP call processing 24/7.
Q. Cost Recovery Plan (Plan): A plan submitted by Communication Mobile Radio Service (CMRS) carriers to the division to detail allowable costs.
R. CMRS: Communication Mobile Radio Service carriers.
S. Database: Information collected, formatted, and distributed, essential for E911 system function, including Geographic Information System (GIS) addressing and digital mapping data.
T. Default Routing (Default Answering): A standard E911 feature activated when selective routing fails due to ANI failure, garbled digits, or other issues.
U. Designated Agents: Partners such as county assessors, city/county GIS personnel, pueblos/tribes within their area, vendors, or any entity performing addressing, mapping, GIS, or MSAG tasks for a PSAP.
V. Diverse Routing: Routing calls through different circuit paths to prevent total 911 system failure if a single circuit is disabled (if available).
W. Division: The local government division of the department of finance and administration.
X. E911 Coordinator: The person designated by the PSAP to liaise with the division and telecommunication companies on 911 matters.
Y. Emergency Service Number (ESN) / Emergency Service Zone (ESZ): A number representing a unique combination of emergency services (law enforcement, fire, EMS) for a specific address range within a geographic area or ESZ.
Z. Enhanced 911 Equipment: PSAP equipment directly related to enhanced 911 system operation, including ANI/ALI controllers and displays, printers, logging recorders, call detail recording software, call center workstations, training equipment, latitude and longitude base station or cell site location data, and GIS equipment for location maps and ESZ data for landline and wireless callers.
AA. Enhanced 911 Service: Service delivering both ANI and ALI to the PSAP.
BB. Enhanced 911 System (E911): A landline and wireless system using database management, mapping, and electronic switching for rapid and reliable emergency response. Key features include:
(1) Tandem or selective call routing to the appropriate PSAP.
(2) Automatic Number Identification (ANI) and Automatic Location Identification (ALI).
(3) One or more communication access paths between users in different areas via a network for voice or data, with potentially limited or open access and various analog, digital, switching, or transmission technologies.
(4) Relay of wireless 911 caller’s number, base station or cell site location, and longitude and latitude of the caller’s location to the designated PSAP.
CC. Fiscal Agent: The local governing body administering grants from the fund for a specific locality or region by agreement.
DD. Fund: The enhanced 911 fund, as defined by Section 63-9D-8 NMSA 1978, created in the state treasury to fund the purchase, lease, installation, or maintenance of enhanced 911 equipment, as defined by Section 63-9D-3 (K) NMSA 1978, necessary for an enhanced 911 system.
EE. GIS: Geographic Information System.
FF. GIS Providers: Individuals, entities, or agencies creating or managing GIS addressing and mapping data within a PSAP service area.
GG. Forced Disconnect: A basic 911 feature allowing a PSAP attendant to disconnect a 911 call, preventing intentional line jamming. E911 uses a time-out CO feature for this.
HH. Grantee: A county board of commissioners or municipality governing body, as defined in the Municipality Code, that has received a grant under the E911 Act.
II. Instant Playback Recorder: A device allowing immediate replay of audio from a 911 call and radio communications at the E911 position.
JJ. Local Exchange Access Line: A telephone line connecting a phone to the telecommunications company’s central office.
KK. Local Exchange Area: A geographic area encompassing one or more local communities served by a telecommunications company.
LL. MSAG Coordinator(s): Person(s) responsible for ensuring the Master Street Address Guide (MSAG) is accurate and current.
MM. Master Street Address Guide (MSAG): A document or computer file listing physical street names (including prefix, suffix, and directional), address ranges, Emergency Service Number (ESN), and other routing codes used in the Data Management System (DMS) of an E911 system with selective routing and/or ALI.
NN. Monthly Recurring Cost (MRC): Ongoing monthly costs for CMRS carriers, including trunking (T-1s to 911 access tandems) and wireless system service provider (3rd party vendor) costs.
OO. National Emergency Number Association (NENA): The national association for 911 service telecommunications professionals. NENA provides PSAP policy recommendations and guidance on wireless E911 call handling. Members include government agencies, telecommunication companies, and communications service and equipment vendors.
PP. Network: Any system providing communication paths between users in different locations, designed for voice, data, or both, with potentially limited or open access and using analog, digital, switching, or transmission technologies.
QQ. Non-Recurring Cost (NRC): One-time costs for CMRS carriers, such as initial connection fees to 911 access tandems and wireless system service provider (3rd party vendor) costs.
RR. Phase I Cellular Service: Wireless carriers deliver a cellular 911 call to the nearest PSAP. The PSAP receives the caller’s phone number (ANI) and a map location of the carrier’s tower handling the call, indicating an approximate area where the caller is located, ranging from a square mile in a city to several miles along a highway.
SS. Phase II Cellular Service: Wireless carriers deliver a cellular 911 call to the nearest PSAP and provide the caller’s phone number (ANI) and approximate location (ALI) using latitude and longitude coordinates with a probability factor.
TT. Primary Public Safety Answering Point: A PSAP equipped with ANI and ALI displays, wireless mapping equipment, and the initial point of reception for an E911 call. It serves its designated 911 service area and potentially other municipalities as determined by the service area committee.
UU. PSAP Consolidation: Combining multiple PSAPs within a county into a single PSAP to serve the constituents previously served by individual PSAPs.
VV. PSAP Serving Area: The geographic area containing a PSAP capable of answering and appropriately responding to all 911 calls.
WW. Public Safety Agency: A public agency providing law enforcement, fire, medical, and/or other emergency services.
XX. Public Safety Answering Point (PSAP): A 24-hour local communication center receiving 911 service calls and either directly dispatching emergency services or relaying calls to the appropriate public or private safety agency.
YY. SAU (Specific Address Unknown): A record in the ALI database (with corresponding MSAG records) lacking a valid street address.
ZZ. Secondary Public Safety Answering Point: A facility equipped like primary PSAPs with ANI, ALI displays, and other features. It receives 911 calls transferred from the primary PSAP or via alternate routing when calls cannot reach the primary PSAP.
AAA. Selective Routing Database: A routing table containing phone number to ESN relationships, determining 911 call routing.
BBB. Selective Transfer: On systems with selective transfer, calls are routed to the correct secondary PSAP(s).
CCC. Service Area: The geographic area where entities participating in a 911 system are responsible for responding to all 911 calls and ensuring appropriate emergency assistance is dispatched.
DDD. Speed Calling: Abbreviated dialing programmed in a central office to allow calling seven or ten-digit numbers by dialing just one or two digits. E911 provides a separate 30-number (two-digit) speed dial list for each primary and secondary PSAP as a standard feature.
EEE. Tandem Routing or Selective Routing: A feature routing an E911 call to the designated primary PSAP based on the caller’s phone number. This routes calls to the PSAP responsible for emergencies at the caller’s address, based on the ANI number and associated Emergency Service Number (ESN) in the tandem office.
FFF. Telecommunications Company: An entity providing public telecommunication services capable of originating an E911 call, including database management companies contracted to create or maintain PSAP MSAGs.
GGG. Telephone Device for the Hearing Impaired/Teletype (TDD/TTY): Telecommunication devices with modems enabling typed telephone conversations for people with hearing or speech impairments.
HHH. Wireless / Cellular: A phone linked to the Public Switched Telephone Network (PSTN) via a radio link through a company providing radio links from towers/antenna sites, connecting wireless callers to the PSTN. Phase I wireless companies connect callers to the nearest PSAP using cell tower location and selective routing.
III. WE911: Wireless Enhanced 911.
JJJ. Wireless Working Group (WWG): An advisory committee for phase I and phase II PSAP implementation, potentially including personnel from the division, PSAP, local and/or Qwest telephone company, wireless call-routing vendor, NM Department of Public Safety (DPS), and local GIS staff. This group operates at the division’s discretion and may be dissolved when no longer needed.
KKK. Uninterruptible Power Supply (UPS): A system providing power when the normal power supply is insufficient.
LLL. USPS Publication 28: A comprehensive guide by the United States Postal Service (USPS) governing acceptable road naming and addressing standards for E911 MSAG and addressing.
MMM. Vendor: A person providing enhanced 911 equipment, systems, services, or network support.
[10.6.2.7 NMAC – Rp, 10.6.2.7 NMAC, 05-15-2006]
10.6.2.8 Introduction:
A. In New Mexico, the responsibility and authority for delivering emergency medical services, fire protection, and law enforcement primarily resides with the state, counties, and municipalities. This holds true even when supplemental services are provided by private ambulance companies, independent public authorities, and non-profit organizations with limited internal security or fire protection.
B. An E911 telephone emergency system enhances basic 911 by:
(1) Expanding the capabilities of the basic 911 emergency telephone number.
(2) Reducing response times, thereby minimizing loss of life and property.
(3) Providing automatic routing to the appropriate Public Safety Answering Point.
(4) Immediately displaying the caller’s phone number, name, and address or location.
(5) Identifying callers, which helps in reducing the misuse of the emergency system.
[10.6.2.8 NMAC – Rp, 10.6.2.8 NMAC, 05-15-2006]
10.6.2.9 Guidelines:
A. The division will establish guidelines for basic and E911 service, system, equipment, and network design and maintenance, following nationally recognized best practices.
B. E911 call information must adhere to the national NENA standards.
[10.6.2.9 NMAC – Rp, 10.6.2.9 NMAC, 05-15-2006]
10.6.2.10 Database Development Requirements:
A. Database:
(1) Grantees and their designated agents must collaborate with telecommunication companies to verify street names, address number ranges, Emergency Service Zones (ESZs), postal communities, and other necessary data for creating the MSAG. These agents also verify 9-1-1 addresses associated with each landline phone number within the PSAP’s boundary. All database information must be provided to telecommunication companies in their specified format for initial database loading. Road name and community database information must be submitted and maintained in compliance with USPS Publication 28 format and content.
(2) The E911 coordinator, or appointed MSAG coordinator(s), as defined in Subsection D of 10.6.2.11 NMAC, is responsible for ensuring that changes and additions to the road network and ESZs within the PSAP’s geographic area are communicated to telecommunications companies as MSAG updates regularly and promptly. Telecommunications companies will dictate the format and transmission method for these updates. The E911 coordinator or MSAG coordinator(s) and the telecommunications company must ensure all submitted changes, deletions, and additions to the MSAG are correctly updated in the telecommunication company’s loaded MSAG. The E911 coordinator or MSAG coordinator(s) should periodically review the loaded MSAG, at least monthly, to confirm that all submitted updates have been accurately implemented by the telecommunications company.
(3) All PSAPs must conduct an annual review of MSAG, ALI, and GIS databases to ensure data accuracy and synchronization. This review must:
(a) Include the following information requested by each PSAP from their telecommunications company(ies) and database provider(s):
(i) Complete MSAG extract for the entire PSAP boundary area.
(ii) Complete ALI extract for the entire PSAP boundary area, including any SAUs.
(iii) Complete 701/709 error reports from all serving local exchange providers (telecommunications companies).
(iv) Number of landline phones within PSAP boundaries.
(v) Road centerline layer(s).
(vi) ESZ layer(s).
(b) Include output demonstrating a 96% or higher MSAG accuracy rate:
(i) The process used will determine the number of accurate ALI records, adjusted for SAUs, by comparing a new MSAG extract to a new ALI extract. For each ALI record to be considered accurate, the house number, road name, and ESN must match a corresponding MSAG record. The accuracy formula is: (number of accurate ALI records / total landline access numbers) x 100%. This rate must be 96% or higher.
(ii) List of SAUs found in MSAG and ALI extracts, with a timeline for correction.
(iii) List of roads/road segments in the MSAG but not in the GIS.
(iv) List of roads/road segments in the GIS but not in the MSAG.
(c) Be submitted annually to the division and shared with the E911 coordinator and GIS providers. The E911 coordinator and/or designated agents, along with GIS providers, will work to correct errors and inconsistencies and distribute corrections to the appropriate telecommunications agencies.
(4) The division requires all municipal and county PSAPs to maintain accurate MSAG, ALI, and GIS databases. Except as provided in Paragraph (5) of Subsection A of 10.6.2.10 NMAC, MSAG and ALI accuracy must be 96% or higher starting December 31, 2006. This means 96% of all landline phone numbers in the PSAP area must be matched with MSAG-valid 9-1-1 addresses, and these addresses must be in the ALI database. PSAPs must meet these accuracy levels to qualify for E911 equipment upgrade funding from the fund.
(5) Exceptions to Paragraph (4) of Subsection A of 10.6.2.10 NMAC may be requested in writing from the secretary of the department of finance and administration, including a written plan detailing how the PSAP will achieve the 96% accuracy rate.
(a) The plan must include tasks, completion dates, responsible individuals/entities, and a designated person accountable for the plan’s successful and timely execution.
(b) The secretary’s decision on granting or denying an exception is final and not subject to appeal.
(c) The division will continue to assist PSAPs denied an exception to develop an acceptable plan.
(6) All telecommunication companies must update the selective routing database, MSAG, and ALI within 48 hours of completing a service order. They must ensure all submitted changes, deletions, and additions are applied to telecommunication databases promptly. If required, the E911 coordinator or 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 must present uniform data, as defined by NENA standards.
(2) ALI data must be displayed and printed or archived in the database immediately when a 911 call is made.
(3) Each ALI data set must include at least:
(a) Area code and telephone number.
(b) Class of service.
(c) Time in 24-hour format (may be printed, not displayed).
(d) Date (may be printed, not displayed).
(e) Subscriber name or designation for non-published numbers.
(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) State name.
(m) Emergency service number.
(n) Pilot number.
(o) Emergency service number translation.
(p) Any comments.
(q) Emergency response agency names (law enforcement, fire, and EMS).
(4) ALI information must use conventional English or NENA standard abbreviations and not use single letter or digit codes.
C. Database Development of Physical Addresses: The division will establish addressing guidelines in addition to these rules. Grantees seeking fund reimbursement must follow these guidelines.
D. Other Classes of Service:
(1) The Wireless Working Group will advise the division on developing procedures for:
(a) Delivering cellular/wireless service to the 911 service area.
(b) Establishing a statewide standard PSAP screen display format for phase I and phase II information.
(2) Personal communications networks and other future mobile/personal communication systems must also adhere to Subsection D of 10.6.2.10 NMAC.
(3) Effective May 28, 2004, all new or upgraded customer-owned or leased Private Branch Exchanges (PBX) must incorporate software that, when 911 is dialed from any extension, transmits the extension number, user name, building address, room number, and floor to the appropriate PSAP.
(4) Effective May 28, 2004, PBX owners or lessees must remit the E911 surcharge for each activated telephone extension on the PBX to the department of taxation and revenue.
[10.6.2.10 NMAC – Rp, 10.6.2.10 NMAC, 05-15-2006]
10.6.2.11 PSAP Equipment, Acquisition, and Disbursement of Funds:
A. PSAP equipment must handle emergency call volumes to meet public needs and be compatible with the telecommunication company’s 911 network and database.
B. To qualify as a PSAP, applicants must have a 24/7 communication facility.
C. At a minimum, a PSAP must be equipped with:
(1) Automatic Number Identification (ANI).
(2) Automatic Location Identification (ALI).
(3) Call detail information.
(4) Default routing (default answering) until selective routing is approved by the division.
(5) Ability to print call detail information, either on paper or electronically.
(6) Ability to transfer voice or TDD/TTY and data.
(7) Selective and fixed button transfer on E911 systems.
(8) Minimum 30-minute Uninterruptible Power Supply (UPS).
(9) TDD/TTY communication capability at each 911 answering position.
(10) Switch hook status indication.
(11) For basic 911, ring back, caller hold, and caller disconnect capabilities.
(12) 911 related calls passing through switching equipment must support transfer, conference, speed dialing, and call supervision until successful transfer or termination.
(13) Each PSAP must have at least one E911 answering position. Multiple positions must be similarly equipped with access to all incoming 911 lines, outgoing dedicated/switched lines, tie lines, and dial-out lines.
(14) Each PSAP must have a continuous logging recorder with:
(a) Capacity to record both sides of conversations on all incoming 911 calls and all radio communications during 911 call dispatch.
(b) Continuous documentation of year, date, and time for each recorded event and the capability to record both voice and TDD/TTY.
(15) For reliability, each PSAP must have instant playback voice recorders at each call answering and radio position.
(16) Each 911 trunk must identify incoming emergency calls with both audible and visual indicators, with different indicators for landline and wireless trunks.
(17) Each PSAP must have sufficient 911 answering positions and staff to ensure that 90% of all 911 calls are answered within 10 seconds and the remaining 10% within 20 seconds during normal peak operating periods. Staffing levels may vary during the day to meet this requirement.
(18) For quality assurance and training, supervisor PSAP answering equipment must be provided to monitor incoming emergency calls.
(19) Each PSAP may be provided with equipment furniture to adequately support E911 and radio equipment, telecommunicators, and dispatchers.
(20) Each PSAP will have a backup generator capable of maintaining PSAP operation until commercial power is restored.
(21) Each PSAP will have a written agreement with a fully equipped PSAP capable of taking calls and dispatching emergency responses. PSAP transfer is done using a make-busy circuit or by calling the E911 center to reroute 911 calls to the agreed-upon PSAP.
D. PSAP Administration:
(1) Every grantee in the E911 system must designate a coordinator to work with the division and telecommunication companies on 911 issues.
(2) All coordinators working with the division and telecommunication companies must have a personal work email address for receiving information about training, consolidation, and required information transmittal.
(3) Only incorporated municipalities, counties, state police, Native American tribes or pueblos, public safety agencies, or their authorized agents may receive 911 calls.
(4) The 911 number is to receive incoming emergency calls transferred to the PSAP from other PSAPs for alternate and default routing.
(5) 911 trunks must not be used for outgoing calls, except for transferring 911 calls if there is an active incoming 911 call on the line/trunk.
(6) 911 trunks are solely for receiving emergency 911 calls at primary PSAPs and transferring 911 calls to other PSAPs.
(7) At least one PSAP must operate 24 hours a day within the 911 service area. Municipalities and counties must participate and assist with operational costs.
(8) Each PSAP must maintain an up-to-date detailed profile, including at least:
(a) Exact PSAP address.
(b) Number and type of positions.
(c) Type of equipment, including E911 call answering equipment, telephone switching equipment, wireless mapping equipment, CAD system, radio system, and make and model of UPS and backup generator.
(d) Number and type of dedicated/switched voice/data circuits.
(e) Routing central office and PSAP end office.
(f) Maintenance control center details: company name, physical address, phone number, email address, and E911 equipment point of contact and voice logging recorder contact (if different).
(g) PSAP coordinator and alternate contact name, address, phone number, and PSAP email address.
(h) Type and manufacturer of CAD system (if any) and voice logging recorder.
(i) GIS representative contact information: physical address, phone number, and email address.
(9) Each PSAP must maintain at least one unpublished seven-digit emergency number for receiving transferred emergency calls.
(10) The PSAP is responsible for coordinating the emergency service listing in local telephone directories. Each PSAP will have a published seven-digit number for non-emergency calls.
(11) Subscriber information provided for the 911 system must only be used for emergency response or ensuing investigations or prosecutions directly resulting from a 911 call, including investigations of false reports.
(12) All voice and TDD/TTY recordings of incoming 911 calls must be retained according to state records center and archives regulations for municipal police and county sheriff records.
(13) Except for devices like TDD/TTY used by disabled persons, automatic alarms or alerting devices that automatically dial 911 and transmit prerecorded signals or messages to the PSAP on a 911 line are prohibited.
(14) PSAP personnel must program and maintain a list of fixed and auto-dial transfer features to transfer 911 calls outside their jurisdiction to the appropriate PSAP using the dedicated/switched 911 network. When transferring, the PSAP must announce to the receiving PSAP that they are transferring a call for service and stay on the line briefly.
(15) Call handling procedures and PSAP operations must follow division-established training guidelines. Each PSAP must be able to:
(a) Transfer 911 calls to their backup PSAP or another PSAP within or outside their 911 service area.
(b) Directly dispatch public safety services or relay information to a public safety agency. PSAPs that transfer 911 calls to a 7-digit administrative line for outside agency dispatch must have a liability release from the dispatch agency on file and provide a copy to the Local Government Division (LGD).
(c) Directly dispatch public safety services.
(16) Emergency units dispatched outside their jurisdiction in response to a request must provide services until relieved by the responsible public safety agency.
(17) All PSAPs must be staffed 24/7 by personnel certified by the state department of public safety under Section 29-7A-4 NMSA 1978. Staffing levels can vary during the day to meet this requirement.
(18) Special circumstances:
(a) In compliance with ADA, each PSAP must have procedures for handling TDD/TTY calls from speech and hearing-impaired individuals, including using TDD call detectors and diverters.
(b) PSAPs should develop procedures for unanswered or silent 911 calls and are urged to dispatch a public safety response unit if there is no response to a callback.
(19) Every PSAP will prepare an annual report for the division, including information from Paragraphs (8), (9), (14), and (18) of Subsection D of 10.6.2.11 NMAC. Reports should be sent electronically (email) or by mail to the division by June 30th each year.
(20) 911 callers may only be transferred once to another PSAP. If the caller is not connected to the appropriate PSAP after transfer, the receiving PSAP must gather all necessary information and contact the correct PSAP for response.
(21) When a 911 caller is transferred, the transferring PSAP must announce this to the receiving PSAP and may stay on the line until released.
(22) Each PSAP must create a contingency plan for continued emergency service during PSAP outages.
E. Funding, Eligible Costs:
(1) Costs for enhanced 911 equipment necessary for E911 service can be recovered from the fund, including purchase, lease, installation, equipment furniture, training, and maintenance, except for CAD, mobile and portable radio equipment, and logging recorder maintenance.
(2) Funding for equipment indirectly related to the E911 system is the grantee’s responsibility unless approved by the division.
(3) Network capability costs and database services for an E911 system are recoverable from the fund.
(4) Addressing costs, including equipment and labor, may be funded based on demonstrated need and fund availability, potentially including software maintenance for GIS/rural addressing departments creating data for PSAPs.
(5) Grantees with division approval can recover course registration costs for telecommunicator and GIS personnel training from the fund.
(6) With prior division approval, travel mileage and per diem for telecommunicator and GIS personnel training may be reimbursed. Requests without prior approval will not be reimbursed.
(7) Mapping equipment and network costs for wireless phase I and phase II, and cost recovery for wireless service providers.
F. Funding, Ineligible Costs:
(1) Basic termination charges for disconnecting telephone equipment replaced with 911 equipment.
(2) Capital outlay expenditures like buildings, remodeling, moveable chattels, communication towers, and equipment not directly related to a 911 telecommunicator position.
(3) Mobile radios, pagers, or cellular telephones.
(4) Seven-digit transfer-to-lines.
(5) Incoming emergency seven-digit line groups.
(6) Costs for implementing or maintaining basic or E911 systems or features not approved in writing by the division.
(7) Private line circuit costs unless approved by the division.
(8) Directory listings.
(9) Call volume indicators used after the initial twelve-month implementation or when not otherwise justified.
(10) Maintenance costs for radio equipment and other miscellaneous equipment not classified as 911 PSAP equipment.
(11) Direct or indirect overhead costs like retirement contributions, health insurance, labor, departmental operations overhead, rent, utilities, or building remodeling.
(12) Reimbursement for equipment not pre-approved by the division before purchase.
[10.6.2.11 NMAC – Rp, 10.6.2.11 NMAC, 05-15-2006]
10.6.2.12 Review and Approval Process:
A. After requesting enhanced 911 service from a telecommunications company or CMRS, a local governing body, acting as the fiscal agent for a PSAP, may recover approved costs from the fund through an ordinance or resolution.
B. The PSAP and fiscal agent submit a formal written funding request to the E911 program manager at the division for equipment upgrades or new equipment to meet PSAP responsibilities or other eligible costs.
C. If applicable, a division project manager will visit the PSAP site to assess the need and funding eligibility for requested equipment and its alignment with PSAP consolidation policy.
D. If the division deems the request meritorious, eligible for funding, and consistent with consolidation policy after discussions with the PSAP manager and clients, the PSAP, with division collaboration, will request price proposals from state price agreement vendors. The division encourages PSAP consolidation and will discuss consolidation feasibility, considering:
(1) Age and remaining useful life of existing equipment.
(2) Estimated maintenance costs for continued use of existing equipment.
(3) Equipment manufacturers’ commitment to continued maintenance support.
(4) Continued use of analog technology versus upgrading to digital technology.
(5) Potential impact of wireless E911 implementation on the PSAP and its existing equipment.
(6) PSAP vendors’ and telephone companies’ readiness to install equipment.
(7) PSAPs’ and clients’ desire to consolidate all PSAP/dispatch functions.
(8) Municipal and county governments’ ability to fund supporting infrastructure for a consolidated PSAP.
E. If the division finds the request without merit or funding is inadequate, it will be returned to the PSAP as unapproved.
F. Validated PSAP requests that pass the above process will be forwarded in writing by the PSAP and fiscal agent to the division director for approval to place the request on the board of finance meeting agenda.
G. Any items deemed inappropriate by the division director will not be approved for the board meeting agenda. Rejected requests will be returned as unapproved.
H. The division will present the E911 funding project list to the board for approval.
I. Fully executed grant agreements and subcontracts must be provided to the division for official records. Subcontracts must comply with the New Mexico Procurement Code and regulations if necessary.
[10.6.2.12 NMAC – Rp, 10.6.2.12 NMAC, 05-15-2006]
10.6.2.13 Geographic Information Systems (GIS) Standards:
To ensure effective statewide use and integration of road centerline shapefiles, standards are needed for attribute data consistency and spatial data development by GIS entities. Under 63-9D-4 NMSA 1978, local governing bodies in an enhanced 911 service area must provide GIS addressing and digital mapping to the PSAP serving them, as follows:
A. Attribute data content must be derived from NENA standards. The format and structure are based on, but not identical to, NENA standards.
B. The datum for geographic data must be North American Datum 1983 (NAD 83), and data must be in a New Mexico state plane or universal transverse mercator (zone 12 or 13) projection. Geographic data must be spatially complete for each GIS entity’s area of responsibility but must not extend beyond it. Road features extending beyond one entity’s area must align with the same feature maintained by the adjacent entity.
C. Spatial accuracy of geographic features must represent the actual feature at a 1:5000 scale. All geographic features must have clean topology and be usable to form a statewide road network with connectivity. All attribute and geographic data must be kept current through regular maintenance.
D. To ensure accurate dispatch call mapping, attribute data associated with GIS data must be synchronized with MSAG and ALI data. This includes all components of road names and address ranges. Road name designations, including spelling, directionals, suffixes, and abbreviations, must match MSAG road names. GIS road ranges must match or be included within MSAG ranges.
E. The PSAP must update the MSAG within 10 working days to reflect changes in addressing and mapping.
[10.6.2.13 NMAC – Rp, 10.6.2.13 NMAC, 05-15-2006]
10.6.2.14 Planning and Implementation of Enhanced Wireless Service:
A. E911 service, including phase I and phase II wireless, must be provided throughout telecommunication company service areas, ideally implemented countywide or regionally.
B. Where a telecommunication company’s local exchange area spans multiple E911 service areas, the Wireless Working Group (WWG) is responsible for initiating and establishing E911 wireless service areas.
C. The division has final approval authority after the PSAP and telecommunication company identify the need for selective routing and the associated network for call processing. The WWG, through the division, has final authority over the selective routing of wireless vendor coverage areas.
D. If the grantee, E911 coordinator, or MSAG coordinator(s) request an MSAG and/or telecommunication company old-to-new records in print or electronic format, the telecommunication company must comply within 20 working days.
E. Once MSAG and ALI are completed and loaded into the database, they are jointly owned by the PSAP and the telecommunications company.
F. The telecommunications company must provide an updated MSAG to the PSAP upon installation completion and as requested thereafter.
G. The telecommunications company must update the data management system and selective routing database within 48 hours of service order completion.
H. The division has final approval authority over the addressing system and GIS system used to develop the database supporting E911 and wireless E911 services.
[10.6.2.14 NMAC – Rp, 10.6.2.14 NMAC, 05-15-2006]
10.6.2.15 PSAP Consolidation:
A. The division mandates that municipal and county PSAPs within contiguous county boundaries consolidate their 911 call answering and radio dispatch functions into one consolidated PSAP per county. Only the consolidated PSAP in each county can apply for and receive funding for E911 equipment, maintenance, training reimbursement, trunk and ALI lines, and E911 call taking and mapping equipment from the E911 fund for phase I and phase II enhanced wireless service.
B. Albuquerque Police Department PSAP and Bernalillo County PSAP are exempt from 10.6.2.15 NMAC due to the large population served, as are Department of Public Safety district PSAPs and Native American pueblos and tribal police.
C. Exceptions to 10.6.2.15 NMAC can be requested in writing with full justification to the division.
(1) Justification must include cost considerations, population served, and proximity to the PSAP’s backup PSAP.
(2) The division’s decision on exception requests is final and not appealable.
D. Municipal and county PSAPs within a county’s contiguous boundaries had one year from May 28, 2004, to develop a consolidation plan and enter into an approved joint powers agreement (JPA) for consolidating E911 call answering and radio dispatch into a single county PSAP.
(1) Consolidation plans are subject to division approval/disapproval.
(2) PSAPs must consolidate as per the plan, unless granted an exception, to be eligible for E911 equipment upgrade funding.
(3) Failure to meet consolidation plan and JPA requirements may result in termination of the 911 grant agreement with the PSAP governing bodies.
E. The division will assist municipal and county governments in preparing consolidation plans to meet these requirements.
[10.6.2.15 NMAC – Rp, 10.6.2.15 NMAC, 05-15-2006]
10.6.2.16 Telecommunicator / Dispatcher Training:
Under Section 63-9D-4A NMSA 1978, local governing bodies must require PSAPs to employ properly trained staff as per the Public Safety Telecommunicator Training Act. Telecommunicators and dispatchers are certified for two years, with recertification required every two years thereafter, needing 20 hours of specified training per interval. Course requirements for recertification are in 10.29.7 NMAC. Each PSAP manager or supervisor will appoint a training officer in writing, whose contact information will be provided to the division and updated upon replacement. The training officer is responsible for:
A. Developing PSAP policies and procedures to ensure all telecommunicators and dispatchers receive required training.
B. Maintaining accurate written training records for each individual.
C. Submitting semi-annual training progress reports to the division in June and January, through the PSAP manager or supervisor, including the number of trained personnel, completed courses, training yet to be completed, and any issues meeting 10.29.7 NMAC training requirements. See Subsection E of 10.6.2.11 NMAC for training reimbursement information.
[10.6.2.16 NMAC – Rp, 10.6.2.16 NMAC, 05-15-2006]
10.6.2.17 Wireless Cost Recovery Guidelines:
After requesting Wireless Enhanced E911 (WE911) from a CMRS provider, local governing bodies may recover CMRS wireless E911 service costs that meet 10.6.2.17 NMAC requirements from the fund, as per Subsection G of Section 63-9D-8 NMSA 1978. The division, on behalf of local bodies, will directly pay or reimburse CMRS for WE911 service costs. To maintain fund adequacy for E911 service and equipment, the division will only reimburse costs incurred by CMRS to provide enhanced wireless 911 service to municipal and county PSAPs that comply with the following:
A. All CMRS carriers must submit a detailed cost recovery plan, invoices, and status reports to the division meeting these criteria:
(1) Plans and invoices must include one-time Non-Recurring Costs (NRC) for connection fees to 911 access tandems and NRC for the wireless system service provider (3rd party vendor).
(2) Plans and invoices must include CMRS carriers’ Monthly Recurring Costs (MRC) for trunking (T-1s to 911 access tandems) and MRC for the wireless systems service provider (3rd party vendor).
(3) Other CMRS carrier costs are not currently eligible for cost recovery.
B. Plans or invoices submitted by a third party on behalf of a CMRS carrier must include a letter of agency. No third-party submissions will be reviewed until the division receives agency notice from the CMRS carrier.
C. Plans must be submitted yearly by March 31st as a comprehensive statewide plan based on current circumstances, detailing: cell site and subscriber numbers per county, projected NRC and MRC per county based on cost recovery guidelines, type of wireless services, jurisdictions served, wireless network service provider relationships, customer/subscriber count in New Mexico, legal entity name, remittance name and tax number for state tax remittances, and contact information for tax and remittance discussions.
D. Plans must provide a detailed explanation of each cost item.
E. Plans must include a map showing the licensed area and actual coverage area.
F. Plans must include a sample monthly invoice from the CMRS carrier, clearly separating MRC and NRC charges by county. Payments will only be made to the carrier, not third-party agents.
G. Plans must be signed and dated by an authorized CMRS carrier or third-party agency official.
H. Once a CMRS carrier’s plan is approved, invoices may be submitted according to guidelines.
I. Quarterly, the FCC wireless telecommunications bureau requires a wireless carrier E911 deployment report. CMRS carriers must provide an electronic copy of the New Mexico portion of the excel spreadsheet (appendix portion) to the division within 5 days of FCC submission.
J. The division may periodically request additional information from CMRS carriers for wireless enhanced 9-1-1 planning, coordination, and implementation.
K. For division consideration and approval, each CMRS carrier must follow these procedures:
(1) CMRS carrier cost recovery is initially capped at a one-time $0.50 per subscriber NRC and a monthly $0.05 per subscriber MRC, based on actual deployments, plus one-time access costs of ~$450 per T-1 NRC and ~$900 per T-1 MRC for trunking to each access tandem.
(2) CMRS carriers must submit a valid IRS form W-9 to establish vendor status for payment processing. Form available at http://www.irs.gov/pub/irs-pdf/fw9.pdf.
(3) CMRS carrier invoices must not exceed trunking cost allowances, $0.50 NRC, and $0.05 MRC per subscriber. Partial invoice payments are not allowed.
(4) CMRS carrier invoices will be processed, approved, and disbursed monthly.
(5) Requests from new CMRS carriers will be reviewed case-by-case.
[10.6.2.17 NMAC – N, 05-15-2006]
HISTORY OF 10.6.2 NMAC:
Pre-NMAC History: Material in this part is derived from DFA-LGD Rule No. 93-3, Enhanced 911 Rules and Regulations, filed 5-20-94.
History of Repealed Material:
10 NMAC 6.2, Enhanced 911 Requirements, filed 2/2/98 – Repealed effective 5-28-2004.
10.6.2 NMAC, Enhanced 911 Requirements, filed 5-17-2004 – Repealed effective 05-15-2006.
