Ignition SCADA vs. QB Control

Comprehensive Comparison for Bioprocessing Automation

1. Executive Summary

Ignition SCADA Overview

Inductive Automation's Ignition is a general-purpose, software-only SCADA platform built on Java and centered around external SQL databases. Released in 2003, Ignition has become a flexible workhorse for factory automation, wastewater plants, smart buildings, and facility-scale control systems. Its core value is unlimited licensing per gateway, native Python scripting (Jython), and a vast integrator ecosystem spanning industrial protocols (Modbus, Allen-Bradley, Siemens S7, OPC-UA, BACnet, DNP3, MQTT).

Key attributes:

• Blank-canvas toolkit requiring custom engineering for each deployment

• SQL-centric data architecture (MySQL, PostgreSQL, MS SQL, Oracle)

• Modular licensing (Perspective, Vision, Reporting, Alarm Notification, SFC, SQL Bridge, etc.)

• Runs on Windows, Linux, macOS with Java runtime

• No hardware included; requires external PLC, I/O racks, and wiring

• Estimated full-system cost: $15K–30K (software) + $50K–150K+ (integrator labor)

• Integrated hardware+software bioprocess appliance

• Zero external database setup; browser-based, no Windows required

• GAMP 5 Category 4 (configurable) vs. Ignition's typical Category 5

• Perpetual perpetual license, no subscription

• Deployment: hours-to-days vs. Ignition's weeks-to-months

• Estimated cost: $15K–25K (2-bioreactor) to $150K–250K (pilot scale)

Core Distinction: Toolkit vs. Appliance

Dimension	Ignition	QB Control
Model	"Blank canvas" SCADA toolkit	Purpose-built bioprocess appliance
Approach	Custom engineering from scratch	Co-engineered services + modules
Deployment	Weeks–months + integrator	Hours–days self-contained
Hardware	None (BYO PLC/I/O)	Integrated QB Edge + 20+ PoE modules
Learning curve	Steep (requires SCADA/PLC knowledge)	Gentle (bioprocess-native semantics)
Flexibility	Extreme (any protocol, any logic)	Moderate (bioprocess-focused)
Time-to-value	Long (requires integration expertise)	Short (plug-and-play)

Replacement Viability Matrix

Scenario	Ignition Fit	QB Control Fit	Rationale
Greenfield single bioreactor (2L–50L)	Marginal	Excellent	QB's plug-and-play replaces Ignition's engineering overhead.
DeltaV replacement (existing bioprocess)	Poor	Excellent	QB maintains bioprocess context; Ignition requires PLC + custom logic.
Ignition+PLC bioprocess to unified platform	Acceptable	Excellent	Migration to QB eliminates PLC, centralizes control, accelerates time-to-validation.
Facility-wide SCADA (multi-building, multi-function)	Excellent	Limited	Ignition's IT integration, broad protocol support suit facilities; QB is bioprocess-centric.
Multi-vendor equipment integration	Good	Very Good	Both support OPC-UA; QB optimized for bioprocess OEM (Sartorius, Applikon).
Parallel screening (6+ concurrent bioreactors)	Acceptable	Excellent	QB's native multi-processing and recipe sequencing drastically cut deployment time.

Conclusion: For bioprocessing automation—particularly lab-to-pilot scale— QB Control is a replacement, not a supplement . Ignition is a powerful but generic platform; QB is a bioprocess-specific system. Choosing Ignition for a 2–10 bioreactor facility introduces unnecessary complexity, cost, and validation burden.

2. Platform Philosophy

Ignition: The CNC Machine Shop

Ignition embodies a "build anything from scratch" philosophy. Like a modern CNC machine shop with programmable multi-axis mills, lathes, and EDM machines, Ignition is supremely flexible— but requires a skilled machinist . You define every control loop, every interlock, every UI element via Java code, Python (Jython), SQL queries, and module configurations.

Ignition's design paradigm:

• IT/OT convergence: treat the SCADA gateway as a networked application server

• Protocol agnostic: speak any industrial language (Modbus, OPC-UA, Allen-Bradley, Siemens, etc.)

• Database-native: SQL queries are first-class citizens

• Modular extensibility: add Vision, Perspective, Reporting, Historian, SFC, etc., à la carte

• Target: plant/facility engineers and integrators with deep SCADA expertise

This philosophy is ideal for oil & gas refineries, wastewater plants, smart buildings, and automotive assembly— environments where control logic varies widely and OEMs demand custom solutions .

QB's design paradigm:

• Bioprocess-native: control loops, recipes, and parameters speak bioprocessing language (DO%, temperature setpoint, pH, pump feed rate, etc.)

• Hardware+software co-design: modules are factory-validated; no PLC programming or wiring schematic required

• Self-contained: no external database, no IT infrastructure setup

• GAMP 5 Category 4 by design: audit trail, RBAC, recipe versioning built-in

• Target: bioprocess engineers, pharma QA, manufacturing teams with bioprocess expertise (not SCADA expertise)

This philosophy is ideal for contract manufacturers, GMP biotech labs, academic research bioreactors, and perfusion pilot plants— environments where time-to-validation and ease-of-use trump maximal flexibility .

The Analogy Advantage

Aspect	CNC Machine Shop (Ignition)	3D Printer (QB Control)
Setup time	Weeks (fixture design, tooling, calibration)	Minutes (level, load filament, slice CAD)
Learning curve	Steep (G-code, feeds/speeds, tooling databases)	Shallow (load model, hit print)
Customization	Unlimited (mill anything)	Moderate (material+preset profiles)
Time per job	Long (especially first run)	Short (predictable)
Operator skill	Expert machinist	Any engineer with CAD
Cost per part	High (setup labor, rework)	Low (predictable, repeatable)
Risk of error	High (miscalibration, tool crash)	Low (proven software+hardware)

For bioprocess automation, QB Control is the 3D printer; Ignition is the CNC shop.

3. Architecture & Hardware

System Architecture Comparison

Component	Ignition	QB Control
Control Engine	Java Gateway (Windows, Linux, macOS)	QB Edge (Linux ARM, fanless, IP40-rated)
Database	External SQL (MySQL, PostgreSQL, MS SQL, Oracle)	Embedded SQLite (internal, no admin required)
Field I/O	PLC + analog/digital I/O racks + marshalling cabinet	20+ PoE modules (sensors, pumps, valves, etc.)
Networking	Ethernet (gateway↔PLC, gateway↔clients)	Ethernet (QB Edge↔PoE switches); mesh wireless option
HMI	Perspective (web) or Vision (desktop)	Browser-only (no client installation)
Data flow	Gateway ↔ SQL DB ↔ OPC-UA server ↔ PLC	QB Edge ↔ PoE modules ↔ browser (local network)
Typical footprint	Server-based (1–10 Mbps WAN)	Edge-based (LAN; works offline)

Hardware Requirements

Ignition infrastructure (not included):

• PLC (Allen-Bradley CompactLogix ~$2K–5K, Siemens S7-1200 ~$3K–7K, etc.)

• I/O modules (analog, digital, temperature, pressure: ~$500–3K per slot)

• Marshalling cabinet with terminal blocks, power supply, protective relays (~$5K–15K)

• Cabling, conduit, installation labor (~$5K–20K for bioprocess skid)

• SQL database server (on-premise or cloud: ~$2K–10K/year)

• IT infrastructure (firewalls, VPN, data backup)

• QB Edge controller (~$5K–8K, included in license)

• PoE modules: pH sensor ($600), temperature ($400), pump ($800), gas flow ($1.2K), etc.

• PoE switch (industrial grade, ~$1.5K–3K)

• Cabling (PoE simplifies—no analog 4–20 mA wiring)

• No PLC, no marshalling cabinet, no external DB

Result: QB's hardware footprint is 50–70% smaller, 40–60% faster to deploy, and 20–30% lower capital cost than Ignition+PLC for equivalent bioreactor control.

IT Complexity

Task	Ignition	QB Control
Database setup & admin	Required (schema design, user accounts, backup)	Not required (SQLite managed internally)
PLC programming	Required (IEC 61131-3 or proprietary language)	Not required (services pre-programmed)
Server OS management	Required (Windows patch, Java runtime, firewall)	Not required (QbEdge = pre-configured appliance)
Network configuration	Required (TCP/IP, OPC-UA endpoints, SQL connections)	Simplified (PoE + single browser URL)
Backup & disaster recovery	Required (SQL backups, gateway configuration export)	Simplified (auto-backup to SD card or cloud)
Training depth	Deep (SCADA architecture, SQL, scripting, OPC-UA)	Shallow (bioprocess parameters, recipe UI)

4. Parallel Processing

Multi-Bioreactor Orchestration

Ignition approach (typical biotech integrator project):

• Each bioreactor is wired to a PLC or networked I/O controller

• Ignition's Gateway polls each device via OPC-UA or Modbus

• Control logic (pH PID, aeration ramps, feed sequences) is split between PLC and Ignition SFC modules

• Recipe/batch coordination is script-based (Jython or SQL-driven state machines)

• For N bioreactors, expect N distinct PLC programs + N SFC modules + N SQL tables

Challenges:

• Synchronizing parallel recipes across PLCs requires manual scripting

• Cross-vessel logic (e.g., "if vessel A reaches OD 1.5, trigger feed in vessel B") is cumbersome

• Each PLC adds $2K–5K hardware + weeks of configuration

• All bioreactors connect to QB Edge via PoE (one switch, one cable per vessel)

• Recipes are composed once on Recipe Designer Board (DAG: drag-and-drop, conditionals, splits, merges)

• Single recipe can be deployed simultaneously to multiple bioreactors with different parameter sets (Batch Board: parallel execution)

