Default global approval processes for BMC Change Management
Remedy ITSM ships with default approval processes that are designed for global use.
The recommended approval processes are already defined for you by default. These global configuration records specify which status occurs next if an approval is approved or rejected, or if no approvers are defined.
Preconfigured approval phases and processes for Change Management
The preconfigured approval processes are described in the following table. These basic approval processes can be configured and applied based on the fields values defined on the tabs of the Approver Mappings form.
Approval Phase | Process | Definition |
|---|---|---|
Review | Change Level CI-IA - Review | This level approval process occurs when the change reaches the Review phase. If approved, the change moves to the Business Approval phase. If no approvers are mapped, the change moves directly to the Business Approval phase and requires the change manager or the change coordinator to move the change forward. By default, the status of this approval process for this phase is Enabled. |
Business Approval - No Impact | Change - Ad Hoc | By default, this Ad Hoc approval process applies only to changes with a Timing setting of No Impact. However, you could use this process with any approval phase. When the change moves through the process flow and the change manager approves the change in the Business Approval - No Impact phase, the change then moves to the Scheduled status. You use this process for pre-approved No Impact changes where the change is automatically scheduled after the approval phase is satisfied. By default, the status of this approval process for this phase is Enabled. For more information, see Configuring additional No Impact processes (optional). |
Business Approval | Change Level CI-IA - Business | This level approval process occurs when the change reaches the Business Approval phase.
|
Implementation Approval | Change Level CI-IA - Implementation | This level approval process occurs when the change reaches the Implementation Approval phase. If approved, the change moves to the Scheduled status. If no approvers are mapped, the change moves to the Scheduled status and requires the change manager or change coordinator to move the change forward. By default, the status of this approval process for this phase is Enabled. |
Close Down Approval | Change Level CI-IA - Close Down | This level approval process occurs when the change reaches the Close Down Approval phase. If the change is approved, the change moves to the Completed status and the Status Reason is automatically updated to Final Review Complete. If no approvers are mapped, the change moves to the Completed status and the Status Reason remains as Final Review Required. By default, the status of this approval process for this phase is Enabled. |
Any phase | Change Management Chain | The Parent-Child process type uses the manager of the change requester as the approver. Based on the levels of approval defined, the process selects approvers based on the requester's manager, or the this manager's manager. This approval is not configured for use out of the box. |
Any phase | Change Ad Hoc | Provides routing authority to each approver without requiring the administrator to create approver mappings for every individual or group. The Change Ad Hoc approval process can be used in any phase. For Change Management, the change manager is the first approver. |
Comments
Log in or register to comment.