Performing an impact analysis for a change request


You can run an IT impact analysis for a change request by using the Initiate impact analysis option. Additionally, you can also run a network impact analysis by using the Network impact analysis console or the Initiate network impact analysis option.

When you run the impact analysis from the Network impact analysis console, you can select the input CIs and their impact weight. When you run the impact analysis by using the Initiate network impact analysis option (quick impact analysis), the impact analysis process uses only the associated CIs and the default impact weight.

Before you begin

  1. Run a SmartGraph Sync Schedule from BMC Helix CMDB .
    For more information, see Scheduling a SmartGraph Sync to share impact attributes with BMC Helix Telco Extensions in the BMC Helix CMDB online documentation portal.
  2. As an administrator, enable BMC Helix Network Service Operations for Communication Service Providers.
    For more information, see Setting-up-and-going-live.
  3. As an administrator, configure the network impact analysis settings for change requests.
    For more information, see Configuring Change Management.
  4. As an administrator, configure the Impact Weight Mapping for the different impact levels.
    For more information, see Configuring-the-impact-analysis-settings.
  5. To run the impact analysis, make sure you have the Change Master or Change User permissions.
    For more information, see Roles-and-permissions.

 

 

To run an IT impact analysis for a change request by using the Initiate impact analysis option

For more information, see the "To perform impact analysis and relating CIs and services" section in the Monitoring the progress of a change request topic in theBMC Helix ITSM: Change Management online documentation portal.

 

To run a network impact analysis by using the Impact Analysis Console

When you run the network impact analysis by using the Impact Analysis Console, you can select the input CIs and their impact weight. Additionally, after the process is successfully completed, based on the results, you have the option to relate the impacted CIs back to a new or existing change request.

  1. Click Console > Impact Analysis Console.
    Impact analysis console.png
  2. From the right corner, click + Impact analysis run.
    Impact analysis run.png
  3. On the Select input CIs tab, enter the Description, and from the list of CIs, select the required CIs.
    New impact analysis run.png
  4. Click Add selected.
  5. Select the new impact weight (%) for the selected CIs and click Save.
    Confirm impact weight.png
  6. Confirm the list of CIs and the impact weights.
    You can also select the required CIs and click Remove or Change impact weight.
    Run analysis.png
  7. Click Run analysis.
    After the impact analysis process starts, the following message is displayed:
    Success. The impact analysis process has started successfully.
  8. From the Impact analysis window, for the impact analysis that you have performed, click the three dots and select either of the following options:
    • Create incident—From the Create incident window, create a new incident and click Save.
    • Create change—From the Create change request window, create a change request and click Save.
    • Relate to incident—From the Relate to incident window, select the required incident, and click Relate.
    • Relate to change—From the Relate to change window, select the required change request, and click Relate.
      Create menu.png

 

 

To run a network impact analysis for a change request by using the Network impact analysis console

  1. From an existing change request, select More > Network impact analysis console.
    Network impact analysis console_change.png
  2. Click + Impact analysis run.
  3. Select either of the following options:
    1. Use associated CIs—You do not have the option of selecting CIs. Only the CIs associated with the change are considered with their default impact weight. After the impact analysis process starts, the following message is displayed:
      Success. The impact analysis has been started using the associated CIs and default impact weight. You can view details in the impact analysis console.  
    2. Select input CIs—You have the option of selecting the required CIs and deciding the impact weight.
      Network impact analysis console 3_change.png
  4. (For the Select input CIs option only) From the New impact analysis run window, select either of the following options:
    1. Select CIs from ticket—This ticket analysis option retrieves all the associated CIs related to the change. 
    2. Select from all CIs—This what-if analysis option retrieves all the CIs from the BMC.ASSET dataset in BMC Helix CMDB
      The description field is automatically populated based on the selection, which you can modify.
      Network impact analysis console 4_change.png
  5. Select the required CIs and click Add selected.
  6. Select the new impact weight (%) for the selected CIs and click Save.
    Network impact analysis console 5_change.png
  7. Confirm the list of input CIs and the impact weights.
    You can also select the required CIs and click Remove or Change impact weight.
    Network impact analysis console 6_change.png
  8. Click Run analysis.
    After the impact analysis process starts, the following message is displayed:
    Success. The impact analysis process has started successfully.Data URI image
  9. After the impact analysis process is completed successfully or even if the impact analysis process fails, an email with the following information is sent to the user who started the impact analysis process:

    The impact analysis run initiated by <username> for the CRQ000000000001 has been completed.

    Change details:
    ————————————————————————————————————
    Change ID: CRQ000000000001
    Priority: High
    Status: In progress
    Summary: Broken fiber optic cable
    ————————————————————————————————————

    Impact analysis details:

    ————————————————————————————————————
    Description: What-if run for <username>
    CIs impacted: 113
    CIs with LoS: 113
    Services impacted: 1
    Services with LoS: 1
    ————————————————————————————————————

 

To run a network impact analysis for a change request quickly by using the Initiate network impact analysis option

 Make sure that the change has at least one associated CI with the Associate type other than Impacts.

  1. To run an impact analysis quickly without manually selecting any additional CIs, from an existing change request, select More > Initiate network impact analysis.
  2. The impact analysis process starts and the following message is displayed:
    The impact analysis has been started using the associated CIs and default impact weight. You can view details in the impact analysis console.

 The process automatically selects the input CIs from the associated CIs with their default weights (100%), except the CIs with the Association Type as Impacts.

 

To view the progress of the impact analysis process for a change request

  1. Run the impact analysis process.
    For more information, see To run network impact analysis for a change request by using the Impact Analysis Console.
  2. From the Network impact analysis console, click Successful from the Status column.

 

To relate impacted CIs back to the change request for an IT impact analysis

For more information about relating CIs and services for IT impact analysis, see the "To perform impact analysis and relating CIs and services" section in the Monitoring the progress of a change request topic in theBMC Helix ITSM: Change Management online documentation portal.

 

To relate impacted CIs back to the change request for a network impact analysisEdit

  1. Run the impact analysis process by using the Network impact analysis console > Select input CIs > Select CIs from ticket option.
    For more information, see To run network impact analysis for a change request by using the Impact Analysis Console.
  2. From the change for which you performed the impact analysis process, select More > Network impact analysis console.
  3. Click the required number from any of the following columns:
    • CIs impacted
    • CIs with LoS
    • Services impacted
    • Services with LoS
    • CIs degraded
    • Services degraded
  4. From the Impacted CIs window, select the required CIs.

     

    Important

    The tick mark under the Input CI column represents input CIs. 

    The link icon under the Already related column represents the CIs that are already associated with the change request.

    Impact analysis Relate CIs.png

  5. Click Relate selected CIs.
  6. Alternatively, you can also select all CIs and click Relate all CIs.
    The following message is displayed:
    Impact analysis Relate CIs message.png
    The related CIs are displayed under the Configuration Item tab of the change with the Association type as Impacts.
  7. If the number of related CIs is more than 100 (default value), an email notification with the following information is sent to the service desk agent who has related the CIs:

    The relationship of the impacted CIs for CRQ000000000001 that is initiated by <username> has been completed.

    CIs related successfully: 501
    CIs already related: 0
    CI relationship creation failed: 0

    Change details:
    ————————————————————————————————————
    Change ID: CRQ000000000001
    Priority: High
    Status: In progress
    Summary: Broken fiber optic cable
    ————————————————————————————————————

    Important

    An administrator can change the default value (100) for the number of CIs. For more information, see To configure the value for the number of CIs.

    Known limitations

    • The impact analysis run for a change request cannot be opened from the activity log entries. 

 

 

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