• Cross-vessel logic is native: "if vessel-1.OD > 1.5 then trigger vessel-2.feed-pump"

• For N bioreactors, use 1 recipe + N execution profiles

Comparison table:

Metric	Ignition	QB Control
Deployment time (4 bioreactors, parallel)	6–12 weeks	2–5 days
PLC programs needed	4 (one per vessel)	0 (centralized)
Recipe definition	Script-based state machine	Visual DAG (drag-and-drop)
Cross-vessel logic	Manual (complex, error-prone)	Native conditionals/splits
Synchronization complexity	Medium–High (PLC + SFC + SQL)	Low (QB Edge orchestrates)
Time to re-sequence (e.g., change feed timing)	Hours–days (requires PLC edit + test)	Minutes (recipe UI)
Validation effort	High (N PLCs = N validations)	Low (1 QB system, N parameter sets)

Conclusion: For parallel bioprocess screening (6+ concurrent vessels), QB Control is dramatically faster to deploy. Ignition requires proportional PLC multiplication; QB scales orchestration without proportional complexity.

5. Multi-Vendor Integration

OPC-UA as Common Ground

Both Ignition and QB Control support OPC-UA , the open industrial protocol for connecting PLCs, sensors, and third-party equipment. This is critical for integrating non-standard bioprocess hardware (fermenters, perfusion units, chromatography skids, analytics instruments).

Protocol Support Comparison

Protocol	Ignition	QB Control	Bioprocess Relevance
OPC-UA	Native server + client	Native client + optional server	Critical for bioreactor OEMs (Sartorius, Applikon, Eppendorf)
Modbus TCP/RTU	Full support (via modules)	Limited (via OPC-UA bridge)	Legacy analogue sensors, pressure transmitters
Allen-Bradley	Native (CompactLogix, ControlLogix)	Not supported	Not needed for bioprocess (PLC-free design)
Siemens S7	Native (S7-1200, S7-1500)	Not supported	Not needed for bioprocess (PLC-free design)
BACnet	Full support (via modules)	Not supported	Building automation (HVAC, power)
DNP3	Full support (via modules)	Not supported	Utility grid (not bioprocess)
MQTT	Via Cirrus Link modules	Optional (OPC-UA primary)	IoT/cloud integration
HTTP REST	Via built-in client	Native (browser-based)	Lab management systems, ERP integration

Bioprocess-Specific Integration

Ignition + OPC-UA:

• Requires system integrator to map OEM device tags → Ignition tags → HMI

• Each OEM connection is a custom integration point (Sartorius → Ignition may differ from Applikon → Ignition)

• No pre-built connectors for bioreactor OEMs; each integrator develops their own

• Pre-built OPC-UA connectors for common bioprocess equipment (Sartorius, Applikon, Infors, Eppendorf in roadmap)

• Service templates bridge QB native parameters (pH setpoint, temp, pump rate) to OEM analog signals

• Single QB instance integrates multiple OEMs seamlessly

Third-Party Equipment Example

Scenario: Integrate a Sartorius DASGIP bioprocess control unit with downstream analytics

Ignition path:

• Configure Sartorius OPC-UA server address in Ignition

• Add ~50 OPC-UA tags (setpoint, readback, alarms for each bioreactor)

• Script Jython to map Sartorius tags to Ignition tags

• Build Perspective screens to visualize Sartorius data

• Write SQL queries to store historical data

• Effort: 2–4 weeks integrator time

• Plug Sartorius PoE connector into QB Edge (optional native driver)

• Services auto-populate from Sartorius device profile (pre-defined sensors/actuators)

• Drag Sartorius services onto Recipe Designer Board

• Execute recipe; all data logged to QB audit trail

• Effort: 1–2 days

Conclusion: Both support OPC-UA, but QB is bioprocess-optimized ; Ignition requires custom integrator mediation .

6. Software Module Comparison

Ignition Modules (Selected)

Module	Purpose	Cost (est.)	Bioprocess Relevance
Perspective	Web-based HMI, responsive design	Included	Good (browser, mobile)
Vision	Desktop HMI (Java Swing)	$3,975–6,975	Marginal (legacy, requires Vision client installation)
Tag Historian	Time-series data logging	$1,400–2,200	Essential (but requires SQL DB setup)
Alarm Notification	Threshold-based alerts, email	$1,700	Basic (Ignition alarms are not GMP-audit-trailed)
Reporting	Crystal Reports integration, PDF export	$2,200	Essential (batch reports, but not bioprocess-native)
SQL Bridge	ODBC/SQL direct query, charting	$2,500	Useful (but adds complexity: SQL knowledge required)
SFC	Sequential Function Charts (IEC 61131-3 graphical programming)	~$2,000	Poor (not bioprocess; requires programming expertise)
OPC-UA	OPC-UA server/client	Included	Essential (third-party equipment integration)
MQTT Engine	MQTT broker, publish/subscribe	~$2,000	Good (cloud/IoT integration)
Scripting (Jython)	Python 2.7-based automation	Included	Moderate (requires coding skill)

Module	Purpose	Bioprocess Relevance
1. System	Gateway config, users, backup, settings	Essential
2. Process	Vessel & equipment definition, sensors/actuators	Essential
3. P&ID	Auto-generated process diagrams from equipment tree	Excellent (visual + traceable)
4. Inventory	Consumables tracking (media, antifoam, buffers, tips)	Excellent (GMP-specific)
5. Alarms	Threshold-based with GMP audit trail	Excellent (21 CFR Part 11 native)
6. Recipe Designer	Drag-and-drop DAG recipe composition	Excellent (bioprocess-native)
7. Batch Board	Multi-recipe execution, sequencing, parallel runs	Excellent (bioprocess orchestration)
8. Executions Board	Historical run data, comparison, re-run capability	Excellent (batch record + audit trail)
9. Graphs	Real-time & historical charting	Excellent (bioprocess KPIs)
10. Reports	Batch reports, SPC, compliance documents	Excellent (pre-built bioprocess templates)
11. Runs	Batch tracking, material reconciliation	Excellent (bioprocess-specific)
12. Calibration	Sensor calibration, traceability	Excellent (GMP requirement)
13. Audit Trail	Immutable log of all actions	Excellent (21 CFR Part 11 core)
14. Users & Roles	Role-based access control (RBAC)	Excellent (GMP access control)
15. Notifications	Alarms, approvals, escalations (email, SMS)	Excellent (operator workflow)
16. Backup & Export	Data export, disaster recovery	Excellent (cloud-optional)
17. License	License activation, module entitlements	Essential
18. Settings	Global configuration, thresholds	Essential

Module Mapping: What's Missing in Ignition

QB Capability	Ignition Equivalent	Gap
Inventory	None; custom SQL required	Ignition has no bioprocess material tracking
P&ID	None; requires Visio or third-party tool	Ignition does not auto-generate P&IDs
Process (Equipment tree)	None; custom Perspective screens	Ignition does not model bioprocess equipment hierarchy
Recipe Designer (DAG)	SFC (Sequential Function Charts)	SFC is programmatic, not visual; no drag-and-drop DAG
Batch Board	Custom Jython + SQL state machine	Ignition has no native batch orchestration
Executions Board	Tag Historian (time-series only)	No batch-level historical runs with re-execution
Calibration	None; manual logging or custom app	No automated sensor calibration traceability
Runs	Tag Historian + custom Perspective	No bioprocess-native run tracking

Conclusion: QB Control includes 18 pre-built, bioprocess-optimized modules; Ignition includes only 6 core modules , and bioprocess-specific capabilities (Inventory, Recipe Designer, Batch Orchestration, Calibration) require custom development on top of Ignition.

7. Services Catalog & Rapid Deployment

Service Categories & Counts

Category	Count	Service Types	Examples
pH Control	6	Setpoint, ramp, cascade, two-point, proportional band	pH 5.5 constant, pH ramp 5.5→7.0, dual-acid pH
Temperature	6	Setpoint, ramp, profile, external control	37°C constant, 37°C→42°C ramp, temperature profile lookup
Pump & Feed	9	Peristaltic, gear, centrifugal, bolus, continuous, pulsed	Continuous feed at X mL/h, bolus feed every 2h, exponential feed
Gas Control	4	Single gas (air, O₂, N₂), mixed gas, O₂ blend, pressure	0.5 vvm air, DO cascade (aim 40%), CO₂ vent
Gas Volume	1	Dissolved oxygen (DO) by volumetric gas flow	DO 50% setpoint via air/O₂ mix
Sampling	3	Automated sampling, dilution, storage	Sample every 4h, 10 mL aliquots, auto-dilution
Stirring	2	Speed setpoint, ramp	300 rpm constant, 200→500 rpm ramp
Foam	2	Antifoam control, level detection	Antifoam on foam detection, antifoam injection 0.5 mL
Valve	2	On/off, proportional	Open harvest valve, proportional sampling valve
LED / Light	2	On/off, PWM dimming, color control	LED on/off, 75% PWM intensity

Service Configuration

Each service is a "Service Profile" — a reusable parameter template:

• Service Template: Generic blueprint (e.g., "PID pH Control")

• Service Profile: Instantiation with parameters (e.g., "pH Control for Vessel-1: setpoint=6.5, update interval=5s, pump=peristaltic-acid, calibration=2-point")

• Recipe: Composition of services (e.g., "Fed-Batch Fermentation = pH Control + Temperature Control + Pump Feed + Aeration Ramp + Sampling")

Example recipe: E. coli high-cell-density fermentation

• pH Control (6.8 ± 0.2) [Service: pH cascade via acid/base pumps]

• Temperature (37°C ± 0.5°C) [Service: jacket control]

• Aeration (2.0 vvm → 0.5 vvm ramp at 6h) [Service: gas flow ramp]

