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. 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.
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. The State may at any time request in writing (each, a “Change Request”) changes to the Statement of Work, including changes to the Services, Work Product, Implementation Plan, or any Specifications (each, a “Change”). Upon the State’s submission of a Change Request, the parties will evaluate and implement all Changes in accordance with this Section 2.2.
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 Transition subject to the following change control process:
Change Control Process. Within ninety (90) days after the Effective 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 "Change Control Process"). The purposes and objectives of the Change Control Process are (i) to determine whether a change to the System is within the scope of the Services or constitutes a New Service under the applicable Transaction Documents, (ii) to prioritize all requests for changes to the System ("CHANGE REQUESTS"), (iii) to minimize the risk of exceeding both time and cost estimates associated with the Change Requests by identifying, documenting, quantifying, controlling, managing and communicating Change Requests and their disposition and as applicable, implementation; and (iv) 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 System. 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. The Change Control Process shall include, at a minimum:
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. 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.
Change Control Process. The purpose of the Change Control Process is to control any additions, deletions, or modifications to the Scope for any constraint including but not limited to cost, resources or schedules. All requests for changes must be evaluated and approved (or disapproved). The steps required to change this SOW are as follows: The Provider Project Manager will create an Innotas CR (Change Request), first describing the proposed change and then enumerating the reasons for it. The Provider Project Manager will provide proper documentation as an aid in the analysis process. The Provider Project Manager will evaluate the effect the change will have on a constraint including the timeline and budget of the project and will forward the request to the District Project Manager and District PMO Director for review. District Project Manager and District PMO Director will review the CR and prepare it for review at the Functional Steering Committee meeting. The Functional Steering Committee will review the CR and will either approve or reject the request. If the request is approved, the District Project Manager will present the CR to the Executive Steering Committee for approval. If approved, the result will be recorded in the Innotas Issues. The District PMO Director will approve the CR. Relevant tasks are then added to the detailed Project Plan of the Project and/or constraint adjustments which may include Scope, Budget, Timeline, Risk, Resources will be made. If the Project Functional or Executive Steering Committee rejects the request, the Provider Project Manager(s) are notified and alternative steps will be taken to fulfill the work requirements. The scope issue will be closed out in the Innotas Issues and marked as rejected in the Innotas CR. APPENDIX B – ADDITIONAL PROJECT RELATED TERMS AND CONDITIONS
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:
