Section 725.520 9-1-1 Traditional Legacy Service Database

a) 9-1-1 database queries will only be allowed by PSAPs for purposes of dispatching or responding to an emergency call or for database integrity verification as set forth in subsection (c).

b) Prior to an initial database integrity verification, the 9-1-1 authority shall obtain a court order detailing the information that is to be disclosed and the reason for disclosure.

c) The 9-1-1 database shall have the capability of allowing database verification queries, provided that the following procedures are adhered to:

1) The 9-1-1 authority shall be responsible for providing a level of security and confidentiality to the database that will prohibit random inquiries;

2) Direct access to 9-1-1 database information will be under strict control and, when technically feasible, a password will be assigned for access by authorized persons only;

3) Database verification queries shall be by subscriber number only and as necessary for purposes of database integrity. Queries in excess of 10 per 24-hour period will only be done with 2 or more days advance notice to the respective 9-1-1 system provider for scheduling purposes. Queries may be for the specific purpose of cross-checking information in the 9-1-1 database with other sources of information, including telephone and other directories, maps, municipal database listings, etc., and for verifying that database update information provided to the 9-1-1 system provider has indeed been posted and is correct. On-site 9-1-1 databases are exempt from 9-1-1 system provider advance notification requirements of this Section;

4) Information retrieved will be used exclusively for the maintenance, update and verification of the 9-1-1 database except as otherwise specified in subsection (a). Any other use is expressly prohibited. The information is subject to strict non-disclosure agreements between the various OSPs, 9-1-1 system providers and 9-1-1 authority. All personnel associated in any way with the 9-1-1 authority and the 9-1-1 systems are bound by these agreements.

5) Trunks/facilities that are not used to transport 9-1-1 emergency calls into the PSAP are prohibited from being connected to the 9-1-1 CPE in any way to allow for queries of the 9-1-1 database.

6) Database queries for the purpose of database verification shall be limited to off-peak times.

7) Database queries shall not be made if there is any known outage or impairment in the database system, including a database data link outage. In the event of an outage, the 9-1-1 system provider shall treat outage notification of the 9-1-1 authority regarding database query suspension as a priority. When practicable, this notification shall be made not later than 15 minutes after a confirmed incident that will cause database queries to be suspended.

d) Each telecommunication carrier shall provide updates to the appropriate 9-1-1 system provider for the 9-1-1 database on a daily basis or more frequently when technology supports it, Monday through Friday during business hours.

e) A 9-1-1 authority using an on-site database is restricted from making any changes to the 9-1-1 data that has been downloaded for its use. Only the 9-1-1 system provider has the authority to correct errors or provide updates to the database. The 9-1-1 authority must adhere to the proper error resolution procedures as specified in subsection (g)(l).

f) 9-1-1 authorities, 9-1-1 system providers and telecommunications carriers shall utilize mutually acceptable and agreed upon standards as prescribed, at a minimum, by the NENA Standards for 9-1-1 databases.

1) Data Formats for ALI, MSAG and GIS (02-010, v9);

2) 9-1-1 Data Management (02-011, v7); and

3) Provisioning and Maintenance of MSAG Files to VDBs and EKDBS (02-013, v3).

g) It shall be the joint responsibility of the 9-1-1 authority, the 9-1-1 system provider and telecommunications carriers to ensure that the error ratio of each 9-1-1 system's database shall not, at any time, exceed 1%.

h) The 9-1-1 authority or 9-1-1 system provider shall forward all error reports within two business days after finding the error to the 9-1-1 authority, 9-1-1 system provider, or carrier to take appropriate action to resolve the error.

i) If the error is a record of the 9-1-1 system provider, it must be corrected and updated within two business days after receipt of the error. If the error is for a participating telecommunications carrier, the 9-1-1 system provider shall forward the error to the appropriate telecommunications carrier or 9-1-1 authority for resolution.

j) Any telecommunications carrier receiving an error record from the 9-1-1 system provider has two business days upon receipt of the error to work with the 9-1-1 Authority and process the corrections and forward the appropriate updates to the 9-1-1 system provider. If the error is for an OSP, the 9-1-1 authority will forward those on to the appropriate company for review.

k) The 9-1-1 authority shall retest and/or validate that all errors have been corrected (e.g., no record found, misroutes).

l) The 9-1-1 authority shall, on a continuing basis, maintain the MSAG (or GIS database or functional equivalent), the ELT for each ESN and the associated telephone numbers for the ELTs.

m) Upon a written request of the 9-1-1 authority, the 9-1-1 system provider shall submit, within 14 working days, a report to assist in the validation of the accuracy of the 9-1-1 database. Before this report is delivered to the 9-1-1 authority, the 9-1-1 authority shall enter into nondisclosure agreements with telecommunication carriers and interconnected VoIP providers to protect proprietary network and customer-related information from public disclosure consistent with the Illinois Freedom of Information Act (FOIA) [5 ILCS 140/7(1)] and other applicable federal or state law.

1) This report shall include the following information when available in the 9-1-1 database:

A) telephone number − area code, prefix, and number in separate fields;

B) pilot number − single telephone number used to tie multiple numbers within a system together;

C) service (civic) address − including street name, house number or equivalent, suffix, directional, community name, state, zip code and location and/or descriptive information, including intersection if MSAG indicates an intersection, in separate fields;

D) billing address − if different than the service address, in separate fields, to be provided on a telephone number only basis pursuant to procedures defined by the telecommunications carrier and the 9-1-1 authority. Billing address information shall be subject to non-disclosure agreements;

E) name − first, last, and middle names or initials in separate fields;

F) date service was initiated − the month, day and year that service was initiated, in separate fields. If this information is not available, the date reflecting the most current service order activity may be provided instead;

G) type of service − residential, business, coin, etc.;

H) PBX/Centrex Extensions/Station Numbers − identify those numbers that are part of a PBX/Centrex system when this information is available;

I) surcharge status − when this information is available, the report shall identify those lines on which a surcharge is being collected and the date on which the collection was initiated. Identify those lines on which no surcharge is being collected and the reason for each exemption, including telecommunications carrier lines, in separate fields;

J) Emergency Service Number (ESN) − appropriate ESN, if assigned, is to be made available only from the primary telecommunications carrier providing database development and routing services.

2) This report may be requested by the 9-1-1 authority in writing, at a maximum, on a monthly basis. The information in this report is considered proprietary and shall be used exclusively for validating the accuracy of the 9-1-1 database. This report will be delivered in an electronic format. It will not be delivered in paper format. There will be a charge for this report that will be a tariffed item by each 9-1-1 system provider.

n) A 9-1-1 authority that has or is in the process of transitioning to an NG9-1-1 system when the 9-1-1 traditional legacy service database will be used in conjunction with, or eventually be replaced with, dynamic data must provide a detailed explanation of the initial development and ongoing maintenance of necessary databases in the NG9-1-1 final plan or modification, pursuant to Section 1325.205.

(Source: Amended at 40 Ill. Reg. 8170, effective May 25, 2016)