QB Control vs Infors EVE Comparison

At a glance

Dimension	QB Control	INFORS eve
Hardware range	◆ 20+ PoE modules + OPC-UA to 3rd-party	INFORS HT devices preferred; limited 3rd-party
Back-end	◆ QB Edge (Linux ARM), embedded stores, no external DB	Windows server + NoSQL database
IT infrastructure	◆ Minimal (QB Edge + PoE switch)	High (Windows server, DB admin, backup)
Protocols	◆ OPC-UA, Modbus, MQTT, REST, SQL, LDAP	OPC, Modbus, REST
Scale / licensing	One perpetual license, all scales	Editions; up to 80 bioreactors per license
Deployment	◆ On-prem appliance, no VM overhead	Windows Server / VM

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

Appendices — Summary Scores by Category · Sources

1. Executive Summary

The Core Argument

eve® by INFORS HT is a web-based bioprocess management software purpose-built to plan, monitor, control, and automate bench-to-pilot bioprocesses — tightly paired with INFORS HT’s own bioreactor line (Minifors, Multifors, Labfors, Techfors) and incubator shakers. QB Control is a SCADA-class, browser-based bioprocess platform that ships its own modular hardware (QB Modules) and software co-engineered as one system — and that deploys both on QB Edge (benchtop QB Modules) and on a standard industrial PC driving stainless-steel, PLC-based systems via OPC-UA for pilot- and production-grade installations.

These are overlapping but distinct products. EVE is a software layer optimized for the INFORS hardware family, with strong DoE and data-management tooling and an established academic/biotech base. QB Control is a vendor-neutral turnkey hardware + software platform with ~40 pre-built services, native multi-vendor sensor support, a visual no-code recipe engine, built-in compliance scaffolding, and a lower total cost of ownership. The comparison is most relevant for lab-to-pilot bioprocessing (150 mL – 50 L benchtop, plus stainless-steel pilot/production via PLC), where a buyer is choosing a control and automation platform for new builds, expansions, or modernization.

Key Finding

QB Control does not replace EVE in every scenario. It replaces EVE where vendor neutrality, turnkey hardware, rapid deployment, and lower TCO matter more than EVE’s deepest strengths — and it is genuinely not the right answer where a lab is committed to the INFORS ecosystem, depends on EVE’s mature DoE tooling, or runs large shaker arrays. The sweet spot for QB Control as an EVE alternative is:

Scenario	QB Control Replaces EVE?	Value Driver
Greenfield lab (no INFORS hardware)	✅ Full replacement	Turnkey hardware + software, days vs. weeks setup
Multi-vendor / mixed bioreactor estate	✅ Strong replacement	OPC-UA native, no driver/gateway tax
Lab-to-pilot upstream (150 mL–50 L)	✅ Full replacement	~40 services, lower TCO, perpetual licensing
Stainless-steel pilot/production (PLC + OPC-UA)	✅ Strong replacement (new)	Industrial-PC deployment, reuse existing PLCs
Parallel fermentation (multi-vessel)	✅ Strong replacement	Plug-and-play parallel, auto-generated P&ID per process
INFORS-committed lab (large EVE recipe base)	⚠️ Partial / complementary	Coexist via OPC-UA; position for new vessels
DoE-centric process development	⚠️ Partial / complementary	EVE’s DoE tooling more mature; QB exports to external DoE
High-throughput shaker screening (40–80 shakers)	❌ Not a replacement	EVE + INFORS incubators are the native fit

2. Platform Philosophy

Fundamental Architecture Difference

Dimension	Infors EVE	QB Control
Product Category	Web-based bioprocess management software	SCADA-class browser-based platform (hardware + software)
Design Philosophy	Software layer over an INFORS hardware family	Co-engineered, modular-first hardware + software
Target Scale	Bench-to-pilot, up to ~80 bioreactors per installation	Lab-to-pilot (150 mL – 50 L benchtop); stainless-steel pilot/production via PLC + OPC-UA
Approach to Hardware	INFORS HT bioreactors preferred; 3rd-party via OPC	Own modular hardware (QB Modules) + open sensors; or existing PLCs (Wago/Siemens/Beckhoff)
Software Delivery	Browser front-end over a Windows back-end + database	Browser-based (any device, any OS)
Deployment Host	Windows workstation/server back-end	QB Edge for benchtop or standard industrial PC for PLC-based stainless steel
Configuration Model	Batch strategy editor + preconfigured functions	Visual drag-and-drop recipe designer (no coding)
Deployment Time	Days to weeks (device drivers, server, OPC setup)	Days (plug-and-play, auto-discovery)
Vendor Strategy	INFORS-aligned ecosystem (soft lock-in)	Open ecosystem (no lock-in)
GAMP Classification	Typically Category 5 with custom drivers	Category 4 (configurable software)

The “Software Overlay vs. Turnkey System” Distinction

EVE assumes the customer brings (or buys) INFORS bioreactors and wants a unifying software layer to bring web accessibility, batch tracking, DoE, and multi-system monitoring across that fleet. That assumption is excellent for labs committed to the INFORS hardware family — EVE’s native fit there is hard to beat. It is far less compelling when the buyer:

Is building a greenfield lab and wants hardware and software from one vendor
Runs a mixed bioreactor estate (Sartorius, Applikon, legacy units) and wants native multi-vendor control
Wants to avoid a Windows server back-end and database administration
Wants a stainless-steel pilot cell controlled through an existing PLC without buying a new bioreactor SKU

For these buyers, EVE’s software-overlay model adds an integration project on top of a hardware purchase. QB Control is a turnkey, vendor-neutral platform — hardware and software arrive co-engineered — and it now extends upward into stainless-steel pilot/production via industrial-PC deployment and OPC-UA/PLC integration, without inheriting EVE’s INFORS coupling or Windows footprint.

3. Architecture & Hardware

Controller & Hardware Architecture

