Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Document control
| Page properties | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Process Owner
OMB
|
...
|
...
|
...
v14
|
...
with process review
Procedure reviews
The following table is updated after every review of this procedure.
...
...
...
...
...
...
...
Table of contents
...
| Excerpt | ||||||
|---|---|---|---|---|---|---|
OverviewThe EGI Change Management is a centralized process for the EGI Federation. If organisations are providing EGI branded services and are already running their own internal Change Management process, they may continue to do so if their process meets the essential requirements of ISO20k with respect to change management:
In addition to the above, if any changes are planned that have the potential to impact other EGI branded services, then the EGI Change Management process should be informed in advance by submission of a ticket following CHM1. EGI Foundation should keep track of organizations running their own internal Change Management process and should periodically run a lightweight audit described in this procedure to ensure that the above requirements are being met. DefinitionsPlease refer to the EGI Glossary for the definitions of the terms used in this procedure. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Entities involved in the procedure
TriggersThe CHM Process Manager becomes aware that an organisation running an EGI branded service is running |
...
its own internal Change Management process Steps
Organisations in EGI Foundation running their own Change Management process
| ||||||||||||||||||||||||||||||
...
|
...
|
...
|
...
|
...
|
Table of contents
| Table of Contents | ||||
|---|---|---|---|---|
|