ODUF Packing Specifications Sample Clauses

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.
AutoNDA by SimpleDocs
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.
ODUF Packing Specifications. 6.3.1 The data will be packed using ATIS EMI records. A pack will contain 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.
ODUF Packing Specifications. 12.7.3.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.
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. 6.3.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to Capital Communications Consultants, Inc. which BellSouth XXX is sending the message. BellSouth and Capital Communications Consultants, Inc. will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by Capital Communications Consultants, Inc. and resend the data as appropriate.
ODUF Packing Specifications. 10.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 maximumof ninety-nine (99) packs and a minimum of one (1) pack. 10.7.3.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. 10.7.4 ODUF 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.
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. 6.3.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to Home Phone which BellSouth XXX is sending the message. BellSouth and Home Phone will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by Home Phone and resend the data as appropriate.
AutoNDA by SimpleDocs
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. 6.3.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to QuantumShift which BellSouth XXX is sending the message. BellSouth and QuantumShift will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by QuantumShift and resend the data as appropriate.
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. 6.3.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to Syniverse which AT&T XXX is sending the message. AT&T and Syniverse will use the invoice sequencing to control data exchange. AT&T will be notified of sequence failures identified by Syniverse and resend the data as appropriate.

Related to ODUF Packing Specifications

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

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

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