Basic 911 and E911 Database Requirements Sample Clauses

Basic 911 and E911 Database Requirements. 10.3.1 The telephone number (“TN”) data is managed in ALI/DBMS by BellSouth, but the responsibility for providing the data resides with each Local Service Provider. 10.3.2 Copies of the MSAG shall be provided within ten (10) business days from the time requested and provided on CD-ROM or such other medium as the Parties may agree. 10.3.3 Universal shall be solely responsible for providing Universal database records to BellSouth for inclusion in BellSouth’s ALI/DBMS database on a timely basis. 10.3.4 BellSouth and Universal shall arrange for the automated input and periodic updating of the E911 database information related to Universal End Users as stated in the BellSouth E911 Local Exchange Carrier Guide for Facility Based Providers. BellSouth shall work cooperatively with Universal to ensure the accuracy of the data transfer by verifying it against MSAG. 10.3.5 Universal shall assign an E911 database coordinator charged with the responsibility of forwarding Universal end user ALI/DBMS record information to BellSouth or via a third-party entity, charged with the responsibility of ALI/DBMS record transfer. Universal assumes all responsibility for the accuracy of the data that Universal provides to BellSouth. 10.3.6 Automatic Location Identification/Data Base Management System (ALI/DBMS). The ALI/DBMS Database contains subscriber information (including name, address, telephone information, and sometimes special information from the local service provider or subscriber) used to determine to which Public Safety Answering Point (PSAP) to route the call. The ALI/DBMS database is used to provide more routing flexibility for E911 calls than Basic 911. This subsection 1.3.6 supplements the requirements for SCPs/Databases set forth in the technical references in Attachment 3, Appendix 1 of this Agreement. BellSouth shall provide the Emergency Services Database in accordance with the following:

Basic 911 and E911 Database Requirements. (a) The ALI database shall be managed by Embarq, but is the property of Embarq and CLEC for those records provided by CLEC. (b) To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three Business Days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. (c) CLEC shall be solely responsible for providing CLEC database records to Embarq for inclusion in Embarq’s ALI database on a timely basis. (d) Embarq and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. Embarq shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. Embarq shall accept electronically transmitted files that conform to NENA Version #2 format. (e) CLEC shall assign an E911 database coordinator charged with the responsibility of forwarding CLEC end user ▇▇▇ record information to Embarq or via a third- party entity, charged with the responsibility of ALI record transfer. CLEC assumes all responsibility for the accuracy of the data that CLEC provides to Embarq. (f) CLEC shall provide information on new subscribers to Embarq within one (1) business day of the order completion. Embarq shall update the database within two (2) Business Days of receiving the data from CLEC. If Embarq detects an error in the CLEC provided data, the data shall be returned to CLEC within two

Basic 911 and E911 Database Requirements. 2.3.1 Where ACS-ANC is the primary 911-service provider or is otherwise responsible for maintaining the E911 database for any service area covered under this agreement, ACS-ANC will be responsible for maintaining the E911 database(s) for ▇▇▇▇▇ ▇. ▇▇▇▇▇ ▇ ▇▇▇▇▇ ▇▇ solely responsible for providing ▇▇▇▇▇ ▇ database records to ACS-ANC for inclusion in the E911 database. LEVEL 3 shall provide database records according to a format provided by ACS-ANC. ACS-ANC shall accept electronic updates from LEVEL 3 no less frequently than daily. The National Emergency Number Association (“NENA”) code for ▇▇▇▇▇ ▇ ▇▇ “▇▇▇▇▇ ▇” (▇▇▇▇▇ ▇ followed by two (2) spaces). ACS-ANC shall work cooperatively with LEVEL 3 to ensure the accuracy of the data transfer by verifying it against the Master Street Address Guide (MSAG). If ACS-ANC detects an error in LEVEL 3 provided data, the data shall be returned to LEVEL 3 within one (1) business day of the time the error was detected. LEVEL 3 shall respond to requests from ACS-ANC to make corrections to errors by providing corrected records within two (2) business days. ACS-ANC shall update the database with LEVEL 3 records within one (1) business day or with the same frequency that ACS-ANC updates the database with its own records, whichever is less. These time frames are guidelines and are established in the interest of public safety. ACS-ANC will make every effort to meet these response times; however, LEVEL 3 recognizes that seasonal impacts or other extraordinary circumstances may impact ACS-ANC’s ability to meet these requirements. Where ACS-ANC is responsible for maintaining the E911 routing database for any service area covered under this agreement, ACS-ANC will be responsible for maintaining the E911 routing database for LEVEL 3. 2.3.2 LEVEL 3 shall assign an E911 database coordinator charged with the responsibility of forwarding LEVEL 3 end user ANI/ALI record information to ACS-ANC or via a third-party entity, charged with the responsibility of ANI/ALI record transfer. LEVEL 3 assumes all responsibility for the accuracy of the data that LEVEL 3 provides to ACS-ANC. ACS-ANC and LEVEL 3 shall jointly research each ANI/ALI discrepancy report. Corrective action shall be taken immediately by the responsible party. 2.3.3 ▇▇▇▇▇ ▇ will provide the Emergency Service Bureaus with a single point of contact for inquiries about LEVEL 3’s customers. 2.3.4 Where there are multiple ANI/ALI databases involved, ACS-ANC will provide a single point o...

Basic 911 and E911 Database Requirements. (a) The ALI database shall be managed by Embarq, but is the property of Embarq and CLEC for those records provided by CLEC. (b) To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three Business Days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. (c) CLEC shall be solely responsible for providing CLEC database records to Embarq for inclusion in Embarq’s ALI database on a timely basis. (d) Embarq and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. Embarq shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. Embarq