Component	Infors EVE	QB Control
Central Host	Windows back-end (workstation or server) + database; browser front-end	QB Edge (runs QB Control locally) or industrial PC for PLC-based stainless-steel systems
I/O Architecture	INFORS bioreactor firmware + OPC/Modbus to 3rd-party	Power-over-Ethernet (one cable = power + data per module); or PLC I/O (Wago/Siemens/Beckhoff) via OPC-UA
Hardware Dependency	INFORS HT bioreactors preferred; 3rd-party via OPC gateway	QB Modules + open sensors; or reuse existing PLCs
Max Devices	Up to ~80 bioreactors per installation	Multiple parallel processes (license-dependent); 7 modules per QB Edge, expandable via QB Switch; PLC-bound for industrial-PC deployments
Device Discovery	Driver/OPC configuration + commissioning	Auto-discovery (Plug & Play) — module appears in QB Control automatically
Workstation Requirement	Browser front-end, but Windows back-end required	Any device with a browser (Chrome, Firefox, Edge, Safari)
Form Factor	Windows server/PC + INFORS bioreactor benches	Bench-top modules (310×115×115 mm each); or industrial PC + existing PLC cabinet
Power Architecture	Standard PC/server power + bioreactor power	PoE — single cable per module, no external power supplies
IT Infrastructure	High (Windows back-end, database admin, patches, backups)	Minimal (QB Edge + PoE switch; cloud backup optional)
Full reboot time	Varies by Windows configuration	Up to ~15 minutes for a full system reboot

QB Modules Hardware Ecosystem vs. EVE 3rd-Party Integration

Function	Infors EVE Approach	QB Control Approach
Pumps	INFORS bioreactor pumps; 3rd-party via OPC	QB Pump (peristaltic, centrifugal, syringe) — native; SmartPump (OPC) for 3rd-party
Sensors	INFORS-mounted probes; 3rd-party via OPC	QB Multisensor — connects up to 6 Hamilton/Mettler Toledo probes natively
Agitation	INFORS bioreactor agitation	QB Agitator, QB Multiagitator (2 or 6 vessels) — native
Temperature	INFORS thermal control	QB Thermo (heating/cooling 2–42 °C, heating mats) — native
Gas Flow	INFORS gas mixing modules	QB Gasflow (up to 2 gas streams, 0.1 SCCM – 20 SLPM) — native
Valves	INFORS bioreactor valves	QB Pinch Valve, QB Selector Valve (24 positions), three-way valves — native
Scales	External / 3rd-party	QB Multiscale (up to 6 scales via RS232) — native
Foam Detection	INFORS foam probe	QB Foam Sensor — optical, patent-pending, non-contact
Lighting	Photobioreactor support varies	QB Light (up to 6 independent LED outputs for photobioreactors)
Pressure	INFORS bioreactor sensors	QB Pressure Sensor (up to 2 single-use IBP transducers)
Incubator shakers	Native (INFORS Multitron, Ecotron, Minitron)	Not covered — QB is bioreactor-focused

Key Hardware Advantage: QB Control

No Windows server back-end and no database administration — QB Edge is self-contained
Auto-discovery eliminates manual device commissioning
PoE eliminates separate power infrastructure for benchtop deployments
Open sensors — use Hamilton, Mettler Toledo, Levitronix at market price (no vendor markup)
Vendor-neutral — QB Modules and OPC-UA endpoints sit side by side in one P&ID
New: for stainless-steel systems with existing PLCs, QB Control deploys on an industrial PC and integrates over OPC-UA — reusing field hardware instead of replacing it

Key Hardware Advantage: Infors EVE

Native, mature integration with the INFORS bioreactor family — no module-by-module configuration for INFORS vessels
Incubator shaker support (Multitron, Ecotron, Minitron) for high-throughput shaker screening
Established hardware + software pairing with a long field track record in academic and biotech labs

4. Parallel Processing

Side-by-Side Comparison

Capability	Infors EVE	QB Control
Max Parallel Vessels	Up to ~80 bioreactors per installation; Multifors 2 (6) per benchtop unit	Multiple parallel processes (license-dependent); QB Multiagitator supports 6 vessels per module; multi-instance services per process
Parallel Architecture	Each vessel monitored/controlled per INFORS device	Each bioreactor = independent Process with own P&ID, alarms, recipes, batch recording
Cross-Vessel Logic	Limited; manual linking or external coordination	Process-level resource allocation; conditional logic across processes; conflict blockade prevents collisions
Independent Recipes Per Vessel	Yes — separate batch strategy per vessel	Yes — different recipes per process; parallel and sequential batch execution
Sequential Campaign Queuing	Manual or external scheduler	Sequential batch execution with Pending queue status + per-batch auto-stop conditions (new)
Unified Data View	EVE dashboard + reports	QB Graphs (per-process live + history), Reports (per-batch)
Cross-Batch Comparison	EVE reports + DoE tooling	QB Graphs multi-parameter overlay + CSV export for external analysis
Technology Transfer	Batch strategy reuse across INFORS vessels	Process & recipe Import/Export with device mapping & conflict resolution; P&ID preserved on versioning
Campaign Management	Manual coordination	Recipe Executions Board with full batch lifecycle (Pending, During Execution, Paused, Hold, Completed, Failed, Aborted)

QB Control’s Parallel Processing Model

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

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

Where QB Control Excels in Parallel Processing

No driver or OPC project to set up parallel operations across QB Modules — they auto-discover
Visual P&ID per process — auto-generated from configuration, not manually drawn; preserved and copied forward on versioning
Process & recipe Import/Export with device mapping — replicate a proven setup to new bioreactors and remap devices to the target system instantly
Multi-user concurrent access — different operators monitor/control different processes simultaneously from different devices
Lower incremental cost — adding a parallel bioreactor = adding QB Modules + license expansion (no new INFORS SKU or driver work)

Where Infors EVE Excels in Parallel Processing

Higher vessel ceiling — up to ~80 bioreactors per installation, ideal for large fleets and screening
Native parallel benchtop — Multifors 2 (6 vessels) ships with firmware EVE understands out of the box; no module configuration
Mature multi-experiment data aggregation across many vessels for DoE and analysis
Established workflows for parallel fermentation campaigns in the INFORS ecosystem

5. Multi-Vendor Integration

Protocol Support Comparison

Protocol	Infors EVE	QB Control
OPC UA	Supported (DA, XML-DA, UA) via gateway/driver	Native — primary path for PLC/stainless-steel integration; dedicated OPC UA Connector module with configurable mappings
Modbus	Supported (RTU, TCP)	Supported (TCP and RTU)
MQTT	Not native	Native — IoT real-time streaming
REST API	Supported (REST API for data/integration)	Native — modern web integrations
SQL (JDBC/ODBC)	Export-based; limited direct access	Native — direct database access
LDAP/Active Directory	Via Windows back-end	Native — SSO with corporate credentials, configurable search scope/timeout/pagination
MTP (Module Type Package)	Not a primary capability	Supported (new) — plug-and-produce integration + MTP-oriented signal presentation in Graphs
PROFIBUS / PROFINET	Limited	Profibus supported; PLC protocols (Wago/Siemens/Beckhoff)
Serial (RS232/RS485)	Via converters	Native (QB Multiscale, QB Multisensor)
SMTP (email)	Native — email alarms	Native — notification dispatch with SMTP config + delivery logs
Secured external communication	Via Windows/IT infrastructure	Supported — encrypted, protected external traffic

