QB Control vs Eppendorf DASware Comparison

At a glance

Dimension	QB Control	Eppendorf DASware
Design philosophy	◆ Universal, vendor-agnostic automation	Eppendorf ecosystem software
Hardware binding	◆ Vendor-agnostic, modular integration	Tightly coupled to Eppendorf hardware
Best use case	Flexible control across vessel scales	◆ Parallel mini-bioreactor HT screening
Architecture	◆ Embedded Linux ARM, browser UI	Windows client-server (SQL Server)
Integration model	◆ API-first, native multi-vendor	Ecosystem-first; 3rd-party bolt-ons
Deployment	◆ Edge computing + cloud-ready	On-premises Windows PC
21 CFR Part 11	Partial built-in; e-signatures on roadmap	◆ Via separate Plus license

Executive Summary
Platform Philosophy
Architecture & Hardware
Parallel Processing
Multi-Vendor Integration
Software Module Comparison
Services Catalog & Rapid Deployment
Recipe Engine
Regulatory Compliance
Pricing, Licensing & TCO
Industry Fit Analysis
What QB Control Can Replace
Where QB Control Creates Superior Value
Gaps & Limitations
Migration & Replacement Scenarios
Competitive Positioning Strategy
Feature-by-Feature Matrix

Appendices — Summary Scores by Category · Sources

1. Executive Summary

The Core Argument

Eppendorf DASware is a mature, ecosystem-centric bioprocess control software built around Eppendorf’s own hardware portfolio — DASbox and DASGIP parallel mini-bioreactors, SciVario twin benchtop systems, and BioFlo/BioBLU control stations. Its standout strength is high-throughput parallel mini-bioreactor screening down to ~24–250 mL (DASbox), with optional bolt-on modules for regulated use (DASware control plus), analyzer integration (DASware analyze), DoE (DASware design), DCS bridging (DASware connect), and cloud analytics (BioNsight).

QB Control is a SCADA-class, browser-based platform designed specifically for modular liquid handling and bioprocessing — deployable both on QB Edge (benchtop QB Modules) and on a standard industrial PC driving stainless-steel, PLC-based systems via OPC-UA for pilot- and production-grade installations.

These products serve overlapping but distinct markets. The comparison is most relevant in upstream bioprocessing from lab bench through pilot scale (150 mL – 50 L benchtop, and stainless-steel pilot/production via PLC), where QB Control provides a vendor-neutral, lower-TCO turnkey alternative. DASware retains a decisive advantage in sub-150 mL parallel mini-bioreactor high-throughput screening — a workload QB Control does not address.

Key Finding

QB Control does not replace DASware in all scenarios. It replaces DASware in segments where Eppendorf’s hardware lock-in, à-la-carte module licensing, and Windows/SQL Server infrastructure create friction — and where vessels are ≥ 150 mL. With the industrial-PC deployment path, QB Control’s footprint now extends upward into stainless-steel pilot and production cells. The sweet spot for QB Control as a DASware alternative is:

Scenario	QB Control Replaces DASware?	Value Driver
Benchtop bioprocessing (150 mL–10 L)	✅ Full replacement	Vendor-neutral turnkey, lower TCO, days vs. weeks setup
Pilot-scale upstream (10–50 L benchtop)	✅ Full replacement	Modular flexibility, ~40 pre-built services
Stainless-steel pilot/production (PLC + OPC-UA)	✅ Strong replacement (new)	Industrial-PC deployment, no Eppendorf hardware lock-in
Multi-vendor / multi-scale operations	✅ Strong replacement	Native OPC-UA/MQTT/REST, no add-on module fees
CDMO multi-client process development	✅ Superior alternative	Process import/export + device mapping, lower cost/program
Mixed Eppendorf + 3rd-party fleets	⚠️ Partial / complementary	QB Control for new lines; DASware retained for legacy
Sub-150 mL mini-bioreactor HTS (24–250 mL)	❌ Not a replacement	DASbox/DASGIP parallel screening required
Established 16–24-vessel DASware HTS farm	❌ Not a replacement	Revalidation cost exceeds savings

2. Platform Philosophy

Fundamental Architecture Difference

Dimension	DASware	QB Control
Product Category	Ecosystem bioprocess control software	SCADA-class browser-based platform
Design Philosophy	Hardware-first, Eppendorf-ecosystem	Modular-first, vendor-agnostic
Target Scale	Mini-bioreactor HTS (24 mL) to pilot/production (BioFlo); identical-vessel parallelism	Lab-to-pilot (150 mL – 50 L benchtop); stainless-steel pilot/production via PLC + OPC-UA
Approach to Hardware	Tightly coupled to DASbox/DASGIP/SciVario/BioFlo	Own modular hardware (QB Modules) + open sensors; or existing PLCs (Wago/Siemens/Beckhoff)
Software Delivery	Windows desktop client-server (SQL Server)	Browser-based (any device, any OS)
Deployment Host	Windows PC/workstation/server	QB Edge for benchtop or standard industrial PC for PLC-based stainless steel
Configuration Model	Profile tables + proprietary scripting	Visual drag-and-drop + recipe designer (no coding)
Module Licensing	À-la-carte (control / plus / analyze / design / connect)	All 18 modules in one perpetual license
Vendor Strategy	Eppendorf ecosystem (lock-in)	Open ecosystem (no lock-in)
GAMP Classification	Category 5 (custom scripting)	Category 4 (configurable software)

The “iTunes vs. Spotify” Problem

DASware assumes the client is committed to the Eppendorf hardware ecosystem and wants the deepest possible tuning of Eppendorf sensors, actuators, and parallel mini-vessel geometries. That assumption is exactly right for a screening lab running banks of identical DASbox or DASGIP vessels — and DASware is genuinely best-in-class there. But it creates friction for:

Multi-vendor bioprocess environments mixing Eppendorf, Sartorius, INFORS HT, Applikon, and custom rigs
Teams that want one platform across heterogeneous vessel scales (benchtop + pilot simultaneously)
Stainless-steel pilot cells that already have a PLC and need supervisory control, not a new hardware fleet
Organizations that resist Windows/SQL Server IT overhead and per-module licensing
CDMOs running many client programs that each demand fast setup, teardown, and segregation

Building a multi-vendor, multi-scale operation on a single-vendor ecosystem means paying for integration bridges and separate software instances. QB Control is purpose-built for vendor-neutral, scale-variable bioprocessing — but it deliberately does not chase the sub-150 mL mini-bioreactor screening niche that DASware owns.

3. Architecture & Hardware

Controller & Hardware Architecture

Component	DASware	QB Control
Central Controller / Host	Windows PC / workstation / server	QB Edge (runs QB Control locally) or industrial PC for PLC-based stainless-steel systems
I/O Architecture	USB to DASbox, Ethernet to DASGIP/BioFlo; analog/digital for external	Power-over-Ethernet (one cable = power + data per module); or PLC I/O (Wago/Siemens/Beckhoff) via OPC-UA
Database	Microsoft SQL Server	Embedded data store (no external database server required)
Device Discovery	Manual configuration per hardware type	Auto-discovery (Plug & Play) for QB Modules; manual for 3rd-party via OPC-UA/Modbus
Workstation Requirement	Windows PC required	Any device with a browser (Chrome, Firefox, Edge, Safari)
Form Factor	Desktop/tower workstation + bioreactor hardware	Bench-top modules; or industrial PC + existing PLC cabinet
Power Architecture	Host PC + hardware power supplies	PoE — single cable per module, no external power supplies
Wiring	USB/Ethernet per system + analog I/O	Single Ethernet cable per module — minimal wiring
Full reboot time	Windows + SQL Server boot dependent	Up to ~15 minutes for a full system reboot

DASware Hardware Ecosystem vs. QB Control Modular Hardware

