This documentation supports the 1.4 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Determining the impact of changes in Smart IT

You can run an impact analysis when you submit a change request in Smart IT, or at any time from change request details. Impact analysis helps you evaluate and manage the risks of a change request, by identifying the services and configuration items (CIs) most affected by the change. Relating the services and CIs found in impact analysis to the change request also helps you identify and manage collisions.


To access impact analysis functionality, you must have the required permissions. See "Smart IT Permissions" in Related topics

Overview of impact analysis

Impact analysis searches BMC Atrium CMDB for CIs and services with impact relationships to CIs related to the change request. The impact relationships among CIs and services must be defined in BMC Atrium CMDB before you run impact analysis, as explained in "Creating relationships between CIs" in Related topics. If you relate additional CIs to the change request after the impact analysis job has started, the new CIs will not be part of the analysis.

The universal client displays relationships among all impacted CIs in a graphical format. Mobile clients show the first 100 impacted CIs in a list view only, with service CIs prioritized at the top.

You have the option to relate services and CIs that were found in the impact analysis to the change request. If you do so, additional collisions might appear in the alerts banner in change request details, based on change requests that exist for the newly related items. You can manage the new collisions as explained in "Managing collisions in Smart IT" in Related topics.

After you relate one or more CIs or services from an impact analysis, the impact analysis job is no longer active in the system. You can also choose to discard or cancel an impact analysis and try again. If you run subsequent impact analysis jobs, the analysis uses only the original items that were related to the change request, not new items that were related to the change request as a result of previous impact analysis jobs.


Impact analysis helps you understand the impact of a change on the system. To simulate the impact of a particular CI (or set of CIs) becoming impaired or unavailable (for disaster planning, for example), use the BMC Atrium Impact Simulator. In BMC Atrium Impact Simulator, you can configure different scenarios, save a simulation and run it again later, or generate a report from the simulation results. For more information, see "Simulating the impact of changes to CIs" in Related topics.

Example impact analysis

As a change coordinator in his organization, Allen wants to manage collisions for a change request. Before doing so, he wants to make sure an impact analysis has been completed, so he can identify and relate all impacted CIs and services to the change request.

  1. Allen opens an existing change request in the Ticket Console in the universal client. 
    The alert banner has a message about collisions, but there is no indication that an impact analysis was run at the time that the change request was saved.
  2. From the More menu on the change request, Allen clicks Initiate Impact Analysis.
    Allen continues working in a new window until he receives a notification that the impact analysis is complete.
  3. Allen opens the impact analysis results from the notification.
    The results show a total of 50 CIs (including 2 services) that are impacted by the change. The CIs and services are arranged in a graph so that Allen can see the relationships among them.
  4. Allen can click individual CIs and relate them to the change request. He also has the option to relate all of the impacted services and CIs to the change request, or just the services. He chooses Relate All > Relate All CIs to relate both CIs and services.


    On mobile clients, you must select and relate individual CIs.

  5. He saves the change request
    The alert banner on the change request details shows more collisions than before the impact analysis.
  6. Allen works with the other change coordinators in his organization to manage the collisions.

How administrators configure this functionality

Impact analysis is enabled by default and requires no configuration. You can choose to disable this functionality for individual tenants (or for the default tenant, if multitenancy is not enabled). See "Disabling collision management and impact analysis in Smart IT" in Related topics.

Related topics

Managing collisions in Smart IT

Creating relationships between CIs (BMC Atrium Core documentation)

Simulating the impact of changes to CIs (BMC Atrium Core documentation)

Smart IT Permissions

Disabling collision management and impact analysis in Smart IT

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.