Configure Degradation Mechanism Roll-up
About Degradation Mechsnism Roll-up
After the Consequence of Failure (CoF) values are calculated, these values are rolled up to the Degradation Mechanism records. The rolled-up values are used during the analysis roll-up to determine the risk value of the component. By default, the values are rolled up based on the logic defined in the baseline rules. However, you can create a policy for the roll-up logic and configure it to be executed during the analysis calculation. When you use the policy for DM roll-up, it overrides the baseline rules.
Workflow
This topic describes the sequence of the tasks that you must perform to configure the DM roll-up 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.
Create a DM Roll-up Policy
About This Task
This topic describes the basic steps on creating a DM roll-up policy. For more information on creating, managing, and activating policies, refer to the Policy Designer documentation.
Procedure
Configure DM Roll-up 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 DM Roll-up Configuration
If you want to override the baseline DM roll-up logic, you must create a flexible DM roll-up record in the RBI 580 Flexible Calculation Preferences section. For more information on creating a flexible roll-up configuration record, refer to the Create a Flexible Calculation Configuration topic.
Before You Begin
Make sure that a policy is created for the logic that you want to perform to roll up the CoF values to DM records.
Procedure
- Analysis Family: RBI Criticality Analysis
- Action: Degradation Mechanism Roll-Up
- Action Family: Select the family that you want to use for the flexible DM roll-up.
- Policy Name: Select the policy that must be used for the roll-up.
- Sequence: 1
Detail section:
- Input Entity Family: Select the family defined in Input Entity of the DM roll-up policy.
- Policy Node Name: Enter the name of the input Entity node defined in the DM roll-up policy.
Results
Configure DM Roll-up - Example
About This Task
Field in Degradation Mechanism | Roll-up logic based on CE values |
---|---|
SHE CoF | Highest consequence value among Flammable, Toxic, and Environmental. |
Financial CoF | Highest consequence value between Product Leak and Lost Production Category. |
Procedure
Results
- The baseline degradation mechanism roll-up will be overridden.
- The configured DM roll-up policy is triggered. As defined in the policy, the CoF values are rolled up to the Degradation Mechanism records.
Create Sample DM Roll-up Policy
This topic describes the general steps that you must perform to configure the DM roll-up policy as part of this scenario. For the detailed information on creating and configuring a policy, refer to the Policy Designer documentation.
Before You Begin
Create the following queries:
- Consequence Evaluation SHE COF Roll Up Query: To roll up the highest consequence value among Flammable, Toxic, and Environmental.
- Consequence Evaluation FIN COF Roll Up Query: To get the highest consequence between Product Leak and Lost Production Category.
The following query is an example for the Consequence Evaluation SHE COF Roll Up Query.
SELECT Min(SHECOF."SHE-COF") "SHECOF"
FROM (SELECT [MI_CRCOEVAL].[MI_CRCOEVAL_ENV_CONS_CAT_C] "SHE-COF"
FROM [MI_PTDEMECH]
JOIN [MI_RBDEMECH]
JOIN_PRED [MI_MRBIANAL]
JOIN_SUCC [MI_CRCOEVAL] ON {MIR_HSCONEVA} ON {MIR_HSDEGMEC} ON [MI_PTDEMECH].[MI_PTDEMECH_DEG_MECH_C] = [MI_RBDEMECH].[MI_DEGR_MECH_DEG_MECH_C]
WHERE ([MI_CRCOEVAL].[MI_RCONEVAL_CONS_C] IN ([MI_PTDEMECH].[MI_PTDEMECH_CONSE_1_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_2_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_3_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_4_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_5_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_6_C]) AND [MI_RBDEMECH].ENTY_KEY = (? :n :caption='DM Entity' :id=DMEntity))
UNION
SELECT [MI_CRCOEVAL].[MI_CRCOEVAL_FLAM_CONS_CAT_C] "SHE-COF"
FROM [MI_PTDEMECH]
JOIN [MI_RBDEMECH]
JOIN_PRED [MI_MRBIANAL]
JOIN_SUCC [MI_CRCOEVAL] ON {MIR_HSCONEVA} ON {MIR_HSDEGMEC} ON [MI_PTDEMECH].[MI_PTDEMECH_DEG_MECH_C] = [MI_RBDEMECH].[MI_DEGR_MECH_DEG_MECH_C]
WHERE ([MI_CRCOEVAL].[MI_RCONEVAL_CONS_C] IN ([MI_PTDEMECH].[MI_PTDEMECH_CONSE_1_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_2_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_3_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_4_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_5_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_6_C]) AND [MI_RBDEMECH].ENTY_KEY = (? :n :caption='DM Entity' :id=DMEntity))
UNION
SELECT [MI_CRCOEVAL].[MI_CRCOEVAL_TOX_CONS_CAT_C] "SHE-COF"
FROM [MI_PTDEMECH]
JOIN [MI_RBDEMECH]
JOIN_PRED [MI_MRBIANAL]
JOIN_SUCC [MI_CRCOEVAL] ON {MIR_HSCONEVA} ON {MIR_HSDEGMEC} ON [MI_PTDEMECH].[MI_PTDEMECH_DEG_MECH_C] = [MI_RBDEMECH].[MI_DEGR_MECH_DEG_MECH_C]
WHERE ([MI_CRCOEVAL].[MI_RCONEVAL_CONS_C] IN ([MI_PTDEMECH].[MI_PTDEMECH_CONSE_1_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_2_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_3_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_4_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_5_C], [MI_PTDEMECH].[MI_PTDEMECH_CONSE_6_C]) AND [MI_RBDEMECH].ENTY_KEY = (? :n :caption='DM Entity' :id=DMEntity))) SHECOF