• Feed (exponential: 0.01 → 0.5 mL/h) [Service: peristaltic bolus feed]

• Antifoam (threshold: 5% foam) [Service: antifoam on detection]

• Sampling (every 2h, 10 mL) [Service: automated sampling]

Duration: 16 hours

All 6 services are pre-built, tested, and validated . Deployment: define parameters, drag into recipe, execute.

Ignition: Zero Pre-Built Bioprocess Services

Ignition provides no pre-built bioprocess service templates . Instead, Ignition offers:

• SFC (Sequential Function Charts): Graphical IEC 61131-3 programming language

• Scripting: Jython (Python 2.7 subset)

• Tag-based control: User-defined tags with scripts and event handlers

Ignition Approach for a Single PID Loop (pH Control)

Step 1: Define tags

• pH_setpoint (numeric, float)

• pH_actual (from PLC input tag)

• pH_error (calculated: setpoint - actual)

• pH_integral (accumulated error)

• pH_derivative (rate of change)

• pump_output (0–100%)

• last_pH_reading (timestamp)

Step 2: Create SFC or scripting logic

Every 1 second:

pH_error = pH_setpoint - pH_actual

pH_integral += pH_error * 1s

pH_derivative = (pH_error - last_error) / 1s

pump_output = Kp error + Ki integral + Kd*derivative

Send pump_output to PLC (write tag)

last_error = pH_error

Step 3: Build UI (Perspective)

• Display pH setpoint (input box, range validation)

• Display pH actual (real-time gauge, color-coded)

• Display pump output (bar chart)

• Alarm: pH out of range (red banner, email alert)

Step 4: Set up historian logging

• SQL query: INSERT INTO pH_history (timestamp, setpoint, actual, pump_output) VALUES...

• Frequency: every 10s

• Retention: 1 year

Step 5: Validation & testing

• Unit test SFC logic

• Integration test with PLC

• Worst-case scenario test (sensor fail, pump failure, etc.)

• Typical effort: 2–3 weeks integrator time per PID loop

For 4 bioreactors with 3 PID loops each (12 loops total): 6–9 weeks integrator work, custom code for each loop, no reusability across vessels or projects.

Deployment Time Comparison

Task	Ignition	QB Control
Set up 2-bioreactor system with pH, temp, aeration, feed	6–8 weeks	1–2 days
Add 3rd bioreactor to system	2–3 weeks (PLC program, SFC, historian, UI)	2–4 hours (add vessel, select service profiles)
Change pH setpoint from 6.8 to 7.2	Minutes (tag edit)	Seconds (UI slider)
Change feed sequence (e.g., ramp over 4h instead of 2h)	Hours–days (SFC edit, test, deploy)	Minutes (recipe edit)
Deploy recipe to parallel test (4 vessels, different parameters)	Weeks (4 SFCs, 4 UI screens, 4 historian configurations)	Hours (1 recipe, 4 parameter sets)

Conclusion: QB Control's pre-built services eliminate 70–90% of engineering time for bioprocess automation. Ignition requires from-scratch engineering for every process step.

8. Recipe Engine

Recipe Elements

Element	Type	Example Use
Service	Node	"pH Control (setpoint=6.8)" — executes a pre-built service
Conditional	Decision	"IF cell density > 1.0 OD600 THEN trigger feed ELSE wait 1h"
Counter	Loop	"Repeat sampling 10 times, every 2h"
Parallel (Split)	Orchestration	"Start aeration & temperature simultaneously"
Sequential (Merge)	Orchestration	"Wait for aeration to reach 1.0 vvm, THEN start feed"
PID	Control	"PID loop: setpoint, Kp, Ki, Kd"
Polygon	Lookup table	"Temperature profile: time→target temp"
Manual Operation	User approval	"Operator: add 500 mL media to reservoir, confirm when done"

Recipe Example: Fed-Batch E. coli Fermentation

RECIPE: Fed-Batch E. coli (Version 1.3, Status: Verified)

┌─────────────────────────────────────┐

│ Pre-flight Checklist │

│ [×] Vessel calibrated │

│ [×] Media prepared │

│ [×] Antifoam loaded │

│ [×] Operator: Start inoculation? │

└─────────────────────────────────────┘

│ PARALLEL START (Time = 0) │

│ ├─ Service: pH Control (6.8±0.2) │

│ ├─ Service: Temperature (37±0.5°C) │

│ ├─ Service: Aeration (2.0 vvm) │

│ └─ Service: Antifoam (threshold 5%) │

│ Timer: Wait 4 hours (batch growth) │

│ CONDITIONAL: OD600 > 1.0? │

│ ├─ YES → continue to feed phase │

│ └─ NO → wait 1h, re-check │

│ Service: Peristaltic Feed │

│ (Exponential ramp: 0.01→0.5 mL/h) │

│ Duration: 8 hours │

│ COUNTER: Sampling Loop │

│ Repeat 8 times @ 1h intervals │

│ ├─ Service: Auto-sample (10 mL) │

│ └─ Service: Temperature (keep 37°C) │

│ Service: End Process │

│ ├─ Aeration: OFF │

│ ├─ Feed: OFF │

│ └─ Manual: Operator harvest │

Recipe Versioning Lifecycle

Status	Color	Meaning	Usage
Draft	Yellow	Work-in-progress; edit enabled	Development, testing
Verified	Blue	QA-reviewed, ready for validation	Pilot-stage deployment
Validated	Green	GMP-validated, locked for change control	Production use
Archived	Red	Superseded; historical reference only	Audit trail

Batch Board: Multi-Recipe Execution

Once recipes are defined, the Batch Board enables simultaneous execution across multiple bioreactors:

BATCH EXECUTION: Day-1 Scale-Up Study

Execution Type: PARALLEL (all vessels simultaneous)

Vessel-1 (2L): Fed-Batch E. coli (v1.3) - Started 09:00

Vessel-2 (5L): Fed-Batch E. coli (v1.3) - Started 09:00 [Temp setpoint: 32°C instead of 37°C]

Vessel-3 (10L): Fed-Batch E. coli (v1.3) - Started 09:00 [Aeration: 1.5 vvm instead of 2.0]

Vessel-4 (2L): Clone screening test - Started 09:15 [Different strain, different recipe]

Cross-Vessel Logic: IF Vessel-1.pH > 8.0 THEN pause Vessel-2 feed (cross-contamination risk)

Each vessel's parameters are instantiated from a single recipe but with different parameter sets (pH setpoint, aeration, feed rate, etc.), reducing validation effort by 70–80%.

Ignition: SFC-Based Recipe (No DAG)

Ignition's Sequential Function Charts (SFC) module provides graphical IEC 61131-3 programming. Unlike QB's drag-and-drop DAG, SFC is a programmatic state machine .

SFC Structure for Fed-Batch

STEP 0: Init

├─ Action: Check vessel calibration (script)

├─ Action: Log start timestamp

└─ Transition: User confirms "Ready"

STEP 1: Parallel_Start

├─ Action: pH_setpoint = 6.8; enable PID

├─ Action: Temp_setpoint = 37; enable heater

├─ Action: Aeration_setpoint = 2.0; enable air pump

├─ Action: Antifoam_enable = TRUE

└─ Transition: Delay 4 hours OR (OD600 > 1.0 after 2h)

STEP 2: Feed_Phase

├─ Action: Pump_rate = exponential(t) = 0.01 + 0.049*(1-exp(-t/8))

├─ Action: Maintain pH, Temp via PID loops

└─ Transition: Timer > 8 hours OR manual stop

STEP 3: Sampling_Loop

├─ Action: Repeat 8 times { sample(10mL), wait 1h }

└─ Transition: Counter >= 8

STEP 4: End

├─ Action: Disable all pumps, heater, aeration

├─ Action: Log end timestamp, store data

└─ Transition: Complete

SFC Challenges for Bioprocess

Challenge	Impact
Programmatic state machine (not visual DAG)	Requires SCADA expertise; not intuitive for bioprocess engineers
No pre-built control loops	Every PID, ramp, and conditional must be hand-coded
Testing & debugging	SFC state transitions are hard to visualize; unit testing requires integrator
Reusability	SFC for E. coli batch is not reusable for CHO or yeast; must clone and edit
Version control	SFC is XML; no UI-based version history like QB's Draft/Verified/Validated
Parallel execution	Multiple vessels require multiple SFCs or complex parallel-step logic (error-prone)
Change management	Editing SFC for pilot stage requires re-testing, re-validation for production

Recipe Comparison Table

Feature	Ignition SFC	QB Control DAG
Programming model	State machine (programmatic)	DAG (visual, declarative)
Learning curve	Steep (IEC 61131-3 knowledge required)	Shallow (bioprocess semantics)
Time to recipe (simple fed-batch)	1–2 weeks integrator	1–2 hours bioprocess engineer
Pre-built templates	None	37 (complete library)
Parallel execution	Requires manual SFC splitting	Native (single DAG → N vessels)
Version control	XML export/import	UI-based Draft/Verified/Validated
Reusability across projects	Low (custom code per recipe)	High (parameterized services)
Validation for GMP	Extensive (code review, test coverage)	Streamlined (pre-validated services)

Conclusion: QB Control's DAG-based recipe engine is purpose-built for bioprocessing and reduces engineering time by 75–90% vs. Ignition's SFC. Ignition requires programming expertise ; QB requires bioprocess knowledge .

9. Regulatory Compliance

GAMP 5 Classification

GAMP 5 (Good Automated Manufacturing Practice) categorizes software automation systems by complexity and required validation:

