Variation to Implementation Plan Sample Clauses

Variation to Implementation Plan. The Implementation Plan may be varied in accordance with the provisions of Clauses 4.3.1, 4.3.2 and 4.3.3 below:
AutoNDA by SimpleDocs
Variation to Implementation Plan. The Implementation Plan may be varied in accordance with the provisions of Clauses 4.3.1, 4.3.2 and 4.3.3 below: The Implementation Plan may be varied by the written agreement of the parties. If: the Contractor is prevented or delayed from carrying out its obligations under this Contract in accordance with the Implementation Plan as a direct consequence of a failure by the Purchaser (or a third party supplier to the Purchaser) to perform a Purchaser Responsibility on or before the relevant date set out in the Implementation Plan (other than to the extent caused by a preceding breach of this Contract by the Contractor) (in this Clause 4.3 each a "Purchaser Delay Event"); and the Contractor has promptly served a written notice on Purchaser setting out details of that Purchaser Delay Event and referring to this Clause 4.3, then: the Parties shall use all reasonable endeavours to mitigate the impact of such delay and to recover any resultant delay; and the Parties shall agree (such agreement not to be unreasonably withheld or delayed by either Party) a reasonable extension of any subsequent dates set out in the Implementation Plan that are directly impacted by the Purchaser Delay Event, such extension having regard to the delay caused by the Purchaser Delay Event, the related dependencies set out in the Implementation Plan, and the consequences of any delay upon Purchaser. If the Contractor is prevented or delayed from carrying out its obligations under the Contract in accordance with the Implementation Plan by reason of any event of Force Majeure then provided the Contractor has complied with the provisions of Clause 29 (Force Majeure) of the Conditions: the Parties shall use all reasonable endeavours to mitigate the impact of such delay and to recover any resultant delay; and the Parties shall agree (such agreement not to be unreasonably withheld or delayed by either Party) a reasonable extension of any subsequent dates set out in the Implementation Plan that are directly impacted by the event of Force Majeure, such extension having regard to the delay caused by the Force Majeure Event, the related dependencies set out in the Implementation Plan and the consequences of any delay upon Purchaser. In the event that the Parties cannot agree an amendment to the Implementation Plan pursuant to Clauses 4.3.2 or 4.3.3 then the provisions of Clause 39 (Dispute Resolution Procedure) of the Conditions shall apply. 5Implementation Environment Target environment Each par...

Related to Variation to Implementation Plan

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

  • Implementation Program 1. The Borrower shall:

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

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Access Rights for implementation Access Rights to Results and Background Needed for the performance of the own work of a Party under the Project shall be granted on a royalty-free basis, unless otherwise agreed for Background in Attachment 1.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Effect of GMP Change Order The Preconstruction Phase cannot extend beyond the execution of the GMP Change Order. By definition, all services provided after the execution of the GMP Change Order are Construction Phase Services and are included in the GMP.

  • Supplementation of Compensation Award ‌ If an employee is prevented from performing the employee's regular work with the City on account of an occupational accident that is recognized by the Workers' Compensation Board as compensable within the meaning of the Workers' Compensation Act, the City will supplement the award made by the Workers' Compensation Board for loss of wages to the employee by such an amount that the award of the Workers' Compensation Board for loss of wages (excluding non- economic loss payment), together with the supplementation by the City, will equal 100% of the employee's regular net wage (gross pay less statutory deductions, union dues and required benefit plan contributions). The said supplementation shall not be payable to any employee entitled to compensation after pension age if such an employee is entitled to an unreduced pension as provided under the Local Authorities Pension Plan or after the full age of 65 years if such an employee is not entitled to a pension. Subject to the foregoing limitation, the procedure to be followed in operating this policy shall be as follows:

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

Time is Money Join Law Insider Premium to draft better contracts faster.