QB Control vs Lucullus PIMS Comparison

At a glance

Dimension	QB Control	Lucullus PIMS
Software platform	◆ Browser-based (any modern browser)	Windows desktop client-server
Database	◆ Local on QB Edge, no external DB	Oracle (XE or full enterprise)
Hardware	20+ purpose-built PoE modules	Third-party bioreactors + controllers
Device integration	◆ Auto-discovery + OPC-UA connector	Custom driver development per device
Client install	◆ None (any browser)	Windows app + Oracle client
IT infrastructure	◆ QB Edge + PoE cabling	Windows Server, Oracle DB, drivers

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

Securecell’s Lucullus PIMS (Process Information Management System) is the bioprocess industry’s most established software-only data-integration and process-control layer — over 25 years of continuous development, deep multi-vendor connectivity, mature design-of-experiments (DoE) integration, sample and media management, and enterprise-scale data warehousing on an Oracle database. QB Control is a SCADA-class, browser-based platform purpose-built for liquid-handling bioprocessing, combining co-engineered hardware (QB Modules) and software with ~40 pre-built bioprocess services, a visual recipe engine, native sensors, and built-in compliance modules. It deploys both on QB Edge (benchtop QB Modules) and on a standard industrial PC driving stainless-steel, PLC-based systems via OPC-UA.

The two products solve different problems. Lucullus is a middleware data layer that sits on top of existing third-party bioreactors and controllers — its value is connecting to everything, centralizing the data, and enabling cross-experiment analysis. It owns no process hardware and depends on driver development for each new device. QB Control ships the bioprocess application and the hardware already built — turnkey from the bench, with an OPC-UA path that also lets it monitor and control third-party OPC-UA equipment. The comparison is most relevant in lab-to-pilot bioprocessing (150 mL – 50 L benchtop, plus stainless-steel pilot/production via PLC), where Lucullus’s infrastructure overhead becomes a burden and QB Control delivers a right-sized, unified alternative.

Key Finding

QB Control does not replace Lucullus PIMS in all scenarios. It replaces Lucullus in specific, high-value segments where Lucullus’s Oracle dependency, driver-development cycle, integrator reliance, and software-only architecture create friction. With the industrial-PC deployment path and the OPC-UA connector, QB Control’s addressable footprint extends from greenfield benchtop labs up into stainless-steel pilot cells and retrofitted legacy hardware. Lucullus retains a genuine lead in cross-experiment analytics, DoE, established multi-vendor breadth, and enterprise multi-site data harmonization. The sweet spot for QB Control as a Lucullus alternative is:

Scenario	QB Control Replaces Lucullus?	Value Driver
Greenfield lab (1–12 bioreactors)	✅ Full replacement	Unified hardware + software, days vs. weeks setup
Academic / teaching lab	✅ Full replacement	Zero IT overhead, no Oracle, browser UI
Small R&D lab (1–6 bioreactors)	✅ Strong replacement	Turnkey control, perpetual license, no DBA
Pilot scale (10–50 L, new build)	✅ Strong replacement	One vendor, lower TCO, native modules
Retrofit of OPC-UA-enabled bioreactors	✅ Strong replacement	OPC-UA connector controls Sartorius, etc.
Stainless-steel pilot cell with PLC	✅ Strong replacement (new)	Industrial-PC deployment + OPC-UA
Adding vessels to an existing Lucullus lab	⚠️ Partial / complementary	QB for new standalone vessels; Lucullus keeps data continuity
DoE-heavy process development	❌ Not a replacement	Lucullus native DoE integration required
Enterprise multi-site data harmonization	❌ Not a replacement	Centralized Oracle warehouse required

2. Platform Philosophy

Fundamental Architecture Difference

Dimension	Lucullus PIMS	QB Control
Product Category	Software-only PIMS / process-control layer	SCADA-class browser-based hardware+software platform
Design Philosophy	Connect to everything, centralize all data	Hardware and software designed as one system
Target Scale	Lab to enterprise (vendor-dependent)	Lab-to-pilot (150 mL – 50 L benchtop); stainless-steel pilot/production via PLC + OPC-UA
Approach to Hardware	None — connects to 3rd-party bioreactors via drivers	Own modular hardware (QB Modules) + open sensors; or existing PLCs (Wago/Siemens/Beckhoff)
Software Delivery	Windows desktop client-server application	Browser-based (any device, any OS)
Deployment Host	Windows / Windows Server + Oracle DB	QB Edge for benchtop or standard industrial PC for PLC-based stainless steel
Database	Oracle (XE standalone → full Oracle enterprise)	Embedded data store on the deployment host — no external DB
Configuration Model	Per-device driver + script/form-based recipes	Visual no-code flow + recipe designer
Deployment Time	Weeks (Oracle, drivers, integrator)	Days (plug-and-play / OPC-UA mapping)
Vendor Strategy	Vendor-agnostic via drivers (integrator-led)	Open ecosystem (no lock-in) + native modules
GAMP Classification	Category 5 (custom, device-specific drivers)	Category 4 (configurable software)

The “Universal Translator” Problem

Lucullus was born from a real need: unify data from heterogeneous bioprocess equipment so scientists can compare runs across vessels, scales, and vendors. Its philosophy — connect to everything, centralize all data, enable cross-experiment analysis — assumes the lab already owns bioreactors (Sartorius, Getinge/Applikon, Eppendorf, Infors, etc.) and needs a software layer to translate, monitor, and warehouse them. That makes Lucullus a powerful middleware platform, but it also makes every deployment dependent on:

An Oracle database (XE for standalone, full Oracle for enterprise) with the licensing and administration that implies
Custom driver development for each new device type (typically weeks per device)
Windows workstations and servers, OPC gateways, and corporate IT governance
A system integrator for setup, configuration, and validation

Lucullus is like a universal TV remote that can control any brand of TV — powerful, but it must be programmed for each new device, and it owns none of the hardware it commands. QB Control was designed with the opposite philosophy: hardware and software are one system. Every QB Module (pump, sensor, agitator, gas-flow controller, thermo unit, valve, scale) communicates natively with QB Control over PoE — no drivers to write, no Oracle to maintain, no integration project. And because QB Control also speaks OPC-UA (with a dedicated connector), it can reach beyond the QB ecosystem to monitor and control third-party OPC-UA equipment — controlling other brands when needed, while remaining turnkey for its own.

QB Control further provides centralized multi-processing: multiple processes run simultaneously from one host, each with its own auto-generated P&ID/HMI — no need to integrate data from separate controllers after the fact, which is precisely the problem Lucullus was built to solve.

3. Architecture & Hardware

Controller & Hardware Architecture

