Delivery Schedule The Goods specified in the List of Goods are required to be delivered within the acceptable time range (after the earliest and before the final date, both dates inclusive) specified in Section V, Schedule of Requirements. No credit will be given to deliveries before the earliest date, and Tenders offering delivery after the final date shall be treated as non-responsive. Within this acceptable period, an adjustment of [insert the adjustment factor], will be added, for evaluation purposes only, to the Tender price of Tenders offering deliveries later than the “Earliest Delivery Date” specified in Section V, Schedule of Requirements.
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.
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.
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.
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.
Delivery of Software 1. SAP will deliver the Software as described in the Documentation and the Price List and will also provide the appropriate license key for the relevant End User. With regard to the features, quality and functionality of the Software the product description in the Documentation and the Price List is solely decisive. SAP does not own any additional features, quality or functionality. Distributor can, in particular, not assert any additional feature, quality or functionality from any public statements, publications or advertisements by SAP except to the extend SAP has expressly confirmed such additional feature, quality or functionality in writing. Any representation, warranty, undertaking or guarantee regarding additional features, quality or functionality is effective only if expressly confirmed by SAP’s management in writing.
2. After acceptance of an order, SAP will deliver to Distributor one copy of the relevant Software:
a) on discs or other data media (“Physical Shipment”); or
b) by making it available for downloading through the internet (usually on the SAP ServiceMarket Place (xxxx://xxxxxxx.xxx.xxx/swdc)) (“Electronic Delivery”).
3. The relevant Software and Documentation will be deemed delivered (including but not limited for the purpose of fixed delivery dates or timely delivery) and the risk passes to Distributor:
a) in case of Physical Shipment, when the relevant disc or other data media thereof is handed over to the freight carrier (FCA - Free Carrier (named place of delivery), Incoterms 2010); or
b) in case of Electronic Delivery, when SAP has made an electronic copy thereof available for downloading and has informed Distributor accordingly, (“Delivery”).
4. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant Open Ecosystem Partner instead (“Open Ecosystem Partner Delivery”). In case of Open Ecosystem Partner Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the Open Ecosystem Partner.
5. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant End User instead (“End User Delivery”). In case of End User Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the End User.
6. SAP might be entitled to suspend the delivery of the Software, Maintenance Services, applicable license key or both to Distributor, Open Ecosystem Partner or End User or both as further set out in this Sell On Premise Distribution Model as well as the Distribution GTCS.
7. If Distributor receives a new copy of the Software, Documentation and/or other SAP Materials that replaces previously provided Software, Documentation and/or other SAP Materials, Distributor must distribute that newest copy provided and either destroy or upon SAP’s request return previous copies.
8. Distributor must not make the Software, Documentation and/or other SAP Materials available to the Open Ecosystem Partner or End User by any means other than by delivering the Software, Documentation and/or other SAP Materials as originally provided by SAP. Distributor’s right to pass on the Software, Documentation and/or other SAP Materials is subject to the provisions of this Agreement.
Instructional Materials A. The Board recognizes that appropriate texts, library reference facilities, maps and globes, laboratory equipment, audio-visual equipment, art supplies, athletic equipment, current periodicals, standard tests and questionnaires, computers, and similar materials are the tools of the teaching profession.
B. Efforts shall be continued to seek and use instructional materials which reflect the contribution and presence of diverse ethnic and cultural groups.
C. 1. Selection of instructional materials for each school shall be made by a committee of teachers chosen by the faculty within that school.
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.
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: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
DELIVERY, STORAGE, AND HANDLING The Contractor shall be responsible to inspect all components on delivery to ensure that no damage occurred during shipping or handling for furnish and installation projects. For equipment only purchases, the ordering entity shall be responsible to inspect all components on delivery. Materials must be stored in original undamaged packaging in such a manner to ensure proper ventilation and drainage, and to protect against damage, weather, vandalism, and theft until ready for installation.
