Project Agreement 1.1 If applicable, the Department will recommend approval of the project by the Federal Highway Administration. 1.2 The Sponsor agrees to comply with Title VI of the Civil Rights Act of 1964, 78 Stat. § 252, 42 U.S.C. § 2000d et seq., and all requirements imposed by or pursuant to Title 49, Code of Federal Regulations, Part 21 - “Nondiscrimination in federally assisted programs of the Department of Transportation - effectuation of Title VI of the Civil Rights Act 1964". 1.3 The DEPARTMENT and SPONSOR mutually recognize that each party is a governmental entity subject to the provisions of the Governmental Tort Claims Act (51 O.S. § 151 et seq.). The DEPARTMENT and SPONSOR hereby mutually agree that each is and may be held severally liable for any and all claims, demands, and suits in law or equity, of any nature whatsoever, paying for damages or otherwise, arising from any negligent act or omission of any of their respective employees, agents or contractors which may occur during the prosecution or performance of this Agreement to the extent provided in the Governmental Tort Claims Act. Each party agrees to severally bear all costs of investigation and defense of claims arising under the Governmental Tort Claims Act and any judgments which may be rendered in such cause to the limits provided by law. Nothing in this section shall be interpreted or construed to waive any legal defense which may be available to a party or any exemption, limitation or exception which may be provided by the Governmental Tort Claims Act. 1.4 The Sponsor understands that should it fail to fulfill its responsibilities under this Agreement, such a failure will disqualify the Sponsor from future Federal-aid funding participation on any proposed project. Federal-aid funds are to be withheld until such a time as an engineering staff, satisfactory to the Department has been properly established and functioning, the deficiencies in regulations have been corrected or the improvements to be constructed under this Agreement are brought to a satisfactory condition of maintenance.
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.
Framework Agreement 4.1.2.1 The Parties shall enter into a Framework Agreement within 28 days after the Contractor receives the Letter of Acceptance, unless the Particular Conditions establish otherwise. The Framework Agreement shall be based upon FORM No. 3 – FRAMEWORK AGREEMENT annexed to the Particular Conditions. The costs of stamp duties and similar charges (if any) imposed by law in connection with entry into the Framework Agreement shall be borne by the Procuring Entity. 4.1.2.2 The Framework Agreement establishes the terms and conditions that will govern the contract awarded during the term of the Framework Agreement. The Framework Agreement establishes for the procurement works by package as and when required, over the specified period of time. The Framework Agreement does not commit a Procuring Entity to procure, nor a Firm to supply. The Framework Agreement allows the Procuring Entity to call the Contractor to commence the works on a particular package in a specified location within the duration of the agreement. 4.1.2.3 This Framework Agreement does not guarantee the contractor of being called for a contract to start and no commitment is made with regard to possible number of packages to carry out. 4.1.2.4 This Framework Agreement does exclude the Procuring Entity from the right to procure the same Works from other firms. 4.1.2.5 This Framework Agreement does not stop the Procuring Entity from removing the contractor from the same Agreement. 4.1.2.6 FAs shall be established for a maximum period of three (3) years. The Procuring Entity may with the Consent of the Contractor extend this Agreement if the agreement period is less than three (3) years, if the initial engagement has been satisfactory. 4.1.2.7 Call-off Contracts; for work on a package to start, the Procuring Entity shall issue a notice of acceptance of a particular package requesting the contractor to furnish a Performance Security and to start the works thereafter, and providing the contractor with details of location where the works, are to be carried out. The call-off statement shall specify the objectives, tasks, deliverables, timeframes and price or price mechanism. The price for individual call-off contracts shall be based on the prices detailed in the Framework Agreement.
Construction Contract If federal funds are included as part of the financing of the non-OPWC portion of the Project, federal law may prevail, including, but not limited to, application of Xxxxx Xxxxx prevailing wage rates, the Xxxxxxxx “Anti-Kickback” Act, the Contract Work Hours and Safety Standards Act, and any federal environmental regulations. Recipient is solely responsible for ensuring compliance with federal requirements applicable to its Local Subdivision Contribution. Notwithstanding the above, the following provisions apply to construction contracts under this Agreement:
Amendment to Agreement Effective as of the Amendment No. 2 Effective Date, the Agreement shall be amended as follows: The parties hereby agree to amend Exhibit A by adding the following new text as a new section 5: [START NEW TEXT]
Interconnection Agreement Seller shall comply with the terms and conditions of the Interconnection Agreement.
Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process 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 Short-Term Reliability 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 STAR or 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 Short-Term Reliability Process 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.
FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).
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. 5.2.2 The Concessionaire shall submit to the Authority the drafts of all Project Agreements, or any amendments or replacements thereto, for its review and comments, and the Authority shall have the right but not the obligation to undertake such review and provide its comments, if any, to the Concessionaire within 15 (fifteen) days of the receipt of such drafts. Within 7 (seven) days of execution of any Project Agreement or amendment thereto, the Concessionaire shall submit to the Authority a true copy thereof, duly attested by a Director of the Concessionaire, for its record. For the avoidance of doubt, it is agreed that the review and comments hereunder shall be limited to ensuring compliance with the terms of this Agreement. It is further agreed that no review and/or observation of the Authority and/or its failure to review and/or convey its observations on any Document shall relieve the Concessionaire of its obligations and liabilities under this Agreement in any manner nor shall the Authority be liable for the same in any manner whatsoever. 5.2.3 The Concessionaire shall not make any addition, replacement or amendments to any of the Financing Agreements without the prior written consent of the Authority if such addition, replacement or amendment has, or may have, the effect of imposing or increasing any financial liability or obligation on the Authority, and in the event that any replacement or amendment is made without such consent, the Concessionaire shall not enforce such replacement or amendment nor permit enforcement thereof against the Authority. For the avoidance of doubt, the Authority acknowledges and agrees that it shall not unreasonably withhold its consent for restructuring or rescheduling of the Debt Due.
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.
