Bioreactor Run Record

A Bioreactor Run Record is the definitive execution and data record for a single cultivation or fermentation run performed on a defined unit (bioreactor/fermentor) under a master recipe. Built on ISA‑88 structure, it chronicles each unit procedure, operation, and phase with their parameters, setpoints, tolerances, and outcomes. It binds equipment identifiers and calibration status, materials/consumables genealogy (e.g., inoculum, media, gases, antifoam), in‑process tests, sampling, alarms, deviations, and yield calculations into a contemporaneous, reviewable package that supports batch release and continued process verification.

In GxP manufacturing, this record must meet 21 CFR 211.188 content expectations for batch records, and when electronic, 21 CFR Part 11 and EU GMP Annex 11 requirements for authenticity, integrity, and e‑signatures. It typically originates in an MES/eBMR and integrates with process equipment (DCS/PLC/SCADA), LIMS for samples, QMS for deviations/changes, and CMMS for maintenance/qualification state, ensuring that what was planned (recipe) and what occurred (run) are demonstrably aligned.

While regulations rarely name “bioreactor run record” explicitly, they prescribe what a compliant record must contain and control. 21 CFR 211.188 requires batch production and control records to include a stepwise description with equipment identification, in‑process and laboratory control results, yields, signatures/initials of those performing and checking each significant step, and any recorded investigations. For biologics and advanced therapies, the same principles apply to upstream operations: unit‑level execution, materials traceability, and verification of process parameters against approved instructions.

When the record is electronic, 21 CFR Part 11 and EU GMP Annex 11 require validated systems, secure, computer‑generated, time‑stamped audit trails, controls for authority checks, and linking of electronic signatures to their records. MHRA’s GxP data integrity guidance operationalizes ALCOA+ (Attributable, Legible, Contemporaneous, Original, Accurate, plus Complete, Consistent, Enduring, and Available), which directly informs how run records are captured, protected, and reviewed. ISA‑88 provides the recognized model to structure the record consistently across recipe elements, aiding review and integration.

• Batch record content: stepwise instructions, equipment IDs, in‑process results, yield calculations, signatures (21 CFR 211.188).
• Electronic controls: validated system, audit trails, security, e‑signatures (21 CFR Part 11; EU GMP Annex 11).
• Data integrity attributes (ALCOA+) for source data, metadata, and context (MHRA guidance).
• Structured model for recipe and record hierarchy (ISA‑88).

A robust bioreactor run record mirrors the ISA‑88 batch control model to achieve consistency and reviewability. The unit procedure (e.g., “Upstream Culture – 2000 L Unit 01”) is decomposed into operations (e.g., vessel preparation, media charge, inoculation, growth, induction, harvest preparation) and then into phases (automatable steps: transfer, heat/cool, control pH, cascade DO, feed bolus, sparge, antifoam dose). Each node carries parameters (setpoints, limits, timers), preconditions/permissives, interlocks, instructions, and acceptance criteria. Execution captures planned versus actual parameter trajectories and events, operator annotations, and exception handling.

This structure allows the run record to be queried and reviewed at the granularity where deviations occur and decisions are made, while remaining traceable up to the batch/lot. It also harmonizes interfaces to equipment modules and control modules in ISA‑88 terminology, simplifying integration to DCS/SCADA and recipe versioning control.

Upstream performance and quality are driven by parameters such as temperature, pH, dissolved oxygen (DO), agitation speed, gas composition and flow (air, O2, N2, CO2), feed and antifoam dosing rates, headspace pressure, and foam level, as well as sampling schedules and in‑line/at‑line PAT (e.g., capacitance, Raman). The run record must capture both the planned values and the actual, time‑series data with synchronized timestamps, plus contextual events: operator interventions, setpoint changes, mode changes, interlock trips, alarms, and exception handling. Materials dispenses (media, buffers, feeds) should be recorded with lot/serial/expiry and weighed/volumetric reconciliation to connect consumption to genealogy.

• Ensure time synchronization across MES, DCS/SCADA, LIMS, and historian so correlations are defensible.
• Preserve raw source data and metadata; the rendered report is not a substitute for primary records.
• Capture rationale for any manual overrides or setpoint changes contemporaneously with execution.

A bioreactor run consumes media, feeds, gases, antifoam, filters, and single‑use assemblies that must be qualified and traceable. The run record should link each dispense or connection to a specific lot/serial, record pre‑use checks (e.g., integrity test for filters), and reconcile theoretical versus actual usage. For inoculum, parent‑child batch relationships must be explicit, with backward/forward genealogy to seed trains and master/working cell banks where applicable. This supports deviation investigations and enables efficient recall/trace if an upstream input is later found nonconforming.

1. Identify and verify each material (lot, expiry, status) at the point of use.
2. Record quantity used and unit of measure; apply weighing tolerances and checks.
3. Reconcile theoretical vs. actual; document overages and losses with reason codes.
4. Capture equipment assemblies and single‑use kit lot/serials linked to the unit and run.

Tying genealogy to the run record also enables robust golden‑batch analytics later, because material attributes (supplier, lot‑specific COA) can be correlated to process performance and quality outcomes.

