Qualification plans for high-containment systems tend to be finalized early in a project, often before SOPs are complete and before operational workflows are clearly defined. When that scope is set around empty or static test conditions, the system can pass every acceptance criterion and still fail during routine use—because the actual failure modes appear only once operator arms are moving through gloves, pass-through cycles are loaded, or VHP cycles are run against realistic vessel configurations. The consequence is not always visible at commissioning; it tends to surface later as process deviations, contested containment claims, or audit findings where the qualification evidence cannot support the operating claim. The practical judgment this article supports is knowing when real operating conditions change what PQ must include, and what that means for scope, surrogate selection, SOP readiness, and the decision to qualify under static versus in-operation conditions.
Representative operating conditions that change scope
SMEPAC testing provides a controlled reference point for evaluating containment device performance, but the ISPE guideline is explicit that it is a laboratory-condition test. It does not represent a particular process or a real manufacturing environment. Treating SMEPAC results as process-representative qualification evidence is a planning mistake with a specific downstream consequence: if a procurement or acceptance decision is grounded in SMEPAC data alone, the system may be accepted for a manufacturing environment it was never actually tested against.
The core scope criterion for PQ is whether equipment meets its performance requirements with the product installed and under conditions that reflect actual use. That is not a stricter interpretation of SMEPAC—it is a different category of evidence entirely. General pharmaceutical equipment qualification principles frame PQ as the stage where installed and calibrated function (OQ) gives way to demonstrated performance under process-representative conditions. For high-containment systems, that distinction matters because containment can behave differently when a load is present, when a pass-through cycle is active, or when an operator is physically working through a glove port.
The structured contrast between laboratory baseline testing and process-specific PQ is worth making explicit because the two are often treated as interchangeable in early planning.
| Tip de test | Conditions | What It Demonstrates | Limitare |
|---|---|---|---|
| SMEPAC (lab) testing | Laboratory environment, no real process materials | Containment device performance under standardized lab conditions | Does not represent a particular process or real manufacturing environment |
| Calificarea performanței (PQ) | Process-specific load, representative operators, actual or surrogate product | Equipment meets performance requirements with the product installed and under representative use | Requires coordination with SOPs, trained personnel, and safe surrogate conditions |
The limitation column in that comparison is not a minor caveat. If scope is not moved from standardized laboratory conditions toward real process conditions, the qualification record will be difficult to defend against any challenge to the operational containment claim—particularly for systems where dynamic use is part of the accepted operating basis.
Load patterns and operator workflows in PQ planning
At-rest OQ testing captures installed function. It does not capture what happens when an operator’s arms disturb airflow through a glove port, when a sequence of manual manipulations affects pressure behavior, or when repeated interventions introduce ergonomic patterns that the empty-system test never encountered. For any containment system where manual operations are part of the routine workflow, the move from OQ to PQ is a failure-risk reduction step, not a documentation formality.
This is directly analogous to qualification practice in radiopharmacy hot cells, where guidance from EANM distinguishes explicitly between at-rest testing for OQ and in-operation testing for PQ—because arm movements through gloves can alter laminar flow patterns in ways that are invisible during idle-state testing. The same logic applies to any isolator, glove box, or containment enclosure where operator interventions are part of normal production. Qualification testing that does not replicate those interventions may accept a system that performs well when no one is working in it.
ICH Q9(R1) provides a risk management framework that is useful here: the extent of qualification testing should be calibrated to the consequence of containment failure and the frequency of operator intervention, not to a fixed number of test runs or a standardized worst-case challenge. When manual operations are frequent, ergonomically constrained, or sequentially dependent—such as BIBO filter changes, glove-port manipulation in OEB4/5 containment, or loaded pass-through cycles—those patterns should be reflected in PQ design.
| Faza de testare | Stare | Implicarea operatorului | Containment Risk Not Addressed in At-Rest Testing |
|---|---|---|---|
| OQ (at rest) | Equipment idle, no operator arms through gloves | Nici unul | Laminar flow disruption from arm movement, ergonomic productivity impacts |
| PQ (in operation) | Normal workflow, manual manipulations through gloves | Operator movements as in real production | Remaining risk areas captured during representative workflow |
The risk not addressed in the OQ column is where actual manufacturing failures tend to originate. A system that passes at rest but has never been tested under representative workflow may create a quiet containment gap that only becomes visible during a deviation investigation or an inspector’s request for in-operation qualification data.
Surrogate or safe-use conditions for high-containment tests
Defining representative operating conditions for PQ creates an immediate practical constraint: the real API, biological agent, or potent compound cannot always be used during qualification. The test must use a surrogate that closely enough represents the actual material to make the results meaningful, without importing the biological, chemical, or production risk that makes the real agent inappropriate for a qualification run.
The SMEPAC guideline identifies several placebo options with different particle sizes and detection limits. What the guideline also makes clear is that the choice of placebo matters: a system tested with an easy-to-detect surrogate may pass acceptance criteria and still fail when challenged with a compound whose particle size, handling characteristics, or detection limit differs from the test material. This is a hidden failure risk that can persist through commissioning and into routine manufacturing.
Placebo consistency across suppliers compounds this risk in procurement contexts.
| Luare în considerare | Ce trebuie clarificat | Risk If Not Addressed |
|---|---|---|
| Placebo relevance to actual API | Confirm which placebo most closely matches particle size, detection limit, and handling characteristics of the real active ingredient | A system may pass with an easy-to-detect placebo but fail when challenged with the actual compound |
| Placebo consistency across suppliers | Ask whether each equipment manufacturer used the same placebo for SMEPAC or qualification testing | Performance comparisons between different suppliers become unreliable, undermining procurement decisions |
When comparing containment performance across competing systems during procurement, a meaningful comparison requires that the same placebo was used under comparable test conditions. If one supplier tested with a coarser, more easily detected surrogate and another used a finer material with a lower detection limit, the performance data are not directly comparable—and a procurement decision made on that basis may be selecting the system that produced the more favorable test result, not the system that will perform better with the actual compound.
Before accepting any qualification dataset as evidence of containment performance, confirm which surrogate was used, whether it is relevant to your specific API or agent, and whether supplier comparisons were made under consistent test conditions.
Tradeoff between confidence and qualification complexity
Extending PQ scope to include representative workflows, loaded conditions, and operator-present testing increases confidence in the system’s operating performance. It also increases the coordination burden significantly. Representative PQ requires finalized SOPs, trained personnel, validated surrogate materials, and a defined test sequence that is reproducible enough to generate defensible acceptance evidence. None of those conditions are automatically in place at the point where PQ execution is typically scheduled.
The planning mistake is treating this as a binary choice—either run a simple PQ or run a comprehensive one. The more useful frame, consistent with risk-based thinking in ICH Q9(R1), is that complexity should be calibrated to consequence. For a system where containment failure during routine operation would create operator exposure to a high-potency compound or a select agent, the case for more extensive in-operation testing is strong regardless of the coordination overhead. For a system where the containment claim depends only on installed mechanical function and the operating workflow is simple and low-frequency, a more limited scope may be defensible.
The decision criteria are not arbitrary. Three factors tend to drive scope extension: how frequently operators interact with the system during routine use, how sensitive the containment field is to those interactions, and how difficult it would be to demonstrate retrospectively that the qualification evidence covered the actual failure mode. Systems with frequent glove-port access, sequential pass-through cycles, or VHP decontamination loads that vary by campaign should generally be qualified under conditions that reflect that variability. Systems where the primary risk is mechanical failure of a static barrier may not require the same scope extension.
The downstream consequence of underscoping is specific: if a containment claim is challenged—in an audit, in a deviation investigation, or following an exposure incident—qualification evidence that does not reflect actual operating conditions will be difficult to defend. The qualification record will show that the system passed, but it will not show that it passed under the conditions that produced the event under review.
SOP readiness before performance execution
PQ execution against a system that is not yet supported by finalized SOPs is a reproducibility risk, not just a documentation gap. If the operator executing a test sequence is working from draft procedures, informal guidance, or verbal instruction, the test cannot confirm that the system performs as intended under routine operation—because routine operation has not yet been defined in a form that can be consistently followed.
This is one of the more common late-project friction points in high-containment system validation. PQ is often scheduled against a commissioning timeline, and SOPs are often still in review when the qualification window opens. The result is pressure to execute PQ with incomplete documentation and then close out the SOP review afterward—at which point any procedural change made during SOP finalization may technically require qualification impact assessment or partial requalification.
The practical check before PQ execution should include confirmation that relevant SOPs are approved and available, that instruction manuals for the equipment are finalized and on-site, and that the operators who will execute the test are documented as trained against those procedures.
| Document/Record Element | What the PQ Protocol Should Include | De ce este important |
|---|---|---|
| SOP and manual references | List of relevant SOPs, instruction manuals, and cleaning procedures | Ensures test sequences match how the equipment will actually be operated |
| Personnel training records | Names of key operators, their training programs, and documented competence | Confirms that staff executing PQ are qualified and that deviations are not due to unfamiliar operators |
| Responsibilities definition | Clear assignment of who performs each step, approves results, and handles exceptions | Prevents ambiguous hand-offs that could lead to unrepresentative or unreproducible test conditions |
The responsibilities definition element in that framework is often underspecified. When it is not clear who approves interim results, who has authority to pause a test sequence, or how deviations are escalated during execution, test conditions can drift in ways that make the results difficult to reproduce or defend. Ambiguous hand-offs during a live PQ run are a reproducibility failure risk that does not appear in equipment qualification protocols—but does appear in audit findings when the protocol is reviewed.
FDA process validation guidance supports the principle that documented procedures and qualified personnel are prerequisites for meaningful qualification execution, not parallel activities that can be completed concurrently. Treating SOP readiness as a pre-execution review gate, rather than a documentation deliverable to be finalized after the fact, is the posture that protects the qualification record.
PQ trigger for non-static containment claims
Not every containment system requires full in-operation PQ. The trigger is not determined by equipment category or regulatory classification alone—it is determined by whether the system’s containment claim depends on dynamic conditions that at-rest testing cannot verify.
For systems where manual operations are part of routine use—glove-port access in an isolator, BIBO filter changes in a ducted containment enclosure, operator-dependent transfer sequences in a BSL-3 pass-through—the containment claim is not static. Airflow patterns, pressure cascades, and barrier integrity under those conditions may differ from idle-state behavior. When containment performance is contingent on what the operator does and how the system responds to those interventions, OQ evidence alone does not support the claim. The hot-cell analogy from radiopharmacy qualification practice illustrates this directly: guidance distinguishes OQ at-rest from PQ in-operation specifically because arm movements through gloves can alter the containment field in ways that are invisible during idle testing.
The absence of in-operation PQ for non-static claims is not simply an incomplete test set—it is an unvalidated claim. If the operating basis of the system assumes that containment is maintained during routine operator interventions, and qualification was never run under those conditions, the claim has not been substantiated. That gap becomes consequential when a process deviation involves an operator-present event, or when an inspector asks what evidence supports the containment rating during active use.
The practical trigger criterion is straightforward: if the acceptance claim would be different, or potentially worse, when an operator is present and working through the system compared to when the system is idle, PQ must include in-operation conditions to support that claim. For containment systems integrated into BSL-3/BSL-4 module laboratories where operator workflows are continuous and varied, or for VHP transfer and decontamination systems where cycle performance depends on load configuration, the trigger condition is almost always present. The earlier in project planning that trigger is identified, the less disruptive the scope extension will be when PQ execution begins.
For teams developing decontamination qualification scope, the VHP validation protocol covering IQ OQ PQ for hydrogen peroxide systems provides a useful reference for how phase boundaries and acceptance criteria are typically structured across the qualification stages.
The qualification evidence that matters most in a high-containment context is not evidence that the system passed under controlled, empty, or idle conditions—it is evidence that the system performed under the conditions that will actually be present during routine use. Before finalizing PQ scope, the most important confirmations are: whether the acceptance claim is dynamic or static, which surrogate most closely represents the actual material the system will contain, and whether SOPs and trained personnel are in place before the first test run begins. Those three checks will determine whether the qualification record produced can support the containment claim if it is ever challenged under operational conditions.
The less visible risk is surrogate selection. A qualification that passes with a coarse, easy-to-detect placebo but was never challenged with a material that reflects the actual API’s particle size or handling characteristics has not demonstrated what it appears to demonstrate. Confirming placebo relevance and supplier consistency before accepting comparative qualification data is a procurement and validation review step that protects both the qualification record and the procurement decision that preceded it.
Întrebări frecvente
Q: Our high-containment system is fully automated and has no routine manual glove-port access or operator interventions. Does the advice to include in-operation PQ still apply?
A: Not necessarily. If the containment claim relies only on static barrier integrity and automated processes that are unaffected by operator presence, at-rest OQ may be sufficient. However, you should still verify that other dynamic conditions—such as varying load configurations, pass-through cycles, or VHP decontamination with different vessel loads—do not alter performance in ways that demand in-operation testing.
Q: We’ve determined our PQ scope must include representative operator workflows and loaded conditions. What is the immediate next step before we begin test execution?
A: Confirm that all relevant SOPs are finalized and approved, and that the operators who will execute the tests are formally trained against those procedures. Running PQ with draft or informal guidance creates a reproducibility risk; if SOPs change after testing, the qualification evidence may no longer support the operational claim.
Q: Is there a specific biosafety level or OEB band where regulators automatically require in-operation PQ, irrespective of the specific workflow?
A: No universal threshold exists. Regulatory expectations are driven by risk, not a fixed classification. That said, for BSL-3/4 or high-OEB systems where containment failure carries severe consequences, a robust in-operation PQ is typically expected because both risk and operator interaction are inherently high. In all cases, ICH Q9(R1) guidance supports calibrating test scope to the likelihood and consequence of failure during actual use.
Q: How do we balance selecting a surrogate that closely represents our actual compound against the need to avoid introducing contamination or safety risk during PQ?
A: Choose the safest surrogate that still matches your actual API or agent in particle size, handling characteristics, and detection limit. The SMEPAC guideline provides several placebo options; document the scientific rationale for your choice. If you are comparing suppliers, ensure they all used the same surrogate under comparable test conditions, otherwise the performance data cannot be meaningfully compared.
Q: Is the extra coordination and time for representative, in-operation PQ always justified, or can a well-executed at-rest OQ pass audits just as well?
A: It is not always justified. If your containment claim is essentially static—such as a permanently sealed barrier with no routine operator access—and operator interventions are rare and low-risk, at-rest OQ with a documented risk rationale may be defensible. However, when operator workflows, load variability, or frequent interventions define the containment performance, the cost of in-operation PQ is minor compared to the audit and safety exposure of an unsubstantiated claim.