Component	Lucullus PIMS	QB Control
Software platform	Windows desktop application (client-server)	Browser-based (Chrome, Firefox, Edge, Safari)
Central host	Windows / Windows Server + Oracle DB	QB Edge (runs QB Control locally) or industrial PC for PLC-based stainless-steel systems
Database	Oracle (XE standalone → full Oracle enterprise)	Embedded data store on the host — no external DB required
Hardware dependency	Third-party bioreactors + controllers	QB Modules (own PoE devices); or existing PLCs via OPC-UA
Controller	Existing bioreactor controllers (Getinge i-Control / ez-Control / my-Control, Sartorius, etc.)	QB Edge or industrial PC
I/O architecture	OPC / serial drivers to external controllers	Power-over-Ethernet (one cable = power + data per module); or PLC I/O via OPC-UA
Device discovery	Manual driver development / commissioning per device	Auto-discovery (plug-and-play) for QB Modules; OPC-UA mapping for third-party
Workstation requirement	Windows client + Oracle client per seat	Any device with a browser
Deployment editions	Standalone (up to 8 bioreactors), Client-Server, Enterprise (multi-site)	Single QB Edge (expandable via QB Switch); or industrial PC for PLC systems
Power architecture	Multiple UPS units, separate circuits	PoE — single cable per module, no external supplies
Wiring	Network (Oracle ↔ workstation), RS232/RS485 to controllers, custom adapters	Single Ethernet cable per module; or existing PLC field wiring

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

Lucullus operates as software only and manufactures no process hardware. It connects to third-party bioreactor controllers, sensors, pumps, and analyzers through device-specific drivers — so every new device type requires Securecell (or the customer) to develop or commission a driver. QB Control supplies the hardware natively:

Function	Lucullus Approach	QB Control Approach
Pumps	3rd-party pumps via drivers (Ismatec, Cole-Parmer, etc.)	QB Pump (peristaltic 3-/4-roller, centrifugal) + QB Syringe Pump — native; SmartPump (OPC) for 3rd-party
Sensors	Hamilton / Mettler Toledo via vendor tools + drivers	QB Multisensor — up to 6 Hamilton / Mettler Toledo probes natively
Agitation	3rd-party agitators via controller drivers	QB Agitator, QB Multiagitator (2 or 6 vessels) — native
Temperature	3rd-party thermocontrollers via drivers	QB Thermo (heating/cooling, heating mats) — native
Gas Flow	3rd-party MFCs via drivers	QB Gasflow (dual mass-flow controllers) — native
Valves	3rd-party valves via controller drivers	QB Pinch Valve, QB Selector Valve (24 positions) — native
Scales	3rd-party scales via serial drivers	QB Multiscale (up to 6 scales) — native
Foam Detection	External, vendor-dependent	QB Foam Sensor — optical, non-contact
Lighting	Not part of the Lucullus ecosystem	QB Light (LED control for photobioreactors)
Pressure	3rd-party transmitters via drivers	QB Pressure Sensor (single-use IBP transducers)
Automated Sampling	Numera — Securecell’s companion sampling/sample-prep hardware	QB Syringe Pump + QB Selector Valve — native sampling service
Bioreactor vessels	3rd-party (any vendor)	QB Tanks (1 L, 3 L, custom to ~10 L); stainless-steel via PLC

Network & Infrastructure Requirements

Requirement	Lucullus PIMS	QB Control
Database administration	Oracle DBA required — licensing, backup/recovery, schema, query tuning	None — embedded data store, automatic backups
OS patching & updates	Monthly security patches, AV management across all client machines	Firmware updates via web UI (infrequent, non-disruptive)
OPC licensing & gateways	OPC server license + gateway maintenance + driver versioning	Native protocol support; no OPC-UA licensing
Network architecture	Corporate IT governance, VLANs, firewalls for DB access, VPN	Plug-and-play PoE switch + single Ethernet cable per module
IT staffing	Database admin (partial FTE) + systems admin + escalations	Minimal — device self-manages; browser access only
Backup & disaster recovery	Oracle DB backups, transaction logs, recovery testing	Scheduled/manual backup wizards + one-click restore
Remote monitoring	VPN tunneling, Windows RDP, firewall exceptions	Secure VPN with QR-code setup; HTTPS browser access
New device onboarding	Contact Securecell → custom driver development (weeks)	Auto-discovery in minutes; OPC-UA endpoint mapping in hours

Key insight: Lucullus was architected when “software + infrastructure” was a bundle — IT and database expertise were assumed. QB Control eliminates the infrastructure layer entirely, shifting the model from “hire a DBA and a system integrator” to “plug in a cable” — or, for stainless-steel pilots, “deploy on an industrial PC and point it at your existing PLC over OPC-UA.”

4. Parallel Processing

Side-by-Side Comparison

Capability	Lucullus PIMS	QB Control
Multi-bioreactor control	Up to 8 standalone; unlimited with Client-Server/Enterprise	Multiple parallel processes (license-dependent), centralized from one host
Centralized multi-processing	Aggregates from multiple separate controllers after the fact	✅ All processes run from one host — no inter-controller data integration
Dynamic P&ID per process	Manual HMI setup per controller/vessel	✅ Auto-generated plug-and-play P&ID/HMI per process
Independent recipes per vessel	Yes — different recipes across reactors	Yes — different recipes per process; parallel and sequential execution
Sequential campaign queuing	Process planning / reactor allocation	Sequential batch execution with Pending queue + per-batch auto-stop (new)
Cross-reactor data comparison	★★★★★ — Oracle-based cross-experiment analytics (core strength)	★★★ — per-process graphs with multi-signal overlay + CSV export
Scaling model	Add bioreactors from any vendor, connect via drivers	Add QB Modules via PoE / expand via QB Switch; 3rd-party via OPC-UA
Independent process control	Each reactor independently controlled	Each process independent with its own P&ID, services, and per-process P-Stop
Shared resource management	Scheduling tools for shared equipment	Process-level allocation via System and Process modules; conflict blockade

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 queue with a Pending status and chain with auto-stop conditions for 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 system integrator needed to set up parallel operations
Visual P&ID per process — auto-generated from configuration, not manually drawn; preserved 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 from different devices
Lower incremental cost — adding a parallel bioreactor = adding QB Modules + license expansion, not buying new controllers, Windows seats, or an integrator engagement

Where Lucullus Excels in Parallel Processing

Cross-experiment data analytics is unmatched: because everything lives in one Oracle database, scientists can query, compare, and overlay data from hundreds of past runs across vessel types and scales — its core value proposition
Practically unlimited vessel count at Client-Server/Enterprise editions
Shared-equipment scheduling across heterogeneous, multi-vendor fleets
Established multi-vendor parallel fleets already running on Lucullus drivers

5. Multi-Vendor Integration

Protocol Support Comparison