Sensor Vendor Support Comparison

Vendor	Infors EVE	QB Control
Hamilton	Via INFORS bioreactor mounting or OPC	Native — Arc module sensors via QB Multisensor (DO, pH, conductivity, OD, CO₂, ORP); two-point / zero-point / slope calibration
Mettler Toledo	Via INFORS bioreactor mounting or OPC	Native — ISM/Modbus sensors via QB Multisensor (DO, pH, ORP, CO₂, conductivity)
Levitronix	Custom integration	Native — flow meters via QB Multisensor
Mettler Toledo / Kern Scales	External / serial	Native — MT-SICS / PKP series via QB Multiscale
Sartorius / Applikon bioreactors	Supported via OPC integration (mature)	OPC-UA native (no gateway, no license penalty)

Integration Philosophy Difference

Infors EVE: “We provide the bioprocess management software and the bioreactors. Our software is tuned for INFORS hardware; third-party equipment (Sartorius, Applikon) connects through OPC integration, which is mature but adds engineering effort. The back-end runs on Windows with a database.”

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

QB Control’s Integration Advantage

Native sensor support — Hamilton and Mettler Toledo probes connect directly to QB Multisensor via Modbus RS485. No INFORS bioreactor required, no gateway
Modern protocols — MQTT, REST API, SQL are native, enabling real-time streaming to data warehouses and AI/ML pipelines. EVE is export- and REST-oriented
OPC UA Connector — a dedicated module bridges OPC-UA equipment into QB Control with configurable mappings, connector profiles, and per-connector service templates — the path for PLC-based stainless-steel systems and for third-party bioreactors with no license penalty
MTP support (new) — plug-and-produce modular integration
Auto-discovery vs. manual driver/OPC commissioning — plug in a QB Module and it appears in the inventory automatically

Infors EVE’s Integration Advantage

Native, mature INFORS hardware integration — no driver work for INFORS vessels and shakers
Proven OPC integration with Sartorius and Applikon — a well-tested path for those vendors
Mature data-management layer — multi-experiment aggregation feeding EVE’s DoE tooling
Established ecosystem — long field history in academic and biotech labs

6. Software Module Comparison

Module-by-Module Mapping

QB Control ships 18 software modules (up from the prior count), accessed through the Portal. The two additions since the previous comparison are Remote Access and Health Monitoring.

Capability Area	Infors EVE Component	QB Control Module	Comparison
Device Management	Device setup UI (INFORS-tied)	Inventory (auto-discovery, device status, configuration import/export, licensing)	QB simpler & vendor-neutral
System Configuration	System admin (basic)	System (visual resource allocation, search, bulk add/remove, history to CSV)	QB no-code & comprehensive
Process Configuration	Batch template per bioreactor type	Process (visual binding, versioning, duplicate process, live connection status, guided import/export)	QB dynamic; EVE static per device
Process Visualization	Setpoint dashboard	P&ID (auto-generated, drag-and-drop, recipe execution from diagram, P-Stop/E-Stop)	QB auto-generates full flow diagram
Batch Management	Batch strategy editor	Recipe (Designer / Batch / Executions Boards)	QB visual designer with Services
Services Catalog	Preconfigured functions (~20, INFORS-tied)	Services (~40 templates across 10 categories, load & execute in minutes)	QB advantage (broader, hardware-agnostic)
Service Profiles	No equivalent	Service Profiles (reusable grouped/atomic parameter templates, portable import/export)	QB unique advantage
Alarm Management	Email/threshold alarms	Alarms (ISA-18.2 conformance, watchlist, in-app global notifications)	QB richer (escalation, ISA-18.2)
Data Visualization	EVE dashboard graphs	Graphs (live + history, multi-axis, annotations, MTP signals, export)	Comparable; QB adds annotation/overlay
Reporting	Report generator (Premium)	Reports (automated + manual, PDF/DOCX, recipe-execution & service-history sections)	Both mature
Batch Tracking	Batch repository	Runs (per-process, batch ID, user tracking, report linkage)	Both adequate
Calibration	INFORS device firmware	Calibration (status tracking, Next Due Dates, Hamilton/pump methods, device-type-aware history)	QB integrated; EVE device-tied
Audit Trail	Premium edition only	Audit Trail (21 CFR Part 11 conformance, cross-module, exportable CSV)	QB built-in, all editions
Access Control	RBAC (Premium only)	Users & Roles (RBAC, 18 permission groups, LDAP/AD)	QB native, all editions
Notifications	Email only	Notifications (in-app center, email/SMTP, per-user preferences, recipe-step alerts, logs)	QB multi-channel
Backup	Manual (user responsibility)	Backup, Export & Archive (scheduled/manual wizards, one-click restore, integrity verification)	QB automated
License Management	Subscription/perpetual tiers	License (feature/device/system/time-based, online/offline, host-bound, license guards)	QB more flexible
Remote Access	Browser front-end over Windows	Remote Access (secure VPN, QR-code setup, phone/tablet/PC, role-based) — new	QB simpler, multi-device
Health Monitoring	Diagnostics via OS/EVE	Health Monitoring (system health dashboard, per-module status, drill-down) — new	QB consolidated, always-on
DoE / Experiment Design	Mature DoE tooling	❌ Not native (export to external DoE tools)	EVE wins
Soft Sensors	Mature soft-sensor library	❌ Not native	EVE wins
Incubator Shaker Support	Native (INFORS incubators)	❌ Not available	EVE wins
Multi-Language UI	Multiple languages	English (localization on roadmap)	EVE wins

7. Services Catalog & Rapid Deployment

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

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

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

Services Catalog by Category

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

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

Service Profiles — Reusable Parameter Templates

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

Infors EVE Approach: Preconfigured Functions & Batch Strategies

EVE provides preconfigured functions (temperature ramp, pH control via acid/base, DO control, feed strategies) within its batch strategy editor. Users build recipes by sequencing these functions and setting parameters (PID gains, setpoints, duration). EVE’s strength is the breadth of bioprocess workflows tuned for INFORS hardware and its mature DoE integration; its limitation is that the functions are coupled to INFORS instruments and custom logic requires manual OPC/Modbus configuration.

