Non-Viable Particle Count in Cleanrooms

Non-Viable Particle Count is a measurement of total airborne particle count or concentration at specified particle-size thresholds in a cleanroom. This is a working glossary definition, not a quoted regulatory definition. The result describes the particle content of sampled air; the word “non-viable” does not establish the biological status of individual particles.

EU GMP Annex 1 uses “total particle” terminology: its paragraph 9.15, Table 5 addresses total particle concentration for monitoring. When interpreting a result, keep three quantities separate:

• Measured count: the number of particles counted at the stated size threshold.
• Sampled air volume: the quantity of air represented by that count.
• Reported concentration: the count divided by sampled air volume, expressed in a stated volume unit, such as particles per cubic metre.

A total-particle result and a viable-monitoring result are separate categories, not interchangeable expressions of the same measurement. Annex 1 paragraph 9.9 addresses viable and total particle monitoring separately within the broader environmental monitoring programme. For the microbial side, see bioburden monitoring.

“Non viable particle counter” is the instrument-related search term. FDA’s 2004 aseptic-processing guidance recommends a remote counting system in its critical-area monitoring discussion. Here, the focus is what the sample represents and how its result is interpreted, rather than detector physics.

These terms distinguish a result, an instrument and the activity that interprets the evidence. This is glossary usage, not a regulatory definition of a particle counter. EU GMP Annex 1, paragraph 9.9 refers separately to “viable and total particle monitoring” and recommends appropriate alert levels and action limits for both.

Annex 1, paragraph 9.21 expressly allows monitoring sample volume to differ from that used for formal classification. The dedicated classification-versus-monitoring section explains the operational distinction.

For related reading, see environmental monitoring and bioburden monitoring. Keep those topics connected without treating their results as interchangeable.

Start with the product and jurisdiction, not the cleanroom label. The three documents below are guidance sources; their recommendations should not be presented as statutory provisions. Assess applicable binding legislation separately, and record why a particular guidance document belongs in the site's monitoring strategy.

Annex 1, section 1 describes general guidance for systems and procedures used to manufacture all sterile products. For the wider framework, see EU GMP Annex 1 (2022).

FDA's critical-area particle-quality recommendation describes air immediately around exposed sterilized containers, closures and filling or closing operations: no more than 3520 particles per cubic metre at 0.5 µm and larger, counted at representative locations during those operations. The passage calls this Class 100 (ISO 5). That terminology does not introduce ISO sampling grids or classification procedures into this comparison.

PIC/S PE 009-18 Annex 1 is the sterile-medicinal-products annex. Its document map distinguishes section 9's ongoing routine monitoring from section 4's premises qualification discussion. Keep that routine-monitoring discussion separate from classification when mapping the site's evidence.

For supplements, food, devices and chemicals, use a documented product-and-jurisdiction assessment rather than assigning pharmaceutical grades automatically. This is a proposed scoping practice, not a universal requirement. The sterile / aseptic supplement boundary is one useful starting point.

Can the monitoring plan move unchanged to another room?

Treat transfer as a site reassessment, not automatic equivalence. As a practical review, have the responsible quality and technical personnel assess the receiving room's process, exposure conditions and sampling rationale before approving reuse or revision of the plan.

Annex 1’s section 9 document map separates ongoing routine monitoring from the premises guidance in section 4, which includes premises qualification. Section 9 addresses monitoring-system design, action limits, alert levels and trend review. These are distinct assessment contexts, not interchangeable labels for particle-count records.

Sample volume is another distinction. Annex 1, paragraph 9.21 states that monitoring sample volume need not be the same as the volume used for formal classification of cleanrooms and clean air equipment. Separately, it states that monitoring sample volumes should be justified. Permission to use a different volume does not remove that expectation.

Classification is a qualification activity. Annex 1 paragraph 4.26 describes it as "a method of assessing the level of air cleanliness against a specification for a cleanroom or clean air equipment by measuring the total particle concentration." Paragraph 4.27 says that particles equal to or greater than 0.5 and 5 µm should be measured "both at rest and in simulated operations in accordance with the limits specified in Table 1." Initial classification is performed during simulated operations, and reclassification during simulated operations or during aseptic process simulation.