Protocol	Lucullus PIMS	QB Control
OPC UA	Server and client (data exchange)	Native — primary path for PLC/stainless-steel integration; dedicated OPC UA Connector with configurable mappings; full control of OPC-UA equipment
OPC DA / serial drivers	Native (RS232/RS485 + custom drivers)	Serial supported (QB Multiscale/Multisensor); legacy OPC DA not primary
Modbus	Via drivers	Native (TCP and RTU)
MQTT	Not a documented primary protocol	Native — IoT real-time streaming
REST API	Lucullus REST API (documented, Python library)	Native — modern web integrations
SQL (JDBC/ODBC)	Via Oracle (full SQL power)	Native — direct access to the embedded data store
LDAP/Active Directory	Basic user management	Native — SSO with corporate credentials, configurable search scope
MTP (Module Type Package)	Not documented	Supported (new) — plug-and-produce integration + MTP signal presentation in Graphs
SMTP (email)	Notifications (limited documentation)	Native — notification dispatch with SMTP config + delivery logs
PROFIBUS / PROFINET	Via controller drivers	Profibus supported; PLC protocols (Wago/Siemens/Beckhoff)
Secured external communication	Via VPN/DMZ/gateways	Supported — encrypted, protected external traffic; secure VPN

Sensor & Bioreactor Vendor Support Comparison

Vendor	Lucullus PIMS	QB Control
Sartorius / Getinge / Applikon / Eppendorf / Infors bioreactors	Native breadth — 25+ years of driver library across dozens of vendors	Via OPC-UA connector (control of OPC-UA-enabled equipment); native QB hardware for new vessels
Hamilton	Via vendor tools + drivers	Native — via QB Multisensor (DO, pH, conductivity, OD, CO₂, ORP); two-point/zero-point/slope calibration
Mettler Toledo	Via vendor tools + drivers	Native — ISM/Modbus via QB Multisensor
Levitronix	Custom integration	Native — flow meters via QB Multisensor
Numera (automated sampling)	Native — best-in-class sample prep (filtration, dilution)	QB Syringe Pump + QB Selector Valve — native alternative

Integration Philosophy Difference

Lucullus: “We are the universal data and control layer. Bring any bioreactor from any vendor; we connect it via a driver, monitor and control it, and warehouse all of its data in Oracle for cross-experiment analysis. New device types require a driver, built by us or commissioned through us.”

QB Control: “We provide both the control platform AND the hardware modules. Our modules natively connect Hamilton, Mettler Toledo, and Levitronix sensors with no drivers. For third-party bioreactors and PLCs, we offer a dedicated OPC-UA connector, plus Modbus, MQTT, REST API, SQL, and MTP — and we deploy on your existing PLCs for stainless-steel systems. No Oracle, no per-device driver project, no integrator.”

QB Control’s Integration Advantage

Native sensor support — Hamilton and Mettler Toledo probes connect directly to QB Multisensor. No vendor middleware, no per-device drivers
Modern protocols — MQTT, REST API, and SQL are native. Streaming bioreactor data to a cloud lake is a broker configuration, not a custom ETL project
OPC UA Connector — a dedicated module bridges OPC-UA equipment (e.g., Sartorius bioreactors) into QB Control with configurable mappings — full control, not just data exchange — making QB Control a modern retrofit platform for legacy hardware
MTP support (new) — plug-and-produce modular integration
Auto-discovery vs. manual driver commissioning — plug in a QB Module and it appears in inventory automatically

Lucullus’s Integration Advantage

Driver-library breadth — 25+ years of connectors for Sartorius, Getinge/Applikon, Eppendorf, Infors, and dozens more, including non-OPC legacy equipment QB cannot reach over OPC-UA
Mature Getinge/Applikon partnership (10+ years) with deeply tested integrations
Extensive analytical-device support — offline/online analyzers, DSP devices, incubators
Numera + Amphora — purpose-built automated sampling, sample prep, and gravimetric multi-feed hardware
Proven at production and enterprise scale with complex, heterogeneous, multi-vendor installations

6. Software Module Comparison

Module-by-Module Mapping

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

Capability Area	Lucullus Component	QB Control Module	Comparison
Device Management	Device management + driver setup	Inventory (auto-discovery, device status, configuration import/export, licensing)	QB simpler & faster (no drivers)
System Configuration	System configuration	System (visual resource allocation, search, bulk add/remove, history to CSV)	QB no-code, visual
Process Configuration	Process planning + reactor allocation	Process (visual binding, versioning, duplicate, live connection status, guided import/export)	QB faster; Lucullus adds DoE planning
Process Visualization	Process visualization (manual HMI screens)	P&ID (auto-generated, drag-and-drop, recipe execution from diagram, P-Stop/E-Stop)	QB auto-generates; Lucullus manual
Batch Management	Recipe management with event-based control	Recipe (Designer / Batch / Executions Boards)	QB visual designer with Services
Services Catalog	No equivalent (per-device configuration)	Services (~40 templates across 10 categories, load & execute in minutes)	QB unique advantage
Service Profiles	No equivalent	Service Profiles (reusable grouped/atomic parameter templates, portable import/export)	QB unique advantage
Alarm Management	Alarm management	Alarms (ISA-18.2 conformance, watchlist, in-app global notifications)	QB explicitly ISA-18.2
Data Visualization	Data visualization + trending	Graphs (live + history, multi-axis, annotations, MTP signals, export)	Lucullus stronger cross-experiment; QB per-process real-time
Reporting	Automatic batch report generation	Reports (automated + manual, PDF/DOCX, recipe-execution & service-history sections)	Comparable
Batch Tracking	Batch execution tracking	Runs (per-process, batch ID, user tracking, report linkage)	Comparable
Calibration	Device-vendor tools (not a core module)	Calibration (status tracking, Next Due Dates, Hamilton/pump methods)	QB integrated; Lucullus external
Audit Trail	Audit trail via Oracle DB	Audit Trail (21 CFR Part 11 conformance, cross-module, exportable CSV)	Both strong; QB purpose-built module
Access Control	User management	Users & Roles (RBAC, granular per-module permissions, LDAP/AD)	QB more granular & modern
Notifications	Notifications (limited documentation)	Notifications (in-app center, email/SMTP, per-user preferences, recipe-step alerts, logs)	QB richer out-of-box
Backup	Database backup (Oracle utilities)	Backup, Export & Archive (scheduled/manual wizards, one-click restore, integrity verification)	QB purpose-built; Lucullus relies on DBA tools
License Management	License management	License (feature/device/system/time-based, online/offline, host-bound, license guards)	QB more flexible
Remote Access	VPN + Windows RDP	Remote Access (secure VPN, QR-code setup, phone/tablet/PC, role-based) — new	QB simpler, multi-device
Health Monitoring	Diagnostics across tools	Health Monitoring (system health dashboard, per-module status, drill-down) — new	QB consolidated, always-on
DoE Integration	Native 3rd-party DoE integration	❌ Not available (export via REST/CSV)	Lucullus wins
Sample Management	Barcode tracking, at-line analyzer retrieval	◐ Manual via Inventory	Lucullus wins
Media Management	Automated media creation, raw-material tracking	◐ Manual via Inventory	Lucullus wins
Cross-Experiment Analytics	Oracle-powered multi-run comparison	◐ Per-process graphs + CSV export	Lucullus wins

