Common use of CONTRACT CHANGE Clause in Contracts

CONTRACT CHANGE. (a) Either Party may request a Change to the Agreement or any Service Agreement (“Contract Change”) by providing the other Party with written Notice of such request (a “Contract Change Request”) describing the proposed Contract Change. In addition to the requirements of Section 23.7 of the Master Agreement, a copy of any such Notice shall also be provided to the Customer Technical Alliance Manager and the Provider Client Executive. Provider will track the status of each Contract Change Request in the manner described in the Procedures Manual. (b) The Customer Technical Alliance Manager and Provider Client Executive, or their respective designated representatives, will be responsible for reviewing and considering any Contract Change Request. (c) Regardless of which Party has proposed the Contract Change, Provider will prepare, at its expense, and submit to Customer as soon as practicable, but in any event within ten (10) Business Days after receipt of the Contract Change Request, unless the Parties mutually agree that more time is reasonably required to complete the requirements for the Contract Change, Provider’s analysis (the “Change Proposal”) of the impact, if any, of the proposed Contract Change on the following elements: CONFIDENTIAL TREATMENT HAS BEEN REQUESTED FOR PORTIONS OF THIS EXHIBIT. THE COPY FILED HEREWITH OMITS THE INFORMATION SUBJECT TO A CONFIDENTIALITY REQUEST. OMISSIONS ARE DESIGNATED [ * * * ]. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. (i) the scope of Services and the Parties’ respective Responsibilities; (ii) Charges; (iii) Service Levels; (iv) technology refresh requirements and obligations; (v) delivery dates; (vi) evaluation testing and Acceptance Criteria; (vii) DR/BC Plan; (viii) Third Party Agreements; (ix) Account Governance; (x) regulatory requirements; (xi) Security Requirements; (xii) the policies and procedures as set forth in the Procedures Manual; (xiii) any impacts on other interfaces, other systems and services; (xiv) the Exit Plan; and (xv) any other matter reasonably requested by Customer at the time of preparation of the Change Proposal or reasonably considered by either Party to be relevant or impacted by implementation of the proposed Contract Change. If the Change Proposal submitted by Provider does not include an impact analysis for any of the foregoing elements, Customer may assume in its evaluation of the Change Proposal that the proposed Contract Change has no impact on such element. Provider will resubmit the updated Change Proposal to address the impact to an element not included in Provider’s initial Change Proposal (“Revised Change Proposal”) and Customer will review such Revised Change Proposal within a reasonable time if (i) any of Customer’s members on the Contract and Commercial Committee becomes aware of an impact to an element not addressed in the initial Change Proposal and notifies Provider of such impact in accordance with the procedures set out in Exhibit 3 (Account Governance) or (ii) Provider discovers an impact to an element not addressed in the initial Change Proposal and notifies Customer of such impact in accordance with the procedures set out in this Exhibit. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED FOR PORTIONS OF THIS EXHIBIT. THE COPY FILED HEREWITH OMITS THE INFORMATION SUBJECT TO A CONFIDENTIALITY REQUEST. OMISSIONS ARE DESIGNATED [ * * * ]. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. (d) Once submitted by Provider, Customer will review the Change Proposal. Within 30 days after receipt of the Change Proposal, unless the Parties mutually agree that more time is reasonably required to review the Change Proposal, Customer will either: (i) approve the Change Proposal; (ii) reject the Change Proposal; (iii) request further analysis of, or information regarding, the Change Proposal; or (iv) request a meeting between the Parties to discuss the Change Proposal further (a “Change Proposal Meeting”). (e) In the event Customer requests a Change Proposal Meeting, the Parties will use reasonable efforts to agree at such meeting to either: (i) approve the Change Proposal; (ii) gather further information regarding the Change Proposal; (iii) modify the Change Proposal as necessary and approve such Change Proposal, as modified; or (iv) reject the Change Proposal. (f) In the event that the Party initiating a Contract Change Request believes that the requested Change is required or necessary, the requesting Party shall inform the other Party in writing of the reasons why the Change is required and the impact if the Change is not implemented. In the event that the other Party does not agree to implement the Change, the requesting Party may consider the other Party’s failure to agree to implement the Change as a Dispute, and the requesting Party may escalate such Dispute for resolution in accordance with the Master Agreement with the intention of reaching a mutually agreeable resolution according to the Dispute Resolution Procedures. (g) The Parties will continue to follow the process detailed above until a final resolution regarding the proposed Contract Change is reached. The Parties will act in good faith at all times during such process.

Appears in 1 contract

Sources: Master Services Agreement (Sabre Corp)

