Delivery Formats Sample Clauses

Delivery Formats. In each instance that documents are delivered to the Remarketing Agent pursuant to this Section 2(e), the Successor Agency shall provide (1) a clean final execution copy of each relevant Rule G-34 Document, and (2) in each case, if any, where the Successor Agency or any other transaction party determines that any redactions need to be made to a Rule G-34 Document (which redactions must be in accordance with MSRB Rule G-34(c) and related guidance from the MSRB), (x) a redacted final execution copy of such Rule G-34 Document, and (y) a marked copy or list showing all redactions that have been made to such Rule G-34 Document; and
Sample 1
AutoNDA by SimpleDocs
Delivery Formats. Delivery of files, image or full-text, assumes delivery with appropriate metadata (see above). Delivery is the responsibility of the contributing institution. FCLA agrees to provide [initials of potential-PALMM partner] with space on its FTP server for direct delivery of cataloging, image and text files, and metadata about those files. [Initials of primary participant PALMM member(s)] agrees to monitor [initials of potential-PALMM partner] submissions to ensure FCLA of image and marked-up text quality. Initial monitoring will begin at 100% and taper off as [initials of potential-PALMM partner] becomes familiar with systems. FCLA agrees to mount digital resources within its normal average time-frame, following receipt images and text files with appropriate metadata and mark-up.
Sample 1
Delivery Formats. In each instance that documents are delivered to the Remarketing Agent pursuant to this Section 20, the City shall provide (1) a clean final execution copy of each relevant Rule G-34 Document, and (2) in each case, if any, where the City or any other transaction party determines that any redactions need to be made to a Rule G- 34 Document (which redactions must be in accordance with MSRB Rule G-34(c) and related guidance from the MSRB), (x) a redacted final execution copy of such Rule G-34 Document, and (y) a marked copy or list showing all redactions that have been made to such Rule G-34 Document.
Sample 1

Related to Delivery Formats

  • Delivery Schedule The scheduled months of delivery of the Aircraft are listed in the attached Table 1. Exhibit B describes certain responsibilities for both Customer and Boeing in order to accomplish the delivery of the Aircraft.

  • DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • 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

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

  • DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

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

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

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