7. Services Catalog & Rapid Deployment

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

One of QB Control’s most powerful advantages over Lucullus 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, Set Sparger Volume & Mass Flow)
Continuous Services — run until explicitly stopped (e.g., Set Agitator Speed, Temperature Control by TCU, pH Control by Base & CO₂)

Lucullus, by contrast, provides process control but has no equivalent template library that works out of the box — each control strategy must be configured per device based on the connected controller’s capabilities and Lucullus drivers. Event-based control is possible but requires configuring triggers, conditions, and actions specific to the connected hardware.

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 let users save standardized parameter configurations as reusable templates with 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 — so an operator can switch strategies or adjust parameters in minutes without re-engineering control logic.

Deployment Time Comparison

Activity	Lucullus PIMS	QB Control
Install software	Hours (Windows, Oracle, client)	0 — browser-based, pre-installed on host
Connect first bioreactor (QB hardware)	Days–weeks (driver development/verification)	Minutes (plug PoE cable, auto-discovery)
Connect third-party bioreactor (OPC-UA)	Days–weeks (driver development)	Hours (configure OPC-UA connector endpoint)
Configure first control loop	Hours (driver + recipe + alarm setup)	Minutes (select service template, apply profile)
Switch pH-by-CO₂ → pH-by-acid	Reconfigure recipe/control logic	Select a different service template — minutes
Add a second identical vessel	Hours (duplicate config, verify)	Minutes (plug in modules, assign to process)
Go from zero to running experiment	Weeks (typical, with integrator support)	Hours to days (self-service)

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). Lucullus provides recipe management with event-based triggers, but its model is form/script-based and tied to per-device driver configuration.

8.1 Designer Board & the Unified Block Library

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

Block	Category	Function
Start Service	Service Control	Single configurable block; 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
Start / Stop / End	Standard	Execution control endpoints for the flow

Authoring productivity: copy/paste of blocks, signal filtering for cleaner input selection, undo/redo, diagram export (image), and recipe import/export across installations.

8.2 Recipe Lifecycle & Governance

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. Recipes can be duplicated for rapid variation, and the designer flags inactive recipes that should not be started as-is. Lucullus does not document an equivalent color-coded state model.

8.3 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
Single recipe → batch and multiple recipes → batch (user-defined sequence or parallel), all recorded with full traceability

8.4 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.5 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.6 Recipe Engine vs. Lucullus — Detailed Comparison

Capability	Lucullus PIMS	QB Control Recipe Engine
Workflow design	Form/script-based with event triggers	Visual drag-and-drop Designer Board (no coding)
Recipe versioning	Not documented in detail	Draft → Verified → Validated → Hold → Archived
Recipe import/export	✓	✓ — full recipe import/export across installations
Process import/export	Limited	✓ — complete process config (devices, services, recipes, P&ID) + device mapping
Conditional logic	Event triggers on sensor readings	Conditional blocks with AND/OR on real-time data
Variables & math	Configurable per controller	Variable / Update Variables (increase/decrease/multiply/divide)
Timers	Event-based scheduling	Timer block (start/stop/pause/resume)
Human-in-the-loop	Configurable prompts	Manual Operation block
Event-based control	★★★★★ — sophisticated triggers + Numera integration	★★★★ — Conditional, sensor-based services
DoE integration	★★★★★ — native 3rd-party DoE	★★ — export via REST/CSV
Pre-execution safety	Not documented as system-enforced	Mandatory checklist + Validator (system-enforced)
Sequential campaigns	Process planning / reactor allocation	Sequential batches with Pending queue + auto-stop
Parallel recipe execution	✓	✓ — user chooses sequence or parallel mode
Diagram export	Not standard	Export as image / PNG for compliance docs
Time to create a recipe	Hours to days	Minutes to hours (visual, no-code)

9. Regulatory Compliance

Standard	Lucullus PIMS	QB Control	Notes
FDA 21 CFR Part 11	Supported — electronic records, audit trail via Oracle	⚠️ Partial conformance	Lucullus supports e-records and e-signatures for regulated environments. QB: electronic records, audit trails, access control, RBAC, data integrity today — electronic signatures not yet covered
EU Annex 11	Supported (implied by pharma installed base)	✅ Compliance support	Both provide computerized-system validation capabilities
GAMP 5	Category 5 (custom, device-specific drivers)	Category 4 (configurable)	QB Control has lower validation burden — no custom code to validate
ISA-18.2 (Alarms)	Not explicitly documented	✅ Conformance	QB supports suppressed, out-of-service, acknowledgement workflows
ISA-88 (Batch)	Partial — recipe-based batch control	⚠️ Follows batch concepts; not formally certified	Comparable at lab/pilot scale
ALCOA+ (Data Integrity)	Oracle structured, traceable storage	✅ Full implementation	Both provide ALCOA+ data integrity
Electronic Signatures	Supported (for regulated environments)	◐ On roadmap (Q3 2026 — not in current version)	Lucullus leads today; QB planned
Audit Trail	Via Oracle database logging	✅ Purpose-built module, cross-module, exportable CSV	Both comprehensive; QB granular per-module
Role-Based Access Control	User management with access control	✅ Granular RBAC with per-module, per-action permissions, LDAP/AD	QB more granular
Safe Position Logic (GMP)	Via controller/interlock engineering	✅ Built-in — define safe actuator states after restart/power cycle	QB has a dedicated, configurable feature
CE Marking	System-level (via 3rd-party hardware)	✅ Per QB Module (EMC + Low Voltage Directive)	Each module ships its own Declaration of Conformity

Compliance Value for QB Control

GAMP 5 Category 4 vs. Category 5 is the critical differentiator. Lucullus’s device-specific drivers constitute custom code (Category 5) that must be validated individually for every unique hardware combination, whereas QB Control is configured through UI settings, service templates, and service profiles — the same validated software runs on every host. The result is roughly 50–70% less validation documentation than a Lucullus installation with multiple device drivers, with faster IQ/OQ/PQ (weeks vs. months), lower CSV cost, and simpler change management (configuration, not code; firmware updates do not trigger re-validation).

Honest Compliance Caveat

