Configure Degradation Mechanism Evaluation Validation and Calculation

About DME Validation and Calculation

When you calculate an RBI Criticality Analysis, you can now configure the Probability of Failure (PoF) calculation based on your requirements. These calculations override the baseline calculations.

Using the flexible DME calculation, you can:
  • Add calculations for configured Degradation Mechanism Evaluations (DMEs) or a baseline DME without having to edit rules.
  • Reduce implementation time.
  • Achieve results through Policies.
  • Avoid the need to write rules to perform flexible calculations.
  • Expedite the database upgrade process.
  • Use a combination of configured DMEs and add existing Criticality Calculator DMEs to calculate RBI Analyses.
The following image illustrates the flexible DME calculation framework.

Workflow

This topic describes the sequence of the tasks that you need to perform to configure the flexible DME validation and calculation. Based on the complexity of the configuration, you may need to perform certain tasks outside of the Risk Based Inspection module. When performing such tasks, we recommend that you follow the documentation of the respective modules.

The following image illustrates the workflow of the flexible DME calculation configuration:

Note: To configure flexible DME calculations, it is not mandatory to perform all the tasks mentioned in the workflow. You can perform only the tasks that are specific to your configuration. For example, if you want to configure only the DME Calculation using the baseline DME family, you can perform only the following tasks:
  • Create a flexible calculation policy.
  • Create the calculation configuration in the RBI Application Settings.
If you do not want to use the baseline DME family and want to use a new DME family for the flexible configuration, you must complete the following tasks before configuring the validation and calculation.

Create DME Family and Datasheet

About This Task

If you want to use a new family to configure the flexible DME calculation, you can create a child family under the Criticality Degradation Mech Evaluation family. This is not a mandatory step to configure the flexible DME calculation. However, if you want to use new fields for the calculation that are not part of the baseline family, we recommend that you create a new family and do the configuration. This will make sure that the baseline family is not modified, and you can use the baseline family whenever required.

For more information on creating and configuring a family, refer to the Family Management documentation.

Create Relationship Between RBI Criticality Analysis and DME Family

About This Task

If you have created a family as part of the flexible DME configuration, you must create a relationship definition between the RBI Criticality Analysis family and the new family.

This topic describes the basic steps to create a relationship definition between the RBI Criticality Analysis and the configured DME family. For the detailed documentation on creating relationship definitions, refer to the Family Management documentation.

Procedure

  1. Access the Has RBI Degradation Mechanism Evaluation relationship definition. For information on accessing a relationship family, refer to the Access the Relationship Definition Section topic.
  2. Create a One-to-Many relationship definition between the RBI Criticality Analysis family (Predecessor family) and the new DME family (successor family). For information on creating a relationship definition, refer to the Create a Relationship Definition section.

Create Degradation Mechanisms

About This Task

A Degradation Mechanism is a defined method that affects failure as explained in an RBI Analysis. As part of the flexible DME calculation, you can create your own Degradation Mechanism and use it for DME calculation. For more information on Degradation Mechanisms, refer to the Degradation Mechanisms section.

Procedure

  1. Access the System Codes and Tables Page.
  2. Access the MI_DEGRADATION_MECHANISM_TYPES System Code Table.
    The workspace for the MI DEGRADATION MECHANISMS TYPES (Degradation Mechanism Types) System Code Table appears.
  3. Add the required Degradation Mechanism to the System Code Table.
    The Degradation Mechanism is created.

What To Do Next

Log out of APM and log back in to make the newly created degradation mechanisms available in the Degradation Mechanisms section.

Create a Potential Degradation Mechanism

About This Task

Potential Degradation Mechanisms (PDM) records are used to represent ways in which a component may fail. If you want to link the new Degradation Mechanism to an RBI Component, you must create a new PDM. For more information on PDMs, refer to the About Potential Degradation Mechanisms (PDM) topic.
Important: You cannot link configured PDMs to PRD components.

Procedure

  1. Select , and then navigate to and select Potential Degradation Mechanisms.
    The Record Manager page appears, displaying a new PDM record.
  2. In the General section of the Potential Degradation Mechanism datasheet, enter the following values:
    • In the Degradation Mechanism box, select the configured Degradation Mechanism.
    • In the Degradation Mechanism Description box, select the configured Degradation Mechanism.
    • In the DM Methodology box, select the configured DME family.
    • In the Methodology Type box, select Quantitative.
  3. Select the Consequences tab.
    • In the Value(s) box, select a failure mode.
    • In the Consequence Eval Used box, select the newly configured DME.
  4. Select .
    The Potential Degradation Mechanism is created.

What To Do Next

Log out of APM and log back in to make the newly created potential degradation mechanisms available in the Potential Degradation Mechanisms section.

Configure Data Mapping

About This Task

For each component that will use a configured Degradation Mechanism Evaluation, you must create a new Data Mapping Group record to map the fields from Component to the configured DME family. For information on creating Data Mapping Groups, refer to the Create Data Mapping Group topic.

Create DME Validation Policy

About This Task

