Structure of Collaborative Head Agreement Sample Clauses

Open Split View

Download

Share

Cite

Structure of Collaborative Head Agreement. 6.1 Structure and priority This Collaborative Head Agreement consists of, in order of priority:

Sample 1

Save

Copy

Related to Structure of Collaborative Head 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.

• Cooperative Drafting This Agreement has been drafted through a cooperative effort of City and Contractor, and both Parties have had an opportunity to have the Agreement reviewed and revised by legal counsel. No Party shall be considered the drafter of this Agreement, and no presumption or rule that an ambiguity shall be construed against the Party drafting the clause shall apply to the interpretation or enforcement of this 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.

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

• Agreement Structure 2.1 An “Agreement” hereunder shall consist of this Master Agreement, the Schedule, and their applicable attachments and represents the complete and exclusive agreement between the Parties regarding the subject matter of the Schedule, and replaces any prior oral or written communications between the Parties relating thereto. Each Lease is effective when the Schedule containing such Lease is executed by the Parties thereto.

• Construction and Scope of Agreement The language of all parts of this Agreement shall in all cases be construed as a whole, according to its fair meaning, and not strictly for or against any party. This Agreement is the only, sole, entire, and complete agreement of the parties relating in any way to the subject matter hereof. No statements, promises, or representations have been made by any party to any other, or relied upon, and no consideration has been offered or promised, other than as may be expressly provided herein. This Assumption of Risk, Release of Claims, Indemnification, and Hold Harmless and Agreement supersedes any earlier written or oral understandings or agreements between the parties. Participant acknowledges that he/she has read this Assumption of Risk, Release of Claims, Indemnification and Hold Harmless Agreement, understands its meaning and effect, and agrees to be bound by it. Date:

• Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

• PJM Agreement Modifications (a) If the PJM Agreements are amended or modified so that any schedule or section references herein to such agreements is changed, such schedule or section references herein shall be deemed to automatically (and without any further action by the Parties) refer to the new or successive schedule or section in the PJM Agreements which replaces that originally referred to in this Agreement.

• AGREEMENT ALTERATIONS AND AMENDMENTS This Agreement may be amended by mutual agreement of the parties. Such amendments shall not be binding unless they are in writing and signed by personnel authorized to bind each of the parties.

• Use of Project Development Security Buyer shall be entitled to draw upon the Project Development Security posted by Seller for Daily Delay Damages until such time as the Project Development Security is exhausted. Buyer shall also be entitled to draw upon the Project Development Security for any damages arising upon Buyer’s declaration of an Early Termination Date.