How Services Transform Experiment Deployment

Workflow Step	Infors EVE Approach	QB Control with Services Catalog
Define control strategy	Select a preconfigured function (INFORS-tied)	Select service template from catalog
Set parameters	Enter values in the batch strategy editor	Load a saved Service Profile or enter values in a visual form
Change control logic	Reconfigure function / OPC script	Swap service template — minutes, not days
Deploy to process	Assign strategy to vessel, monitor via dashboard	Add service to process; it appears in Recipe Designer — minutes
Try a different strategy	New batch strategy / manual reconfiguration	Select a different service / apply a different profile — instant

Time-to-Deploy for Experiment Strategy Changes

Scenario	Infors EVE Time	QB Control Time	QB Advantage
Switch pH control from CO₂+Base to Acid+Base	Days (reconfigure, test)	5 minutes (swap service template)	~100× faster
Add foam control to an existing process	Days (probe + function setup)	10 minutes (add service + connect foam sensor)	~50× faster
Change temperature control from setpoint to ramp	Hours–days	2 minutes (change parameters or swap template)	~100× faster
Deploy a completely new experimental strategy	1–3 weeks	1–2 hours (select services, build recipe, validate)	~50× faster
Replicate a proven setup to a new bioreactor	1–2 weeks (new vessel config)	15 minutes (Process Import/Export + device mapping + Profiles)	~50× faster

This breadth of plug-and-play, hardware-agnostic services is where QB Control pulls ahead at lab/pilot scale. EVE’s functions are mature but tied to INFORS instruments; QB Control makes a strategy change a catalog selection on any supported hardware.

8. Recipe Engine

Overview

The Recipe Module is the core automation engine of QB Control. It translates biotechnological protocols into executable digital workflows by combining logic blocks and Services (hardware actions), through three integrated boards: Designer Board (create/edit), Batch Board (configure/execute), and Executions Board (monitor history).

8.1 Designer Board & the Unified Block Library

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

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

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

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

8.2 Batch Board

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

8.3 Executions Board

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

8.4 Validation & Safety

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

8.5 Recipe Engine vs. EVE Batch Strategies — Detailed Comparison

Capability	Infors EVE	QB Control Recipe Engine
Workflow design	Batch strategy editor with preconfigured functions	Visual drag-and-drop Designer Board (no coding)
Parallel execution	Per-vessel batch strategies; multi-vessel via INFORS device	Split/Merge blocks for parallel paths
Sequential campaigns	Manual or external scheduler	Sequential batches with Pending queue + auto-stop
Conditional logic	Threshold-based functions	Conditional blocks with AND/OR on real-time data
Variables & math	Limited	Variable / Update Variables (increase/decrease/multiply/divide)
Timers	Phase timing	Timer block (start/stop/pause/resume)
Human-in-the-loop	Operator prompts	Manual Operation block
Execution monitoring	EVE dashboard	Batch Board with real-time, color-coded status
Recipe versioning	Implicit strategy versions	Draft → Verified → Validated → Hold → Archived
Pre-execution safety	Configurable checks	Mandatory checklist + Validator (system-enforced)
Ramp/profile control	Preconfigured ramp functions	Polygon block + service ramp parameters
Import/export	XML (EVE-specific)	Recipe/process import/export (portable across installations) + image export
DoE integration	Mature DoE tooling	Export to external DoE tools (MODDE, JMP)
Time to create recipe	Hours to days	Minutes to hours (visual, no-code)

9. Regulatory Compliance

Standard	Infors EVE	QB Control	Notes
FDA 21 CFR Part 11	✅ Premium edition (with e-sigs via integration)	⚠️ Partial conformance	EVE: full on Premium tier. QB: electronic records, audit trails, access control, user management today — electronic signatures not yet covered
EU Annex 11	✅ Premium edition	✅ Compliance support	Both provide computerized-system validation capabilities
GAMP 5	Typically Category 5 (custom drivers)	Category 4 (configurable)	QB Control has lower validation burden — no custom code to validate
ISA-18.2 (Alarms)	Basic threshold/email alarms	✅ Conformance	QB supports suppressed, out-of-service, acknowledgement workflows
ALCOA+ (Data Integrity)	✅ (Premium)	✅ Full implementation	Both provide ALCOA+ data integrity
Electronic Signatures	◐ Via LIMS / Premium integration	◐ On roadmap (Q3 2026 — not in current version)	EVE has a workaround today; QB planned
Audit Trail	✅ Premium edition only	✅ Immutable, exportable (CSV), cross-module, searchable — all editions	QB built-in across all editions
Role-Based Access Control	✅ Premium edition only	✅ All editions (18 permission groups)	QB native, lower cost
Safe Position Logic (GMP)	Via interlock engineering	✅ Built-in — define safe actuator states after restart/power cycle	QB has a dedicated, configurable feature
CE Marking	System-level	✅ Per QB Module (EMC + Low Voltage Directive)	Each module ships its own Declaration of Conformity

Compliance Value for QB Control

GAMP 5 Category 4 vs. Category 5 is a significant differentiator:

EVE with custom device drivers typically qualifies as Category 5 → full IQ/OQ/PQ validation, custom test scripts, extensive documentation
QB Control = Category 4 (configurable software) → reduced validation scope, standardized test scripts, faster qualification

What this means for the client: 50–70% reduction in validation effort, faster time to GMP-ready operation (weeks vs. months), lower CSV cost, and simpler change management (configuration changes, not code changes). In addition, QB Control includes audit trail and RBAC in all editions, whereas EVE gates these behind its Premium tier.

Honest Compliance Caveat

QB Control’s 21 CFR Part 11 conformance is partial: it delivers electronic records, audit trails, access control, and user management today, but electronic signatures are not yet implemented (roadmapped for Q3 2026). For workflows that require digital signatures on an active IND today, EVE Premium (with its e-signature integration path) is the safer choice until QB Control’s e-signature release. Do not represent QB Control as fully 21 CFR Part 11 compliant.

10. Pricing, Licensing & TCO

Direct Cost Comparison

