Fermentation Batch Record

A fermentation batch record is the executed, controlled copy of a master recipe for a single fermentation lot. It evidences that the batch was made as specified, on qualified equipment, with identified materials, under controlled parameters, and that all results, deviations, and approvals were captured contemporaneously. In biotech and pharma it is an essential component of GMP lot release; in regulated food/supplements it supports traceability, process control, and hazard management. The record merges structured operator interactions (checklists, weigh/dispense, charge steps, sampling) with time-series data (e.g., temperature, pH, dissolved oxygen, agitation, gas composition/flow) and event logs (alarms, holds, interventions).

Conceptually, it ties ISA‑88 recipe constructs (master/control recipe, unit procedures, operations, phases) to GMP record requirements (21 CFR 211.188) and to computerized system controls (21 CFR Part 11; EU GMP Annex 11). It is broader than a bioreactor run record because it also includes materials genealogy, weigh-and-dispense traceability, cleaning and sterilization evidence, in-process tests, yields, deviations, and QA approvals.

In drug manufacturing, 21 CFR 211.188 requires batch production and control records to include, among other items, the complete manufacturing and control instructions, identification of equipment and lines used, each significant step and the in-process and laboratory control results, yields (actual vs. theoretical), investigation results for deviations, dates, and signatures/initials of persons performing and checking each step. EU GMP Volume 4 likewise expects comprehensive documentation and computerized system controls per Annex 11.

• Recipe and version: link to approved master (and any controlled permissible parameter ranges).
• Equipment identification and status: fermentor, skid, utilities; evidence of cleaning (CIP) and sterilization (SIP) readiness; calibration status of critical sensors.
• Materials genealogy: lots, quantities, dispensers, weigh tickets, reconciliation; inoculum lineage and seed train traceability.
• Execution detail: timestamps, setpoints and actuals for CPPs; operator entries; interlocks and permissives; alarms and responses.
• Sampling and testing: sample IDs, methods, timepoints, analyst, results, limits; data attachments and LIMS links.
• Yield and reconciliation: in-process and final yields vs. theoretical, losses, line flush/hold records.
• Deviations/OOS and change control: descriptions, impact assessment, approvals, CAPA links.
• Approvals: step sign-offs, batch review, and final release authorization with e-signatures.

For electronic implementations, Part 11 and Annex 11 require validated systems, secure user management, audit trails, record retention/retrieval, and e-signature controls aligned to SOPs. GAMP 5 (2nd ed.) promotes risk-based lifecycle controls over configuration and integration that directly affect product quality or patient safety.

ISA‑88 provides a modular model to design and document batch processes. For fermentation, the master recipe defines the process intent, while the control recipe captures the executed instance with parameterization and as-run data. Decomposing into unit procedures (e.g., vessel prep, inoculation, growth, feed, harvest), operations (e.g., sterilize, charge, aerate, feed, hold), and phases (e.g., valve open/close, setpoint ramps, PID control, antifoam dosing) ensures traceability from high-level instructions to low-level control actions in the batch record.

This mapping supports review-by-exception: reviewers can navigate from a deviation or limit excursion at phase-level telemetry to the related operation, unit procedure, and master recipe requirements. It also structures interfaces (ISA‑95) for consuming data across MES, LIMS, and historians.

Electronic fermentation batch records are subject to Part 11 and Annex 11 controls. Key expectations include unique user IDs, role-based access, secure and computer-generated audit trails capturing who/what/when/why for create/modify/delete; binding of e-signatures to records; time-synchronized, attributable entries; validated interfaces; and reliable retention with true copies. MHRA’s data integrity guidance emphasizes ALCOA+ principles: data must be attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available.

