Change Management Procedures Sample Clauses

Change Management Procedures. 7.1 In addition to any other express right stated in any Order, a Party may, at any time during the Term, request changes to any part of an Order by giving to the other Party a Change Request. 7.2 Each Change Request must be individually sequentially numbered and provide the following details: (a) a complete description of the proposed change; (b) the reason(s) for issuing the Change Request; (c) any required date by which the proposed change must be made; (d) the impact of the Change Request on the other Party, including in the case of a Change Request issued by Supplier, a breakdown of estimated costs to implement the Change Request; and (e) provision for signature by the Authorised Signatory of each Party for acceptance of the Change Request. 7.3 If Client submits a Change Request to Supplier, Supplier will within 14 days of receiving the Change Request (or such other period as the Parties agree), provide Client with a change proposal detailing how Supplier will implement the requested change, the impact of the requested change on any fees payable by Client, proposed changes to resourcing, delivery or milestone dates and Supplier’s ability to meet its other obligations under the Order (Change Proposal). 7.4 Supplier may accept or reject any Change Request from Client at its sole discretion. 7.5 Client must, after receiving a Change Request or a Change Proposal from Supplier, within 7 days, notify Supplier that it: (a) accepts the Change Request or Change Proposal; (b) wishes to negotiate the Change Request or the Change Proposal in which case the Parties will negotiate the Change Request or the Change Proposal and if agreement cannot be reached within 21 days of commencing negotiations, then Client may: i) accept the Change Request or Change Proposal; ii) reject the Change Request or Change Proposal; iii) accept the Change Request or Change Proposal at a reasonable market based price determined by an independent expert in accordance with the processes in clause 20.3; or (c) withdraws the Change Request made by Client to which the Change Proposal relates; or (d) rejects the Change Request or Change Proposal (as the case may be), after acting reasonably, in which case the Order to which it relates will continue unchanged. 7.6 Any accepted Change Request or Change Proposal that varies the clauses of an Order must be executed by an Authorised Signatory of each Party after which it will vary and form part of the Order to which it relates.

Change Management Procedures. 8.1 It may become necessary to amend this Statement of Work for reasons including, but not limited to, the following: 8.1.1 Customer's changes to the scope of work and/or specifications for the Deliverables, 8.1.2 Customer's changes to the Implementation Plan, 8.1.3 Non-availability of resources which are beyond either party's control; and/or, 8.1.4 Environmental or architectural impediments not previously identified. 8.2 In the event either party desires to change this Statement of Work, the following procedures will apply: 8.2.1 The party requesting the change will deliver a change request document ("Change Request") to the other party. The Change Request will describe the nature of the change, the reason for the change, and the effect the change will have on the scope of work, which may include changes to the Deliverables, and the schedule. 8.2.2 A Change Request may be initiated either by the customer or by Cisco for any material changes to the SOW. The designated Program/Project Manager of the requesting party will review the proposed change with his/her counterpart. The parties will evaluate the Change Request and negotiate in good faith the changes to the Services and the additional charges, if any, required to implement the Change Request. If both parties agree to implement the Change Request, the appropriate authorized representatives of the parties will sign the Change Request, indicating the acceptance of the changes by the parties. 8.2.3 Upon execution of the Change Request, said Change Request will be incorporated into, and made a part of, this SOW. **** Represents material which has been redacted and filed separately with the Commission pursuant to a request for confidential treatment pursuant to Rule 406 under the Securities Act of 1933, as amended. Cisco Systems, Inc. Master Agreement Number:__________ CONFIDENTIAL Statement of Work Number:__________ Project Number:__________ 8.3 Whenever there is a conflict between the terms and conditions set forth in a fully executed Change Request and those set forth in the original SOW, or previous fully executed Change Request, the terms and conditions of the most recent fully executed Change Request shall prevail.

Change Management Procedures. 8.1 In the event it is necessary to change this SOW other than as provided in Section 12 of the Agreement, the following procedure will be used: 8.1.1 A change request document ("Change Request") will be executed by the parties describing the nature of the change, the reason for the change, and the effect the change will have on the scope of work, which may include changes to the Subcontractor Work Product. Parties will determine the additional charges, if any. 8.1.2 A Change Request may be initiated by either party for any material changes to an applicable SOW. The requesting party will review the proposed change with the other party, and the appropriate authorized representatives of the parties will sign a mutually acceptable Change Request, indicating the acceptance of the changes by the parties. 8.1.3 Upon execution of the Change Request, said Change Request will be incorporated into and made a part of the applicable SOW. 8.2 Whenever there is a conflict between the terms and conditions set forth in a Change Request and those set forth in the SOW or previous Change Request, the terms and conditions of the most recent Change Request shall prevail.

Change Management Procedures. If changes to the work detailed in this SOW become necessary, they must be requested in writing and an amendment must be prepared to reflect these changes.

