The Change Impact Detection dashboard enables you to derive insights into Incidents that can potentially be caused by Change Requests. Most often, we do not have structured IT Service Management data that captures the link between Incidents and the Changes. Therefore, we analyze data from Change and Incident, such as free-form text fields, Configuration Items, Assignment Groups, and various other factors to determine the probability of an Incident being caused by a Change.
For example, common CIs between a Change and Incident indicate greater probability of the Incident being caused by the Change. Similarly, a Change description that reads "Reboot Server XYZ" has a greater probability of causing an Incident whose description reads "Due to reboot of Server XYZ".
A Change-Incident pair is formed based on the similarities and scores are assigned to determine the probability percentage.
The Change Impact Detection dashboard helps IT managers address the following scenarios:
The dashboard displays information applicable to the last 6 months and you can use the filters to analyze overall information specific to Leaders, Senior Leaders, or Change Assignment Groups.
The Change Impact Detection dashboard consists of the following sections:
Note: Incidents in the Canceled state are excluded.
You can select an Incident priority category in this report to drive and filter all the other sections of the dashboard.
You can select a specific bucket to drive and filter the remaining sections of the dashboard.
You can select a specific bucket to drive and filter the remaining sections of the dashboard.
The probability match percentage values for the Change-Incident pairs are categorized based on the following preconfigured buckets and can be modified based on your requirements:
You can select a specific bucket to drive and filter the remaining sections of the dashboard.
You can click the Last 30 Days or Last 13 Weeks headers to view day-wise or week-wise information. The bars in the graph represent the number of Changes and the line graph represents the number of Incidents.
You can select a specific bar graph or a node in the line graph to drive and filter the remaining sections of the dashboard.
The following table provides information about the factors and how they contribute to the scores:
Factor Name | Description |
---|---|
Time Difference Days Bucket | The time duration between Incident Opened Date and Change Actual Start Date/Change Implementation Date are grouped into preconfigured buckets and can be configured based on your requirements. By default, the following bucket values are provided: 0 to 3 days, 4 to 7 days, and all other days. This attribute contributes to the aggregate score and the scores are assigned as:
|
CHGINC Keywords Count Bucket | Count of common keywords across all text fields of the Change-Incident pairs. The values are offered as buckets and can be configured based on your requirements. By default, the following bucket values are provided: >5, 1 to 5, and 0. This attribute contributes to the aggregate score and the scores are assigned as:
|
Change Number Incident Text | Flag to indicate if the Change Request number is present in the probable Incident's text fields. This attribute contributes to the aggregate score and the scores are assigned as:
|
Common CIs in Text Flag | Flag to indicate if a CI is present in both the Change and Incident text fields. This attribute contributes to the aggregate score and the scores are assigned as:
|
INC CI in CHG Text | Flag to indicate if the Configuration Item associated with the Incident is present in the probable Change Request's text fields. Note: The entire configuration item name must be present in the Change Request text fields. This attribute contributes to the aggregate score and the scores are assigned as:
|
Common Assignment Group | Flag to indicate if the assignment group of the Change-Incident pair is the same. This attribute contributes to the aggregate score and the scores are assigned as:
|
Common CI | Flag to indicate if the Configuration Item of the Change-Incident pair is the same determined from the Configuration Item field. Note: If the affected CI of the Change is same as the Incident CI, then the flag value is displayed as 'A'. This attribute contributes to the aggregate score and the scores are assigned as:
|
CHG CI in INC Text | Flag to indicate if the CI associated with Change Request is present in the probable Incident's text fields. The entire configuration item name must be present in the Incident text fields. Note: If the affected CI of the Change is mentioned in the Incident text, then the flag value is displayed as 'A'. This attribute contributes to the aggregate score and the scores are assigned as:
|
© 2022 Digital.ai Inc. All rights reserved.