Cost Component	Infors EVE Path	QB Control	Savings with QB
Entry-Level System	$40,000–$80,000+ (bioreactor + EVE license + Windows back-end)	QB Edge + basic modules + license: ~$15,000–25,000 (software reference)	50–70%
Typical Lab Setup (4 bioreactors)	$150,000–$250,000+ (INFORS hardware + EVE Standard/Premium)	4× bioreactor module sets + QB Edge + license: ~$60,000–85,000	50–65%
6-Bioreactor Lab Setup	$200,000–$300,000+	6× bioreactor module sets + QB Edge(s) + license: ~$100,000	55–67%
Pilot Setup (8–12 bioreactors)	$300,000–$500,000+	8–12× module sets + QB Edge(s)/switches + license: ~$150,000–250,000	40–55%
System Integrator / 3rd-party integration	$5,000–$20,000+ (OPC/driver connections)	$0 (self-setup, plug-and-play)	100%
Workstation Hardware	Browser, but Windows back-end PC/server required	$0 (any existing device with a browser)	100%
Software License	Subscription (Basic/Standard/Premium) or perpetual	Perpetual license (one-time purchase)	Significantly lower long-term
Windows Server / IT Overhead	$30,000–$50,000 over 5 years (license, DBA, patches, backups)	$0 (QB Edge self-contained)	100%
Training	Vendor training courses	QB Systems Online Portal + documentation — self-paced	80–90%
Validation (GAMP 5)	Category 5 — extensive IQ/OQ/PQ ($50,000–$100,000)	Category 4 — reduced scope ($15,000–$35,000)	50–70%

QB Control System Pricing by Scenario

Scenario	Reference Price (software)	Configuration Notes
Benchtop Entry (1 process, 1 bioreactor)	$15K–25K	QB Edge + Pump + Multisensor + Agitator + basic infrastructure
4-Bioreactor Benchtop Lab	$60K–85K	QB Edge + 4× (Pump, Multisensor, Agitator, Tanks) + PoE switch
6-Bioreactor Lab (Advanced)	~$100K	QB Edge + 6× (Pump, Multisensor, Agitator, Selector, Gasflow) + advanced P&ID
Pilot Scale (8–12 vessel equivalent)	$150K–250K	Scaled hardware + QB Edge(s)/switches + integration with legacy bioreactors
Integrator / VAR	$0 (white-label)	Full QB Control platform, included in system integrator’s price
End-user Workstation License	$0 (unlimited)	Read-only or operator-role access; any browser, any number of users

Total Cost of Ownership (5-Year Projection)

Scenario: 6-bioreactor parallel upstream processing lab

TCO Component	Infors EVE Path (5-Year)	QB Control (5-Year)
Hardware (bioreactors / QB Modules + QB Edge)	$200,000 (INFORS)	$100,000 (QB Modules)
Software licensing	$100,000–$150,000 (subscription accumulation)	$30,000 (perpetual, one-time)
Paid support & maintenance	$40,000–$75,000	$25,000 (tiered support plan)
3rd-party integration	$20,000	$0
Windows / IT infrastructure	$30,000–$50,000	$0
Validation	$80,000 (GAMP Cat 5)	$20,000 (GAMP Cat 4)
Training	$10,000 (vendor courses)	$5,000 (Online Portal, self-paced)
TOTAL	~$480,000–$575,000	~$180,000
		~60–70% lower TCO

Note: INFORS HT does not publish list prices. EVE estimates are based on typical bioprocess equipment market pricing for comparable configurations and include INFORS bioreactor hardware. All QB Control prices are reference figures based on past quotations and do not constitute a specific priced offer.

Licensing Model Comparison

Aspect	Infors EVE	QB Control
Model	Subscription (monthly/annual) OR perpetual; Basic/Standard/Premium tiers	Perpetual license — feature-, device-, system/process-, and time-based dimensions
License Type	Tiered; compliance features gated to Premium	Perpetual — buy once; no recurring license fees; all compliance scaffolding included
Support	Bundled into subscription or paid for perpetual	Paid separately — tiered (Basic, Standard, Premium), client’s choice
Scalability Cost	New tier / per-bioreactor cost steps	One license covers all hardware; scale by adding modules
Concurrent Users	Named/seat licensing	Unlimited concurrent users (workstation license $0)
Enforcement	Subscription/seat enforcement	Software license bound to the deployment host; license-aware UI and guards surface limits
Lock-In	INFORS-aligned ecosystem	Not tied to a specific hardware vendor
Hardware Dependency	INFORS bioreactors + Windows back-end	Any browser-capable device; QB Edge or industrial PC

Licensing Model — Key Client Value

No recurring license fees — the perpetual license does not expire, eliminating EVE’s subscription accumulation ($100K–$200K over 10 years for multi-bioreactor setups)
All compliance scaffolding included — audit trail and RBAC are not gated behind a Premium tier
Paid support is optional and tiered — no forced bundling
Predictable budgeting — one-time license + optional support
No “license hostage” risk — perpetual model means a lapsed contract never locks you out of your own system

11. Industry Fit Analysis

Biotech (Lab & Pilot Scale)

Criterion	Infors EVE	QB Control	Winner
Cell culture (150 mL–10 L)	Strong on INFORS vessels	Purpose-built, vendor-neutral	QB Control (multi-vendor)
Fermentation (1–50 L)	Strong on INFORS vessels	Native support	QB Control (open hardware)
Parallel bioreactors (lab)	Up to ~80; native parallel benchtop	Multiple processes, auto-generated P&IDs	Tie (EVE higher ceiling; QB simpler/cheaper)
Stainless-steel pilot (PLC)	OPC integration	Industrial-PC deployment + OPC-UA (new)	QB Control (right-sized, reuse PLC)
Process development / DoE	Mature DoE tooling	Rapid reconfiguration; export to external DoE	Infors EVE (DoE depth)
Single-use bioprocessing	Supported on INFORS SU	Native SU pump heads, SU pressure sensors	QB Control (more flexible)
Soft sensors / estimated parameters	Mature library	Not native	Infors EVE
Technology transfer	Batch strategy reuse on INFORS	Process/recipe import/export + device mapping	Tie

Pharmaceuticals

Criterion	Infors EVE	QB Control	Winner
R&D lab automation	Capable on INFORS hardware	Right-sized, vendor-neutral	QB Control
Process development	Good; DoE depth	Faster iteration, lower cost	Tie (QB speed/cost; EVE DoE)
Batch records / audit trail	Premium edition only	Built-in, all editions	QB Control
GMP production (small scale)	Premium (e-sigs via integration)	CFR Part 11 partial (no e-sigs yet)	Infors EVE (e-sigs today)
GMP production (large scale)	Up to ~80 bioreactors	Lab-to-pilot/early production	Infors EVE (vessel ceiling)
Validation documentation	Manual; external consultant	QB templates; 50–70% reduction	QB Control

