Particle counter calibration for cleanroom classification
ISO 21501-4 sets what a light-scattering particle counter has to demonstrate. Why counting efficiency at the smallest channel is the specification that matters, and how flow rate error becomes concentration error.
Cleanroom classification under ISO 14644-1 is a counting measurement, and its credibility rests on the instrument doing the counting. ISO 21501-4 is the standard that says what a light-scattering airborne particle counter has to demonstrate, and it is referenced from the classification standard for that reason.
Counting efficiency, and the 50 % that looks like a fault
The requirement that surprises people is counting efficiency at the smallest channel: 50 % ± 20 % at the smallest size the counter reports, and 100 % (within tolerance) at 1.5 to 2 times that size. A counter that detected everything at its smallest channel would be out of specification.
The reason is that a real counter's response does not switch on sharply at a threshold — it rises over a range of sizes. Specifying 50 % at the nominal size puts the midpoint of that transition at the stated channel, so that particles slightly smaller are under-counted and particles slightly larger are over-counted in a balanced way. The alternative, demanding full efficiency at the smallest channel, would place the whole transition below the stated size and make the counter's nominal channel meaningless.
| Characteristic | Why it is specified |
|---|---|
| Counting efficiency | Ties the reported channel size to a defined point on the response curve |
| Size setting and resolution | Ensures channels mean what they say and can be told apart |
| Flow rate | Concentration is counts per volume; volume comes from flow and time |
| False count rate / zero count | Electronic and optical noise appearing as particles |
| Maximum concentration and coincidence | Above a limit, two particles are counted as one |
| Sampling time | The other half of the sampled volume |
Flow rate is concentration
A particle counter reports a concentration — particles per cubic metre — obtained by dividing the counts by the volume it believes it sampled. That volume is the flow rate multiplied by the sampling time. A flow rate 5 % low means the counter thinks it sampled 5 % less air than it did, and the reported concentration is 5 % high, with nothing in the count itself to reveal it.
This is why flow verification belongs in routine use rather than only at annual calibration: a partially blocked filter, a tired pump or a kinked sample line changes the flow, and the instrument keeps reporting confident numbers throughout.
Coincidence at high concentrations
When two particles pass through the sensing volume at once, the counter sees one event — and, because the scattered light is greater, may size it larger than either. This coincidence loss means counts fall and sizes shift upwards as concentration rises, which is why counters carry a maximum concentration specification. Using one above that limit in a dirty area or during recovery testing produces results that understate the contamination.
Isokinetic sampling
Where air is moving — unidirectional flow areas in particular — the sample probe should draw air at a velocity matching the airflow it is sampling from. Draw too slowly and larger particles' inertia carries them into the probe disproportionately, over-representing them; draw too quickly and the opposite happens. The probe should also face into the flow. In turbulent or low-velocity areas the requirement relaxes, but the sample line does not: long, coiled or sharply bent tubing loses large particles to the walls before they ever reach the sensor.
What the calibration does not cover
The certificate describes the instrument. It says nothing about whether the sample point was representative, whether the room was at rest or in operation, how many locations were sampled, or how long each sample ran — all of which belong to ISO 14644-1 and to the protocol. A perfectly calibrated counter sampling in the wrong place gives a precise answer to the wrong question.
Frequently asked questions
- Why is 50 % counting efficiency acceptable at the smallest channel?
- Because it is the specification, not a shortfall. A real counter's response rises gradually across a range of particle sizes rather than switching on at a threshold. ISO 21501-4 requires 50 % ± 20 % efficiency at the smallest reported size and 100 % at 1.5 to 2 times that size, which places the midpoint of the transition at the stated channel so that slightly smaller particles are under-counted and slightly larger ones over-counted in a balanced way. Demanding full efficiency at the smallest channel would push the whole transition below the nominal size and make the channel label misleading.
- How does flow rate error affect particle counts?
- Directly and invisibly. The counter reports a concentration by dividing counts by the volume it believes it sampled, and that volume is flow rate times sampling time. If the flow is 5 % below nominal, the counter has actually sampled more air than it thinks, and the reported concentration is about 5 % high. Nothing in the counts reveals it, which is why flow should be verified in routine use — a blocked filter, a tired pump or a kinked line all change it while the instrument keeps producing confident numbers.
- What is coincidence loss?
- When two particles pass through the sensing volume simultaneously, the counter registers one event rather than two, and because the scattered light is greater it may also size that event larger than either particle. The net effect as concentration rises is that counts fall and the apparent size distribution shifts upward. This is why counters specify a maximum concentration, and why using one above that limit — in a dirty area, or during recovery testing — produces results that understate the contamination.
- Do I need an ISO 21501-4 calibrated counter for ISO 14644-1 classification?
- Yes. ISO 14644-1 references ISO 21501-4 for the instrument, so a classification performed with a counter that has not demonstrated those characteristics rests on an instrument whose counting behaviour is unknown. The calibration is a prerequisite rather than a refinement.
- What is isokinetic sampling?
- Sampling at a probe velocity that matches the velocity of the air being sampled, with the probe facing into the flow. If the probe draws too slowly, the inertia of larger particles carries them in disproportionately and over-represents them; too quickly and they are under-represented. It matters most in unidirectional flow areas and relaxes in turbulent or low-velocity ones — but the sample line always matters, because long, coiled or sharply bent tubing deposits large particles on the walls before they reach the sensor.
References
- [1]ISO 21501-4 — Determination of particle size distribution: Light scattering particle counter for clean spaces
- [2]ISO 14644-1:2015 — Cleanrooms and associated controlled environments, Part 1: Classification of air cleanliness by particle concentration
- [3]ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories
General technical guidance written against the cited sources. It is not regulatory or legal advice and does not replace the applicable standard, guideline or a qualified reviewer's judgement.
Have a question on this topic?
Ask ValiTrac AI and see the evidence and calculation behind the answer.
Ask ValiTrac AIFree calculator: Calibration interval
Paste an instrument's as-found history and see how fast it is actually drifting, how much of its tolerance that consumes, and how long the evidence supports trusting it. The strongest input to an interval is the instrument's own record — this reads it.
Open the calculatorRelated articles
Measurement uncertainty explained
What an uncertainty statement means, how it is built up, and why a coverage factor matters.
How to set calibration intervals
There is no universal interval. Set it from risk, manufacturer data and — above all — the instrument's own as-found history.
Qualifying a temperature monitoring system
Installation checks, functional tests including alarm and failure modes, and a performance period under routine use — plus the software validation that sits underneath.