Agreement Change Control Process Sample Clauses

Agreement Change Control Process. (a) Within thirty (30) days after the Commencement Date and for the remainder of the Term, the Parties shall define, establish, implement, document and maintain a Change Control Process for activities, processes, provisions and operations under the Agreement (including each Transaction Document) and to evolve the Services. The purposes and objectives of the Change Control Process are (i) to review each Change Request to the Agreement (including any Transaction Document) and the Services to determine whether such change is appropriate, (ii) to determine whether such change is within the scope of the Services or constitutes a New Service under the applicable Transaction Documents, (iii) to prioritize all Change Requests, (iv) to minimize the risk of exceeding both time and cost estimates associated with the requested changes by identifying, documenting, quantifying, controlling, managing and communicating requested changes and their disposition and as applicable, implementation; and (v) to identify the different roles, responsibilities and actions that shall be assumed and taken by the Parties to define and implement the changes to the Services and to the Agreement (including any Transaction Document). The Project Executives shall be the focal point for all Change Requests and shall be responsible for promptly and diligently effecting the activities set forth above in this Section 6.3 with respect to each Change Request. ----------- (b) The Change Control Process shall include, at a minimum: (i) Changes to the Agreement (including any Transaction Document) and Services may be requested by either Party. Since a change may affect the price, Schedule J, Performance Standards, Minimum Service Levels, Service Credits ---------- and/or other terms, both the Equifax and EDS Project Executives must review and approve, in writing, each Change Request before any Change Request is implemented. (ii) The Party proposing a Change Request will prepare a Change Request Form, describing the change, the rationale for the change and the effect that change will have (if completed) or the impact it will have (if rejected) on the Agreement, any Transaction Document and/or the Services. (iii) Equifax's or EDS's Project Executive, as appropriate, will review the proposed Change Request. If accepted, the Change Request Form will be submitted to the other Party for review. If rejected, the Change Request Form will be returned to the originator along with the reason for rejection. (iv...
AutoNDA by SimpleDocs

Related to Agreement Change Control Process

  • Change Control Procedure 34.1 In the event that either Party desires any change the terms of this Agreement or any Contract which may materially impact on the timings, scope, Specification or Charges of the Goods or Services, or the scope of either parties’ obligations under this Agreement or the relevant Contract, or which the relevant Party otherwise reasonably determines warrants the use of this change control procedure, the following procedures will apply: (a) the Party requesting the change will deliver a “Change Request” (in the form (or substantially in the same form) contained in Schedule 5 to this Agreement) which describes: (i) the nature of the change; (ii) the reason for the change; (iii) the effect that the requested change will have on the scope or Specification for the Goods or Services; and (iv) any change to the Charges and the Term. (b) Upon receipt of a Change Request, the receiving Party’s authorised representative will contact his/ her counterpart within 5 working days to discuss and agree the Change Request. The parties will negotiate the proposed changes to the Agreement and/or affected Contract in good faith and agree a timeline in which to finalise the Change Notice. (c) Neither party is obliged to agree to a Change Request, but if the parties do agree to implement such a Change Request, the appropriate authorised representatives of both parties will sign the Change Request which will be effective from the date set out in the Change Request. (d) If there is any conflict between the terms and conditions set out in the Agreement or any Contract and the Change Request, then the terms and conditions set out in the most recent fully executed Change Request will apply. (e) The Supplier shall neither be relieved of its obligations to supply the Goods and/or Services in accordance with the terms and conditions of this Agreement or any Contract, nor be entitled to an increase in the Charges as the result of: (i) a General Change in Law; or (ii) a Specific Change in Law where the effect of that Specific Change in Law on the Goods and/or Services is reasonably foreseeable at the Commencement Date of this Agreement, or, where the Change Request relates to a Contract, the applicable Contract Commencement Date. 34.2 The Parties agree that any variations to the Agreement or any Contract to reflect non- material changes (including for example a change to the name/contact details of a Party’s representative) may be agreed in writing and shall not be required to be made in accordance with the procedure in this clause 34, provided always that UKRI shall, in their absolute discretion, decide whether a proposed change is non-material for these purposes.

  • Change Control Procedures (a) No changes or additions may be made to any Work Order without the written agreement of LAUSD as evidenced by a duly executed Change Order. (b) Contractor will not take an action or make a decision which may have a material effect on LAUSD or which adversely affects the function or performance of, or decreases the resource efficiency of, the Services, including implementing changes in technology or equipment and software configuration, without first obtaining LAUSD’s written approval, which approval LAUSD may withhold in its sole discretion as respects any change which may have an adverse effect on LAUSD or the Services.

  • Agreement Changes The Company reserves the right to change the terms of this Agreement and the Plan without your consent to the extent necessary or desirable to comply with the requirements of Code section 409A, the Treasury regulations and other guidance thereunder.

  • AMENDMENT AND CHANGE CONTROL Any amendment or change of any nature made to this Agreement and the Schedule of Requirements thereof shall only be valid if it is in writing, signed by both Parties and added to this Agreement as an addendum hereto. In this regard a Change Notice must first be defined and issued by the requesting Party. A Change Notice Response must then be issued by responding Party. A formal approval of the Change Request will then trigger the issue of the addendum to this Agreement.

  • Amendment, change and supplement Any amendment, change and supplement to this Agreement shall require the execution of a written agreement by all of the Parties.

  • Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.

  • Exchange Control Information Exchange control reporting is required for cash transactions exceeding AUD10,000 and for international fund transfers. The Australian bank assisting with the transaction will file the report for you. If there is no Australian bank involved in the transfer, you will have to file the report.

  • Exchange Control Notification Exchange control reporting is required for cash transactions exceeding A$10,000 and international fund transfers. If there is an Australian bank assisting with the transaction, the Australian bank will file the report for the Participant. If there is no Australian bank involved in the transaction, the Participant must file the report.

  • Account Changes Neither the Financial Institution nor the Grantor will change the name or account number of a Collateral Account without the consent of the Secured Party. The Financial Institution will promptly notify the Servicer of any changes. This Agreement will apply to each successor account to a Collateral Account, which will also be a Collateral Account.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!