Change Control Management. 2.1 Either Service Provider or Client may initiate a Change Request by delivering to the other's Designated Executive or his/her nominated representative a writing that describes the Change and sets forth the reasons for it. Service 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 Management. With Customer’s assistance, XXXX will develop and document a written change control plan, following XXXX’x then-current implementation management and processes outlining the implementation plan, test plan, back-out and recovery plan, and the responsibilities of both Customer and XXXX in implementing Application Software releases consisting of fixes and patches (n), maintenance release updates (Z). During such implementations, XXXX will provide Remote Support (or On-Site Support, at XXXX’x discretion) throughout the implementation of the change control plan. Change Control development is subject to the 28 day notification requirement. 4 Extended Services When an Order includes XXXX Extended Services, XXXX will deliver the following Services:
Change Control Management. 1 3.0 EFFECTIVENESS OF A CHANGE......................................... 4 4.0 CHANGE MANAGEMENT REPORTING REQUIREMENTS.......................... 4 5.0 FAILURE TO AGREE.................................................. 5 6.0 EMERGENCY CHANGE PROCESS; COMPULSORY CHANGES...................... 5 7.0 CHANGE REQUEST LOG................................................ 5 SCHEDULE K CHANGE CONTROL MANAGEMENT
Change Control Management. Changes in scope may happen due to a variety of unforeseen factors. For the purposes of this program, change is defined as a request originating from the Commonwealth or Vendor that affects scope, schedule, and/or cost to the Commonwealth. It is known, at the time of issuing of this RFP, that there will be changes to the requirements, presented herein, as rules and regulations evolve and are finalized by CMS and by the Commonwealth. These rules and regulations are expected to change through the lifecycle of the project. Changes in requirements due to evolution of Federal and Commonwealth regulations do not constitute a change in scope for this program. Potential changes to regulations, such as those pending legislation or judicial review, that pose the potential to disrupt the delivery schedule shall be documented by the selected Vendor in the Risk and Issue Log as defined in the approved PMP and managed accordingly. The selected Vendor shall inform CHFS of any potential scope changes as soon as is reasonably possible to discuss, analyze, and document the impact of the change in scope, and determine direction and next steps. The assessment of the change in scope shall include specific impacts to both schedule and costs. CHFS will work with the selected Vendor to confirm/reconfirm Project scope for subsequent tasks, phases, and/or milestones. Additional details of the changes to scope are available in Section 40 of this RFP.
Change Control Management. 5.1.11.1 Change Management is the process whereby out of scope requests or requirements are documented, analyzed, assessed for impact on the project and submitted for approval on mutually agreed upon Change Management Control.
Change Control Management. Both parties shall make commercially reasonable efforts to come to agreement on a change control management process no later than thirty (30) days following the date of this contract. The process shall be defined around the following areas: - Planned Maintenance Procedures - Planned Service Interruption