As part of the flexible DME calculation, if you do not want to use the baseline validations and want to use new validations, you can create a new validation policy. If you use a configured validation policy, it overrides all the baseline validations. After you create the validation policy, you must configure the policy in the Flexible Calculation Validation section in RBI 580 Flexible Calculation Preferences page.

This topic describes the basic steps on creating a validation policy. For more information on creating, managing, and activating policies, refer to the Policy Designer documentation.

Procedure

  1. Create a policy.
  2. Access the Design workspace of the policy.
  3. Add an Entity node that represents the family that you want to validate. For information on Entity nodes, refer to the Entity Nodes in Policy Designer topic.
  4. As needed, add other nodes required for the validations. For information on the different types of nodes, refer to the Condition, Logic, and Calculation Nodes in Policies section in the Policy Designer documentation.
  5. For each validation, add a Return Value node that has the error message that you want to display to the user when validating the policy. For information on Return Value nodes, refer to the Return Value Nodes in Policy Designer topic.
    Note: Each Return Value node must have a unique name, and the error messages must not contain more than 255 characters.
  6. Save the policy.
    The validation policy is created.

Create DME Calculation Policy

About This Task

As part of the flexible DME calculation configuration, you must create a new calculation policy to perform the calculations. These calculations are used to derive the PoF values. If you use configured calculations, all the baseline calculations are overridden.

This topic describes the basic steps on creating a calculation policy. For more information on creating, managing, and activating policies, refer to the Policy Designer documentation.

Note: As a best practice, save the PoF value to the Degradation Mechanism record as part of the Degradation Mechanism Evaluation calculation.

Procedure

  1. Create a policy.
  2. Access the Design workspace of the policy.
  3. Add an Entity node that represents the family that you want to use in calculations. For information on Entity nodes, refer to the Entity Nodes in Policy Designer topic.
    Note: As a best Practice for the DME Calculation, there should be minimum of two input nodes, one for the DME family and one for the DM family.
  4. As needed, add other nodes required for calculations. For information on the different types of nodes, refer to the Condition, Logic, and Calculation Nodes in Policies section in the Policy Designer documentation.
  5. For each calculation, add an Edit Entity node that contains the details of the output field and its value. For information on Edit Entity nodes, refer to the Edit Entity Nodes in Policy Designer topic.
  6. Save the policy.
    The calculation policy is created.

Configure DME Output Preferences

About This Task

You can configure the output fields for the family where you have configured the flexible calculation. The output fields are not copied to new records when the parent RBI Criticality Analysis is copied, and the values are reset when the analysis is calculated. For more information on configuring the output fields, refer to the Create a Flexible Calculation Output Preference topic.

Create Flexible DME Validation Configuration

If you want to override the baseline validations, you must create a flexible validation record in the RBI 580 Flexible Calculation Preferences section. For more information on creating a flexible validation record, refer to the Create a Flexible Calculation Validation topic.

Before You Begin

Make sure that a policy is created for the validations that you want to perform.

Procedure

Create a flexible validation record with the following configuration:Master section:
  • Analysis Family: RBI Criticality Analysis
  • Action: Degradation Mechanism Evaluation Validation
  • Action Family: Select the family that you want to use for the flexible DME validation.
  • Policy Name: Select the policy that must be used for the validation.
  • Sequence: 1

Detail section:

  • Input Entity Family: Select the family defined in Input Entity of the DME validation policy.
  • Policy Node Name: Enter the name of the input Entity node defined in the validation policy.

Results

The flexible DME validation record is created.

Create Flexible DME Calculation Configuration

If you want to override the baseline DME calculations, you must create a flexible calculation record in the RBI 580 Flexible Calculation Preferences section. For more information on creating a flexible calculation record, refer to the Create a Flexible Calculation Configuration topic.

Before You Begin

Make sure that a policy is created for the calculations that you want to perform.

Procedure

Create a flexible calculation record with the following configuration:

Master section:

  • Analysis Family: RBI Criticality Analysis
  • Action: Degradation Mechanism Evaluation Calculation
  • Action Family: Select the family that you want to use for the flexible DME calculation.
  • Policy Name: Select the policy that must be used for the calculation.
  • Sequence: 1

Detail section:

  • Input Entity Family: Select the family defined in Input Entity of the DME calculation policy.
  • Policy Node Name: Enter the name of the input Entity node defined in the calculation policy.

Configure DME Calculation - Example

About This Task

Suppose you want to create a new DME calculation configuration such that:

  • A new degradation mechanism, Creep, is used for calculation.
  • The output is calculated based on the value in the following input fields:
    • Date in Service: This is a required date field and the date must be greater than 1900-01-01.
  • Based on the values in the input fields, following output field values are updated:
    • Age: The value in this field is calculated based on value in the Date in Service field.
    • Likelihood Category: The value in this field is calculated based on the value in the Age field as described in the following table.
      AgeLikelihood Category
      Less than or equal to 1 Year5
      More than 1 and less than or equal to 3 Years3
      More than 3 and less than or equal to 7 Years2
      More than 7 Years1