Function	DASware Approach	QB Control Approach
Mini-bioreactors	DASbox (24–250 mL), 4-fold / 8-fold parallel — native, best-in-class	Not supported below 150 mL (genuine DASware advantage)
Parallel benchtop	DASGIP (50 mL–multi-liter), 16–24 vessels	QB Multiagitator (2 or 6 vessels) + multi-process architecture
Pumps	DASGIP peristaltic pumps (proprietary)	QB Pump (peristaltic, centrifugal, syringe) — native; SmartPump (OPC) for 3rd-party
Sensors	Eppendorf/InPro probes (pO₂, pH, temp) — native	QB Multisensor — connects up to 6 Hamilton/Mettler Toledo probes natively
Agitation	Integrated in DASbox/DASGIP/SciVario	QB Agitator, QB Multiagitator (2 or 6 vessels) — native
Temperature	Integrated (Pt100, heat exchanger)	QB Thermo (heating/cooling 2–42 °C, heating mats) — native
Gas Flow	DASGIP MX module gas mixing	QB Gasflow (up to 2 gas streams, 0.1 SCCM – 20 SLPM) — native
Valves	System-specific	QB Pinch Valve, QB Selector Valve (24 positions), three-way valves — native
Scales	External, via I/O	QB Multiscale (up to 6 scales via RS232) — native
Foam Detection	Probe-based antifoam pump	QB Foam Sensor — optical, patent-pending, non-contact
Lighting	Not part of ecosystem	QB Light (up to 6 independent LED outputs for photobioreactors)
Pressure	Optional (0–3 bar)	QB Pressure Sensor (up to 2 single-use IBP transducers)
External analyzers	DASware analyze (separate license)	OPC-UA / REST API (native, included)
DCS / PLC integration	DASware connect (separate license)	OPC-UA + OPC UA Connector (native, included)

Key Hardware Advantage: QB Control

No Windows/SQL Server infrastructure — embedded data store, browser UI, no IT licensing
Auto-discovery eliminates manual device commissioning for QB Modules
PoE eliminates separate power infrastructure for benchtop deployments
Open sensors — use Hamilton, Mettler Toledo, Levitronix at market price (no vendor markup)
New: for stainless-steel systems with existing PLCs, QB Control deploys on an industrial PC and integrates over OPC-UA — reusing field hardware instead of replacing it

Key Hardware Advantage: DASware

Native sub-150 mL mini-bioreactors (DASbox 24–250 mL) — QB Control cannot match this scale
Vertically integrated stack — DASbox/DASGIP/SciVario/BioFlo sensors, actuators, and geometries pre-validated together
Parallel sensor calibration across 8+ identical vessels simultaneously
40+ years of Eppendorf bioprocess hardware refinement and a global service network

4. Parallel Processing

Side-by-Side Comparison

Capability	DASware	QB Control
Max Parallel Vessels (same scale)	8 (DASbox), 16–24 (DASGIP) — purpose-built HTS	Multiple parallel processes (license-dependent); QB Multiagitator supports 6 vessels per module
Parallel Architecture	Vessel replication — identical geometry & sensor suite	Each bioreactor = independent Process with own P&ID, alarms, recipes, batch recording
Heterogeneous-Scale Parallelism	Limited — requires matched vessels	Native — benchtop + pilot + stainless-steel in parallel (min. 150 mL)
Sub-150 mL Screening	✅ DASbox down to ~24 mL	❌ Not supported
Shared Resource Management	Unified host arbitration	Process-level resource allocation via System and Process modules; conflict blockade prevents collisions
Independent Recipes Per Vessel	All vessels typically run identical recipe	Yes — different recipes per process; parallel and sequential batch execution
Sequential Campaign Queuing	Sequential profiles	Sequential batch execution with Pending queue status + per-batch auto-stop conditions (new)
Unified Data View	Single SQL Server consolidates all parallel runs	QB Graphs (per-process live + history), Reports (per-batch)
Cross-Batch Comparison	Online batch-to-batch comparison (Professional edition)	QB Graphs multi-parameter overlay + CSV export for external analysis
Parallel Sensor Calibration	✅ All vessels simultaneously	Per-service basis (per device)

QB Control’s Parallel Processing Model

QB Control implements parallel processing through its System → Process → Batch hierarchy:

System defines the physical resources (devices, services, equipment, media)
Multiple Processes can be defined within a system, each with its own auto-generated P&ID, alarm configuration, recipe assignment, batch recording, and reports
Multi-instance services allow the same service type to be instantiated across multiple processes
Parallel Recipe Execution — multiple recipes run simultaneously across different processes, even at different vessel scales (≥ 150 mL)
Sequential execution (new) — batches can be queued with a Pending status and chained with auto-stop conditions, enabling unattended campaign sequencing
Process-level isolation — each process operates independently with its own control loop and its own per-process emergency stop (P-Stop)

Where QB Control Excels in Parallel Processing

Heterogeneous-scale parallelism — unlike DASware (which requires matched vessels), QB Control runs benchtop + pilot + stainless-steel in parallel
No additional instances — a single QB Control instance manages many independent processes; DASware mixed-scale work typically needs separate software instances
Visual P&ID per process — auto-generated from configuration, preserved and copied forward on versioning
Process & recipe Import/Export with device mapping — replicate a proven setup to new bioreactors and remap devices instantly
Multi-user concurrent access — different operators monitor/control different processes simultaneously from different devices

Where DASware Excels in Parallel Processing

Sub-150 mL mini-bioreactor screening (DASbox 24–250 mL) — QB Control does not serve this scale
High vessel count at identical scale (16–24 DASGIP vessels) optimized for DoE / parameter sweeps
Simultaneous parallel sensor calibration across all vessels in one workflow
Mature batch-to-batch analytics built into the Professional edition
Vessel-replication design purpose-built for true high-throughput screening

5. Multi-Vendor Integration

Protocol Support Comparison

Protocol	DASware	QB Control
OPC UA	Via DASware connect (separate license)	Native — primary path for PLC/stainless-steel integration; dedicated OPC UA Connector module with configurable mappings
Modbus	Via DASware connect (separate license)	Supported (TCP and RTU)
MQTT	Not available (BioNsight cloud is separate)	Native — IoT real-time streaming
REST API	Not available	Native — modern web integrations
SQL (JDBC/ODBC)	SQL Server only (internal)	Native — direct database access (JDBC/ODBC)
LDAP/Active Directory	Windows domain integration only	Native — SSO with corporate credentials, configurable search scope/timeout/pagination
MTP (Module Type Package)	Not native	Supported (new) — plug-and-produce integration + MTP-oriented signal presentation in Graphs
PROFIBUS / PROFINET	DASGIP-specific	Profibus supported; PLC protocols (Wago/Siemens/Beckhoff)
Serial (RS232/RS485)	Via converters	Native (QB Multiscale, QB Multisensor)
Bluetooth / WiFi	Not supported	Supported (QB Edge wireless options)
SMTP (email)	Notification in Professional edition	Native — notification dispatch with SMTP config + delivery logs
External analyzer feedback	Post-run, logged (DASware analyze)	Real-time — external analyzer data can trigger service actions
DCS bridging	DASware connect (separate license)	Native OPC-UA / Modbus (included)

Sensor Vendor Support Comparison

Vendor	DASware	QB Control
Eppendorf / InPro probes	Native — deeply tuned	Via OPC-UA / Modbus where applicable
Hamilton	Via DASware analyze / connect	Native — Arc module sensors via QB Multisensor (DO, pH, conductivity, OD, CO₂, ORP); two-point / zero-point / slope calibration
Mettler Toledo	Via DASware analyze / connect	Native — ISM/Modbus sensors via QB Multisensor (DO, pH, ORP, CO₂, conductivity)
Levitronix	Custom integration	Native — flow meters via QB Multisensor
Mettler Toledo / Kern Scales	Via I/O	Native — MT-SICS / PKP series via QB Multiscale

Integration Philosophy Difference

DASware: “We provide deeply tuned control for the Eppendorf hardware family. Anything outside the ecosystem — third-party sensors, analyzers, DCS systems — is reached through separately licensed bolt-on modules (DASware connect, DASware analyze), each requiring manual OPC server setup, tag mapping, or vendor-specific drivers.”

