That Day, The RCA Report Couldn't Pass No Matter How It Was Written
I remember once, we were running a new product in our factory. A customer audit revealed a dreadful problem on the production line. At that time, the auditor walked over, grim-faced, pointed to one of our wafers, and said, "Your yield, with a Cpk value of only 1.08, do you know what that means? This is an absolute disaster!" The entire atmosphere instantly froze. I looked at my team lead; his face turned green, as this was already the second time they had been caught with lax process control. Even worse, he was singled out by the auditor on the spot, who stated that this issue would be classified as a "Major Non-conformance," requiring improvement within a specified deadline, or shipments would be halted. It was then that I truly understood the pressure associated with a "Major Non-conformance."
Does Filling Out Audit Reports Really Make a Difference?
To be honest, when I first joined the semiconductor factory and saw "non-conformances" in audit reports, I always thought, "Isn't it just a matter of writing an improvement plan and submitting it?" I was young then, and I felt these were just administrative tasks, unrelated to actual production. But later, I discovered that non-conformances are actually divided into two types: "Major Non-conformance" and "Minor Non-conformance." The severity of these two types, simply put, is the difference between "whether your product can be shipped or not."
In short, a "Major Non-conformance" generally refers to serious issues that directly impact product quality, reliability, or could even lead to customer complaints, returns, or legal non-compliance. For example, the Cpk of 1.08 we were caught with that day was due to uncontrolled process parameters, leading to excessive variation in the product's Critical-to-Quality (CTQ) characteristics, directly affecting customer requirements. Think about it: if your product's DPMO soars to 6210, the customer might just say goodbye.
Conversely, a "Minor Non-conformance" refers to deficiencies that, while not meeting standards, have less impact on product quality or pose lower systemic risks. For instance, if your document management process is a bit disorganized, some SOP versions haven't been updated to the latest, or a few signatures are missing from training records, these are considered minor non-conformances. Although they still require correction, they usually won't immediately halt your production line.
How to Actually Determine This to Avoid Being Nailed?
So, how do auditors on site determine if a problem is "major" or "minor"? Frankly, there's no absolute formula, but they usually consider several angles:
1. Impact on Product Quality: Will the problem directly lead to product functional anomalies, failures, or safety concerns? If so, it's likely a major one. For example, our Cpk of 1.08 meant product parameters were far outside specifications, so it was naturally major.
2. Regulatory Requirements or Customer Contracts: Does it violate government regulations, industry standards, or requirements explicitly stated in customer contracts? If violated, it will usually be considered major.
3. Systemic Risk: Is this issue an isolated incident, or does it reflect a defect in the entire management system? If it's the latter, it's very likely to be escalated to major. For example, if your equipment calibration process is completely non-existent, rather than just one piece of equipment not being calibrated, that would be a major problem.
4. Recurrence: Has the same problem been flagged multiple times without improvement? If you've been caught with high DPMO before, and the next audit shows 6210 again, it will definitely be treated as major.
So the key is, when an auditor raises an issue, don't immediately refute or shirk responsibility. Instead, first assess the potential scope and severity of the problem.
The Most Common Pitfall: Neglecting Minor Issues
The most common pitfall I've seen is when some engineers think, "Oh, this is just a minor non-conformance; we can fix it slowly." What happens then? At the next audit, this "minor" issue, because it wasn't thoroughly addressed, is escalated by the auditor into a "Major Non-conformance." This is because the auditor will conclude that you haven't given enough importance to the quality system, and might even question the execution capability of your entire team.
I recall one instance when our factory's document control was flagged for having several outdated SOPs still in use on the production line, which was initially classified as minor. Our team, thinking it wasn't serious, waited half a year before initiating a comprehensive review. When the next customer audit came, the auditor directly asked, "How was that document issue from last time handled?" Then, they randomly sampled a few documents and found remaining outdated versions. On the spot, that issue was escalated to a "Major Non-conformance," and an improvement notice was issued, impacting the month's shipping schedule. That lesson taught us that even minor issues indicate system vulnerabilities that must be truly resolved. Frankly, what auditors want to see is your attitude towards quality, not just a report.
One Thing You Can Do Today
Go back and look at your audit reports, identify any issues that were previously classified as "Minor Non-conformance," and resolve them thoroughly today.