QB Control’s 21 CFR Part 11 conformance is partial: it delivers electronic records, audit trails, access control, RBAC, and data integrity today, but electronic signatures are not yet implemented (roadmapped for Q3 2026). Lucullus, deployed in regulated pharma environments for years, supports electronic signatures today. For workflows that require digital signatures on an active IND now, Lucullus (or another e-signature-capable system) remains 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	Lucullus PIMS (Estimated)	QB Control	Savings with QB
Software license	~$30,000–80,000+ (edition & bioreactor count)	Included with QB hardware (perpetual license)	Significant
Oracle database license	$0 (XE standalone) → $10,000–50,000+ (full Oracle)	$0 — no external database	100%
Bioreactor hardware	Third-party — $30,000–100,000+ per bioreactor	QB Modules included in system price	Significant
Driver development	$5,000–20,000 per device type (custom drivers)	$0 — QB Modules auto-discover	100%
System integrator	$10,000–50,000+ (install, config, validation)	$0 — self-service plug-and-play	100%
Windows Server license	$500–2,000	$0 — runs its own OS / industrial PC	100%
Annual maintenance/support	~15–25% of license cost per year	Optional tiered support (Basic/Standard/Premium)	Significant
Training	$5,000–15,000 (formal Securecell courses)	QB Systems Online Portal + docs (self-paced, included)	80–90%
Validation (GAMP 5)	Category 5 — extensive IQ/OQ/PQ	Category 4 — reduced scope	50–70%

QB Control System Pricing (Reference Figures, USD)

Configuration	QB Control Price
Entry-level system (1 bioreactor)	$15,000–25,000
4-bioreactor lab setup	$60,000–85,000
6-bioreactor lab setup	~$100,000 (hardware)
Pilot setup (8–12 bioreactors)	$150,000–250,000
System integrator cost	$0 (self-setup, plug-and-play)
Workstation hardware	$0 (any device with a browser)

Total Cost of Ownership (5-Year Projection)

Scenario: 4-bioreactor lab

Cost Component	Lucullus PIMS	QB Control
Software license	$50,000	$0 (included)
Oracle DB (standalone XE)	$0	$0
Bioreactor hardware (4 vessels + controllers)	$120,000–200,000	$60,000–85,000 (all-inclusive)
Driver integration	$15,000	$0
System integrator / installation	$20,000	$0
Windows Server + workstations	$3,000	$0
5-year maintenance (software)	$37,500 (~15%/yr)	$15,000–25,000 (support tier)
5-year database administration	$10,000	$0
Training	$10,000	$0 (online portal)
5-Year Total	$265,500–345,500	$75,000–110,000
		~58–78% lower TCO

Note: Lucullus pricing is estimated based on typical enterprise bioprocess software costs. Securecell does not publish list prices; actual costs vary by configuration, region, and negotiation. QB Control prices are reference figures based on past quotations and do not constitute a specific priced offer.

Licensing Model Comparison

Aspect	Lucullus PIMS	QB Control
Model	Annual or subscription (typical enterprise software) + Oracle	Perpetual — feature-, device-, system/process-, and time-based dimensions
License Type	Recurring renewal	Perpetual — buy once; no recurring license fees
Per-bioreactor licensing	Commonly by bioreactor count or edition tier	Device- and feature-based
Support	Annual maintenance (% of license)	Paid separately — tiered (Basic/Standard/Premium), client’s choice
Enforcement	License management + Oracle	Software license bound to the deployment host; license-aware UI and guards
Upgrade path	Paid version upgrades	Software updates via the management interface
Lock-in	Oracle + Windows + driver dependency	Not tied to a specific hardware vendor

Licensing Model — Key Client Value

No recurring license fees — the perpetual license does not expire, eliminating Lucullus’s annual renewal burden
No Oracle tax — zero database licensing and zero DBA labor
Paid support is optional and tiered — no forced bundling
Predictable budgeting — one-time license + optional support
No “license hostage” risk — a lapsed contract never locks you out of your own system

11. Industry Fit Analysis

Biotech (Cell Culture, Fermentation)

Criterion	Lucullus PIMS	QB Control	Winner
Multi-vendor bioreactor support	★★★★★	★★★★	Lucullus
Turnkey lab automation	★★★	★★★★★	QB Control
Cross-experiment data analytics	★★★★★	★★★	Lucullus
Time to first experiment	★★★	★★★★★	QB Control
Automated sampling	★★★★★ (Numera)	★★★★ (QB Syringe + Selector Valve)	Lucullus
Cost per bioreactor setup	★★★	★★★★★	QB Control

Pharmaceuticals (Process Development)

Criterion	Lucullus PIMS	QB Control	Winner
DoE integration	★★★★★	★★	Lucullus
Regulatory validation effort	★★★ (GAMP 5)	★★★★★ (GAMP 4)	QB Control
Data integrity for submissions	★★★★★	★★★★	Lucullus
Electronic signatures today	★★★★	★★	Lucullus
Recipe management flexibility	★★★★	★★★★★	QB Control
Enterprise scalability	★★★★★	★★	Lucullus

Cosmetics & Food/Beverage

Criterion	Lucullus PIMS	QB Control	Winner
Small batch flexibility	★★★	★★★★★	QB Control
Setup simplicity	★★	★★★★★	QB Control
Hardware cost	★★	★★★★★	QB Control
IT overhead	★★	★★★★★	QB Control

Academic / Research

Criterion	Lucullus PIMS	QB Control	Winner
Budget compatibility	★★	★★★★★	QB Control
Student ease of use	★★★	★★★★★	QB Control
Data analysis tools	★★★★★	★★★	Lucullus
No IT department needed	★★	★★★★★	QB Control
Teaching lab scalability	★★★	★★★★★	QB Control

Industry Decision Guide

Biotech R&D / Process Development: Lucullus preferred IF DoE and cross-experiment analytics are the #1 priority; QB preferred IF rapid setup, compliance burden, and unified hardware control matter more.
CDMOs: QB wins for dedicated client lines with standardized vessels (fast changeover, perpetual licensing, no Oracle admin); Lucullus wins where vendor-agnostic breadth across many client bioreactors is essential.
Academic Research: QB wins — no IT department, plug-and-play teaching labs.
Cosmetics & Fine Chemicals: QB wins — small batches, simple deployment, cost-effective.
GMP Scale-Up: Lucullus can complement QB — Lucullus for historical data aggregation and DoE, QB for real-time control and stainless-steel pilot cells via PLC.

12. What QB Control Can Replace

Full Replacement Scenarios

QB Control can fully replace Lucullus PIMS when:

New greenfield lab — building from scratch with no legacy equipment. Value: unified hardware + software, days vs. weeks setup, no Oracle, no integrator.
Small R&D lab (1–6 bioreactors) — where Lucullus’s analytics breadth is not the priority. Value: turnkey control, perpetual license, zero DBA.
Academic / teaching lab — budget-sensitive, simplicity over analytical depth. Value: browser UI, no IT overhead, modular hardware.
Pilot facility with standardized vessels — all vessels on QB hardware. Value: one vendor, lower TCO, native sensors.
Startup biotech — rapid setup, minimal IT, maximum operational speed. Value: unbox and run.
Lab with retrofittable OPC-UA equipment — Sartorius and other OPC-UA bioreactors. Value: QB’s OPC-UA connector controls third-party hardware as a modern replacement control platform.
Stainless-steel pilot cell with an existing PLC (new) — Value: deploy QB Control on an industrial PC and integrate the PLC over OPC-UA, reusing field hardware.

