Related Topics: | ||
Causes (typically called failure modes in RCM analysis) are FMEA records that state the specific reason for the failure, preferably found by asking "why" until the root cause is determined. Some of the features for working with causes will depend on the FMEA structure that has been selected for the current project.
The following topics are discussed here:
As discussed in Choosing the FMEA Structure, you can use the FMEA Structure field on the General page of the Project Properties window to choose how you want to display effect and cause records in the FMEA hierarchy. Note the following:
If the FMEA structure is Causes Before Effects or Grouped Effects and Causes, each cause will be associated with a failure record.
If the FMEA structure is Effects Before Causes, the cause will be associated with an effect record.
To add or insert causes into an FMEA, select the failure or effect that the cause will be associated with and choose FMEA > FMEA Records > Causes, then select one of the following options:
Add Cause adds a new record to the bottom of the list.
Insert Cause inserts a new cause above the one that is currently selected.
Import Causes opens the Import Existing Causes window so you can choose to copy one or more of the existing causes into this FMEA. There is no link to the original record(s) (i.e., changes made in one record will not automatically update the other(s)), and you have the choice to import with or without dependents (e.g., associated effects, causes, etc.).
To edit an existing cause in the project, either edit it directly in the worksheet view or use the properties window. To open the properties window, select the cause and choose FMEA > FMEA Records > Causes > Edit Cause or double-click the cause in the hierarchy or filtered view.
If you have copied a cause, there are two options when you choose Home > Clipboard > Paste:
Paste (CTRL+V) pastes the cause(s) and all dependent records (e.g., controls, actions, etc.).
Paste Without Dependents pastes only the cause(s) without any dependent records.
The properties enabled (and their display names) will depend on the interface style for the current project. To view or change these settings, choose Project Management > Configurable Settings > Interface Style.
Note the following:
The Cause Description is required.
The Short Description is a shortened version of the record description that will be used in locations where the full description would be too long to display (e.g., diagrams). If the field is blank when you save the record, the application automatically populates it based on the first 50 characters of the full description.
Use Classification to identify design characteristics that require special manufacturing control (e.g., Critical, Significant, Key Leading, etc.).
The options in the following drop-down lists are based on the occurrence scale that has been assigned in the Project Properties window. The RPN will be calculated automatically if you have defined a Severity rating for the effect, and Occurrence and Detection ratings for the cause.
The Initial Occurrence and Revised Occurrence ratings are numerical values that estimate the probability of occurrence for the potential failure cause.
The Initial Detection and Revised Detection ratings are numerical values that estimate the probability that the problem will be detected before it reaches the customer or end user.
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 RBI and BlockSim or perform RCM cost/availability calculations.
© 1992-2015. ReliaSoft Corporation. ALL RIGHTS RESERVED.