Changes to Project Plan Sample Clauses

Changes to Project Plan. Any changes to the Project Plan will require the prior written approval of both Parties, and if such changes require additional activities, the Project Plan will include a budget for such activities and a method of funding.
Sample 1Sample 2See All (4)
Changes to Project Plan. The Parties mutually intend and agree that (i) the Project Plan defines for various purposes the boundaries of the Project in respect of which the Province has agreed to provide the Funding to each of the Recipients, and (ii) the Recipients should have an adaptive capacity to make modifications to the Project Plan that do not materially affect the Province’s interests under this Agreement. The Parties therefore agree as follows: (a) the Recipients shall notify the Province of all proposed changes to the Project Plan; (b) the Province shall agree to amend the Project Plan in accordance with changes proposed by the Recipients if: (i) the proposed changes are not material to the interests of the Province under this Agreement; or (ii) the proposed changes, although potentially material to the interests of the Province under this Agreement, are such that, in the circumstances and having regard to the intentions of the Parties as expressed in this Agreement and the expressed objectives of the Province’s Carbon Capture and Storage Program as set out in the FPP, it would be unreasonable for the Province not to agree to such changes.
Sample 1Sample 2See All (4)
Changes to Project Plan. If FEC notifies Merchant that all or any part of a System will not be delivered on the schedule set forth in the Project Plan, Merchant may terminate or revise or limit the Project to avoid delay. Merchant shall specify such revisions or limitations to the Project Plan in a Software Development Project Plan Revision. If Merchant determines to continue the Project pertaining to such System, FEC shall prepare to Merchant a revised Project Plan encompassing the revisions or limitations selected by Merchant to avoid or mitigate the delay.
Sample 1
Changes to Project Plan. The Parties mutually intend and agree that (i) the Project Plan defines for various purposes the boundaries of the Project in respect of which the Province has agreed to provide the Funding to each of the Recipients, and (ii) the Recipients should have an adaptive capacity to make modifications to the Project Plan that do not materially affect W K H 3 U R Y L Q F H ¶ V L Q W H U H V W V (a) the Recipients shall notify the Province of all proposed changes to the Project Plan; (b) the Province shall agree to amend the Project Plan in accordance with changes proposed by the Recipients if: (i) the proposed changes are not material to the interests of the Province under this Agreement; or (ii) the proposed changes, although potentially material to the interests of the Province under this Agreement, are such that, in the circumstances and having regard to the intentions of the Parties as expressed in this $ J U H H P H Q W D Q G W K H H [ S and Storage Program as set out in the FPP, it would be unreasonable for the Province not to agree to such changes.
Sample 1
Changes to Project Plan. 5.1 Nokia may request and the Licensor may recommend at any time prior to Acceptance of the last Deliverable to be provided under this Agreement changes to the Specifications, Project Plan, delivery schedule or delivery arrangements (hereinafter referred to as "Change"). The Developer undertakes to make such Changes that may be requested by Nokia. All Changes shall be defined and agreed in writing with reference to the exact terms of the Project Plan or Specifications that are affected. 5.2 The Parties will respond in writing or meet to discuss any Change upon Nokia's request. The Licensor will advise Nokia of the likely impact of any Change, including any effect on price and/or delivery schedule, promptly upon request, and submit a written offer accordingly. 5.3 Until such time as any Change is formally agreed, the Licensor will, unless otherwise agreed or requested by Nokia in writing, continue the Development as if such Change had not been requested or recommended. 5.4 Notwithstanding anything said in this Clause 5, if a Change becomes necessary in order to comply with terms and conditions of this Agreement, the cost of such Change shall be borne by the party to whose action or omission such Change is attributable.
Sample 1

Related to Changes to Project Plan

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

  • Project Implementation The Borrower shall:

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

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

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

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

  • Project Changes Project changes prior to bid opening shall be made by addendum to plans and specifications. Changes after bid opening shall be made by change order. The Local Government shall submit all addenda and all change orders to the Department for an eligibility determination. After execution of all construction, equipment and materials contracts, the Project contingency may be reduced.