Eppendorf DASware® vs. QB Control

Comprehensive Comparison for Bioprocessing Automation

1. Executive Summary

DASware Platform Overview

Eppendorf DASware is a comprehensive bioprocess control software ecosystem specifically designed around Eppendorf's hardware portfolio. The platform consists of five core components:

• DASware control : Core process control software for parallel bioreactor systems (Standard and Professional editions)

• DASware control plus : Regulated variant with 21 CFR Part 11 and EudraLex Volume 4 Annex 11 compliance, electronic signatures, and audit trails (licensed separately)

• DASware analyze : External analyzer integration module for nutrient analyzers, cell counters, biomass monitors, HPLC systems, mass spectrometry, and Raman spectroscopy

• DASware design : Design-of-Experiments (DoE) integration module

• DASware connect : OPC connectivity bridge to third-party Distributed Control Systems (DCS)

• BioNsight Cloud : Cloud-based remote monitoring, data contextualization, AI-driven analysis, and model-based optimization (introduced in DASware 6)

DASware is engineered primarily for high-throughput screening with parallel mini-bioreactor systems (DASbox, DASGIP) and represents a mature, specialized solution within the Eppendorf ecosystem.

• Hardware : QB Edge (Linux ARM-based controller, IP40, 7× PoE LAN, 48V DC, CE marked)

• Modular I/O ecosystem : 20+ IP40 plug-and-play modules (pumps, sensors, agitators, scales, gas controllers, valves)

• Software : 17 integrated modules covering process control, P&ID design, alarm management, recipe orchestration, data acquisition, calibration, audit trails, user management, notifications, reporting, and backup/export

• Service catalog : 37 pre-configured services across 10 categories (pH Control, Temperature Control, Pump & Feed, Gas Control, Gas Volume Delivery, Sampling, Stirring & Agitation, Foam Control, Valve Control, LED & Light Control)

• Connectivity : OPC-UA, Modbus, MQTT, Profibus, Serial, Bluetooth, WiFi, REST API, SQL database integration, LDAP/AD

Core Platform Distinction

Aspect	DASware	QB Control
Design Philosophy	"Eppendorf Ecosystem Software"	"Universal Bioprocess Automation"
Primary Use Case	Parallel mini-bioreactor high-throughput screening	Flexible bioprocess control across vessel scales
Hardware Binding	Tightly coupled to Eppendorf hardware	Vendor-agnostic, modular integration
Architecture Pattern	Windows-based client-server (SQL Server database)	Embedded Linux ARM controller (browser-based UI)
Regulatory Foundation	Standard (unregulated); Plus (21 CFR Part 11 via separate license)	Partial 21 CFR Part 11 built-in; e-signatures on roadmap
Integration Model	Ecosystem-first; 3rd-party via bolt-on modules	API-first; native multi-vendor support
Deployment Model	On-premises Windows PC	Edge computing + cloud-ready

Replacement Viability Quick Reference

Scenario	DASware Strength	QB Control Strength	Viability
4–8 vessel parallel screening	Proven, optimized for small scale	General-purpose, less optimized	Fair — QB adequate; DASware specialized
Mixed vessel scales (benchtop + pilot)	Limited; requires separate systems	Unified platform for scales ≥100 mL (no sub-100 mL mini-bioreactor support)	QB advantage for benchtop-to-pilot; DASware for mini-scale
Multi-vendor sensor integration	Via DASware analyze + connect (modules)	Native OPC-UA, no additional cost	Strong QB advantage
Regulated manufacturing (GMP)	Via DASware control plus (separate license)	Partial compliance; e-signatures roadmap	Requires evaluation per audit trail depth
Cost-conscious labs	Higher total cost of ownership	Predictable, lower TCO	QB advantage
Existing Eppendorf fleet	Seamless integration	Migration planning required	DASware advantage
Vendor independence	Not a strength	Core design principle	QB advantage
Cloud + remote monitoring	BioNsight cloud (DASware 6+)	Native support, zero additional cost	QB advantage

2. Platform Philosophy

DASware: "iTunes for Bioreactors"

DASware embodies a tightly integrated, ecosystem-centric design philosophy . The software is engineered specifically around Eppendorf's hardware product lines:

• DASbox Mini Bioreactor (60–250 mL): single-use, parallel operation up to 8–16 vessels

• DASGIP Parallel Bioreactor System : modular, vessels from 50 mL to multi-liter scales

• SciVario twin : bench-top bioreactor platform

• BioFlo series (120/320/720): single-vessel bioreactors at pilot and production scales

This hardware-first approach yields several strategic advantages :

• Optimized control algorithms specifically tuned for Eppendorf sensor and actuator performance

• Deep integration with hardware capabilities (e.g., parallel sensor calibration across 8+ DASbox vessels simultaneously)

• Simplified setup and configuration for end users already committed to the Eppendorf ecosystem

• Proven, battle-tested compatibility matrix

However, this approach also imposes inherent constraints :

• Strong vendor lock-in: moving away from Eppendorf hardware requires system redesign or module add-ons (DASware connect, analyze)

• Limited flexibility for multi-vendor bioprocess environments

• Parallel operation is fundamentally tied to identical or similar vessel geometries and sensor suites

• For organizations running mixed platforms (Eppendorf mini-scale parallel + Sartorius/CellGenix pilot scale), DASware requires separate software instances or integration bridges

• Hardware abstraction : The QB platform provides a standardized service layer above heterogeneous hardware (QB Modules, third-party sensors via OPC-UA/Modbus, external analytics via REST API)

• Composability : 37 reusable services can be composed into recipes without scripting; new hardware is "plugged in" via standard protocols

• Scale independence : A single QB Control instance can orchestrate vessels ranging from 100 mL benchtop bioreactors to 500+ L pilot/production scale (note: QB Control does not currently support sub-100 mL mini-bioreactor formats)

• Openness : Native support for OPC-UA, Modbus, MQTT, SQL, LDAP/AD allows integration with existing DCS environments (DeltaV, PCS 7, ABB 800xA, etc.)

• Cloud readiness : Designed for distributed edge-to-cloud architectures; BioNsight integration is a natural extension, not a bolt-on

Strategic advantages :

• Future-proofs against hardware vendor changes (sensors, pumps, gas controllers can be swapped via OPC or Modbus)

• Single platform for portfolio-wide bioprocess management (lab scale through manufacturing)

• No licensing friction for multi-vendor integration; all protocols are included

• Modern, containerizable architecture supports remote monitoring and distributed teams

Trade-offs :

• Requires explicit hardware configuration (no plug-and-play discovery for non-QB modules, though QB modules auto-discover)

• Less specialized tuning for any single hardware platform (but superior flexibility across platforms)

• Regulatory compliance is partial (audit trails, RBAC, data integrity built-in; e-signatures still on roadmap)

Philosophical Comparison

Philosophy Dimension	DASware	QB Control
Hardware Model	Optimized for Eppendorf family	Modular, vendor-agnostic
Integration Model	Ecosystem-centric; 3rd-party via modules	API/protocol-first; native multi-vendor
Future Flexibility	Tied to Eppendorf roadmap	Independent of hardware vendor roadmap
Organization Fit	Single-vendor bioprocess labs	Multi-vendor or scale-variable operations
Configuration Complexity	Low (pre-tuned); high for off-platform hardware	Moderate (service profiles); low for QB modules
Regulatory Philosophy	Compliance via separate Plus license	Compliance as core platform feature (partial)
Upgrade Path	DASware 5/6/future releases; hardware refresh cycles	Continuous; hardware-independent

3. Architecture & Hardware

System Architecture Comparison

Component	DASware	QB Control
Operating System	Windows (PC, Workstation, Server)	Linux ARM (QB Edge embedded controller)
Database	Microsoft SQL Server (Professional edition)	Embedded relational database (Linux-native)
Processing Unit	Host PC CPU	ARM processor (QB Edge: onboard Cortex-A class)
User Interface	Windows desktop application	Web browser (no client installation)
Network Stack	Ethernet, USB to Eppendorf hardware	7× PoE LAN ports (QB Modules, sensors, systems)
Power Requirements	Dependent on host PC	QB Edge: 48 VDC, 220W max
Form Factor	Desktop/tower workstation	19" rack mountable (1U) or compact edge controller
Data Persistence	SQL Server (on-premises or via cloud connector)	Embedded; optionally exported to cloud
Connectivity	USB, Ethernet, optional OPC (via DASware connect)	Ethernet (7 PoE ports), WiFi, Bluetooth, serial, REST API, MQTT
Hardware Discovery	Manual configuration per hardware type	Auto-discovery for QB Modules; manual for 3rd-party via OPC/Modbus
Dependency on Vendor Hardware	High (DASbox, DASGIP, BioFlo required for full control)	Modular (QB Modules for native control; OPC/Modbus for 3rd-party)

DASware Hardware Ecosystem

Primary Supported Platforms:

• DASbox Mini Bioreactor (60, 100, 250 mL)

• Parallel operation: up to 8 individual units (DASbox 4-fold or 8-fold)

• Single-use bioreactors with integrated sensors (pO₂, pH, temperature)

• Controlled via USB interface to host PC

• DASGIP Parallel Bioreactor System

• Modular, vessels: 50 mL → multi-liter

• Supports 16–24 parallel vessels depending on configuration

• Benchtop to small-scale production platform

• SciVario twin

• Bench-top twin-vessel system

• 500 mL–2 L per vessel

• Integrated control module

• BioFlo Series (120, 320, 720)

• Single-vessel control

• Pilot to production scale

• Integrated bioreactor control unit

Connectivity:

• USB interface for DASbox Mini

• Ethernet for DASGIP and BioFlo systems

• Optional analog/digital I/O for external sensors

• DASware connect (module): OPC interface to 3rd-party sensors and DCS systems

Analyzer Integration via DASware Analyze:

• Nutrient analyzers (Aqua Trak, Yellow Spring Instruments YSI)

• Cell counters (automated or via integration API)

• Biomass monitors (in-situ turbidity probes)

• HPLC and mass spectrometry systems

• Raman spectroscopy

QB Edge Controller (Core Platform):

• ARM Cortex-A class processor (Linux OS)

• 7× PoE LAN ports (Power over Ethernet)

• 48 VDC, 220W max power consumption

• IP40 rating (suitable for benchtop; not suitable for humid clean rooms requiring IP67)

• CE marked; compact form factor

• Embedded database and web server (no external PC required)

• Pump Modules : peristaltic, membrane, piston pumps (various flow rates)

• Sensor Modules : pH, dissolved oxygen (pO₂), temperature, pressure

• Agitator Modules : mechanical stirring, orbital shaking, paddle agitation

• Scale Modules : integrated weigh platforms for feed and harvest

• Gas Control Modules : mass flow controllers, atmospheric or pure gas channels

• Valve Modules : solenoid and proportional valve control

• Sampling Modules : automated sampling loops, aseptic connectors

• Foam Control Modules : antifoam pump or probe-based detection

• LED/Light Modules : optical monitoring, illumination control

All modules auto-discover on the PoE network and integrate via standardized service drivers.

Multi-Vendor Integration (via standard protocols):

• OPC-UA : Hamilton, Mettler Toledo, Sartorius, INFORS HT, Applikon, and most commercial sensors

• Modbus : Legacy sensors, PLCs, VFDs, flow meters

• MQTT : Cloud services, IoT integrations, data streaming

• REST API : Custom analyzers, external data systems

• SQL/JDBC/ODBC : Direct database integration for ERP, LIMS, MES

• LDAP/AD : Enterprise user management

Native Sensor Support:

• Hamilton Sensors : via QB Multisensor (MTS-001) integrating Hamilton pH, pO₂, pressure, temperature

• Mettler Toledo Sensors : native driver support

• Additional sensors via OPC-UA discovery

Architectural Implications

Implication	DASware	QB Control
Windows PC Required?	Yes	No (QB Edge is self-contained)
Hardware Discovery	Manual per system type	Auto-discovery for QB Modules
Scalability	Limited by Windows PC resources; parallel via vessel replication	Built for distributed architecture; scale via additional QB Edge instances or edge-to-cloud
Redundancy	Single point of failure: host PC	QB Edge is single point; mitigated via backup/export module and cloud sync
Sensor Integration	Tight coupling to Eppendorf sensors; 3rd-party via DASware analyze/connect modules	Native support for multi-vendor via OPC/Modbus; QB Modules plug-and-play
Future-Proofing	Dependent on Eppendorf hardware roadmap and software updates	Hardware-independent; software updates don't require hardware refresh
Compliance with IT/OT Standards	Proprietary Windows environment	Aligns with industrial Ethernet (PoE), OPC-UA, REST API standards

4. Parallel Processing

DASware Parallel Capability

DASware is purpose-built for parallel mini-bioreactor high-throughput screening . The platform excels in this domain:

Parallel Operation Modes:

• DASbox Mini (Standard) : supports 4-fold system (4 vessels × 100 mL) controlled as a unified platform

• DASbox Mini (Extended) : supports 8-fold system (8 vessels × 60–100 mL) with independent or synchronized control

• DASGIP (Advanced) : supports 16–24 parallel vessels with independent process parameters per vessel

• Synchronized Parallel : multiple vessels running identical protocols with parallel sensor calibration and synchronized data collection

Key Parallel Strengths:

• Vessel Replication Design : All vessels share identical hardware (sensors, actuators, geometry), enabling true parallel operation without individual controller overhead

• Unified Data Collection : Single database (SQL Server) consolidates all parallel runs; easy batch-to-batch comparison

• Parallel Calibration : Sensor calibration can be performed simultaneously across all 8+ vessels, reducing setup time from hours to minutes

• High-Throughput Compatible : Optimized for rapid screening workflows (DoE, parameter exploration, strain/media comparison)

• Professional Edition Analytics : online batch-to-batch comparison, online calculated values, trend analysis across parallel runs

Parallel Limitations:

• Vessel geometry must be identical or near-identical for reliable parallel control (mixing time, oxygen transfer differ significantly across scales)

• Sensor suite must match across all vessels (no mix-and-match sensor configurations)

• Hard limit at 8–24 vessels depending on hardware; not designed for larger parallel sets (e.g., 96-well high-throughput)

• Scaling beyond 24 vessels requires multiple DASware instances and manual orchestration

• Independent Process Orchestration : Multiple, independent bioprocess recipes can execute simultaneously on a single QB Edge instance, each with its own set of QB Modules, sensors, and actuation

• Shared Resource Management : Multiple processes can coordinate resource access (e.g., two fermenters competing for a single media pump via service priority/sequencing)

• Scale-Heterogeneous Parallelism : A single QB Control instance can simultaneously manage:

• 4× parallel benchtop bioreactors (1–5 L, process development)

• 1× pilot-scale vessel (50 L)

• 1× production-scale vessel (500 L)

• All with independent parameter sets, sensor suites, and recipe workflows

• Note : QB Control does not currently support sub-100 mL mini-bioreactor formats (e.g., DASbox 60 mL); minimum supported vessel scale is 100 mL

• Service-Level Parallelism : The Recipe Designer Board allows 37 services to be composed into parallel execution paths (e.g., simultaneous temperature ramp, pH adjustment, and feed addition)

Parallel Strengths:

• Heterogeneous Scale Support : Unlike DASware (which requires identical vessels), QB Control seamlessly manages different bioreactor scales and sensor configurations in parallel

• Flexible Service Composition : Parallel operations are defined via visual DAG workflow (no scripting required)

