Prioritisation of Collaborative Head Agreement and Project Agreement Sample Clauses

Prioritisation of Collaborative Head Agreement and Project Agreement. In the event and to the extent of any inconsistency between this Collaborative Head Agreement and any Project Agreement, the Project Agreement will take priority to the extent of the inconsistency.
AutoNDA by SimpleDocs

Related to Prioritisation of Collaborative Head Agreement and Project Agreement

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Coordination of Design and Construction Contract Documents 5.5.1 Review model(s), Drawings, Specifications and other Construction Documents as they are developed by A/E during the Schematic Design, Design Development, and Construction Documents design phases of the Project.

  • Construction of Agreement The parties mutually acknowledge that they and their attorneys have participated in the preparation and negotiation of this Agreement. In cases of uncertainty this Agreement shall be construed without regard to which of the parties caused the uncertainty to exist.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • Project Agreement (a) Subsequent to the establishment of a Cooperative Agreement pursuant to § 81.3, the Secretary may further agree with the States to provide xxxxx- cial assistance in the development and implementation of acceptable projects for the conservation of endangered and threatened species. Financial agree- ments will consist of an Application for Federal Assistance and a Project Agreement. Such agreements’ contin- ued existence, and continued financial assistance under such agreements, shall be contingent upon the continued existence of the Cooperative Agree- ment described in § 81.3 of this part.

  • Construction Phase - Administration of the Construction Contract 1.6.1 The Construction Phase shall commence with the acceptance of the Construction Manager’s Guaranteed Maximum Price (or acceptance of a partial Guaranteed Maximum Price for a stage or phase) and issuance of a Notice to Proceed with Construction Services and terminate sixty (60) days after Final Payment to the Contractor is made, or when all of Architect/Engineer’s services have been satisfactorily performed, whichever occurs later.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • COMPLETION OF AGREEMENT The District and the Union agree that this contract is complete. There shall be no additions to or deletions from the content of any Articles and there shall be no Articles added except by mutual agreement by the Board and the Union. In addition, there shall be no further negotiations on any matter that is within or comes within the scope of representation for the duration of the contract except by mutual agreement.

  • PARTIES TO AGREEMENT This agreement is between the University of Central Florida (UCF) on behalf of its Board of Trustees, for the benefit of the University of Central Florida Department of Housing and Residence Life (UCF DHRL), and any person seeking residence accommodations in any of the various UCF DHRL residences (the Student). If the Student is a minor, or suffers any incapacity affecting the Student’s legal ability to enter into a contract, the term the Student shall also include the Student’s parent or legal guardian. The Student may not designate another person to act as agent or representative of the Student with regard to this agreement (i.e., having a friend pick up or turn in keys). The Student remains personally responsible for all rights and obligations arising from or related to this agreement.

  • Commencement and Completion of Construction The Company shall begin Construction Activities no later than January 1, 2014 (“Commencement Date”) and secure a final Certificate of Compliance by June 30, 2015 (hereinafter, “Completion Date”).

Time is Money Join Law Insider Premium to draft better contracts faster.