Where AT&T-13STATE Sample Clauses
The 'Where AT&T-13STATE' clause defines the specific geographic or operational scope within which certain terms, obligations, or provisions of an agreement apply, specifically referencing the AT&T-13STATE region. In practice, this clause clarifies that particular rights, responsibilities, or procedures are only relevant when services, products, or activities occur within the states covered by AT&T's 13-state operating territory. By delineating this scope, the clause ensures that both parties understand the territorial limits of their contractual obligations, thereby preventing misunderstandings about where certain terms are enforceable or applicable.
Where AT&T-13STATE manages the 911 and E911 Databases and Carrier deploys a CAS or Hybrid-CAS Solution utilizing AT&T-13STATE E911 DBMS:
Where AT&T-13STATE is the 911 System Service Provider, and Carrier deploys a CAS or Hybrid CAS Solution utilizing AT&T-13STATE 911 DBMS:
4.3.1.1 Carrier or its representatives shall be responsible for providing Carrier's ALI Records to AT&T-13STATE, for inclusion in AT&T-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 AT&T-13STATE 911 DBMS; in addition, ▇▇▇▇▇▇▇ is responsible for correcting any errors that may occur during the entry of their data as reflected on the status and error report.
Where AT&T-13STATE manages the E911 Database, AT&T-13STATE shall coordinate access to the AT&T-13STATE DBMS for the initial loading and updating of CLEC End User 911 Records.
Where AT&T-13STATE manages the DBMS, AT&T-13STATE shall establish a process for the management of NPA splits by populating the DBMS with the appropriate NPA codes.
Where AT&T-13STATE manages the E911 Database, AT&T-13STATE shall provide CLEC access to the E911 Database to store CLEC's End User 911 Records [that is, the name, address, and associated telephone number(s) for each of CLEC’s End Users. CLEC or its representative(s) is responsible for electronically providing End User 911 Records and updating this information.
Where AT&T-13STATE manages the E911 Database, AT&T-13STATE's E911 Database shall accept electronically transmitted files that are based upon NENA standards. Manual (i.e. facsimile) entry shall be utilized only in the event that the DBMS is not functioning properly.
Where AT&T-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 AL▇ ▇re submitted to AT&T-13STATE, for inclusion in AT&T-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 AT&T-13STATE has provided the CLEC a physical collocation arrangement within the eligible structure, the CLEC’s radio equipment will be located in the CLEC’s dedicated physical collocation arrangement. AT&T-13STATE will allow both physical collocation of the CLEC’s equipment associated with its Microwave Entrance Facility on an ICB basis until such time as costs and permanent rates based upon those costs may be determined by AT&T-13STATE.