QB Control vs Sartorius MFCS 4 Comparison

At a glance

Dimension	QB Control	Sartorius MFCS 4
What it is	Turnkey, software-defined bioprocess platform (hardware + software)	GMP SCADA / data-management software layer
Hardware	◆ QB Modules included; or reuse existing PLC via OPC-UA	Software only; bioreactors + Windows/SQL estate bought separately
Reconfiguration	◆ Made in the software layer (drag-and-drop)	Changes span DCU/PLC + OPC tags + SCADA config
Deployment	◆ Days (auto-discovery, plug-and-play)	Weeks–months (install, configure, validate, services)
Access	◆ Any browser; secure remote access; unlimited users	Windows clients via RDP (per-client, up to 30)
Electronic signatures	Roadmapped (not yet released)	◆ Available today
Licensing	◆ Perpetual, all-inclusive; optional support	Base + per-module + per-client + services
Best for	Agile, multi-vendor lab-to-pilot development	Standardized Sartorius production fleet; GMP records

Table of Contents

1. Executive Summary
2. Two Models: Supervisory Layer vs. Software-Defined System
3. Operational Agility for Process Development
4. Control Content & Recipes
5. Compliance & Data
6. Cost, Licensing & Deployment
7. Where Sartorius MFCS 4 Wins
8. Recommendation

Appendices — Feature Snapshot · Sources

---

1. Executive Summary

Sartorius MFCS 4 is a mature, GMP-proven supervisory and data-management layer for a standardized Sartorius bioreactor fleet — strong on electronic-signature compliance, enterprise historization, and analytics, delivered as Windows/SQL-Server software with per-module and per-client licensing and integration services.

QB Control is a turnkey, vendor-neutral, browser-based bioprocess platform — hardware and software co-engineered so that control strategies, process diagrams, and even hardware changes are made in the software layer. It is built for agile process development: fast to stand up, easy to reconfigure, and operable by scientists without an automation team.

Bottom line for process development: choose QB Control when the priority is development speed, iteration, multi-vendor flexibility, and lower total cost at lab-to-pilot scale. Keep or choose MFCS 4 when a standardized Sartorius production fleet needs electronic signatures today and enterprise-scale historization/analytics. On a Sartorius site the two are complementary over OPC-UA.

Dimension	Sartorius MFCS 4	QB Control
What it is	GMP SCADA / data-management software layer	Turnkey, software-defined bioprocess platform (hardware + software)
Hardware	Software only; bioreactors + Windows/SQL estate bought separately	QB Modules included; or reuse existing PLC via OPC-UA
Reconfiguration	Changes span DCU/PLC + OPC tags + SCADA config	Made in the software layer (drag-and-drop)
Deployment	Weeks–months (install, configure, validate, services)	Days (auto-discovery, plug-and-play)
Access	Windows clients via RDP (per-client, up to 30)	Any browser; secure remote access; unlimited users
Electronic signatures	Available today	Roadmapped (not yet released)
Licensing	Base + per-module + per-client + services	Perpetual, all-inclusive; optional support
Best for	Standardized Sartorius production fleet; GMP records	Agile, multi-vendor lab-to-pilot development

---

2. Two Models: Supervisory Layer vs. Software-Defined System

MFCS 4 sits on top of bioreactors whose control logic lives in the equipment’s own DCU/PLC. MFCS supervises, records, and orchestrates over OPC — so a change to the process often reaches down into the controller (PLC registers, control program, OPC tag mapping) as well as the SCADA configuration. That is the right model for a validated, standardized Sartorius production fleet, but it makes each change an automation project.

QB Control is software-defined: the platform owns the control layer, and the hardware (QB Modules, or a PLC reached over OPC-UA) is presented as software objects. Devices, process diagrams, control services, and recipes are all configured — and changed — in the software, without touching controller code. For a process-development group that iterates constantly, that difference is the headline: changes live in software, not in PLC programming.

---

3. Operational Agility for Process Development

This is where the two platforms diverge most for a development team.

3.1 Hardware changes happen in the software layer — not in PLC code

When a pump faults and is swapped, or a new probe or sensor is added to a running development program, QB Control absorbs the change in software: the replacement or new QB Module auto-discovers, you assign it in inventory and drag it onto the P&ID, and it is immediately available to services and recipes — no PLC register mapping, no control-program edit, no controls engineer, no cabinet rework. (On the industrial-PC/PLC deployment, new devices are mapped over OPC-UA in software the same way.)

