跳至主要内容

The Relationship between Mistake-Proofing and FMEA

 In modern manufacturing, mistake-proofing (or poka-yoke) is widely adopted across various industries as a critical method for ensuring product quality. However, many companies commonly encounter a significant issue during its implementation: the development of mistake-proofing measures often lacks systematic risk assessment and appears to be based on intuition or ad hoc decisions, resulting in suboptimal effectiveness.


A typical scenario is that a company maintains a detailed mistake-proofing checklist, which not only includes specific information about each characteristic but also clearly outlines the underlying principles, methods, and verification requirements for each mistake-proofing measure—and these measures are regularly validated. Yet, when tracing back to the FMEA (Failure Mode and Effects Analysis) documentation, one finds that the corresponding mistake-proofing information is missing. This raises an important question: why were certain characteristics selected for mistake-proofing while others were excluded?

Clearly, teams do not arbitrarily decide the scope of mistake-proofing; their selections are undoubtedly informed by considerations of risk and lessons learned from past experience. Unfortunately, this risk assessment process has not been formally documented, leading to gaps in the FMEA records. As a standardized risk-prevention tool, the core value of FMEA lies in its systematic analytical process, which identifies and prioritizes critical risks that could affect product quality or safety. Therefore, the aforementioned phenomenon reflects a deficiency in how companies execute FMEA.

IATF 16949:2016 Clause 10.2.4 – Error-Proofing states the following:

10.2.4 Error-Proofing The organization shall have a documented process to determine the appropriate error-proofing methods to be used. Details of the methods employed shall be documented within process risk analyses (e.g., PFMEA), and the testing frequency shall be specified in the control plan.

The process shall include tests for error-proofing device failures or simulated failures. Records shall be maintained. If challenge parts are used, they shall, where feasible, be identified, controlled, verified, and calibrated. A reaction plan shall be established for error-proofing device failures.

According to IATF 16949, detailed information on error-proofing methods must be documented within process risk analyses, with PFMEA being a typical tool for this purpose.

The standard also requires that the determination of error-proofing methods be governed by a documented procedure. This involves systematically planning the identification of error-proofing targets, the development and deployment of error-proofing methods, and verification activities to ensure the effectiveness of error-proofing and ultimately control risk.

Therefore, from the perspective of the IATF 16949 standard, we need to derive the error-proofing checklist from the prevention and detection controls in the PFMEA and reflect these measures as control methods in the control plan.

The IATF 16949 standard emphasizes that error-proofing verification must be purposeful and grounded in lessons learned from past experience. Error-proofing devices themselves can also be sources of risk. The author has personally encountered an awkward situation where, after confidently assuring a customer about the reliability of an error-proofing system one moment, the very next moment the customer conducted an on-site verification—and the error-proofing device failed to respond to the challenge part at all. Determining when to perform verification is itself a science.

If challenge parts are used, they must also be calibrated.

Since error-proofing devices can fail, should we conduct an FMEA analysis on them? Whether or not to perform an FMEA depends on how we define the scope of the FMEA. Generally speaking, it is not necessary to perform an FMEA specifically on error-proofing devices. However, if deemed essential, a Machine FMEA (MFMEA)—a specialized application of the FMEA methodology—can be used.

Deep integration between FMEA and error-proofing is key to achieving continuous improvement in product quality. Through FMEA, organizations can systematically identify potential risks and proactively develop effective error-proofing measures. During mass production, FMEA and error-proofing can reinforce each other, jointly safeguarding manufacturing quality.


 

评论

此博客中的热门博文

How Quality Engineers Can Build Professional Influence

The influence of a Quality Engineer (QE) within a team is critical for the effective implementation of inspection, gatekeeping, and oversight of improvements. This is not merely a matter of technical competence, but rather a comprehensive reflection of leadership, communication skills, and interpersonal relationship management. Below are specific strategies for how a Quality Engineer can build personal influence: 1. Establish Professional Competence and Reliability (Credibility & Expertise)   ● Become a technical expert:     ○ Deeply understand products and processes: Go beyond knowing quality standards —gain thorough insight into the technical details, architecture, implementation approaches, and the entire development lifecycle of the products your team builds. When you can identify potential risks or design flaws at the code level, your input carries far more weight than generic statements like “quality is important.”     ○ Master tools an...

Understand the "Unwritten Rules" of R@R vs. 2TP

  They’re both "final exams" before mass production, so why do some suppliers breeze through R@R only to be forced into overnight rework by 2TP? If you work in automotive parts, two abbreviations inspire equal parts love and dread: R@R and 2TP . Newcomers often mix them up, thinking, "Isn’t it just running the production line before mass production? How different can it be?" Very different. I’ve seen too many suppliers apply their American R@R mindset to a German 2TP audit, only to get schooled by the auditor on the spot. Let’s break down exactly how these two systems work. 01 The Definition: What is R@R? Let’s correct a common misconception: R@R stands for Run @ Rate , not Ready for Ramp-up. While the ultimate goal is "production readiness," the name itself reveals the core logic—running at the required pace. American OEMs ( Ford , GM , etc.) want to verify your production claims. If you say your capacity is fine, prove it by running at the actual produ...