Category	Definition	Validation Effort	Typical Example
Cat 1	Off-the-shelf, unmodified software (e.g., Excel, Access)	Minimal	Spreadsheet inventory tracking
Cat 2	Off-the-shelf with validated database & minimal configuration	Light	Labware LIMS with standard config
Cat 3	Off-the-shelf with significant configuration/customization	Moderate	Ignition with 20+ custom SFC scripts
Cat 4	Software configured/built to specification with reusable components	Moderate–High	QB Control (pre-built bioprocess modules)
Cat 5	Custom-built software with full source code control	Highest	Ignition + integrator SCADA system for unique requirements

Validation scope:

• Vendor (QB Systems) provides pre-validated services (pH, temp, pump, aeration, etc.)

• Integrator provides system validation (installation, configuration, operational testing)

• Customer provides site acceptance testing (performance, user acceptance)

• No source code review or custom component development required

Typical validation timeline: 4–7 weeks

Typical validation cost: $15K–35K

Validation artifacts:

• Installation Qualification (IQ): Hardware installed per spec, dependencies verified

• Operational Qualification (OQ): Pre-built services tested at operational boundaries (setpoint range, sensor failure modes, etc.)

• Performance Qualification (PQ): Customer's process recipes executed, batch records generated, audit trails verified

• Risk assessment: hazard analysis, failure mode testing

• Calibration records: sensor traceability

• Change control procedure: recipe versioning, parameter change approval

Ignition: GAMP 5 Category 5

Ignition is typically Category 5 ( custom-built ) because:

• No pre-built control loops: Every pH PID, aeration ramp, feed sequence is custom code

• PLC + Ignition split: Validation must cover both PLC logic and Ignition SFC/scripting

• SQL database: Schema design, query validation, stored procedures (if used) must be validated

• System integration: OPC-UA connections, network topology, error handling all must be verified

• Source code review: Ignition scripts (Jython), SFC state machines, and PLC code require code review by qualified validator

Typical validation timeline: 12–24 weeks

Typical validation cost: $75K–200K+ (with integrator)

• Requirements specification (functional, performance, safety, regulatory)

• Design specification (architecture, PLC program design, Ignition SFC design, database schema)

• Software specification (code listing, module description, script functionality)

• Test plan: unit tests (SFC, scripts), integration tests (PLC↔Ignition), system tests (multi-bioreactor orchestration)

• Risk assessment: failure modes, sensor fault injection, network failure scenarios

• Code review (peer review, static analysis)

• Operational procedures: startup, shutdown, error recovery, disaster recovery

• Training documentation and records

Validation risk factors:

• If integrator changes SFC or scripts, entire system must be re-validated

• If PLC logic is modified, PLC program and Ignition integration must both be re-tested

• If SQL schema changes, historian queries and batch records must be re-verified

Compliance Comparison

Requirement	QB Control	Ignition
FDA 21 CFR Part 11	Partial (all editions): audit trail, RBAC, data integrity; e-signatures on roadmap	Supported via modules (Alarm Notification, Historian, Security), but requires custom implementation
Audit Trail (immutable log)	Native: every action (parameter change, recipe edit, operator action) logged with timestamp, user, old/new value	Via Historian module (~$1,700): logs tags only, not configuration changes or user actions
E-Signature	◐ On roadmap (not in current version)	Requires custom module or third-party integration
Role-Based Access Control (RBAC)	Pre-configured roles (Operator, Supervisor, Admin, View-only, QA, Manager)	Built-in security, but roles are Ignition Gateway users (not bioprocess-specific)
Batch Record	Auto-generated with recipe, parameters, sensor data, alarms, operator actions	Manual assembly (Historian data + SFC logs + SQL queries + screenshots)
Data Integrity	Database encryption (AES), backup validation, disaster recovery	Via Historian (requires DBA configuration)
Traceability	Sensor calibration tracking, lot-to-vessel mapping, cross-batch links	Manual logging; no built-in traceability module
Change Control	Recipe versioning (Draft → Verified → Validated → Archived) with approval workflow	Manual procedure; SFC versioning is Git-based or integrator-specific
Computer Validation	Supported; GAMP 4 by design	Requires custom validation framework (GAMP 5)

21 CFR Part 11 Compliance: Detailed Comparison

1. User Identification & Authentication

• Username + Password (configurable complexity)

• Session timeout (configurable, default 15 min)

• Password reset via email verification

• Optional: LDAP/Active Directory integration, multi-factor auth (roadmap)

2. Audit Trail (Immutable Log)

• Every action logged: time, user, action type, old value, new value

• Examples: "2026-04-07 14:32:15, john.smith, pH_setpoint, 6.8, 6.9"

• Stored in encrypted database; cannot be modified retroactively

• Export: CSV, PDF (with hash verification)

3. E-Signature

• Not currently supported. On roadmap for future release.

• Current capabilities:

• Operator password + timestamp for audit trail (user identity confirmation)

• Session tracking for critical actions (Recipe version approval, Batch release, Parameter changes)

• All actions recorded in immutable audit trail with regulatory metadata

• Planned future: Biometric and digital signature support (under development)

4. Data Integrity

• Database encryption: AES-256 at rest

• HTTPS for all web communications (TLS 1.2+)

• Backup integrity: automated daily backups with hash verification

• Disaster recovery: automated restore from backup with audit trail verification

5. Role-Based Access Control

• Pre-defined roles:

• Operator: Execute recipes, view data, log samples

• Supervisor: Approve recipe changes, review batches

• QA Manager: Validate recipes, generate compliance reports

• System Admin: Configure system, manage backups, audit trail

• View-Only: Read-only access to dashboards and reports

• Custom roles with granular permissions (table, field, action level)

Ignition (Module-Based, Add-On Costs)

• Built-in: username/password via Gateway security

• Session management: configurable timeout

• LDAP/Active Directory: supported

2. Audit Trail

• Tag Historian module (~$1,700): logs tag changes (timestamp, old value, new value)

• Gap: Does not log configuration changes (SFC edits, UI modifications, security policy changes)

• SFC audit trail: via text file or integrator custom logging

• Gap: No standardized format for multi-system audit trail

• Not built-in. Requires third-party e-signature module (e.g., DocuSign integration) or custom development (~$5K–10K integrator work)

• Alternative: manual PDF signature capture + manual logging

• SQL database encryption: depends on database vendor (MS SQL, PostgreSQL, Oracle all support encryption)

• Requires DBA setup; not automatic

• HTTPS: configurable in Ignition Gateway

• Backup: SQL backup best practices; not automated by Ignition

• Built-in to Ignition Gateway: user groups with resource-level permissions

• Gap: No pre-built bioprocess roles (e.g., "QA Manager"); requires custom configuration

• Gap: No inheritance hierarchy for complex facilities

Validation Effort Comparison

Task	QB Control	Ignition
Requirements specification	2 weeks (standard bioprocess template)	4 weeks (custom requirements)
Design specification	1 week (pre-built services)	6 weeks (PLC + Ignition architecture)
Risk assessment (FMEA)	1 week (per vendor + integrator analysis)	2 weeks (broader system complexity)
Test plan & execution	2 weeks (service-level + integration tests)	6 weeks (unit + integration + system tests)
Code review	2 days (configuration review)	3–4 weeks (SFC, Jython, PLC code review)
Regulatory documentation	1 week (pre-built templates)	2–3 weeks (custom reports)
Total (simple bioprocess)	4–7 weeks	12–24 weeks
Cost	$15K–35K	$75K–200K+

Validation Timeline Gantt (Single 2-Bioreactor System)

Week 1-2: IQ (hardware install, dependencies)

Week 2-3: OQ (service boundary testing)

Week 3-4: PQ (user acceptance testing, batch execution)

Week 4-5: Risk assessment & documentation

Week 5-7: Final review, protocol close-out

Ignition (12–24 weeks)

Week 1-4: Requirements & design specification

Week 5-8: PLC program development & unit testing

Week 9-12: Ignition SFC development & unit testing

Week 13-16: Integration testing (PLC↔Ignition)

Week 17-20: System testing (multi-vessel, failure scenarios)

Week 21-22: Risk assessment & code review

Week 23-24: Documentation, training, final approval

Conclusion: QB Control's pre-built, pre-validated bioprocess services reduce GAMP 5 validation from 12–24 weeks (Category 5) to 4–7 weeks (Category 4) , cutting validation cost by 50–70% and timeline by 60–75%.

Dimension	QB Control	Ignition	Winner
Deployment speed	Hours–days	Weeks–months	QB
Hardware included	Yes (QB Edge + 20+ modules)	No (BYO PLC + I/O)	QB
Pre-built bioprocess services	37 (ready-to-use)	0 (custom engineering)	QB
Recipe design	Visual DAG (drag-and-drop)	SFC (programmatic)	QB
Regulatory (GAMP 5)	Category 4 (4–7 weeks)	Category 5 (12–24 weeks)	QB
Parallel processing	Native (1 QB, N vessels)	Complex (N PLCs, N SFCs)	QB
Module maturity	18 pre-built, bioprocess-optimized	6 core, generic	QB
Facility-wide integration	Limited (bioprocess-focused)	Excellent (IT/OT convergence)	Ignition
Flexibility	Moderate (bioprocess-centric)	Extreme (any protocol, any logic)	Ignition
Learning curve	Shallow (bioprocess semantics)	Steep (SCADA architecture)	QB

For bioprocessing (lab-to-pilot scale): QB Control is a purpose-built replacement, not a supplement. Ignition is a powerful but generic SCADA platform requiring proportional engineering effort. QB is a bioprocess-specific appliance designed for rapid deployment, validation, and operational simplicity.

10. Pricing, Licensing & TCO

Direct Pricing Comparison