QB Control: “We provide both the control platform AND the hardware modules. Our modules natively connect Hamilton, Mettler Toledo, and Levitronix sensors. For anything else, we offer OPC UA (with a dedicated connector), Modbus, MQTT, REST API, SQL, and MTP — all included, no add-on licenses — and we deploy on your existing PLCs for stainless-steel systems.”

QB Control’s Integration Advantage

All protocols included — OPC-UA, Modbus, MQTT, REST API, SQL, LDAP/AD, and MTP ship in the base license; DASware charges per integration module
Native sensor support — Hamilton and Mettler Toledo probes connect directly to QB Multisensor. No DASware analyze license, no separate gateway
OPC UA Connector — a dedicated module bridges OPC-UA equipment into QB Control with configurable mappings — the path for PLC-based stainless-steel systems
Real-time analyzer feedback — external analyzer data can trigger QB Control service actions (e.g., adjust feed if cell density drops); DASware logs analyzer results post-facto
MTP support (new) — plug-and-produce modular integration

DASware’s Integration Advantage

Deepest Eppendorf-ecosystem integration — pre-validated sensor/actuator stack across DASbox/DASGIP/SciVario/BioFlo
DASware analyze — purpose-built drivers for nutrient analyzers (YSI, Roche Cedex), cell counters, biomass monitors, HPLC, MS, and Raman
BioNsight Cloud — Eppendorf’s cloud platform for remote monitoring, data contextualization, and model-based optimization
Mature, proven at production scale within single-vendor pharma installations
Integrated DoE via DASware design — auto-generates and executes experimental matrices

6. Software Module Comparison

Module-by-Module Mapping

QB Control ships 18 software modules, accessed through the Portal, all included in a single perpetual license. DASware delivers capability through a base product (DASware control, Standard/Professional) plus separately licensed modules (control plus, analyze, design, connect) and the BioNsight cloud.

Capability Area	DASware Component	QB Control Module	Comparison
Device Management	Manual per-system configuration	Inventory (auto-discovery, device status, configuration import/export, licensing)	QB simpler & faster
System Configuration	DASware control setup	System (visual resource allocation, search, bulk add/remove, history to CSV)	QB no-code, vendor-neutral
Process Configuration	Per-vessel configuration	Process (visual binding, versioning, duplicate process, live connection status, guided import/export)	QB faster; heterogeneous scale
Process Visualization	DASware control HMI	P&ID (auto-generated, drag-and-drop, recipe execution from diagram, P-Stop/E-Stop)	QB auto-generates; DASware vessel-centric
Batch Management	Recipe / profile management (scripted)	Recipe (Designer / Batch / Executions Boards)	QB visual designer; no scripting
Services Catalog	No equivalent (custom recipes/scripts)	Services (~40 templates across 10 categories, load & execute in minutes)	QB unique advantage
Service Profiles	No equivalent	Service Profiles (reusable grouped/atomic parameter templates, portable import/export)	QB unique advantage
Alarm Management	Basic threshold configuration	Alarms (ISA-18.2 conformance, watchlist, in-app global notifications)	QB stronger (formal ISA-18.2)
Data Visualization	Charting / trends (Pro: batch-to-batch)	Graphs (live + history, multi-axis, annotations, MTP signals, export)	Comparable; DASware stronger HTS analytics
Reporting	Data export + batch reports	Reports (automated + manual, PDF/DOCX, recipe-execution & service-history sections)	QB automated certified output
Batch Tracking	SQL Server run logs	Runs (per-process, batch ID, user tracking, report linkage)	Both adequate
Calibration	Manual workflow / via recipe	Calibration (status tracking, Next Due Dates, Hamilton/pump methods, device-type-aware history)	QB integrated
Audit Trail	DASware control plus only (separate license)	Audit Trail (21 CFR Part 11 conformance, cross-module, exportable CSV)	QB built-in to base
Access Control	Basic auth (Standard); RBAC in plus	Users & Roles (RBAC, 18 permission groups, LDAP/AD)	QB built-in to base
Notifications	Email/log alert (Professional)	Notifications (in-app center, email/SMTP, per-user preferences, recipe-step alerts, logs)	QB richer out-of-box
Backup	Manual export (SQL Server)	Backup, Export & Archive (scheduled/manual wizards, one-click restore, integrity verification)	QB built-in automated
License Management	Per-module activation	License (feature/device/system/time-based, online/offline, host-bound, license guards)	QB unified, more flexible
Remote Access	Windows remote desktop / BioNsight cloud	Remote Access (secure VPN, QR-code setup, phone/tablet/PC, role-based) — new	QB simpler, multi-device
Health Monitoring	Diagnostics per system	Health Monitoring (system health dashboard, per-module status, drill-down) — new	QB consolidated, always-on
External Analyzers	DASware analyze (separate license)	OPC-UA / REST API (native, included)	QB no add-on fee
DoE Integration	DASware design (separate license)	Service-based recipes + external DoE tools	DASware wins (native DoE)
DCS Integration	DASware connect (separate license)	Native OPC-UA / Modbus (included)	QB no add-on fee
Cloud / AI Analytics	BioNsight Cloud (DASware 6+, separate)	MQTT/REST export to any cloud/analytics	DASware wins (turnkey AI cloud)
E-Signatures	DASware control plus	❌ On roadmap (Q3 2026)	DASware wins (today)

7. Services Catalog & Rapid Deployment

QB Control’s Services Catalog — A Game-Changing Differentiator

One of QB Control’s most powerful advantages over DASware is the Services Catalog — a library of pre-built, parameterized service templates that can be loaded and executed within minutes. A Service is a pre-defined control action that directly commands hardware. Services come in two types:

Autocomplete Services — execute a discrete task and close automatically (e.g., Transfer Volume by Pump, Add Gas Volume by MFC)
Continuous Services — run until explicitly stopped (e.g., Set Agitator Speed, Temperature Control by TCU, pH Control by Base & CO₂)

DASware, by contrast, drives control logic through profile tables and a proprietary scripting language (e.g., IF pO2 < 20 THEN AddAir; WAIT 300; ENDIF) — powerful for tuned single-vessel workflows, but treated as custom code for validation (GAMP Category 5).

Services Catalog by Category

QB Control ships with ~40 pre-built service templates across 10 functional categories out of the box, with QB Filtration adding a tangential-flow filtration set (recently expanded). This covers every core bioprocess control need:

Category	Example Services	Count	Types
pH Control	pH Control by Base & CO₂, by Base & Acid, by One Pump, One Pump PID, pH PID Control	6	Continuous
Temperature Control	by TCU, by Heating Mat, by Steam & Water, Split Temp, Set Circulator Temp, Set Heating Mat Power	6	Continuous
Pump & Feed	Feed, Autosubstrate, Set Pump Flow Rate, Set Centrifugal Pump RPM, Transfer Volume/Bolus, Gravimetric Feeding	9	Continuous + Autocomplete
Gas Control	O₂ Control, Advanced O₂ Control, Set MFC Flow, Set Sparger Mass Flow	4	Continuous
Gas Volume Delivery	Set Sparger Volume & Mass Flow	1	Autocomplete
Sampling	Automated Sampling, Sample by Syringe Pump, Sampler Cleaning	3	Continuous + Autocomplete
Stirring & Agitation	Stirring, Set Agitator Speed	2	Continuous
Foam Control	Foam Control, Foam Control by Antifoam Reagent	2	Continuous
Valve Control	Set Selector Valve Position, Set Valve Position	2	Continuous
LED & Light	LED Control, LED Control Scheduler	2	Continuous
Core catalog (out of the box)		~40	across 10 categories
QB Filtration add-on	Filtervig Control, Concentration Factor Logic, NWP Calculator, Breakthrough Detection, plus six new tangential-flow services	expanded	Continuous + Autocomplete