The two operating states are defined precisely in paragraph 4.29. "At rest" is the condition with utilities and HVAC installed and functioning and the main equipment installed "but not operating and without personnel present in the room." "In operation" means equipment functioning in the defined operating mode "with the maximum number of personnel present performing or simulating routine operational work." At-rest limits should be achieved after a clean-up period following operations and line clearance; Annex 1 gives a guidance value of less than 20 minutes, to be determined during room qualification.

The values above reproduce Annex 1 Table 1, maximum permitted total particle concentration for classification. Footnote (a) states that classification including 5 µm particles "may be considered where indicated by the CCS or historical trends." Footnote (b) says Grade D in-operation limits are not predetermined and that the manufacturer should establish them based on a risk assessment and routine data where applicable. Routine monitoring then has a different purpose: paragraph 9.4 says the programme should provide assurance that cleanrooms and clean air equipment "continue to provide an environment of appropriate air cleanliness".

For a site-designed record, the following attributes provide useful context rather than an official mandatory field list:

• Assessment purpose: classification or routine monitoring.
• Area grade: the grade associated with the observation.
• Operating state: the state represented by the observation.

As a practical review step, use those attributes before combining results or selecting a comparison limit. Keeping that context attached to observations supports data integrity by design and helps an environmental monitoring program distinguish records collected for different purposes.

The numerical table later in this article is specifically Annex 1 Table 5 for monitoring. Paragraph 9.9 identifies it as the maximum total particle action limits; it is not presented here as a classification-limit table.

For sterile-drug aseptic processing, FDA's critical-area sampling recommendation calls for representative locations normally not more than 1 foot from the work site, within the airflow, during filling or closing. On an aseptic fill line, this means sampling the area around exposed product—not simply choosing a convenient instrument location.

FDA recommends measurements where exposed sterilized product, containers and closures face the greatest potential risk. The probe orientation should be demonstrated to obtain a meaningful sample; proximity alone does not establish this. FDA also recommends regular monitoring during each production shift.

Placement must also account for the sampling activity itself: Annex 1, paragraph 9.8 says sampling methods should not pose a contamination risk to manufacturing operations.

Grade A coverage and sample volume

For Grade A, Annex 1, paragraphs 9.16–9.17 recommend monitoring throughout critical processing, including equipment assembly. Monitoring should be continuous for both ≥0.5 µm and ≥5 µm particles, using a suitable sample flow of at least 28 litres per minute. These are sterile-manufacturing Annex 1 expectations, not a generic sampling prescription for every cleanroom.

Worked case: assume a constant flow of 50 L/min for 2 minutes and an observed count of 250 particles in the ≥0.5 µm channel. These are illustrative settings, not a prescribed sampling configuration.

• Sample volume = 50 L/min × 2 min = 100 L = 0.100 m³.
• Concentration = 250 particles ÷ 0.100 m³ = 2500 particles/m³.

Does FDA prohibit portable particle counters?

No. In its critical-area discussion, FDA recommends remote counting systems for nonviable monitoring because they can collect more comprehensive data and are generally less invasive than portable counters. This is a recommendation for that aseptic-processing context, not a blanket prohibition on portable instruments.

What if the product generates powder particles?

FDA recognizes that some operations generate product particles that do not themselves pose a product-contamination risk. Where this prevents meaningful differentiation within one foot, FDA allows sampling to be adapted to characterize, as far as possible, the extrinsic particle contamination reaching the product. This is not a blanket exemption for dusty operations: the objective remains characterization of external contamination.

Use this proposed lifecycle to assign ownership at each handoff; it is not a universally mandated workflow. Record the responsible people in the site procedure.

Workflow: Approve monitoring scope → select locations → configure sampling → confirm readiness → collect results → evaluate observations → handle exceptions → complete authorised review.