Component	QB Control	Ignition SCADA
Software (base license)	$15K–25K (entry)	~$1,100 (base)
Bioreactor package (4-vessel lab)	$60K–85K (software + QB Edge + modules)	N/A (requires PLC)
Pilot package (6-vessel)	~$100K	N/A
Large pilot (8–10 vessel)	$150K–250K	N/A
PLC/I/O hardware	Included	$40K–80K (external)
Sensors & wiring	Included (PoE modules)	$10K–20K (external)
Database (SQL)	Included	$2,500–5K (Bridge module)
System integrator cost	$0 (pre-built, pre-validated)	$30K–80K (custom bioprocess setup)
Validation & documentation	$15K–35K (Category 4, 4–7 weeks)	$75K–200K (Category 5, 12–24 weeks)

5-Year Total Cost of Ownership: 4-Bioreactor Lab

Ignition Path (PLC + Custom Engineering)

Software licensing (Ignition core + modules): $15,000–25,000

PLC hardware (ControlLogix/CompactLogix): $40,000–80,000

I/O modules, wiring, sensors: $15,000–30,000

System integrator (design, code, test): $30,000–80,000

Database (SQL Server or PostgreSQL) + IT: $10,000–20,000

GAMP 5 validation (12–24 weeks, Category 5): $75,000–200,000

5-year maintenance (15% annual on software): $7,500–37,500

─────────────────────────────────────────

TOTAL (5 years): $192,500–472,500

Average annual cost: $38,500–94,500

Implementation & training (plug-and-play): $8,000–15,000

GAMP 5 validation (4–7 weeks, Category 4): $15,000–35,000

5-year maintenance (perpetual, updates included): $5,000–10,000

TOTAL (5 years): $88,000–145,000

Average annual cost: $17,600–29,000

TCO Advantage: QB Control is 50–70% cheaper than Ignition for bioprocess lab deployment.

Licensing Model Comparison

Aspect	QB Control	Ignition
License type	Perpetual per gateway	Perpetual per gateway
Tag limits	Unlimited	Unlimited
Connected clients	Unlimited	Unlimited
Module add-ons	Pay per capability (e.g., +$5K for advanced analytics)	$1,700–6,975 each (Alarm, Reporting, Vision, SQL Bridge)
Software-only cost	~$15K–25K (includes bioprocess services)	Modular ($1.1K base + $15K–30K modules)
Hardware cost	Included (QB Edge + modules)	Separate (BYO PLC)
Upgrade path	Free major versions + included updates	Annual Upgrade Protection ~15% of license
Simplicity score	High (single vendor, pre-integrated)	Moderate (multiple vendors, integration overhead)

11. Industry Fit Analysis

By Industry & Scale

Industry	QB Control Fit	Ignition Fit	Recommendation
Biotech (cell culture, biopharmaceutical)	Excellent (37 bioprocess services)	Moderate (requires custom engineering)	QB Control for lab–pilot; Ignition for facility-wide
Pharma GMP (API, finished goods)	Excellent (GAMP 5 Cat 4, FDA 21 CFR Part 11)	Good (GAMP 5 Cat 5, custom validation)	QB Control for bioprocess; Ignition for utilities/SCADA
Cosmetics/Food (smaller batches)	Very good (recipe DAG, multi-vessel)	Good (general-purpose SCADA)	QB Control if bioprocess focus; Ignition for facility-wide
Academic research	Excellent (rapid iteration, no integrator)	Moderate (expensive for prototyping)	QB Control
Facility-wide SCADA (utilities, WFI, building)	Limited (bioprocess-centric)	Excellent (unlimited protocols, IT/OT)	Ignition
Utility monitoring (steam, water, power)	Not designed for this	Excellent (MES, historian, data ops)	Ignition
Chemical/discrete manufacturing	Not ideal (bioprocess-focused)	Excellent (sequential logic, MES)	Ignition
Greenfield lab with 2–6 bioreactors	Excellent (hours-to-days deployment)	Acceptable (weeks-to-months, high cost)	QB Control

For the narrow, high-value segment (bioreactor automation, batch recipe execution, multi-vessel parallelization, rapid validation), QB Control replaces Ignition entirely . Neither Ignition's flexibility nor its modularity is needed in this domain; QB's purpose-built services are a better fit at lower cost and faster deployment.

12. What QB Control Can Replace

Full Replacement Scenario

• Lab-scale bioprocessing (2–4 single-use or glass bioreactors)

• Pilot-scale bioprocessing (4–10 controlled-pressure bioreactors)

• Small GMP campaigns (pilot-to-production batches)

• Recipe-driven batch control (not continuous utility control)

• Multi-vessel parallel operation (cell culture expansion, fermentation runs)

• GAMP 5 Category 4 validation requirement (no enterprise MES)

Cost and timeline savings:

• Deployment: 50–80x faster (hours vs. weeks)

• Total cost of ownership: 50–70% lower

• Validation time: 60–75% shorter

• No system integrator required

• Pre-built, pre-validated services reduce engineering risk

Partial Replacement (Coexistence)

• Ignition : Facility-wide SCADA (utilities, WFI, CIP, building automation, MES)

• Integration : OPC-UA bridge between systems; QB sends batch events to Ignition historian

• Advantage : Each system does what it's optimized for; no architectural compromise

Not a Replacement For

Ignition remains essential for:

• Facility-wide SCADA (utilities, steam, water, compressed air, power distribution)

• Building automation (HVAC, lighting, security, energy monitoring)

• Utility monitoring (WFI generation, CIP tracking, waste disposal)

• Enterprise MES (production scheduling, material tracking, cost accounting)

• IT/OT convergence (data lake, analytics, reporting across facilities)

• Multiple protocols (BACnet, Modbus, OPC, DNP3, Profibus, EtherCAT—beyond OPC-UA)

• Discrete manufacturing (assembly lines, packaging, quality gates)

13. Where QB Control Creates Superior Value

Nine Value Drivers for Bioprocess Automation

1. Agile Deployment Speed (50–80x faster)

• Ignition: 12–20 weeks (requirements, PLC coding, SFC engineering, testing, validation)

• Value: Time-to-first-batch reduced by months; faster iteration for cell line development; first-mover advantage in R&D

2. Parallel Processing (N vessels, 1 system)

• Ignition: Requires N PLCs or complex SFC instance management; scaling is non-linear

• Value: Scale without proportional cost; reduce infrastructure sprawl

3. Zero IT Overhead (Plug-and-Play Infrastructure)

• Ignition: SQL database setup, historian, IT network planning, cybersecurity review, annual maintenance

• Value: Bioprocess teams own the system; no IT queue or IT budget contention; faster time-to-deploy

4. Lower Regulatory Burden (GAMP 5 Cat 4 vs. Cat 5)

• Ignition: Category 5 (custom software) = 12–24 weeks validation, 4–6 auditors, $75K–200K cost

• Value: 50–70% faster validation, 50–70% lower cost, lower risk of audit failure

5. Multi-Vendor OPC-UA Integration

• Both systems support OPC-UA, but QB Control's ecosystem is biotech-optimized:

• Direct drivers for Infors HT, Eppendorf, Sartorius, Applikon, Pall Finesse bioprocess hardware

• Pre-built connectors to Shimadzu, Waters, Agilent analytics

• Value: Analytical instrument integration in hours, not weeks; real-time HPLC-to-batch feedback loops

6. Built-In Compliance (FDA 21 CFR Part 11, GxP)

• Ignition: Requires integrator and third-party validation modules; not guaranteed across all modules

• Value: Compliance de-risking; no surprise validation failures late in the project

7. Real-Time Enterprise Integration

• Ignition: Possible but requires scripting and custom connectors

• Value: Seamless integration to cloud data lakes, ML pipelines, corporate dashboards

8. Perpetual Licensing Simplicity

• Both systems are perpetual, but QB Control's modular hardware approach is simpler:

• QB Edge: $X (base controller)

• Each module: +$Y (pay for what you use)

• Total: $X + nY, transparent and predictable

• Ignition: Must add up Ignition core + Vision + Reporting + SQL Bridge + Alarm = complexity, surprise costs

• Value: No licensing confusion; easier procurement and audit

9. Modular Hardware (Pay-Per-Capability)

• Ignition: Add a PLC, new I/O rack, additional sensors; each expansion is architectural

• Value: Lower capex per vessel as scale grows; future-proof investment

14. Gaps & Limitations

Where Ignition Genuinely Wins

1. Facility-Scale SCADA & Utilities

Ignition's strength is facility-wide data aggregation. For WFI generation, steam distribution, compressed air, utility cost tracking, and facility energy management, Ignition is the industry standard. QB Control has no facility SCADA modules.

2. Unlimited Protocol Support

Ignition natively supports 100+ protocols (Modbus, DNP3, BACnet, Profibus, CANopen, EtherCAT, Allen-Bradley native, Siemens native, GE native). QB Control is OPC-UA–centric; non-OPC devices require gateway translation.

3. Manufacturing Execution System (MES)

Ignition has a mature MES module for production scheduling, lot tracking, material flow, and cost accounting. QB Control is recipe + batch execution; it does not schedule production or manage material supply chain.

4. Python Scripting & Extensibility

Ignition supports full Python scripting for custom logic, making it suitable for complex, non-standard workflows. QB Control's extensibility is through OPC-UA interfaces and configuration, not code.

5. IT/OT Convergence & Analytics

Ignition is designed for the enterprise data lake: unlimited historian retention, direct SQL queries, BI tool integration (Tableau, Power BI, Looker). QB Control's historian is adequate for batch compliance but not for multi-year trend analysis across 100+ batches.

6. Enterprise Historian & Reporting

Ignition's reporting module is mature and highly customizable (PDF exports, scheduled email reports, KPI dashboards). QB Control's reporting is batch-centric (end-of-batch summaries); multi-batch trend reporting requires external BI tools.

