The ISO 4406 oil cleanliness code is a three-number rating that reports how many solid particles of specific sizes are suspended in one milliliter of a fluid sample, giving maintenance teams a standard, auditable measure of contamination.
Roughly 70 to 80 percent of hydraulic and lubrication failures trace back to contaminated fluid, so the code is not a lab formality. It is a leading indicator of bearing, valve, and gear wear.
Read correctly, it lets you set a target cleanliness level for each critical asset and prove whether your filtration and handling practices are actually holding that line.
An ISO 4406 code looks like 18/16/13. Each number is a scale code that corresponds to the counted number of particles per milliliter at three size thresholds, measured with an automatic particle counter calibrated to ISO 11171:
The scale is logarithmic. Each scale code represents a doubling of the particle count in the range above it. Code 13 means between 40 and 80 particles per milliliter; code 14 means 80 to 160; code 18 means 1,300 to 2,500. That doubling matters: dropping just one target number represents cutting the particle population of that size roughly in half.
Suppose a hydraulic power unit returns 20/18/15 and, after you install a better return-line filter, the next sample reads 17/15/12 . Translate the coarse channel (greater than or equal to 14 micrometers): code 15 is 160 to 320 particles per milliliter, while code 12 is 20 to 40.
You have taken the worst-case coarse count from about 320 down to about 40, an eightfold reduction, because you improved by three scale codes and each code halves the population (2 x 2 x 2 = 8).
That single translation is why the code beats a vague label like "the oil looks dirty." It quantifies the improvement, ties it to the filter change that caused it, and gives you a number to trend. Feed those readings into a condition-based maintenance program and the sample result becomes a trigger rather than a filed report.
There is no universal "clean." The right target depends on the most sensitive component in the circuit, because that component sets the tolerance the whole system must respect. General starting points many reliability teams adopt:
Set the target one to two codes cleaner than the manufacturer minimum if the asset is a constraint in your line. Buying that margin is cheap insurance for anything governed by the theory of constraints, where an hour of unplanned downtime on the bottleneck costs far more than the filtration to prevent it.
Contamination follows a life-multiplier relationship: sustaining a fluid one to two ISO codes cleaner than baseline commonly extends bearing and pump life by a meaningful factor, because abrasive wear scales with the population of hard particles in the clearance-sized range. In practice, teams that hold a two-code improvement often report noticeably longer intervals between failures.
You can validate that on your own assets by trending the MTBF against MTTR before and after tightening the target, and by fitting failure data to a Weibull analysis to see whether the characteristic life shifts.
Cleaner fluid moves most fluid-power assets away from the wear-out region of the bathtub curve .
A cleanliness code is only as trustworthy as the sample behind it. Pull samples from a live, turbulent line (not a dead leg or a settled reservoir bottom), flush the sampling port first, and use clean bottles rated for particle counting. Sample at a consistent point in the duty cycle so your trend compares like with like. To actually hold the target, combine three levers:
Treat "sustained oil cleanliness code at or below target" as a documented standard on the asset, much like a control plan defines the reaction when a reading drifts out of limit. Operators pulling and logging routine samples is a natural extension of autonomous maintenance.
ISO 4406 gives you the target; you still need a system that turns each lab result into scheduled, tracked action. Fabrico is an EU-built CMMS and real-time monitoring platform that acts as the data foundation for a cleanliness program.
In Fabrico you can attach each oil analysis result to the specific asset, set preventive schedules for sampling and filter changes, and auto-generate a work order when a reading breaches the target code.
Its CMMS work-order and asset management keeps the full history of samples, filter changes, and spare-parts usage in one place, so the trend line and the corrective actions live on the same record.
Because Fabrico also delivers real-time OEE and production monitoring , including computer vision on machines that have no PLC, you can correlate rising contamination on a critical asset with the availability losses it is starting to cause on the line.
With EU data residency, the sampling and maintenance record stays inside your compliance perimeter. Fabrico does not replace the particle counter or the lab; it makes their output actionable and auditable.
A lower code means cleaner fluid, and cleaner is generally safer for sensitive components. That said, driving far below the manufacturer target adds filtration cost and energy for diminishing returns.
The goal is to hold the appropriate target for the most sensitive component in the circuit consistently, not to chase the lowest possible number on every asset. Use a Pareto analysis to spend your filtration budget on the assets where contamination actually drives failures.
Frequency depends on criticality and duty. Constraint assets and servo-valve systems often warrant monthly sampling, while general hydraulics may be quarterly. New systems, post-repair fills, and any asset showing a rising trend should be sampled more often until the code stabilizes. The right cadence is the one that catches a contamination excursion before it causes a failure, which is a core aim of any proactive maintenance strategy.
No. The code counts particles by size, not by type or source. A high count could be ingested dust, internally generated wear metal, or water-related debris. To identify the cause you pair the particle count with elemental spectroscopy, water content, and viscosity checks, then investigate with a structured method such as 8D problem solving to trace the ingression path and prevent recurrence.
Ready to turn oil analysis results into scheduled work orders and asset-level trends instead of filed PDFs? Book a Fabrico demo and see how real-time monitoring and a field-ready CMMS keep your contamination targets under control.
Login
Blog