Cosmetics

Criterion	Infors EVE	QB Control	Winner
Formulation development	Batch strategy editor	Visual recipe designer — right-sized	QB Control
Small batch production	Capable but INFORS-tied	Affordable with compliance support	QB Control
Multi-product flexibility	Per-vessel strategies	Process reconfiguration in minutes	QB Control
Cost sensitivity	Subscription + Windows overhead	Perpetual, no IT overhead	QB Control

Academic / Research

Criterion	Infors EVE	QB Control	Winner
Teaching labs	Established INFORS base	Affordable, visual, intuitive	Tie
Research bioprocessing	Mature, DoE tooling	Fast, modular, reconfigurable	Tie (EVE DoE; QB agility)
Multi-student access	Named/seat licensing	Any browser, multi-user concurrent	QB Control
Hardware cost entry	Low-cost Minifors benchtop	QB Edge + modular (~$15K–25K)	Infors EVE (lower hardware entry)
Shaker / HTS screening	Native incubator support	Not covered	Infors EVE
Publication-ready data	Reports, CSV/XML	Graphs export (PNG, CSV) + Reports (PDF, DOCX)	Tie

12. What QB Control Can Replace

Full Replacement Scenarios

1. Greenfield Lab Bioreactor Control (150 mL–10 L) — EVE software overlay + INFORS hardware purchase → QB Edge + QB Modules as one turnkey system. Value: no integration project, days vs. weeks setup, no Windows back-end, browser-based access.

2. Multi-Vendor / Mixed Bioreactor Estate — EVE + OPC-integrated 3rd-party vessels → QB Control with native OPC-UA orchestration alongside QB Modules in a unified P&ID. Value: no gateway/driver tax, no license penalty for third-party hardware.

3. Parallel Small-Scale Fermentation — EVE per-vessel monitoring → QB Control multi-process with QB Multiagitator. Value: plug-and-play parallel, auto-generated P&ID per process, sequential auto-stop campaigns, lower incremental cost per vessel.

4. Stainless-Steel Pilot Cells with Existing PLCs (new) — EVE OPC layer → QB Control on an industrial PC integrating the PLC via OPC-UA + the OPC UA Connector. Value: reuse field hardware, no Windows server, no integration re-engineering.

5. pH/DO/Temperature Control Loops — EVE preconfigured functions on INFORS probes → QB Multisensor (Hamilton/MT) + QB Gasflow + QB Thermo + services. Value: native multi-vendor sensor integration, no INFORS vessel dependency.

6. Recipe Design & Batch Execution (no shakers) — EVE batch strategy editor → QB Designer Board with the unified block library. Value: more expressive visual no-code logic, portable import/export.

7. Compliance-Driven Modernization — EVE Premium (audit trail/RBAC gated) → QB Control’s built-in audit trail and RBAC in all editions, GAMP 5 Category 4. Value: lower validation burden and no Premium-tier surcharge for governance features.

8. Real-Time Enterprise Data Integration — EVE export/REST model → QB Control native SQL + MQTT streaming. Value: real-time feeds to data warehouses and AI/ML pipelines without custom middleware.

Partial Replacement Scenarios

9. DoE-Centric Process Development — QB Control handles monitoring, control, and automation and exports data to external DoE tools (MODDE, JMP); EVE’s native DoE tooling may still be preferred for design-and-analysis depth. Value: QB Control as the control platform with external DoE, or coexist with EVE for the DoE layer.

10. Small-Scale GMP Production — QB Control provides partial 21 CFR Part 11 conformance (records, audit trails, RBAC, data integrity; e-signatures on roadmap). Value: lower validation burden (GAMP 5 Category 4), but may require an e-signature bridge until Q3 2026.

13. Where QB Control Creates Superior Value

13.1 Time-to-Process

Metric	Infors EVE	QB Control	Improvement
System setup	Days–weeks	< 1 week	Faster, turnkey
Add a bioreactor	1–2 weeks (new vessel/config)	< 1 day	~90% faster
Recipe modification	Hours (batch strategy editor)	Minutes (visual drag-and-drop)	~80% faster
New process configuration	Days–weeks	Hours (import/export or visual config)	~80% faster

13.2 Value Summary

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

Lowest TCO — ~~60–70% lower 5-year cost for a 6-bioreactor lab (~~$180K vs. ~$480K–575K), perpetual license, no Windows server or database administration (§10).
No vendor lock-in — open sensors and consumables, open protocols, no INFORS coupling, or reuse of existing PLCs (§5).
Operational simplicity — browser-based, auto-discovery, no-code recipes, multi-user access, and a single Health Monitoring dashboard (§3, §6).
Instant strategy changes — ~40 pre-built services and reusable Service Profiles let scientists swap a control strategy in minutes, on QB Modules or OPC-UA endpoints (§7).
Modern, open integration — native OPC-UA, REST, MQTT, SQL, MTP, and secure remote access with QR-code setup (§5).
Right-sized safety & governance — P-Stop/E-Stop, Safe Position Logic, and a mandatory pre-execution checklist + Validator (§8).

14. Gaps & Limitations

Infors EVE Capabilities Not Available in QB Control

Capability	Infors EVE	QB Control	Impact
Incubator shaker support	Native (Multitron, Ecotron, Minitron)	Not available	High for HTS/screening labs
Mature DoE tooling	Built-in design-and-analysis	Export to external DoE (MODDE, JMP)	Medium–high for DoE-centric labs
Soft sensors / estimated parameters	Mature library (biomass, yield, kinetics)	Not native	Medium for kinetic research
Vessel ceiling	Up to ~80 bioreactors per installation	Lab-to-pilot/early-production focus	High for large fleets/biobanks
Native INFORS hardware integration	Deep, out-of-the-box	OPC-UA to third-party (incl. INFORS with OPC-UA)	High for INFORS-committed labs
Electronic signatures	Premium / LIMS integration today	On roadmap (Q3 2026)	High for regulated production today
Multi-language UI	Multiple languages	English (localization on roadmap)	Low–medium for global teams
Established regulatory history	10+ years of FDA/EMA precedent	Emerging; Category 4 increasingly accepted	Medium for risk-averse pharma

Honest Assessment of QB Control Limitations