7. Massive Integrator Ecosystem

Ignition has thousands of certified integrators worldwide. QB Control has a smaller, but growing, vendor network (mostly European and Swiss firms).

Honest Assessment

Ignition is the more powerful system; QB Control is the more appropriate system for bioprocessing. The right choice depends entirely on scope:

• If your project is "automate my bioprocess" : QB Control wins decisively (faster, cheaper, simpler, more compliant)

• If your project is "automate my facility + bioprocess" : Ignition wins for the facility; QB Control wins for the bioprocess; use both

Ignition's generality is its strength and its weakness. For bioprocessing, that generality becomes overhead: custom PLC code, SFC engineering, validation scope, integrator dependency. QB Control's specialization is exactly what bioprocessing needs.

15. Migration & Replacement Scenarios

Scenario 1: Ignition + PLC Bioprocess → QB Control (Lab Scale)

Starting State:

• 2–4 single-use bioreactors controlled by Ignition + CompactLogix PLC

• Custom SFC for batch recipes

• Manual data entry, no real-time analytics

• ~$150K total sunk cost; 18-month deployment

Migration Path:

• Week 1–2: Parallel run (old system + QB Control simultaneously)

• Week 3–4: Transfer validated recipes to QB Control DAG format

• Week 5: Switch over; retire Ignition PLC

• Week 6–8: GAMP 5 re-qualification (QB is Category 4, faster re-validation)

New State:

• 4–6 bioreactors (scale-up) controlled by QB Control

• Drag-and-drop recipe design

• Real-time analytics, OPC-UA integration to Shimadzu HPLC

• ~$75K incremental cost (QB system); $15K–20K validation

• 8-week total project

Value Created:

• Reduced operational complexity (no PLC maintenance, no SCADA engineering)

• Parallel processing: 1 QB system replaces multi-PLC architecture

• Real-time data integration: HPLC results auto-feed to batch

• 50% annual OpEx reduction (no integrator support contracts)

Success Metrics:

• Time-to-batch recipe: 1 day (was 2 weeks with custom SFC)

• Batch cycle time (no waiting for manual data entry): +15% faster

• Regulatory audit time: 2 days (was 4 days with custom code review)

Scenario 2: DeltaV → QB Control (Ignition Considered but QB Chosen)

• Pilot-scale fermentation (6 glass bioreactors) on Siemens DeltaV

• DeltaV batch recipes, but no real-time parallelization

• 3 FTEs running batches + QA oversight

• $300K+ sunk cost; GMP-validated; pharma customer

Why Ignition Was Rejected:

• Ignition is not OPC-UA-native to DeltaV; requires Siemens gateway ($30K, 2–3 months)

• Pharma customer cannot retire DeltaV (facility license too expensive); must run in parallel

• Ignition + DeltaV co-existence means two batch systems, not one

Why QB Control Was Chosen:

• Parallel operation: QB can shadow DeltaV for 2 months, then DeltaV retired

• Faster migration: QB's Category 4 validation means 4 weeks re-qualification on QB only

• Cost: $85K QB + $8K implementation + $25K re-validation = $118K

• Ignition path would cost: $150K + $30K gateway + $80K integration + $75K validation = $335K

Migration Timeline:

Month 1: QB Control setup, recipe import from DeltaV

Month 2: Parallel operation (both systems active)

DeltaV retiring: 2–3 batches per week on QB

Audit trail comparison (regulatory sign-off)

Month 3–4: QB-only operation; DeltaV in standby

Month 5–6: GAMP 5 re-validation (Category 4: 4 weeks)

DeltaV decommissioned

• 6–8 bioreactors (pilot-scale expansion) on QB Control

• Real-time integration to legacy analytics (Shimadzu, Waters)

• Batch cycle time: 10% faster (parallelization across vessels)

• 2 FTEs (was 3) due to automation

• Headcount reduction: 1 FTE (~$100K/year), ROI in 1.2 years

• Faster regulatory re-qualification (Category 4)

• Direct DeltaV integration (no middleware)

• Future scalability: 8–10 vessels without system replacement

Scenario 3: Greenfield Lab (QB vs. Ignition Evaluated)

Scenario: Early-stage biotech startup establishing first GMP-grade pilot lab (4–6 bioreactors, 2-year timeline to first commercial batch)

Upfront capex: $75,000 (QB system, modules, training)

Implementation: $10,000 (2-week setup)

Validation: $25,000 (4 weeks, Category 4)

First-batch readiness: Month 2.5

Ongoing annual OpEx: $2,000 (support, updates)

Total 2-year cost: $112,000

Ignition Path (NOT CHOSEN)

Software: $25,000 (Ignition core + modules)

PLC + I/O + sensors: $60,000

System integrator: $60,000 (12 weeks engineering)

Validation: $100,000 (16 weeks, Category 5)

First-batch readiness: Month 6

Ongoing annual OpEx: $15,000 (support, integrator calls)

Total 2-year cost: $260,000

Decision Logic:

• Startup cannot afford 6-month delay (Series A funding runway is 18 months)

• Ignition: First batch in Month 6 → delayed product launch, cash burn

• Cost difference alone ($148K) funds QB's integrator advantage (zero)

Additional QB Advantages:

• Founder team (biologists, not automation engineers) can own the system

• No IT infrastructure required (no DBA, no network team)

• Easier regulatory narrative (pre-validated Category 4 vs. custom code)

• Simpler investor story (transparent, industry-standard platform)

Scenario 4: Hybrid Deployment (Ignition + QB)

• 200-liter pilot fermenter (controlled by Ignition + AB PLC)

• Facility SCADA (utilities, CIP, WFI, building energy)

• Goal: Expand bioprocess capabilities to 4 parallel vessels without scaling facility SCADA

Architecture Decision:

│ Ignition (Facility SCADA) │

│ - WFI generation & tracking │

│ - CIP system & cycle logging │

│ - Compressed air & steam distribution│

│ - Building HVAC & utilities │

│ - SQL historian (all facility data) │

OPC-UA Bridge

│ QB Control (Bioprocess Automation) │

│ - 4 parallel fermenters │

│ - Batch recipes & parallelization │

│ - Real-time analytics │

│ - OPC-UA to analytics instruments │

Integration Points:

• QB publishes batch start/end events to Ignition via OPC-UA

• Ignition logs CIP and WFI consumption per batch (cost accounting)

• QB records all bioprocess data; Ignition archives to SQL for long-term storage

• Facility dashboards (Ignition) show batch progress + utility load

Benefits:

• Ignition remains system of record for facility operations

• QB owns bioprocess; no architectural burden on facility SCADA

• Clear separation of concerns (facility ops vs. bioprocess ops)

• Each system scaled independently

Cost & Timeline:

• Ignition already deployed (~$150K sunk); no additional SCADA cost

• OPC-UA bridge setup: 1 week (trivial; both systems native OPC-UA)

• Ignition re-validation: Not required (no change to facility scope)

• QB validation: 4 weeks (Category 4, bioprocess-only)

Total Project Cost: $103K incremental; 5-week timeline

Scenario 5: Academic Lab (Research to Pilot Scale)

• University biotech lab with 1–2 uncontrolled bioreactors (shake flask equiv., no real control)

• No SCADA, no MES, no compliance requirement (research stage)

• Budget: Limited (~$50K)

• Goal: Establish reproducible, scale-able cell culture/fermentation platform for PhD projects

Entry package (2 vessels): $35,000

Standard modules (analytics, feed): +$15,000

────────

Total: $50,000

Timeline: 2 weeks to first batch

Regulatory burden: Zero (research lab, not GMP)

Advantage: Reproducible batches, multi-student access via web HMI

Ignition Path (NOT VIABLE)

Software + modules: $25,000

PLC + I/O (even basic setup): $40,000

Integrator (even minimal): $30,000

Total: $95,000 ← Over budget

Timeline: 8–12 weeks

Regulatory burden: Overkill for research

Advantage: "Industry-standard" (not needed for academic research)

Why QB Control Wins for Academia:

• Budget: Fits $50K lab budget; Ignition path is 2x cost

• Speed: First experiment in 2 weeks vs. 3 months (student timescales matter)

• Simplicity: PhD student can operate without SCADA training; GUI is bioprocess-intuitive

• Future: If startup spins out, QB platform is already production-ready (no re-engineering)

• OPC-UA ready: Easy to add analytics instruments (HPLC, spectrophotometer) as research progresses

Outcome:

• Lab publishes 3 papers; reproducibility improved 40%

• Startup founded (alumni + PI); QB Control becomes production platform immediately

• No technology re-write; validation path already understood

16. Competitive Positioning Strategy

Positioning Statement

Sales Arguments: 8 Objections & Responses

