Locked lesson.
About this lesson
Exercise files
Download this lesson’s related exercise files.
DFMEA Failure Modes.docx60.9 KB DFMEA Failure Modes Example Spreadsheet.xlsx
12.1 KB DFMEA Failure Modes - Solution.docx
145.1 KB
Quick reference
DFMEA Failure Modes
Once the functions for the system or device that is being analyzed have been determined, the failures of each of those functions can be identified. The functions and failures then initiate the Design FMEA form.
When to use
Every Design FMEA requires the failure modes for the functions to be identified in order to be scored. Capturing these failure modes is Step 4 in the Design FMEA process.
Instructions
Using the functions that were identified in the block diagram, product specification and interface matrix, brainstorm with the FMEA team the failure modes associated with each function. Use the failure types discussed in previous lessons to assist in identifying failures. Generally, the intermittent failure and over-processing failure are not useful for the Design FMEA. There is not enough history with the new product to identify intermittent problems and the over-processing failure is focused on the work done in the operational processes.
Every function will have at least one failure and many will have multiple failure modes. Each failure mode may manifest itself in one or more failure types. For instance, a failure mode may lead to a complete failure, a partial failure, or degraded performance depending upon the magnitude of the actual failure involved. The Function-Failure matrix is an excellent tool to help brainstorm failures. Your organization may have other tools and techniques or you may just record the failures that are identified in a brainstorming session. I have found this technique helps to both stimulate the process and document the comments.
With your list of functions and failures, you are now ready to initiate the Design FMEA form. These items make up the first two columns of the form. If a function has multiple failure modes, each failure mode is a separate line on the FMEA form. Every function should have at least one failure mode associated with it. However, there is no maximum number of failure modes, you should record all that are relevant to that function.
Hints & tips
- Don’t jump to effects yet; just record the function and how that function could fail to operate as expected. The next step will discuss effects.
- Don’t combine different failure modes onto one line; each failure mode will likely have a different score and should be analyzed by itself.
- If the same failure mode shows up with multiple functions, you can either combine all those into one failure mode or continue to treat them separately. A caution when combining is that you need to be sure that you consider the impact to all the functions when evaluating severity and detection. The absence of some functions may be much more severe than others. For that reason, I often will keep them both, each associated with the different functions.
- The Function-Failure matrix is a tool to help brainstorming. Don’t get hung up in the format. At the end of the analysis what we are keeping and documenting is the Design FMEA, not the Function-Failure matrix.
Lesson notes are only available for subscribers.
PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.