Product Specific Service Delivery Provisions Sample Clauses

Product Specific Service Delivery Provisions. 4.1 For CLEC Non-CATS Messages and California 900/976 Messages billed to CLEC End Users that AT&T WEST REGION 2-STATE forwards to CLEC, AT&T WEST REGION 2-STATE shall calculate the amount due based on the following formula: Rated Value of Non-CATS Messages and California 900/976 Messages - Rejected/Unbillable Messages - Recharges - Billing Charges = Amount Due AT&T WEST REGION 2-STATE 4.2 As used in Section 4.1 above the following terms are defined as set forth below: 4.2.1 Rated Value of Non-CATS Messages and California 900/976 Messages means the total computed charges for Non-CATS Messages and California 900/976 Messages based on the Transporting LEC’s schedule of rates. 4.2.2 Rejected Messages means the rated value of Non-CATS Messages and California 900/976 Messages that failed to pass the industry standard edits and were returned to AT&T WEST REGION 2-STATE. 4.2.3 Unbillable Messages means the rated value of Non-CATS Messages and California 900/976 Messages that were not billable to a CLEC End User because of missing information in the billing record or other billing error, not the result of an error by CLEC or CLEC’s CMDS Host, that are returned in a timely fashion to AT&T WEST REGION 2-STATE.
Sample 1
AutoNDA by SimpleDocs
Product Specific Service Delivery Provisions 
Sample 1Sample 2Sample 3See All (7)

Related to Product Specific Service Delivery Provisions

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

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