Common use of Change Management Process and Procedures Clause in Contracts

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 Exhibit A.8 Gap / IBM Proprietary and Confidential Information Second Amended and Restated Master Services Agreement minimum, on a ** rolling calendar, 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 the 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; andand * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. (6) A statement of the potential risk, business impact, and/or complexity of the proposed Change. (d) For proposed Changes that represent represents 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 Projects and dates. (g) Providing regular progress updates to Gap and other known affected third parties. (h) Testing Changes to the Gap IT Environment and Resolve Incidents and Problems prior to production Implementation, including inter-operability testing. (i) Controlling Changes to systems and activities required by moves, upgrades, replacements, and migrations. (j) Collecting data and reporting to Gap on a * on every Change attempted, including the cause of any related Incidents and Problems, the measures taken to prevent recurrence and whether the Change satisfied the documented acceptance criteria. (k) Maintaining records of any and all Changes to both the production and test environments within Gap’s IT Environment.

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 ** rolling calendar, 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;; * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. (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. (h) Testing Changes to the Gap IT Environment and Resolving Incidents and Problems prior to production Implementation, in the Gap provided Test environment. (i) Controlling Changes to systems and activities required by moves, upgrades, replacements, and migrations.