Most procurement teams requesting a quote for a VHP pass box specify chamber volume, door configuration, and material finish — and receive a supplier response that answers exactly those questions while leaving the qualification-critical details unresolved. The gap rarely surfaces until FAT or early qualification runs, when the intended load fits physically but the cycle distribution is inadequate, the control system exports data in a format the facility’s DMS cannot accept, or the validation responsibility matrix turns out to be blank. Retrofitting cycle data requirements after the controls architecture is built is expensive and time-consuming; redefining door interlock logic post-installation can require a full requalification of the safety case. The checklist that follows is structured around the decisions that are hardest to recover from once the equipment is built — so that what gets specified in the RFQ matches what the facility actually needs to qualify, operate, and defend at inspection.
Chamber Size by Validated Load and Clearance
Chamber sizing is one of the earliest decisions in a VHP pass box procurement and one of the most frequently underspecified. The failure mode is straightforward: a facility quotes nominal internal volume, the supplier builds to that dimension, and the chamber physically accepts the intended load — but the load geometry restricts airflow and H₂O₂ distribution enough that cycle performance across the full load envelope cannot be verified. The unit passes visual inspection and basic commissioning checks, and the problem only becomes visible during biological indicator runs when kill performance at load surfaces is inconsistent.
The underlying issue is that nominal internal volume says nothing about how a specific load fits within the chamber, how much clearance remains for adequate gas circulation around all surfaces, or whether the load can be introduced and removed without breaching the cleanroom boundary. A chamber that is sized from the largest validated load plus the handling clearance required to load and unload it safely is a different design constraint from one sized to a round-number volume.
The RFQ should request that the supplier confirm the maximum validated load dimensions they have tested the chamber against, the clearance available on all sides of that load, and whether trolley or rack geometry was included in the original validation envelope. If the facility’s load is not yet defined at RFQ stage, that is the first problem to resolve — because cycle parameters, sensor placement, and biological indicator positions all depend on the load being fixed.
| Specification Approach | What It Overlooks | Wat verduidelijken |
|---|---|---|
| Nominal internal volume only | Ignores load geometry and handling clearance | Ask for the largest validated load dimensions and the required clearance the chamber can accommodate |
| Load‑defined sizing (largest validated load + clearance) | Depends on accurate load documentation | Confirm the maximum size of the load that can be presented, including trolley or rack handling room |
The distinction in the table is not academic. A chamber sized only on nominal volume may satisfy a line item in the purchase specification while producing a qualification program that requires cycle re-development once the actual load is introduced.
Door Interlocks Across Loading Exposure and Aeration
Door interlock requirements for a VHP pass box span three operationally distinct phases, and the failure risk at each phase is different. Treating them as a single specification line — “interlocked doors, both sides” — is a known source of controls architectures that protect one condition but not another.
During loading, the relevant risk is cleanroom boundary integrity and personnel safety. The interlock must prevent the cleanroom-side door from opening if a cycle has been initiated, is in progress, or has ended without completing aeration to endpoint. The consequence of a gap here is operator exposure to residual H₂O₂ or an uncontrolled pressure event across the boundary. During the exposure phase, the risk is cycle integrity: any door opening — even momentary — interrupts the concentration profile and may invalidate the run. ISO 22441:2022 provides a process reference for the importance of controlled access during active VHP cycles, and the RFQ should ask specifically how the supplier’s interlock logic handles an attempted override during exposure, and whether that override event is logged with user identity and timestamp.
Aeration presents a third and often underspecified condition. The interlock on the unclean-side door should not release simply because the exposure phase has ended — it should release only when aeration has reached the validated endpoint, typically confirmed by a H₂O₂ concentration sensor reading below a defined residual threshold. The RFQ should ask what that endpoint criterion is, how it is measured, and what happens if the sensor fails to confirm the endpoint within a defined time window. An interlock that releases on a timer rather than a confirmed sensor reading represents a qualitatively different safety and compliance posture.
| Cyclusfase | Interlock Must Protect | Wat bevestigen? |
|---|---|---|
| Loading | Cleanroom boundary and personnel safety | Door can open only when chamber is safe and no active cycle; alarms if door is open at incorrect time |
| Exposure | Cycle integrity and containment | Interlock prevents opening during decontamination; any override requires justification and logged event |
| Beluchting | Controlled containment until endpoint | Interlock releases only after aeration endpoint is reached and verified; early‑release consequence is defined |
Override capability is sometimes treated in supplier documentation as a minor operational feature rather than a safety and audit event. The RFQ should define that any override during exposure or aeration requires a logged justification and that such events are accessible to QA-level user roles without requiring IT or supplier involvement.
Cycle Data Sensors Alarms and User Access
Specifying cycle data requirements after the controls system is designed is among the most expensive corrective actions in a pass box procurement. Data format, field structure, timestamp resolution, sensor layout, alarm log configuration, and user access tiering are all decisions baked into the controls architecture early. Requesting them at FAT — or discovering at IQ that the system exports in a proprietary format incompatible with the facility’s audit trail infrastructure — typically means a controls change order, a delayed validation schedule, and a re-run of at least part of the FAT protocol.
The RFQ should name specific data requirements rather than request “full cycle data.” That means defining the required export format, the minimum timestamp granularity acceptable for regulatory review, and the explicit data fields that must appear in every cycle record. ASTM E3116 provides a useful testing-framework reference for understanding which sensor positions and data points are relevant to cycle performance verification — and the RFQ should ask the supplier to provide a sensor layout diagram with rationale for each sensor position, not just a count of sensors installed.
Alarm records deserve equal attention. An alarm log that records alarm type and time but does not capture resolution action or the identity of the operator who acknowledged it will create a defensibility gap at inspection. The RFQ should ask for retention period, export format, and whether the alarm record includes free-text or coded resolution fields.
| Item | What It Covers | What to Request in the RFQ |
|---|---|---|
| Cycle data format | Structure, content, and export of cycle records | Specify required file format, timestamp granularity, and which data fields must be logged |
| Sensor locations | Placement of temperature, humidity, and H₂O₂ sensors | Request a sensor layout diagram and rationale for chosen positions |
| Alarm records | Log of alarms with time, type, and resolution | Confirm retention period, export capability, and whether alarm rationale is included |
| User access levels | Roles, permissions, and login control | Define required access tiers (e.g., admin, operator, maintenance) and audit trail expectations |
User access tiering is frequently specified too loosely at RFQ stage — “admin and operator roles” without defining what permissions each role carries, whether maintenance access is a distinct tier, or how login events are captured in the audit trail. A facility that discovers post-installation that maintenance-mode access can modify cycle parameters without generating a change record has a data integrity problem that may require a software revision and requalification, not just a procedural control.
Chamber Materials Seal Design and Maintenance Records
Chamber material selection and seal design are engineering trade-offs with direct lifecycle and maintenance consequences, and they are often reviewed too late in the procurement process. The relevant questions are not only whether the material is VHP-compatible in principle, but how the chosen surface finish and construction method affect the uniformity of H₂O₂ distribution, the rate of concentration decay during the cycle, and the ease of routine decontamination between runs.
Electropolished stainless steel interior surfaces are a common and defensible choice for VHP chamber construction, but the RFQ should ask specifically about welded seam treatment, internal corner geometry, and any recesses or blind spaces in the chamber interior that may create shadows in H₂O₂ distribution. These are not abstract concerns — they determine where biological indicators must be placed to represent worst-case positions during qualification, and if the supplier has not characterized them, that work falls to the facility.
Seal design is where maintenance lifecycle risk concentrates. Door seals exposed to repeated VHP cycles will degrade over time, and the rate of degradation depends on seal material, H₂O₂ concentration range, and cycle frequency. The RFQ should ask for the manufacturer’s recommended seal inspection interval, replacement procedure, and whether seal replacement requires the chamber to return to the supplier or can be performed on site by facility maintenance staff. A seal that requires specialist tooling or factory service to replace creates a routine maintenance dependency that affects facility operational continuity and should be reflected in lifecycle cost modeling before procurement.
Maintenance records that arrive with the equipment — baseline seal condition, surface finish inspection, sensor calibration certificates — matter at qualification and at every subsequent periodic review. Equipment delivered without these baseline records creates a documentation gap that QA will need to close before IQ can proceed, and in some cases before the equipment can be placed in service at all. The RFQ should specify which maintenance and calibration records are expected at delivery and confirm that they arrive with the equipment, not as a post-delivery action item.
BI CI Strategy and FAT Documentation
Biological and chemical indicator strategy is frequently left to the supplier as a default rather than defined by the facility in the RFQ — and this ambiguity consistently creates ownership disputes at the qualification stage. The practical question is not whether BI/CI testing will occur, but who selects the BI type and load, who determines placement positions, who interprets results, and who is responsible for retesting if a run fails. A supplier quote that includes “BI testing” without specifying these responsibilities has not resolved the question; it has deferred it to a point in the project where schedule pressure makes renegotiation difficult.
ASTM E3116 provides a testing-framework reference for BI/CI methodology and FAT structure in VHP equipment. The RFQ should ask the supplier to describe how BI positions are selected relative to the validated load geometry — specifically whether worst-case positions are identified from H₂O₂ distribution mapping data or from a generic placement protocol applied across all chamber configurations. These are not equivalent approaches, and the distinction matters when the qualification program is reviewed.
FAT documentation scope is the other common underspecification. A FAT checklist that confirms door interlock function, cycle completion, and data export without establishing acceptance criteria tied to the facility’s specific operating parameters leaves the FAT as a supplier-conducted equipment check rather than a facility-relevant performance verification. The RFQ should define what acceptance criteria apply at FAT, whether the facility’s QA team or an independent party will witness the FAT, and what documentation is required before the equipment releases for shipment. Equipment that arrives on site with FAT records that do not reference facility-specific parameters will typically require additional commissioning work that could have been performed at the factory with lower cost and time impact.
Supplier Validation Scope in the RFQ
The most consequential omission in a VHP pass box RFQ is often not a technical specification — it is a failure to define which validation activities the supplier’s scope includes and which remain the facility’s responsibility. When this is unresolved at procurement, the facility discovers the gap at a project stage where filling it requires either unbudgeted internal resource or a change order that extends both cost and schedule.
A supplier quote that describes equipment delivery, installation support, and “full documentation package” without specifying which qualification activities are included, which are available at additional cost, and which are outside scope entirely has told the facility very little. The facility’s QA and validation teams, EHS leads, and project managers should all be able to read the quote and identify exactly what they are responsible for.
Scope ambiguity in this area produces three consistent failure patterns: a facility that has not planned or budgeted for OQ execution discovers this at IQ close-out; BI/CI responsibility is assumed by both parties to belong to the other until a failed run forces the question; or FAT documentation arrives with gaps that require the supplier to return to site for additional commissioning work, adding weeks to the schedule.
| Validatieactiviteit | What the Quote Should Address | Risico indien onduidelijk |
|---|---|---|
| Installatiekwalificatie (IQ) | Who performs IQ, site preparation, and utility readiness | Facility may be unprepared or installation may be delayed |
| Operationele kwalificatie (OQ) | OQ test parameters, acceptance criteria, and responsibility | Cycle may not be validated against the facility’s specific requirements |
| Biological/Chemical Indicator (BI/CI) testing | BI/CI placement, interpretation, and responsibility for retesting | Unclear ownership can delay release and compliance |
| Factory Acceptance Test (FAT) documentation | Scope of FAT, acceptance criteria, and on‑site support if needed | Equipment may arrive with unverified performance under field conditions |
The RFQ should request that the supplier’s response explicitly addresses each of the four validation activities in the table — not as a general statement of support, but as a description of what the supplier will deliver, when, and to what acceptance criteria. Where the supplier’s scope ends and the facility’s begins should be unambiguous in the quote, so that it can be reflected accurately in the facility’s validation master plan before the purchase order is issued.
For facilities reviewing generator integration alongside the pass box procurement, the VHP waterstofperoxidegenerator type I en Draagbare VHP waterstofperoxidegenerator (Type II, Type III) pages include configuration information relevant to cycle parameter alignment — particularly where the generator is supplied separately from the pass box and interface validation scope needs to be assigned in the RFQ.
The decisions that determine whether a VHP pass box procurement delivers a qualifiable, inspection-ready system are almost all made before the purchase order is issued. Chamber sizing against a defined validated load, interlock logic specified across all three cycle phases, cycle data and alarm requirements defined before controls are built, material and seal choices reviewed against maintenance lifecycle, BI/CI ownership assigned to a named party, and validation scope documented without assumption — these are the items that tend to drift when the RFQ treats them as details rather than governing specifications.
Before issuing or evaluating a supplier response, the facility’s procurement team should be able to confirm that each of these areas has a clear answer in the quote — not as a general capability claim, but as a defined deliverable with named responsibility. For teams preparing the RFQ document itself, Welke validatiedocumentatie moet worden gevraagd van VHP-fabrikanten vóór de RFQ? sets out the documentation baseline that should accompany any technically credible supplier response.
Veelgestelde vragen
Q: What if the facility’s validated load is not yet defined when the RFQ needs to go out?
A: The RFQ should not be issued until the load is fixed. Chamber sizing, sensor placement, biological indicator positions, and cycle parameter development all depend on a defined load geometry — issuing an RFQ against an undefined load produces a quote that cannot be meaningfully evaluated for qualification readiness. If procurement schedule pressure requires early engagement with suppliers, the RFQ should explicitly flag that load definition is pending and request that the supplier describe how the design accommodates late load confirmation without triggering a controls or chamber change order.
Q: Does the advice in this article apply equally when the VHP generator is supplied by a different vendor than the pass box?
A: Split-supply configurations introduce an additional scope boundary that the article’s guidance does not fully resolve. When the generator and pass box come from different suppliers, interface validation — including concentration delivery, sensor integration, and alarm routing between the two systems — must be explicitly assigned in both RFQs. Neither supplier will assume ownership of the interface by default, and a validation master plan that does not name a responsible party for interface OQ will surface this gap at a stage where it delays qualification rather than procurement.
Q: At what point does adding more sensors in the chamber stop improving cycle verification and create a data management problem instead?
A: Sensor count becomes counterproductive when it generates more data than the facility’s qualification protocol can interpret against defined acceptance criteria. The value of each sensor position depends on whether it corresponds to a worst-case location for the validated load — additional sensors placed without distribution mapping rationale add raw data without adding qualification defensibility. The RFQ should ask the supplier to justify each sensor position relative to load geometry rather than simply maximising sensor count.
Q: Is a timer-based aeration endpoint acceptable for any load or cleanroom classification, or is a sensor-confirmed endpoint always required?
A: A timer-based endpoint may be technically permissible in lower-risk configurations, but it represents a weaker compliance posture in any environment subject to regulatory inspection. A timer assumes that aeration performance is consistent across all loads, ambient conditions, and seal states — assumptions that a sensor-confirmed residual reading does not require. For facilities operating under pharmaceutical GMP expectations or working adjacent to personnel-occupied cleanrooms, a sensor-confirmed endpoint is the defensible standard; a timer-based release should be explicitly justified in the URS and risk assessment rather than accepted as a default supplier configuration.
Q: How should a facility weigh a lower-cost supplier quote that omits validation support against a higher-cost quote that includes OQ execution?
A: The comparison is only meaningful once the facility has costed the gap itself. A quote that excludes OQ execution is not cheaper if the facility lacks internal validation resource and will need to contract it separately — at rates and timelines that are typically less favourable than those negotiated at equipment procurement. The relevant question is whether the facility can resource and schedule OQ internally without affecting the site’s broader validation workload. If it cannot, the delta between quotes underestimates the true cost difference, and the lower-cost option carries schedule risk that should be reflected in the business case before the purchase order is issued.