Partial Replacement Scenarios

QB Control can replace specific aspects while Lucullus handles others:

New vessel additions — run new vessels on QB Control while legacy vessels remain on Lucullus
Satellite labs — QB Control for smaller satellite operations, Lucullus for the main facility
Real-time control layer — QB handles SCADA control while Lucullus retains historical data warehousing and DoE
Prototyping / rapid iteration — QB for early-stage work, transfer to Lucullus for formal data studies

Not a Replacement For

QB Control is not designed to replace Lucullus PIMS in:

Enterprise multi-site deployments — where a centralized Oracle data warehouse is essential
Existing installations with dozens of drivers — where Lucullus’s vendor integration library (including non-OPC equipment) is already established
DoE-heavy process development — where Lucullus’s native DoE tooling provides irreplaceable value
Numera-dependent workflows — where Securecell’s automated sampling/sample-prep hardware is deeply integrated
Cross-experiment analytics at scale — where unlimited Oracle SQL querying across hundreds of historical runs is core

13. Where QB Control Creates Superior Value

13.1 Value Summary

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

No external database dependency — an embedded data store on the host replaces Lucullus’s Oracle requirement, eliminating DB licensing, DBA labor, and database-failure risk (§3).
Unified hardware + software, single vendor — QB Systems builds the host, the modular devices, and all software, so one vendor owns the whole stack and the support for it (§3).
Unified SCADA control + process data in one platform — real-time control and batch data run on the same host, versus Lucullus being a data/PIMS layer on top of separate controllers (§6).
No driver development — QB Modules auto-discover natively and the OPC-UA connector monitors and controls third-party equipment, with no per-device drivers, OPC licensing, or gateways (§5).
Zero-integrator self-service — unbox, connect PoE, auto-discover, and run from any browser; perpetual licensing with no Oracle tax or vendor lock-in (§7, §10).
Modern, open integration and right-sized governance — native REST, MQTT, SQL, MTP, and OPC-UA, plus GAMP 5 Category 4 (~50–70% less validation), P-Stop/E-Stop, Safe Position Logic, and a mandatory pre-execution checklist + Validator (§5, §9).

14. Gaps & Limitations

Lucullus Capabilities Not Available (or Weaker) in QB Control

Capability	Lucullus PIMS	QB Control	Impact
Cross-experiment analytics	Oracle-powered multi-run comparison/overlay across hundreds of runs	Per-process graphs + CSV export	High
Design of Experiments (DoE)	Native 3rd-party DoE integration	Export via REST/CSV to external tools	High
Multi-vendor breadth (non-OPC)	25+ years of drivers, including legacy non-OPC equipment	OPC-UA connector reaches OPC-UA devices only	High
Enterprise multi-site	Centralized Oracle data harmonization across sites	Single-site (networkable)	High
Numera automated sampling	Best-in-class sample prep (filtration, dilution)	Native alternative (Syringe Pump + Selector Valve)	Medium
Amphora multi-feed	Dedicated gravimetric single/multi-feed station	QB Multiscale + QB Pump (native alternative)	Medium
Media management	Automated media creation + raw-material tracking	Manual via Inventory	Medium
Sample management	Barcode tracking + at-line analyzer retrieval	Manual via Inventory	Medium
Electronic signatures	Supported today	On roadmap (Q3 2026)	High for regulated production today
Established installed base	25+ years, deployed at enterprise scale	Newer, lab-to-pilot focus	Medium

Honest Assessment of QB Control Limitations

Cross-experiment analytics depth — Lucullus’s Oracle backbone enables unlimited querying and overlay across hundreds of historical runs; QB exports data for external analysis but is not a data-warehouse platform
No native DoE — design-of-experiments planning is not a QB Control feature; data must be exported to external DoE tools
Multi-vendor breadth — QB reaches third-party hardware via OPC-UA; legacy non-OPC equipment still needs Lucullus drivers
No enterprise multi-site warehouse — QB is single-site (networkable), not a global data-harmonization layer
No electronic signatures yet — 21 CFR Part 11 conformance is partial until the Q3 2026 release
Media / sample management — automated media creation and barcode-based sample lifecycle management are Lucullus-only workflows
Liquid-handling focus — QB Control does not address gas-phase, solid-phase, or complex hybrid processes

For a lab that already runs Lucullus with Numera and 10+ multi-vendor bioreactors, switching wholesale to QB Control would mean replacing process hardware — an unrealistic proposition. Lucullus’s strength is being the software backbone for heterogeneous, established labs. QB Control wins when starting fresh, when cost and IT simplicity matter, when a unified platform is the goal, or when retrofitting OPC-UA-enabled hardware.

15. Migration & Replacement Scenarios

Scenario A: Greenfield Lab (New Biotech Startup)

Recommendation: QB Control. New company, no legacy equipment, 4–8 bioreactors for cell-culture process development. Single order from QB Systems (everything included), $0 software/Oracle add-on, plug-and-play setup in days vs. weeks, ~60–70% lower total investment than a multi-vendor Lucullus build. No migration, no legacy.

Scenario B: Lab Expansion (Existing Lucullus Customer)

Recommendation: QB Control in parallel for new vessels. A pharma R&D lab runs Lucullus on 6 Applikon bioreactors and wants 4 more for a new project. Add QB Control systems (plug-and-play, perpetual license, $60K–85K hardware) for the independent new project rather than buying more controllers and extending the Oracle schema. Keep Lucullus for the existing fleet’s data continuity; export QB data via REST API/CSV where aggregation is needed. Best if the new project is independent and budget-conscious.

Scenario C: Academic Teaching Lab

Recommendation: QB Control (full replacement). A university needs 6 benchtop bioreactors for teaching. Lucullus’s minimum viable setup carries Oracle, Windows Server, and DBA/network admin burden; QB Control runs in any browser on any laptop with no IT support, intuitive auto-generated P&IDs, and firmware-only maintenance — at materially lower cost and a gentler learning curve for students.

Scenario D: Retrofit of OPC-UA-Enabled Bioreactors

Recommendation: QB Control via the OPC-UA connector. A lab has Sartorius (or other OPC-UA) bioreactors with dated control interfaces. Deploy QB Control and use the OPC-UA connector to monitor and control the existing equipment, gaining a modern browser UI, Services Catalog, centralized multi-processing, and built-in compliance modules — without replacing working hardware or commissioning Lucullus drivers.

Scenario E: Stainless-Steel Pilot Cell with an Existing PLC (new)

Recommendation: QB Control on an industrial PC. Deploy QB Control on an industrial PC, integrate the existing PLC (Wago/Siemens/Beckhoff) over OPC-UA via the OPC UA Connector, and keep the field instruments. Value: SCADA-class supervisory control and recipes without Oracle, driver development, or integrator re-engineering — and without a software-only PIMS layer bolted on top.

Scenario F: CDMO (Contract Development & Manufacturing)