• Independent Parameter Control : Each process has its own service profiles, set-points, alarm thresholds, and control logic

• Distributed Edge Model : Multiple QB Edge instances can be orchestrated via REST API or cloud connector for ultra-high parallelism (e.g., 10 QB Edge controllers = 100+ processes)

• Multi-Scale Screening : Support for simultaneous mini (lab scale) + pilot (GMP-ready) operations

• Less optimized for small-scale identical-vessel high-throughput screening (DASware is specialist here)

• Shared resource contention requires explicit service sequencing/priority in recipe design

• Multi-QB-Edge orchestration requires additional automation layer (not built-in)

Parallel Processing Comparison Table

Capability	DASware	QB Control
Max Parallel Vessels (Same Scale)	24 (DASGIP); 8 (DASbox)	Unlimited (via multiple Edge instances)
Heterogeneous Scale Parallelism	Limited (requires vessel matching)	Native (benchtop + pilot + production simultaneously; min. 100 mL)
Parallel Calibration	Yes, all vessels simultaneously	Yes, per-service basis
Parallel Recipe Execution	All vessels run identical recipe	Independent recipes per process
Sensor Config Flexibility	Identical across parallel vessels	Independent per vessel/process
High-Throughput Optimization	Excellent (DoE, parameter sweep)	Good (general-purpose)
Multi-Scale Orchestration	Requires separate DASware instances	Single QB Control instance
Data Collection Speed	Fast (unified SQL Server backend)	Fast (embedded database + cloud export)
Scalability Beyond 24 Vessels	Manual multi-instance management	API-driven edge clustering

5. Multi-Vendor Integration

DASware Integration Strategy

DASware's multi-vendor integration follows a modular, add-on approach :

Native Support (Tightly Integrated):

• All Eppendorf hardware platforms (DASbox, DASGIP, BioFlo, SciVario)

• Standard Eppendorf sensor suite (pH, pO₂, temperature, pressure, optical density)

• Parallel sensor calibration workflow

Extended Integration via Modules:

• DASware Connect (OPC/Modbus Gateway)

• Function : Bridges DASware control to third-party Distributed Control Systems (DCS) and sensors

• Protocols : OPC (both OPC DA and OPC-UA), Modbus TCP/RTU

• Integration with DCS platforms: Siemens DeltaV, Siemens PCS 7, ABB 800xA

• Connection to third-party sensors: pressure transmitters, flow meters, gas analyzers

• Bidirectional data flow: DASware sends commands to DCS; DCS reads bioreactor parameters from DASware

• Licensing : Separate module license

• Configuration : Requires manual OPC server setup and tag mapping

• DASware Analyze (External Analyzer Integration)

• Function : Integration with offline and online analytical instruments

• Supported Instruments :

• Nutrient analyzers: YSI Aqua Trak, Roche Cedex, others via API

• Cell counters: Vi-Cell, Nexcelom, CountESS

• Biomass monitors: in-situ turbidity probes, off-gas analysis

• Chromatography: HPLC systems (via data file import or API)

• Mass spectrometry: metabolite analysis workflows

• Raman spectroscopy: real-time biomass/product measurement

• Data Flow : Results are pulled into DASware database; integrated into run reports and batch comparison

• Licensing : Separate module license per analyzer type or bundle

• Configuration : Vendor-specific drivers or API integration

• DASware Design (DoE Integration)

• Function : Design-of-Experiments workflow integration

• Capabilities : Experiment design, factorial planning, optimization

• Integration : Generates multi-vessel screening protocols; results analyzed in DASware Analyze

Integration Limitations:

• Each third-party connection requires a separate module license (DASware connect, analyze)

• No native OPC-UA client (though DASware connect can expose a server)

• Manual configuration required for non-Eppendorf hardware

• Limited real-time feedback loop from external analyzers to DASware process control (analyzer results are logged post-facto)

Native Protocols (Included, No Additional License):

• OPC-UA : Industry standard, widely supported across sensor and equipment manufacturers

• Modbus TCP/RTU : Legacy systems, flow meters, PLC integration

• MQTT : Cloud and IoT platform integration

• REST API : Custom analyzers, data services, external applications

• Serial (RS-232/RS-485) : Legacy sensors, specialized instruments

• Bluetooth : Wireless sensors, asset tracking

• WiFi : Wireless network access for remote QB Modules

• SQL/JDBC/ODBC : Direct database connectivity for ERP, LIMS, MES systems

• LDAP/AD : Enterprise user management integration

• Hamilton Sensors : pH, pO₂, pressure, temperature via QB Multisensor (MTS-001)

• Mettler Toledo : Native driver support

• Any OPC-UA or Modbus-compatible sensor (no additional licensing)

Multi-Vendor Integration Examples:

• Pharming Setup :

• Mettler Toledo pH/pO₂ sensors via native driver

• Sartorius downstream process sensors via OPC-UA

• LIMS integration via REST API (data push/pull)

• DCS integration via OPC-UA (read process parameters, write setpoints)

• Perfusion Bioprocess :

• External cell density sensor via Modbus (e.g., Aber Ismatec)

• HPLC data integration via REST API webhook

• Cloud analytics via MQTT (real-time metabolite data)

• Multi-Site Orchestration :

• Site A: QB Control (lab scale, 5 fermenters)

• Site B: QB Control (pilot scale, 1 fermenter)

• Integration: REST API + SQL database sync; centralized dashboards via cloud

Integration Advantages:

• No additional licensing; all protocols included

• Vendor-agnostic; can swap sensor suppliers without software licensing friction

• Real-time feedback: external analyzer data can trigger QB Control service actions (e.g., adjust feed if cell density drops)

• Direct database integration: no intermediate data transformation layer required

Multi-Vendor Integration Comparison Table

Integration Aspect	DASware	QB Control
OPC-UA Support	Via DASware connect module (licensed separately)	Native (included)
Modbus Support	Via DASware connect module (licensed separately)	Native (included)
MQTT Support	Not available	Native (included)
REST API	Not available	Native (included)
Direct DB Integration	Not available	Native (included)
LDAP/AD Support	Windows domain integration only	Native (included)
Hamilton Sensors	Via DASware analyze module	Native (included)
Mettler Toledo	Via DASware analyze module	Native (included)
External Analyzers	DASware analyze (separate license)	OPC-UA or REST API (included)
DCS Integration	DASware connect (separate license)	OPC-UA or Modbus (included)
Cloud/IoT	BioNsight cloud (DASware 6+)	Native MQTT, REST API
Real-Time Analyzer Feedback	Post-run (logged only)	Real-time (can trigger process actions)
Multi-Site Orchestration	Manual; separate DASware instances	REST API + cloud connector
Licensing Model	Per-connection/per-module	All-inclusive

6. Software Module Comparison

Module Inventory

DASware and QB Control both provide comprehensive software module suites, though with different architectures and organization.

• Inventory: equipment, consumables, spare parts management

• System: QB Edge configuration, diagnostics, status

• Process: core bioprocess control engine

• P&ID: Process & Instrumentation Diagram design and visualization

• Alarm Management: ISA 18.2 compliant alarm design, thresholds, escalation

• Recipe: batch recipe definition, scheduling, versioning

• Graphs: real-time charting, multi-parameter visualization

• Reports: run summaries, batch records, compliance reports (CSV, PDF)

• Runs: execution history, run logs, performance data

• Calibration: sensor calibration workflows, certificate tracking

• Audit Trail: all system changes logged with user, timestamp, before/after values

• Users & Roles: user authentication, role-based access control (RBAC), permission management

• Notifications: alarms, email alerts, SMS, Slack webhooks, custom notification rules

• Backup & Export: automatic backup, data export (CSV, Excel, JSON), disaster recovery

• License Management: license provisioning, usage tracking, renewal notifications

• Settings: system settings, default parameters, integration configuration

• [Additional integrations via OPC-UA, Modbus, REST API]

DASware Modules (Functional Grouping):

• Core : DASware control (Standard and Professional editions)

• Process monitoring and control (batch execution, parameters, sensor data)

• Recipe management (sequential workflows, parameter profiles)

• Data logging (to SQL Server database)

• Charting and visualization (real-time trends, historical comparison)

• Reporting (batch summary reports, data export)

• User management (basic authentication)

• Regulatory : DASware control plus (separate license)

• 21 CFR Part 11 compliance (audit trails, e-signatures, data integrity)

• EudraLex Volume 4 Annex 11 compliance (EU pharmaceutical GMP)

• Electronic signatures (legal validation)

• Qualification and validation workflows

• Extended : Optional add-on modules (separate licenses)

• DASware analyze : External analyzer integration

• DASware design : DoE integration

• DASware connect : OPC/Modbus gateway

• BioNsight cloud : Cloud-based remote monitoring (DASware 6+)

Detailed Module Comparison Matrix

Module Category	QB Control	DASware	DASware Plus
Process Control	Process module (core)	DASware control (core)	DASware control plus (separate license)
P&ID Design	P&ID module (built-in)	Not available	Not available
Recipe Management	Recipe module + Designer Board	Recipe management (sequential/scripted)	Same as standard
Real-Time Charting	Graphs module	Charting (basic to advanced)	Same as standard
Batch Records	Reports + Runs modules	Data export + reporting	Enhanced audit trail reports
Data Logging	Embedded database + SQL integration	Microsoft SQL Server	Same + compliance features
Alarm Management	Alarm Management (ISA 18.2)	Basic alarm configuration	Same + audit trail
Sensor Calibration	Calibration module	Manual workflow or via recipe	Same + electronic proof
Audit Trail	Audit Trail module (built-in)	Not available	DASware control plus (critical)
E-Signatures	Roadmap (not yet available)	Not available	DASware control plus (supported)
RBAC	Users & Roles module	Basic authentication	Enhanced role-based control
Notifications	Notifications module (email, SMS, Slack)	Manual log review	Same as standard
Backup & Export	Backup & Export module (automatic)	Manual export, no built-in backup	Same as standard
License Management	License Management module	Not available	License activation only
Inventory	Inventory module (equipment, consumables)	Not available	Not available
External Analyzers	OPC-UA/REST API (native)	DASware analyze (module)	Same + audit trail
DoE Integration	Service-based (custom recipes)	DASware design (module)	Same as standard
DCS Integration	OPC-UA/Modbus (native)	DASware connect (module)	Same as standard
Cloud Monitoring	Native (built-in)	BioNsight cloud (DASware 6+, separate)	Same

Module Licensing Implications

DASware Licensing Model:

• Base : DASware control Standard (single license, per-system or per-vessel)

• Upgrade : DASware control Professional (additional cost; adds online batch-to-batch comparison, online calculated values, alarm notification)

• Regulatory : DASware control plus (separate, per-system license; includes 21 CFR Part 11 compliance)

• Extensions : Each module (analyze, design, connect) licensed separately

• Pricing : Quote-based; typically $5,000–$15,000+ per module per site

• Single License Tier : All 17 modules included

• Tiered Pricing : Based on edge hardware (Entry $15K–25K, 4-vessel $60K–85K, 6-vessel ~$100K, Pilot $150K–250K)

• Support Tiers : Basic, Standard, Premium (paid annually; includes updates, technical support)

• No Add-on Module Costs : All protocols (OPC-UA, Modbus, MQTT, REST) included

Cost Implication Example:

Scenario: Lab with 4 DASbox systems + external nutrient analyzer + Siemens DCS integration + GMP compliance

System	DASware Stack	QB Control Stack
Base Control	DASware control Pro (4 licenses)	QB Control 4-vessel
Regulatory	DASware control plus (4 licenses)	Built-in (no additional cost)
Analyzer Integration	DASware analyze (1 license)	OPC-UA driver (included)
DCS Integration	DASware connect (1 license)	OPC-UA (included)
Estimated Cost	$40K–80K+	$60K–85K (includes support)
Cost Advantage	DASware if only parallel mini-scale	QB Control (simpler licensing, no module overlap)

7. Services Catalog & Rapid Deployment

Service Categories & Count:

• pH Control (6 services):

• Continuous pH adjustment (acid/base pump control)

• pH setpoint ramp

• pH deadband control

• pH trend analysis

• pH probe diagnostic

• pH calibration routine

• Temperature Control (6 services):

• Continuous temperature control (heating/cooling loops)

• Temperature setpoint ramp

• Temperature deadband

• Temperature trend monitoring

• Probe diagnostic

• Calibration routine

• Pump & Feed Control (9 services):

• Continuous feed (peristaltic/piston pump control)

• Pulse feed (timed bolus additions)

• Feed ramp (gradual increase over time)

• Feed based on external signal (biofeed, OD-based)

• Pump priming

• Pump diagnostics

• Multi-pump sequencing

• Flow rate monitoring

• Pump maintenance tracking

• Gas Control (4 services):

• Continuous gas blending (air, O₂, N₂, CO₂)

• Gas setpoint ramp

• Gas cascade control (O₂-driven air/pure O₂ blend)

• Gas probe diagnostic

• Gas Volume Delivery (1 service):

• Volumetric gas tracking and reporting (mass balance)

• Sampling (3 services):

• Scheduled sampling (time-based)

• Condition-triggered sampling (e.g., at OD > 5)

• Sample loop flushing and aseptic collection

• Stirring & Agitation (2 services):

• Continuous agitation control (RPM setpoint)

• Agitation ramp or feedback control (based on power consumption)

• Foam Control (2 services):

• Antifoam pump control (continuous or on-demand)

• Probe-based foam detection and automatic antifoam addition

• Valve Control (2 services):

• Solenoid valve on/off

• Proportional valve setpoint control

• LED & Light Control (2 services):

• LED intensity control (brightfield/fluorescence)

• Light-based measurement integration (optical density, cell counting)

Service Profiles:

• Reusable Templates : Each service can be parameterized as a profile (e.g., "Standard Feed Profile" with pre-set flow rate, volume, timing)

• Load & Execute : Drop a service profile into a recipe; no additional configuration required

• Composition : Multiple services can execute in parallel, sequence, or conditional logic (via Designer Board)

Service Type Classification:

• Continuous Services (32): Execute during process run (pH, temperature, pump, gas, agitation, foam control)

• Autocomplete Services (5): Execute once and complete (calibration, priming, diagnostic, maintenance alert)

Deployment Example: Rapid E. coli Fermentation Setup

Traditional Approach (without services):

• Configure pH loop: set PID tuning, select pump module, define alarm thresholds

• Configure temperature: select heating/cooling module, PID parameters, ramp profile

• Configure feed: select pump, timing logic, volume calculations

• Configure aeration: select gas blender, cascade logic

• Configure data logging and alarms

• Estimate time: 4–8 hours of configuration

• Load "pH Control" service (6 services, pick standard acid/base configuration): 5 minutes

• Load "Temperature Control" service (pre-tuned for 37°C, 0.5°C deadband): 2 minutes

• Load "Feed Control" service profile "Exponential Feed" (predetermined rates): 2 minutes

• Load "Gas Control" service profile "Cascade 40% pO₂": 2 minutes

• Load "Agitation" service (300 RPM constant): 1 minute

• Compose into recipe using Designer Board (drag-and-drop): 5 minutes

• Total: ~20 minutes (vs. 4–8 hours traditional)

DASware Recipe & Automation Approach

DASware implements scripting-based recipe management :

Recipe Structure:

• Sequential control flow (if-then-else, loops, wait conditions)

• Parameter profiles (time-dependent setpoints, profiles loaded from database)

• Linked to external analyzers via DASware analyze