Service Profiles — Reusable Parameter Templates

QB Control’s Service Profiles (Settings → Service Profiles) let users save standardized parameter configurations as reusable templates. QB Control offers grouped and atomic-style configuration models, structured profile cards (e.g., PID Controller Tuning, Temperature Ramp, Operating Limits), and portable export/import to transfer complete profile sets between templates or environments. Profile-driven values are labeled in execution review for traceability.

How Services Transform Experiment Deployment

Workflow Step	DASware Approach	QB Control with Services Catalog
Define control strategy	Write proprietary script or build profile tables	Select service template from catalog
Set parameters	Enter values per profile (vessel-specific)	Load a saved Service Profile or enter values in a visual form
Change control logic	Edit script, recompile, re-validate	Swap service template — minutes, not days
Deploy to process	Configure recipe, test, validate — days	Add service to process; it appears in Recipe Designer — minutes
Try a different strategy	New scripting/profile effort	Select a different service / apply a different profile — instant

Time-to-Deploy for Experiment Strategy Changes

Scenario	DASware Time	QB Control Time	QB Advantage
Switch pH control from CO₂+Base to Acid+Base	Hours–days (edit profile/script, test)	5 minutes (swap service template)	~50–100× faster
Add foam control to an existing process	Days (configure, test)	10 minutes (add service + connect foam sensor)	~100× faster
Change temperature control from setpoint to ramp	Hours (modify profile)	2 minutes (change parameters or swap template)	~100× faster
Deploy a completely new experimental strategy	Days–weeks (scripting + validation)	1–2 hours (select services, build recipe, validate)	~50× faster
Replicate a proven setup to a new bioreactor	Hours–days (copy, adapt, re-validate)	15 minutes (Process Import/Export + device mapping + Profiles)	~50× faster

For multi-vendor and multi-scale work, QB Control makes strategy changes a catalog selection. DASware’s depth shines on tuned, identical-vessel screening, but every control-logic change is scripted and revalidated as custom code.

8. Recipe Engine

Overview

The Recipe Module is the core automation engine of QB Control. It translates biotechnological protocols into executable digital workflows by combining logic blocks and Services (hardware actions), through three integrated boards: Designer Board (create/edit), Batch Board (configure/execute), and Executions Board (monitor history). This contrasts with DASware’s profile-table + proprietary-scripting model.

8.1 Designer Board & the Unified Block Library

The Designer Board is a visual, drag-and-drop workspace for building process logic as a connected flow. QB Control consolidates per-service blocks into a unified block library with built-in grouping, descriptions, tooltips, and embedded in-app guidance:

Block	Category	Function
Start Service	Service Control	Single configurable block (replaces many per-service start blocks); pick the service at configuration; supports Autocomplete (run-to-completion) and Continuous (keep running)
Stop Service	Service Control	Explicitly stop a continuous service later in the flow
Update Service Inputs	Service Control	Change service input values mid-execution (startup vs. runtime-adjustable inputs kept separate)
Service Profile support	Service Control	Start/Update blocks accept preset profile configurations; profile values labeled in execution review
Manual Operation	Operations	Pause for operator-driven action where supervised intervention is required
Variable / Update Variables	Variables	Declare named values (boolean, text, number, time); update with increase / decrease / multiply / divide
Timer	Timing	Shared timer control with start / stop / pause / resume modes
Set Valve State	Equipment commands	Command valve positions directly as part of the sequence
Conditional	Logic & flow	Evaluate real-time variables with AND / OR expressions
Counter	Logic & flow	Loop control with iteration count
PID	Logic & flow	Inline PID-oriented control block
Polygon	Logic & flow	Piecewise-linear mapping (X→Y) for ramps and profiles
Split / Merge	Logic & flow	Fork into parallel paths and join them back together
Wait / Wait Until / Start / Stop / End	Standard	Time-based pause, condition-based pause, and execution control

Authoring productivity: copy/paste of blocks, signal filtering for cleaner input selection, undo/redo, diagram export (image), and recipe import/export across installations. The designer flags inactive recipes that should not be started as-is.

Recipe state lifecycle: Draft → Verified → Validated → Hold → Archived. Critically, only Verified or Validated recipes can run in batches — not just Validated — which streamlines development without weakening control.

8.2 Batch Board

Create batches for processes and assign single or multiple recipes per batch
Real-time view to monitor and control execution (stop, pause, resume)
Sequential batch execution with Pending status for queued batches and auto-stop configuration per batch
Edit parameters from the execution board where permitted — no round-trip to the designer mid-run
Step execution counts and live recipe status updates

8.3 Executions Board

List of executed batches with start/finish time, status, and configuration
Statuses: During Execution, Paused, Hold, Pending, Completed, Failed, Aborted
Filter by System, Process, Status; export list to CSV; export recipe flow to PNG
Direct links to the live view of currently executing recipes

8.4 Validation & Safety

The Validator — visual workspace for verifying recipe logic before execution
Automated pre-start validations prevent batch collisions, unauthorized recipe starts, and execution on disconnected hardware
Mandatory pre-execution checklist forces operators to verify critical lab elements (tubing integrity, media preparation) before start
License guard — creating, duplicating, or importing recipes is blocked when the recipe license limit is reached
Emergency integration — runs hold or abort safely when a P-Stop or global E-Stop is active

8.5 Recipe Engine vs. DASware — Detailed Comparison

Capability	DASware	QB Control Recipe Engine
Workflow design	Profile tables + proprietary scripting language	Visual drag-and-drop Designer Board (no coding)
Code-free configuration	Partial (profiles visual; logic scripted)	100% visual
Parallel execution	All vessels run identical recipe	Split/Merge blocks for parallel paths; independent recipes per process
Sequential campaigns	Sequential profiles	Sequential batches with Pending queue + auto-stop
Conditional logic	Basic if-then rules	Conditional blocks with AND/OR on real-time data
Variables & math	Limited dynamic calculation	Variable / Update Variables (increase/decrease/multiply/divide)
Timers	Wait conditions	Timer block (start/stop/pause/resume)
Human-in-the-loop	Manual step prompts	Manual Operation block
Real-time parameter edit	Recipe modification requires restart	Editable during run (Update Service Inputs)
Recipe versioning	Manual version control	Draft → Verified → Validated → Hold → Archived
Pre-execution safety	Operator workflow (configurable)	Mandatory checklist + Validator (system-enforced)
Diagram export	Not standard	Export as image / PNG for compliance docs
GAMP category	Category 5 (custom scripts)	Category 4 (configurable services)
Time to create recipe	Hours to days (scripting)	Minutes to hours (visual, no-code)
Integrated DoE	✅ DASware design (native)	External tools / service-based recipes

9. Regulatory Compliance

Standard	DASware	QB Control	Notes
FDA 21 CFR Part 11	✅ Full (via DASware control plus, separate license)	⚠️ Partial conformance	DASware plus: full (with e-sigs). QB: electronic records, audit trails, access control, user management today — electronic signatures not yet covered
EU Annex 11	✅ Full (DASware control plus)	✅ Compliance support	Both provide computerized-system validation capabilities
GAMP 5	Category 5 (custom scripting)	Category 4 (configurable)	QB Control has lower validation burden — no custom code to validate
ISA-18.2 (Alarms)	⚠️ Basic alarm configuration; not formally ISA-18.2	✅ Conformance	QB supports suppressed, out-of-service, acknowledgement workflows; DASware basic
ALCOA+ (Data Integrity)	✅ Full (DASware control plus)	✅ Full implementation	Both provide ALCOA+ data integrity
Electronic Signatures	✅ Built-in (DASware control plus)	◐ On roadmap (Q3 2026 — not in current version)	DASware leads; QB planned
Audit Trail	✅ Immutable (DASware control plus only)	✅ Immutable, exportable (CSV), cross-module, searchable — base license	QB built-in to base; DASware requires plus
Safe Position Logic (GMP)	Via system engineering	✅ Built-in — define safe actuator states after restart/power cycle	QB has a dedicated, configurable feature
CE Marking	System-level	✅ Per QB Module (EMC + Low Voltage Directive)	Each module ships its own Declaration of Conformity

