This documentation supports the 20.02 version of Remedy Change Management.

To view an earlier version, select the version from the Product version menu.

Example of risk factor configuration

This example explains the risk factor configuration data for the Calbro Systems company in order to walk through how the system sets the risk level for a change request. When you create your own risk factor configuration data, note that this is probably an iterative process, for you to get the desired risk levels for your given change use cases.

In this example, we have configured the following questions with the related risk weights and values within the Risk Factors Configuration form. This example explains how the system uses the data to calculate the risk level.

Risk Factor

Risk Weight

Risk Values

Will the change require a scheduled down time?

60%

Yes – Risk Value = 5
No – Risk Value = 1

Will the change affect more than one CI?

100%

Yes – Risk Value = 5
No – Risk Value = 1

Can the change be rolled back easily?

100%

Yes – Risk Value = 1
No – Risk Value = 5

Is this a standard change that has been successfully done before?

60%

Yes – Risk Value = 1
No – Risk Value = 5
Unknown – Risk Value = 3

In addition, we have also configured the following derived risk factors:

Derived Risk Factor

Field Name

Risk Weight

Maximum priority of Configuration Items

CI Priority

100%

Performance rating of change coordinator

Change Coordinator

60%

Risk calculation based on change impact

Change Impact

100%

When we create a new change request where the Change Location Company is Calbro Systems, the system selects the above risk factors configuration and applies the risk questions and the derived risk factors to calculate the risk level as shown below.

  1. While creating the change request, set the value of Change Impact to 3-Moderate/Limited as this is used by the Risk Calculation based on Change Impact derived risk factor.

  2. Relate the CI that the change request is changing. The following CI Priority value is PRIORITY_4 as defined in CMDB as this is used by the Maximum Priority of Configuration Items derived risk factor.

    Important

    If there is more than one related CI, the system uses the priority value from the CI with the highest priority value.

     

  3. Answer the risk factor questions as follows:


    After you save the change request, the Risk Level automatically sets to Risk Level 3 as shown below:

To see how Risk Level 3 was determined, plug in each risk factor risk value and risk weight into the risk level equation. Note that there are four risk factor questions and three derived risk factors.

Risk Factor Value

Weight Value

Risk Factor values come from

Question: Will the change require a scheduled down time?
Answer: Yes

Question: Will the change affect more than one CI?
Answer: No

Question: Can the change be rolled back easily?
Answer: No

Question: Is this a standard change that has been successfully done before?
Answer: Yes

Derived Risk Factor: Maximum priority of Configuration Items
CI Priority = PRIORITY_4
The system derives the risk level by taking the equivalent enumerated value for PRIORITY_4, which is 1 as seen from Developer Studio.

The system then runs the CI Priority value through the calculations to get the final Risk Level equivalent. It then sets CI Priority = CI Priority + 1, so CI Priority = 2 and then sets CI Priority = (5 - CI Priority) +1, so CI Priority = (5-2) +1 = 4, which becomes the risk level equivalent.

Derived Risk Factor: Performance rating of the change coordinator.

The risk value is determined by the data that has been calculated over time within the CHG:Risk Derived Factors form. For the change coordinator. there is only one previous rating.

The risk value is the average performance rating over time.

Derived Risk Factor: Risk calculation based on change impact.
Change Impact = 3-Moderate/Limited

The system derives the risk level by taking the equivalent enumerated value for 3-Moderate/Limited, which is 3000 as seen from Developer Studio.

The system then runs the Change Impact value through the following calculations to get the final risk level equivalent.

It the sets Change Impact = Change Impact / 1000 = 3 and then sets Change Impact = (4 - Change Impact) +1, so Change Impact = (4-3) +1 = 2 which becomes the risk level equivalent.

The following equation is with the above table values:

The equation returns the value as 3. When comparing this value to the data in the CHG:ChangeRiskRanges form, the range falls between 2.000001 and 3.000000, which equates to a Risk Level to 3.

For additional information about risks, see the Risk Assessment in BMC Remedy Change Management article on BMC Communities. Also, seeMultiExcerpt named config_risk was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro.

Was this page helpful? Yes No Submitting... Thank you

Comments