Operator-Initiated Change
Goal
The goal of this use case is to automate the change tracking process whenever an automated job execution requires approval.
The following video (04:09 min) explains this use case and provides a quick demonstration of the capability.
When operational changes are implemented, operators need to document these changes in BMC Remedy Change Management. To automate this change tracking process, a Request For Change (RFC) is automatically created in BMC Remedy Change Management when a BMC Server Automation operator submits a job that requires change management tracking and approval. After the change is approved in Change Management, the job is scheduled for execution in BMC Server Automation. After the job has run, the change task is closed with an associated completion status and any changed configuration items (CIs). The change management user can view the job details in the BMC Server Automation console.
This use case can be executed in an on premises deployment or in a hybrid deployment.
Products needed in this use case
- An automation system such as BMC Server Automation (running on premises)
- An intermediate transport layer such as BMC Atrium Orchestrator (running on premises)
- A change management system such as BMC Remedy Change Management (running on premises or on demand)
Benefit
The main benefit of this integration is to enforce continuous compliance to the change process without introducing labor intensive activities. The integration reduces the risk of unauthorized and unplanned changes through enforced change tracking.
Workflow
The following diagram depicts the workflow of the operator initiated change use case.
The following table describes the stages of this use case:
Stage | Description |
|---|---|
1 | A job operator creates a job for a job type and specifies that the job requires change management approval prior to execution. The job is then scheduled. |
2 | A Request For Change is sent to the change management system. |
3 | A request to create a change record is sent to the change management system through BMC Atrium Orchestrator. |
4 | A suitable template is applied to the change record based on the inputs received in the change creation request. |
5 | The change manager reviews and approves the RFC. A change record is created. |
6 | Certain changes can occur either in the change record or in the original job definition. |
7 | After the change record is approved, the job is executed in the automation system. |
8 | BMC Atrium Orchestrator polls for updates to the change record and reflects those updates in the automation system including worklog updates. |
9 | If the change record is approved, job is executed in the automation system. If the change record is rejected, job is cancelled. |
10 | The change record is updated with the job status. |
11 | The change record is closed in change management. |
Where to go from here