Technical Cleanliness: Build a QMS Control Plan
A component can pass visual inspection and still fail technical cleanliness requirements, because particles that threaten its performance may be invisible. One hard metal chip inside a fuel injector or brake valve can trigger a field failure months after shipment, and by then the cause is slow and expensive to trace.
That risk explains why technical cleanliness belongs inside your quality management system (QMS). A washing procedure alone does not protect your customers. Manufacturers need defined technical cleanliness requirements, reliable inspection, production controls, and documented follow-up.
This guide walks you through a technical cleanliness QMS control plan. You will see how ISO 16232 and VDA 19 guide technical cleanliness inspection and contamination prevention, how to map risks and control suppliers, and what to do when a test fails. Finally, you will see how quality software keeps records and corrective actions connected.
What Is Technical Cleanliness in Manufacturing?
Technical cleanliness describes how free a component is from particulate contamination that can harm its function. Labs measure it through residual dirt: the weight, number, size, and composition of particles on functionally relevant surfaces. Quality teams also call it component cleanliness or particulate cleanliness.
Common Particulate Contaminants
Solid contaminants threaten technical cleanliness from many sources. Machining leaves metal chips, burrs, and swarf, while wipes, gloves, and clothing shed fibers. Dust drifts in from the shop floor, and abrasive grains, rubber fragments, and casting sand add to the mix.
Each type behaves differently. A fiber can block a narrow orifice, and a hard metal particle can score a bearing surface or jam a valve.
Visible Dirt Versus Harmful Particles
Visible dirt and harmful particles are not the same thing. A part can look spotless while carrying hundreds of particles too small to see, and another part can show obvious dust that never affects function.
Function decides the risk. Size, hardness, shape, and location on the component all matter, and specialists use the term “killer particles” for the most damaging contaminants.
Why Contamination Matters
Precision components such as injectors, pumps, and bearings leave almost no clearance for debris. Automotive fluid systems carry loose particles straight to the valves, filters, and seals downstream. Sensitive assemblies, including control units and electric-vehicle power electronics, face a different threat, because conductive particles can bridge contacts and cause short circuits.
Technical cleanliness failures can also surface late, in the field, where warranty costs run highest. That delay makes prevention and early detection far cheaper than a recall.
What ISO 16232 Says About Scope
ISO 16232 sets requirements for applying and documenting methods that determine particulate contamination on functionally relevant road vehicle components and systems. The standard does not define cleanliness limit values for specific parts. Required cleanliness depends on the component, the system around it, and the intended application.
That point shapes your entire technical cleanliness control plan. You cannot copy a limit from a standard, so you must derive it from your own component and its use.
How ISO 16232 and VDA 19 Guide Technical Cleanliness Control
Two document families dominate technical cleanliness work: ISO 16232 and the VDA 19 series. They overlap in places, yet they serve different needs. Understanding both helps you write stronger specifications and audit your own controls.
ISO 16232 for Component Cleanliness Inspection
ISO 16232:2018 is the current published international edition, and it consolidated the earlier ten-part series from 2007. The standard supports initial inspection and evaluation, checks of incoming and outgoing components, and quality control of cleanliness-relevant processes.
Inspection follows a consistent chain. First, the lab extracts particles from the component, for example by rinsing or ultrasonic agitation. Next, it collects those particles on an analysis filter, and analysts then count, size, and classify them. Many labs add gravimetric analysis to measure residual dirt weight, and scanning electron microscopy with EDX can identify particle composition when root cause matters.
Reporting and comparability sit at the heart of the standard. ISO 16232 defines how to express a cleanliness specification and how to report results, so validated extraction procedures and blank values keep results comparable across labs and suppliers. Without that discipline, two labs can test the same part and reach different answers.
The standard excludes filmy contamination such as grease and oils. Your control plan needs a separate method for those residues.
VDA 19.1 and VDA 19.2 for Analysis and Assembly
The VDA 19 series splits technical cleanliness into testing and prevention. VDA 19.1 covers how to inspect particulate contamination, while VDA 19.2 covers how to keep components clean during assembly.
VDA QMC published a revised edition of VDA 19.1 in February 2026. The revision ran from February 2023 to May 2025, and it adds dry extraction methods, newer analysis techniques, and an SEM/EDX standard analysis with uniform material classes.
VDA 19.2, first published in 2010, addresses environment, logistics, personnel, and assembly equipment. Planners and quality staff use it to design and improve cleanliness-sensitive assembly areas.
| VDA 19.1 | VDA 19.2 | |
| Focus | Testing and analysis of particulate contamination | Cleanliness during assembly, logistics, and production |
| Typical users | Cleanliness labs, inspectors, quality engineers | Process planners, production and logistics managers |
| Key topics | Extraction, analysis, documentation, specification format | Environment, personnel, equipment, material flow |
| Role in your control plan | Verifies cleanliness | Prevents contamination |
Inspector qualification matters in technical cleanliness work too. Whoever runs extractions and analyses needs current training, so your QMS should track those qualifications as controlled records.
What the Standards Do Not Tell You
Neither ISO 16232 nor VDA 19 supplies one universal technical cleanliness limit. Your customer specification and your component’s function set the limit. ISO 16232:2018 remains the published edition, although a revision is under development, so confirm the current status of each document before you cite it in a specification.
How to Build a Technical Cleanliness QMS Control Plan
A technical cleanliness QMS control plan turns standards into daily practice. The five steps below give quality teams a repeatable structure, and you should adapt each one to your components, customers, and production flow.
1. Define Component-Specific Technical Cleanliness Requirements
Start with the component, not the standard. Identify the functionally relevant surfaces, meaning the areas that contact fluid, seal, slide, or conduct current. Then ask which particle sizes, hardness levels, and types could damage each surface.
Review customer specifications, drawings, and IATF 16949 expectations. Write acceptance criteria that state the maximum particle size, the allowed counts per size class, and separate limits for metallic and fibrous particles. Use the specification format that ISO 16232 and VDA 19.1 define.
Have a technical specialist approve every specification, then store it in a controlled document management system with full revision history. When a customer changes a limit, every affected team must see the new version immediately.
2. Map Contamination Risks Across Production
Walk the entire process, from raw material to shipment. Machining creates chips and burrs, cleaning baths redeposit particles when filters degrade, and handling adds fibers and skin particles. Storage and transport expose parts to dust, while assembly introduces tool wear and packaging debris.
Mark every point where particles can enter or stay on the component, and rate each point by likelihood and impact. This risk map anchors the rest of your technical cleanliness control plan. Then assign a control, such as deburring, filtration, covered racks, gloves, clean packaging, or zoned work areas.
Use VDA 19.2 as your reference for assembly zones, personnel rules, and logistics. Review the map after every process, tool, or layout change, because a risk map that nobody updates stops protecting you.
3. Establish Technical Cleanliness Inspection and Testing Procedures
Define what you test for technical cleanliness, how often, and who decides. Build sampling plans around risk and production volume, and specify the extraction method, analysis method, filter type, and blank value limit. Validate the extraction so you know it removes particles reliably.
Check whether the component tolerates liquids. VDA 19.1 now includes dry extraction methods, which suit parts that cannot take wet extraction, so match the method to the component rather than defaulting to what the lab already owns.
Assign clear responsibilities by naming who samples, who analyzes, who reviews, and who releases the lot. Require clean handling of test parts, because careless sampling can ruin a valid result. Each report should state the specification, the method, the results, and a clear pass or fail.
Finally, confirm that your inspectors hold current qualifications. Training records belong in the same system as your procedures, and a training management system can flag expiring certificates before an auditor does.
4. Control Suppliers and Incoming Components
Your finished product inherits every particle your suppliers leave behind, so supplier control is central to technical cleanliness. Send the cleanliness specification with the purchase order or quality agreement, and state the test method, reporting format, and inspection frequency. Require lot-identified test reports with each shipment.
Run incoming inspections based on part risk and supplier history, because a new supplier deserves tighter checks than a proven one. Define the escalation path in advance: a first failure might trigger a supplier corrective action request, and repeat failures might trigger an on-site audit or a change in approval status.
Keep qualification files, certificates, and performance data together. Effective supplier management gives your team one place to see which suppliers meet the specification and which ones need attention.
5. Maintain Records and Traceability
Technical cleanliness traceability starts here: connect every inspection result to the component identification, production lot, supplier, process record, and any nonconformity report. That chain lets you answer the hard questions quickly: which lots does a failed result affect, and which machine, cleaning bath, or shift produced them?
Keep analysis reports and, where possible, filter images and raw data. Set retention periods that match customer and regulatory requirements. Use ISO 16232 as your guide for inspection and documentation principles, and VDA 19.2 for assembly and contamination prevention records.
Traceability also supports audits. Auditors want proof that you tested what your specification requires and acted on what you found, and complete, linked records give them that proof in minutes instead of days.
What to Do When a Technical Cleanliness Test Fails
A failed technical cleanliness test challenges your quality management system as much as your parts. A consistent response protects customers and shortens investigations, so follow these five steps every time:
- Identify and contain affected components. Stop shipment of the suspect lot immediately, quarantine parts in process, in stock, and in transit, and check upstream and downstream lots that shared the same equipment or materials.
- Review inspection records and define the scope. Confirm the result first by checking the blank value, extraction validity, and sampling method. Then compare the failure against recent results to see whether it signals a trend or a one-off.
- Investigate contamination sources and process conditions. Examine particle size, shape, and composition, and check cleaning bath condition, filter changes, handling practices, packaging, and recent maintenance. Interview operators about anything unusual.
- Document the nonconformity and assign corrective actions. Record the failure in a nonconformity report, name an owner, set due dates, and address both the immediate cause and the system weakness behind it.
- Verify that the corrective action works. Repeat testing after the fix, confirm that results stay within the specification across several lots, and close the action only when the data supports it.
Why Particle Size, Shape, and Composition Matter
A Thermo Fisher Scientific case study shows why detailed particle data pays off in technical cleanliness programs. A Fortune 50 automaker saw field failures rise as its components became more sensitive to micron-size particles, and gravimetric testing plus optical inspection no longer gave enough insight. The team added measurement of particle size and shape along with compositional analysis, which helped engineers trace particles to their sources. The case study reports a 75 percent reduction in field failure rates.
The lesson for technical cleanliness root cause analysis is simple: size counts, but shape and composition point toward the source.
How QMS Software Supports Technical Cleanliness
Quality software does not weigh filters or count particles, because your laboratory does that. Software organizes everything around the test: the procedures, the people, the records, and the corrective actions. eLeaP pairs a QMS with an LMS on one platform, so quality records and training evidence stay linked. The right quality management system software gives your technical cleanliness program structure without replacing technical judgment.
Here is where software helps most:
- Controlled procedures and specifications. Teams work from approved, current versions, and revision history shows who changed a limit and when.
- Inspection records and traceability. Test reports link to lots, components, suppliers, and process records, so you find affected product in minutes.
- Supplier nonconformity management. Failed incoming results trigger a documented supplier response, and escalation steps follow your rules every time.
- Corrective and preventive action workflows. A CAPA management system assigns owners, tracks due dates, and requires effectiveness checks before closure.
- Audit evidence and trend reporting. Dashboards reveal repeat failures by supplier, part number, or process, and auditors see the full story in one place.
Training deserves equal attention in a technical cleanliness program. Operators who handle components, inspectors who run extractions, and planners who design clean areas all need current competence. Because eLeaP connects quality events with learning, a changed procedure or a closed corrective action can trigger retraining for the right people.
Software organizes the actions and evidence around technical cleanliness testing. It does not choose the inspection method or set acceptance criteria, so qualified technical staff still make those decisions.
Technical Cleanliness QMS Checklist
Adapt this technical cleanliness checklist to your components, customers, and audit schedule:
- Component-specific cleanliness requirements are approved.
- Contamination risks are assessed across relevant processes.
- Inspection methods and acceptance criteria are documented.
- Supplier requirements and incoming checks are defined.
- Failed results trigger documented containment and investigation.
- Corrective actions include effectiveness verification.
- Records remain traceable to components and production lots.
Conclusion
Technical cleanliness is a managed quality requirement, not a final cleaning task. Strong technical cleanliness programs combine suitable specifications, contamination prevention, reliable inspection, and traceable corrective action. ISO 16232 and VDA 19 give you the framework, while your own components and customers give you the limits.
Take a hard look at your current quality management system. Does it connect technical cleanliness requirements with production controls, supplier oversight, and documented evidence? If gaps appear, start with the weakest link. Whether you build the technical cleanliness QMS control plan on paper or in software such as eLeaP, the goal stays the same: proof that every component leaves your plant clean enough to perform.
Frequently Asked Questions
What is technical cleanliness in a QMS?
Technical cleanliness in a QMS means managing particulate contamination as a controlled quality requirement, with a documented control plan behind it. The system holds the specifications, inspection records, supplier actions, and corrective actions, and it links results to lots and components so you can contain problems fast and prove control during audits.
How are technical cleanliness requirements measured?
Labs extract particles from the component, collect them on a filter, and analyze them. They typically count and size particles, weigh residual dirt, and sometimes identify composition with SEM/EDX. The exact method depends on the component and the applicable customer specification, and ISO 16232 and VDA 19.1 define how to run and report these tests.
What is the difference between ISO 16232 and VDA 19?
ISO 16232 is the international standard for cleanliness inspection of road vehicle components. VDA 19.1 covers the same inspection topic in more detail for the automotive supply chain, and VDA 19.2 adds guidance on keeping assembly, logistics, and personnel clean. Neither document sets universal limits.
Can QMS software prevent particulate contamination?
No software removes particles from a part. Physical contamination prevention relies on manufacturing controls such as cleaning, handling rules, and clean assembly areas. A platform like eLeaP supports those controls by managing procedures, training, traceability, and corrective action, which strengthens discipline but does not replace it.
How should manufacturers respond to a failed cleanliness test?
For a failed technical cleanliness test, contain the affected lots first, then confirm the result and define the scope. Investigate sources using particle size, shape, and composition, document the nonconformity, assign corrective actions, and verify the fix with follow-up testing. Close the action only after the data confirms the problem is gone.