Configuring criteria for historical impact analysis

The impact analysis engine can use historically identified impact data, rather than impact analysis rules, to calculate impacts. Historical analysis leverages existing impact information to reduce analysis time. It also enables Change Analysts to calculate impacts if you have not captured the CI relationship information that the rules require, or if you are using assets, rather than CIs. A rules-based analysis cannot be performed on assets.

About this task

When it uses historical impact data to retrieve impacts for a Change, the impact analysis engine uses two system properties that define the criteria for the search. As an administrator, you can configure these system properties to meet the needs of the impacts analyses in your data center.
  • Overview of historical analysis
    When a Change Analyst specifies a historical impact analysis, the impact analysis engine mines existing impact data to find previously completed implementation tasks that have the same target CI or asset for which you want impact data. The engine harvests the impacts that were previously identified for those tasks.
  • Modifying criteria for historical impact analysis
    The criteria that you use to perform historical impact analyses restrict the engine to a specified number of implementation tasks, and to a time period during which to search for tasks. This product ships with default values for each of these criteria, which are defined as system properties. You can modify these criteria to meet the requirements of your historical analyses.
Parent topic: Managing impact analysis settings

Feedback