• Audit trails: enabled for GMP-significant data (parameters, materials, results, status changes), reviewable with filters and annotations.
• Time synchronization: NTP-managed clocks across DCS, historian, MES, LIMS to preserve event sequence and causality.
• E-signatures: meaning of signature defined in SOP; signer identity verification; dual sign-off where required (e.g., critical additions).
• Attachments: tamper-evident storage with metadata (instrument, method, analyst, version).
• Retrospective vs. contemporaneous entry: minimize manual transcription by interfacing to source systems; if manual, enforce structured entry with verification.

"A control strategy is a planned set of controls, derived from current product and process understanding that ensures process performance and product quality."

Fermentation batch records aggregate evidence from multiple layers. ISA‑95 delineates interfaces between business (ERP), manufacturing operations (MES/LIMS/WMS/CMMS), and control (DCS/SCADA/PLCs). Robust implementations avoid data silos by capturing the authoritative source and referencing it in the batch record with strong identity resolution (equipment IDs, material lots, sample IDs).

• Control layer (Level 2/1): DCS/SCADA/PLC event and analog data; recipe phase confirmations; alarm/event logs; historian references.
• Operations layer (Level 3): MES eBMR instructions and checks; weigh-and-dispense with barcode verification; WMS lot holds/releases; CMMS maintenance states and calibration due dates; LIMS sample registration and results.
• Business layer (Level 4): ERP material and batch master data; approved recipe versions; CoA/CoC receipt checks feeding release eligibility.
• Identity and context: consistent batch IDs, equipment allocation, campaign/run numbers; sampling plan anchored to batch timebase.
• Genealogy: one-up/one-down trace of inoculum, media, feeds, antifoam, gases; post-harvest transfers and splits tracked to next unit operations (e.g., cell separation, chromatography).

Critical to review is the ability to traverse from a test result (LIMS) or alarm (DCS) to the precise step and material context in the eBMR, with audit-trail transparency and date/time coherence. ISA‑95-aligned data models and event frameworking enable this without duplicating raw time-series.

Upstream control strategies define CPPs and associated ranges/limits derived from development (ICH Q11). The batch record must carry the authorized setpoints and record the actuals with sufficient resolution to support release decisions and investigations. Typical fermentation CPPs include temperature, pH, dissolved oxygen (DO) or oxygen uptake rate proxies, agitation/cascade logic, gas flows/composition (e.g., air/O2/CO2/N2), pressure, foam level/antifoam dose, feed rates (bolus/continuous), and vessel additions. CQAs are often measured via off-line or at-line analytics, with sampling plans embedded in the record.

• CPPs and limits: store authorized ranges per recipe version; capture setpoint changes with reason codes and authorization.
• Sampling plan: time- and event-based (e.g., every X hours, before/after feed); predefine containers, preservative, chain-of-custody; auto-generate sample IDs.
• Testing: link to method version; record instrument ID and calibration status; capture results, units, and limits; manage attachments (e.g., chromatograms, qPCR).
• Alarms and interlocks: log occurrences, time-to-response, and corrective actions; identify excursions impacting product quality.
• Yield tracking: inoculum to harvest mass balance; document losses (line hold-up, filter change); reconcile against theoretical.

Acceptance decisions combine compliance to recipe, absence/resolution of critical deviations, passing in-process and release testing, and acceptable yield. The batch record should explicitly show pending items (e.g., test results, deviation closures) gating final release.

When instructions are not followed as written, a parameter exceeds a limit, or an unexpected event occurs (e.g., contamination alarm, sensor failure), the batch record should automatically initiate or link to a deviation record capturing problem statement, immediate correction, impact assessment, and approvals. Evidence includes relevant time-series snippets, alarm trails, operator notes, and analytical results. Where product quality may be impacted, the record must show the final disposition decision and rationale.

• Auto-trigger deviations on limit breaches of CPPs or missed critical checks; pre-populate context from the eBMR.
• Route to QMS for root cause analysis and CAPA; maintain bi-directional links for audit readiness.
• Aggregate batch-to-batch trends (CPV): overlay golden batch envelopes, identify drift in kLa proxies, oxygen demand profiles, or feed conversion correlations.
• Feed-forward/feedback impact: link upstream deviations to downstream purification performance and yields.
• Periodic review: use standardized queries (e.g., all batches with DO cascade manual override) to detect systemic issues.

