Change Control Process. The University may at any time request in writing (each, a “Change Request”) changes to the Statement of Work, including changes to the Services and Implementation Plan (each, a “Change”). Upon the University’s submission of a Change Request, the parties will evaluate and implement all Changes in accordance with this Section 2.2.
(a) As soon as reasonably practicable, and in any case within twenty (20) Business Days following receipt of a Change Request, Supplier will provide the University with a written proposal for implementing the requested Change (“Change Proposal”), setting forth:
(i) a written description of the proposed Changes to any Services or Deliverables;
(ii) an amended Implementation Plan reflecting: (A) the schedule for commencing and completing any additional or modified Services or Deliverables; and (B) the effect of such Changes, if any, on completing any other Services under the Statement of Work;
(iii) any additional University Resources Supplier deems necessary to carry out such Changes; and
(iv) any increase or decrease in Fees resulting from the proposed Changes, which increase or decrease will reflect only the increase or decrease in time and expenses Supplier requires to carry out the Change.
(b) Within thirty (30) Business Days following the University’s receipt of a Change Proposal, the University will by written notice to Supplier, approve, reject, or propose modifications to such Change Proposal. If the University proposes modifications, Supplier must modify and re-deliver the Change Proposal reflecting such modifications, or notify the University of any disagreement, in which event the parties will negotiate in good faith to resolve their disagreement. Upon the University’s approval of the Change Proposal or the parties’ agreement on all proposed modifications, as the case may be, the parties will execute a written agreement to the Change Proposal (“Change Notice”), which Change Notice will be signed by the University’s Agreement Administrator and will constitute an amendment to the Statement of Work to which it relates; and
(c) If the parties fail to enter into a Change Notice within fifteen (15) Business Days following the University’s response to a Change Proposal, the University may, in its discretion:
(i) require Supplier to perform the Services under the Statement of Work without the Change;
(ii) require Supplier to continue to negotiate a Change Notice;
(iii) initiate a Dispute Resolution Procedure; or
(iv) notwithstan...
Change Control Process. 2.1 Either Provider or Company may initiate a Change Request by delivering to the other's Relationship Manager or his/her nominated representative a writing that describes the Change and sets forth the reasons for it. Provider shall assign a unique number to any such request and shall register the Change Request in the Change Request Log as described in Section 7.1. Each Change Proposal that may be prepared for a Change Request shall be tracked by reference to the Change Request to which it relates.
2.2 Each Party's respective Relationship Manager or his/her nominated representatives shall be responsible for reviewing and considering any Change Request, and shall approve it for further investigation, if deemed necessary. If the Parties agree that the Change Request requires further investigation, the Company and Provider Relationship Managers shall authorize such investigation, which shall be performed as required by Provider and/or Company. In accordance with Section 7.2, the Relationship Managers shall be responsible for keeping up to date the status of each Change Request in the Change Request Log as the status of the Change Request changes through the Change Control Process. Schedule K - Technical Services Agreement - Final 1 October 18, 2001 Proprietary and Confidential International Paper / Exult
2.3 For each Change Request that the Parties have approved for further investigation, regardless of which Party has proposed or investigated the Change, Provider shall prepare and submit to Company within [***]* (or as otherwise agreed), with Company's full cooperation and provision of any information reasonably requested by Provider, a preliminary report containing the following information and analysis:
(a) Such preliminary report shall contain:
(i) the estimated costs associated with the Change;
(ii) the timeframe for implementing the Change (including any timing constraints);
(iii) the preliminary technical or business case for making the Change, as well as any changes or additions to policies, standards and procedures in accordance with which the Change is to be implemented;
(iv) an initial analysis of the potential risks (if any) to Company or Provider if the Change is not implemented;
(v) an estimate of the costs and expenses associated with preparing a comprehensive Change Proposal containing the information and analysis set forth in Section 2.3(b) below (the "Estimate"). Provider shall bear the costs of preparing the preliminary report and Estimate ...
Change Control Process. The CI Plus LLP shall notify Named Licensee of changes by procedure set forth in Exhibit K (Change Procedure).
Change Control Process. Any request for any change in services must be in writing; this includes requests for changes in project plans, scope, specifications, schedule, designs, requirements, service deliverables, software environment, hardware environment or any other aspect of your order. Oracle shall not be obligated to perform tasks related to changes in time, scope, cost, or contractual obligations until you and Oracle agree in writing to the proposed change in an amendment to this ordering document and/or applicable exhibit(s).
Change Control Process. During the Term of this Project Agreement, the Parties may mutually agree to alter the Field Operations Services outlined in this Exhibit A-1. Such changes will be addressed as follows:
(1) Assess the impact of scope changes on Project schedules, resources and pricing;
(2) Provide a formal vehicle for approval to proceed with any changes to the Project Agreement;
(3) Provide a Project audit record of all material changes to the original Project Agreement; and
(4) If requirements arise that are outside the scope of this Exhibit A-1, a Change of Scope document (or an amendment to the Project Agreement, as applicable) will be submitted for Client approval following the below process:
(i) Client requests additional requirements for new functionality or deliverables outside the scope of work provided herein.
(ii) Syneos Health reviews change, meets with Client and internal team members to understand and scope Client expectations regarding business need, timelines, and other deliverable expectations.
(iii) Syneos Health provides Change of Scope (or Amendment or new Project Agreement, as applicable) document, which outlines work effort, timeline and pricing impacts of the change. Pricing will be determined based on standard rates provided below.
(iv) Client accepts proposal and signs Change of Scope (or Amendment or new Project Agreement, as applicable) document which authorizes work to begin on the change request.
(5) Standard Pricing Table. RolePrice/HR Software Development [***] CRM Configuration [***] Data Management [***] Alignment/Call Planning [***] Incentive Comp Modeling/Design [***] Analytics & Reporting [***] Project Management/Business Analysis/Solution Design [***] Testing [***] IC Administration [***] Training (Content/Delivery) [***] Hardware/Help Desk [***]
Change Control Process. IWT projects follow a standard change control process. If during the course of a project, a scope change is identified, then the IWT project manager will document the change and associated cost or schedule impacts on a change authorization form. Once documented, the IWT project manager reviews the change with the Client project manager. Scope changes are defined as any modification to the agreed scope of a project, including but not limited to requirements, software modules, configuration changes, project delays and enhancements or modifications to the product. Scope changes can require modification to cost, schedule, quality or other project deliverables and therefore require sign-off from the Client project manager. No work on scope changes will be conducted until sign off is obtained. Changes that impact scope require approval from the IWT project manager and the Client project manager.
Change Control Process. 13.1 Unless otherwise provided herein, all proposed changes, additions or modifications by either Party to the services, including all proposals by service recipient for additional services (such changes, additions, modifications and additional services, collectively, “changes”) shall be subject to the formal change control process set forth in this Clause 13 (the “Change Control Process”). The Party seeking a change will document the proposed change in writing, deliver such writing to the other Party, and specify a desired implementation date. The Party receiving the proposal for a change shall evaluate.
13.2 No change shall be effective unless and until the Parties in their own discretion, mutually agree on the changes and reflect such agreed upon changes in writing on amended terms or an amended schedule which shall include the following information, as applicable:
13.2.1 the date and term of effectiveness of the changes,
13.2.2 a description of the changes,
13.2.3 the applicable charges, if any, for such changes, and
13.2.4 any additional provisions applicable to the changes that are not otherwise set forth in this Agreement or that are exceptions to the provisions set forth in this Agreement.
13.3 Amended terms or an amended schedule reflecting changes made pursuant to this Clause 13 shall become effective only when executed in writing by both of the Parties.
Change Control Process. The change control process is part of the overall project management system which will be implemented by Vendor to control changes to the Services. Either ACI or Vendor may request a change to a Project subject to the following change control process:
a. A Project may be changed only by a writing signed by authorized representatives of ACI and Vendor.
b. All Project Change Requests (“PCRs”) to a Project will be submitted in writing by the requesting Vendor or ACI Project Manager. The PCR will reference the Project, describe at a reasonable level of detail the change, the rationale for the change and the impact the change may have on the Project both if it is accepted and if it is rejected.
c. The Project Managers will review the PCR and either:
(1) recommend approval of the change by authorized representatives of ACI and Vendor signing the PCR. Upon such approval, the change will be implemented; or
(2) agree in writing to submit the PCR for further investigation and to pay Vendor for its reasonable charges, if any, for Vendor’s investigation. Such investigation will determine the technical merits and the effect on price, schedule, and other terms and conditions that may result from the implementation of the PCR. ACI and Vendor will then agree to mutually approve or reject the PCR. If ACI and Vendor do not agree, either Vendor or ACI may submit such PCR to the Project Executives for resolution; or
(3) reject the PCR. If rejected, the PCR will be returned to the requesting Project Manager along with the reason for rejection.
Change Control Process. Change control for additional Services or scope to be delivered under a Statement of Work will be completed according to the following procedure prior to DevFactory starting any work.
(a) Specific changes may be proposed by Client’s business team members.
(b) Proposed changes will be reviewed by DevFactory and a report of the scope, schedule, resource and budget impact (“Impact Report”) will be prepared and delivered to Client management.
(c) Client management reviews the Impact Report and approves by signature or denies changes in scope, schedule, resources and/or budget.
(d) DevFactory receives the signed, approved Impact Report and creates. for Client’s approval, an additional Statement of Work with a copy of the Impact Report attached.
(e) Client approves by signature such Statement of Work and delivers such Statement of Work to DevFactory for DevFactory’s signature.
(f) DevFactory begins work on specific changes defined in the signed, approved Impact Report only upon the mutual execution of the new Statement of Work referenced above.
Change Control Process. Either party may request changes to an Exhibit upon notice to the other, and the parties will use Wind River’s PCR form for this purpose. If the changes proposed by Customer are feasible in Wind River’s opinion, Wind River will submit an estimate of the effort required to evaluate Customer’s request, including any fees or expenses associated with such effort. If the request is made by Wind River, Wind River will submit an estimate of the effort required to generate a reasonably detailed proposal. Customer will sign or reject each PCR within ten (10) working days, and return it to Wind River. In the event the Parties are unable to resolve any outstanding issues involving a PCR within five (5) working days after Customer rejects the PCR, Wind River shall proceed with the Exhibit without incorporating any changes proposed in the PCR; provided however, Wind River shall not be liable for any schedule delays in the Exhibit resulting from the change control process.