The person assigned monitoring readiness confirms that the approved setup is ready before collection begins. During production, the designated responder records the observation and immediate response in the process event log. Unresolved events pass to the assigned investigator with the relevant results, production context and actions already taken. The authorised product decision-maker receives the investigation assessment and documents the product decision; the responder’s acknowledgement does not substitute for that review.

Keep routine acquisition, alarm acknowledgement and investigation closure as distinct statuses. Acquisition describes data collection; acknowledgement records a response, not the technical explanation for an event. Closure records completion of the investigation and its review. This separation supports exception-based review without allowing an acknowledged alarm to disappear from unresolved work.

Should an alarm prompt additional microbial monitoring?

For grade A monitoring, Annex 1, paragraph 9.17 recommends that procedures define alarm-response actions, including consideration of additional microbial monitoring. That is consideration within the response procedure, not an instruction to perform additional testing after every alarm.

For sterile medicinal-product cleanrooms, EU GMP Annex 1 guidance gives the following maximum total particle concentrations for monitoring in Table 5. All concentrations are in particles/m³.

(a) See “How are Grade D operating limits set?” below.

These are maximum action limits, not default alert settings. Paragraph 9.9 calls for viable and total particle alert levels based on cleanroom qualification results, with periodic review against ongoing trend data.

For Grade A monitoring, paragraph 9.17 calls for frequent comparison of each individual sample result with alert levels and action limits. Alarms should trigger when alert levels are exceeded—not only when the maximum action limit is exceeded.

Worked case 2: aggregation hides an excursion

Assume two consecutive Grade A samples, each 0.100 m³, contain respectively 3 and 0 particles at ≥5 µm. Individual concentrations are 3 ÷ 0.100 = 30 and 0 ÷ 0.100 = 0 particles/m³. The first exceeds Table 5’s value of 29. Combining the samples gives 3 ÷ 0.200 = 15 particles/m³, obscuring that exceedance. This illustrates information loss, not a prescribed averaging window. As a data-integrity design practice, retain individual results alongside aggregates.

Can action limits be tighter?

Yes. Paragraph 9.9 permits more stringent action limits based on data trends, the process’s nature or the contamination control strategy (CCS).

How are Grade D operating limits set?

Table 5, footnote (a) says the manufacturer should establish in-operation limits using a risk assessment and routine data, where applicable.

Is clean-up always a 20-minute deadline?

No. Table 5, Note 1 describes a qualification-defined clean-up period, with a guidance value of less than 20 minutes—not a universal deadline—for achieving at-rest limits after operations in an unmanned state.

Can occasional Grade A macro-particle counts be ignored?

Table 5, Note 2 recognises possible false indications, especially at ≥5 µm, from electronic noise, stray light or coincidence loss. Consecutive or regular low-level counts may indicate contamination and should be investigated. As review practice, preserve the observations and record the assessment through attributable recording; a possible false count is not permission to discard a result.

A proposed architecture would connect particle observations to manufacturing execution records through batch, operation and time-window references, then link exceptions to quality investigations. This is a design proposal, not an existing interface or prescribed integration standard. Use production context tagging to define those relationships before specifying transfers.

Suggested evidence model

The diagram uses stable identifiers; arrows represent record links, not automatic data movement: LocationID + InstrumentID + SamplingPlanID/version → SampleID SampleID → SourceObservationID → CalculationID SampleID ↔ BatchID + OperationID SampleID or ExpectedIntervalID → ExceptionID → InvestigationID → ReviewID

Keep source observations—counts by size channel, sampled volume and interval—separate from calculated concentrations. A calculation record would reference its inputs, formula and units. A review record would identify the reviewer, assessment and decision; it would not overwrite either the observation or calculation. An ExpectedIntervalID allows an exception to exist when no sample arrives.

For a proposed MES–historian integration, define timestamp meaning, time zone and interval boundaries separately from import time. Preserve original units alongside conversions; map instrument location codes to controlled LocationIDs. Detect repeat imports using source identifiers, and retain the limit version applied to each sample rather than silently substituting the latest version. Proposed MES–QMS links would carry exception and investigation identifiers without transferring decision authority.

