Change Management. BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.
Change Management. BNY Mellon shall require that changes to its network or software used to provide the services are tested and applied pursuant to a documented change management process.
Change Management. This clause provides a change management approach, and national oversight arrangements for management of change. This approach is to be used where the change is multi-dimensional and will challenge the ability of existing change management clauses in this agreement to respond efficiently and effectively; and where the proposed change will impact at one or more of the following levels:
Change Management. CPS must be notified of all post go-live changes to the Products, which include changes to functionality, the introduction of additional applications, major upgrades, and any expansion or reduction of data elements. Change notifications must be sent to an email address determined by CPS, and the notifications should be provided ( 1-week minimum) before any change takes effect.
Change Management. 15.1. Where either party wishes to seek a variation to this agreement (a “Change”) then that party (the “Requesting Party”) shall submit a change request as specified in this clause (a “Change Request”) to the other (the “Recipient”) and the provisions of this clause shall apply in respect of the Change. All Changes shall be made in accordance with this clause.
Change Management. The IT organization manages changes to the corporate infrastructure, systems and applications through a centralized change management program, which may include testing, business impact analysis and management approval where appropriate. All relevant application and systems developments adhere to an approved change management process. Security Incidents and Response Plan
Change Management. 21.1 The Supplier acknowledges to the Authority that the Authority’s requirements for the Services may change during the Term and the Supplier shall not unreasonably withhold or delay its consent to any reasonable variation or addition to the Specification and Tender Response Document, as may be requested by the Authority from time to time.
Change Management. (Changes to the baseline SOW must be documented for proper project oversight. Depending on your project, you may need to manage and capture changes to configuration, incidents, deliverables, schedule, price or other factors your team designates as critical. Any price changes must be done in compliance with the Code of Virginia, § 2.2-4309. Modification of the contract, found at this link: xxxx://xxx0.xxxxx.xx.xx/cgi-bin/legp504.exe?000+coh+2.2-4309+500825. Changes to the scope of this SOW must stay within the boundaries of the scope of the VITA Contract. For complex and/or major projects, it is recommended that you use the VITA PMD processes and templates located at: xxxx://xxx.xxxx.xxxxxxxx.xxx/oversight/projects/default.aspx?id=567. Administrative or non-technical/functional changes (deliverables, schedule, point of contact, reporting, etc.) should extrapolate the affected sections of this SOW in a “from/to” format and be placed in a numbered modification letter referencing this SOW and date, with a new effective date. The VITA Contract may include a template for your use or you may obtain one from the VITA Contract’s Point of Contact. It is very important that changes do not conflict with, but do comply with, the VITA Contract, which takes precedence. The following language may be included in this section, but additional language is needed to list any technical/functional change management areas specific to this SOW; i.e., configuration, incident, work flow, or any others of a technical/functional nature.) All changes to this SOW must comply with the Contract. Price changes must comply with the Code of Virginia, § 2.2-4309. Modification of the contract, found at this link: xxxx://xxx0.xxxxx.xx.xx/cgi- bin/legp504.exe?000+coh+2.2-4309+500825 All changes to this SOW shall be in written form and fully executed between the Authorized User’s and the Supplier’s authorized representatives. For administrative changes, the parties agree to use the change template, attached to this SOW. For technical/functional change management requirements, listed below, the parties agree to follow the processes and use the templates provided at this link: xxxx://xxx.xxxx.xxxxxxxx.xxx/oversight/projects/default.aspx?id=567
Change Management. The Supplier acknowledges to the Authority that the Authority’s requirements for the Services may change during the Term and the Supplier shall not unreasonably withhold or delay its consent to any reasonable variation or addition to the Specification and Tender Response Document, as may be requested by the Authority from time to time. Any change to the Services or other variation to this Contract shall only be binding once it has been agreed either: (a) in accordance with the Change Control Process if the Key Provisions specify that changes are subject to a formal change control process; or (b) if the Key Provisions make no such reference, in writing and signed by an authorised representative of both Parties.
Change Management. The parties recognise that change is an ongoing feature of the work environment and that appropriate management of change is essential for the benefit of both employees and the Council. For the purposes of the Agreement, change includes but is not limited to any of the following:
