"VDA 6.3 Audit is Coming!" the PM said, his face ashen
That day, I was still explaining the difference between Ppk and Cpk to the new PE intern when the production line PM rushed over, his face paler than a popsicle just pulled from the freezer. He slammed his phone onto the table; the screen displayed an email from a certain German car manufacturer: "VDA 6.3 Process Audit, next Wednesday, time confirmed." I saw it, and my heart immediately sank halfway. Damn, they're just looking for trouble again! Honestly, dealing with Germans, which part is ever easy? For us in semiconductors, connecting with the automotive industry is just this kind of sweet burden.
German Automotive Manufacturers' "Interrogation": What Exactly is VDA 6.3?
Simply put, VDA 6.3 is a "process audit" standard developed by the German Association of the Automotive Industry (VDA). Imagine, the chips you produce will eventually go into a sports car traveling at 200 km/h. If there's even a slight problem with my chip, at best the car breaks down, at worst it's a matter of life and death. Therefore, these Germans naturally raise quality requirements to the highest level.
VDA 6.3 doesn't just look at whether your final product is good; it starts inspecting from the "source." From design, development, supplier management, production, shipment, to customer service, every single step must be laid bare for review. Frankly, this system is more detailed and in-depth than ISO/TS 16949. It gives you a score, with each item weighted; if you fail, it's goodbye. In other words, they want to confirm that your "process" itself is one that can consistently produce high-quality products.
In Reality, How Do They "Nitpick"?
Let me give an example we often encounter. They will break down your process into modules from P2 to P7, and each module has several checkpoints.
For instance, in the "P6 Process Analysis and Production" module, they will ask:
- Is your equipment maintenance plan comprehensive enough? How is your preventive maintenance (PM) schedule executed? Is it ever skipped due to urgent shipments?
- Are process parameters effectively monitored? You claim your etching rate target is 500 nm/min; where are the daily measurement data? Has the Cpk reached 1.33? If it's only 1.08, expect to be scrutinized.
- What is your abnormality handling process? Suppose a wafer suddenly breaks; what is your S.O.P.? Who is responsible? How is it recorded? Is there follow-up?
These questions aren't about "whether you did it," but "how you did it" and "how well it was done." They will go directly to the site, inspect your production records, review your control charts, and even randomly check reports for several batches. Previously, one of our batches had a DPMO skyrocketing to 6210, and it was caught by the auditor on the spot. The scene was so embarrassing I wished I could crawl into a wafer furnace.
The Most Common Pitfall: Disconnect Between Documentation and On-Site Reality
Frankly, the pitfall we most frequently stumble into is "beautiful documentation, but a different reality on-site." Due to time constraints and insufficient manpower, S.O.P.s are often written perfectly, but their actual execution is compromised. Auditors are most skilled at "finding inconsistencies."
Once, our PM report stated that the calibration cycle for all equipment was six months. The auditor then walked directly to a machine, casually picked up the calibration tag of a measuring instrument, and it conspicuously read: "Last Calibration Date: 10 months ago." At that moment, the PM's face was even paler than when the email first arrived. This is what's known as "saying one thing and doing another," a major taboo in front of Germans. They would rather you say, "We are in the process of improving," than "conceal the truth."
Another pitfall is the "authenticity of data." You cannot only present favorable data; marginal or problematic data can better reflect your risk management capabilities. If all your data appears flawless, they will instead suspect you might be hiding something.
One Thing You Can Do Today
Go back and check your SOPs to see where the discrepancies lie between them and actual on-site operations.