A cRABS integration package usually looks settled until someone asks who owns the inlet air condition, the pressure sensor, and the alarm that follows it. The barrier’s classification claim does not answer that question; the protection objective, the operating states, and the surrounding room conditions have to be defined first. Owners and equipment suppliers tend to disagree less about hardware than about which party supplies each design input, control signal, and piece of verification evidence. Drawing the boundary during package definition is usually cheaper than drawing it during commissioning, when both systems are installed and change control applies to both.
Define the Required Conditions at the cRABS Critical Zone
Before any line is drawn between the building air system and the barrier, the project needs a shared statement of what the critical zone has to achieve and under which conditions. That statement begins with the exposed-product operations involved, the protection objective for the critical zone, the supporting background environment, and the intervention states the barrier is expected to accommodate — including states that occur during routine operation, not only at rest.
The regulatory reference point is general rather than project-specific. EU GMP Annex 1 describes RABS as maintaining Grade A conditions with unidirectional airflow and first-air protection in an applicable sterile-manufacturing context. That description supports defining critical-zone protection, supporting background, unidirectional airflow, first air, pressure relationships, airflow studies, monitoring, and alarms, and it frames how facility HVAC interacts with the barrier. It does not specify whether the facility or the cRABS supplies any given function, does not define project setpoints, does not validate an active or passive concept, and does not establish performance for a particular installation.
The practical consequence is that the guidance text cannot serve as a design deliverable. Setpoints, airflow-study acceptance, intervention definitions, and the conditions to be demonstrated later remain project confirmations, and they belong in the same document that records which system is expected to deliver them.
Map Which Air Functions Come From the Facility and Which From the cRABS
The facility–barrier split is a project choice before it is a supply question. Qualia Bio’s current background records two first-party product concepts for cRABS air: passive use of facility air, and an active configuration with an independent air-handling unit, both reachable through the Closed Restricted Access Barrier System – cRABS entry point. These concepts frame the comparison; the actual arrangement and its capability remain subject to project confirmation against the application.
A workable way to test either concept is to walk each air function through the same worksheet, leaving the assignment column open until the project confirms it.
| Air function | Existing evidence to review | Boundary decision to confirm |
|---|---|---|
| Air source and conditioning | Facility system description and proposed cRABS concept | Which system provides the required inlet condition in each operating state |
| Filtration and distribution | Existing terminal arrangement and proposed internal air path | Where filtration and distribution scope changes hands |
| Return or exhaust path | Current room air path and proposed barrier discharge route | How air leaves the cRABS and interacts with the facility |
| Pressure influence | Room relationships, sensors, and control sequences | Which system influences each pressure relationship and how conflicts are avoided |
| Monitoring and alarms | Existing points, signals, records, and ownership | Which party provides, receives, retains, and reviews each item |
| Verification and maintenance | Site quality strategy, test needs, and access responsibilities | Who supplies evidence and support for project-defined checks and service |
The tracing matters more than the labelling. For each row, follow the air from supply through filtration and distribution to return or exhaust, note where the boundary changes hands, and record which functions condition the air and which only influence pressure. Failure dependencies belong in the same trace: if the facility system stops, trips, or loses a control signal, the project should be able to state which functions the barrier still performs and which it does not — and that answer may differ between a passive and an active concept. Qualia Bio’s discussion of cRABS air systems applies the same separation between barrier air functions and conditions or services supplied by the building HVAC system.
Assign Interface Design, Control, and Verification Responsibilities
For every air function identified, the interface package needs named roles rather than shared assumptions: who supplies the design input, who supplies and installs the hardware, who provides the power or utility connection, who emits and receives the control signal, where the monitoring point sits, who handles the alarm, who supports testing, who retains records, and who approves the result. ASTM E2500-25 supports treating process equipment, supporting utilities, associated monitoring and control systems, and automation as linked elements through specification, design, installation, operation, performance, and verification. It does not allocate contractual scope, signal ownership, test responsibility, or acceptance criteria; those remain project decisions to be negotiated and recorded.
The distinction matters most where a single air function is delivered jointly. A room pressure relationship, for example, may be influenced by facility supply and return, by the barrier’s internal air path, and by door and intervention states. Assigning the sensor to one party does not assign the control action, the alarm response, or the evidence. A monitoring point can likewise be installed by one supplier while the setpoint, alarm logic, and data retention are owned by another.
A useful test for an interface matrix is whether each row survives a change of supplier. If moving one function from the facility scope to the barrier scope forces a rewrite of assumptions about controls, alarms, records, or test support, the boundary was never fully defined.
Record Shared Assumptions and Unresolved Boundaries
Some functions will remain unresolved at contract stage, and that is workable provided the open items stay visible. Room pressure relationships, operating modes, door and intervention states, maintenance access, and change control are typical candidates, because they depend on both systems and often on the user’s operating practice rather than on any single equipment supply.
An open boundary item needs one stated assumption, one evidence owner, and one resolution step; without them it will be absorbed into whichever supply package is convenient.
Without those three elements, an unresolved function tends to be absorbed into the equipment package by default and reappears later as a commissioning discrepancy. Where the responsibility is already shared, Qualia Bio’s discussion of managing pressure in cRABS frames pressure-control assumptions and verification responsibilities as items to settle at the facility boundary rather than inside one package.
Change control deserves explicit treatment at that boundary. A later modification to the building air system, to the barrier’s internal configuration, or to the room pressure strategy can shift the effective boundary even when the hardware and the contract have not changed. The assumptions and evidence ownership recorded earlier should therefore be reviewed whenever one side of the boundary is altered.
Frequently Asked Questions
Q: Should the air-scope boundary follow the physical edge of the cRABS enclosure?
A: Define it by function and interface rather than the enclosure edge alone. Air supply, filtration, distribution, return or exhaust, pressure influence, controls, and monitoring can involve both systems, so each function needs an explicit project boundary.
Q: What is the practical difference between passive and active air concepts for scope planning?
A: The recorded passive concept uses facility air, while the active concept includes an independent air-handling unit. Compare how each proposed concept obtains its air conditions and interacts with the room; the actual arrangement, remaining facility dependencies, and capability need project confirmation.
Q: Does an independent air-handling unit remove the need to review facility HVAC?
A: Facility interfaces still need review. Trace the proposed air discharge route, room-pressure relationships, operating states, utility connections, and failure dependencies to determine which building conditions remain relevant to the active concept.
Q: How should shared pressure and alarm functions be handled in the scope discussion?
A: Give each shared function a stated assumption, an evidence owner, and a resolution step. Identify which system influences the pressure relationship and which parties provide, receive, retain, and review monitoring or alarm information so the boundary remains visible.
Q: What should be agreed beyond the air-system hardware supply?
A: Agree the design-input, control-signal, monitoring, verification-support, maintenance-access, record, and approval boundaries. These decisions connect the equipment package to the conditions the project intends to demonstrate without assuming that all supporting work belongs to one supplier.