CONTRACT CHANGE. (ai) Either Party may request a Change to the Agreement or any Service Agreement (“Contract Change”) by providing the other Party with written Notice of such request (a “Contract Change Request”) describing the proposed Contract Change. In addition to the requirements of Section 23.7 of the Master Agreement, a copy of any such Notice shall also be provided to the Customer Technical Alliance Manager and the Provider Client Executive. Provider will track the status of each Contract Change Request in the manner described in the Procedures Manual. (bii) The Customer Technical Alliance Manager and Provider Client Executive, or their respective designated representatives, will be responsible for reviewing and considering any Contract Change Request. (ciii) Regardless of which Party has proposed the Contract Change, Provider will prepare, at its expense, and submit to Customer as soon as practicable, but in any event within ten (10) Business Days after receipt of the Contract Change Request, unless the Parties mutually agree that more time is reasonably required to complete the requirements for the Contract Change, Provider’s analysis (the “Change Proposal”) of the impact, if any, of the proposed Contract Change on the following elements: CONFIDENTIAL TREATMENT HAS BEEN REQUESTED FOR PORTIONS OF THIS EXHIBIT. THE COPY FILED HEREWITH OMITS THE INFORMATION SUBJECT TO A CONFIDENTIALITY REQUEST. OMISSIONS ARE DESIGNATED [ * * * ]. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION.: (i1) the scope of Services and the Parties’ respective Responsibilities; (ii2) Charges; (iii3) Service Levels; (iv4) technology refresh requirements and obligations; (v5) delivery dates; (vi6) evaluation testing and Acceptance Criteria; (vii7) DR/BC Plan; (viii) 8) Third Party Agreements; (ix9) Account Governance; (x10) regulatory requirements; (xi11) Security Requirements; (xii12) the policies and procedures as set forth in the Procedures Manual; (xiii13) any impacts on other interfaces, other systems and services; (xiv14) the Exit Plan; and (xv15) any other matter reasonably requested by Customer at the time of preparation of the Change Proposal or reasonably considered by either Party to be relevant or impacted by implementation of the proposed Contract Change. If the Change Proposal submitted by Provider does not include an impact analysis for any of the foregoing elements, Customer may assume in its evaluation of the Change Proposal that the proposed Contract Change has no impact on such element. Provider will resubmit the updated Change Proposal to address the impact to an element not included in Provider’s initial Change Proposal (“Revised Change Proposal”) and Customer will review such Revised Change Proposal within a reasonable time if (i) any of Customer’s members on the Contract and Commercial Committee becomes aware of an impact to an element not addressed in the initial Change Proposal and notifies Provider of such impact in accordance with the procedures set out in Exhibit 3 (Account Governance) or (ii) Provider discovers an impact to an element not addressed in the initial Change Proposal and notifies Customer of such impact in accordance with the procedures set out in this Exhibit. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED FOR PORTIONS OF THIS EXHIBIT. THE COPY FILED HEREWITH OMITS THE INFORMATION SUBJECT TO A CONFIDENTIALITY REQUEST. OMISSIONS ARE DESIGNATED [ * * * ]. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. (div) Once submitted by Provider, Customer will review the Change Proposal. Within 30 days after receipt of the Change Proposal, unless the Parties mutually agree that more time is reasonably required to review the Change Proposal, Customer will either: (i1) approve the Change Proposal; (ii2) reject the Change Proposal; (iii3) request further analysis of, or information regarding, the Change Proposal; or (iv4) request a meeting between the Parties to discuss the Change Proposal further (a “Change Proposal Meeting”). (ev) In the event Customer requests a Change Proposal Meeting, the Parties will use reasonable efforts to agree at such meeting to either: (i1) approve the Change Proposal; (ii2) gather further information regarding the Change Proposal; (iii3) modify the Change Proposal as necessary and approve such Change Proposal, as modified; or (iv4) reject the Change Proposal. (fvi) In the event that the Party initiating a Contract Change Request believes that the requested Change is required or necessary, the requesting Party shall inform the other Party in writing of the reasons why the Change is required and the impact if the Change is not implemented. In the event that the other Party does not agree to implement the Change, the requesting Party may consider the other Party’s failure to agree to implement the Change as a Dispute, and the requesting Party may escalate such Dispute for resolution in accordance with the Master Agreement with the intention of reaching a mutually agreeable resolution according to the Dispute Resolution Procedures. (gvii) The Parties will continue to follow the process detailed above until a final resolution regarding the proposed Contract Change is reached. The Parties will act in good faith at all times during such process.

Appears in 1 contract

Sources: Master Services Agreement (Sabre Corp)