Change Management Process and Procedures Sample Clauses
The Change Management Process and Procedures clause defines the formal steps and requirements for requesting, evaluating, approving, and implementing changes to the scope, deliverables, or terms of an agreement. Typically, this clause outlines how either party can propose a change, the documentation required, and the approval process that must be followed before any modifications take effect. By establishing a clear and structured approach to managing changes, this clause helps prevent misunderstandings, scope creep, and disputes, ensuring that all parties are aligned and that changes are properly controlled throughout the project or contractual relationship.
Change Management Process and Procedures. Supplier’s responsibilities with respect to Change Management processes and procedures include:
(a) Participating in Change meetings. Supplier’s representative in these meetings shall have the requisite authority to make binding and enforceable commitments on behalf of Supplier.
(b) Submitting all proposed Changes in advance to Gap for Approval. Unless otherwise mutually agreed, all proposed Changes shall be submitted to Gap, at a Exhibit A.8 Gap / IBM Proprietary and Confidential Information Second Amended and Restated Master Services Agreement minimum, on a *, with special notice for major Changes proposed on a longer term but requiring more preparation and Coordination.
(c) At a minimum, each submitted proposed Change shall include all standard applicable information to provide effective Change Management and Supplier shall include in each submission a schedule of proposed Implementation dates for determination of any existing conflict with business events communicated to Supplier by Gap, including:
(1) A description of the proposed Change;
(2) A statement of purpose and justification for the proposed Change;
(3) A list of Service(s), Gap Authorized User(s), and Third Party Vendor(s) potentially affected by the proposed Change;
(4) The proposed schedule, including Implementation date(s) and approximate time(s);
(5) The proposed Implementation process; and
(6) A statement of the potential risk, business impact, and/or complexity of the proposed Change.
(d) For proposed Changes that represent a potentially high risk or high impact to Gap’s operations or business, or at the request of Gap, Supplier shall include a comprehensive end-to-end test plan (including clear Change acceptance criteria); notification and escalation lists per agreement of Gap and Supplier; and work-around plans and a comprehensive contingency plan, including a back-out plan and procedures (with specific criteria to initiate the execution of the back-out plan).
(e) Reviewing proposed Changes and schedules with Gap, obtaining all necessary approvals and coordinating all Supplier Change Management activities with Gap and all affected third parties to minimize disruption of normal business process.
(f) Reporting the status of scheduled Changes including maintaining a comprehensive list of projects and dates.
(g) Providing regular progress updates to Gap and other known affected third parties.
Change Management Process and Procedures. Supplier’s responsibilities with respect to Change Management processes and procedures include:
(a) Participating in Change meetings. Supplier’s representative in these meetings shall have the requisite authority to make binding and enforceable commitments on behalf of Supplier.
(b) Submitting all proposed Changes in advance to Gap for Approval. Unless otherwise mutually agreed, all proposed Changes shall be submitted to Gap, at a minimum, on a *, with special notice for major Changes proposed on a longer term but requiring more preparation and Coordination.
Change Management Process and Procedures. Supplier’s responsibilities include the following:
1. Participate in Company’s Change Advisory Board (CAB) meetings as prescribed by Company Policies.
2. Submit proposed Changes in advance to Company. At a minimum, each submitted proposed Change will include:
a. A description of the Change.
b. The purpose and justification for the Change, including any corresponding Service Request, Incident, or Problem identifiers.
c. A list of Services, Authorized Users, and Third-Party Vendors potentially affected by the Change.
d. The proposed schedule, including implementation dates and approximate times for determination of any existing conflict with business events.
e. The proposed implementation procedures.
f. A rating of the potential risk, business impact, and/or complexity of the Change.
3. Where a proposed Change represents a potentially high risk or high impact to Company’s operations or business, or at the request of Company, Supplier will also:
a. Include a comprehensive end-to-end test plan (including clear Change acceptance criteria), notification and escalation lists, and work-around plans.
b. Include a comprehensive contingency plan, including a back-out plan and procedures (with specific criteria to initiate the execution of the back-out plan).
4. Verify compliance with Company Policies.
5. Review proposed Changes and schedules with Company, and obtain all necessary approvals for proposed Changes.
6. Coordinate with Company the impact on all affected Third Parties and designated representatives at Sites potentially affected by a Change in order to minimize disruption of normal business processes.
7. Control system Changes and activities required by moves, upgrades, replacements, migrations, and so forth.
8. Include rollout, testing, and roll-back plans for every Service Request for Change.
9. Provide information to Company in accordance with the Company Change Management Process on the outcome of any Service Request for Change and the updated status after each Change is implemented.
10. Update all operational and other documentation affected by the Change.
11. Report the status of scheduled Changes, including maintaining a comprehensive list of projects and dates.
12. Collect data on every Change attempted, which includes the following:
a. The cause of any Incidents, measures taken to prevent recurrence, and whether the Change was successful from the perspective of the Authorized User or Third Party affected by the Change.
13. Conduct Post Implementatio...