The bioreactor run record sits at the manufacturing operations layer and depends on reliable, validated integrations up and down the ISA‑95 stack. At Level 2/3, interfaces to DCS/PLC/SCADA and weigh scales populate parameters and events. At Level 3, MES orchestrates execution, sampling, and review, while LIMS returns verified test results. QMS manages deviations/change controls linked to the run. CMMS provides equipment status and calibration locks. At Level 4, ERP supplies material masters and receives consumption confirmations and lot genealogy updates.

• SCADA/MES: bidirectional exchange of phase start/stop, parameters, events, and operator annotations.
• LIMS/MES: sample pull list, chain of custody, result import with method/version and analyst identity.
• QMS/MES: deviation initiation from alarms/out‑of‑trend, CAPA linkage, change control on recipe updates.
• CMMS/MES: qualification/calibration status enforcement as permissives; equipment lockout on lapse.
• ERP/MES: lot reservations/consumption posting; backflush strategies reconciled to weigh records.

Design integrations to preserve data provenance and audit trails across systems; do not reduce high‑resolution process data to low‑frequency snapshots that cannot support investigations or CPV.

Under Part 11 and Annex 11, electronic run records require validated systems and technical and procedural controls: unique user accounts with role‑based access, secure computer‑generated audit trails that cannot be altered, date/time stamps with time zone, and e‑signatures that are legally binding and linked to the record’s content and meaning. MHRA’s guidance reinforces that raw data must be retained in its original form and context, including metadata (who, what, when, where, why), and that review should be risk‑based and periodic.

• Enforce two‑person e‑signatures for high‑risk verifications (e.g., inoculation, critical setpoint changes) where SOPs require.
• Audit trail review should be targeted to critical parameters, exceptions, and any data lifecycle vulnerabilities.
• Ensure hybrid records (paper + electronic) have a single source of truth and controlled reconciliation procedures.

The computerized components that create, process, and store the run record must be validated commensurate with risk (GAMP 5). This includes MES/eBMR, interfaces to SCADA/historians, e‑signature functions, audit trail, reporting, and long‑term archiving. Apply a lifecycle approach: URS traceable to test evidence; supplier assessment; configuration specifications; risk‑based testing; and change control for recipe versions. Verify that the system enforces recipe and parameter limits, captures exceptions, and prevents unauthorized changes. Qualification of the bioreactor unit and its instruments (IQ/OQ/PQ; calibration) must be current and referenced in the record.

1. Define critical data and functions for the run record (risk assessment) and align test depth to risk.
2. Test audit trail completeness, time synchronization, e‑signature binding, and report accuracy.
3. Challenge recipe versioning, phase logic, permissives/interlocks, and exception handlers with negative tests.
4. Verify data flows to LIMS, QMS, CMMS, and ERP with failure mode tests (e.g., network loss, retry logic).

Part 11/Annex 11 expectations include procedures for user account management, periodic review, backup/restore, disaster recovery, and business continuity. Retention periods should be defined to meet product‑specific requirements and enable effective trend analysis for CPV.

Quality review should verify completeness (all phases executed; samples collected; results received), conformance to recipe limits, disposition of alarms/excursions, yield calculations, reconciliation variances, and closure of associated deviations or change controls. Electronic review workflows can enforce segregation of duties and checklist‑driven approvals, with targeted audit trail review for high‑risk steps. Once the unit‑level run is cleared, it rolls into the batch eBMR, which aggregates upstream/downstream records for final lot disposition.

For CPV, retain high‑resolution process data and contextual metadata to compute golden‑batch fingerprints and multivariate models. Correlate parameter trajectories, material attributes, and outcomes (titer, purity, CQAs). ISA‑88 structure enables apples‑to‑apples comparisons across runs. ICH Q10 principles support feedback and feed‑forward improvements via change control and knowledge management grounded in the run record.

• Unlinked raw data: Trend images stored without accessible primary time‑series undermine investigations. Preserve source data with integrity checks and metadata.
• Clock drift: MES and SCADA timestamps disagree. Implement enterprise time services and verify during validation.
• Recipe sprawl: Multiple uncontrolled copies of phase logic. Enforce version control, change control, and impact assessment before deployment.
• Hybrid gaps: Paper additions for late changes not reconciled to eRecord. Define hybrid controls and reconciliation SOPs.
• Calibration blind spots: Instrument due dates not checked at time of use. Integrate CMMS status as permissives to run.
• Material mis‑reconciliation: Backflushing without weigh data. Balance ERP postings with MES weigh tickets and tolerances.

Internal audits should sample recent runs for these vulnerabilities, checking audit trail quality, user access reviews, and correctness of integrations. Trending deviations by root cause (human factors, interface, recipe logic, equipment) helps prioritize CAPA.

In V5, the bioreactor run record is an ISA‑88‑native object inside the MES/eBMR, with recipe/phase models, parameter libraries, and version control. Real‑time interfaces bring in continuous data and events from DCS/SCADA and smart instruments; materials are verified against WMS/ERP with weigh tickets and tolerances; sampling is orchestrated with LIMS integration. Deviation initiation, change control, and CAPA are embedded through the QMS; equipment status and calibration permissives are enforced via integrated Maintenance/CMMS. Part 11/Annex 11 controls—RBAC, e‑signatures, secure audit trails—are built‑in and validated under a GAMP 5 approach.