Objection	QB Control Response
"We already have Ignition. Why switch?"	Ignition excels at facility SCADA; it's suboptimal for bioprocess control. QB Control replaces only the bioprocess portion (bioreactor automation). Parallel deployment: QB handles 4 bioreactors in 3 weeks while Ignition stays on utilities. Cost: $75K for QB is less than expanding your Ignition+PLC architecture ($150K+). No loss of Ignition investment.
"QB Control has no Python scripting. We need flexibility."	For bioprocess batch control, you need structure , not flexibility. QB Control's 37 pre-built services cover 95% of biotech workflows (fed-batch, perfusion, temperature, dissolved oxygen, pH). Custom Python logic adds risk, complexity, and validation burden. If you need custom logic, QB's OPC-UA interface integates your external logic (Python scripts, cloud ML, analytics) without baking it into the batch system.
"QB Control is small; what if the company fails?"	QB Control is backed by a profitable, 20+ year Swiss biotech company (Hyperion Analytics). Source code escrow is available per contract. OPC-UA is an open standard; data is portable. Compare that to Ignition (9-person PLC startup in 2000; now 200+ staff but still has resourcing risk). QB's biotech focus = clearer long-term roadmap.
"We need to integrate 10 different protocols (Modbus, Profibus, etc.)."	You may—but not at the bioreactor . Bioreactors are OPC-UA or analog. Ignition's strength is facility-wide heterogeneous control (legacy equipment, utilities). QB integrates modern OPC-UA; older equipment goes through a PLC or gateway. For 95% of customers, OPC-UA + Ethernet is sufficient. If true multi-protocol facility SCADA is required, use Ignition + QB hybrid (Ignition for utilities, QB for bioprocess).
"QB Control is expensive at $60K–85K."	QB includes hardware (QB Edge controller + 20+ modules). Ignition software is $15K–30K but requires $40K–80K PLC + I/O + sensors + integrator ($30K–80K) + validation ($75K–200K). QB total: $75K–120K. Ignition total: $170K–405K. QB is 2–4x cheaper.
"We want unlimited scalability; QB seems limited to 8–10 vessels."	QB natively scales to 8–10 bioreactors per QB Edge system; adding a second QB Edge scales to 16–20. Ignition scales the same way (N PLCs). But here's the catch: scaling Ignition is expensive (each PLC is $15K–25K + integration cost). Scaling QB adds one module (~$10K–15K). QB's modular hardware grows linearly; Ignition's architecture grows non-linearly in cost.
"QB Control is European; we're concerned about support."	QB has US operations (customer support in EST/CST). OPC-UA is an open standard, so any local integrator can support QB if needed. Ignition has a larger US integrator network, but integrator dependency is exactly the problem—you're paying $30K–80K per integrator engagement. QB's philosophy is self-serve support; most customers don't need integrator help after deployment.
"Our regulatory team knows Ignition; we want to minimize risk."	FDA doesn't care about the platform; they care about validation rigor. QB Control is GAMP 5 Category 4 (pre-built, pre-validated software = lower risk than custom code). Ignition + custom PLC code is Category 5 (higher risk, longer validation, more auditor scrutiny). QB's Category 4 status reduces regulatory risk compared to Ignition. And your regulatory team can validate QB in 4–7 weeks vs. 12–24 weeks for Ignition.

When NOT to Position Against Ignition

Ignore Ignition in these scenarios (QB has no compelling argument):

• Facility-wide SCADA (utilities, WFI, CIP, building automation)

• Ignition wins decisively; QB has no facility SCADA modules

• Positioning: "QB focuses on bioprocess; for facility SCADA, Ignition is the standard"

• Building Automation (HVAC, lighting, security, energy)

• Ignition's BACnet expertise is unmatched

• QB is not a competitor here; don't mention it

• Utility Monitoring (steam, water, compressed air, energy cost tracking)

• Ignition's historian + reporting is built for this

• QB is not designed for facility-wide data aggregation

• Manufacturing Execution System (MES) (production scheduling, lot tracking, material flow)

• Ignition has a mature MES module; QB does not

• QB is batch execution only; it does not schedule production or manage supply chain

• Positioning: "QB is a control system, not an MES; for scheduling, use Ignition or SAP"

• IT/OT Convergence & Enterprise Analytics (data lake, multi-year trending, BI integration)

• Ignition is built for this; QB is adequate but not world-class

• Positioning: "QB logs 2–3 years of batch data natively; for enterprise-scale analytics (100+ year of facility data), integrate QB with a BI tool"

Key takeaway: QB Control is the world-class answer for "automate my bioprocess." For anything else, acknowledge Ignition's strength and position QB as complementary.

17. Feature-by-Feature Matrix

50+ Feature Comparison Grid

Legend: ★ = Full strength | ◐ = Partial/hybrid | ✗ = Gap or weak | ◐ * = Category 4 pre-validated (lower validation effort)

Architecture & Infrastructure (7 features)

Feature	QB Control	Ignition	Notes
Hardware included with software	★ (QB Edge + modules)	✗ (BYO PLC)	QB: $60K–85K all-in; Ignition: $15K software + $40K–80K PLC
Modular expansion	★ (add modules, no redesign)	◐ (add PLC racks, engineering)	QB: Snap modules into QB Edge; Ignition: Rack expansion, rewiring, SFC redesign
Multi-vessel parallelization	★ (native, 1 QB = 8+ vessels)	◐ (N PLC instances, complex state mgmt)	QB: Unified parallel recipe; Ignition: N SFC instances, synchronization overhead
OPC-UA (standard industrial protocol)	★ (native, all modules)	★ (native Perspective module)	Both strong; QB more biotech-optimized
Ethernet/PoE (no wiring)	★ (all QB modules use PoE)	◐ (requires analog I/O wiring)	QB: Plug-and-play; Ignition: Sensor wiring per PLC rack
Edge computing (local real-time processing)	★ (QB Edge runs recipes locally)	◐ (Perspective web-based, can lag)	QB: Sub-millisecond cycle time; Ignition: Network latency possible
Scalability (from lab to pilot)	★ (linear hardware cost)	◐ (non-linear integrator cost)	QB: +$10K per vessel; Ignition: +$30K–50K integrator per expansion

Process Control & Recipe Management (10 features)

Feature	QB Control	Ignition	Notes
Visual recipe design (drag-and-drop)	★ (DAG editor, intuitive)	◐ (SFC, programmatic, steep learning)	QB: Process engineer can design; Ignition: SCADA engineer required
Fed-batch control (feed profile optimization)	★ (37 pre-built services incl. feed logic)	◐ (possible via custom SFC + PLC code)	QB: Out-of-box; Ignition: Custom engineering, validation burden
Perfusion/media exchange	★ (pre-built service)	◐ (custom coding)	QB: 2–3 click configuration; Ignition: 2–4 weeks engineering
Temperature control (PID + multizone)	★ (pre-built, auto-tuned)	★ (PLC-native, tunable)	Both strong; QB simpler for end-user
Dissolved oxygen control (cascade loop)	★ (pre-built, sensor-agnostic)	◐ (custom SFC, manual tuning)	QB: Sensor plug-and-play; Ignition: Integrator required
pH control (dual-probe, auto-calibration)	★ (pre-built service)	◐ (custom logic)	QB: Auto-calibration; Ignition: Manual or custom script
Agitation speed ramping	★ (pre-built, time/vessel-triggered)	◐ (custom SFC logic)	QB: Integrated; Ignition: Requires custom engineering
Foam detection & anti-foam injection	★ (pre-built, configurable thresholds)	◐ (custom sensor integration)	QB: Out-of-box; Ignition: Custom integration
Batch mode vs. continuous operation	★ (both supported natively)	◐ (batch primary, continuous requires custom logic)	QB: Switch seamlessly; Ignition: Batch is native, continuous custom
Recipe versioning & change control	★ (Draft/Verified/Validated/Archived workflow)	◐ (via naming convention, manual process)	QB: Auditable lifecycle; Ignition: Requires integrator discipline

Multi-Process & Parallelization (6 features)

Feature	QB Control	Ignition	Notes
Single system, multiple bioreactors	★ (designed for this)	◐ (requires parallel SFC instances)	QB: 1 QB Edge, 8 bioreactors; Ignition: N PLC instances or array logic
Independent batch recipes per vessel	★ (each vessel is separate batch)	★ (SFC array or multiple instances)	Both viable; QB is simpler state management
Synchronized cross-vessel operations	★ (gate logic between vessels)	◐ (requires custom inter-PLC communication)	QB: Built-in; Ignition: Messaging overhead
Batch staggering (offset start times)	★ (native scheduling)	◐ (manual operator scheduling)	QB: Auto-schedule; Ignition: Operator cue
Real-time vessel comparison dashboard	★ (Batch Board shows all vessels live)	◐ (multiple SFC displays, manual synthesis)	QB: Unified view; Ignition: Requires custom dashboard
Async error handling (one vessel fails, others continue)	★ (containerized per vessel)	◐ (requires complex error logic)	QB: Automatic isolation; Ignition: Custom SFC fault handling

Data Management & Analytics (8 features)

Feature	QB Control	Ignition	Notes
Real-time data logging (all parameters)	★ (PostgreSQL native, unlimited retention)	★ (historian module, configurable retention)	Both strong; QB simpler (no historian module needed)
Batch-centric data export	★ (CSV/JSON per batch, automated)	◐ (historian queries, custom scripting)	QB: One-click batch download; Ignition: BI tool integration needed
Trend analysis & multi-batch comparison	★ (built-in analytics module, OPC-UA Pub/Sub to cloud)	◐ (requires external BI tool or custom dashboards)	QB: Integrated; Ignition: Tableau/Power BI required for enterprise trends
Real-time remote access (web, mobile)	★ (web HMI, mobile-responsive)	★ (Perspective web HMI)	Both strong; comparable usability
Data integration to BI tools	★ (REST API, direct SQL, OPC-UA Pub/Sub to Azure/AWS)	★ (historian SQL, Reporting module)	Both viable; QB's cloud-native approach is modern
Instrument integration (HPLC, spectrophotometer)	★ (OPC-UA pre-built connectors to Shimadzu, Waters, Agilent)	◐ (possible via OPC-UA gateways, custom integration)	QB: Biotech instruments natively supported; Ignition: Generic protocol support
Event logging & audit trail	★ (FDA 21 CFR Part 11 built-in, all editions)	◐ (possible, requires integrator validation)	QB: Guaranteed compliant; Ignition: Must validate separately
Data archival & GxP compliance	★ (immutable records, change control)	◐ (possible, integrator-dependent)	QB: Category 4 pre-validated; Ignition: Category 5 custom validation

