Overview of the Blackout Policy solution
Overview
When a change request with one or more configuration items (CIs) is in a Scheduled state in BMC Helix ITSM, BMC Helix Intelligent Automation creates a blackout policy that includes the CI details in BMC Helix Operations Management. All events generated on the associated CIs are ignored, and you cannot perform any operations on events that are blacked out until the blackout period expires.
Before implementing the blackout policy solution, learn more about the solution:
- A single blackout policy is created for a single change request. A change request can contain multiple CIs.
- A blackout policy is created only when the change request is in a Scheduled status.
- If a change request is updated for associating CIs or if the scheduled start or end date changes before the scheduled blackout period, the policy also gets updated.
- When the change request is marked as Complete, Cancelled, or Pending, even if the blackout period has not expired, the blackout policy gets deleted in BMC Helix Operations Management.
- After the change request is complete and marked as Closed, no more automation policies are triggered.
Video
The following video created by the BMC Customer Support team (4:52) gives an overview, demonstrates the steps to configure the solution, and walks you through the use case flow:
Products involved
The following table provides information about the products involved and the role of each product.
Product | Role |
---|---|
BMC Helix Intelligent Automation | Automates creating, updating, and deleting blackout policies in BMC Helix Operations Management based on a change request scheduled in BMC Helix ITSM. |
BMC Helix Operations Management | Suppresses events for a scheduled maintenance window by using the blackout policies that are enabled based on a scheduled change request. |
BMC Helix ITSM | Supported change management system. |
For more information about the supported versions of each of the products, see System-requirements.
Where to go from here