ADUF Packing Specifications Sample Clauses

ADUF Packing Specifications. 9.6.5.1 The data will be packed using ATIS EMI records. 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.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
ADUF Packing Specifications. 13.6.5.1 The data will be packed using ATIS EMI records. A pcak will contani aminimum of one (1) message record or amaximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain amaximum of ninety-nine (99) packs and aminimum of one (1) pack.
Sample 1Sample 2Sample 3
ADUF Packing Specifications. 13.6.5.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack. Version: 3Q06 MBR 07/18/06 Market Agreement Attachment 1 13.6.5.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to CUSTOMER which BellSouth XXX is sending the message. BellSouth and CUSTOMER will use the invoice sequencing to control data exchange. CUSTOMER will notify BellSouth of sequence failures identified by CUSTOMER and BellSouth will resend the data as appropriate.
Sample 1Sample 2
ADUF Packing Specifications. 11.6.5.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety nine thousand nine hundred and ninety nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximumof ninety-nine (99) packs and a minimum of one (1) pack. 11.6.5.2 The OCN, From XXX, and InvoiceNumber will control the invoice sequencing. XxxXxxx XXX will be used to identify to CARRIER which AT&T SOUTHEAST REGION 9-STATE XXX is sending the message. AT&T SOUTHEAST REGION 9-STATE and CARRIER will use the invoice sequencing to control data exchange. CARRIER will notify AT&T SOUTHEAST REGION 9-STATE of sequence failures identified by CARRIER andAT&T SOUTHEAST REGION 9-STATE will resend the data as appropriate. 11.6.6 ADUF Pack Rejection. CARRIER will notify AT&T SOUTHEAST REGION 9-STATE within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of- balance condition on grand totals, invalid data populated). Standard ATISEMI error codes will be used. CARRIER will not be required to return the actual rejected data toAT&T SOUTHEAST REGION 9-STATE. Rejected packs will be corrected and retransmitted to CARRIER byAT&T SOUTHEAST REGION 9-STATE.
Sample 1
ADUF Packing Specifications. 13.6.5.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack. Version: 2Q07 MBR 05/22/07 Market Agreement Attachment 1 13.6.5.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to CUSTOMER which AT&T XXX is sending the message. AT&T and CUSTOMER will use the invoice sequencing to control data exchange. CUSTOMER will notify AT&T of sequence failures identified by CUSTOMER and AT&T will resend the data as appropriate.
Sample 1

Related to ADUF Packing Specifications

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) 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.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • 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.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Escrow Format Specification 3.1. 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.

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