USAGE DATA REQUIREMENTS Sample Clauses

USAGE DATA REQUIREMENTS. 5.1 AT&T OKLAHOMA will pack and organize the Usage Data according to EMI guidelines. 5.2 AT&T OKLAHOMA will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties. 5.3 AT&T OKLAHOMA will transmit formatted Usage Data to CLEC via CONNECT: Direct or as otherwise agreed to by the Parties. 5.4 CLEC and AT&T OKLAHOMA will test and certify the CONNECT:Direct interface to ensure the accurate transmission of Usage Data. 5.5 AT&T OKLAHOMA will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the AT&T Daily Usage File User’s Guide. 5.6 AT&T OKLAHOMA will establish a single point of contact to respond to CLEC call usage, data error, and record transmission inquiries.
AutoNDA by SimpleDocs
USAGE DATA REQUIREMENTS. 5.1 AT&T ARKANSAS will pack and organize the Usage Data according to EMI guidelines. 5.2 AT&T ARKANSAS will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties. 5.3 AT&T ARKANSAS will transmit formatted Usage Data to CLEC via CONNECT: Direct or as otherwise agreed to by the Parties. 5.4 CLEC and AT&T ARKANSAS will test and certify the CONNECT:Direct interface to ensure the accurate transmission of Usage Data. 5.5 AT&T ARKANSAS will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the AT&T Daily Usage File User’s Guide. 5.6 The IS Call Center can be contacted to respond to CLEC record transmission inquiries. Other Usage inquiries should be coordinated through Account Management. If written notification is not received within thirty (30) calendar days, AT&T ARKANSAS shall have no further obligation to recover the data and shall have no further liability to the CLEC.
USAGE DATA REQUIREMENTS. 5.1 AT&T OKLAHOMA will pack and organize the Usage Data according to EMI guidelines. AT&T OKLAHOMA will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties.
USAGE DATA REQUIREMENTS. 5.1 AT&T will pack and organize the Usage Data according to EMI guidelines. 5.2 AT&T will provide Usage Data for Resale services to a CLEC location as agreed to by the Parties. 5.3 AT&T will transmit formatted Usage Data to CLEC via CONNECT: Direct or as otherwise agreed to by the Parties. 5.4 CLEC and AT&T will test and certify the CONNECT:Direct interface to ensure the accurate transmission of Usage Data. 5.5 AT&T will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the AT&T Daily Usage File User’s Guide. 5.6 AT&T will establish a single point of contact to respond to CLEC call usage, data error, and record transmission inquiries. 5.7 In Georgia, CLEC record transmission inquiries can be made to the CLEC’s account manager or by contacting the DUF contact as listed in the DUF (Daily Usage File) User Guide. If written notification is not received within thirty (30) calendar days, AT&T shall have no further obligation to recover the data and shall have no further liability to the CLEC.
USAGE DATA REQUIREMENTS. 5.1 AT&T will pack and organize the Usage Data according to EMI guidelines. AT&T will provide Usage Data for Resale services to a CLEC location as agreed to by the Parties.
USAGE DATA REQUIREMENTS. 5.1 AT&T will pack and organize the Usage Data according to EMI guidelines. AT&T will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties. 5.2 AT&T will provide Usage Data for Resale services to CLEC locations as agreed to by the Parties. 5.3 AT&T will transmit formatted Usage Data to CLEC via CONNECT: Direct (C:D) or as otherwise agreed to by the Parties. 5.4 CLEC and AT&T will test and certify the CONNECT: Direct interface to ensure the accurate transmission of Usage Data. 5.5 AT&T will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the AT&T Daily Usage File User’s Guide. 5.6 The IS Call Center can be contacted to respond to CLEC record transmission inquiries. Other Usage inquiries should be coordinated through Account Management. If written notification is not received within thirty (30) calendar days, AT&T shall have no further obligation to recover the data and shall have no further liability to the CLEC.
USAGE DATA REQUIREMENTS. 5.1 SBC KANSAS will pack and organize the Usage Data according to EMI guidelines. 5.2 SBC KANSAS will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties. 5.3 SBC KANSAS will transmit formatted Usage Data to CLEC via CONNECT: Direct or as otherwise agreed to by the Parties. 5.4 CLEC and SBC KANSAS will test and certify the CONNECT:Direct interface to ensure the accurate transmission of Usage Data. 5.5 SBC KANSAS will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the SBC Daily Usage File User’s Guide. 5.6 The IS Call Center can be contacted to respond to CLEC record transmission inquiries. Other Usage inquiries should be coordinated through Account Management. If written notification is not received within thirty (30) calendar days, SBC KANSAS shall have no further obligation to recover the data and shall have no further liability to the CLEC.
AutoNDA by SimpleDocs
USAGE DATA REQUIREMENTS. 5.1 SBC MISSOURI will pack and organize the Usage Data according to EMI guidelines. 5.2 SBC MISSOURI will provide Usage Data for Resale services to a CLEC locations as agreed to by the Parties. 5.3 SBC MISSOURI will transmit formatted Usage Data to CLEC via CONNECT: Direct or as otherwise agreed to by the Parties. 5.4 CLEC and SBC MISSOURI will test and certify the CONNECT:Direct interface to ensure the accurate transmission of Usage Data. 5.5 SBC MISSOURI will provide Usage Data to CLEC daily (normally Monday through Friday cycles). Holiday exceptions are listed in the SBC Daily Usage File User’s Guide. 5.6 The IS Call Center can be contacted to respond to CLEC record transmission inquiries. Other Usage inquiries should be coordinated through Account Management. If written notification is not received within thirty (30) calendar days, SBC MISSOURI shall have no further obligation to recover the data and shall have no further liability to the CLEC.
USAGE DATA REQUIREMENTS. Each Use Element defined below can be delineated by the following subdivisions: o By title o By subscribing institution username o By total consortium (defined group of institutional identifiers) o By individual user o By society (defined group of individuals) o By time period. The site minimally reports by month. For each month, each type of use is reported by hour of the day, US Eastern Standard Time o HealthGate will hold 24 months of historical data and then provide an archive to the Publisher in a mutually agreed standard format.

Related to USAGE DATA REQUIREMENTS

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!