Related Topics: | ||
To add a failure (typically called a functional failure in RCM analysis) to the FMEA, select the function with which it is associated and choose FMEA > FMEA Records > Failures.
To insert a new failure above the selected failure, choose FMEA > FMEA Records > Failures > Insert Failure. The new failure will be associated with the same function as the existing failure.
To edit an existing failure in the project, either edit it directly in the worksheet view or use the properties window. To open the properties window, select the failure and choose FMEA > FMEA Records > Failures > Edit Failure or double-click the failure in the hierarchy or filtered view.
Note: The fields that are enabled in the interface and the options available in configurable drop-down lists will depend on the interface style settings that have been defined for the current project. You can choose Project > Management > Configurable Settings > Interface Style to open the Edit Interface Style (This Project) window and change the settings for the current project.
When adding a failure, in addition to the options common to all FMEA record properties windows, you will need to define the failure properties.
In the Failure area the following fields may be available:
Failure Description: The ways the item may fail to perform each intended function within the specified limits. This may include total failure to perform the function, poor performance of the function, performing an unintended function, etc.
Short Description: A shortened (50 character maximum) version of the record description that appears in diagrams where the full description would be too long to display. If you do not enter text in this field, the software automatically populates the field when you save the record (based on the first 50 characters of the record description). Note that the description fields are not automatically updated if you later change one of them so you must be sure to make the same changes to both fields if necessary.
Mechanism of Failure: The physical, chemical, electrical, thermal or other process that results in the failure mode.
Mission Phase/Operational Mode: The mission phase (or operational mode) in which the failure mode occurs. For example, in an airplane, does the failure occur during takeoff, while flying or during landing?
Undetectable: Indicates that the failure mode is not detectable during normal operation.
Dormancy Period: If the failure is undetectable, the length of time that the failure will be hidden.
The following fields will be available if they are enabled on the FMEA > Criticality page of the project's interface style. RCM++ will not fully validate these factors until you perform the criticality analysis.
Failure Probability: Allows you to rate the likelihood that the failure will occur. The options in this drop-down list are based on the failure probability scale that has been assigned in the Project Properties window. This is for qualitative criticality analysis.
Severity Class: Allows you to rate the severity for the failure. The options in this drop-down list are based on the severity class scale that has been assigned in the Project Properties window. This is for qualitative criticality analysis, and also is required to generate a criticality matrix for the quantitative analysis.
Tip: If you need to define the reliability/maintainability characteristics for this record, use the FMRA tab. These characteristics will be applicable if you wish to perform criticality analysis, use the FMEA occurrence ratings to calculate a preliminary baseline estimate of the system reliability, share system configuration/reliability data between RCM++ and BlockSim or perform RCM cost/availability calculations.
© 1992-2013. ReliaSoft Corporation. ALL RIGHTS RESERVED.