Notice by Project Agreement Parties. The performance of the Functions, Duties and Obligations (or any part thereof) may be suspended at any time by the Project Agreement Parties:
Notice by Project Agreement Parties Sample Clauses
Related to Notice by Project Agreement Parties
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.
Project Agreements Provided that where the company commences work on a project where a site agreement exists to which the company is contractually obligated or where a site agreement exists between the union and the client or their agent that provides for higher rates of pay and conditions, the conditions contained in any such site agreement will take precedence over this Agreement for the duration of the project.
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.
Obligations relating to Project Agreements 5.2.1 It is expressly agreed that the Concessionaire shall, at all times, be responsible and liable for all its obligations under this Agreement notwithstanding anything contained in the Project Agreements or any other agreement, and no default under any Project Agreement or agreement shall excuse the Concessionaire from its obligations or liability hereunder.
000 APPLICATION FOR PROJECT AGREEMENT 1.100 Any Company desiring to enter into a Project Agreement for Maintenance by Contract, must appear before the General Presidents' Committee (hereinafter the "Committee") for purposes of review and orientation and present to the Committee written evidence of the Owner's intent to engage that Company in the performance of maintenance service for a minimum period of one full year, subject to the usual termination clauses in such contracts.
PARTIES TO THIS AGREEMENT This Agreement binds:
Copies of this Agreement This Agreement shall be executed in four counterparts; each party holds one and the restare used for the transaction of related formalities. Each of the copies shall be deemed as the original one and has the same effect. [The remainder of this page is intentionally left blank.] Exclusive Purchase Option Agreement
AGREEMENT RENEWAL This Agreement shall not bind nor purport to bind the AZDOHS for any contractual commitment in excess of the original Agreement period.
Waiver and Amendment Any provision of this Note may be amended, waived or modified upon the written consent of the Company and the Holder.
Contracting Parties The Government customer (Licensee) is the “Ordering Activity”, “defined as an entity authorized to order under GSA contracts as set forth in GSA ORDER 4800.2G ADM, as may be revised from time to time. The Licensee cannot be an individual because any implication of individual licensing triggers the requirements for legal review by Federal Employee unions. Conversely, because of competition rules, the contractor must be defined as a single entity even if the contractor is part of a corporate group. The Government cannot contract with the group, or in the alternative with a set of contracting parties.
