This documentation applies to the 8.1 version of Change Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring derived risk factors

You can configure any of the following derived risk factors:

  • CI priority (highest priority of all CIs that are related to the change request)
  • CI impact
  • Performance rating of support group
  • Performance rating of change manager
  • Performance rating of change coordinator
  • Performance rating of change implementer
  • Performance rating of operational CTI
  • Performance rating of the support group
  • Change impact
  • Change priority

    Tip

    To see examples of configured derived risk factors, search the Risk Factors Configuration form for records in which the Company field is set to - Global -.

Before you begin

Configure risk factor questions, as described in Configuring risk factor questions.

To configure derived risk factors

  1. Click the Derived Factors tab, and then click Add.
  2. In the Risk Factor Type field on the Derived Risk Factors Template form, select a type from the following choices:

    Risk factor type

    Description

    Risk Object

    Derives risk from the related CI with the highest priority. This rating is derived from the related CIs, and not from values specified on the change.

    Performance Indicator

    Derives risk based on performance of a manager or a group. The stored performance rating of specific entities is recorded. A performance indicator risk factor refers to ratings that are directly related to values specified on the change.


    For more information, see Review and Authorize stage - Risk and impact analysis.

  3. In the Risk Weight field, select the percentage weight.
    Select a risk weight that indicates how significant the risk is to the change request. These values are defined in the CHG:ChangeRiskRanges form. You must have the AR Administrator role or the Infrastructure Change Config permission to modify these values.
  4. In the Field Name field, select the field on the Infrastructure Change form from which the risk factor is derived.
    Depending on the risk factor type, select one of the following fields.

    Risk factor type

    Fields from the Change form

    Risk Object

    The following fields are now available for selection:

    • CI Priority
    • CI Impact
    • Change Impact
    • Change Priority

    Performance Indicator

    • Change Coordinator
    • Change Implementer
    • Change Manager
    • Operational CTI
    • Support Group Name


    This information is calculated based on the historical performance of the changes that use these values.
    For example, if you select Operational CTI, a historical record is kept separately for each CTI used. If the CTI was Request > Virtual Machine > Provision, a performance history would be stored for it for each of the closed changes that had an operational CTI of Request > Virtual Machine > Provision.

  5. If you selected Performance Indicator, select Performance Rating from the Rating Field Name field.
  6. Click Save.

    Note

    If you are modifying an existing risk factor by adding questions or derived risk factors, clicking Save is optional.

Example of derived risk factor based on CI Impact and CI Priority values

If you relate a CI to a change request and change the value of the Impact or Priority fields on the CI form in Remedy Asset Management, the derived risk factor of the change request changes accordingly. The following is the relation between the values of the CI Impact and CI Priority with the risk value of the related change request:

CI Impact field valuesRisk value of the change request
1-Extensive/Widespread5
2-Significant/Large4
3-Moderate/Limited3
4-Minor/Localized2
CI Priority field valuesRisk value of the change request
PRIORITY_51
PRIORITY_42
PRIORITY_33
PRIORITY_24
PRIORITY_15

Follow the steps given below to calculate the derived risk factor of a change request that is related to a CI:

  1. Go to the CI form and create a CI by selecting the following values:
    • Impact field—1-Extensive/Widespread
    • Priority field—PRIORITY_5
    • Service Type field—Business Service
  2. From the Risk Factor Configuration form, go to Derived Factors tab > Derived Risk Factor Template.
  3. Select the following values:
    • Risk Factor Type—Risk Object
    • Risk Weight—100%
    • Field Name—CI Impact
  4. Create a new change request and relate this created CI. 
  5. Save the change request.
    The Risk Level value is automatically calculated as 5.

For information about the formula used for calculations, see Sample rating calculation.

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

Comments

  1. Ivan Pirishanchin

    Hi,

    Is there more information on how each derived factor is mapped to Risk Level values? For instance, for the CI Impact and CI Priority factors we have very different values than the ones for Risk Level. What is the formula used?

    Also, I think that the section:
    "This information is calculated based on the historical performance of the changes that use these values.
    For example, if you select Operational CTI, a historical record is kept separately for each CTI used. If the CTI was Request > Virtual Machine > Provision, a performance history would be stored for it for each of the closed changes that had an operational CTI of Request > Virtual Machine > Provision."

    is only valid for Performance Indicator type, and not for Risk Object. Could you check and confirm, please?

    Thanks!

    Dec 06, 2016 10:29
    1. Mokshada Shivarekar

      Hi,

      I will work with the SME and get back to you.

      Thanks,

      Mokshada

      Jan 04, 2017 11:23
  2. Surabhee Kulkarni

    Hello,

    I have updated the topic with an example of derived risk factor based on CI Impact and CI Priority values.

    Also, the following section is valid only for the performance indicator type. Based on the performance indicator, the derived factors are calculated.

    "This information is calculated based on the historical performance of the changes that use these values. For example, if you select Operational CTI, a historical record is kept separately for each CTI used. If the CTI was Request > Virtual Machine > Provision, a performance history would be stored for it for each of the closed changes that had an operational CTI of Request > Virtual Machine > Provision."

    Thanks and regards,
    Surabhee

    Jul 01, 2020 07:35