| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| articles:golf [2022/03/07 21:08] – ["Risk Management System" instead of "Corrective Action System"?] rrandall | articles:golf [2022/03/07 21:13] – [Conclusion] rrandall |
|---|
| * New/Updated equipment (e.g., with improved accuracy, precision, reliability) | * New/Updated equipment (e.g., with improved accuracy, precision, reliability) |
| * Change the process (e.g., incorporating new technologies) | * Change the process (e.g., incorporating new technologies) |
| * Decreasing calibration intervals of M&TE (to reduce the risk of measurement errors) | * Increasing measurement accuracy ratios of M&TE to product tolerances (to reduce the risk of measurement errors) |
| * Improving “detection” of nonconformities through adding Checks/Reviews | * Improving “detection” of nonconformities through adding Checks/Reviews (e.g., by humans of Automated Optical Inspection) |
| * Obtaining a “waiver” from the customer to change/modify or eliminate a requirement | * Obtaining a “waiver” from the customer to change/modify or eliminate a requirement |
| |
| How much more would your quality improve if you replaced your "corrective action" system with a much more effective and encompassing "risk management" system? | How much more would your quality improve if you replaced your "corrective action" system with a much more effective and encompassing "risk management" system? |
| |
| IF a nonconformity is due to a “Common Cause” variation, then "controls" could be put in place to "__mitigate__" the risk of the nonconformity recurring. Alternatively, IF a nonconformity is determined due to a “Special Cause” variation, then the process can be changed to "__eliminate__" the cause (or risk) of the nonconformity recurring. | IF a nonconformity is due to a “Common Cause” variation, then "controls" could be put in place to "__mitigate__" the risk of the nonconformity recurring. Alternatively, IF a nonconformity is determined due to an “Assignable Cause” variation, then the process can be changed to "__eliminate__" the cause (or risk) of the nonconformity recurring. |
| {{ :articles:fmea-infographic.jpeg?direct&250|}} | {{ :articles:fmea-infographic.jpeg?direct&250|}} |
| |
| Such a system would keep all of the problem solving and root cause analysis tools (e.g., the 5 Whys, Fishbone Charts, Fault Tree Analysis), while using the "//root cause theories//" as input to a [[https://asq.org/quality-resources/fmea|"Failure Mode and Effects Analysis" (FMEA)]]... or PFMEA ("Process Failure Mode and Effects Analysis"). | Such a system would keep all of the problem solving and root cause analysis tools (e.g., the 5 Whys, Fishbone Charts, Fault Tree Analysis, Apollo Root Cause Analysis), while using the "//root cause theories//" as input to a [[https://asq.org/quality-resources/fmea|"Failure Mode and Effects Analysis" (FMEA)]]... or PFMEA ("Process Failure Mode and Effects Analysis"). |
| |
| Upon completing a PFMEA, one quickly realizes just how few "true" corrective actions are actually possible. And that by shifting the mindset to "risk management", rather than being obsessed with "risk elimination" (aka "Corrective Action"), significant quality improvements can finally be realized. | Upon completing a PFMEA, one quickly realizes just how few "true" corrective actions are actually possible. And that by shifting the mindset to "risk management", rather than being obsessed with "risk elimination" (aka "Corrective Action"), significant quality improvements can finally be realized. |
