Where SBC-13STATE is the 911 System Service Provider, and Carrier deploys an NCAS solution:
4.3.2.1 Carrier’s designated third-party provider shall perform the above database functions.
4.3.2.2 Carrier’s designated third party shall be responsible for ensuring Carrier's Shell Records for ALI are submitted to SBC-13STATE, for inclusion in SBC-13STATE’s 911 DBMS, on a timely basis, once E911 trunking has been established and tested between Carrier’s MSC and all appropriate SRs.
4.3.2.3 Carrier’s third-party provider shall provide initial and ongoing updates of Carrier's Shell Records for ALI that are in electronic format based upon established NENA standards.
Where SBC-13STATE is the 911 service provider and Carrier deploys a CAS or Hybrid-CAS Solution utilizing SBC-13STATE E911 DBMS:
3.4.1.1 SBC-13STATE shall store the Carriers ALI records in the electronic data processing database for the E911 DBMS.
Where SBC-13STATE is the 911 service provider, Carrier will transport 911 calls from each Carrier MSC to the SR office of the E911 system.
Where SBC-13STATE is the 911 service provider, and Carrier deploys a CAS or Hybrid CAS Solution utilizing SBC-13STATE E911 DBMS:
4.3.1.1 Carrier or its representatives shall be responsible for providing Carrier's ALI Records to SBC-13STATE, for inclusion in SBC-13STATE’s DBMS on a timely basis, once E911 trunking has been established and tested between Carrier’s MSC and all appropriate SRs.
4.3.1.2 Carrier or its agent shall provide initial and ongoing updates of Carrier's ALI Records that are in electronic format based upon established NENA standards.
4.3.1.3 Carrier shall adopt use of a Company ID on all Carrier ALI Records in accordance with NENA standards. The Company ID is used to identify the tone provider.
4.3.1.4 Carrier is responsible for providing updates to SBC-13STATE ALI database; in addition, Carrier is responsible for correcting any errors that may occur during the entry of their data as reflected on the status and error report.
Where SBC-13STATE is the ALI Database Provider all ALI queries will be directed to the SBC database for ALI lookup.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE shall coordinate access to the SBC-13STATE E911 DBMS for the initial loading and updating of Carrier ALI Records.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE shall store the Carrier's ALI records in the electronic data processing database for the E911 DBMS.
Where SBC-13STATE is the 911 Database Provider, SBC-13STATE's ALI database shall accept electronically transmitted files that are based upon NENA standards.
Where SBC-13STATE is the 911 System Service Provider, and Carrier deploys a CAS or Hybrid CAS Solution utilizing SBC-13STATE 911 DBMS:
4.3.1.1 Carrier or its representatives shall be responsible for providing Carrier's ALI Records to SBC-13STATE, for inclusion in SBC-13STATE’s DBMS on a timely basis, once E911 trunking has been established and tested between Carrier’s MSC and all appropriate SRs.
4.3.1.2 Carrier or its agent shall provide initial and ongoing updates of Carrier's ALI Records that are in electronic format based upon established NENA standards.
4.3.1.3 Carrier shall adopt use of a Company ID on all Carrier ALI Records in accordance with NENA standards. The Company ID is used to identify the carrier of record in facility configurations.
4.3.1.4 Carrier is responsible for providing updates to SBC-13STATE 911 DBMS; in addition, Carrier is responsible for correcting any errors that may occur during the entry of their data as reflected on the status and error report.
Where SBC-13STATE manages the DBMS, SBC-13STATE shall establish a process for the management of NPA splits by populating the DBMS with the appropriate NPA codes.