Compliance Value for QB Control

GAMP 5 Category 4 vs. Category 5 is the key differentiator. As configurable (not custom) software, QB Control needs reduced validation scope and standardized test scripts rather than the full custom IQ/OQ/PQ, design documentation, and UAT that DASware’s scripted recipes require as custom code — roughly 50–70% less validation effort (typically 2–4 weeks per configuration vs. 6–8 weeks per DASware recipe), faster time to GMP-ready operation, lower CSV cost, and simpler change management (configuration, not code). QB Control also bundles audit trail, RBAC, and data integrity in the base license, whereas DASware gates these behind the separately licensed DASware control plus.

Honest Compliance Caveat

QB Control’s 21 CFR Part 11 conformance is partial: it delivers electronic records, audit trails, access control, and user management today, but electronic signatures are not yet implemented (roadmapped for Q3 2026). For workflows that require digital signatures on batch release or an active IND today, DASware control plus remains the safer choice until QB Control’s e-signature release. Do not represent QB Control as fully 21 CFR Part 11 compliant. DASware also carries longer established regulatory precedent in FDA-filed pharma installations.

10. Pricing, Licensing & TCO

Direct Cost Comparison

Cost Component	DASware	QB Control	Savings with QB
Entry-Level System	DASware control + base hardware: ~$50,000–65,000	QB Edge + basic modules + license: ~$15,000–25,000	50–70%
Typical Lab Setup (4 vessels)	DASware Pro + DASbox 4-fold + Windows/SQL: ~$65,000–95,000	4× bioreactor module sets + QB Edge + license: ~$60,000–85,000	10–35%
Regulated 4-vessel (21 CFR Part 11)	+ DASware control plus: ~$80,000–120,000	Built-in compliance — no surcharge: ~$60,000–85,000	25–45%
6-Vessel Lab Setup	DASware Pro/plus + DASGIP + analyze/connect: ~$120,000+	6× bioreactor module sets + QB Edge(s) + license: ~$100,000	~20–40%
Pilot Setup (8–12 vessels)	Multi-instance DASware + hardware: $200,000+	8–12× module sets + QB Edge(s)/switches + license: ~$150,000–250,000	comparable, fewer add-ons
Add-on Modules	analyze $8K–15K, design $10K–20K, connect $5K–12K, BioNsight $5K–30K/yr	$0 — OPC-UA/Modbus/MQTT/REST/cloud-export all included	100% of module fees
Windows / SQL Server	$3,000–10,000 + ongoing licensing	$0 (embedded data store, browser UI)	100%
Software License	Per-module subscription/perpetual (quote-based)	Perpetual license (one-time purchase)	Lower long-term
Training	Eppendorf-led, 1–2 weeks ($3,000–8,000)	QB Systems Online Portal + documentation — self-paced	70–90%
Validation (GAMP 5)	Category 5 — 6–8 weeks per recipe ($50,000–80,000)	Category 4 — 2–4 weeks per config ($30,000–50,000)	40–50%

Total Cost of Ownership (5-Year Projection)

Scenario: 4-vessel regulated upstream lab

TCO Component	DASware control plus (5-Year)	QB Control (5-Year)
Hardware (bioreactors / QB Modules + Edge)	$40,000–50,000	$25,000–35,000
Software licensing	$15,000–25,000 (per-module, recurring upgrades)	$10,000–15,000 (perpetual, one-time)
Add-on modules (analyze/connect/design)	$20,000–50,000	$0 (included)
Windows / SQL Server (5-yr)	$15,000–40,000	$0
Annual maintenance (Y2–Y5)	$60,000–100,000 (~20%/yr, mandatory)	$20,000–48,000 (optional tiered support)
Paid support & training	$12,000–18,000	$5,000 (Online Portal, self-paced)
Validation	$50,000–80,000 (Category 5)	$30,000–50,000 (Category 4)
TOTAL	~$205,000–330,000	~$98,000–160,000
		~40–50% lower TCO

Licensing Model Comparison

Aspect	DASware	QB Control
Model	À-la-carte: control (Standard/Pro), plus, analyze, design, connect; quote-based	Perpetual license — feature-, device-, system/process-, and time-based dimensions, all 18 modules included
License Type	Subscription or perpetual per module; major-version upgrade fees	Perpetual — buy once; no recurring license fees
Annual Maintenance	15–25% of license cost (typically mandatory)	Optional — tiered (Basic, Standard, Premium), client’s choice
Compliance Tier	Separate DASware control plus license	Included in base (audit trail, RBAC, data integrity)
Integration	Per-module (connect, analyze)	Included (OPC-UA, Modbus, MQTT, REST, SQL, MTP)
Infrastructure Dependency	Windows + SQL Server licensing	None — embedded data store, any browser
Lock-In	Tied to Eppendorf hardware ecosystem	Not tied to a specific hardware vendor

Licensing Model — Key Client Value

No add-on module overlap — protocols, compliance features, and analyzer integration are in the base license, not separate purchases
No recurring license fees — the perpetual license does not expire, eliminating DASware’s 15–25% annual maintenance burden
No Windows/SQL Server overhead — no per-core licensing, no IT patching cycle
Predictable budgeting — one-time license + optional support
No “license hostage” risk — perpetual model means a lapsed contract never locks you out of your own system

11. Industry Fit Analysis

Biotech R&D & Process Development

Criterion	DASware	QB Control	Winner
Speed to first run	6–8 weeks	2–3 weeks	QB Control
Multi-vendor hardware	Eppendorf ecosystem	Vendor-agnostic	QB Control
Parallel benchtop (150 mL–10 L)	Capable (DASGIP)	Multiple processes, auto-generated P&IDs	QB Control (vendor-neutral)
Sub-150 mL mini-bioreactor screening	DASbox 24–250 mL	Not supported	DASware
DoE integration	Native (DASware design)	Via external tools	DASware
Recipe iteration	Good (scripted)	Excellent (visual versioning)	QB Control
Cost efficiency	Higher (per-module)	Lower TCO	QB Control

Pharmaceuticals

Criterion	DASware	QB Control	Winner
R&D lab automation	Ecosystem-bound	Right-sized, vendor-neutral	QB Control
Process development	Good but per-module cost	Faster iteration, lower cost	QB Control
GMP audit trail + RBAC	DASware control plus	Built-in to base	QB Control
GMP production (e-sigs required)	DASware control plus (today)	CFR Part 11 partial (no e-sigs yet)	DASware (e-sigs today)
Regulatory precedent (FDA filings)	Strong, established	Growing	DASware
Validation effort	Category 5 (6–8 wk/recipe)	Category 4 (2–4 wk/config)	QB Control

CDMOs & Multi-Client Operations

Criterion	DASware	QB Control	Winner
Multi-process isolation	Separate instances	Native multi-process	QB Control
Multi-vendor bioreactors	Eppendorf-centric	Sartorius, INFORS, Applikon, custom	QB Control
Per-program batch records	Manual export	Automated certified PDF/DOCX	QB Control
Cross-site federation	DASware connect / manual	REST API + cloud-ready	QB Control
Cost per program	Per-instance license	One license, many processes	QB Control

High-Throughput Screening (HTS)

Criterion	DASware	QB Control	Winner
Max parallel mini-vessels	24 (DASGIP), 8 (DASbox)	Not optimized for HTS	DASware
Mini-bioreactor (24–250 mL) native	DASbox 24/16/8	Not supported	DASware
Parallel sensor calibration	Simultaneous all vessels	Per-service	DASware
Statistical analysis suite	DASware analyze	External tools	DASware
Cost for 24-vessel HTS rig	Optimized	Not a fit	DASware

Academic / Research

