Change Management Procedure. A change identified at any stage of the assignment, which requires the Deliverables under development and/or Services under scope to deviate from the then current baseline, shall be conveyed by the Client to TCS in writing using Change Request Form in Annexure F. The request for change will then be assessed by TCS to evaluate its impact including on technical feasibility, technical requirements in consequence of the proposed change, impact on ongoing service delivery, time schedule and cost. TCS will present this assessment with any review and re-estimation thereof to the Client for its approval. The Client shall signify either its approval or disapproval to TCS within seven days of receipt of such re-estimation from TCS. If Client rejects the re-estimation, then the change request shall be deemed to be cancelled. If the Client does not signify either its approval or disapproval to TCS within seven days of receipt of such re-estimation from TCS, then, it shall be deemed to be cancelled. In the case of delay of approval by the Client, the baseline itself may undergo a change and this can result in further reassessment of the charges, and the Client shall pay for these reassessed charges whenever invoices are raised for the same. TCS shall not be liable to provide any new services to the Client, other than what is agreed in Annexure A Scope of Services, unless Parties have agreed and executed a Change Request or entered into a new Service Agreement and parties have agreed on the TCS’s charges for new service. TCS rates for any Change Requests, over and above the ongoing Service Delivery Charges, are covered as part of Annexure C Service Charges.
Change Management Procedure. The Change Management Procedure is specified in Paragraph 29 of this Agreement.
Change Management Procedure. Either Party may request a change to the Matrix II Development Plan, the Matrix II Specifications (including line extensions) or the Matrix II Release Criteria at any time by giving a written request to the other Party. Any change requested by MTF will describe the requested change and explain the anticipated impact of such change on MTF’s performance of its obligation to develop the Matrix II in accordance with this Agreement, including the Matrix II Development Milestones; and in response to any change requested by MTF, Orthofix will advise MTF, as promptly as practicable, of the anticipated impact of such change on Orthofix’s performance of its obligations hereunder. Any change requested by Orthofix will describe the requested change and explain the anticipated impact of such change on Orthofix’s performance of its obligations in accordance with this Agreement; and in response to any change requested by Orthofix, MTF will advise Orthofix, as promptly as practicable, of the anticipated impact of such change on MTF’s performance of its obligation to develop the Matrix II in accordance with this Agreement, including the Matrix II Development Milestones. No change to the Matrix II Specifications, the Matrix II Development Plan or the Matrix II Release Criteria will become effective unless and until approved by the Steering Committee.
Change Management Procedure. This service implements the change management policy, processes, and procedures as described in the Service Management Program Change Management Policy, Process, and Procedures document available at xxx.xxx.xxx/xxxxxxxxx. Please refer to that document for a detailed description of the policy, processes, and procedures.
Change Management Procedure. Any change in the scope of work or approach/ methodology other than as provided in a Task Order or new work shall be handled through a Change Management Procedure as provided in Appendix 2.
Change Management Procedure iXL TO REQUEST CHANGES If, at any time before the Acceptance Date, iXL requests to alter all or any part of the requirements definition, time-scales or a scope of work as stated in the Task Order, then iXL shall provide HPS with full written particulars of such changes ("Change Request").
Change Management Procedure. 1 If either Opodo or TRX (the “Proposer”) wish to propose a change to the nature or manner of provision or receipt of the Services (a “Proposed Change”), it shall notify the other party (the “Recipient”) of the Proposed Change and such Proposed Change shall be introduced pursuant to this Schedule 4.2.
Change Management Procedure. Either Client or Appiant can submit ---------------------------- a request to change the services under an SOW (a "SERVICE CHANGE REQUEST") or (a "SERVICE CHANGE ORDER") as described below:
Change Management Procedure. (a) The Foundation may, at any time during the Term, request changes to the Services and/or Deliverables by providing written notice to the Consultant of a requested change to those Services and/or Deliverables (Change Request).
(b) Each Change Request must contain the following details:
(i) a complete description of the proposed change;
(ii) any date by which the proposed change is requested to be made; and
(iii) the estimated effect of the Change Request on the Consultant.
(c) The Consultant must within seven days of receiving the Change Request provide the Foundation with a change proposal detailing:
(i) how the Consultant will implement the requested change while continuing to meet its other obligations under this Agreement (including the Schedules);
(ii) the impact of the requested change on the Charges; and
(iii) the Consultant's proposed changes to resourcing, (Change Proposal).
(d) The Consultant may reject any Change Request from the Foundation only if it can demonstrate to the Foundation's reasonable satisfaction that the proposed change:
(i) would adversely affect the relevant Service and/or Deliverable; or
(ii) is not feasible to implement.
(e) The Foundation must, after receiving a Change Proposal, as soon as reasonably practicable, notify the Consultant that it:
(i) accepts the Change Proposal;
(ii) rejects the Change Proposal; or
(iii) wishes to negotiate the Change Proposal, in which case the parties will endeavour to reach agreement on the Change Proposal.
Change Management Procedure. 12.1. Notification of all planned changes or Scheduled Maintenance events will be emailed to the Customer.
12.2. The MetroFibre NOC shall attempt to inform the Customer of any scheduled change or Scheduled Maintenance that will affect Service at least 7 (seven) calendar days before the planned implementation date.
12.3. If the Customer requires that the planned changes or maintenance be stalled, postponed or rescheduled because of business-affecting reasons, these reasons must be reported to the MetroFibre NOC within 24 (twenty-four) hours of receiving the initial notification from MetroFibre.
12.4. The MetroFibre Technical Service Desk will inform and consult with the Customer regarding any emergency change or maintenance to correct a fault that will affect Service, at least 1 (one) hour before the implementation, if possible.
12.5. If and to the extent an emergency change is required and, after all attempts to inform the appropriate the Customer representative per the Customer escalation matrix have failed, MetroFibre may make such a change, provided it is otherwise in compliance with the Master Services Agreement, and shall as soon as reasonably practicable after making such a change provide the Customer representative with full written details of such change and the reason or reasons therefore
12.6. All changes are managed by the Technical Service Desk.
