Appendix E Transportation Specific Issues Sample Clauses
Appendix E Transportation Specific Issues
Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following: a) drawings, designs, or specifications, where Goods to be furnished under the Contract are to be specifically manufactured for the Procuring Entity; b) the method of shipment or packing; c) the place of delivery; and d) the Related Services to be provided by the Supplier. 33.2 If any such change causes an increase or decrease in the cost of, or the time required for, the Supplier's performance of any provisions under the Contract, an equitable adjustment shall be made in the Contract Price or in the Delivery/Completion Schedule, or both, and the Contract shall accordingly be amended. Any claims by the Supplier for adjustment under this Clause must be asserted within twenty-eight (28) days from the date of the Supplier's receipt of the Procuring Entity's change order. 33.3 Prices to be charged by the Supplier for any Related Services that might be needed but which were not included in the Contract shall be agreed upon in advance by the parties and shall not exceed the prevailing rates charged to other parties by the Supplier for similar services.
Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:
Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria
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-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.
CLOUD SPECIFIC TERMS AND CONDITIONS To the extent that Contractor has received an award for Lot 3, Cloud, the following terms and conditions apply to Lot 3, Cloud. For the duration of an Authorized User Agreement, the Cloud Solution shall conform to the Cloud Solution Manufacturer’s specifications, Documentation, performance standards (including applicable license duration, warranties, guarantees, Service Level Agreements, service commitments, and credits). Contractor is responsible for providing physical and logical security for all Data, infrastructure (e.g. hardware, networking components, physical devices), and software related to the services the Contractor is providing under the Authorized User Agreement. All Data security provisions agreed to by the Authorized User and Contractor within the Authorized User Agreement may not be diminished for the duration of the Authorized User Agreement without prior written agreement by the parties amending the Authorized User Agreement.