Change control process flows
The BMC Helix ITSM: Change Management application supports several best practice change control process flows for the various changes classes. The following change classes are provided out-of-the-box:
Change classes | Description |
|---|---|
Standard | Change requests that are typically preapproved and require approval by the Change Manager. |
Emergency | Change requests that resolve an incident or problem deemed critical to business continuity and for which a workaround is not sufficient. |
Expedited | Change requests that have an enterprise-wide impact with an associated risk. |
Latent | Change requests that have already been performed. This out-of-the-box configuration of latent changes cannot be changed. |
Normal | Change requests that proceed through all steps of the change management process and those that are categorized as medium or high risk will be reviewed by the Change Advisory Board (CAB). |
No Impact | Change requests that indicate a change that has no impact on the infrastructure and requires no approval. |
The Change Management application supports the custom approval process configuration for altering the status changes within a given class. Additionally, the application supports custom change control process flows by using change templates. For more information, see Configuring-process-flows-and-approvals.
Change control process flow for Standard and Normal changes
Within the change control process flow for Standard and Normal changes, there are eight defined stages or sub processes, three of which are approval processes. All the approval stages require approval mapping configurations to make them active.
No. | Stages | Reference topic |
|---|---|---|
1 | Change Initiation and Recording | |
2 | Approval: Authorization for Business Assessment | |
3 | Change Assessment, Planning, and Scheduling | |
4 | Change Plan and Schedule Review | |
5 | Approval: Authorization for Implementation | |
6 | Change Implementation | |
7 | Approval: Authorization for Close Down | |
8 | Change Completion and Close Down |
The following process flow explains the lifecycle stages of a change request for Standard and Normal changes.
Change control process flow for No Impact changes
Within the change control process flow, there are six defined stages or sub processes, two of which are approval processes. The approval stages are optional and require approval mapping configurations to make them active. The stages are:
No. | Stages | Reference topic |
|---|---|---|
1 | Change Initiation and Recording | |
2 | Change Plan and Schedule Review | |
3 | Approval: Authorization for Implementation | |
4 | Change Implementation | |
5 | Approval: Authorization for Close Down | |
6 | Change Completion and Close Down |
The following change control process flow explains the lifecycle stages of a change request for out-of-the-box No Impact changes.
Change control process flow for Latent changes
Within this process flow, there are three defined stages or sub processes, one of which is an approval process. The approval stage is optional and requires an approval mapping configuration to make it active. The stages are:
No. | Stages | Reference topic |
|---|---|---|
1 | Change Initiation and Recording | |
2 | Approval: Authorization for Close Down | |
3 | Change Completion and Close Down |
The following change control process flow explains the lifecycle stages of a change request for out-of-the-box Latent changes.