Procedure

  1. Create the following DME family (Criticality Configured Creep DME). For information on creating a family, refer to the Create a Family topic.
    1. Create the following fields:
      • Date in Service
      • Age
      • Likelihood Category

      For information on creating family fields, refer to the Create a New Family Field topic.

    2. Create a datasheet in the family. For information on creating a datasheet, refer to the Create a Datasheet topic.
    3. Add the newly created fields to the datasheet in their respective sections as described in the following table.
      Input FieldsOutput Fields
      Date in ServiceAge
      Likelihood Category

      For information on adding fields to a datasheet, refer to the Add Fields to a Datasheet topic.

  2. Create a One-to-Many relationship definition between the RBI Criticality Analysis family (Predecessor family) and the Criticality Configured Creep DME family (successor family). For more information on creating a relationship definition, refer to the Create a Relationship Definition topic.
  3. Create a new Degradation Mechanism (Creep). For information on creating Degradation Mechanisms, refer to the Create Degradation Mechanisms topic.
  4. Create a Potential Degradation Mechanism.
  5. Create a validation policy to perform the validations on the input field. For detailed steps on creating the validation policy, refer to the Create a Sample Validation Policy topic.
  6. Create a calculation policy to update the output fields based on the value in the input field. For detailed steps on creating the calculation policy, refer to the Create a Sample Calculation Policy topic.
  7. Configure the output fields in the Output Preferences section in RBI Application settings. For more information on configuring output preferences, refer to the Configure DME Output Preferences.
  8. Create a flexible validation record in the RBI Application Settings with the following settings:
    • Analysis Family: RBI Criticality Analysis
    • Action: Degradation Mechanism Evaluation Validation
    • Action Family: Criticality Configured Creep DME
    • Policy Name: Select the validation policy created in step 4.

    For more information on validation configuration, refer to the Create a Flexible Calculation Validation topic.

  9. Create a flexible calculation configuration in the RBI Application Settings with the following settings:
    • Analysis Family: RBI Criticality Analysis
    • Action: Degradation Mechanism Evaluation Calculation
    • Action Family: Criticality Configured Creep DME
    • Policy Name: Select the calculation policy created in step 5.

    For more information on calculation configuration, refer to the Create a Flexible Calculation Configuration topic.

Results

The flexible DME calculation is now configured. Now, when you calculate an RBI Criticality Analysis, the following events will occur:
  • The baseline calculations will be overridden.
  • The validation policy will be triggered. If the input field contains null values or invalid values, the calculation will fail, displaying an appropriate validation error message.
  • If there is no validation error, the calculation policy will be triggered.
  • As defined in the calculation policy, the value in the output fields are populated based on the values in the input field.

Create a Sample Validation Policy

About This Task

This topic describes the basic steps that you need to perform to configure validations as part of the example. For detailed information on creating and configuring a policy, refer to the Policy Designer documentation.

Procedure

  1. Create a Policy with the name Configured CE Validation Policy.
  2. Configure an Entity node to represent the Configured Consequence Evaluation family.
  3. Configure an Is Null node and map the value in the Production Loss field of the Configured Consequence Evaluation family.
  4. Set the output value of the Is Null node to -1.


  5. Map the output of the Is Null node to the input of the Equal node.
  6. Configure the Equal node such that:
    • If the value in the Production Loss field is null, a Return Value node is triggered to display an error message indicating that Production Loss is a required field.


    • If the value in the Production Loss field is not null, the output is mapped to the Less Than node.


  7. Configure the Less Than node such that if the value in the Production Loss field is less than zero, a Return Value node displays an error message indicating that the value must not be less than zero.


  8. Save the policy.
    The validation policy is created.


Create a Sample Calculation Policy

This topic describes the general steps that you need to perform to configure the calculations as part of the scenario. For detailed information on creating and configuring a policy, refer to the Policy Designer documentation.

Before You Begin

Create a query to derive the value in the Calculated Age field based on the value in the Date in Service field.
SELECT ABS((DATEDIFF('DD', [MI_MRBIANAL].[MI_CRITANAL_DATE_CRIT_CALC_D], [CRIT_CUST_CREEP_DME].[MI_RBDEMEEV_DATE_IN_SERV_DT]) / 365.4)) "Age"
FROM [MI_MRBIANAL]
JOIN_SUCC [CRIT_CUST_CREEP_DME] ON {MIR_HSRBIDME}
WHERE [MI_MRBIANAL].ENTY_KEY = (? :s :caption='Analysis Key')

For information on creating queries, refer to the About Creating Queries topic.

Procedure

  1. Create a Policy with the name Configured DME Calculation Policy.
  2. Configure an Entity node (DME) to represent the Criticality Configured Creep DME family.
  3. Add a Query node and map the DME Entity node to the Query node.
  4. Configure the Query node to the query created for Age calculation.


    The value in the Age field is configured to be updated based on the value in the Date in Service field.
  5. Add a Less Than or Equal node and configure it such that if the value in the Age field is less than or equal to 1, it triggers an Edit Entity node. Configure the Edit Entity node to update the value in the Likelihood Category as 5.


  6. Similarly, configure the other calculations by adding Less Than or Equal nodes and the corresponding Edit Entity nodes.
  7. Save the policy.
    The calculation policy is created.