Cytiva portfolio vs. QB Control
Cytiva portfolio vs. QB Control
Connectivity, data exchange & control capabilities
Cytiva vs QB Control
Flexible. Innovative. Limitless.
CONFIDENTIAL Disclaimer & Confidentiality Notice
For Danaher/Cytiva Recipients Only. This document has been prepared by QB Systems (A4BEE Sp. z o.o.) for the exclusive use of Danaher Corporation and Cytiva personnel. The contents are confidential and should not be distributed, reproduced, or shared with third parties without prior written consent from QB Systems.
Basis of Analysis: The information regarding Cytiva solutions presented in this document has been compiled entirely from publicly available sources, including published product datasheets, technical manuals, installation guides, application notes, and press releases accessible via cytivalifesciences.com and third-party industry publications. The information regarding QB Systems solutions (QB Control, QB Modules, and related products) is based on internal A4BEE documentation, product catalogs, and technical specifications.
No Warranty: While every effort has been made to ensure accuracy, this analysis is provided "as-is" for informational and strategic evaluation purposes. Product specifications, pricing, and capabilities may change without notice. QB Systems makes no representations or warranties regarding the completeness or accuracy of Cytiva product information, which should be independently verified with Cytiva for any procurement or integration decisions.
QB Systems → Cytiva Connectivity Map
This document is a QB Systems connectivity map into the Cytiva bioprocessing portfolio — it identifies, for every Cytiva system (bioreactors, chromatography, filtration, cell therapy, enterprise automation), which QB product connects , via which QB-native protocol , and what data and control flows in each direction. It is not a generic survey of Cytiva's connectivity options. Each Cytiva system is analyzed through a single lens: how QB Systems reaches it.
Five QB-native connection paths cover the entire portfolio: (1) MTP — native on Figurate DCS and native across all QB products; (2) OPC UA dual-mode — reading ÄKTA/WAVE/Figurate and exposing QB data back; (3) Modbus — direct to Xcellerex sensors and legacy devices; (4) REST/MQTT bridge — for any IT-layer, LIMS, ELN, or cloud target; (5) protocol-translation gateways — for EtherNet/IP, PROFIBUS, OPC DA, and Pall Link endpoints.
1 Executive Summary
Cytiva (a Danaher company) operates one of the broadest bioprocessing portfolios in the industry, spanning bioreactors, chromatography, filtration, cell therapy, and enterprise automation. This document assesses how QB Systems connects to each Cytiva product line — Xcellerex, ÄKTA, ReadyToProcess WAVE, iCELLis, Sefia, FlexFactory, and Figurate — and identifies the specific QB-native path that establishes the bridge in every case.
There is no Cytiva system in scope without a QB connection path. The strongest alignment is at the MTP layer : Cytiva's Figurate DCS supports MTP natively, and QB Systems are natively MTP-capable across all products — which means QB units plug into Figurate-controlled facilities as first-class modules without middleware, custom engineering, or protocol translation. For systems without MTP exposure, QB Control's dual-mode OPC UA (client + server), native Modbus , and REST/MQTT stack cover direct integration; residual endpoints (OPC DA, EtherNet/IP, PROFIBUS, Pall Link) are reached via QB protocol-translation gateways. The result: QB Systems functions as the unifying connectivity fabric across Cytiva's multi-protocol portfolio.
2 Cytiva Product Portfolio Overview
| Category | Key Product Lines | Scale Range | Primary Application |
|---|---|---|---|
| Stirred-Tank Bioreactors | Xcellerex XDR, X-platform | 10 L – 2,000 L | Cell culture, upstream bioprocessing |
| Rocking Bioreactors | ReadyToProcess WAVE 25 | 0.1 L – 25 L | Seed train, cell expansion |
| Fixed-Bed Bioreactors | iCELLis Nano/500 | Nano – 500 m² | Adherent cell culture, viral vectors |
| Chromatography Systems | ÄKTA pure, process, ready, pcc | Lab – production | Protein purification, downstream |
| Filtration Systems | ÄKTA flux, readyflux, readyflux XL | Lab – manufacturing | TFF, UF/DF, cross-flow filtration |
| Cell Therapy Platforms | Sefia S-2000, Select, Expansion | Clinical manufacturing | CAR-T, cell processing, gene therapy |
| Enterprise Automation | FlexFactory, Figurate DCS, Chronicle | Facility-wide | DCS, MES integration, batch records |
3 Cytiva Systems Connectivity Analysis
3.1 Xcellerex X-Platform Bioreactors (Stirred-Tank)
Control Architecture: Figurate automation platform powered by Rockwell PlantPAx DCS or Emerson DeltaV DCS. HMI panel for local operation.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| Modbus TCP | None — direct network access to Xcellerex sensor subsystem | — QB Control speaks Modbus TCP directly | |
| EtherNet/IP | EtherNet/IP scanner (internal subsystem bus) | — EtherNet/IP-to-OPC UA bridge | |
| OPC DA/UA | Figurate DCS (Rockwell PlantPAx or Emerson DeltaV) required as intermediary layer | — QB Control OPC UA Client via Figurate | |
| Wireless | Vendor-specific probe calibration handshake; local instrument only | — calibration data ingested via REST adapter |
Direct device control: Not available from external systems. All control commands must pass through the Figurate DCS layer (PlantPAx or DeltaV). Data extraction: Available via Modbus TCP (sensor-level) and OPC DA/UA (DCS-level). No native REST API, MQTT, or modern IT-protocol access.
3.2 ReadyToProcess WAVE 25 (Rocking Bioreactor)
Control Architecture: Embedded Process Controller (EPC) with local HMI. UNICORN software for method programming and execution.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| OPC DA | Pre-installed OPC DA server on EPC; no additional hardware | — via OPC DA-to-UA protocol translation | |
| OPC UA | UaGateway software (separate install on client PC) | — QB Control OPC UA Client | |
| OPC UA Tunneller | Additional OPC Tunneller software for firewall traversal | — not required for local network |
Remote control: Possible via OPC DA from SCADA/DCS systems, but requires explicit SCADA infrastructure configuration. Data extraction: Natively available via OPC DA server on the EPC. OPC UA requires additional UaGateway software. No native MQTT or REST API.
3.3 iCELLis Fixed-Bed Bioreactors
Control Architecture: mPath Control Tower with Pall Link software for system management and control.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| Pall Link (proprietary) | Pall Link Server (Cytiva-supplied); closed proprietary protocol | — via Pall Link Server OPC DA exposure (read-only) | |
| OPC DA | Pall Link Server exposing OPC DA endpoint; read-only | — OPC DA-to-UA protocol translation | |
| Ethernet | Transport layer only; Pall Link runs over it | — used as carrier for OPC DA translation path (see above) |
Proprietary Pall Link protocol creates vendor lock-in. Limited interoperability with non-Cytiva systems. No standard industrial protocol for external write access.
3.4 ÄKTA Chromatography Systems
Control Architecture: UNICORN software (versions 5.x through 7.6) running on dedicated workstation or EPC. All ÄKTA systems share UNICORN as common control platform.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| OPC DA | Pre-installed on UNICORN EPC; OPC Security configuration required | — OPC DA-to-UA translation | |
| OPC UA | UNICORN 7.x licensed OPC UA add-on (separate purchase) | — QB Control OPC UA Client (requires UNICORN license) | |
| EtherNet/IP | ÄKTA process EtherNet/IP gateway module (optional) | — EtherNet/IP-to-OPC UA bridge | |
| PROFIBUS | Optional ÄKTA process PROFIBUS DP node; PROFIBUS master required | — PROFIBUS-to-OPC UA bridge | |
| File export (ZIP) | Offline; UNICORN workstation file-system access required | — file-ingest adapter for LIMS/ELN (batch/historical only) |
Remote control: Available via OPC DA for authorized SCADA/DCS clients. Requires UNICORN OPC Security configuration. Data extraction: Rich data via OPC DA/UA (real-time) and ZIP file export (batch/historical). OPC UA is separately licensed. UNICORN is Windows-only.
3.5 ÄKTA Filtration Systems
Control Architecture: UNICORN software for method creation, system control, and process evaluation. Same platform as chromatography systems.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| OPC DA | Pre-installed on UNICORN EPC; OPC Security configuration required | — OPC DA-to-UA translation | |
| OPC UA | UNICORN 7.x licensed OPC UA add-on (separate purchase) | — QB Control OPC UA Client (requires UNICORN license) | |
| PROFIBUS | Optional PROFIBUS DP node; PROFIBUS master required | — PROFIBUS protocol-translation gateway |
3.6 Sefia Cell Therapy Platform
Control Architecture: Integrated instrument controller with Chronicle automation software overlay for facility-wide orchestration.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| Chronicle (proprietary) | Chronicle server (Cytiva-supplied); closed orchestration layer | — via Chronicle MES/LIMS export hooks | |
| Ethernet | Instrument telemetry and alarm feed on local network | — via TCP/IP ingest adapter | |
| Third-party integration | Chronicle middleware license + custom integration configuration; typical MES/LIMS/QMS bridging | — via REST API connectors |
Chronicle is a closed ecosystem. Integration with non-Cytiva instruments requires custom configuration. Not designed for real-time external API access.
3.7 FlexFactory & Figurate Enterprise Automation
Control Architecture: Figurate DCS platform, available for Rockwell PlantPAx, Emerson DeltaV, and Siemens PCS 7.
| Protocol | Options | Requirements | QB Systems Integration |
|---|---|---|---|
| MTP (NAMUR NE 148) | Native on Figurate DCS orchestration layer; modular automation standard | — QB registers as PEA, no middleware | |
| OPC DA/UA | Primary DCS data exchange; no additional hardware | — QB Control OPC UA dual-mode (Client + Server) | |
| EtherNet/IP | Rockwell PlantPAx fieldbus (internal to DCS) | — EtherNet/IP-to-OPC UA bridge (optional direct path) | |
| PROFIBUS/PROFINET | Siemens PCS 7 fieldbus (internal to DCS) | — PROFIBUS/PROFINET-to-OPC UA bridge | |
| HART | HART multiplexer/gateway for smart-sensor diagnostics | — HART multiplexer to OPC UA | |
| Modbus TCP | Direct network access for legacy sensor/device data | — QB Control speaks Modbus TCP directly | |
| AVEVA PI | AVEVA PI System license (enterprise historian) | — QB OPC UA Server feeds PI directly | |
| MES/EBR interfaces | MES software license and integration configuration | — QB REST API or OPC UA |
Remote control: Full capability through DCS workstations. Remote access for Cytiva technician maintenance. Data extraction: AVEVA PI Historian provides enterprise-grade data aggregation. Key limitation: Requires full DCS infrastructure ($500K–$2M+). Massive overkill for lab/pilot scale.
4 Cytiva Systems Connectivity Matrix
| System | MTP | OPC DA | OPC UA | Modbus | EtherNet/IP | PROFIBUS | MQTT | REST API |
|---|---|---|---|---|---|---|---|---|
| Xcellerex X-platform | ||||||||
| WAVE 25 | ||||||||
| iCELLis | ||||||||
| ÄKTA Chromatography | ||||||||
| ÄKTA Filtration | ||||||||
| Sefia | ||||||||
| FlexFactory/Figurate |
Native = built-in, no extra cost Licensed = additional purchase Gateway = additional hardware/software or protocol translation Via = through intermediary layer — = not supported
5 Cytiva Systems Connectivity Options
5.1 The Critical Distinction
Collecting sensor readings and process parameters
Generating reports and trend analysis
Sending data to LIMS, ELN, or data historians
Monitoring alarms and equipment status
No ability to change process conditions
Changing setpoints (temperature, pH, DO, agitation)
Starting/stopping processes, methods, or recipes
Adjusting pump flow rates, valve positions
Executing automated sequences and batch recipes
Modifying alarm thresholds and safety interlocks
5.2 Cytiva's Three-Layer Control Hierarchy
5.2.1 Where QB Systems Plugs In at Each Layer
For most Cytiva systems, achieving remote control (Layer 2) traditionally requires a full DCS infrastructure. Without DCS, external systems can only perform data extraction (Layer 3). This creates a binary cost decision : either invest $500K+ in DCS infrastructure for full control, or accept read-only data access. QB Systems eliminates this binary by operating as a Layer-2 supervisory bridge itself — via MTP (into Figurate) or OPC UA dual-mode (into UNICORN, Figurate, WAVE EPC) — at a fraction of DCS cost, while simultaneously handling Layer-3 IT-protocol feeds natively.
5.3 Per-System Control Capability Summary
| System | Local Control | Remote Control | Data Extraction | QB Systems Access Route |
|---|---|---|---|---|
| Xcellerex X-platform | Full | Full (Figurate) | Modbus read-only | Modbus TCP (direct, native) + OPC UA via Figurate |
| WAVE 25 | Full | Full (OPC DA) | OPC DA read + file export | OPC UA Client via UaGateway (or QB OPC DA-UA translation) |
| iCELLis | Full | Limited (Pall Link) | OPC DA read-only | QB OPC DA-to-UA translation gateway (Read) |
| ÄKTA Chromatography | Full | Full (OPC DA) | OPC DA read + file export | OPC UA Client (licensed) or OPC DA-UA translation + REST webhooks |
| ÄKTA Filtration | Full | Full (OPC DA) | OPC DA read + file export | OPC UA Client + PROFIBUS translation gateway |
| Sefia | Full | Via Chronicle | Chronicle export | REST API via LIMS + Ethernet telemetry ingest |
| FlexFactory/Figurate | Full | Full (Figurate DCS) | AVEVA PI read | Native MTP (PEA) + OPC UA dual-mode (Read/Write) |
The QB access-route column identifies the concrete connection mechanism used by QB Control in each scenario. Every Cytiva system has at least one QB-native path; FlexFactory/Figurate is the strongest case (native MTP on both sides, zero middleware).
6 Cytiva and QB Systems Comparison
6.1 Architectural Philosophy
| Aspect | Cytiva Ecosystem | QB Control |
|---|---|---|
| Control architecture | 3-layer hierarchy: local → DCS → enterprise | Flat: browser-based portal directly controls all devices |
| Device connectivity | Per-device protocols (OPC, Modbus, EtherNet/IP, proprietary) | PoE auto-discovery — plug in, it appears |
| Software platform | UNICORN (Windows-only) + Figurate DCS + Chronicle | Browser-based portal (any device, any OS) |
| Protocol stack | OPC DA/UA, Modbus, EtherNet/IP, PROFIBUS (industrial) | MTP, MQTT, REST API, SQL, OPC UA, Modbus (modular + modern IT + industrial) |
| Modular plug-and-play (MTP) | Native on Figurate DCS | Native across all QB products — QB units register as PEAs directly into Figurate without middleware |
| Multi-vendor integration | Limited to Figurate-supported equipment | Native Hamilton, Mettler Toledo; extensible via MQTT/REST |
| Remote control path | Requires DCS infrastructure ($500K+) | Built into every installation (browser access) |
| Data access | OPC + file export + AVEVA PI historian | Native time-series database with export, REST API, real-time MQTT |
| GAMP classification | Category 5 (DCS = custom coded) | Category 4 (configurable) — 50–70% less validation |
6.2 Protocol Comparison
| Protocol | Cytiva | QB Control | Advantage |
|---|---|---|---|
| MTP (NAMUR NE 148, modular automation) | Native on Figurate DCS | Native across all QB products | Both supported natively — plug-and-play modular integration with zero middleware |
| OPC DA | Native on most systems | Supported with protocol translation (OPC DA-to-UA gateway) | Both supported — QB via translation |
| OPC UA | Licensed add-on or via gateway | Both supported — QB native, Cytiva licensed | |
| Modbus | Native on X-platform sensors | Both supported natively | |
| EtherNet/IP | Native on Xcellerex, ÄKTA process | Supported with protocol translation (EtherNet/IP gateway) | Both supported — QB via translation |
| PROFIBUS/NET | Available on ÄKTA and FlexFactory | Supported with protocol translation (PROFIBUS/NET gateway) | Both supported — QB via translation |
| MQTT | Not supported | QB Control | |
| REST API | Not supported | QB Control | |
| Time-series DB / data export | Not supported natively (requires AVEVA PI) | QB Control | |
| WebSocket | Not supported | Browser-based real-time | QB Control |
MTP (Module Type Package, per NAMUR NE 148 and VDI/VDE/NAMUR 2658) is the modern modular-automation standard that lets process equipment register as self-describing modules into an orchestrating DCS. Cytiva's Figurate DCS supports MTP natively , and QB Systems are natively MTP-capable across all QB products . This is the rare case where the two ecosystems align at the modern-standards tier rather than diverge — in a Figurate-controlled facility, QB units plug in as first-class PEAs without middleware, OPC UA gateways, or custom engineering. The table above lists MTP as the first row for exactly this reason: it is the deepest and cleanest integration path available.
6.3 Cost of Connectivity
| Scenario | Cytiva Cost | QB Control Cost |
|---|---|---|
| Single bioreactor, local control | $50K–150K | $15K–25K |
| 4-bioreactor lab, centralized monitoring | $300K–500K | $60K–85K |
| 4-bioreactor lab, remote control | $600K–1M+ | $60K–85K (included) |
| Pilot, 6–8 bioreactors, full automation | $1M–2.5M+ | $100K–250K |
| System integrator cost | $100K–300K per engagement | $0 (plug-and-play) |
| Annual software licensing | $20K–100K/year | $0 (perpetual license) |
7 QB Systems Products × Cytiva Products: Integration Analysis
This section maps concrete integration scenarios between specific QB Systems hardware/software products and specific Cytiva systems, with a heavy focus on OPC UA connector integrations (QB Control as both OPC UA client and server) and REST API-based integrations .
7.1 QB Systems Products for Integration
| QB Systems Product | Type | Integration-Relevant Capabilities |
|---|---|---|
| QB Bioreactor | Hardware + QB Control | Full sensor suite (pH, DO, temp, agitation), recipe execution, MQTT/REST/SQL output |
| QB Autosampler | Hardware + QB Control | Time/event-triggered sampling, syringe pump + selector valve, volume-controlled collection |
| QB Filtration System | Hardware + QB Control | Pump control, TMP monitoring, flux measurement, automated TFF/UF/DF sequences |
| QB Precise Dosing & Feeding | Hardware + QB Control | Gravimetric feeding, balance integration, PID control loops, feed strategy profiles |
7.2 OPC UA Integration Architecture
7.2.1 QB Control as OPC UA Client → Reading from Cytiva Systems
Per-Cytiva System: OPC UA Client Integration Details
| Cytiva System | OPC UA Server Source | Data Points (Read) | Complexity |
|---|---|---|---|
| ÄKTA pure/process | UNICORN 7.x OPC UA (licensed) | UV, conductivity, pH, pressure, flow rate, fractions, method status | Medium |
| ÄKTA readyflux | UNICORN 7.x OPC UA | TMP, flux, permeate flow, feed/retentate pressure, UV, conductivity | Medium |
| WAVE 25 | EPC OPC DA + UaGateway | Rocking rate, angle, temperature, DO, pH, bag volume, method status | Medium-High |
| Xcellerex X-platform | Figurate DCS OPC UA (or MTP via Figurate) | pH, DO, dCO&sub2, temp, agitation, gas mix, pressure | Low (MTP) / High (OPC UA) |
| FlexFactory/Figurate | Native MTP (primary) + Figurate DCS OPC UA | Facility-wide process data, batch states, alarms; QB registers as PEA | Low (native MTP on both sides) |
| iCELLis | OPC DA via Pall Link — reached via QB OPC DA-to-UA translation gateway | Temperature, pH, DO, gas flow, batch status | Medium (via QB translation) |
| Sefia | No OPC exposure — use REST via LIMS instead | Batch data via Chronicle/LIMS join | Medium (REST path) |
7.2.2 QB Control as OPC UA Server → Exposing Data to Cytiva/DCS
Key OPC UA Server Use Cases:
| Use Case | External OPC UA Client | Data Exposed | Direction |
|---|---|---|---|
| Unified facility view | Figurate DCS | All QB bioreactor, autosampler, filtration, dosing data | Read |
| Historian aggregation | AVEVA PI System | All QB process data with timestamps | Read |
| DCS supervisory override | Figurate DCS | QB setpoints for critical parameters | Write |
| Method coordination | UNICORN OPC Client | Autosampler status, filtration completion flags | Read |
| MES batch tracking | MES System | QB batch states, recipe phases, alarm events | Read |
7.2.3 Bidirectional OPC UA: Full Integration
7.2.4 Native MTP Alignment — The Deepest Integration Layer
Cytiva's Figurate DCS natively supports MTP (Module Type Package, NAMUR NE 148 / VDI/VDE/NAMUR 2658), the modern modular-automation standard that lets process equipment register as self-describing Process Equipment Assemblies (PEAs). QB Systems are natively MTP-capable across all products — QB Bioreactor, QB Autosampler, QB Filtration, and QB Precise Dosing each ship as MTP-enabled PEAs out of the box.
This is the strongest integration story in the entire document: for Figurate-controlled facilities, QB units plug in directly as first-class modules. No OPC UA server/client configuration. No middleware. No custom integration code. No gateway hardware. No DCS I/O engineering. The Figurate orchestration layer discovers the QB PEA, reads its MTP definition, and integrates it into batch recipes, supervisory control, and facility-wide sequencing automatically.
Practical implication: A pharma/biotech site running Figurate today can deploy QB Bioreactor or QB Autosampler modules and have them appear as orchestrated units within the existing Figurate facility — typically within hours of physical installation, versus weeks of engineering for OPC UA integration or months for custom DCS function-block development.
7.3 REST API Integration Scenarios
Real-time streaming of all connected device data to cloud and analytics platforms
Programmatic access: GET data, POST commands, PUT setpoints, trigger webhooks
High-frequency sensor data storage with built-in export (CSV, PDF), queryable via REST API for analytics, ML/AI, Power BI, Grafana
REST API × Cytiva Integration Scenarios:
| Scenario | How It Works | QB Product(s) | Cytiva Product(s) |
|---|---|---|---|
| Unified LIMS data | QB REST API pushes bioreactor/sampling data to LIMS; UNICORN ZIP exports parsed separately | QB Bioreactor, Autosampler | ÄKTA pure/process |
| Auto sampling → chromatography | QB Autosampler completes sample → REST webhook notifies orchestrator → triggers ÄKTA method via OPC UA | QB Autosampler | ÄKTA pure |
| Adaptive feeding | ML model reads QB Bioreactor data via REST API, calculates optimal feed rate, writes setpoint to QB Dosing via REST | QB Bioreactor, Dosing | Cytiva VCD probes via OPC UA |
| Cross-scale comparison | REST API exports QB pilot data; compared with Xcellerex production data extracted via OPC UA | QB Bioreactor | Xcellerex X-platform |
| Regulatory dossier | REST API pulls QB audit trail + batch reports; combined with Chronicle batch records | All QB products | ÄKTA, Sefia, Chronicle |
| Cloud dashboard | REST API streams to Grafana/Power BI; Cytiva data joins via OPC UA → QB → REST pipeline | All QB products | Any with OPC UA |
REST API vs. OPC UA: When to Use Which
| Criterion | OPC UA | REST API |
|---|---|---|
| Best for | Real-time process data between control systems | IT-layer: cloud, LIMS, ELN, analytics |
| Latency | Milliseconds (subscription-based) | Seconds (request/response or webhook) |
| Security | X.509 certificates, OPC UA policies | HTTPS + API keys / OAuth |
| Firewall | Requires OPC UA port config | Standard HTTPS (443) — firewall-friendly |
| DCS integration | Native — DCS speaks OPC UA | Not native — requires custom work |
| LIMS/ELN integration | Not native | Native — REST is standard IT protocol |
| Cloud integration | Complex — needs UA cloud gateways | Simple — standard HTTPS calls |
7.4 Product-to-Product Integration Matrix
QB Bioreactor × Cytiva Systems
| Cytiva System | Protocol | Direction | Use Case |
|---|---|---|---|
| ÄKTA pure/process | OPC UA Client | Read | Display chromatography progress on bioreactor dashboard; correlate harvest → purification timing |
| ÄKTA readyflux | OPC UA Client | Read | Monitor downstream filtration (TMP, flux) alongside upstream bioreactor data |
| WAVE 25 | OPC UA Client | Read | Seed train monitoring — track expansion in WAVE alongside inoculation into QB Bioreactor |
| Xcellerex | OPC UA Client (via Figurate) | Read | Scale comparison: production Xcellerex data alongside QB pilot bioreactor data |
| Figurate DCS | OPC UA Server | Read/Write | DCS incorporates QB bioreactor into facility view; optional DCS override of setpoints |
QB Autosampler × Cytiva Systems
| Cytiva System | Protocol | Direction | Use Case |
|---|---|---|---|
| ÄKTA pure | OPC UA + REST webhook | Bidirectional | Autosampler takes sample → webhook triggers ÄKTA analytical method → results read back via OPC UA |
| Sefia | REST API (via LIMS) | Read | Cell therapy process samples pushed to LIMS; join with Sefia batch records |
| Figurate DCS | OPC UA Server | Read | DCS monitors sample count, timing, and sequence status in production supervisory view |
QB Filtration System × Cytiva Systems
| Cytiva System | Protocol | Direction | Use Case |
|---|---|---|---|
| ÄKTA pure/process | OPC UA bidirectional | Coordinated | QB Filtration completes UF/DF → flag read by ÄKTA → automatic capture chromatography start |
| ÄKTA readyflux | OPC UA Client | Read | Side-by-side comparison of QB vs. Cytiva TFF for scale-down model validation |
| Xcellerex | OPC UA Client (via Figurate) | Read | Monitor harvest from Xcellerex → auto-start QB clarification when harvest complete |
| Figurate DCS | OPC UA Server | Read/Write | DCS includes QB Filtration in facility batch sequence; can override pump speeds |
QB Precise Dosing & Feeding × Cytiva Systems
| Cytiva System | Protocol | Direction | Use Case |
|---|---|---|---|
| Xcellerex X-platform | OPC UA Client + QB write | Read → Calculate → Write | Transformative: QB reads VCD/glucose from Xcellerex via OPC UA → calculates optimal feed rate → adjusts QB pump. Adaptive feeding for Cytiva bioreactors without DCS recipe modification |
| WAVE 25 | OPC UA Client + QB write | Read → Calculate → Write | QB reads culture parameters from WAVE → adjusts gravimetric feed for precise nutrient delivery during seed train |
| ÄKTA pure | REST API webhook | Event-triggered | QB Dosing adds buffer/reagent to chromatography prep tank based on ÄKTA method requirements |
| Figurate DCS | OPC UA Server | Read/Write | DCS monitors feed rates, total volumes, balance readings; can override feed strategy |
7.5 Complete Facility Integration Architecture
7.6 Coexistence Scenarios
| Scenario | Cytiva Role | QB Systems Role | Primary Protocol |
|---|---|---|---|
| Lab: ÄKTA + QB bioreactors | ÄKTA chromatography (UNICORN) | QB Bioreactor, Autosampler, Dosing + ÄKTA data on QB dashboard | OPC UA Client + REST |
| Pilot: Cytiva seed + QB production | WAVE 25 seed expansion | QB Bioreactor production, QB Filtration harvest, QB Dosing feeding | OPC UA Client |
| Pilot: Xcellerex + QB analytical | Xcellerex bioreactors (Figurate DCS) | QB Autosampler at-line sampling, QB Dosing supplemental feeding | OPC UA bidirectional |
| Facility: FlexFactory + QB lab | FlexFactory GMP production | QB Control for R&D/PD lab; data to AVEVA PI via OPC UA Server | OPC UA Server |
| CDMO: Multi-client | FlexFactory for client A (large mAb) | QB Control for client B (fast deploy, different process) | REST API (independent) |
| Cell therapy: Sefia + QB | Sefia cell processing | QB Bioreactor expansion, QB Dosing media feeding | REST API (via LIMS) |
8 Strengths Assessment
8.1 Cytiva Strengths
8.2 QB Systems Strengths
9 A4BEE Integration Experience & QB Control Integration Roadmap
A4BEE Sp. z o.o. (the company behind QB Systems) has accumulated extensive hands-on experience integrating a wide range of bioprocessing instruments and software platforms through its system integration projects for pharmaceutical, biotech, and CDMO clients. This experience forms the technical foundation for QB Control's 2026 integration roadmap.
The integrations listed below reflect A4BEE's proven project experience with these instruments and software platforms in broader system integration contexts. Not all of those integrations are available as a production-ready features in QB Control product. Many of the integrations are done per project basis and are reusing integration patterns and assets, informed by the practical knowledge gained through A4BEE's integration projects.
9.1 Bioreactor & Cell Culture Systems
| Vendor | Instrument / System | Software | Integration experience |
|---|---|---|---|
| Cytiva | GE ÄKTA | — | OPC UA client integration for ÄKTA UNICORN data readback |
| Emerson | Bioreactor controller (DCS) | DeltaV v13 | OPC UA client connector for DeltaV data points |
| Sartorius (Novasep) | BioSC (MCC) | iFix-based SCADA | OPC UA / Modbus connector development |
| Sartorius | AMBR | — | REST API / OPC UA data bridge |
| Sartorius | Bioreactors (3–70 L) | — | OPC UA client for Sartorius BioPAT data |
| Applikon | Bioreactors | — | OPC UA / Modbus connector |
| MilliporeSigma | Cellicon™ Perfusion | Controller Software (Embedded) | Embedded controller data bridge |
9.2 Analytical & Sampling Instruments
| Vendor | Instrument / System | Software | Integration experience |
|---|---|---|---|
| Merck Millipore | MAST (Automated Sampling) | MAST Connect | REST API / OPC UA connector for sampling coordination |
| Beckman Coulter | Vi-CELL Blu (Cell Counter) | Vi-CELL Blu v1.4.4.1 | REST API connector for automated cell count data |
| Roche | Cedex Bio HT (Metabolite Analyzer) | Cedex Bio HT Software | REST API / file-based connector for metabolite data |
| Nova Biomedical | FLEX2 | BioProfile FLEX Software | REST API connector for BioProfile data |
| Agilent | Liquid Chromatography (LC) | OpenLab CDS 2.7 | File-based / REST API connector for OpenLab CDS |
| Agilent | Mass Spectroscopy | — | File-based data import connector |
| Repligen (C Tech) | FlowVPX (Variable Pathlength UV) | Viper AnalytX | OPC UA / REST API connector |
| Endress+Hauser | Raman Rxn2 | — | OPC UA / Modbus connector for spectral data |
9.3 Filtration & Downstream Systems
| Vendor | Instrument / System | Software | Integration experience |
|---|---|---|---|
| Repligen | ATF C24U | Controller Software (Embedded) | Embedded controller / OPC UA data bridge |
| Flownamics | SegFlow (Automated Sampler) | Flow-Control | REST API connector |
9.4 Pumps, Sensors & Dosing Equipment
| Vendor | Instrument / System | Software | Integration experience |
|---|---|---|---|
| MasterFlex | Pumps | — | Modbus / RS-485 connector |
| Mettler Toledo | Various scales | — | |
| Mettler Toledo | Sensors | — | |
| Hamilton | pH Meter | — | |
| Hamilton | Sensors | — | |
| Pendotech | Sensors | — | OPC UA / Modbus connector |
| Sartorius | Scales | — | Modbus / RS-232 connector |
9.5 Automation Platforms & Software
| Vendor | System / Software | Type | Integration experience |
|---|---|---|---|
| Siemens | WinCC-based systems | SCADA/HMI | OPC UA client connector for WinCC OPC server |
| CopaData | POI (Orchestrator) | Orchestration | OPC UA / REST API bidirectional connector |
| Lucullus | PIMS | Process Information Mgmt | REST API connector for PIMS data exchange |
| Custom Build | Downstream instruments | LabVIEW | OPC UA / REST API bridge for LabVIEW instruments |
| Other | Printers, barcode scanners | — | REST API connector for track-and-trace workflows |
9.6 Roadmap Summary
A4BEE's integration experience spans 30+ instrument types from 20+ vendors across bioreactors, analytical instruments, filtration systems, pumps, sensors, scales, and automation platforms. This breadth of hands-on knowledge directly informs QB Control's connector development roadmap, with priority given to:
Leveraging QB Control's existing OPC UA client/server infrastructure to productize library of connectors for Siemens WinCC, Emerson DeltaV, Cytiva UNICORN, Sartorius BioSC
Productizing HTTP-based integrations for modern analytical instruments and PIMS/LIMS platforms (Beckman Coulter Vi-CELL, Roche Cedex, Nova BioProfile, Lucullus PIMS)
Extending QB Control's native Modbus support to cover legacy pumps, sensors, and embedded controllers (MasterFlex, Pendotech, Repligen ATF)
Productizing library of file based connectors for instruments that export data as structured files (Agilent OpenLab CDS, Agilent Mass Spec, Cytiva UNICORN ZIP exports)
Instruments where A4BEE has existing native support through QB Modules (Hamilton sensors, Mettler Toledo sensors and scales) are already integrated into QB Control and do not require additional connector development.