1 Organization and Formatting
1.1 General (same as for other B-Sheets; follow this link for easy reference)
1.2 Sheet-Specific — Making it All Fit
The DPFMEA table should be legible at the scaling required to make it fit across the width of the sheet. That is generally not a problem. You can split it vertically (an upper and lower portion, though each with headings) across two pages if needed.
Correct-Content Reminder: The DPFMEA is not related to what you are designing; that will come later and is called your DFMEA (no “P” after the leading “D”). Your DPFMEA is for your Design Project itself, identifying potential failure modes of the project.
2 Content Presentation
- There is no specific Page Input textbox/content to be addressed for this page.
- In the open space on the sheet, insert a graphical rendering of your DPFMEA table (or portion thereof if spread across two sheets) showing RPNs and all information that leads to their calculation. It should be sorted from highest RPN to lowest RPN.
- In the pre-titled Recommended Actions box, present the ways in which the higher RPNs will be reduced (i.e., actions to be taken, meaning countermeasures to be put in place).
- In the template is an example of putting a three side-by-side textboxes within the larger Recommended Actions
- You need not adhere to that format, but it may be useful given the aspect ratio of a typical DPFMEA table being short-by-wide.
- If you work your recommended actions into the DPFMEA table, that is fine as an alternative; delete the Recommended Actions group at the bottom, or use it to expand on what is in the table as that is often brief to the point that someone not immediately associated with the work would not be able to make sense of.
- There is no specific Page Output textbox/content to be addressed for this page.
3 Examples of Great Work
Do a great job and be the first!
Project is a trademark of Microsoft Corporation.
| © 2017, William J. Endres | Updated September 09, 2022 |
