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.
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.
Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project:
A. TxDOT 2011 Texas Manual of Uniform Traffic Control Devices for Streets and Highways, including latest revisions
B. Texas Department of Transportation's Standard Specifications for Construction of Highways, Streets, and Bridges, 2014 (English units)
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
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.
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 Contracts Prior to the delivery of this Lease, the Company may have entered into a contract or contracts with respect to the acquisition and/or construction of the Improvements. Those contracts, and any such contracts entered into by the Company after delivery of this Lease are hereinafter referred to as the “Project Contracts.” Prior to the delivery hereof, certain work has been or may have been performed on the Improvements pursuant to said Project Contracts or otherwise. Subject to the Lender’s rights in the Project Contracts, the Company hereby conveys, transfers and assigns to the Issuer all of the Company’s rights in, but not its obligations under the Project Contracts and the Issuer hereby designates the Company as Issuer’s agent for the purpose of executing and performing the Project Contracts. After the execution hereof, the Company shall cause the Project Contracts to be fully performed by the contractor(s), subcontractor(s) and supplier(s) thereunder in accordance with the terms thereof, and the Company covenants to cause the Improvements to be acquired, constructed and/or completed in accordance with the Project Contracts. Any and all amounts received by the Issuer, the Trustee or the Company from any of the contractors or other suppliers by way of breach of contract, refunds or adjustments shall become a part of and be deposited in the Project Fund.
Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.
Construction Contracts Item A: Enter the total dollar amount of all contacts awarded on the project/ program. Item B: Enter the total dollar amount of contracts connected with this project/program that were awarded to Section 3 businesses.
Design Development Documents See Section 2, Part 1, Article 2.1.5.