Change Management Procedures. 4.12.1 All changes to the Service Provider's infrastructure go through a three phase change procedure. In almost all cases changes will not affect the availability; however, the Customer will be notified of any alterations that will change the functionality of the Service. In some cases, changes may require some programming alterations to the ASP web applications or SQL Server functionality used by the Service, which must be completed by the Customer. The timeframe for Customer change will be negotiated with the Customer on a case by case basis. The three phases are as follows: Phase 1 Internal testing and staging of the change using hardware and network infrastructure independent to the production environment, but closely simulating the production network. Phase 2 Partial rollout into the production network by removing a single member of redundant infrastructure and updating just those devices. This may not always be possible in the case of some devices such as core network routers. Phase 3 Full rollout onto all remaining devices. 4.12.2 Changes are made during scheduled system maintenance. Some more urgent changes may be escalated and performed through unscheduled system maintenance as described in this Agreement. 4.12.3 Change management procedures will also be applied to any lower level components developed for the Service by the Customer, such as COM/COM+ objects and packages and third party add-ons that might be required. 4.12.4 Complex web applications may include more sophisticated roll out procedures, tailored around the requirements for that particular application.

Change Management Procedures. Overview There will be a process to coordinate and control any changes to the responsibilities outlined in the project in order to ensure timely response to all proposed changes with input by the appropriate governing bodies. Project Change Requests must be submitted in writing to the Operating Committee representative from SFI and EOAF with a Project Change Request form (see Appendix C) and relevant supporting documentation. The Operating Committee will review, classify and respond to Project Change Requests in a timely fashion, including convening interim meetings if required. The Operating Committee may approve of changes to project policy and implementation specified in this PFS Contract and Schedules that do not materially affect the rights or obligations of the Parties, including non-material changes to extensions of Cure period, Schedule C (Evaluation Plan), Schedule F (Governance and Reporting) as related to reporting provisions, and Schedule G (Publicity), provided that any member of the Operating Committee may request that a change be sent to the Oversight Committee for approval. Provided that the Oversight Committee must approve of any changes likely to materially affect the timing or amount of any Success Payments such as modifications to the definition of enrollment; material changes to data or measurement; or significant modifications as to the timing of the project. For the avoidance of doubt, (i) JVS may optimize program delivery including numbers of classes/hours of instruction/class schedule/amounts of supports etc to achieve Final Outcomes without requiring approval of either Committee provided that (a) the core principles and target population remains consistent with original design and (b) any increase in enrollment beyond targets specified for each Program Track in Schedule A to the PFS Contract will be subject to Oversight Committee approval; (ii) JVS and Independent Evaluator may propose modifications to Appendix D: Random Assignment Operations Plan, Schedule C without requiring approval of either Committee provided that such modifications are not materially likely to affect the measurement of outcomes. All changes requiring an amendment must be addressed by the Oversight Committee and cannot be made without prior written consent of the Parties to the PFS Contract. Any material modification to the obligations of a party to the PFS Contract under the PFS Contract shall require the consent of that party. For the avoidance of doubt, an...

Change Management Procedures. Change Request Procedure STEP 1 Each Change Request is forwarded to Riskonnect Professional Services by the Client’s project manager. STEP 2 Riskonnect assesses the impact of each Change Request on the project as defined in the existing Statement of Work and may make suggestions and/or modifications to the Change Request. STEP 3 Client’s project manager may approve, reject, or further modify Riskonnect’s suggestions and/or modifications. STEP 4 Upon approval and mutually agreed upon terms, Riskonnect will incorporate Change Request into the project schedule and perform the required work ● Riskonnect will manage all Change Requests within the integrated Riskonnect Project Management system. ● Potential impact on the existing deliverable schedules (timelines), and potential changes (both intentional and unintentional) to other components, modules, features, reports and other system functionality will be assessed. Multiple impact assessments will be made as required until final approval is completed.

Change Management Procedures. Included in the Service Delivery Reference Manual are change management procedures (the “Change Management Procedures”) that the Parties will use to, among other things, document mutually agreed changes to the Services to be provided by ACS under the Agreement and/or Symetra’s computing and/or operating environment. The Parties’ use of the Change Management Procedures as a means of documenting their agreement on such changes as contemplated in the various Sections of the Agreement is not intended to be, and shall not be, interpreted to mean that additional charges will be owed by Symetra to ACS in connection with all such changes.

Change Management Procedures. It may become necessary to amend this SOW for reasons including, but not limited to, the following: 6.1 Customer changes to the scope of work and/or specifications for the Services or Deliverables; 6.2 Customer changes to the IP addressing scheme. 6.3 Non-availability of resources which are beyond either party's control; or 6.4 Environmental or architectural impediments not previously identified. In the event it is necessary to change the Services and/or Deliverables contemplated by this SOW the following procedure will be followed: Either Cisco or Customer will prepare a document describing the nature of the change, the reason for the change, and the effect of the change on the scope of work, which may include changes to the project schedule, Services and/or Deliverables. The parties will negotiate any price increase or decrease as a result of the change.

Change Management Procedures. It may become necessary to amend this SOW for reasons including, but not limited to, the following: 7.1 Customer changes to the scope of work and/or specifications for the Services or Deliverables; 7.2 Customer changes to the IP 7.3 Non-availability of resources which are beyond either party's control; or 7.4 Environmental or architectural impediments not previously identified. In the event it is necessary to change the Services and/or Deliverables contemplated by this SOW, the following procedure will be followed: Either Cisco, Subcontractor or Customer will prepare a document describing the nature of the change, the reason for the change, and the effect of the change on the scope of work, which may include changes to the project schedule, Services and/or Deliverables. The parties will negotiate any price increase or decrease as a result of the change. A requested Service commencement date is to be included in Customer's Purchase Order subject to confirmation by Subcontractor and Cisco.