Development Impact Project Agreement Sample Clauses

Development Impact Project Agreement for Parcel B Project at Fan Pier by and between Eleven Fan Pier Boulevard LLC and the Boston Redevelopment Authority (the “BRA”)*;
AutoNDA by SimpleDocs
Development Impact Project Agreement. On November 15, 2016 the Applicant and the BPDA entered into a Development Impact Project Agreement with respect to the Project (“DIP Agreement”) pursuant to which the Applicant committed to (i) making Housing Exaction payments based upon a rate of $8.34 per square foot of gross floor area devoted to DIP Uses (“DIP Gross Floor Area”) for the Project in excess of the 100,000 square foot exemption set forth in Section 80B-7.4(a)(i) of the Code, calculated at approximately 288,700 square feet based on current plans for the Project (i.e., 388,700 s.f. less 100,000 s.f. = 288,700 s.f. subject to Housing Exactions), subject to recalculation and adjustment as provided for in the DIP Agreement, and (ii) making Jobs Exaction payments to the Neighborhood Jobs Trust based on a rate of $1.67 per DIP Gross Floor Area for the Project in excess of the 100,000 square foot exemption set forth in Section 80B-7.4(a)(i) of the Code calculated at approximately 288,700 square feet based on current plans for the Project (i.e., 388,700 s.f. less 100,000 s.f. = 288,700 s.f. subject to Jobs Exactions), subject to recalculation and adjustment as provided for in the DIP Agreement.

Related to Development Impact Project Agreement

  • 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 Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

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

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • 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 Implementation The Borrower shall:

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

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!