FMEA and RCM have mitigated and unmitigated risk assessments for Failure Effects and Recommendations respectively. Each Risk Assessment has related Risk Rank records which is in essence a sub-model. The FMEA loader uses the Risk Assessment service to manage the Risk Assessment and underlying Risk Rank records. Any changes here should be reflected in the Strategy FMEA Mappings Document.
Failure Effect
The Failure Effect also acts as the Risk Assessment record. Review the Failure Effect web service and you will see that the manage operation creates a Risk Ranks collection. There is no need to create an additional Risk Assessment record linked to the Failure Effect.
RCM FMEA Recommendation
The Recommendation will need to have a linked Risk Assessment record if there are mitigated values in the worksheet. The data loader should locate the Risk Assessment record linked to the Recommendation. If one exists, then update it.
If one does not exist, then use the Risk Assessment web service to create it and use the relationship Mitigates Risk [MIR_MITRISK ] to relate it to the Recommendation.
Risk Assessment ID Field
You can use any combination of fields to uniquely identify the record, you are not limited to ID. The ID on the Risk Assessment record has no purpose but the Web Service requires it.
If the service requires an ID, then auto-generate is used with the understanding that it will not be used to do a lookup.
There are two entities and each has two scenarios with regards to the Risk Assessment. None of them require an ID since no attempt is being made to find a risk assessment by ID.
Entity |
Scenario |
Processing Assumptions |
Additional Validation and Integrity Logic |
---|---|---|---|
Failure Effect |
Unmitigated (Create new assessment) |
Since the Failure Effect is the Risk Assessment, there is no need to create a Risk Assessment record.
|
The unmitigated fields on the Failure Effect Record should not be null if the user is loading RCM FMEA recommendations that have a mitigated risk rank. When created through the UI, the recommendation always inherits the unmitigated Risk Assessment from the failure effect and thus we could be creating a situation where there are Mitigated Risks without corresponding Unmitigated Risks. Conversely, a recommendation cannot have a Risk Assessment whose Failure Effect does not have one Risk Assessment, or else an out of sync condition will be created.
|
Failure Effect |
Unmitigated (Update - assessment Exists) |
Update the unmitigated risk fields on the failure effect |
|
RCM FMEA Recommendation |
Mitigated (Create new assessment) |
Check if there is an existing mitigated Risk Assessment linked to the Recommendation. There can only be one. If none exists, then one is created. |
|
RCM FMEA Recommendation |
Mitigated (Update - assessment Exists) |
Check if there is an existing mitigated risk assessment linked to the Failure Effect. If one does exist then update the Risk Assessment. |
Copyright © 2018 General Electric Company. All rights reserved.