Use > Modeling > Modeling > Impact Analysis Manager > How to Define an Impact Rule – Workflow

How to Define an Impact Rule – Workflow

This section describes how to define an Impact rule whereby a change in CPU operation impacts the node to which it is connected.

  1. Create an Impact Analysis TQL Query

    To create an Impact Analysis TQL query, you need to create an Impact Analysis TQL and then add the TQL query nodes and relationships that define the query.

    Select Managers > Modeling > Impact Analysis Manager to open the Impact Analysis Manager. For details about how to create an Impact Analysis TQL query, see New Impact Rule/Impact Rule Properties/Save As Impact Rule Wizard. For details about how to add query nodes and relationships to a query, see How to Add Query Nodes and Relationships to a TQL Query.

    Example of an Impact Analysis TQL Query:

    In this Impact Analysis TQL query, a CPU and a node are linked by a Composition relationship. The TQL query results must comply with the direction of the arrows.

    Note An Impact Analysis TQL query is subject to certain validation restrictions. For details, see Troubleshooting and Limitations – Topology Query Language.

  2. Define an Impact Rule

    When you define an Impact rule, you must specify the required causal relationship between the query nodes. Define one query node as the trigger, or the query node that represents the changes you want to make to the system, and another query node as the one that is impacted.

    Right-click the query node you want to define as the trigger query node and select Define Impacted to open the Impacted Query Nodes dialog box. Select the query node you want the trigger query node to impact. Then click the Add button to open the Impact Rules Definition dialog box to set conditions for defining impacted query nodes. For details about how to define an Impact rule, see Impact Rules Definition Dialog Box.

    Note The change state option in the Impact rule definition is no longer relevant for Impact Analysis. The only supported state is operation.

    Example of an Impact Rule:

    The Conditions area in the Impact Rules Definition dialog box defines the conditions under which the simulated change in the system is triggered. The Severity area defines the severity of the impact on the impacted query node.

    The Impact rule in this example states that when the CPU operation is not in the normal state, the node is impacted. Since the severity is set to 100% of the trigger's severity, the severity of the node is the same as the severity of the CPU, which is determined when Impact Analysis is run.

    In the resulting TQL query, an upward arrow appears next to the query node defined as the trigger query node and a downward arrow appears next to the query node defined as the impacted query node.

    Note To retrieve the Impact Analysis results, you must run the Impact rule in IT Universe Manager. For details, see How to Retrieve Impact Analysis Results – Scenario.

Related Topics Link IconRelated Information