How does the BMC Change Management integration work?

When you configure a change request on a CI for maintenance in BMC Change Management, and update its status to Scheduled or higher, a notification is sent to Operations Management. Operations Management displays the change request as change event in the TrueSight console, and creates an automated blackout policy and a scheduled down time for the change event. 

An Operations Management change event is initiated when the change request has reached the Scheduled state and the event is closed when the change request reaches Completed state.

Note

  • Any ITSM change requests defined before Operations Management is integrated with BMC Change Management are not configured for automated blackout policy or down time creation after the integration.
  • Any change requests created in BMC Change Management version 7.6 or earlier do not generate change events in Operations Management, even if the change events are upgraded from BMC Change Management version 7.6 to a newer version of BMC Change Management.

Notification scenarios

The following table lists the possible notification scenarios and their outcomes: 

Scenario

Activity

Outcome

No CI is associated with the task and request.

None

No notification is sent to Operations Management.


  1. Move the change request (no CI associated with it) to Scheduled state.
  2. Add a task and associate a CI to it.

Notification for the CI associated with the change request is sent to Operations Management.


  1. Move the change request (no CI associated with it) to Scheduled state.
  2. Add a task and associate a CI to it.
  3. Move the change request to Implementation in Progress state so that the task is in Staged state.
  4. Move the task to Work In Progress state.

The following notifications are sent to Operations Management:

  • Change-CI
  • Task-CI

Different CIs are associated with the task and change request.

Move the change request (one CI associated with it) to Scheduled state.

Notification for CI associated with the change request is sent to Operations Management.


  1. Move the change request (one CI associated with it) to Scheduled state.
  2. Add a task to the change request and associate a different CI to the task.
  3. Move the change request to Implementation In Progress state so that the task is in Staged state.
  4. Move the task to Work In Progress state.

The following notifications are sent to Operations Management corresponding to the CI associated with the task:

  • Change-CI
  • Task-CI

The same CI is associated with the change and task request.

  1. Move the change request (one CI associated with it) to Scheduled state or Implementation In Progress state.
  2. Add a task and move it to Work In Progress state.
  3. Add the same CI that is associated with the change request to the task.

Notification for the CI associated with the task is sent to Operations Management.

Note

Operations Management receives notifications only for CIs with cell enabled classes.

Supported request statuses

The integration between BMC Change Management and Operations Management supports the following request statuses.
Change request statuses

  • Scheduled 
  • Implementation In Progress 
  • Completed 
  • Closed 
  • Pending 
  • Cancelled

Task request statuses:

  • Staged 
  • Assigned 
  • Pending 
  • Work In Progress

Click the Related Event icon in the TrueSight console to view all of the task events associated to the change event.
For more information about change request and task request statuses, see the BMC Change Management User Guide.

Communicating between BMC Change Management and Operations Management

BMC Change Management sends change and task requests to Operations Management through RESTful web services. 



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*