Recommendation: mixed. For dedicated client lines with standardized vessels, QB Control wins — rapid setup/teardown, process import/export + device mapping for fast replication, perpetual licensing, no Oracle admin between campaigns. Where the CDMO must connect to many clients’ different (and sometimes non-OPC) bioreactors and harmonize all data centrally, Lucullus’s vendor-agnostic breadth is the better fit — and the two can coexist.

Coexistence Architecture

QB Control and Lucullus can coexist in a hybrid architecture:

QB handles real-time bioreactor control — SCADA layer: monitoring, recipe execution, setpoint management, multi-process orchestration
Lucullus aggregates data from QB + other sources — PIMS layer: historical warehousing, cross-experiment analytics, DoE-tool integration via REST API or OPC-UA
Realistic hybrid where QB replaces Lucullus’s control functions while Lucullus retains data warehousing and advanced analytics

Customers can migrate incrementally: run QB for new processes, stream data to Lucullus for aggregation, and eventually retire Lucullus’s control layer while preserving its data repository.

Migration Risk Assessment

Risk Factor	Impact	Mitigation
Historical data loss	High — Oracle DB not directly portable	Export via Lucullus REST API or Oracle dump before migration; archive on shared storage
Driver / OPC incompatibility	Medium — existing OPC configs won’t transfer	QB auto-discovers modules; OPC-UA enables integration with third-party legacy bioreactors
Staff retraining	Low — QB browser UI simpler than Lucullus	1–2 day QB training vs. longer Lucullus onboarding; self-paced QB Systems Online Portal
Recipe re-implementation	Medium — Lucullus recipes must be rebuilt	QB Services Catalog provides ~40 pre-built strategies; most logic recreated visually via drag-and-drop
Regulatory re-validation	Medium — new system requires IQ/OQ/PQ	GAMP Category 4 reduces effort 50–70% vs. Lucullus Category 5

16. Competitive Positioning Strategy

Positioning Statement

QB Control is not trying to be Lucullus. Lucullus PIMS is the industry’s most established bioprocess data-integration layer — a universal translator for every bioreactor language, with deep cross-experiment analytics and DoE. But that translation layer comes at a cost: Oracle databases, Windows servers, custom drivers, and system integrators that add weeks and hundreds of thousands of dollars to every deployment. When you are building a new lab, modernizing legacy equipment, or expanding with standardized vessels, you do not need a universal translator — you need hardware and software that speak the same language natively. QB Control delivers a unified platform with ~40 pre-built services, plug-and-play deployment, an OPC-UA connector for existing equipment, an industrial-PC path for stainless-steel PLC systems, 50–70% less validation effort, and 58–78% lower total cost.

Key Sales Arguments Against Lucullus

Lucullus Pain Point	QB Control Advantage	Evidence
”Every new device needs a driver — weeks of work”	Plug-and-play auto-discovery; OPC-UA for third-party	Minutes vs. weeks
”Oracle DBA and licensing cost us every year”	Embedded data store — zero DBA, zero DB licensing	No Oracle tax
”We pay an integrator for every change”	Self-service — visual no-code recipe designer + Services Catalog	$0 integrator
”Validation took months under Category 5”	GAMP 5 Category 4	50–70% less validation
”Control and data live in two different systems”	Unified SCADA + PIMS on one host	Single pane of glass
”Switching a control strategy means reconfiguring controllers”	Swap a service template	Minutes, not days
”Our Sartorius bioreactors have a dated interface”	OPC-UA connector controls them as a modern retrofit	No new hardware
”We have a stainless-steel pilot with a PLC”	Industrial-PC deployment over OPC-UA (new)	Reuse field hardware
”License renewals and upgrades keep escalating”	Perpetual license — buy once	No recurring fees

When NOT to Position Against Lucullus PIMS

Do not propose QB Control as a replacement for Lucullus when the client needs:

50+ bioreactors from multiple vendors already on Lucullus — switching cost is prohibitive; position QB for new standalone vessels only
Enterprise multi-site data harmonization — Lucullus Enterprise with a centralized Oracle warehouse is the right tool
DoE-driven process development as the core workflow — Lucullus’s native DoE integration is genuinely superior
Cross-experiment analytics across hundreds of historical runs — Oracle SQL querying is Lucullus’s core strength
Numera automated sampling deeply embedded — replacing Numera with QB sampling may not be acceptable
Electronic signatures on an active IND today — defer until QB Control’s Q3 2026 e-signature release
Connection to legacy non-OPC multi-vendor hardware — Lucullus’s driver breadth covers what QB’s OPC-UA reach cannot

In these cases, position QB Control as complementary to Lucullus — QB for real-time control and new/stainless-steel cells, Lucullus for data warehousing, DoE, and enterprise analytics — bridged over OPC-UA/REST.

17. Feature-by-Feature Matrix

