Change Management Process. If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.
Change Management Process. During the Term of this Agreement or any Renewal Term, the parties may determine that change(s) to the Agreement is necessary. In such an event, the parties shall determine if the proposed change amounts to a material revision as described in this Section before determining how that change will be documented.
Change Management Process. If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice or as otherwise specified in the SOW.
Change Management Process. In the event the employer considers that the employee’s role could be affected by redundancy or could be made redundant, the employer shall consult with the employee and NZEI Te Riu Roa regarding the possibility of redundancy. In the course of this consultation the employer shall provide to the employee and NZEI Te Riu Roa sufficient information to enable understanding and meaningful consultation, and shall consider the views of the employee with an open mind before making a decision as to whether to terminate the employee’s employment due to redundancy. Nothing in this clause limits the legal rights and obligations of the parties.
Change Management Process. ENTITY agrees to notify STATE in advance of any changes associated with this MOU or access to the CURES data that will materially affect or impact the technical environment of the HIT system, including, but not limited to, technical or system changes involving major modifications to infrastructure or disconnection from the CURES database by ENTITY, and modifications to agreed upon configurations or outages. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU.
Change Management Process. If You or Blue Planet requests a change in any of the specifications, requirements, Deliverables, or scope of the Professional Services described in any SOW, within five (5) days of receipt of written notice of such requested change, each party’s Project Lead shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Blue Planet will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties and, to the extent applicable, You issue Blue Planet or an Affiliate of Blue Planet a purchase order for any additional Change Order fees. Executed Change Orders shall be deemed part of, and subject to this Agreement. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution. Blue Planet will not perform any work detailed in a Change Order until it has been executed by both parties.
Change Management Process. Each Party may request a Change to an SOW. Changes shall be made pursuant to the following process:
4.2.5.1 For all Changes requested by either Party, except as otherwise provided in this MSA, Service Provider shall prepare and deliver to ALU, within fifteen (15) Days or such other agreed timeframe, a written response indicating, at a minimum, the following: (i) the effect of the proposal, if any, on the amounts payable by ALU hereunder; (ii) the effect of the proposal, if any, on Service Levels; (iii) the anticipated time schedule for implementing the proposal, as well as the effect of the proposal, if any, on any schedule associated with a Project or any other work undertaken by Service Provider in conjunction with the Services; and (iv) any other information requested or reasonably necessary for ALU to make an informed decision regarding the proposal.
4.2.5.2 To the extent a Change under this Section is agreed by the Parties, it shall be documented using a Change Order approved by the Parties in writing. Each Change Order shall include: (i) the identity of the requesting Party and the date of the request for the Change; (ii) the reason for the Change; (iii) the requested Changes (including associated changes, if any, in the pricing and Service Levels); and (iv) a description of how the change will be implemented.
Change Management Process. The Change Management Process provides change control and management of CE firewall configuration changes, as requested by you. With Change Management Process, Rogers will acknowledge your change request within one
(1) business day, at which time Rogers and you will schedule a review of the change request. During the review, a maintenance window will be scheduled for the applicable configuration change (the “Maintenance Window”). The Change Management Process provides unlimited single changes (subject to Rogers’ reasonable requirements) for certain types of changes as itemized in the Table 1 below. For change requests that are deemed billable, a one- time billable change request service fee may apply. You will be informed at the time of request if the change is billable and its Rogers sales representative will provide you with a quotation in order to proceed with the work. Change Management Process includes the following:
4.7.1 All moves/adds/changes/deletes (“MACD”) will be scheduled for an agreed-upon date and time with you.
4.7.2 You must submit an email to the Rogers support team and copy its Rogers sales representative for all move/add/change/delete requests.
4.7.3 All MACD requests will be acknowledged and you will be contacted by Rogers within one (1) Business Day to review and schedule a Maintenance Window to perform the change.
4.7.4 All emergency changes will be deemed billable.
4.7.5 For change requests not identified in the below table, You will be advised at time of request of the change request timeframe completion requirements and applicable rate structure.
4.7.6 You will be responsible for any charges associated with required on-site technicians to implement moves/adds/changes.
4.7.7 You are responsible for testing network and/or application functionality within 48 (forty-eight) hours of completion of MACD by Rogers. If additional changes are required after this period, such changes will be subject to the Change Management Process. The following Table 1 provides examples of change requests. Table 1 – Examples of changes requests EXAMPLES OF CHANGE REQUESTS RESPONSIBILITY OF: BILLABLE OR INCLUDED CHANGE Rogers Client Standard change request Billable change request
Change Management Process. Change to any part of the Statement of Work, Service Levels, Agreement and/or associated Exhibits, policies or procedures will be managed by the Change Control Board. Events that could require a change include but are not limited to business planning activities, budget changes, audit or regulatory requirements, benchmark study results, process improvement team recommendations or changes in the EMW business. In each case the following process will be followed to approve changes. The initiator/sponsor of the change will document that request through a project change request (PCR) and present it to the Change Control Board for consideration. The change request document must include at a minimum a detailed description of the recommended change, the objective and benefits of the change, the cost to implement the change, any risks associated with making the change, the impact of the change to other processes, time schedules, agreements, exhibits, etc. The initiator/sponsor will also provide a high-level implementation project plan and communication plan for the change. Within three days of receipt of the PCR with regard to the SI Services and within 15 days of a receipt of the PCR with regard to the Steady State Services, the Change Control Board will review the proposed change and approve it for investigation or rejection. IBM shall make any changes requested by EMW with regard to the SI Services subject to IBM being compensated at the hourly rate for services set forth for SI Services in Exhibit 4. If the Change Control Board denies any other change, the initiator/sponsor will be notified of the reason for such rejection and the change request will be closed. If the Change Control Board denies any change with regard to the Steady State Services that IBM is the exclusive provider pursuant to Section 3.04 of the Agreement, then EMW shall be entitled to implement such change itself or engage a third party to implement such change. If the Change Control Board approves the change, the initiator/sponsor will provide a detailed project plan for implementation approved by all relevant parties to the Change Control Board. The initiator/sponsor will assign a project manager to manage the implementation plan and provide monthly status to the Change Control Board until such time as the change has been implemented and the request can be closed. Change requests denied by the designated approving authorities could be escalated by the initiator/sponsor pursuant to the Dispute...
Change Management Process. Continuous process improvements occur as new technology emerges and customer needs are better understood. This Agreement between NPIRS and the authorized Export Tracking Mart users ensures that any enhancements or corrective activity implemented to processing within NPIRS will be applied to the data mart structure/processing when available and appropriate, along with appropriate documentation and release notes in accordance with NPIRS Change Control procedures and notifications. Additional details regarding the NPIRS change management process may be found in the “NPIRS Change Management Plan” under the Documentation Library on the IHS Data Warehouse internet web site at xxxx://xxx.xxx.xxx/NDW/.
