General Release Management Clause Samples
General Release Management. Service Provider’s responsibilities include:
1. Define and establish Release Management Policies and procedures which support the following:
1.1. Coordinate with other Service Component Providers and DIR Customer to ensure the provision of requested support as needed for a successful deployment.
1.2. Define agreed upon release and deployment plans, including the overall Release Management Plan and Release schedule, with DIR and DIR Customers.
1.3. Ensure that each release package consists of a set of related assets and service components that are compatible with each other.
1.4. Ensure that integrity of a release package and its constituent components is maintained throughout the transition activities and recorded accurately in the CMS.
1.5. Ensure that all release and deployment packages can be tracked, installed, tested, verified, and/or uninstalled or backed out if appropriate.
1.6. Ensure that organization and stakeholder change is managed during the release and deployment activities.
1.7. Record and manage deviations, risks, issues related to the new or changed service and take necessary corrective action.
1.8. Ensure that there is knowledge transfer to enable the customers and users to optimize their use of the service to support their business activities.
1.9. Ensure that skills and knowledge are transferred to operations and support staff to enable them to effectively and efficiently deliver, support and maintain the service according to required warranties and service levels.
1.10. The definition, identification and management of release units.
1.11. The definition, identification and use of release design options.
1.12. The identification, design and management of releases and release packages.
1.13. The identification, design and management of release models.
1.14. The planning, execution and management of testing methods, tools and procedures.
1.15. The use of pilots.
1.16. The definition of release success / failure criteria for each point in the Release lifecycle.
1.17. Establish measurement processes to record the success and failure of Releases, including recording Incidents related to Release activities in the period following a Release.
2. Perform tracking of the Release Management Plan and oversight of functions against the execution of the plan.
3. Participate in the formal review and close of Releases (e.g. post-mortem review), including the following:
3.1. Capturing experiences and feedback on customer, user and Service Provider satis...
General Release Management. Service Provider responsibilities include:
1. Conform Service Provider operations to policies and procedures that set the objectives, scope and principles that will ensure the success of the Release Management process, including compliance with policies and procedures for the following:
1.1. Assist the DIR Customer and other DCS Service Providers in the provision of requested support as needed for a successful deployment.
1.2. Define agreed upon release and deployment plans, including the overall Release Management Plan and Release schedule, with DIR and DIR Customers.
1.3. Ensure that each release package consists of a set of related assets and service components that are compatible with each other.
1.4. Ensure that integrity of a release package and its constituent components is maintained throughout the transition activities and recorded accurately in the CMS.
1.5. Ensure that all release and deployment packages can be tracked, installed, tested, verified, and/or uninstalled or backed out if appropriate.
1.6. Ensure that organization and stakeholder change is managed during the release and deployment activities.
1.7. Record and manage deviations, risks, issues related to the new or changed service and take necessary corrective action.
1.8. Ensure that there is knowledge transfer to enable the customers and users to optimize their use of the service to support their business activities.
1.9. Ensure that skills and knowledge are transferred to operations and support staff to enable them to effectively and efficiently deliver, support and maintain the service according to required warranties and service levels.
1.10. The definition, identification and management of release units.
1.11. The definition, identification and use of release design options.
1.12. The identification, design and management of releases and release packages.
1.13. The identification, design and management of release models.
1.14. The planning, execution and management of testing methods, tools and procedures.
1.15. The use of pilots.
1.16. The definition of release success / failure criteria for each point in the Release lifecycle.
1.17. Establish measurement processes to record the success and failure of Releases, including recording Incidents related to Release activities in the period following a Release.
2. Maintain a Release Management Plan, which includes Release schedule, that ensures compliance with Release Management Policies and process, which at a minimum articulates the f...
General Release Management. (a) Within 90 calendar days prior to the start of a calendar year (or as otherwise reasonably advised by PEXA to the Financial Institution), PEXA will provide the Financial Institution with an indicative timetable of the new release programs, Major Releases and Minor Releases, to be implemented in that calendar year.
(b) PEXA will schedule no more than two Major Releases and two Minor Releases (this does not include any Scheduled Maintenance) in relation to the ELN each calendar year, unless otherwise agreed between the parties.
(c) PEXA will, prior to implementing any release into production, rigorously test that release to a standard which would reasonably be expected of a well run and diligent professional services organisation providing services similar to the Services and, where requested by the Financial Institution, provide a summary of such test results, including details of any known issues, to the Financial Institution.
(d) For any release other than Scheduled Maintenance, ▇▇▇▇ will, prior to implementing that release into production:
(i) provide the Financial Institution with at least 6 calendar months’ notice of the scheduled date of implementation of that release into production and regularly update the Financial Institution of any changes to that scheduled date. PEXA will use its best endeavours to schedule releases during non-peak periods and at times which minimise disruption to the Services;
(ii) provide the Financial Institution with the specification and list of enhancements and modifications ("Release Notes") for the release as soon as practicable prior to implementation of that release into production and in any event with reasonably sufficient notice in order to enable the Financial Institution to properly implement any necessary modifications to its internal processes, procedures, systems or access points;
(iii) provide the Financial Institution with controlled access to the release in a non- production environment in line with an agreed (with each Financial Institution) implementation schedule (provided that such access is provided in a mutually agreed timeframe prior to the implementation of that release into production unless otherwise agreed in writing), to enable the Financial Institution to:
(A) conduct its own tests on the release, including with respect to any integration with or access points to the Financial Institution’s systems; and
(B) conduct such training with the Financial Institution as is reasonably considered neces...