No incubator shaker support — EVE + INFORS incubators remain the native choice for high-throughput shaker screening
No native DoE tooling — design-and-analysis requires export to external tools; EVE’s DoE depth is a genuine strength
No soft sensors yet — estimated parameters (biomass, yield) are not native
Scale ceiling — optimized for lab-to-pilot and early stainless-steel production; very large fleets favor EVE’s higher vessel ceiling
No electronic signatures yet — 21 CFR Part 11 conformance is partial until the Q3 2026 release
Less regulatory track record — EVE has a longer FDA/EMA precedent base; QB Control’s Category 4 status is increasingly accepted but newer
English-only UI — localization is on the roadmap
Liquid-handling focus — QB Control does not address gas-phase, solid-phase, or complex hybrid processes

15. Migration & Replacement Scenarios

Scenario A: Greenfield Lab (No Existing INFORS Hardware)

Recommendation: QB Control. New lab from scratch = no migration, no Windows back-end, no integration project. QB Control delivers turnkey hardware + software for lab/pilot bioprocessing, ~60–70% lower TCO than the EVE + INFORS path, operational in days.

Scenario B: INFORS/EVE Lab Seeking Modernization

Recommendation: QB Control replacement for new vessels; coexist initially. Replace aging EVE-managed benchtop systems with QB Control; keep EVE running for any shaker arrays or large existing fleets; bridge via OPC-UA if needed. ROI typically recovered through eliminated subscription, Windows, and validation costs.

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

Recommendation: QB Control on an industrial PC. Deploy QB Control on an industrial PC, integrate the existing PLC over OPC-UA via the OPC UA Connector, and keep the field instruments. Value: SCADA-class supervisory control and recipes without buying a new bioreactor SKU or a Windows server.

Scenario D: Expanding Parallel Capacity

Recommendation: QB Control for new vessels. Keep existing EVE-managed INFORS bioreactors; add parallel capacity with QB Control + QB Modules; no impact on validated EVE systems; OPC-UA bridge for unified data if needed.

Scenario E: Multi-Vendor (EVE + legacy Sartorius/Applikon) Consolidation

Recommendation: QB Control for unified multi-vendor control. Consolidate EVE-monitored Sartorius/Applikon vessels under QB Control’s native OPC-UA orchestration in one P&ID and one recipe engine. Value: single pane of glass, unified batch records, no Windows back-end, lower dual-system administration.

Scenario F: Academic / Research Institution

Recommendation: QB Control (full replacement) — unless shakers or DoE are central. QB Control provides professional-grade control at accessible cost, multi-student browser access (no per-seat licensing), and modular hardware for curriculum flexibility. If high-throughput shaker screening or mature DoE tooling is central to the curriculum, retain EVE for that work and use QB Control for stirred-tank bioprocessing.

16. Competitive Positioning Strategy

Positioning Statement

QB Control is not trying to out-INFORS Infors EVE inside the INFORS ecosystem. QB Control is the vendor-neutral, turnkey alternative for everyone who doesn’t want to buy a software overlay plus a hardware family plus a Windows server to run a development lab. EVE is excellent when a lab is committed to INFORS bioreactors, needs mature DoE tooling, or runs large shaker arrays. For greenfield builds, mixed bioreactor estates, stainless-steel pilot cells with existing PLCs, and budget- or IT-constrained teams, QB Control delivers hardware and software as one co-engineered system — ~40 pre-built services, native multi-vendor sensors, a visual no-code recipe engine, built-in compliance scaffolding, perpetual licensing, and ~60–70% lower 5-year TCO.

Key Sales Arguments Against the EVE Path

EVE Pain Point	QB Control Advantage	Evidence
”EVE needs a Windows server back-end and a DBA”	QB Edge is self-contained; no Windows server, no database admin	$30K–$50K IT overhead avoided over 5 years
”Compliance features are behind the Premium tier”	Audit trail + RBAC built into all QB editions	No Premium-tier surcharge for governance
”EVE’s subscription never stops”	Perpetual license — buy once, use forever	$100K–$200K saved over 10 years
”Connecting a non-INFORS bioreactor is an OPC project”	Native OPC-UA + dedicated Connector; no license penalty	Hours, not weeks
”Changing a control strategy takes days”	Swap a service template in 5 minutes	~100× faster strategy changes
”We validated EVE as Category 5”	GAMP 5 Cat. 4, configuration-validated	50–70% validation reduction
”We’re tied to the INFORS hardware family”	Open sensors, open consumables, open protocols, MTP, PLC reuse	No vendor lock-in at any level
”We can’t access the system off-network easily”	Secure remote access with QR-code setup	Phone/tablet/PC, role-based

When NOT to Position Against Infors EVE

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

High-throughput incubator shaker screening (40–80 shakers) — EVE + INFORS incubators are the native fit; QB Control does not cover shakers
Mature, native DoE tooling as the center of their workflow — EVE’s DoE depth exceeds QB Control’s export-to-external-tools approach
Soft sensors (biomass/yield estimation) as a core requirement — not native in QB Control
A large, committed INFORS estate (20+ INFORS bioreactors, years of EVE recipes, regulatory approvals in production) — acknowledge sunk cost; position QB for new vessels or the next facility
Electronic signatures on an active IND today (before QB Control’s Q3 2026 release) — EVE Premium is the safer answer until then
A vessel ceiling approaching ~80 bioreactors in one installation — EVE’s higher ceiling fits large fleets

In these cases, position QB Control as complementary to EVE — handling new, multi-vendor, or stainless-steel lines while EVE continues to serve the INFORS fleet, shaker arrays, and DoE work.

17. Feature-by-Feature Matrix