On MFCS 4, the same change typically reaches the equipment’s DCU/PLC and the OPC tag layer as well as the SCADA configuration — i.e., an automation/engineering task rather than a scientist’s drag-and-drop. For a group adding probes and reconfiguring vessels week to week, this is the difference between minutes and a change request.

3.2 Dynamic, user-modifiable P&ID

QB Control’s P&ID is auto-generated from the process configuration and is freely modifiable by the user: scientists drag to position, size, and orient elements, choose which parameters each element displays, hide or reorder services to match how they run the process, and read status at a glance (color-coded gas/media piping and device states). The diagram is also the live control surface — manual device control, service control, recipe start/pause/resume, and a per-process emergency stop all run from the P&ID itself. No screen-engineering project; the operator shapes the view.

MFCS 4 provides process visualization (a Process Unit Display and charting), but its mimics/graphics follow the classic SCADA model — configured and maintained as engineered screens rather than auto-generated from the process and reshaped by the scientist at runtime.

3.3 Adjust recipe parameters and services during the run

QB Control lets a scientist change parameters mid-run: update a running service’s inputs live, edit permitted parameters directly from the execution board without returning to the designer, and update recipe variables during execution — startup values and runtime-adjustable values are separated so live changes are controlled and traceable. Development teams can tune a setpoint, feed rate, or control strategy in-flight without aborting the batch.

MFCS 4 emphasizes pre-run control definition: ISA-88 recipes with formula management (adjust the master recipe before execution) and supervisory setpoint changes during a run. Based on Sartorius’s available documentation, free operator modification of recipe parameters and services during execution is not clearly described and appears more constrained than QB Control’s in-run model — worth confirming with Sartorius for a given deployment.

3.4 Secure remote access

QB Control is browser-based, so a run is reachable from any device. Secure remote access adds a per-user, QR-code-onboarded, role-based connection from phone, tablet, or laptop — a scientist can monitor and adjust a development run from anywhere without IT provisioning a Windows session.

MFCS 4 remote access is via RDP to its Windows clients (per-client licensed, up to 30), which generally requires IT/VDI infrastructure and a managed Windows estate.

---

4. Control Content & Recipes

QB Control ships bioprocess control content out of the box: roughly 40 pre-built control services across 10 categories — pH, temperature, pump & feed, gas, gas-volume delivery, sampling, stirring & agitation, foam, valve, and LED/light — plus a filtration add-on. Reusable Service Profiles capture proven parameter sets, and a visual, no-code recipe engine (design, batch, executions) provides versioned recipes with a controlled lifecycle, sequential auto-stop campaigns, a pre-execution validator, and per-process and global emergency stops. A scientist selects a service, assigns it to a module, and runs.

MFCS 4 provides a formal ANSI/ISA-88.01 recipe-control module (optional) with graphical phase configuration, formula management, and perfusion templates — but it ships no pre-built control-service library. Control strategies are configured, and for complex automation Sartorius offers paid recipe-engineering services (custom and perfusion recipe services). The result is strong, standardized batch control, but building it is a configuration/engineering effort rather than a selection.

---

5. Compliance & Data

Area	Sartorius MFCS 4	QB Control
21 CFR Part 11 — records & audit trail	✅ Comprehensive	✅ Records, audit trail, access control today
Electronic signatures	✅ Available today	◐ Roadmapped (not yet released)
EU Annex 11 / ALCOA+	✅	✅
GAMP 5	Category 4 (configurable COTS)	Category 4 (configurable)
Data historian	Enterprise SQL Server; cross-scale incl. Ambr®	Per-process live + history; export via OPC-UA/REST/SQL
Advanced analytics	Built-in MVDA / DoE modules	Export to external analytics
Safety	Engineered interlocks	Built-in Safe Position Logic + P-Stop/E-Stop

Read: both are configurable GxP software, so neither carries a custom-code validation burden. MFCS 4’s clear advantage today is electronic signatures and enterprise historization/analytics; QB Control matches on records and audit trail and adds built-in process safety. For a workflow that must apply digital signatures on an active IND today, MFCS 4 (or another route) is the safer choice until QB Control’s e-signature release. Do not represent QB Control as fully 21 CFR Part 11 compliant.

---

6. Cost, Licensing & Deployment

MFCS 4 is priced as an enterprise stack: a base license plus per-module licenses (recipe control, 21 CFR Part 11, OPC server, calculations, sample data, MVDA, DoE), per-client operator licenses, Windows Server + Microsoft SQL Server and DBA time, installation/validation/engineering services, and a recommended annual support agreement — with the bioreactor hardware purchased separately. Standing it up runs weeks to months.