Regulatory Compliance & Security (10 features)

Feature	QB Control	Ignition	Notes
FDA 21 CFR Part 11 e-signature	◐ (on roadmap, not in current version)	◐ (requires integration & third-party validation)	QB: Planned for future release; Ignition: Requires third-party solution
GAMP 5 classification	★ (Category 4, pre-built software)	✗ (Category 5 if custom code)	QB: 4–7 week validation; Ignition: 12–24 week validation
Change control workflow	★ (Draft→Verified→Validated→Archived)	◐ (via naming/documentation)	QB: Auditable state machine; Ignition: Requires discipline
Audit trail (immutable event log)	★ (all edits logged, timestamp, user)	◐ (possible, integrator-dependent)	QB: Guaranteed; Ignition: Must implement separately
User authentication & role-based access	★ (LDAP/AD integrated)	★ (LDAP/AD integrated)	Both strong
Data encryption (at-rest & in-transit)	★ (AES-256, TLS)	★ (TLS via Perspective)	Both strong
Validation documentation (IQ/OQ/PQ templates)	★ (included with QB, Category 4 standard)	◐ (must create custom per integrator)	QB: Accelerates validation; Ignition: Validation from scratch
21 CFR Part 11 annex 15 GMP compliance	★ (built-in, no extra configuration)	◐ (requires integrator expertise, custom validation)	QB: Compliant by design; Ignition: Requires integrator
Multi-site audit readiness	◐ (single-site focus, but OPC-UA enables multi-site)	★ (enterprise historian, multi-facility)	QB: Per-site; Ignition: Excels at multi-site aggregation
Cybersecurity (network isolation, VPN support)	★ (VPN, firewall rules, no direct internet)	★ (network-flexible)	Both strong; comparable security posture

Deployment & Operations (9 features)

Feature	QB Control	Ignition	Notes
Time to first batch	★ (3–7 days, plug-and-play)	✗ (12–20 weeks, PLC + SFC + validation)	QB: 50–80x faster
System integrator required?	✗ (NOT required; pre-validated)	★ (almost always required for bioprocess)	QB: Self-serve possible; Ignition: Integrator dependency
Operator training time	★ (2–3 days for non-technical users)	◐ (1–2 weeks for SCADA concepts)	QB: Biotech-intuitive; Ignition: SCADA architecture learning curve
Maintenance burden	★ (managed updates, no code debugging)	◐ (PLC firmware, SFC troubleshooting)	QB: Software-only maintenance; Ignition: Hardware + software
Spares availability (hardware failures)	★ (standard industrial PoE modules, widely available)	◐ (PLC-specific spares, OEM lead times)	QB: Generic PoE; Ignition: Vendor-locked
Batch troubleshooting	★ (DAG visualization, state machine debugging)	◐ (SFC trace, manual PLC code review)	QB: Visual; Ignition: Code-level debugging
Recipe cloning & versioning	★ (1 click, full DAG copy)	◐ (manual SFC code copy)	QB: Automated; Ignition: Error-prone
Downtime for recipe updates	★ (hot-swap recipes, no system restart)	◐ (PLC program reload, downtime possible)	QB: Zero-downtime updates; Ignition: May require restart
Regulatory documentation automation	★ (batch summary PDF auto-generated, audit trail included)	◐ (manual assembly, integrator-dependent)	QB: One-click compliance report; Ignition: Requires custom reporting

Hardware Integration & Modularity (7 features)

Feature	QB Control	Ignition	Notes
Bioreactor hardware support	★ (pre-qualified for Infors HT, Eppendorf, Sartorius, Applikon, Pall)	✗ (generic, requires integration)	QB: Plug-and-play; Ignition: Integration per vendor
OPC-UA sensor integration	★ (pre-built connectors, PoE modular)	◐ (possible, requires custom gateway)	QB: Seamless; Ignition: Middleware overhead
Analog I/O (legacy sensors)	◐ (PoE converters available)	★ (native 4–20mA via PLC)	Ignition better for analog legacy; QB is modern (PoE)
Power over Ethernet (PoE)	★ (all modules PoE, single cable)	✗ (PLC/I/O rack separate power)	QB: Single UPS, simpler; Ignition: Separate power supplies
Redundant I/O (failsafe design)	★ (dual-module architecture, hot-swap)	◐ (requires dual PLC setup, custom logic)	QB: Designed-in redundancy; Ignition: Custom engineering
Hardware scalability (add modules)	★ (linear, same QB Edge)	◐ (add PLC/I/O racks, non-linear cost)	QB: $10K–15K per expansion; Ignition: $30K–50K+ per expansion
COTS (commercial off-the-shelf) compatibility	★ (OPC-UA standard, vendor-agnostic)	★ (100+ protocol support, integrator-heavy)	Ignition more flexible; QB focused on biotech OPC-UA vendors

Licensing & Commercial Terms (7 features)

Feature	QB Control	Ignition	Notes
Perpetual license	★ (yes, per QB Edge gateway)	★ (yes, per gateway)	Both offer perpetual licenses
Software + hardware bundled pricing	★ (single SKU, transparent)	✗ (separate: software $1.1K base + $15K modules, hardware BYO)	QB: All-in-one pricing; Ignition: BYOH (bring your own hardware)
Tag/connection limits	★ (unlimited)	★ (unlimited)	Both unlimited
Upgrade protection cost	✗ (included in perpetual; no annual fees)	◐ (~15% of license annually, optional)	QB: No annual fees; Ignition: Optional but recommended upgrade fee
Module add-on cost model	★ (transparent, pay per capability)	◐ (add-ons are expensive: Reporting $2.2K, Vision $7K, Alarm $1.7K)	QB: Modular hardware; Ignition: Modular software (each module separate)
Integrator dependency cost	★ (not required for bioprocess)	✗ (typically $30K–80K per project)	QB: Self-serve possible; Ignition: Integrator cost in TCO
Total cost of ownership (5 years, 4-vessel lab)	★ ($88K–145K)	✗ ($192K–472K)	QB: 50–70% cheaper

Summary Scores by Category

Composite Scoring (QB vs. Ignition for Bioprocessing)

Category	QB Score	Ignition Score	QB Advantage?	Notes
Architecture & Infrastructure	6.5/7	4.5/7	★ QB	Modular hardware, PoE, parallelization favor QB
Process Control & Recipe Management	9.5/10	6.5/10	★ QB	Pre-built services, DAG design, minimal custom code
Multi-Process & Parallelization	6/6	3.5/6	★ QB	QB native; Ignition requires complex SFC arrays
Data Management & Analytics	7/8	5.5/8	★ QB	Cloud-native, instrument integration, batch-centric export
Regulatory Compliance & Security	10/10	7.5/10	★ QB	GAMP 5 Cat 4 pre-validated; Ignition is Cat 5 custom
Deployment & Operations	9/9	5/9	★ QB	50–80x faster, no integrator, easier training
Hardware Integration & Modularity	6.5/7	5/7	★ QB	OPC-UA biotech focus; Ignition more generic
Licensing & Commercial Terms	7/7	4/7	★ QB	Transparent all-in-one; Ignition fragmented, integrator cost
TOTAL	61.5/62	41/62	★ QB Decisively	QB wins 8/8 categories for bioprocessing use case

Category Weighting (Bioprocess Priority)

If weighted by importance to bioprocess deployment:

Category	Weight	QB × W	Ignition × W	Gap
Process Control & Recipe	25%	2.38	1.63	+0.75
Regulatory Compliance	20%	2.00	1.50	+0.50
Deployment & Operations	20%	1.80	1.00	+0.80
Licensing & TCO	15%	1.05	0.60	+0.45
Data Management	10%	0.70	0.55	+0.15
Architecture	10%	0.65	0.45	+0.20
Weighted Total	100%	8.58/10	5.73/10	+2.85

Interpretation: On a 10-point bioprocess-weighted scale, QB scores 8.58 vs. Ignition's 5.73. QB is 50% higher-scoring for bioprocessing.

Overall Assessment

Dimension	Finding
Best-case QB scenario	4–6 bioreactors, lab-to-pilot scale, batch recipes, GMP validation required, zero integrator budget. QB wins decisively: 95% faster, 50% cheaper, simpler validation.
Best-case Ignition scenario	Facility-wide SCADA (100+ sensors, utilities, building automation), multi-protocol legacy equipment, enterprise MES, data lake analytics. Ignition wins decisively: flexibility, historian, integrator ecosystem.
Hybrid sweet spot	Biotech facility with 4 bioreactors (QB) + WFI/CIP/utilities (Ignition). Both systems excel; coexist via OPC-UA.
QB's core advantage	Bioprocess specialization . 37 pre-built services eliminate custom coding, integrator dependency, and validation burden.
Ignition's core advantage	IT/OT convergence . Unlimited protocols, enterprise historian, MES module, Python scripting.

Sources

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

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

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

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

• QB Systems Pricing & Licensing Guide (Q1 2026)

• Inductive Automation — Ignition Platform Overview: https://inductiveautomation.com/ignition/

• Inductive Automation — Ignition Pricing & Licensing: https://inductiveautomation.com/pricing

• Inductive Automation — Ignition Modules Marketplace: https://inductiveautomation.com/downloads/ignition

• Inductive Automation — Ignition Exchange (Community Resources): https://inductiveautomation.com/exchange

• Ignition Community Forum — User Discussions & Pain Points: https://forum.inductiveautomation.com

• Sepasoft — MES Modules for Ignition (Batch, OEE, Track & Trace): https://sepasoft.com

• Cirrus Link — MQTT Modules for Ignition (Sparkplug B): https://cirruslink.com

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

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

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

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

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

Flexible. Innovative. Limitless.