Criterion	DASware	QB Control	Winner
Teaching labs	Capable	Affordable, visual, intuitive	QB Control
Cost (startup/undergrad labs)	Higher	Lower upfront	QB Control
Multi-group/student access	Per-license	Any browser, multi-user concurrent	QB Control
Established support community	Large, 40+ years	Growing	DASware
Publication-ready data	Charting + analyze	Graphs export (PNG, CSV) + Reports (PDF, DOCX)	Tie

12. What QB Control Can Replace

Full Replacement Scenarios

1. Benchtop Bioreactor Control (150 mL–10 L) — DASware control / SciVario / DASGIP benchtop → QB Edge + QB Modules. Value: vendor-neutral turnkey, lower TCO, days vs. weeks setup, browser-based access.

2. Multi-Vendor / Multi-Scale Operations — DASware + DASware connect bridges → QB Control single instance across benchtop + pilot + stainless-steel (≥ 150 mL). Value: no separate instances, no integration-module fees, heterogeneous-scale parallelism.

3. Stainless-Steel Pilot Cells with Existing PLCs (new) — DASware connect to DCS → QB Control on an industrial PC integrating the PLC via OPC-UA + the OPC UA Connector. Value: reuse field hardware, no Eppendorf hardware fleet, no add-on license.

4. Multi-Vendor Sensor & Analyzer Integration — DASware analyze (separate license) → native OPC-UA/Modbus + REST API with real-time feedback. Value: analyzer data triggers control actions live; no per-analyzer module fee.

5. CDMO Multi-Client Process Development — separate DASware instances per client → QB Control multi-process with import/export + device mapping. Value: one license many programs, automated per-program batch records, fast setup/teardown.

6. pH/DO/Temperature Control Loops — Eppendorf-tuned loops → QB Multisensor (Hamilton/MT) + QB Gasflow + QB Thermo + services. Value: open sensor integration, no ecosystem lock-in.

7. Academic & Teaching Labs — DASware Standard → QB Control with multi-user browser access. Value: lower cost, no per-seat licensing, intuitive visual designer.

Partial Replacement Scenarios

8. Mixed Eppendorf + Greenfield Fleets — keep existing DASGIP/DASbox systems; deploy QB Control for new ≥ 150 mL product lines. Value: avoid rip-and-replace, standardize new development on QB Control, integrate via cloud/data export.

9. Small-Scale GMP Production — QB Control provides partial 21 CFR Part 11 conformance (records, audit trails, RBAC, data integrity; e-signatures on roadmap). Value: lower validation burden (GAMP 5 Category 4) and built-in compliance, but requires manual sign-off or a DASware control plus bridge until Q3 2026.

13. Where QB Control Creates Superior Value

13.1 Time-to-Process

Metric	DASware	QB Control	Improvement
System setup	4–6 weeks (Windows/SQL config)	2–3 days (plug-and-play)	~90% faster
First run	6–8 weeks	2–3 weeks	~60% faster
Recipe modification	Hours (scripting + recompile)	Minutes (visual drag-and-drop)	~90% faster
New process configuration	Days (per-vessel)	Hours (import/export or visual config)	~80% faster

13.2 Value Summary

Each pillar is detailed in the section noted; in brief, QB Control delivers:

Lower TCO — ~40–50% lower 5-year cost for a regulated 4-vessel lab ($98K–160K vs. $205K–330K), perpetual license, all 18 modules included (no analyze/design/connect surcharges), no Windows/SQL Server licensing (§10).
No vendor lock-in — open sensors and consumables, open protocols, or reuse of existing PLCs (§5).
Operational simplicity — browser-based with no SQL Server, auto-discovery, no-code recipes, multi-user access, and a single Health Monitoring dashboard (§3, §6).
Instant strategy changes — ~40 pre-built services and reusable Service Profiles let scientists swap a control strategy in minutes, where DASware requires scripting and re-validation (§7).
Modern, open integration — native OPC-UA, REST, MQTT, SQL, MTP, and secure remote access with QR-code setup, all included (§5).
Right-sized safety & governance — P-Stop/E-Stop, Safe Position Logic, and a mandatory pre-execution checklist + Validator (§8).

14. Gaps & Limitations

DASware Capabilities Not Available in QB Control

Capability	DASware	QB Control	Impact
Sub-150 mL mini-bioreactors	DASbox (24–250 mL), native parallel HTS	Not supported (min. 150 mL)	High for screening labs
High-throughput parallel screening	16–24 identical vessels (DASGIP/DASbox)	Not optimized; multi-process at ≥ 150 mL	High for HTS
Parallel sensor calibration	Simultaneous across all vessels	Per-service	Medium
Native DoE platform	DASware design (auto-matrix + execution)	External DoE tools	Medium
Integrated analyzer suite	DASware analyze (drivers + statistics)	OPC-UA/REST (no built-in statistics)	Medium
Cloud AI analytics	BioNsight Cloud (model-based optimization)	MQTT/REST export to external platforms	Medium
Electronic Signatures	Built-in (DASware control plus)	On roadmap (Q3 2026)	High for regulated production today
Regulatory precedent	Established FDA-filed installations	Growing	Medium
Eppendorf hardware optimization	Vertically integrated, pre-validated stack	Vendor-neutral, integrator-validated combinations	Low–Medium
Global on-site service network	Eppendorf in 50+ countries	Remote-first support + regional integrators	Medium for global GMP

Honest Assessment of QB Control Limitations

Vessel-scale floor — minimum supported vessel scale is 150 mL; QB Control does not serve sub-150 mL mini-bioreactor / HTS screening (24–250 mL DASbox). This is a genuine DASware win.
Not optimized for HTS — banks of 16–24 identical screening vessels are DASware’s specialty, not QB Control’s.
No native DoE — design-of-experiments requires external tools (Design-Expert, JMP, Minitab); DASware design is integrated.
No turnkey cloud AI — BioNsight-style model-based optimization is not built in; QB Control exports to external analytics via MQTT/REST.
No electronic signatures yet — 21 CFR Part 11 conformance is partial until the Q3 2026 release.
Less single-vendor tuning — DASware’s Eppendorf-only stack is more deeply pre-validated than any multi-vendor combination.
Newer regulatory track record — DASware has longer established FDA-filed precedent.
Service-network footprint — Eppendorf’s global on-site network exceeds QB Systems’ remote-first model for 24/7 global GMP.

15. Migration & Replacement Scenarios

Scenario A: Greenfield Lab (No Existing DASware)

Recommendation: QB Control for ≥ 150 mL work. New lab from scratch = no migration, no Eppendorf lock-in. QB Control provides vendor-neutral lab/pilot bioprocessing, lower TCO, operational in days. Caveat: if the lab’s core mission is sub-150 mL parallel screening, choose DASware.

Scenario B: DASware Lab Seeking Modernization

Recommendation: QB Control replacement for benchtop/pilot ≥ 150 mL. Replace DASware control on benchtop/DASGIP systems with QB Control; keep DASbox for mini-bioreactor screening; bridge data via REST/cloud. ROI typically recovered through eliminated module/maintenance costs.

Scenario C: Stainless-Steel Pilot Cell with an Existing PLC

Recommendation: QB Control on an industrial PC. Deploy QB Control on an industrial PC, integrate the existing PLC over OPC-UA via the OPC UA Connector, and keep the field instruments. Value: SCADA-class supervisory control and recipes without an Eppendorf hardware fleet, DASware connect license, or re-engineering.

Scenario D: Expanding Multi-Vendor Capacity

Recommendation: QB Control for new vessels. Keep existing DASware for current Eppendorf bioreactors; add ≥ 150 mL capacity with QB Control + QB Modules or 3rd-party hardware; no impact on validated DASware systems; data bridge for unified reporting if needed.

Scenario E: CDMO Scaling Up Client Projects

Recommendation: QB Control for client-facing process development. Rapid setup/teardown for different client processes; process import/export + device mapping for fast replication; one license across many programs = higher margins; DASware retained for any sub-150 mL screening campaigns.