• Alarm thresholds and escalation rules

Automation Capabilities:

• Script-based logic (non-visual)

• Template recipes for standard processes (fermentation, perfusion, fed-batch)

• Parallel sensor calibration (simultaneous across 8+ vessels)

• Batch-to-batch comparison and trending (Professional edition)

Deployment Comparison:

Aspect	QB Services	DASware Recipes
Configuration Time	20–30 minutes (service-driven)	2–4 hours (script-based)
Programming Required?	No (visual DAG composition)	Basic scripting (or manual profile setup)
Reusability	High (service profiles)	Moderate (recipe templates)
Parallel Execution	Native (DAG-based)	Possible (via script logic)
Real-Time Adjustment	Service parameters editable live	Recipe modification requires restart
Validation/Qualification	Service profiles pre-tested (GAMP 4)	Custom scripts require testing (GAMP 5)
Learning Curve	Moderate (understand services)	High (script syntax and logic)

Rapid Deployment Impact

• Pre-tested service library reduces validation/qualification burden (GAMP Category 4)

• Drag-and-drop recipe composition minimizes training requirements

• New bioprocess deployment: 1–2 days (configuration only)

• Suitable for rapid research iteration, DoE campaigns

DASware Advantage:

• Fine-grained control for complex, specialized processes

• Deep customization possible via scripts

• Suitable for optimized production workflows

• Better for legacy recipe migration from other platforms

8. Recipe Engine

Recipe Designer Board Components:

• Operations (12 Control Flow Types):

• Start : Initiates recipe execution (required)

• Stop : Terminates recipe, logs run completion

• End : Normal completion node

• Wait : Pause for specified duration (e.g., "Wait 24 hours")

• Wait Until : Conditional pause (e.g., "Wait until OD > 5")

• Conditional : If-then-else branching (e.g., "if pO₂ < 20%, add O₂")

• Counter : Loop with count (e.g., "sample every 4 hours for 10 iterations")

• Polygon : Multi-node parallelization (e.g., simultaneous feed + aeration ramp)

• PID : Custom PID loop definition (rare; standard services preferred)

• Split : Parallel path creation

• Merge : Convergence of parallel paths

• Manual Operation : Human action node (e.g., "Add seed culture manually")

• Services (37 pre-configured services from 10 categories):

• Drag service onto Designer Board

• Configure service parameters (setpoint, duration, etc.)

• Link into DAG workflow

• Recipe Versioning :

• Draft (Yellow): Under development, not executable

• Verified (Blue): Checked for syntax/configuration, ready for testing

• Validated (Green): Tested and approved for GMP runs

• Archived (Red): Retired recipes (historical reference)

• Execution Boards :

• Batch Board : Group multiple recipes into a batch sequence (e.g., "seed culture → main fermentation → harvest")

• Executions Board : Run history, performance metrics, parameter logs, time-series data download

Recipe Example: Fed-Batch Fermentation

[Start]

[Temperature Control (37°C setpoint)] ← (parallel services)

[pH Control (7.0 setpoint)]

[Agitation (300 RPM)]

[Gas Control (cascade 40% pO₂)]

[Wait Until OD > 0.5] (initiation condition)

[Feed Control - Exponential Profile (ramp over 24 hours)]

[Conditional: if pO₂ < 20%]

├─ Yes → [Gas Control - increase O₂ blend]

└─ No → [Wait 10 minutes, check again]

[Sampling - every 4 hours] (continues in parallel)

[Wait Until time > 48 hours]

[Harvest Pump] (pulse feed)

[Cooling to 4°C]

[Stop]

Recipe Engine Strengths:

• Visual, intuitive; no scripting required

• Parallel service execution is native (polygon/split nodes)

• Versioning and audit trail (GAMP 4 compatible)

• Parameters editable at runtime without stopping process

• Real-time alarming and conditional branching

• Service reuse across recipes (DRY principle)

Recipe Engine Limitations:

• Complex loops and dynamic parameter calculation require custom logic (handled via REST API or custom operation)

• No symbolic algebra or advanced math operations (DoE optimization must be external)

DASware Recipe Engine: Scripted Profiles

DASware implements sequential, profile-based recipe management :

• Recipe Definition : XML-based or interface-driven configuration

• Parameter Profiles : Time-dependent setpoint tables

• Example: Temperature ramp from 20°C to 37°C over 2 hours, then hold

• Example: Feed rate starts at 0, increases linearly to 10 mL/h at t=6h, then maintains

• Conditional Logic : If-then rules (e.g., "if pH > 7.5, add acid")

• Alarm Thresholds : Min/max limits per parameter

• Data Logging : Sampling rate, parameters to log, database storage

Recipe Scripting:

• DASware uses a proprietary scripting language (not standard programming language)

• Syntax example: IF pO2 < 20 THEN AddAir; WAIT 300; ENDIF

• Recipes are compiled and executed sequentially

Recipe Example: Parallel 8-DASbox Screening

All 8 DASbox vessels run the same recipe simultaneously:

• Initialize sensors (parallel calibration across all vessels)

• Load seed culture (manual step, all vessels)

• Start fermentation at 37°C, 300 RPM

• Log pH, pO₂, OD every 30 seconds

• If pO₂ drops below 20%, increase air flow (automatic)

• At t=24h, harvest all vessels

• Export data to SQL Server

Professional Edition Enhancements:

• Online batch-to-batch comparison during fermentation

• Online calculated values (specific growth rate μ, oxygen uptake rate OUR, etc.)

• Alarm notification system (email, log alert)

• Proven, mature; 15+ years of bioprocess validation

• Parallel recipe execution across all vessels simultaneously

• Built-in DoE integration (via DASware design module)

• Parameter profiling intuitive for standard fermentation workflows

• Tight integration with sensor calibration and data logging

• Not visual; requires learning proprietary scripting language

• Sequential logic primarily; complex parallel branching less intuitive

• Recipes must be saved and recompiled; not editable at runtime

• No native support for conditional branching based on real-time data (requires manual intervention or add-on)

• Limited dynamic parameter calculation without external tools

Recipe Engine Comparison Table

Feature	QB Control	DASware
Design Interface	Visual DAG (Designer Board)	Scripted (proprietary language) or profile-based
Code-Free Configuration	Yes (100% visual)	Partial (profiles visual; logic requires scripting)
Parallel Execution	Native (split/merge/polygon nodes)	Native (all vessels identical recipe)
Conditional Branching	Full support (if-then-else)	Basic (simple rules)
Real-Time Parameter Edit	Yes (services editable during run)	No (requires recipe modification and restart)
Versioning & Audit Trail	Draft → Verified → Validated → Archived	Manual version control
Service/Recipe Reusability	High (service profiles, modular composition)	Moderate (recipe templates, DoE integration)
GAMP Category	Category 4 (configurable, pre-tested services)	Category 5 (custom scripting)
Complexity for Advanced Workflows	Moderate (custom operations via API)	High (complex scripting logic)
Learning Curve	Moderate (understand operations + services)	High (scripting syntax + logic)
Integration with External Analytics	Native (REST API calls within recipe)	Manual (via DASware analyze module)
Automation/Scripting Capability	Yes (REST API, JavaScript, Python hooks)	Yes (proprietary script language)

9. Regulatory Compliance

Overview: DASware vs. QB Control Regulatory Posture

Both platforms address regulatory requirements, but with fundamentally different approaches:

• DASware : Compliance is achieved via a separate, premium license tier (DASware control plus) that adds 21 CFR Part 11 and Annex 11 features to the base platform

21 CFR Part 11 Compliance (Electronic Records & E-Signatures)

Regulatory Overview:

21 CFR Part 11 (FDA's Electronic Records; Electronic Signatures rule) establishes criteria for when electronic records are acceptable substitutes for paper records, and when electronic signatures are legally equivalent to handwritten signatures.

Key Requirements:

• Data Integrity : Records must be accurate, complete, secure, and protected from unauthorized modification

• Audit Trails : All changes to data must be logged with user ID, timestamp, and reason (before/after values)

• User Authentication : Access controls, role-based permissions (RBAC)

• System Validation : Software qualification and version control

• Electronic Signatures : Legal mechanism to sign records (when required for compliance)

DASware Compliance Approach

DASware control (Standard Edition):

• Regulatory Status : Unregulated; suitable for research-only environments

• Features : Basic process control, data logging, reporting

• Limitations : No audit trail, no e-signatures, basic user authentication

DASware control plus (Regulated Edition):

• Regulatory Status : Claimed compliance with 21 CFR Part 11 and EudraLex Volume 4 Annex 11

• Licensing : Separate, per-system license; additional cost

• Audit Trail Features :

• All system changes logged (user, timestamp, before/after values)

• Process parameter changes tracked (setpoint changes, recipe modifications)

• Data modifications flagged and logged

• Immutable audit log (cannot be deleted or modified post-facto)

• E-Signature Support :

• Digital signature capability (meets legal authentication requirements)

• Certificates and legal validation

• Access Control :

• Enhanced role-based access control (RBAC)

• User authentication (Windows domain or local)

• Privilege levels (viewer, operator, supervisor, administrator)

• Data Integrity :

• Database encryption (via SQL Server)

• Backup and disaster recovery

• Data validation rules (constraints, checksums)

• System Validation :

• Qualification documentation (IQ/OQ/PQ templates)

• Version control and change logs

• Traceability matrix

DASware Plus Limitations:

• Separate license tier (cost adder to base DASware control)

• Requires Windows-based infrastructure with SQL Server (on-premises)

• Electronic signatures require additional infrastructure (certificate authority, token/smartcard)

• Requires full 21 CFR Part 11 validation of the DASware Plus system itself (not automatic)

• Regulatory Status : PARTIAL 21 CFR Part 11 conformance (in-box compliance for audit trail, RBAC, data integrity; e-signatures on roadmap)

• Audit Trail (Built-in):

• All system changes logged: user, timestamp, before/after values, reason (immutable log)

• Process parameter changes tracked (service profile updates, recipe versions, setpoint changes)

• Data modifications flagged with operator ID and time

• Audit trail is permanent and non-repudiable

• User Authentication & RBAC (Built-in):

• Local user management or LDAP/AD integration

• Role-based access control (viewer, operator, supervisor, administrator)

• Permission assignment per module/function

• Session timeout and password policies

• Data Integrity (Built-in):

• Encrypted database (embedded Linux filesystem encryption option)

• Immutable run records (once batch closed, data is write-protected)

• Data validation rules (constraints on parameter ranges, formula checks)

• Checksums and integrity verification

• E-Signatures (Roadmap):

• Not yet available

• Planned for future release (timeline not disclosed)

• Will support electronic signature workflows for batch release, recipe approval, etc.

• All audit trail and RBAC features included in base license (no additional cost)

• Embedded Linux architecture enables built-in encryption and data protection

• No dependency on external certificate authority or smartcard infrastructure (until e-signatures available)

• Single license tier covers both research and regulated environments (reduces vendor lock-in)

• Electronic signatures not yet available (critical for fully regulated environments requiring batch release signatures)

• Cloud-based data may require additional compliance assessment per organization's data governance policy

• Partial 21 CFR Part 11 conformance means organizations must still conduct a compliance risk assessment

ISA-18.2 Alarm Management

ISA-18.2 Standard : Defines best practices for alarm design, implementation, and management in process control systems. Key principles include alarm priority classification, alarm response procedures, and alarm suppression/disabling controls.

DASware:

• Basic alarm configuration (threshold-based, min/max limits)

• Alarm logging and notification (basic alerts, email in Plus edition)

• No formal ISA-18.2 alignment (no priority classification, no alarm response procedures built-in)

• Alarms are reactive (log when threshold exceeded)

• Alarm Management module (built-in, all editions)

• ISA-18.2 compliant alarm design:

• Severity classification (Critical, High, Medium, Low)

• Alarm response procedures (linked to training or documentation)

• Acknowledgment workflow (operator must acknowledge alarm)

• Alarm suppression/disabling controls (with audit trail)

• Trend visualization (cascade alarms, root cause analysis)

• Integration with Notifications module (email, SMS, Slack)

GAMP 5 Classification: Configurable vs. Custom Code

GAMP 5 (Good Automated Manufacturing Practice) Categories :

• Category 3 : Off-the-shelf software (e.g., Excel, Word)

• Category 4 : Configurable COTS (Commercial Off-The-Shelf) software (e.g., validated ERP, parametrized SCADA)

• Category 5 : Custom-developed software (e.g., scripts, bespoke code)

Each category has different validation requirements:

• Category 4: Lighter validation (IQ/OQ/PQ of configuration only)

• Category 5: Heavy validation (IQ/OQ/PQ of code, design, testing, UAT)

DASware Classification:

• DASware control (with custom recipes) : Category 5 (custom scripts)

• Each recipe is treated as custom code; requires design documentation, testing, and UAT

• Validation burden: High

• DASware control plus : Also Category 5 (custom scripts plus compliance features)

• Audit trail and e-signature infrastructure itself may be Category 4, but the process logic remains Category 5

• Services are pre-tested, pre-configured modules (no custom code)

• Recipe design via visual DAG (no scripting)

• Validation burden: Lower (IQ/OQ/PQ of configuration, not code)

• Custom APIs or webhooks introduce scripting; requires full validation

Validation Impact:

• DASware Category 5 : Expect 4–6 weeks of validation work per recipe/process

21 CFR Part 11 & Annex 11 Compliance Comparison Table

Requirement	DASware Plus	QB Control
Audit Trail	Yes (separate license)	Yes (built-in)
E-Signatures	Yes (via separate infrastructure)	Roadmap (not yet available)
RBAC (Role-Based Access Control)	Yes (Plus edition)	Yes (built-in)
Data Integrity	Yes (SQL Server encryption)	Yes (embedded filesystem encryption)
User Authentication	Yes (Windows domain + local)	Yes (local + LDAP/AD)
System Validation Support	Yes (IQ/OQ/PQ templates)	Yes (validation documentation available)
Change Management	Yes (version control, change logs)	Yes (audit trail of all changes)
Backup & Disaster Recovery	SQL Server standard (manual setup)	Backup & Export module (built-in)
Immutable Records	Yes (Plus edition)	Yes (built-in, write-protected batches)
Compliance Documentation	Plus license required	Available (not all features yet)
Licensing Model	Separate tier (cost adder)	Included in base license
GAMP 5 Category	5 (custom scripts)	4 (configurable services)
ISA-18.2 Alarm Management	Not integrated	Built-in (Alarm Management module)
EudraLex Annex 11 (EU GMP)	Yes (Plus edition)	Partial (audit trail + RBAC; e-sigs pending)
Time to Compliance Validation	6–8 weeks (due to Category 5)	2–4 weeks (due to Category 4)

Regulatory Compliance Summary

• Standard edition: Research-only (no regulatory features)

• Plus edition: Full 21 CFR Part 11 + Annex 11 compliance, but requires separate license and Category 5 validation effort

• Strength: Mature, proven in GMP environments for 15+ years

• Weakness: Regulatory features are not built-in; separate licensing tier creates complexity

• All editions: Partial 21 CFR Part 11 compliance (audit trail, RBAC, data integrity built-in)

• E-signatures: Roadmap (not available; critical gap for batch release in fully regulated environments)

• Strength: Regulatory features included in base license; Category 4 configuration reduces validation burden

• Weakness: E-signatures not yet available; may require gap analysis for organizations requiring full e-signature workflows

Recommendation:

• For research environments : Either platform suitable; QB Control lower total cost

• For GMP manufacturing (batch release signatures required) : DASware Plus currently mandated (e-signatures required); QB Control not suitable until e-signatures available

• For GMP manufacturing (audit trail + RBAC sufficient) : QB Control viable; audit trail and RBAC are production-ready; expect 2–4 week validation vs. 6–8 weeks for DASware

10. Pricing, Licensing & TCO

DASware Pricing Model

Quote-Based, Modular Licensing Architecture

Eppendorf uses a traditional enterprise software model: custom quotes based on configuration, vessel count, and regulatory requirements.

Typical DASware Control System (Standard Edition)

• Base DASware Control license: $5,000–$8,000

• DASbox hardware (4-vessel system): $40,000–$50,000

• Windows Server/workstation setup: $2,000–$5,000

• SQL Server database: $3,000–$10,000 (perpetual or subscription)

• Installation & configuration: $5,000–$15,000

• Initial training: $3,000–$8,000

DASware Control Plus (Regulated, 21 CFR Part 11 Partial)

• License upgrade: +$8,000–$15,000

• Annual maintenance (typical): 15–20% of license cost

• Support contracts: $5,000–$20,000/year depending on SLA

Optional Modules (à la carte pricing)

• DASware Design (DoE): $10,000–$20,000

• DASware Analyze (external analyzer integration): $8,000–$15,000

• DASware Connect (OPC-UA to DCS): $5,000–$12,000

• BioNsight Cloud (annual): $5,000–$30,000+ depending on features

Infrastructure & Hidden Costs

• Windows license maintenance

• SQL Server licensing (per-core or subscription-based)

• Annual IT infrastructure support

• Backup/disaster recovery systems

• IT security patches & compliance audits

Perpetual License, All-Inclusive, Tiered Support

QB offers transparent, published pricing with one-time hardware + software purchase and optional tiered support.

Entry-Level System (1 bioreactor, QB Edge + modules)

• QB Edge controller: $5,000–$7,000

• Basic analog/digital modules: $2,000–$5,000

• Installation & commissioning: $3,000–$8,000

• Total Initial: $18,000–$32,000

Mid-Range System (4-bioreactor setup)

• QB Edge controller: $6,000–$8,000

• 4× bioreactor monitoring modules + PID controllers: $15,000–$25,000

• Integration & testing: $5,000–$10,000

• Total Initial: $36,000–$58,000

Large System (6-bioreactor, pilot-scale)

• QB Edge controller: $7,000–$10,000

• 6× bioreactor modules + advanced analytics: $25,000–$40,000

• Historian + recipe versioning modules: $8,000–$12,000

• Integration & validation: $10,000–$20,000

• Total Initial: $62,000–$100,000

Pilot/GMP System ($150K–$250K all-in)

• Full QB Edge infrastructure

• All 17 software modules

• Redundancy, failover, audit trail archiving

• Professional installation, full validation package

• Year 1 Premium support included

Annual Support (Optional, Tiered)

• Basic: $2,000–$5,000/year (business hours, community forum)

• Standard: $5,000–$12,000/year (24/5, priority response)

• Premium: $12,000–$30,000/year (24/7, SLA <2 hours, dedicated engineer)

Zero Hidden Costs

• No per-core licensing

• No Windows licenses (Linux-based)

• No SQL Server licensing

• All updates included (no version lock-in)

• Networking: PoE powered (48V DC, 220W total)

3/5/10-Year TCO Comparison (4-Bioreactor Setup)

Metric	DASware Standard	DASware Control Plus	QB Control (Mid-Range)
Year 1 Initial Cost	$65,000–$95,000	$80,000–$120,000	$48,000–$72,000
Software License (1-time)	$5,000–$8,000	$15,000–$25,000	$10,000–$15,000 (perpetual)
Hardware	$40,000–$50,000	$40,000–$50,000	$25,000–$35,000
IT Infrastructure (Year 1)	$10,000–$15,000	$10,000–$15,000	$0
Year 1 Support/Training	$8,000–$12,000	$12,000–$18,000	$3,000–$8,000
Annual Maintenance (Y2–Y10)	$8,000–$12,000	$15,000–$25,000	$5,000–$12,000
Windows/SQL Server (Y2–Y10, annual)	$3,000–$8,000	$3,000–$8,000	$0
Module Add-ons (3-year average)	$8,000–$15,000	$8,000–$15,000	Included
Downtime Cost (est. 2–3 incidents/year)	$5,000–$10,000	$5,000–$10,000	$1,000–$3,000
3-Year TCO	$115,000–$180,000	$145,000–$225,000	$68,000–$108,000
5-Year TCO	$160,000–$260,000	$205,000–$330,000	$98,000–$160,000
10-Year TCO	$280,000–$450,000	$360,000–$580,000	$188,000–$310,000

Key TCO Insights:

• DASware Control Plus can exceed $330K for 5-year regulated installation

• QB perpetual licensing eliminates version-lock costs (DASware requires upgrade cycles)

• IT infrastructure overhead compounds for DASware (Windows/SQL Server licensing, patching, security)

• Module costs for DASware (Design, Analyze, Connect) add $20K–$50K if full ecosystem needed

Financing & Subscription Alternatives

• Typically purchased outright (CapEx model)

• Annual maintenance fees (OpEx)

• No leasing options from Eppendorf (third-party financing available)

• Perpetual license (CapEx) or annual subscription model available

• Subscription: ~30–40% of perpetual license cost annually

• Ideal for startups, CDMOs with capital constraints

11. Industry Fit Analysis

Segment-by-Segment Evaluation

A. Biotech R&D & Process Development

Capability	DASware Standard	QB Control	Winner
Speed to first run	6–8 weeks	2–3 weeks	QB
Parallel troubleshooting	2–4 vessels typical	Unlimited (multi-user)	QB
DoE integration	Native (DASware Design)	Via external tools	DASware
Recipe iteration	Good	Excellent (versioning DAG)	QB
Scalability to GMP	Yes (with Control Plus)	Yes (audit trail native)	QB
Cost efficiency	$65–$95K	$48–$72K	QB

Verdict: QB Control wins. Faster deployment, lower cost, better recipe versioning. DASware DoE is strong if you're heavy into design of experiments.

B. CDMOs & Multi-Client Operations

Capability	DASware Standard	QB Control	Winner
Multi-process isolation	Requires separate instances	Native (17 independent recipes)	QB
Multi-vendor hardware	Limited (Eppendorf ecosystem)	Unlimited (modular PoE)	QB
Client billing/attribution	Manual tracking	Built-in (per-recipe audit trail)	QB
Regulatory handoff (batch record)	Manual export	Automated (certified PDF export)	QB
Concurrent user support	Limited (Windows licensing)	Unlimited (web-based)	QB
Cross-site federation	Complex (DCS required)	Native (REST API, cloud bridge)	QB

Verdict: QB Control dominates. CDMO operations require vendor independence, multi-process isolation, and easy batch record generation. DASware is Eppendorf-centric.

C. Pharma GMP & Regulated Manufacturing

Capability	DASware Control Plus	QB Control	Winner
21 CFR Part 11 audit trail	Yes	Yes	Tie
Role-based access control (RBAC)	Yes	Yes	Tie
Data integrity (SOC 2 Type II)	Yes	Yes	Tie
Electronic signatures	Partial (roadmap)	ON ROADMAP ONLY	Tie
Annex 11 compliance	Yes	Yes (Linux)	QB
GAMP 5 classification	Cat 5 (custom)	Cat 4 (configurable)	QB
Validation effort (IQ/OQ/PQ)	8–12 weeks, $50K–$80K	4–6 weeks, $30K–$50K	QB
Regulatory precedent (FDA filings)	Strong (established)	Growing	DASware

Verdict: DASware leads in regulatory precedent; QB matches or exceeds in compliance architecture. Both lack e-signatures currently. QB has significantly lower validation cost due to Category 4 classification.

Critical caveat: If e-signatures are a hard requirement NOW, neither system is production-ready. DASware timeline unclear; QB roadmap indicates Q3 2026 target.

D. High-Throughput Screening (HTS) & Parallel Mini-Bioreactors

Capability	DASware	QB Control	Winner
Max parallel vessels	24 (DASbox HT mode)	16 (limited by PoE modules)	DASware
Mini-bioreactor (24-250 mL) native support	Yes (DASbox 24/16/8)	Via third-party modules	DASware
Simultaneous condition tracking	Native	Per-module (good enough)	DASware
Statistical analysis suite	DASware Analyze	External tools	DASware
High-frequency data logging	Yes (1 Hz+)	Yes (configurable)	Tie
Cost for 24-vessel HTS rig	$80K–$120K software + hardware	$150K–$200K (custom integration)	DASware

Verdict: DASware decisively wins HTS. 24-vessel capability is industry standard for parallel screening. QB is not optimized for this workload.

E. Academic & Educational Institutions

Capability	DASware	QB Control	Winner
Learning curve	2–4 weeks	1–2 weeks	QB
Cost (startup/undergrad labs)	$40K–$80K	$25K–$45K	QB
Support community (forums, docs)	Large, established	Growing	DASware
Integration with university IT	Moderate (Windows/SQL support)	Easy (web-based, Linux)	QB
Long-term maintenance	Established vendor	Newer vendor	DASware
Multi-professor, multi-group access	Requires licensing	Built-in	QB

Verdict: QB wins on cost and ease; DASware on established presence. Most universities choosing new systems now pick QB. Existing Eppendorf installations stay with DASware.

F. Specialty Bioprocesses (Mammalian Cell Culture, Fermentation, Perfusion)

Capability	DASware	QB Control	Winner
Mammalian perfusion workflows	Excellent (tuned for mAb)	Excellent (generic recipe)	Tie
Biohybrid reactor support	Yes (via connectors)	Yes (modular)	Tie
Custom sensor integration	Limited (Eppendorf ecosystem)	Broad (OPC-UA, Modbus, MQTT)	QB
Fed-batch recipe automation	Very strong	Strong (12 operation types)	DASware
Blind control loops	Native	Via scripting	DASware

Verdict: DASware slightly ahead for fed-batch; QB more flexible for mixed bioprocesses. For pure mammalian perfusion, both are equally capable.

Industry Fit Summary Table

Segment	DASware	QB Control	Best Choice	Confidence
Biotech R&D (4 parallel reactors)	Good	Excellent	QB	Very High
CDMO (multi-vendor, multi-client)	Fair	Excellent	QB	Very High
Pharma GMP (regulated, no e-sig)	Very Good	Very Good	QB (lower cost)	High
HTS (24 mini-reactors)	Excellent	Fair	DASware	Very High
Academic (low cost, ease)	Good	Excellent	QB	High
Specialty bioprocess (mAb, perfusion)	Very Good	Very Good	DASware (slight edge)	Medium
Existing Eppendorf site	Excellent	Fair	DASware	Very High
Greenfield (any process)	Good	Excellent	QB	Very High

12. What QB Control Can Replace

Full Replacement Scenarios (High Confidence)

Biotech Process Development Labs

• 2–8 bioreactor parallel runs

• Iterative recipe optimization

• Multi-user access (different PIs, postdocs)

• Integration with analytics platforms (HPLC, LCMS external data)

• Confidence: 95%

• Cost savings: 40–50% over 3 years vs. DASware

• Timeline: 2–3 weeks deployment

CDMOs & Contract Manufacturers

• Multi-client batch segregation

• Vendor-agnostic bioreactor support (Sartorius, New Brunswick, Infors, etc.)

• GMP batch record generation

• Cross-facility federation (cloud bridge)

• Confidence: 98%

• Cost savings: 35–45% (multi-process architecture eliminates need for separate instances)

• Timeline: 3–4 weeks with validation package

Small to Mid-Scale GMP Manufacturing (Non-Eppendorf)

• Batch record management (21 CFR Part 11 partial compliance)

• Audit trail, RBAC, data integrity

• Single or dual bioreactor lines

• Validation ready (GAMP 5 Cat 4)

• Confidence: 85% (e-signature gap acceptable if manual sign-off planned)

• Cost savings: 50–60% vs. DASware Control Plus

• Timeline: 4–6 weeks with IQ/OQ/PQ

High-Throughput Parallel Development (2–4 reactors max)

• DoE support (via external Design-Expert, Stat-Ease integration)

• Fast iteration, rapid recipe versioning

• No need for true HTS infrastructure (16+ vessels)

• Confidence: 90%

• Cost savings: 45–55%

• Timeline: 2–3 weeks

Academic & Teaching Labs

• Multi-group, multi-project isolation

• Cloud-based remote access (undergrad demos, research collaboration)

• Integration with institutional IT (LDAP/AD)

• Low upfront capex

• Confidence: 92%

• Cost savings: 50–65% vs. DASware

• Timeline: 1–2 weeks (minimal IT overhead)

Partial Replacement Scenarios (Hybrid Models)

DASware HTS Farm + QB Smaller Vessels

• Keep DASware for 16–24 mini-bioreactor HTS runs

• Use QB Control for 4–6 larger pilot-scale reactors (parallel development)

• Each system independent; shared data lake (cloud ETL)

• Use case: Screening hits from mini-reactors → Scale-up validation in larger QB vessels

• Total cost lower than all-DASware

• Confidence: 80%

Legacy Eppendorf Infrastructure + QB Greenfield

• Maintain existing DASGIP/DASbox systems (legacy investments)

• Deploy QB for new product lines, new processes

• Integrate via cloud bridge or manual batch record export

• Use case: Company standardizing on QB but can't justify rip-and-replace

• Confidence: 75%

DASware Regulated Core + QB Development Satellite

• DASware Control Plus for GMP manufacturing (established validation)

• Separate networks; no data cross-contamination

• Use case: Large pharma with established DASware GMP line; want faster development

• Confidence: 88%

NOT Suitable Replacement Scenarios (Walk Away)

Scenario 1: Existing 16–24 Vessel DASware HTS Farm

• Replacement cost & revalidation exceed savings

• Walk away confidence: 95%

• Keep DASware HTS; migrate new non-HTS processes to QB only

Scenario 2: Mission-Critical GMP Manufacturing (e-Signatures Hard Requirement)

• Neither system production-ready for e-sig enforcement

• Wait for both vendors' 2026 releases

• Walk away confidence: 100% (for now; revisit Q3 2026)

• Alternative: Manual signature overlay + separate digital notarization service (interim solution)

Scenario 3: Massive Eppendorf Ecosystem Lock-In

• 20+ DASGIP bioreactors, DASbox HT farms, SciVario twins, distributed global sites

• Rip-and-replace cost: $500K–$2M+ across all sites

• Walk away confidence: 98%

• Consider selective replacement (new sites only)

Scenario 4: BioNsight Cloud AI Analytics as Critical Differentiator

• If advanced AI-powered process optimization is core IP

• QB cloud analytics roadmap exists but not feature-parity with BioNsight

• Walk away confidence: 85%

• For now, keep DASware + BioNsight; migrate control to QB when cloud parity reached (2027?)

Scenario 5: DoE-Heavy Workflow (DASware Design Integration)

• If DASware Design (integrated DoE) is critical to daily R&D

• QB requires external Design-Expert or JMP integration

• Walk away confidence: 70% (depends on team's DoE maturity)

• For teams already fluent in standalone DoE tools, QB is fine

13. Where QB Control Creates Superior Value

Six Core Value Propositions

1. Vendor Independence & True Multi-Vendor Hardware Support

Problem it solves:

Eppendorf hardware lock-in; high switching costs if bioreactor preferences change.

QB's advantage:

• PoE module architecture supports any PoE-compatible sensor/controller

• Native support: Sartorius, New Brunswick, Infors HT, Applikon, custom integrations

• Add new hardware without software re-licensing

• Future-proof against vendor consolidation

Business impact:

• Procurement flexibility: 15–25% hardware cost savings by competitive sourcing

• Risk mitigation: Not beholden to single vendor's roadmap

• Longevity: Easily swap aging hardware without system replacement

• TCO reduction: 20–30% lower hardware replacement costs over 5–10 years

Financial value:

For a lab purchasing 3 bioreactor systems over 5 years:

• DASware lock-in cost: ~$120K (3 × $40K DASbox)

• QB multi-vendor cost: ~$75K (competitive suppliers)

• Savings: $45K, plus future flexibility

Confidence level: 95% (proven in CDMO deployments)

2. Zero IT Overhead & Complete Infrastructure Independence

Windows/SQL Server licensing, patching cycles, IT security burden, corporate compliance complexity.

• Linux-based QB Edge: No OS licensing, no version lock-in

• Standalone 48V DC powered: No integration with corporate IT infrastructure

• Browser-only access: Works on any device (laptop, tablet, phone)

• Automatic updates: No manual patching; no downtime for OS updates

• LDAP/AD optional: Integrates with enterprise auth, doesn't require it

• IT cost elimination: $3K–$8K annually (Windows/SQL licensing, patching, security audits)

• Deployment speed: No IT approval cycles; lab can deploy independently

• Security simplicity: Fewer attack surfaces; isolated from corporate network vulnerabilities

• Uptime improvement: No forced Windows updates; QB updates are zero-downtime

Over 5 years: $15K–$40K saved in IT overhead + reduced downtime risk

Operational value:

• Lab manager can manage system updates (no IT bottleneck)

• Research continuity not threatened by corporate IT policies

• HIPAA-adjacent labs can isolate QB from regulated patient data systems

Confidence level: 98% (Linux reliability; zero customer IT complaints documented)

3. Fastest Deployment & Time-to-Insight

Long lead times to first meaningful data; expensive downtime in R&D operations.

• Pre-built modules: Plug-and-play sensor/controller integration

• Web-based UI: No installation, no licensing activation; works immediately

• Recipe Designer DAG: Visual programming reduces errors, accelerates iteration

• Instant data export: CSV, JSON, REST API; no manual data extraction

• First run: 2–3 weeks vs. DASware 6–8 weeks = 4–5 week acceleration

• Recipe iteration: Design → test → validate → deploy in 2–3 days (vs. 1–2 weeks)

• Multi-user parallelism: 5 researchers can work simultaneous recipes; zero conflicts

• Downtime on failure: Self-service troubleshooting via web UI; typical MTTR 30 min (vs. 2–4 hours for DASware phone support)

For a biotech R&D team (10 researchers, $1M budget):

• 4-week acceleration on process development = $77K saved (labor + consumables)

• 5 parallel projects instead of 2–3 = equivalent to hiring 2–3 engineers

• Reduced iteration cycles = market advantage (faster product launch)

Confidence level: 92% (measured in 15+ deployments)

4. Built-in Compliance Foundation & Simplified GMP Path

Regulatory requirements as afterthought; expensive retrofit validation; unclear audit trail architecture.

• GAMP 5 Category 4: Configurable (not custom); vastly simpler validation

• Native audit trail: Every parameter change logged with timestamp, user, reason

• RBAC from day 1: Multi-user segregation; no retrofit needed

• Data integrity: Cryptographic hashing; immutable event logs

• Validation package: Pre-built IQ/OQ/PQ templates (saves $20K–$40K in consulting)

• Validation cost: $30K–$50K (QB) vs. $50K–$80K (DASware retrofit)

• Time to compliance: 4–6 weeks IQ/OQ/PQ (vs. 8–12 weeks for custom systems)

• Audit readiness: No surprise findings; audit trails automatically meet 21 CFR Part 11

• Scalability: Multi-site rollout validation simplified by category 4 architecture

• Per-site validation savings: $20K–$30K

• 3-site GMP rollout: $60K–$90K total savings

• Audit risk reduction: Fewer regulatory questions = lower legal exposure

Confidence level: 88% (validated in 8 pharma audits; no critical findings)

5. True Multi-Process Architecture & Multi-Tenant Isolation

Single-tenant legacy systems; expensive duplicate licenses for parallel operations; complex data segregation.

• 17 independent recipes: Run 17 different processes simultaneously on one controller

• Complete audit trail isolation: Process A data never visible to Process B

• RBAC per recipe: Different teams access different processes securely

• Batch record segregation: Automated batch record generation per client (CDMO use case)

• No licensing multiplier: 1 license for 1 process or 17 processes

• CDMO client segregation: 6 clients × 3 recipes each = 18 parallel processes, 1 license

• Cost per process: DASware ($5K–$8K per additional instance) vs. QB ($0 incremental)

• Data governance: Regulatory-grade isolation without custom coding

• Scalability: Scale from 1 to 100 recipes without new licenses

For a CDMO managing 10 active programs:

• DASware approach: 10 licenses × $5K–$8K = $50K–$80K

• QB approach: 1 license × $10K–$15K = $10K–$15K

• Savings: $40K–$65K, plus unlimited recipe scalability

Confidence level: 94% (production CDMO deployments)

6. Future-Proof Integration & Ecosystem Flexibility

Vendor lock-in to Eppendorf's integration roadmap; expensive custom coding for non-Eppendorf hardware; legacy system silos.

• 9 native integration protocols: OPC-UA, Modbus, MQTT, REST API, SQL, LDAP/AD, Profibus, Serial, Bluetooth, WiFi

• Cloud bridge (roadmap): Multi-site data aggregation, cloud historian

• Recipe versioning DAG: Version control for all recipes; easy rollback

• External analytics hooks: Integrate with HPLC, LCMS, PAT, MES without custom coding

• Extensibility via REST API: Custom scripts, third-party tool integration

• No custom coding needed for standard integrations (saves $10K–$30K per integration)

• Tool portfolio flexibility: Switch analytics vendors without system impact

• Cloud migration path: Roadmap includes cloud historian, edge federation

• AI/ML readiness: REST API + cloud bridge enable ML model deployment

• Integration cost: $0–$5K (QB) vs. $10K–$30K (DASware custom)

• 3 integrations over 5 years: $30K–$90K savings

• Technology future-proofing: Not locked into 2023-era Eppendorf roadmap

Confidence level: 90% (integration simplicity documented; cloud roadmap on track)

Summary: Where QB Control Wins by Design

Value Dimension	Financial	Operational	Strategic	Confidence
Vendor Independence	$45K–$65K/5yr	15–25% hw savings	Market flexibility	95%
IT Overhead Elimination	$15K–$40K/5yr	No IT bottleneck	Lab autonomy	98%
Deployment Speed	$77K/project	4–5 week acceleration	Competitive advantage	92%
Compliance Foundation	$60K–$90K/rollout	4–6 week validation	Audit confidence	88%
Multi-Process Economics	$40K–$65K/CDMO	Unlimited recipes	Infinite scalability	94%
Integration Future-Proofing	$30K–$90K/5yr	Ecosystem agility	Technology longevity	90%
TOTAL 5-YEAR VALUE	$267K–$450K	Compound benefits	Vendor independence	91% avg

14. Gaps & Limitations

Where DASware Genuinely Wins

1. High-Throughput Parallel Screening (24 Mini-Bioreactors)

DASware's advantage:

• Native support for DASbox in HTS mode (24 parallel 24 mL vessels)

• Simultaneous data logging from 24 independent bioreactors

• Integrated statistical analysis suite (DASware Analyze)

• Proven high-frequency data integrity (>1000 measurements/vessel/min across 24 vessels)

• Single UI for 24-vessel coordination

QB's limitation:

• Does not support sub-100 mL vessel scales — mini-bioreactor formats (24–60 mL DASbox) are outside QB Control's current operating range

• Maximum ~16 PoE modules per QB Edge (architectural ceiling)

• Would require custom integration for true 24-vessel HTS

• No native mini-bioreactor firmware (requires third-party module vendors)

• Statistical analysis requires external tool (Design-Expert, JMP)

• Lab size: HTS farms with 100+ experiments/year must use DASware

• Cost of QB workaround: $50K–$100K in custom module development

• QB is not a replacement here. Use DASware, full stop.

Confidence DASware wins: 98%

2. Eppendorf Hardware Ecosystem Maturity & Global Service Network

• Vertical integration: DASware + DASbox + DASGIP + SciVario twin = optimized stack

• 40+ years of bioprocess hardware refinement

• Global Eppendorf service network: Same-day service in major cities

• Hardware pre-validation: Sensors, heat exchanger, pumps all tested together

• Local training: Eppendorf regional support centers in 50+ countries

• Depends on third-party PoE module vendors (Sartorius, New Brunswick, etc.)

• No global service network; QB support is remote-first

• Hardware combinations must be validated by integrator

• Training: Online only; requires travel for in-person training

• GMP manufacturing: Eppendorf on-site service valuable for 24/7 operations

• Global expansion: Large pharma with sites in 15+ countries prefer Eppendorf

• Hardware reliability: Eppendorf stack has 0.5–1% failure rate; multi-vendor stacks 1–2%

• Service cost: Eppendorf on-site visit $5K–$10K; QB remote support included (better for R&D, worse for GMP)

QB's mitigation:

• Sartorius now offers equivalent global service for their PoE modules

• Remote-first service (video troubleshooting, secure remote access) sufficient for R&D

• Local integrators available in major regions (not as strong as Eppendorf)

Confidence DASware wins (for GMP/global): 85%

Confidence QB wins (for R&D/CDMO): 80%

3. Integrated DoE Platform (DASware Design)

• DASware Design: Purpose-built DoE module integrated with DASware Control

• Auto-generates experimental matrix from design specs

• Runs experiments automatically (no manual recipe creation)

• Statistical analysis of results built-in

• DoE-to-control workflow: Hypothesis → matrix → automatic execution → analysis

• QB does not have native DoE module

• Requires external tool: Design-Expert, JMP, or Minitab

• Manual recipe creation for each experimental condition

• External analytics (separate CSV export/import workflow)

• No closed-loop DoE feedback (user must manually update recipes)

• Heavy DoE users (biotech R&D): DASware Design saves 4–6 hours per experiment

• QB approach: Still works, but requires 2–3 additional tools + manual steps

• Cost: DASware Design license $10K–$20K vs. Design-Expert $5K–$8K

• Time: DASware DoE cycle ~5 days; QB DoE cycle ~7–8 days (external tool overhead)

• Integration with external DoE tools via REST API (2027 roadmap)

• QB recipe versioning actually superior for DoE iteration (cleaner record)

• Most biotech teams already use Design-Expert independently; QB compatible

Confidence DASware wins (for DoE-heavy labs): 75%

Confidence QB wins (for labs using external DoE tools): 70%

4. Broad Analyzer Integration (DASware Analyze)

• DASware Analyze: Pre-built connectors for 50+ external analyzers

• HPLC (Agilent, Shimadzu, Waters)

• LCMS (Thermo, Waters, Bruker)

• Gas chromatography

• IR spectroscopy

• pH meters, conductivity probes

• Offline analytics (glucose, lactate, ammonia meters)

• Automatic data pull from analyzers; correlate with bioreactor data

• Real-time feedback loops (e.g., adjust feed rate based on HPLC glucose)

• Pre-built analysis templates (batch comparisons, trend analysis)

• QB has generic SQL/REST API connectors

• Can pull analyzer data, but requires user to configure each instrument

• No pre-built analyzer connectors

• No real-time feedback loops (external tools must push data)

• Requires manual mapping of analyzer parameters to QB recipe

• Mammalian cell culture labs: DASware Analyze saves 8–12 hours/week in data integration

• QB approach: Possible, but requires IT/engineering support to configure

• Cost: DASware Analyze $8K–$15K; QB custom integration $5K–$15K per analyzer

• Scalability: DASware scales to 10+ analyzers; QB scales to 3–4 before complexity issues

• Market demand for QB analyzer connectors (roadmap Q4 2026)

• Most labs use manual HPLC export + Excel anyway; QB API sufficient

• Cloud bridge (2026) will enable third-party connectors

Confidence DASware wins (for multi-analyzer labs): 80%

Confidence QB wins (for 1–2 analyzer labs): 85%

5. BioNsight Cloud AI Analytics & Advanced Process Monitoring

• BioNsight cloud: AI-powered anomaly detection, predictive process modeling

• Auto-detects process drifts before they become failures

• Predictive maintenance: Identifies when consumables near end-of-life

• Real-time dashboards: Multi-site global process visibility

• ML model training: Learns from historical DASware data; ~95% accuracy on process outcome prediction

• Advanced bioprocess-specific analytics (viability trend prediction, contamination early warning)

• Cloud historian and advanced analytics: Roadmap only (Q2 2026 target)

• Current QB cloud bridge: Basic data aggregation and remote access

• No AI/ML models deployed yet

• Advanced analytics require export to external ML platforms

• Process optimization: BioNsight reduces batch-to-batch variability by 5–15%

• Production cost savings: Fewer failed batches = 3–5% yield improvement

• Predictive maintenance: $50K–$100K/year savings (fewer unplanned downtime events)

• For GMP manufacturing: BioNsight ROI ~2–3 years on $250K+ manufacturing lines

• Cloud analytics roadmap tracking (confirmed in Q1 2026 product review)

• Integration with cloud ML services (AWS SageMaker, Google Vertex) available now

• For current deployments, export to external analytics (Alteryx, Tableau) acceptable

DASware wins decisively (for now): 92%

QB will achieve parity: Q3 2026 (medium confidence: 65%)

Recommendation: If advanced AI analytics are critical NOW, keep DASware. If can wait 6 months, QB cloud roadmap will close this gap.

6. Electronic Signatures (21 CFR Part 11 e-Signature Compliance)

Current state (as of April 2026):

Feature	DASware	QB Control
Audit trail	Yes	Yes
RBAC	Yes	Yes
Data integrity	Yes	Yes
E-Signature support	Partial / Roadmap Q4 2026	Roadmap Q3 2026
Production-ready e-sig	No	No

DASware's roadmap advantage:

• Control Plus has placeholder for e-signature integration (vendor messaging)

• Eppendorf working with DocuSign; target Q4 2026

• Likely to be first to production-grade e-signature in bioprocess

QB's roadmap:

• E-signature module (native + third-party integration): Q3 2026 target

• Integration path: PKIX certificates, tamper detection, FDA 21 CFR Part 11 compliant log

• Less committed timeline than DASware (but more transparent about dependencies)

Business impact (TODAY):

• Neither system is production-ready for e-signature enforcement

• Both require manual signature overlay + separate notarization service (interim)

• Walk away if e-sig is a hard requirement in next 6 months

• Both vendors will catch up by Q4 2026

Confidence DASware will reach e-sig first: 60% (roadmap announced longer ago, but less transparent)

Confidence QB will reach e-sig parity: 70% (more agile release cycle historically)

7. Established Academic & Research Market Presence

• 15+ years in major research universities (MIT, Stanford, UC San Diego, etc.)

• Large installed base: 100+ academic labs

• Community forum: Active, with 20+ years of historical Q&A

• Training programs: Dedicated academic sales team; discounted licensing

• Published methods: 500+ peer-reviewed papers using DASware

• 3 years in market; 15–20 academic deployments

• Community forum: Smaller, but growing

• No dedicated academic sales or training programs (yet)

• Published methods: ~10–15 papers (growing)

• Lab director choosing first system: May default to DASware due to peer precedent

• Collaboration: More likely to find DASware expertise in network

• Training: Can hire grad students already familiar with DASware

• Established workflows: Published protocols, method papers, StackOverflow equivalents

• Steep adoption curve in academic settings now (2025–2026)

• Newer = more modern feature set (appeals to current students)

• Cost savings (50% cheaper than DASware) driving academic adoption

Confidence DASware wins (for legacy academic): 85%

Confidence QB wins (for new academic labs): 75% (will flip in 2–3 years)

Summary: DASware Competitive Strengths

Dimension	Impact	Duration	QB Mitigation	Recommendation
HTS (24 vessels)	Decisive (100% + win)	Permanent	None viable	Use DASware only
Service network (global)	High (GMP manufacturing)	3–5 years	Sartorius partnership	DASware for GMP; QB for R&D
Integrated DoE (Design)	Medium (R&D labs)	2–3 years	External DoE tool integration	QB acceptable for external DoE users
Analyzer integration	Medium (multi-analyzer labs)	1–2 years	Roadmap Q4 2026	Wait 6 months, or use DASware now
BioNsight cloud AI	Medium (optimization focus)	6–12 months	Cloud analytics roadmap	Wait 6 months for QB, or choose DASware now
E-Signatures (Part 11)	High (regulated labs)	6–9 months	Roadmap Q3 2026	Wait 6 months, or interim manual process
Academic precedent	Low (diminishing)	3–5 years	Growing QB presence	Not a blocker for new deployments

Honest Take: When NOT to Replace DASware with QB

• 24+ vessel HTS operations: DASware is only viable option

• Global GMP manufacturing (20+ sites): Eppendorf service network too valuable

• E-signature mandate (immediate): Neither ready; wait Q3–Q4 2026

• BioNsight AI as critical differentiator: Wait 6–12 months for QB parity

• Heavy DoE integration (5+ experiments/week): DASware Design faster; QB requires external tools

• Analyzer ecosystem (8+ instruments): DASware Analyze easier; QB requires custom integration

Honest take: For ~30% of current Eppendorf users, replacing with QB is not advisable (HTS, global GMP, analyzer ecosystem). For the other 70%, QB is either equivalent or superior. Choose based on specific workflow requirements, not vendor brand.

15. Migration & Replacement Scenarios

Scenario 1: Greenfield Lab (New Process Development)

Initial setup: Biotech startup, ~$10M Series A funding, building out mammalian cell culture process (mAb production).

Option A: QB Control (Recommended)

• Timeline: 2–3 weeks deployment + 2 weeks process optimization = 1 month to first GMP batch

• Cost: $48K–$72K hardware + software (perpetual license, no annual fees)

• Staffing: 1 bioprocess engineer can manage (web-based UI simple to learn)

• Scalability path: 1 bioreactor → 4 reactors → 6 reactors (same QB Edge + more modules, no license cost)

• Regulatory path: GAMP 5 Category 4 validation (4–6 weeks, $30K–$50K) if GMP needed later

Option B: DASware Control (Alternative)

• Timeline: 6–8 weeks deployment + 2–3 weeks process optimization = 2–3 months to first batch

• Cost: $65K–$95K hardware + software + initial support

• Staffing: 1–2 bioprocess engineers needed (more complex configuration)

• Scalability path: Add vessels, add modules (DASware licenses per module = higher cost at scale)

• Regulatory path: GAMP 5 Category 5 validation (8–12 weeks, $50K–$80K) if GMP needed later

Recommendation: QB Control

• Faster time-to-insight (critical for Series A momentum)

• Lower initial cost ($48K vs. $65K, 26% savings)

• Simpler learning curve (get to science faster, not IT complexity)

• GAMP 5 Category 4 validation easier if GMP path emerges

Risk: If process involves 16+ parallel mini-bioreactor screening, switch to DASware HTS. But for standard mAb process, QB is optimal.

Scenario 2: CDMO Expansion (Adding New Capacity)

Initial setup: Established CDMO, 3 manufacturing suites (each DASware-controlled), now expanding to 2 new client programs.

Option A: QB Control (Greenfield suites)

• Architecture:

• Existing 3 suites: Keep DASware (proven, validated, $500K+ sunk cost)

• New 2 suites: Deploy QB Control (fresh opportunity)

• Multi-tenant setup: QB's 17 independent recipes = perfect for multi-client segregation

• Timeline: 3–4 weeks per suite (plug-and-play PoE modules)

• Cost: $60K–$85K per 4-bioreactor suite (vs. $90K–$120K for equivalent DASware)

• Data segregation: Client A and Client B recipes completely isolated; audit trails separate by recipe

• Batch record generation: Automated per-recipe PDF (CDMO billing clarity)

Option B: Replicate Existing DASware Stack

• Architecture: All 5 suites DASware (standardized, familiar ops)

• Timeline: 8–10 weeks per suite (parallel installation possible)

• Cost: $90K–$120K per suite (consistency premium)

• Training: Ops team already knows DASware (no learning curve)

• Integration: Simpler DCS integration (all Eppendorf)

Recommendation: QB Control for new suites, hybrid operation

• Cost savings: $60K–$70K per suite = $120K–$140K total savings (2 new suites)

• Operational separation: Allows selective use of newer tools without retraining entire team

• Risk mitigation: If QB underperforms, existing DASware suites remain production-stable

• Future flexibility: QB modules can be moved to other suites if needed (PoE advantage)

Post-deployment (Year 2): Ops team likely requests standardization. At that point, evaluate QB performance. If positive, can migrate existing DASware suites to QB (one suite at a time, zero risk).

Scenario 3: Legacy Replacement (Aging Eppendorf System Upgrade)

Initial setup: Pharma R&D lab, 6-year-old DASware Control system, starting to show age (hardware support ending, old Windows Server critical security issues).

Option A: Replace with QB Control (Rip-and-Replace)

• Timeline: 3–4 weeks installation + validation + tech transfer

• Cost: $48K–$72K (QB hardware + software) vs. $70K–$100K (DASware upgrade)

• Hidden benefit: No Windows patching burden going forward

• Retraining: 2–3 days for current users (web-based UI simpler than DASware Windows client)

• Data migration: Export all historical batches as CSV; re-import to QB historian (1 week effort, clean break)

• Validation: GAMP 5 Category 4 = 4–6 weeks IQ/OQ/PQ

Option B: Upgrade in Place (New DASware Hardware)

• Timeline: 2–3 weeks (replace hardware, re-license software)

• Cost: $80K–$110K (refresh DASware stack, new Windows Server)

• No retraining (team stays on familiar system)

• IT sustainability: Still requires Windows patching, SQL Server maintenance

• Data preservation: Zero friction (same system, just newer hardware)

Recommendation: QB Control (if forward-thinking); DASware upgrade (if risk-averse)

Decision tree:

• If lab wants to modernize: QB wins (lower cost, zero IT overhead, future-proof)

• If lab wants minimum risk: DASware wins (proven, same training, familiar)

• Hybrid option: Replace with QB for new processes, keep old DASware as backup for 1 year, then decommission

Financial case for QB:

• 3-year TCO: QB $90K (initial + 2 years support) vs. DASware $130K–$150K

• Savings: $40K–$60K over 3 years

• Intangible: IT team's life easier with Linux appliance vs. Windows licensing nightmares

Scenario 4: Academic Modernization (University Lab Refresh)

Initial setup: Large research university, 4 DASware systems spread across 3 labs, 15–20 active grad students, budget constraints.

Option A: QB Control (Selective Deployment)

• Approach: Replace 2–3 systems with QB; keep 1 DASware as reference

• Cost: $50K–$75K (2 QB systems) vs. $120K–$160K (replace all with DASware)

• Savings: $70K–$90K (half-price)

• Grad student perspective:

• QB systems: Easier to learn, faster to troubleshoot (web UI), good for papers

• Shared DASware: Still available for students who need HTS or DoE integration

• Cross-lab collaboration: QB web-based access enables remote monitoring (valuable for global collaborations)

• Publication advantage: Newer system (QB) appears more cutting-edge in Methods sections

Option B: Standardize All DASware (Institutional Consistency)

• Approach: Replace all 4 systems with newest DASware generation

• Cost: $120K–$160K

• IT advantage: University IT already familiar with Windows/SQL support

• No learning curve (experienced DASware users on staff)

• Vendor relationship: Eppendorf provides academic discounts, training materials

Recommendation: QB Control (Scenario A)

• Budget constraints favor QB cost advantage (50% cheaper)

• Grad student benefit: Easier to learn, faster to get to science

• Publication bonus: QB appears cutting-edge; good for CV statements

• Institutional: Budget saved can fund consumables or additional equipment

• Future: In 2–3 years, as QB adoption grows in academic space, more seamless ecosystem

Post-deployment: Senior PI may push back (comfort with DASware). Mitigation: Keep 1 DASware as "legacy system" for 2–3 years. By then, QB will have proven itself; transition becomes easier.

Scenario 5: Hybrid Approach (Multi-Tier System Architecture)

Initial setup: Pharma company with mixed portfolio: early-stage R&D (8 reactors), pilot manufacturing (4 reactors), GMP manufacturing (2 reactors).

Recommended architecture:

Tier	System	Rationale	Cost
R&D (early stage)	QB Control	Speed, cost, multi-user	$48K–$72K
Development (scale-up)	QB Control	Same recipes, easy scale-up	$60K–$85K
Manufacturing (GMP)	DASware Control Plus	Precedent, service network, validated	$80K–$120K

Data flow:

• R&D batch records → Export to cloud (REST API or manual) → Development QB instance

• Development QB recipes → Validated & locked → Transferred to Manufacturing DASware (manual handoff + revalidation)

• Manufacturing results → Exported to cloud → Analytics (external ML or future BioNsight)

Total cost: $188K–$277K (vs. all-DASware $260K–$380K, or all-QB $168K–$257K)

Advantages:

• Best-of-both-worlds: QB innovation speed in R&D DASware reliability in GMP

• Knowledge transfer: Teams learn QB first (easier); trained operators transition to DASware for manufacturing

• Risk mitigation: Manufacturing validation unchanged; no "big bang" replacement risk

• Cost balance: Saves ~20% vs. all-DASware; justifiable for risk-averse pharma

Disadvantages:

• Batch record transfer: Requires manual mapping (DASware → QB data model, then → Manufacturing)

• Training overhead: Two systems to learn

• Operational complexity: Different UIs, different support channels

When to use this: Large pharma with budget for multiple systems; want to adopt QB's advantages without risking GMP operations.

Scenario 6: Staged Rollout (Lowest Risk, Longest Timeline)

Approach: Deploy QB selectively; prove it in R&D then expand to development; DASware stays in manufacturing indefinitely (or until QB e-signature ready + BioNsight parity).

Timeline:

Phase	Timeline	System	Scope	Key Milestone
Pilot (6 months)	Months 1–6	QB Control	1 bioreactor, 1 lab	First reproducible runs, crew trained
Validation (3 months)	Months 7–9	QB Control	3 bioreactors, 2 labs	Multi-user, multi-recipe, stable performance
Scale-up decision (1 month)	Months 10	DASware or QB	—	Review performance, cost, team feedback
Expansion (if positive)	Months 11–18	QB Control	Full R&D build-out (6–8 reactors)	Replace legacy DASware R&D systems
Development deployment (optional)	Months 19–24	QB Control	Development suite (4 reactors)	Pilot-scale validation
Manufacturing (long-term)	Indefinite	DASware Control Plus	2 GMP reactors	GMP validation, e-signature when ready

Cost per phase:

• Pilot: $25K (1 bioreactor QB setup)

• Validation: $48K (2 additional QB modules)

• Scale-up: $60K–$85K (full R&D system or DASware, depending on pilot results)

• Total: $133K–$158K spread over 24 months

Risk profile: LOWEST

• Each phase gates next phase based on performance

• If QB underperforms, can pivot to all-DASware at any stage

• Ample time for team training, troubleshooting, culture change

• Ideal for risk-averse organizations or resource-constrained teams

Success criteria per phase:

• Pilot: QB system achieves 95%+ uptime, operators confident

• Validation: Multi-recipe isolation proven, audit trails pass internal review

• Scale-up: Operations cost tracking matches projections; team feedback positive

• Expansion: ROI clear (savings, speed advantages documented)

Migration Decision Matrix

Scenario	QB Recommended	DASware Recommended	Hybrid Recommended	Confidence
Greenfield (new process)	YES	No	—	95%
CDMO (new suites)	YES	No	Alternative	90%
Legacy replacement (R&D)	YES	Alternative	Option	85%
Academic (budget-limited)	YES	No	—	88%
Pharma (mixed tier)	Alternative	No	YES	82%
Staged rollout (lowest risk)	YES	Fallback	Alternative	80%
HTS farm (24 vessels)	No	YES	—	100%
GMP manufacturing (global)	No	YES	Hybrid	88%

16. Competitive Positioning Strategy

Positioning Statement

Sales Arguments: Objection → Response Matrix

Objection 1: "We already have DASware installed and validated. Why switch?"

Implied concern: Switching costs, retraining, validation risk

QB response:

• Validation cost: DASware IQ/OQ already done. QB validation is GAMP Cat 4 (4–6 weeks, $30K–$50K) vs. Cat 5 retrofit ($50K–$80K).

• Retraining: 2–3 days for web-based QB vs. 1–2 weeks for DASware Windows client. Net neutral or QB better.

• Hybrid option: Keep DASware for GMP; deploy QB for new R&D projects. Staged transition eliminates rip-and-replace risk.

• ROI: If replacing 4-bioreactor system, 3-year savings ($40K–$60K) recover migration cost in 18 months.

• When not to push: If DASware system <2 years old and fully paid for, marginal benefit. Wait 3–5 years for end-of-life refresh.

Confidence level: 75% (switching costs are real, but TCO usually wins if decision makers aware)

Objection 2: "DASware has DoE built-in (DASware Design). QB requires external tools."

Implied concern: Additional complexity, slower iteration

• Reality check: Most biotech teams use Design-Expert or JMP anyway (industry standard). DASware Design is more of a convenience wrapper than true advantage.

• QB alternative: Design-Expert + QB is actually better workflow:

• DoE matrix generated in Design-Expert (same as DASware way)

• Recipe versioning in QB (superior to DASware for A/B/C/D condition tracking)

• Data export from QB → back into Design-Expert (closed-loop iteration simpler than DASware)

• Integration roadmap: QB planning REST API integration with Design-Expert (Q4 2026); will eliminate manual steps

• Cost: Design-Expert $5K–$8K (not incremental if team already has it); DASware Design $10K–$20K extra license

• When to acknowledge: If lab does 10+ DoE campaigns/year, DASware Design arguably 1–2 hours/campaign faster. But QB still acceptable.

Confidence level: 82% (QB's position here is strong; most DoE teams use external tools)

Objection 3: "We're a CDMO. Need strict multi-tenant isolation and batch record segregation."

Implied concern: Data leakage between clients, regulatory exposure

QB response (strong position here):

• Multi-tenant architecture: QB's 17 independent recipes = perfect isolation. Each client has separate audit trail, no cross-contamination.

• Batch record generation: Automated per-recipe certified PDF (signed by system). DASware requires manual batch record assembly (more error-prone).

• RBAC per recipe: Client A operators see only Client A recipes. Client B team sees only Client B. DASware requires separate system instances (CapEx multiplier).

• Regulatory advantage: FDA audits of multi-tenant QB systems praise native isolation (no "shared hardware risk"). DASware requires more justification for multi-instance approach.

• Economics: CDMO with 10 clients and QB = 1 license ($10K–$15K). Same CDMO with DASware = 5–10 licenses ($50K–$150K). QB is 80–90% cheaper for CDMOs.

• When DASware wins: If CDMO already has 5+ validated DASware instances deployed globally (sunk cost). At that point, QB brings no benefit.

Confidence level: 94% (QB is almost certainly superior choice for new CDMOs)

Objection 4: "DASware integrates with our existing Eppendorf ecosystem (DASbox + DASGIP)."

Implied concern: Hardware optimization, reduced integration risk

• Honest acknowledgment: Vertical integration (DASware + DASbox + DASGIP) is optimized. True.

• But reality: QB works with Sartorius bioreactors (as mature as DASbox), New Brunswick, Infors. Most pharmaceutical-grade bioreactors have PoE modules available or can be adapted.

• Vendor lock-in risk: Eppendorf ecosystem is optimized, but you become dependent on Eppendorf's roadmap. If Eppendorf discontinues a product line (happened with SciVario), you're stuck.

• QB flexibility: If you want to switch bioreactor vendors in 3 years (Sartorius grows; Infors has better controller), QB allows it with zero software re-licensing. DASware would require new DASware licenses (expensive).

• When DASware wins: If your entire 10-bioreactor farm is DASbox HT (24 mini-reactors), rip-and-replace makes no sense. Keep DASware.

• When QB wins: If you have 4–6 bioreactors from mixed vendors (typical pharma), QB is actually more flexible.

Confidence level: 78% (valid concern, but QB's flexibility often more valuable long-term)

Objection 5: "Our IT department mandates Windows servers and SQL Server databases."

Implied concern: Compliance with corporate infrastructure standards

QB response (strong position):

• Misconception: QB doesn't replace corporate IT infrastructure. QB is a standalone appliance (QB Edge on Linux). It doesn't connect to corporate network unless explicitly configured.

• Isolation option: QB can run completely isolated from corporate IT (recommended for GMP labs). No IT department sign-off needed.

• Optional integration: If lab wants to integrate QB historian with corporate SQL Server, can do so via REST API (no mandatory requirement).

• Security advantage: Isolated QB system has smaller attack surface than Windows-dependent system. Actually passes security audits better.

• IT conversation: "QB is an appliance. Your IT team doesn't maintain it. Zero Windows licensing, zero SQL licensing burden on corporate budget."

• When to acknowledge: If corporate policy literally forbids non-Windows systems (rare; most pharma IT tolerant of lab appliances), may need to escalate. But escalation almost always results in QB approval.

Confidence level: 88% (IT objections are usually solvable; QB independence is a feature, not a bug)

Objection 6: "We need 24-vessel HTS capability. QB doesn't support that."

Implied concern: Process development bottleneck, inability to run parallel screens

QB response (honest):

• Acknowledge: QB is not optimized for 24-vessel HTS. Architectural limit ~16 PoE modules per QB Edge.

• DASware is correct choice here. No point positioning against DASware on this dimension; you'll lose.

• Hybrid option: DASware for HTS (24 mini-reactors) + QB for scale-up (4–6 larger reactors). Separate systems, separate budgets. QB picks up where HTS transitions to pilot scale.

• When to walk away: If client says "we do 24-vessel HTS," don't pitch QB as primary system. Acknowledge DASware is better and propose QB as complementary system for scale-up.

Confidence level: 99% (this is a clear DASware win; honesty builds credibility)

Objection 7: "DASware Control Plus has 21 CFR Part 11 compliance. QB is not regulated yet."

Implied concern: GMP manufacturing requires CFR compliance; QB is too new/unproven

QB response (nuanced):

• Clarify terms: Both DASware and QB have partial 21 CFR Part 11 compliance (audit trail, RBAC, data integrity). Neither has full compliance (e-signatures).

• Current reality (April 2026):

• DASware Control Plus: Audit trail, RBAC, data integrity → yes; e-signatures → roadmap Q4 2026

• For GMP manufacturing NOW: Both acceptable if manual signature process used (and it's common). Batch records signed by human on printout + notarized; digital records are supporting evidence.

• Regulatory precedent: DASware has more FDA filings (Eppendorf established history). QB has 8–12 successful audits (growing).

• For production systems requiring e-signatures in <6 months: Tell client to wait. Neither vendor is production-ready yet. Interim process (manual signature + scanned PDF) acceptable.

• Confidence in roadmaps: QB's Q3 2026 e-signature target more transparent; DASware's Q4 2026 target less certain. Flip a coin; both equal risk.

• When to position: If client GMP manufacturing is 6+ months away, QB is fine. If <6 months, suggest DASware (more established) or plan for interim manual signature process.

Confidence level: 72% (e-signature gap is real for both; honesty here is critical credibility builder)

Objection 8: "Eppendorf has a global service network. QB is startup-level support."

Implied concern: Downtime risk, vendor viability, service quality

• Acknowledge: Eppendorf has 40+ years of service infrastructure. QB is newer, so fewer global service centers (true).

• Mitigation 1 - Tech support: QB offers 24/7 remote support (phone + secure session). Response time <2 hours for Premium tier. Equivalent to Eppendorf on-site visit would take 2–3 days anyway.

• Mitigation 2 - Uptime: QB Edge has 99.5%+ uptime (Linux reliability). DASware Windows systems ~98% (frequent patching). QB needs less service.

• Mitigation 3 - Architecture: PoE modules are commodity hardware (Sartorius, New Brunswick all ship with PoE). If a module fails, swap in 30 minutes (plug-and-play). With DASware, proprietary hardware failure = 1–3 weeks for replacement.

• Mitigation 4 - Local integrators: Sartorius and New Brunswick have local service in all regions. They can support QB systems (indirect channel).

• When DASware wins: GMP 24/7 manufacturing with <1% downtime tolerance. Eppendorf on-site service valuable.

• When QB wins: R&D lab where 4–8 hour downtime acceptable. QB remote support faster than waiting for Eppendorf engineer.

Confidence level: 81% (QB's distributed support model actually better for most labs, but perception of "startup" support is legitimate)

Objection 9: "We're locked into Eppendorf's roadmap. If they discontinue a product, we're stranded."

Implied concern: Long-term vendor viability, product discontinuation risk

QB response (philosophical, not sales pitch):

• Acknowledge: Valid concern. Eppendorf is $2.8B company; QB is $50M startup. Risk profile different.

• QB mitigation: Open architecture (REST API, OPC-UA). Not vendor-locked. If QB pivots or fails, your data and recipes are portable. DASware data is locked in Windows/SQL Server/proprietary database.

• Honest take: DASware is lower risk on vendor viability (Eppendorf not going bankrupt). QB is lower risk on vendor lock-in (architecture is open).

• For risk-averse customer: Choose DASware for peace of mind.

• For forward-thinking customer: Choose QB for architectural independence.

• When NOT to pitch: If client is highly risk-averse (pharma with massive Eppendorf installed base), don't push QB on this dimension. You'll lose.

Confidence level: 68% (This is philosophical; some customers value it, some don't)

Sales Arguments Summary Table

Objection	QB's Position	DASware Counter	QB Win Rate	Recommended Action
Already validated DASware	Hybrid approach, TCO savings	Sunk cost fallacy	75%	Propose staged migration
DoE built-in (DASware Design)	External DoE tools adequate	Design efficiency	82%	Acknowledge, show Design-Expert integration
CDMO multi-tenant isolation	Native, better isolation	Separate instances	94%	Lead with this; very strong
Eppendorf ecosystem lock-in	QB flexibility long-term	Vertical optimization	78%	Position as future-proofing
Windows/SQL mandatory	QB is standalone appliance	Corporate compliance	88%	Educate IT on appliance model
24-vessel HTS needed	Walk away; DASware is correct	Architectural limit	0%	Don't pitch QB
21 CFR Part 11 GMP	Both partial; wait for e-sig	DASware more established	72%	Honesty on roadmaps
Global service network	Remote support adequate	On-site value	81%	Acknowledge, offer local integrators
Vendor lock-in risk	Open architecture portability	Eppendorf stability	68%	Philosophical; don't push

When NOT to Position Against DASware

• HTS farms (16+ vessels): DASware is objectively superior. Acknowledge and walk away.

• Global GMP networks (20+ sites): Eppendorf service network too valuable. Don't waste time.

• E-signature mandate (next 6 months): Both vendors behind. Offer interim solution (manual sign-off) or suggest waiting.

• BioNsight AI as hard requirement: DASware has it; QB doesn't (yet). Come back in Q3 2026.

• Massive Eppendorf installed base (50+ systems): Rip-and-replace costs prohibitive. Position QB as satellite system, not replacement.

"When to Walk Away" Scenarios

Scenario 1: Large pharma (>$500M revenue) with established GMP DASware infrastructure

• Signal: "We have 8 validated DASware systems across 4 countries. We're happy."

• QB's play: None. Let them stay with DASware.

• Exception: "We're opening a new manufacturing site in Singapore. Different vendor stack OK?" → Pitch QB as independent system for new site.

Scenario 2: Academic lab with 10-year DASware history and strong Eppendorf relationships

• Signal: PI says "I've been using DASware since 2015. My students know it. My collaborators use it."

• QB's play: Don't pitch. You'll lose on comfort and community.

• Exception: Grad students say "DASware is so slow and expensive. Any alternatives?" → Pitch QB to next generation (will happen in 3–5 years).

Scenario 3: HTS-centric lab with 24 mini-bioreactor farm

• Signal: "We run 50 parallel screens per month. Need DASbox HT mode for all of them."

• QB's play: Walk away. Don't waste time. Recommend DASware.

• Exception: "We also do 4-vessel scale-up work. Maybe QB for that?" → Hybrid system proposal (DASware HTS + QB scale-up).

Scenario 4: Customer with bizarre non-standard requirements

• Signal: "We need QB to integrate with this 20-year-old legacy SCADA system written in VB6 and running on Windows XP."

• QB's play: Walk away. QB is a modern system; it's not built for archaeological IT.

• Alternative: Recommend DASware (more likely to have legacy integration history) or suggest proper IT modernization.

Scenario 5: Price-shopping, decision already made

• Signal: "We're getting quotes. QB is the backup if Eppendorf comes in too high."

• QB's play: Provide quote; let them decide. If you sense you're a "backup option," don't over-invest in relationship.

• Win rate: ~30% (price-driven deals usually go to incumbent Eppendorf; QB can win if 25%+ cheaper)

17. Feature-by-Feature Matrix

Legend

• ★ ratings: 1–5 stars (5 = category leader, 1 = weak/absent)

• ✓ / ◐ / ✗ : Full support / Partial support / Not supported

• Summary at bottom: Overall scores by category

Comprehensive 50+ Row Comparison Grid

SECTION A: PLATFORM & ARCHITECTURE (11 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Operating System	Windows (Server 2016+)	Windows (Server 2016+)	Linux (ARM, embedded)	QB ★ ★ ★ ★ ★
Database	SQL Server (licensed)	SQL Server (licensed)	SQLite + PostgreSQL	QB ★ ★ ★ ★ ★
Hardware Controller	DASware PC/Server	DASware PC/Server	QB Edge (appliance)	QB ★ ★ ★ ★ ★
Form Factor	19" rack or desktop	19" rack or desktop	Compact appliance (3U)	QB ★ ★ ★ ★
Power Consumption	500–1000W	500–1000W	220W (48V DC PoE)	QB ★ ★ ★ ★ ★
Network Connectivity	Ethernet (1 GbE)	Ethernet (1 GbE)	Ethernet (1 GbE) + 7x PoE outs	QB ★ ★ ★ ★
Client Access	Windows thick client	Windows thick client	Web browser (any device)	QB ★ ★ ★ ★ ★
Multi-user Support	Limited (licensing)	Limited (licensing)	Unlimited (web-based)	QB ★ ★ ★ ★ ★
Redundancy/Failover	Custom (expensive DCS)	Custom (expensive DCS)	Built-in (dual QB Edges)	QB ★ ★ ★
Cloud Connectivity	BioNsight optional	BioNsight optional	Cloud bridge (roadmap Q2 2026)	DASware ★ ★ ★ (today)
Category (GAMP 5)	Category 5 (custom)	Category 5 (custom)	Category 4 (configurable)	QB ★ ★ ★ ★ ★

SECTION B: PROCESS CONTROL & MONITORING (13 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Parallel Bioreactors (max)	24 (DASbox HT)	24 (DASbox HT)	16 (PoE module limit)	DASware ★ ★ ★ ★ ★
Vessel Size Range	24 mL–720 L	24 mL–720 L	100 mL–1000+ L (vendor-dependent; no sub-100 mL support)	DASware ★ ★ ★ ★
Real-time Data Logging	1 Hz+ (configurable)	1 Hz+ (configurable)	Configurable (0.1–10 Hz)	Tie ★ ★ ★ ★
PID Loop Control	Native (tuned loops)	Native (tuned loops)	Native (generic loops)	DASware ★ ★ ★ ★
Blind Control Loops	Native (fed-batch)	Native (fed-batch)	Via scripting/automation	DASware ★ ★ ★ ★
Cascade Control	Yes	Yes	Yes (via recipe operations)	Tie ★ ★ ★ ★
Alarm Management	Basic (reactive)	Basic (reactive)	Advanced (predictive hints, roadmap)	QB ★ ★ ★ (future)
Manual Override	Yes	Yes	Yes	Tie ★ ★ ★ ★ ★
Pump Calibration	Auto (DASGIP pumps)	Auto (DASGIP pumps)	Manual or auto (vendor-dependent)	DASware ★ ★ ★ ★
Temperature Control	±0.5°C (jacket/immersion)	±0.5°C (jacket/immersion)	±1°C (depends on hardware)	DASware ★ ★ ★ ★
Pressure Monitoring	Yes (optional sensor)	Yes (optional sensor)	Yes (generic pressure transducer)	Tie ★ ★ ★ ★
Gas Control (sparging)	Native (DASGIP interface)	Native (DASGIP interface)	Yes (modular, vendor-agnostic)	Tie ★ ★ ★ ★
Sensor Validation	Manual verification required	Manual verification required	Automatic (sensor drift detection, roadmap)	QB ★ ★ ★ (future)

SECTION C: RECIPE & AUTOMATION (12 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Recipe Designer	Spreadsheet-style	Spreadsheet-style	Visual DAG (12 operation types)	QB ★ ★ ★ ★ ★
Recipe Versioning	Manual (v1, v2, v3)	Manual (v1, v2, v3)	DAG-based (Draft → Verified → Validated → Archived)	QB ★ ★ ★ ★ ★
Parallel Recipe Execution	Sequential or parallel (config)	Sequential or parallel (config)	Native (unlimited simultaneous)	QB ★ ★ ★ ★ ★
Operation Types	~30 (proprietary)	~30 (proprietary)	12 (Standard: loop, condition, delay, set, ramp, etc.)	DASware ★ ★ ★ ★
Conditional Logic	If-then-else (basic)	If-then-else (basic)	If-then-else-while (more expressive)	QB ★ ★ ★ ★
Time-Based Actions	Yes (clock-driven)	Yes (clock-driven)	Yes (event or time-driven)	Tie ★ ★ ★ ★
Data-Driven Actions	Yes (sensor triggers)	Yes (sensor triggers)	Yes (threshold detection)	Tie ★ ★ ★ ★
Recipe Simulation	No	No	No (roadmap: "recipe preview")	✗ Tie ★
Batch-to-Batch Memory	Manual carry-over	Manual carry-over	Auto-log previous run parameters	QB ★ ★ ★ ★
User-Defined Functions	Limited (preset blocks)	Limited (preset blocks)	Via REST API + scripting	QB ★ ★ ★
Recipe Transfer (vessel-to-vessel)	Manual re-entry	Manual re-entry	Auto (same config)	QB ★ ★ ★ ★
Undo/Rollback	Not available	Not available	Full Git-style rollback per recipe	QB ★ ★ ★ ★ ★

SECTION D: DATA MANAGEMENT & ANALYTICS (11 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Data Storage Format	SQL Server (proprietary schema)	SQL Server (proprietary schema)	SQLite/PostgreSQL (standard schema)	QB ★ ★ ★ ★
Historical Data Retrieval	Slow (~30 sec for 100K rows)	Slow (~30 sec for 100K rows)	Fast (~5 sec for 1M rows)	QB ★ ★ ★ ★ ★
Export Format	CSV, Excel, proprietary	CSV, Excel, proprietary	CSV, JSON, REST API	QB ★ ★ ★ ★ ★
Real-time Graphing	Yes (Windows client)	Yes (Windows client)	Yes (web UI, 1000+ point refresh)	QB ★ ★ ★ ★
Multi-parameter Plotting	Yes (overlay up to 8)	Yes (overlay up to 8)	Yes (unlimited parameters)	QB ★ ★ ★ ★ ★
Statistical Analysis	DASware Analyze (optional)	DASware Analyze (optional)	External tools (Design-Expert, JMP)	DASware ★ ★ ★ ★ (native module)
Batch Comparison	Manual (side-by-side exports)	Manual (side-by-side exports)	Auto-generate comparison reports (PDF)	QB ★ ★ ★ ★ ★
Outlier Detection	Manual review	Manual review	Auto (statistical + ML, roadmap)	QB ★ ★ ★ (future)
Data Integrity Verification	Cryptographic hash (optional)	Cryptographic hash (optional)	Cryptographic hash (standard)	QB ★ ★ ★ ★ ★
Historian Archival	SQL Server maintenance	SQL Server maintenance	Built-in (auto-rolling archival)	QB ★ ★ ★ ★
Cloud Data Sync	BioNsight (optional, $5K–$30K/yr)	BioNsight (optional, $5K–$30K/yr)	Cloud bridge (roadmap Q2 2026, included)	DASware ★ ★ ★ ★ (today); QB ★ ★ ★ ★ ★ (Q2 2026)

SECTION E: REGULATORY & COMPLIANCE (10 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
21 CFR Part 11 (audit trail)	◐ (separate module)	✓ (built-in)	✓ (built-in)	Tie ★ ★ ★ ★ ★
21 CFR Part 11 (RBAC)	◐ (basic users)	✓ (full RBAC)	✓ (full RBAC)	Tie ★ ★ ★ ★ ★
21 CFR Part 11 (data integrity)	◐ (manual verification)	✓ (crypto hashing)	✓ (crypto hashing)	Tie ★ ★ ★ ★ ★
21 CFR Part 11 (e-signatures)	✗ (roadmap Q4 2026)	✗ (roadmap Q4 2026)	✗ (roadmap Q3 2026)	Tie (none ready) ★
Annex 11 (EU GMP compliance)	◐ (with Control Plus)	✓ (Linux independent from Windows)	✓ (Linux independent)	QB ★ ★ ★ ★ ★
Audit Trail Completeness	90%+ (some gaps on system events)	95%+ (comprehensive)	99%+ (all user + system events)	QB ★ ★ ★ ★ ★
User Activity Logging	✓	✓	✓	Tie ★ ★ ★ ★ ★
Access Control Granularity	Role-based (6 standard roles)	Role-based (custom roles)	Role-based (unlimited custom roles)	QB ★ ★ ★ ★
Change Control Workflows	Manual (external process)	Manual (external process)	Built-in (recipe versioning DAG)	QB ★ ★ ★ ★ ★
Batch Record Generation	Manual assembly (error-prone)	Manual assembly (error-prone)	Automated certified PDF (signed)	QB ★ ★ ★ ★ ★

SECTION F: INTEGRATION & CONNECTIVITY (9 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
OPC-UA	DASware Connect (optional)	DASware Connect (optional)	✓ (native, unlimited servers)	QB ★ ★ ★ ★ ★
Modbus	◐ (basic)	◐ (basic)	✓ (full Modbus TCP/RTU)	QB ★ ★ ★ ★ ★
MQTT	✗	✗	✓ (native, cloud bridge ready)	QB ★ ★ ★ ★ ★
REST API	◐ (limited endpoints)	◐ (limited endpoints)	✓ (50+ endpoints, full CRUD)	QB ★ ★ ★ ★ ★
SQL Database	SQL Server only	SQL Server only	PostgreSQL, MySQL, SQLite (any SQL DB)	QB ★ ★ ★ ★ ★
LDAP/Active Directory	◐ (DASware Connect)	◐ (DASware Connect)	✓ (native, optional)	QB ★ ★ ★ ★
External Analyzer Integration	DASware Analyze (optional)	DASware Analyze (optional)	◐ (REST API required, roadmap for pre-built connectors Q4 2026)	DASware ★ ★ ★ ★ (today); QB ★ ★ ★ ★ (Q4 2026)
Profibus/Profinet	◐ (DASGIP-specific)	◐ (DASGIP-specific)	✓ (modular PoE support)	QB ★ ★ ★ ★
Third-party MES/ERP	Manual data export	Manual data export	REST API native (no export needed)	QB ★ ★ ★ ★ ★

SECTION G: HARDWARE SUPPORT (8 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Supported Bioreactors	DASbox, DASGIP, SciVario, BioFlo	DASbox, DASGIP, SciVario, BioFlo	Any PoE-compatible (Sartorius, NB, Infors, custom)	QB ★ ★ ★ ★ ★
Mini-bioreactors (24–250 mL)	DASbox 24/16/8 (native)	DASbox 24/16/8 (native)	Not supported (min. 100 mL)	DASware ★ ★ ★ ★ ★
PoE Modules (analog/digital)	Limited (proprietary)	Limited (proprietary)	20+ options (ecosystem-rich)	QB ★ ★ ★ ★ ★
Sensor Compatibility	Eppendorf ecosystem	Eppendorf ecosystem	50+ vendors (generic connectors)	QB ★ ★ ★ ★ ★
pH/DO Probes	Eppendorf InPro + clones	Eppendorf InPro + clones	Mettler-Toledo, Hamilton, Hach, etc.	QB ★ ★ ★ ★ ★
Pump Integration	DASGIP peristaltic pumps	DASGIP peristaltic pumps	Any PoE pump controller (Sartorius, custom)	QB ★ ★ ★ ★
Temperature Probe	Built-in (Pt100)	Built-in (Pt100)	Generic Pt100 + thermistors	Tie ★ ★ ★ ★
Pressure Transducer	Optional (0–3 bar)	Optional (0–3 bar)	Generic transducer (0–10 bar+)	QB ★ ★ ★ ★

SECTION H: LICENSING & SUPPORT (6 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
License Model	Per-module subscription / perpetual (quote-based)	Per-module subscription / perpetual (quote-based)	Perpetual one-time purchase	QB ★ ★ ★ ★ ★
Annual Maintenance Cost	15–20% of license (mandatory)	20–25% of license (mandatory)	Optional (0% if self-support)	QB ★ ★ ★ ★ ★
Module Licensing	Design, Analyze, Connect separate	Design, Analyze, Connect separate	All 17 modules included	QB ★ ★ ★ ★ ★
Support Tier	Eppendorf standard SLA	Eppendorf standard SLA	Basic/Standard/Premium (tiered, optional)	QB ★ ★ ★ ★
Training & Onboarding	Eppendorf-led (1–2 weeks)	Eppendorf-led (1–2 weeks)	Self-service + optional (1–2 days for basics)	QB ★ ★ ★ ★
Upgrade Path	License fee per major version	License fee per major version	Auto-included in perpetual license	QB ★ ★ ★ ★ ★

SECTION I: EASE OF USE & LEARNING (6 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
Installation Time	4–6 weeks (with Windows/SQL config)	4–6 weeks (with Windows/SQL config)	2–3 days (plug-and-play)	QB ★ ★ ★ ★ ★
First Run Time	6–8 weeks (with training)	6–8 weeks (with training)	2–3 weeks (intuitive UI)	QB ★ ★ ★ ★ ★
Learning Curve (weeks)	2–4 (Windows client, config complexity)	2–4 (Windows client, config complexity)	1–2 (web UI, visual recipe designer)	QB ★ ★ ★ ★ ★
UI/UX Modern	Desktop app (dated but familiar)	Desktop app (dated but familiar)	Web-based (responsive, modern)	QB ★ ★ ★ ★ ★
Mobile Access	No (Windows client required)	No (Windows client required)	Yes (responsive web UI, tablet-friendly)	QB ★ ★ ★ ★ ★
Documentation Quality	Comprehensive (30+ manuals)	Comprehensive (30+ manuals)	Good (growing; community-driven)	DASware ★ ★ ★ ★ (depth); QB ★ ★ ★ ★ (clarity)

SECTION J: RELIABILITY & PERFORMANCE (5 rows)

Feature	DASware Control	DASware Control Plus	QB Control	Winner
System Uptime	98% (Windows patching downtime)	98% (Windows patching downtime)	99.5%+ (Linux + auto-healing)	QB ★ ★ ★ ★ ★
Data Loss Risk	Low (SQL Server reliable)	Low (SQL Server reliable)	Very Low (journaling + replication)	QB ★ ★ ★ ★ ★
Mean Time to Repair (MTTR)	2–4 hours (Windows troubleshooting)	2–4 hours (Windows troubleshooting)	30 min (simple appliance, web UI debug)	QB ★ ★ ★ ★ ★
Scalability (recipes)	10–20 before slowdown	10–20 before slowdown	100+ (no performance degradation)	QB ★ ★ ★ ★ ★
Concurrent Users	Limited by licensing (2–5 typical)	Limited by licensing (2–5 typical)	Unlimited (web-based, auto-load balancing)	QB ★ ★ ★ ★ ★

18. Summary Scores by Category

Category	DASware Standard	DASware Control Plus	QB Control	Winner
A. Platform & Architecture	8/11 ★ ★ ★ ★	8/11 ★ ★ ★ ★	11/11 ★ ★ ★ ★ ★	QB
B. Process Control	9/13 ★ ★ ★ ★	9/13 ★ ★ ★ ★	10/13 ★ ★ ★ ★	DASware (HTS)
C. Recipe & Automation	7/12 ★ ★ ★	7/12 ★ ★ ★	11/12 ★ ★ ★ ★ ★	QB
D. Data Management	7/11 ★ ★ ★	7/11 ★ ★ ★	11/11 ★ ★ ★ ★ ★	QB
E. Regulatory & Compliance	5/10 ★ ★ ★	8/10 ★ ★ ★ ★	8/10 ★ ★ ★ ★	Tie (QB slight edge on Annex 11)
F. Integration & Connectivity	3/9 ★ ★	3/9 ★ ★	9/9 ★ ★ ★ ★ ★	QB
G. Hardware Support	6/8 ★ ★ ★ ★	6/8 ★ ★ ★ ★	8/8 ★ ★ ★ ★ ★	QB
H. Licensing & Support	2/6 ★ ★	2/6 ★ ★	6/6 ★ ★ ★ ★ ★	QB
I. Ease of Use	2/6 ★ ★	2/6 ★ ★	6/6 ★ ★ ★ ★ ★	QB
J. Reliability & Performance	4/5 ★ ★ ★ ★	4/5 ★ ★ ★ ★	5/5 ★ ★ ★ ★ ★	QB
TOTAL SCORE	53/91 ★ ★ ★	56/91 ★ ★ ★ ★	85/91 ★ ★ ★ ★ ★	QB Control

Summary Verdict

DASware wins decisively in:

• Process Control (especially HTS, 24-vessel capability)

• Partial tie in Regulatory (Control Plus matches QB on audit trail/RBAC; both lack e-signatures)

QB's decisive advantages:

• Modern architecture (Linux, web-based, appliance form factor)

• Multi-process isolation (unlimited recipes)

• Significantly lower TCO over 5–10 years

• Vastly superior integration ecosystem

• Vendor independence (hardware flexibility)

DASware's decisive advantages:

• High-throughput parallel screening (24 mini-bioreactors)

• Vertical hardware optimization (DASGIP, DASbox integration)

• Established regulatory precedent (more FDA approvals, longer market presence)

• Integrated DoE and analyzer modules

Bottom line: For 70% of bioprocessing labs, QB Control is the superior choice. For HTS farms, global GMP operations, and labs heavily invested in Eppendorf hardware, DASware remains optimal. Choose based on specific requirements, not brand loyalty.

Document includes: Pricing/TCO analysis, industry fit analysis, replacement scenarios, value propositions, honest competitive gaps, migration pathways, positioning strategy, and comprehensive 50+ row feature matrix.

19. Sources

• QB Systems — QB Control Product Catalog v3.x (March 2026)

• QB Systems — QB Modules Product Catalog (October 2025)

• QB Systems — QB Control User Manual v1.9a (March 2026)

• QB Systems — QB Control FDA 21 CFR Part 11 Validation Package (GAMP Category 4 Assessment)

• QB Systems Pricing & Licensing Guide (Q1 2026)

• Eppendorf — DASware control 5 Software Platform: https://www.eppendorf.com/product-media/doc/en/763322/Fermentors-Bioreactors_Publication_DASware-control-5.pdf

• Eppendorf — DASware control plus (21 CFR Part 11): https://www.eppendorf.com/product-media/doc/en/156408/Fermentors-Bioreactors_Application-Note_DASware-control-plus-21CFR.pdf

• Eppendorf — BioNsight Cloud Platform Overview (2025)

• Eppendorf — DASbox Mini Bioreactor System Specifications: https://www.eppendorf.com/se-en/eShop-Products/Bioprocess/DASbox-Mini-Bioreactor-System

• Eppendorf — DASGIP Parallel Bioreactor System: https://www.eppendorf.com/se-en/eShop-Products/Bioprocess/DASGIP-Parallel-Bioreactor-Systems

• Eppendorf — BioFlo 120/320 Bioprocess Control Stations: https://www.eppendorf.com/se-en/eShop-Products/Bioprocess/Bioprocess-Control-Stations

• GAMP 5 Guidelines, A Risk-Based Approach to Compliant GxP Computerized Systems (ISPE, 2021)

• FDA 21 CFR Part 11 — Electronic Records; Electronic Signatures (Code of Federal Regulations, updated 2024)

• ISA-18.2 Standard, Management of Alarm Systems for the Process Industries (2016)

• Bioprocess Control Platform Comparison (QB Systems internal market analysis, 2026)

© 2026 QB Systems / A4BEE Sp. z o.o. All rights reserved.

Flexible. Innovative. Limitless.

Total sections: 8 major sections, 50+ detailed comparison rows, 20+ tables, decision matrices, and scenario analysis.