#	Feature	Infors EVE	QB Control	QB Advantage	Notes
CORE CONTROL
1	Bioreactor control	★★★★★	★★★★		EVE: deep INFORS tuning; QB: PID-based services
2	Mixer/agitator control	★★★★	★★★★★	✅	QB native agitator modules (up to 6 vessels)
3	Pump control	★★★★	★★★★★	✅	QB: 4 pump types native + SmartPump OPC
4	Sampler control	★★★	★★★★★	✅	QB: native selector valve (24 positions)
5	Gas flow control	★★★★	★★★★		Both capable; QB native MFC
6	Temperature control	★★★★	★★★★		EVE on INFORS; QB: 2–42 °C native
7	Valve control	★★★	★★★★★	✅	QB: Set Valve State block + three-way valves
8	Scale/weight measurement	★★★	★★★★★	✅	QB: native multiscale (6 channels)
9	Foam detection	★★★★	★★★★★	✅	QB: patent-pending optical sensor
10	LED/light control	★★	★★★★★	✅	QB: native photobioreactor LED control
PARALLEL PROCESSING
11	Multi-device parallel	★★★★★	★★★★		EVE: up to ~80 bioreactors
12	Sequential campaign queuing	★★★	★★★★★	✅	QB: Pending queue + auto-stop (new)
13	Auto-generated P&ID per process	✗	★★★★★	✅	QB auto-generates; EVE setpoint dashboard
14	Process import/export + device mapping	★★	★★★★★	✅	QB: one-click replication + remap
15	Multi-user concurrent access	★★	★★★★★	✅	QB: any browser; EVE named/seat
RECIPE, BATCH & SERVICES
16	Recipe management	★★★★	★★★★		EVE: batch strategies; QB: visual no-code flow
17	Visual recipe designer	★★	★★★★★	✅	QB: drag-and-drop, no coding
18	Recipe versioning	★★★	★★★★★	✅	QB: Draft→Verified→Validated→Hold→Archived
19	Services Catalog	★★★	★★★★★	✅	QB: ~40 across 10 categories; EVE ~20 functions
20	Service Profiles (reusable params)	★★	★★★★★	✅	QB: grouped/atomic + portable import/export
21	Variables / Timer / Manual blocks	★★	★★★★★	✅	QB: unified block library (new)
22	Strategy switching speed	★★	★★★★★	✅	QB: swap service in minutes
23	Batch Board (execution tracking)	★★★★	★★★★★	✅	QB adds flow-diagram export
24	Pre-execution safety checklist	★★★	★★★★★	✅	QB: mandatory + Validator (system-enforced)
25	DoE integration	★★★★★	★★		EVE: mature DoE tooling
INTEGRATION
26	OPC UA	★★★	★★★★★	✅	QB: native + dedicated OPC UA Connector
27	REST API	★★★	★★★★★	✅	Both; QB native and broader
28	MQTT	✗	★★★★★	✅	QB native; EVE export/REST-oriented
29	SQL access	★★	★★★★★	✅	QB native JDBC/ODBC
30	LDAP/AD SSO	★★★	★★★★★	✅	QB native; EVE via Windows
31	MTP support	★★	★★★★	✅	QB supports (new); EVE not primary
32	Hamilton / Mettler Toledo sensors	★★★	★★★★★	✅	QB: direct via Modbus RS485, no INFORS vessel
33	PLC reuse (Wago/Siemens/Beckhoff)	★★	★★★★★	✅	QB: industrial-PC deployment (new)
COMPLIANCE
34	21 CFR Part 11	★★★★	★★★★	⚠️	EVE full on Premium; QB partial (no e-sigs yet)
35	GAMP 5 classification	Cat. 5	Cat. 4	✅	QB: lower validation burden
36	ISA-18.2 alarms	★★★	★★★★	✅	QB conformance; EVE basic/email
37	Audit trail	★★★	★★★★★	✅	QB all editions; EVE Premium only
38	Role-based access control	★★★	★★★★★	✅	QB all editions; EVE Premium only
39	Electronic signatures	★★★	★★	⚠️	EVE Premium/LIMS today; QB roadmap Q3 2026
40	Safe Position Logic (GMP)	★★★	★★★★★	✅	QB: built-in configurable feature
USABILITY & OPS
41	Setup time	★★★	★★★★★	✅	QB turnkey, days
42	Learning curve	★★★	★★★★★	✅	QB: no formal training needed
43	Windows/IT overhead	★★	★★★★★	✅	QB: no Windows back-end, no DBA
44	Client device flexibility	★★★	★★★★★	✅	QB: any browser; EVE Windows back-end
45	Remote access	★★★	★★★★★	✅	QB: secure VPN + QR setup (new)
46	Health monitoring dashboard	★★★	★★★★★	✅	QB: consolidated module/host health (new)
47	Multi-language UI	★★★★	★★		EVE multi-language; QB English (roadmap)
COST & LICENSING
48	Initial investment	★★	★★★★★	✅	50–67% lower (turnkey)
49	5-year TCO	★★	★★★★★	✅	~60–70% lower TCO
50	License model	★★★	★★★★★	✅	QB perpetual; EVE subscription/tiered
51	Incremental expansion cost	★★	★★★★★	✅	Fraction of cost
52	Vendor lock-in	★★	★★★★★	✅	QB: open ecosystem
ADVANCED & ECOSYSTEM
53	Incubator shaker support	★★★★★	❌		EVE exclusive
54	Soft sensors	★★★★★	❌		EVE exclusive
55	DoE design-and-analysis	★★★★★	★★		EVE: mature tooling
56	Vessel ceiling (~80)	★★★★★	★★★		EVE: large fleets
57	Installed base / regulatory history	★★★★★	★★★		EVE: 10+ years FDA/EMA

Summary Scores by Category

Category	Infors EVE Average	QB Control Average	Winner
Core Control	3.6	4.6	QB Control
Parallel Processing	3.4	4.6	QB Control
Recipe, Batch & Services	3.0	4.6	QB Control
Integration	2.6	4.8	QB Control
Compliance	3.3	4.3	QB Control
Usability & Ops	2.9	4.7	QB Control
Cost & Licensing	2.2	5.0	QB Control
Advanced & Ecosystem	4.6	2.2	Infors EVE

Overall: QB Control wins in 7 of 8 categories for the target lab/pilot/early-production market. With its unified recipe block library, sequential auto-stop campaigns, native MTP, secure remote access, Health Monitoring, vendor-neutral hardware, and the industrial-PC deployment path, QB Control’s lead in Recipe/Batch, Integration, Usability, and Cost is decisive. Infors EVE retains a clear lead in the Advanced & Ecosystem category — native incubator shaker support, mature DoE and soft-sensor tooling, a higher vessel ceiling, and a longer installed base — which keeps EVE the better fit for INFORS-committed labs, large shaker farms, and DoE-centric process development.

Recent QB Control Enhancements (current release)

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

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

Legal Notice & Disclaimer

Versions compared. This comparison is between QB Control (release 6.x, per the current QB Control release notes) and INFORS HT eve® — current commercially available release (INFORS HT does not publish a numeric public version). Feature statements in this document refer to these versions.

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

Trademarks. All trademarks, logos, and brand names are the property of their respective owners. All company, product, and service names used in this document are for identification and comparison purposes only, and use of these names, trademarks, and brands does not imply endorsement or affiliation. eve® and INFORS HT® are registered trademarks of INFORS AG. QB Control and QB Systems are brands of A4BEE Sp. z o.o.

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

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

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

Assumptions

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

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

Sources

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

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

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