Scenario F: Academic / Research Institution

Recommendation: QB Control (full replacement) for benchtop teaching/research ≥ 150 mL. QB Control provides professional-grade control at accessible cost, multi-student browser access (no per-seat licensing), and modular hardware for curriculum flexibility. Existing Eppendorf installations and dedicated screening rigs stay with DASware.

16. Competitive Positioning Strategy

Positioning Statement

QB Control is not competing with DASware on its home turf of sub-150 mL parallel mini-bioreactor screening — it is replacing the portion of the bioprocess stack that never needed to be Eppendorf-only. DASware is a deeply tuned, ecosystem-centric platform built around DASbox/DASGIP/SciVario/BioFlo hardware, with à-la-carte modules and Windows/SQL Server infrastructure. QB Control is a vendor-neutral, browser-native SCADA-class platform for benchtop-to-pilot bioprocessing (≥ 150 mL) — and, with its industrial-PC deployment, the stainless-steel pilot cell that already has a PLC. Where a lab pays for separate analyze/connect/design licenses, a regulated control-plus tier, and recurring maintenance, QB Control delivers one perpetual license with ~40 pre-built services, built-in compliance, and ~40–50% lower 5-year TCO. For mini-bioreactor HTS, recommend DASware — and win everywhere else.

Key Sales Arguments Against DASware

DASware Pain Point	QB Control Advantage	Evidence
”Every integration is a separate license”	All protocols included — OPC-UA, Modbus, MQTT, REST, SQL, MTP	No analyze/connect surcharge
”Compliance means buying DASware control plus”	Audit trail, RBAC, data integrity built into base	One license tier
”We’re locked into Eppendorf hardware”	Open sensors, open consumables, open protocols, PLC reuse	No vendor lock-in at any level
”We run Windows + SQL Server for it”	Browser-based, embedded data store — no IT overhead	Zero Windows/SQL licensing
”Changing a control strategy means editing scripts”	Swap a service template in 5 minutes	~50–100× faster strategy changes
”Mixed scales need separate software instances”	One instance, heterogeneous-scale parallelism (≥ 150 mL)	Single QB Control instance
”Maintenance is 15–25% of license every year”	Perpetual license, optional tiered support	No recurring license tax
”Validation takes 6–8 weeks per recipe”	GAMP 5 Cat. 4 — 2–4 weeks per config	40–50% validation reduction
”CDMO work needs a license per client instance”	One license, many isolated processes	Lower cost per program

When NOT to Position Against DASware

Do NOT position QB Control as a replacement when the client needs:

Sub-150 mL mini-bioreactor screening (DASbox 24–250 mL) — QB Control does not serve this scale
High-throughput parallel screening with 16–24 identical vessels (DASGIP) — DASware is purpose-built
Native integrated DoE (DASware design) as a daily R&D dependency
BioNsight cloud AI / model-based optimization as a critical differentiator
Electronic signatures on batch release or an active IND today (before QB Control’s Q3 2026 release)
An established 16–24-vessel DASware HTS farm where revalidation cost exceeds savings
A deeply invested global Eppendorf ecosystem (20+ DASGIP/DASbox systems across many sites)

In these cases, position QB Control as complementary to DASware — handling vendor-neutral benchtop/pilot/stainless-steel (≥ 150 mL) while DASware handles mini-bioreactor screening.

17. Feature-by-Feature Matrix

#	Feature	Eppendorf DASware	QB Control	QB Advantage	Notes
CORE CONTROL
1	Bioreactor control	★★★★★	★★★★		DASware: Eppendorf-tuned; QB: PID-based services
2	Mixer/agitator control	★★★★★	★★★★★		QB native agitator modules (up to 6 vessels)
3	Pump control	★★★★	★★★★★	✅	QB: 4 pump types native + SmartPump OPC
4	Sampler control	★★★★	★★★★★	✅	QB: native selector valve (24 positions)
5	Gas flow control	★★★★★	★★★★		DASware: DASGIP MX; QB native
6	Temperature control	★★★★★	★★★★		DASware: integrated; QB: 2–42 °C
7	Valve control	★★★	★★★★★	✅	QB: Set Valve State block + three-way valves
8	Scale/weight measurement	★★★	★★★★★	✅	QB: native multiscale (6 channels)
9	Foam detection	★★★	★★★★★	✅	QB: patent-pending optical sensor
10	LED/light control	★	★★★★★	✅	DASware: not in ecosystem; QB: native
PARALLEL PROCESSING
11	Sub-150 mL mini-bioreactor HTS	★★★★★	❌		DASware: DASbox 24–250 mL exclusive
12	Parallel identical-vessel screening	★★★★★	★★★		DASware: 16–24 DASGIP vessels
13	Heterogeneous-scale parallelism	★★	★★★★★	✅	QB: benchtop + pilot + stainless steel (≥ 150 mL)
14	Sequential campaign queuing	★★★★	★★★★		QB: Pending queue + auto-stop (new)
15	Auto-generated P&ID per process	★★	★★★★★	✅	QB auto-generates; DASware vessel-centric
16	Process import/export + device mapping	★★★	★★★★★	✅	QB: one-click replication + remap
17	Parallel sensor calibration	★★★★★	★★★		DASware: all vessels simultaneously
18	Multi-user concurrent access	★★	★★★★★	✅	QB: any browser; DASware: Windows client
RECIPE, BATCH & SERVICES
19	Recipe management	★★★★	★★★★★	✅	DASware: scripted; QB: visual
20	Visual recipe designer	★★	★★★★★	✅	QB: drag-and-drop, no coding
21	Recipe versioning	★★★	★★★★★	✅	QB: Draft→Verified→Validated→Hold→Archived
22	Services Catalog	★★	★★★★★	✅	QB: ~40 services across 10 categories; DASware: none
23	Service Profiles (reusable params)	★★	★★★★★	✅	QB: grouped/atomic + portable import/export
24	Variables / Timer / Manual blocks	★★★	★★★★★	✅	QB: unified block library (new)
25	Real-time parameter editing	★★	★★★★★	✅	QB: editable during run; DASware: restart
26	Strategy switching speed	★★	★★★★★	✅	QB: swap service in minutes
27	Integrated DoE	★★★★★	★★		DASware design native; QB external tools
28	Pre-execution safety checklist	★★★	★★★★★	✅	QB: mandatory + Validator (system-enforced)
29	Batch-to-batch analytics	★★★★★	★★★		DASware: built-in (Professional)
INTEGRATION
30	OPC UA	★★★	★★★★★	✅	QB: native + Connector; DASware via connect license
31	REST API	★	★★★★★	✅	QB native; DASware lacks
32	MQTT	★	★★★★★	✅	QB native; DASware uses BioNsight
33	SQL access	★★	★★★★★	✅	QB native JDBC/ODBC, multi-engine
34	LDAP/AD SSO	★★	★★★★★	✅	QB native; DASware Windows-domain only
35	MTP support	❌	★★★★	✅	QB supported (new); DASware not native
36	Hamilton / Mettler Toledo sensors	★★★	★★★★★	✅	QB: direct; DASware via analyze license
37	External analyzer integration	★★★★★	★★★		DASware analyze native; QB via OPC/REST
38	Real-time analyzer feedback	★★	★★★★★	✅	QB: triggers control actions; DASware post-run
39	PLC reuse (Wago/Siemens/Beckhoff)	★★	★★★★★	✅	QB: industrial-PC deployment (new)
40	Cloud AI analytics	★★★★★	★★★		DASware BioNsight; QB exports to external
COMPLIANCE
41	21 CFR Part 11	★★★★★	★★★★	⚠️	DASware plus full; QB partial (no e-sigs yet)
42	GAMP 5 classification	Cat. 5	Cat. 4	✅	QB: lower validation burden
43	ISA-18.2 alarms	★★	★★★★	✅	QB formal conformance; DASware basic
44	Audit trail	★★★★	★★★★★	✅	QB built-in base; DASware needs plus
45	Electronic signatures	★★★★★	★★	⚠️	DASware plus; QB roadmap Q3 2026
46	Safe Position Logic (GMP)	★★★	★★★★★	✅	QB: built-in configurable feature
47	Regulatory precedent	★★★★★	★★★		DASware: established FDA filings
USABILITY & OPS
48	Setup time	★★	★★★★★	✅	QB: days vs. weeks
49	Learning curve	★★★	★★★★★	✅	QB: no scripting; visual designer
50	Client device flexibility	★★	★★★★★	✅	QB: any browser; DASware Windows client
51	Mobile access	❌	★★★★★	✅	QB: responsive web; DASware: none
52	Remote access	★★★	★★★★★	✅	QB: secure VPN + QR setup (new)
53	Health monitoring dashboard	★★★	★★★★★	✅	QB: consolidated module/host health (new)
54	IT overhead (Windows/SQL)	★★	★★★★★	✅	QB: no OS/DB licensing
COST & LICENSING
55	Initial investment	★★★	★★★★★	✅	QB lower for regulated setups
56	5-year TCO	★★	★★★★★	✅	~40–50% lower TCO
57	License model	★★	★★★★★	✅	QB perpetual, all-inclusive; DASware per-module
58	Module bundling	★★	★★★★★	✅	QB: all 18 modules included
59	Annual maintenance	★★	★★★★★	✅	QB optional; DASware 15–25% mandatory
60	Vendor lock-in	★★	★★★★★	✅	QB: open ecosystem
ADVANCED CAPABILITIES
61	High-throughput screening rig	★★★★★	★★		DASware exclusive (24-vessel)
62	Native DoE module	★★★★★	★★		DASware design exclusive
63	Integrated analyzer suite	★★★★★	★★★		DASware analyze exclusive
64	Cloud AI optimization	★★★★★	★★★		DASware BioNsight exclusive
65	Global on-site service	★★★★★	★★★		Eppendorf 50+ country network

