Package Format. Interested Parties shall arrange their AMS Response package into the sections as set forth in section 5.2 and adhere to the following format requirements:
Package Format Sample Clauses
Related to Package Format
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.
Proposal Format a. Offerors shall submit an original of their proposals and the number of copies listed in paragraph “c” below.
CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.
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.
Invoice Format Invoices furnished by Contractor under this Agreement must be in a form acceptable to the Controller and City, and must include a unique invoice number. Payment shall be made by City as specified in 3.3.6 or in such alternate manner as the Parties have mutually agreed upon in writing.
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-‐format is as follows:
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.
Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record
Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.
