Change Management Sample Clauses

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. 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.

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. 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. 16.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. 16.2. A Change Request can be signed only by an authorised signatory of the Requesting Party. 16.3. A Change Request signed by the authorised signatory of the Recipient is an agreed Change to this Agreement. 16.4. Until such time as a Change Request is signed by both parties in accordance with this clause, the Agreement shall not be varied by the proposed Change and each party shall, unless otherwise agreed in writing, continue to fulfil its obligations as if the proposal for a Change had not been made. Any discussions which may take place between the parties in connection with a proposed Change before the agreement of the Change Request shall be without prejudice to the rights of each Party. 16.5. Each Change Request shall be raised by providing in writing the following information to the Recipient, clearly stating that the document is a Change Request in accordance with this clause of this agreement: 16.5.1. a Change Request reference number; 16.5.2. the author and submission date of the Change Request; 16.5.3. the requested implementation date (which shall be no less than 20 working days from the date of the Change Request); 16.5.4. the reason for the Change; 16.5.5. full details of the Change including an assessment on all aspects of the Agreement and Services; 16.5.6. any proposed changes in the Charges; 16.5.7. the consequential amendments, if any, to this Agreement (including the Schedules) necessitated by the Change; and 16.5.8. the date of expiry of validity of the Change Request which, unless agreed otherwise, shall be for twenty (20) Working Days after the date the Change Request. 16.6. For the avoidance of doubt, any written notice that contains all of the information set out in clause 16.5 shall be considered a valid Change Request, and the Recipient shall be obliged to comply with the terms of this clause. 16.7. On receipt of a valid Change Request, the Recipient shall, within the period of validity of the Change Request, evaluate the Change Request and: 16.7.1. decide to approve, sign and return the Change Request to the Requesting Party; 16.7.2. decide to reject the Change Request, g...

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. 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. 21.2 Subject to Clause 21.3 of this Schedule 2 of these Call-off Terms and Conditions, 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 any Change Control Process if any 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. 21.3 Any change to the Data Protection Protocol shall be made in accordance with the relevant provisions of that protocol.

Change Management. Coinbase has built a production environment designed with strict controls, which includes a formal change management process to manage changes to software, applications and system software that will be deployed within the production environment. New (or changes made to existing) products, services and features (“Changes”) are deployed in a development environment that closely mirrors the production environment. Before Changes are deployed in the production environment, they are peer reviewed and automated security, functional, and unit testing is performed. Customer data is not used outside of the production environment unless required for troubleshooting issues where real data is relevant and, even then, the data is first obfuscated to prevent exposure of personal data. Prior to high-risk Changes being made, an assessment is carried out to consider the impact and risk of a requested change, evidence acknowledging applicable testing for the change, approval of deployment into production by appropriate approver(s), and roll back procedures. After all tests are passed, and peer reviews completed, Changes are deployed to the production environment. All Changes deployed in the production environment must be indexed and documented using a formal and auditable system of record. The production environment is closely monitored for anomalous conditions that may suggest unexpected activity or potential security threats. When a vulnerability is identified, the criticality will be evaluated and the service affected will be isolated, patched or upgraded as necessary according to vulnerability management requirements. Coinbase has implemented a Bug Bounty Program, available at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇/coinbase, through which researchers may report design and implementation issues or possible vulnerabilities.

Change Management. UKG shall employ a change management process based on industry accepted standards for change management in configurations, software, and hardware.