Summary Scores by Category

Category	Eppendorf DASware Average	QB Control Average	Winner
Core Control	4.0	4.6	QB Control
Parallel Processing	3.8	4.0	QB Control (heterogeneous scale) / DASware (HTS)
Recipe, Batch & Services	3.2	4.6	QB Control
Integration	2.9	4.7	QB Control
Compliance	4.1	4.0	DASware (e-sigs today)
Usability & Ops	2.4	5.0	QB Control
Cost & Licensing	2.2	5.0	QB Control
Advanced Capabilities	4.8	2.4	DASware

Overall: QB Control wins in 5 of 8 categories for the target vendor-neutral, benchtop-to-pilot (≥ 150 mL) market. With its unified recipe block library, sequential auto-stop campaigns, native MTP, all-inclusive integration, secure remote access, Health Monitoring, and the industrial-PC deployment path, QB Control’s lead in Recipe/Batch, Integration, Usability, and Cost is decisive. DASware retains a genuine, decisive advantage in sub-150 mL parallel mini-bioreactor high-throughput screening (DASbox/DASGIP), native DoE (DASware design), integrated analyzers (DASware analyze), cloud AI (BioNsight), and electronic signatures today — recommend DASware for those workloads.

Recent QB Control Enhancements (current release)

The current QB Control release adds the capabilities referenced in this comparison (reflecting the current QB Control release):

Batch scheduling — recurring (daily / weekly / interval) or one-time run schedules per batch, with a calendar view, named schedules, skip-on-conflict handling, and matching audit-trail records.
Recipe portability — a recipe can be reassigned to a different process, automatically remapping its devices and services so a proven design moves between similar lines instead of being rebuilt.
Equipment changes from the P&ID — lab equipment can be added directly in the P&ID editor (auto-creating the matching inventory and process records), with freeform note elements and anchor-point piping connections; lab equipment can also be added or removed on already-deployed processes without creating a new process version.
Embedded OPC UA server — the OPC UA Connector can now run its own embedded OPC UA server, letting external OPC UA clients (e.g., MES, historians) read from QB Control directly.
Expanded catalog — six additional tangential-flow (cross-flow) filtration services and six new lab-equipment types (including cooling chamber, filter cassette, hollow-fiber filter, and vials holder).
Operations & safety — an alarm watchdog reconciling alarm state against live equipment values every 30 seconds; calibration that reserves the device during calibration (blocking conflicting operations); Protect / Interlock faceplate safeguards; audit-trail events filtered to the active license; and license-aware controls shown with explanatory tooltips.
Usability — an in-app Help section with guided walkthroughs and searchable content across every module; search across inventory tables; and Health Monitoring showing system start time and uptime.

Legal Notice & Disclaimer

Versions compared. This comparison is between QB Control (release 6.x, per the current QB Control release notes) and Eppendorf DASware® control 5 (current release). Feature statements in this document refer to these versions.

Accuracy and currency. The information provided in this comparison is based on publicly available data gathered on 20 July 2026. While we strive to keep this information accurate and up to date, product features, pricing, and terms are subject to change by the respective manufacturers. We make no warranties regarding the absolute accuracy of the competitor data, and a later release may add, change, or remove capabilities described here.

Trademarks. All trademarks, logos, and brand names are the property of their respective owners. All company, product, and service names used in this document are for identification and comparison purposes only, and use of these names, trademarks, and brands does not imply endorsement or affiliation. Eppendorf®, DASware®, DASGIP®, DASbox®, BioFlo®, BioBLU®, and BioNsight® are registered trademarks of Eppendorf SE. QB Control and QB Systems are brands of A4BEE Sp. z o.o.

Transparency note. This comparison is prepared, owned, and operated by A4BEE Sp. z o.o., the creators of QB Systems and QB Control. It was created to highlight how our product differs from other options on the market, based on objective, verifiable features.

Purpose and limitation of liability. This comparison is provided for informational and educational purposes only, to help readers build knowledge of the options available to them. It is not an assessment, audit, ranking, benchmark, or endorsement of the technical expertise, quality, safety, or performance of Eppendorf DASware® control or its vendor. A4BEE Sp. z o.o. assumes no responsibility or liability for any errors or omissions in the content, nor for any decisions made based on this information; any reliance on the comparison is at the reader’s own risk.

Comparative-advertising basis. This document is intended to align with applicable comparative-advertising and fair-use rules, including EU Directive 2006/114/EC and US nominative-fair-use principles: it compares products intended for the same needs, relies on material, relevant, verifiable, and representative features, and is not intended to mislead or to denigrate any competitor. Where a competitor capability could not be verified from public sources, it is identified as such. If you believe any statement is inaccurate or out of date, please contact [email protected] and it will be reviewed and corrected promptly.

Assumptions

To keep the comparison transparent and fair, the following assumptions and estimates were applied:

Third-party capabilities are interpreted from public vendor datasheets, brochures, manuals, and websites current at the analysis date. Where a capability was not clearly documented publicly, it is described as such (“not clearly documented,” “appears limited,” etc.) rather than asserted or denied.
Competitor pricing and total-cost-of-ownership figures are indicative estimates derived from public information and typical configurations — not vendor quotations or list prices.
QB Control reference figures are indicative, based on past quotations, and do not constitute a specific priced offer.
The comparison assumes a lab-to-pilot bioprocessing context (roughly 150 mL–50 L, plus stainless-steel pilot/production via PLC over OPC-UA); conclusions may differ at large multi-train production scale.
“QB Control” reflects the current released version at the analysis date; third-party products reflect the newest versions identified in public sources.

Sources

QB Control capabilities referenced in this document reflect QB Control release 6.x (current release).

Product and brand names listed below are trademarks of their respective owners (attributed in the Legal Notice & Disclaimer) and are used here for identification and comparison purposes only.

Analysis prepared July 2026 | Version 1.0 (v1-July) | QB Systems vs. Eppendorf DASware competitive positioning QB Systems — Flexible. Innovative. Limitless. | A product brand of A4BEE Sp. z o.o. | https://qb.systems