ICH Q11 emphasizes that control strategies evolve with process understanding; fermentation batch records are therefore living inputs to lifecycle management. Good practice is to periodically mine executed records to refine allowable ranges, sampling frequencies, and alarm thresholds.

An effective electronic fermentation batch record orchestrates operator guidance with automated data capture. Electronic work instructions drive line clearance, equipment status verification (e.g., CIP/SIP complete), material verifications (barcode/label scans with expiry checks), and step confirmations with e-signatures. Interfaces subscribe to DCS/SCADA and historian tags to bind setpoints/actuals, alarms, and mode changes to the exact phase. Where manual readings persist (e.g., microscopy cell counts), structured entry with checks and witness signatures mitigate error risk.

• Permissives: block critical steps unless prerequisites (cleanliness, sterilization, calibration due) are satisfied.
• Dynamic parameters: allow authorized, reason-coded setpoint adjustments within predefined ranges; log outside-range deviations.
• Sampling orchestration: generate labels and chain-of-custody; automatically dispatch tests to LIMS and read back results/state.
• Review by exception: flag limit excursions, late samples, alarm response delays, and failed verifications; summarize for QA.
• Record visualization: phase-level overlays for core CPPs; drill-through from exception to raw time-series and audit trail.

Implementations succeed when the batch record is the connective tissue across execution, quality, lab, materials, and assets. The platform must natively reconcile time-series evidence with structured GMP data and present reviewers a coherent, exception-focused narrative that withstands regulatory scrutiny.

• Timebase drift across systems causing misordered events; mitigate with central NTP and cross-system time-audit checks.
• Incomplete inoculum genealogy or missing media/feeds CoA linking; enforce mandatory scans and lot attribute capture.
• Manual transcription of time-series or results; replace with validated, read-only interfaces and structured data capture.
• Undefined meaning of e-signatures or inconsistent review workflows; codify in SOPs and configure system-enforced rules.
• Weak sampling metadata (no method/version, container, analyst); template mandatory fields and attach instrument IDs.
• Attachment sprawl without provenance; store immutably with metadata and checksum, reference from the exact phase/step.
• Poor version control of master recipes; adopt change control and training workflows; archive true copies per retention policy.

Treat electronic fermentation batch records as GxP computerized systems. Apply a risk-based lifecycle (GAMP 5) to define requirements, design, configure, integrate, verify, and maintain. Focus testing on functions that can impact product quality or data integrity, including recipe control, material verification, alarm handling, audit trails, e-signatures, and interfaces to DCS/SCADA, historians, LIMS, WMS, and CMMS.

1. URS and process mapping: capture ISA‑88 recipe structure, CPP/CQA definitions, sampling plan, approval workflows, and integration points (ISA‑95).
2. Configuration and integration: implement master/control recipes, enforce ranges and permissives, and wire interfaces with identity synchronization (batch/equipment/material IDs).
3. Risk-based testing: unit and integration tests for phase binding to telemetry, alarm/event capture, audit-trail integrity, e-signature rules, and exception logic; challenge time sync and failover behavior.
4. CSV/CSA deliverables: validation plan, requirements traceability, risk assessments, test protocols/results, deviation handling, summary report; SOPs for operation, backup/restore, admin, and audit-trail review.
5. PQ with representative batches: dry runs and shadow batches, then live execution under QA oversight; calibrate review-by-exception rules to minimize false positives/negatives.
6. Continuous improvement: CPV analytics over executed batches; periodic review of master recipe limits, alarm thresholds, and sampling plans; maintain change control and training.

Ensure retention and retrieval meet regulatory expectations: preserve complete, original electronic records (including audit trails and attachments) in durable, accessible formats for the defined lifecycle. Periodically verify true-copy export and disaster recovery procedures.