Conformity with Plan This Agreement is intended to conform in all respects with, and is subject to all applicable provisions of, the Plan. Inconsistencies between this Agreement and the Plan shall be resolved in accordance with the terms of the Plan. In the event of any ambiguity in this Agreement or any matters as to which this Agreement is silent, the Plan shall govern. A copy of the Plan is available upon request to the Administrator.
Conformity with XXXXX Filing The Prospectus delivered to the Agent for use in connection with the sale of the Placement Shares pursuant to this Agreement will be identical to the versions of the Prospectus created to be transmitted to the Commission for filing via XXXXX, except to the extent permitted by Regulation S-T.
Conformity with EXXXX Filing The Prospectus delivered to the Agent for use in connection with the sale of the Placement Shares pursuant to this Agreement will be identical to the versions of the Prospectus created to be transmitted to the Commission for filing via EXXXX, except to the extent permitted by Regulation S-T.
Amendments to Clarify and Correct Errors and Defects The parties may amend this Agreement to clarify an ambiguity, correct an error or correct or supplement any term of this Agreement that may be defective or inconsistent with the other terms of this Agreement, in each case, without the consent of the Noteholders, the Certificateholders or any other Person. The parties may amend any term or provision of this Agreement from time to time for the purpose of conforming the terms of this Agreement to the description thereof in the Prospectus, without the consent of Noteholders, the Certificateholders or any other Person.
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.
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.
Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.
General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:
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.