#	Feature	Lucullus PIMS	QB Control	QB Advantage	Notes
CORE CONTROL
1	Real-time process control	◐ (data layer; control via controllers)	★★★★★	✅	QB: unified SCADA + PIMS
2	Mixer/agitator control	★★★★ (via controller)	★★★★★	✅	QB native agitator modules (up to 6 vessels)
3	Pump control	★★★★ (via controller)	★★★★★	✅	QB: 4 pump types native + SmartPump OPC
4	Sampler control	★★★★★ (Numera)	★★★★		Numera: sample prep, filtration, dilution
5	Gas flow control	★★★★ (via controller)	★★★★★	✅	QB: native mass flow controller
6	Temperature control	★★★★ (via controller)	★★★★★	✅	QB Thermo + PID service
7	pH control	★★★★ (via controller)	★★★★★	✅	QB: CO₂, acid, or base+acid options
8	Dissolved oxygen control	★★★★ (via controller)	★★★★		Comparable (QB Gasflow + Multisensor)
9	Scale/weight measurement	★★★★ (via controller)	★★★★★	✅	QB: native multiscale (6 channels)
10	Foam detection	★★★★ (via controller)	★★★★★	✅	QB: native optical sensor
11	LED/light control	✗	★★★★★	✅	QB: native photobioreactor lighting
PARALLEL PROCESSING
12	Multi-bioreactor parallel	★★★★★	★★★★		Lucullus: practically unlimited at Enterprise
13	Centralized multi-processing	★★ (aggregates controllers)	★★★★★	✅	QB: all processes on one host
14	Sequential campaign queuing	★★★★	★★★★		QB: Pending queue + auto-stop (new)
15	Auto-generated P&ID per process	★★ (manual HMI)	★★★★★	✅	QB auto-generates; Lucullus manual
16	Process import/export + device mapping	★★★	★★★★★	✅	QB: one-click replication + remap
17	Multi-user concurrent access	★★★	★★★★★	✅	QB: any browser; Lucullus: licensed seats
RECIPE, BATCH & SERVICES
18	Recipe management	★★★★	★★★★★	✅	Lucullus event-based; QB visual
19	Visual drag-and-drop designer	★★★	★★★★★	✅	QB: no-code DAG-style flow
20	Recipe versioning	★★★	★★★★★	✅	QB: Draft→Verified→Validated→Hold→Archived
21	Services Catalog	✗	★★★★★	✅	QB: ~40 services across 10 categories; Lucullus: none
22	Service Profiles (reusable params)	✗	★★★★★	✅	QB: grouped/atomic + portable import/export
23	Variables / Timer / Manual blocks	★★★	★★★★★	✅	QB: unified block library (new)
24	Strategy switching speed	★★	★★★★★	✅	QB: swap service in minutes
25	Recipe import/export	★★★★	★★★★★	✅	QB: cross-installation sharing
26	Process import/export	★★★	★★★★★	✅	QB: complete process config + device mapping
27	Pre-execution safety checklist	★★★	★★★★★	✅	QB: mandatory + Validator (system-enforced)
28	Batch/Executions tracking	★★★★	★★★★★	✅	QB: dedicated Batch + Executions Boards
29	Event-based control	★★★★★	★★★★		Lucullus: sophisticated triggers + Numera
DATA MANAGEMENT & ANALYTICS
30	Centralized database	★★★★★ (Oracle)	★★★ (embedded data store)		Lucullus: enterprise-grade warehouse
31	Cross-experiment analytics	★★★★★	★★		Lucullus: core differentiator
32	Real-time process graphs	★★★★	★★★★★	✅	QB: per-process live signals
33	Historical data views	★★★★★	★★★★		Lucullus: Oracle-powered queries
34	Data export (CSV, PDF)	★★★★	★★★★★	✅	Both support standard exports
35	Design of Experiments (DoE)	★★★★★	✗		Lucullus only
36	Media management	★★★★★	◐		Lucullus: automated media creation
37	Sample management	★★★★★	◐		Lucullus: barcoding + at-line analyzers
INTEGRATION
38	OPC UA	★★★★ (data exchange)	★★★★★	✅	QB: native + dedicated Connector, full control
39	Multi-vendor bioreactor support	★★★★★	★★★★		Lucullus: broader driver library; QB: OPC-UA reach
40	REST API	★★★★	★★★★★	✅	Both provide REST API
41	MQTT	★★	★★★★★	✅	QB: native
42	SQL access	★★★★★ (Oracle SQL)	★★★★		Lucullus: full Oracle power
43	MTP support	✗	★★★★	✅	QB: plug-and-produce (new)
44	LDAP/AD SSO	★★★	★★★★★	✅	QB: native LDAP/AD
45	PLC reuse (Wago/Siemens/Beckhoff)	★★★ (via drivers)	★★★★★	✅	QB: industrial-PC deployment (new)
COMPLIANCE & SECURITY
46	FDA 21 CFR Part 11	★★★★	★★★★	⚠️	Lucullus e-sigs today; QB partial (no e-sigs yet)
47	GAMP 5 classification	Category 5 (custom)	Category 4	✅	QB: 50–70% less validation
48	Electronic signatures	★★★★	★★	⚠️	Lucullus today; QB roadmap Q3 2026
49	ISA-18.2 alarm management	★★★	★★★★★	✅	QB: documented conformance
50	Audit trail	★★★★ (Oracle logs)	★★★★★	✅	QB: granular per-module module
51	Role-based access control	★★★	★★★★★	✅	QB: granular per-action RBAC
52	Safe Position Logic (GMP)	★★★	★★★★★	✅	QB: built-in configurable feature
53	Calibration management	★★ (vendor tools)	★★★★★	✅	QB: integrated calibration module
DEPLOYMENT & OPERATIONS
54	Installation time	★★ (hours–days)	★★★★★	✅	QB: browser-based, no install
55	IT infrastructure required	★★ (Windows + Oracle + network)	★★★★★	✅	QB: host + PoE cables
56	Training requirement	★★★ (formal courses)	★★★★★	✅	QB: self-paced online portal
57	System integrator dependency	★★ (often needed)	★★★★★	✅	QB: $0, self-service
58	Remote access	★★★ (VPN + RDP)	★★★★★	✅	QB: secure VPN + QR setup (new)
59	Health monitoring dashboard	★★★	★★★★★	✅	QB: consolidated module/host health (new)
COST & LICENSING
60	Initial investment	★★	★★★★★	✅	58–78% lower (4-bioreactor)
61	5-year TCO	★★	★★★★★	✅	$75K–110K vs. $265K–345K
62	License model	★★	★★★★★	✅	QB perpetual; Lucullus recurring
63	Oracle / DB licensing	★★	★★★★★	✅	QB: none
64	Vendor lock-in	★★	★★★★★	✅	QB: open ecosystem
HARDWARE
65	Own hardware ecosystem	✗	★★★★★	✅	QB: native PoE modules
66	Native Hamilton / Mettler Toledo sensors	★★★	★★★★★	✅	QB: direct via QB Multisensor
67	Automated sampling hardware	★★★★★ (Numera)	★★★★		Numera best-in-class for sample prep
68	Photobioreactor lighting	✗	★★★★	✅	QB: QB Light, native

Summary Scores by Category

Category	Lucullus PIMS	QB Control	Winner
Core Control	3.6	4.7	QB Control
Parallel Processing	3.4	4.7	QB Control
Recipe, Batch & Services	3.4	4.9	QB Control
Data Management & Analytics	4.6	3.5	Lucullus (Oracle, DoE, cross-experiment)
Integration	3.5	4.7	QB Control
Compliance & Security	3.4	4.5	QB Control (GAMP Cat 4; e-sigs trail Lucullus)
Deployment & Operations	2.4	5.0	QB Control

Overall: QB Control wins in 6 of 7 categories for the target lab-to-pilot market. With its unified recipe block library, sequential auto-stop campaigns, native MTP, OPC-UA connector, secure remote access, Health Monitoring, and the industrial-PC deployment path, QB Control leads decisively in architecture, deployment, recipe/services, integration, compliance burden, and cost. Lucullus retains a strong lead in data management — Oracle-powered cross-experiment analytics, native DoE, and enterprise multi-site harmonization — making it the better choice for data-intensive process development and established heterogeneous fleets. Lucullus also leads on electronic signatures until QB Control’s Q3 2026 release.

Scoring reflects lab-to-pilot scale bioprocessing scenarios. Lucullus would score higher for enterprise multi-site and cross-experiment analytics use cases.

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 Securecell Lucullus® version 24.x (current release; 2024 version-numbering scheme). 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. Lucullus®, Numera®, and Amphora® are trademarks of Securecell AG; Getinge® is a trademark of Getinge AB. 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 Securecell Lucullus® 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. Lucullus PIMS competitive positioning QB Systems — Flexible. Innovative. Limitless. | A product brand of A4BEE Sp. z o.o. | https://qb.systems