Worked case 3: interrupted transfer

Assume a six-minute interval with three expected two-minute records: 0–2, 2–4 and 4–6 minutes. After an interruption, records for 0–2 and 4–6 minutes are recovered. Reconcile both to their original intervals and check for duplicates. Three expected minus two recovered leaves one unresolved gap: 2–4 minutes. Record that interval as missing, not as a zero-particle result, and send it for documented human assessment. Recovery remains a design objective, not a promised capability.

Use the preceding diagram as the context model, then define a sample record that lets a reviewer reconstruct the measurement. A practical minimum is the original count, size threshold, air volume, reported concentration, time interval, location, operating state and applicable monitoring-plan version. This is a proposed record design, not a universal required field list. Keep units explicit and preserve the connection between the observation and its calculated result.

For site-selected verification, document test inputs, expected results, actual results and reviewer conclusions. Useful exercises include:

• Convert a known air volume between the units used by the counter and reporting system.
• Recalculate concentration independently from the original count and sampled volume.
• Check that the selected size threshold retrieves the intended measurement channel.
• Trace an observation to its correct location, operating state and applicable limit set, including after a plan revision.

These checks test numerical and contextual correctness. They do not establish whether the physical sampling position represents the activity being assessed; assess that separately through the sampling design. Clear production context tagging supports this distinction.

For a correction example, suppose review identifies an incorrect location label. As a proposed data-integrity control, retain the original observation, identify the location field and its corrected value, record why it changed, and link the review. Do not silently overwrite the label.

Make sample rejection, invalidity and unresolved gaps explicit reviewable states. Record the reason, assessment status and any trend exclusion so later reviewers can distinguish excluded observations from missing intervals. Use the recovery approach described above rather than silently removing these records from trends.

In its aseptic-processing guidance, FDA's critical-area contamination discussion explains why airborne particles matter: they can enter product as extraneous contaminants and carry microorganisms into it. This product-quality concern gives particle observations a role in assessing exposure, rather than treating them simply as room-performance statistics.

A practical product-impact assessment should connect the event to production context. Use the batch record and related environmental monitoring results to address:

• Timing: when did the observation occur, and which production interval could be affected?
• Exposure: which products, containers or closures were exposed, and during which operations?
• Interventions: what activities or stoppages coincided with the event?
• Corroboration: what do related monitoring results show for that location and period?
• Record reliability: are timestamps, sampling continuity and the underlying particle data adequate to support the assessment?

Separate observations from causal conclusions. A particle increase coinciding with an intervention is an association to investigate, not proof that the intervention contaminated product. Document alternative explanations and unresolved gaps rather than forcing a definitive cause.

In this workflow, authorised people assess product impact and approve or release according to the applicable quality system. Neither an alarm, its acknowledgement nor a below-limit measurement automatically determines rejection or batch release.

Close the review with a concise statement of the event, evidence considered, remaining uncertainty, affected production scope and authorised decision. Frame the conclusion around the combined assessment, not a particle result presented as proof of sterility.

Use this proposed implementation review to test whether particle results retain their meaning from collection through assessment. These are design recommendations, not prescribed regulatory controls or documented incidents. Focus on interpretation errors that can survive even when the counter produces a valid measurement.

Connect location identifiers to production context tagging, and make assessment changes traceable through an audit trail. Test these controls with representative records, not only configuration screenshots.

Implementation and periodic-review checklist

• Applicability ownership: identify who maintains the product and jurisdiction assessment discussed under scope and status.
• Plan approval: confirm the monitoring-plan owner, approver and current approved version, as covered in the operational lifecycle.
• Verification evidence: locate test results and unresolved issues from system verification; use risk-based validation to organise review priorities.
• Escalation ownership: confirm named roles and handoffs for the excursion process covered above.
• Reviewer access: demonstrate access to original results, context, exclusions and assessment history.
• Change assessment: review changes to mappings, time conventions and limit versions for effects on interpretation.

Can a reviewer reconstruct what was sampled, which interpretation applied, what happened next and who authorised the conclusion?