QB Control is perpetual and all-inclusive — hardware, software, the control services, and compliance modules in one system, with unlimited browser users, no external database, and optional tiered support. It deploys in days. Indicative reference figures (from past quotations, not a specific offer) run from roughly $15K–25K for an entry single-vessel system to about $100K for a six-vessel lab.

For lab-to-pilot development, QB Control’s all-inclusive model typically lands well below a fully-moduled MFCS 4 deployment once Windows/SQL, per-client licenses, recipe services, and validation are counted. For an existing Sartorius production estate, MFCS 4’s incremental cost is lower because that estate already exists.

---

7. Where Sartorius MFCS 4 Wins

Be clear-eyed — MFCS 4 is a strong, mature platform and leads QB Control in several areas that matter at production scale:

• Electronic signatures today — full 21 CFR Part 11 including e-signatures now (QB Control: roadmapped).
• Deep native Sartorius integration — best-in-class for Biostat®/Certomat®/Flexact® fleets, with cross-scale historization including Ambr® multi-parallel systems.
• Enterprise historian & scale — up to 32 process units, SQL-Server historization, replication, and high availability.
• Built-in MVDA / DoE — multivariate analytics and design-of-experiments modules in-platform.
• Formal ISA-88.01 recipe control with formula management for standardized, auditable batch manufacturing.
• Track record — a 40-year pharma pedigree with mature validation and engineering services.

---

8. Recommendation

Choose QB Control when process development needs: rapid, self-service iteration; the freedom to change hardware, diagrams, recipes, and in-run parameters in software without touching PLC code; multi-vendor flexibility; browser and secure remote access; and lower total cost at lab-to-pilot scale.

Choose or retain MFCS 4 when the priority is a standardized Sartorius production fleet, electronic signatures on active INDs today, or enterprise historization and MVDA/DoE analytics at 32-unit scale.

Run them together where both apply: QB Control for new, multi-vendor, and development lines; MFCS 4 as the Sartorius fleet historian and compliance record; bridged over OPC-UA. The end of mainstream support for the legacy MFCS/win 3.x generation (2024) is a natural moment to evaluate QB Control for development lines rather than defaulting to a like-for-like upgrade.

---

Feature Snapshot

Dimension	Sartorius MFCS 4	QB Control
Turnkey hardware + software	✗ (software only)	✓
Vendor-neutral (multi-brand bioreactors/sensors)	◐ (Sartorius-centric; others via OPC)	✓
Hardware change in software (no PLC programming)	✗	✓
Dynamic, user-modifiable P&ID	◐ (engineered screens)	✓ (auto-generated, drag-and-drop)
Modify recipe parameters/services mid-run	◐ (pre-run formula + setpoints; in-run unclear)	✓
Pre-built control services (categories)	✗	✓ (~40 across 10 categories)
Visual no-code recipe engine	◐ (ISA-88 config)	✓
Secure remote access (browser, any device)	◐ (RDP, per-client)	✓
Electronic signatures (21 CFR Part 11)	✓ (today)	◐ (roadmapped)
Enterprise historian + MVDA/DoE, 32 units	✓	◐ (lab-to-pilot; export)
Native Sartorius fleet + Ambr historization	✓	◐ (via OPC-UA)
Deployment time	Weeks–months	Days
Licensing	Per-module + per-client + services	Perpetual, all-inclusive
External database / DBA required	✓ (SQL Server)	✗

Legend: ✓ = yes / strong · ◐ = partial / conditional · ✗ = no

---

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 Sartorius BioPAT® MFCS 4 (Biobrain® Supervise) — current release per 2025–2026 datasheets. 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. Sartorius®, BioPAT®, Biobrain®, Biostat®, and ambr® are registered trademarks of Sartorius AG. QB Control and QB Systems are brands of A4BEE Sp. z o.o.

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

Purpose and limitation of liability. This comparison is provided for informational and educational purposes only, to help readers build knowledge of the options available to them. It is not an assessment, audit, ranking, benchmark, or endorsement of the technical expertise, quality, safety, or performance of Sartorius BioPAT® MFCS 4 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.

1. Sartorius — Biobrain® Supervise (BioPAT® MFCS) SCADA software product page
2. Sartorius — Biobrain® Supervise Software Features (datasheet, DIR 2624182, 2025)
3. Sartorius — Biobrain® Supervise: The Standard in Bioprocess Data Management and Automation (brochure, SBI1519-e, 2026)
4. Sartorius — BioPAT® MFCS ANSI-88 Compliant Batch Control (datasheet)
5. bionity — BioPAT® MFCS SCADA software overview

---

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