All blueprints

Biopharma manufacturing. The batch starts at the bank.

Biologics manufacturing software and biopharma MES that records cell-bank genealogy, upstream execution, purification pools, single-use assemblies and release as one lineage from bank vial to final container.

Illustration of a seal beside a production line of sealed vials.
BIO-DS-024 / one living lineage
Each step carries its source and acceptance.
Starting system
WCB vial / 3F-071
identity · viability · passage
Seed 01
identity · viability · passage
Seed 02
identity · viability · passage
Production culture
BR-04 / fed batch
media · feeds · signals · samples
Viability94.8%
Titre5.1 g/L
Open events00
Harvest accepted
Material transformations
Harvest
quantity · hold · sample
Capture
quantity · hold · sample
Viral safety
quantity · hold · sample
Final bulk
quantity · hold · sample
Backward to WCB vial. Forward to every released container.

Figure 1. Lineage BIO-DS-024: working-bank vial 3F-071 through two seed stages to production culture BR-04 (viability 94.8%, titre 5.1 g/L, harvest accepted), then harvest, capture, viral safety and final bulk. Each edge carries its process evidence, traceable back to the vial and forward to every container.

Summary

The problem
A biologics batch depends on a bank vial, a seed train, prepared solutions, single-use assemblies, purification assets, hold clocks and viral-safety steps, usually recorded in different systems. Release and investigations begin by reassembling that lineage by hand.
Seal’s approach
Every transformation from bank vial to final container is recorded as it happens, with its materials, equipment, process evidence, samples and acceptance decision. Control systems and historians stay authoritative for automation data; Seal carries the accountable context.
What changes
QA reviews completed stages while manufacturing continues, and a finding against a vial, component lot or column cycle traces forward to every affected pool and lot without a separate genealogy spreadsheet.
Where to start
One bank-to-release lineage, including a failed acceptance decision, a missing historian interval and forward and backward trace exercises. Book a demo.

A biologics batch does not begin when the production order opens. It begins with the cell substrate: the bank vial selected, the expansions that lead to the production culture and the materials and assemblies introduced along the way. Harvest, purification, viral-safety steps, holds and testing then change the physical shape of the batch several times before release.

Seal records each of those transformations as it happens, with its materials, equipment, process evidence, samples and acceptance decision. The result is one manufacturing record rather than a batch record beside a separately maintained genealogy report.

Biologics manufacturing needs more than recipe steps.

A conventional MES guides operators through recipe steps. Biologics also need living lineage, many-to-one and one-to-many material transformations, product-contact genealogy, time-sensitive intermediates and laboratory decisions that gate the next step. Seal holds these in the same record as execution.

Table 1. Where a connected biologics record differs from a batch record kept beside the genealogy.
Batch record beside the genealogySeal
Bank and seed trainA vial number typed into the batch recordThe withdrawn vial, each expansion and its acceptance decision, linked to the production culture
Single-use assembliesA kit numberComponent lots, positions and product-contact intervals for the assembly actually built
Pools and columnsInventory receipts and a manual cycle counterExplicit splits and pools; column and resin eligibility from actual use history
Automation dataSelected values retyped from the historianPhase events and source references, with missing intervals shown as pending
ReleaseLineage assembled at the endExceptions surfaced against the stage where they occurred, reviewed as stages complete

Why teams choose Seal for biologics manufacturing

When QA reviews a biologics lot, the lineage is usually rebuilt by hand: the MES executed the recipe steps, but bank genealogy, pool decisions, hold clocks and viral-safety evidence sit in LIMS, spreadsheets and paper. Seal records each transformation on the same platform as the laboratory and quality work, and Neil can propose a process change from that run evidence. The process can then be refined across campaigns: an approved change applies to the next lot, and every earlier lot keeps the process version it ran.

1Give every manufacturing system one authority.

Biologics facilities rely on ERP, distributed control systems, equipment controllers, historians, LIMS, chromatography data systems and quality tools. The design works only when each object and decision has one owner. ERP can own demand, purchasing and financial inventory. Control systems own process control and high-frequency acquisition; historians retain dense time series; CDS and instruments own analytical acquisition and processing. Seal can own the GMP order, the approved process, bank and material genealogy, accountable execution, samples, equipment eligibility, quality events and disposition.

Seal adds the context a manufacturing decision needs. A harvest decision carries culture state, critical values, samples, limits, reviewer and destination pool. A chromatography result carries column and resin identity, cycle, fractions, pool and acceptance.

Interfaces define acknowledgement, retry, outage and reconciliation. Missing automation or laboratory evidence stays visibly pending rather than becoming a blank field filled from memory.

ACQ-1842 / HPLC-04Sample acquisition

Raw acquisition

sequence-1842.raw

Source measurements
Received

Method

assay-method-v08.xml

Acquisition settings
Received

Sequence

sequence-1842.csv

Sample and injection order
Received

Audit trail

audit-1842.xml

Actions and changes
Missing

3 of 4 required files received

The PDF report cannot stand in for the missing audit trail. Keep the package incomplete.

Figure 2. An acquisition record shows three of four required files received and holds the result incomplete until the audit trail arrives

2The lineage starts at the bank vial.

A master or working cell bank is not ordinary inventory. Its identity, passage history, characterisation, storage, use authorisation and remaining population determine whether a manufacturing lineage may begin.¹ Seal manages bank structures and individual vials as controlled records. Withdrawal identifies the exact vial, user, time, location, storage exposure and process order, and the vial cannot be silently substituted once execution has begun.

Each expansion, from thaw through shake flasks and seed bioreactors to the production vessel, is both a process step and a lineage event. It records source culture, target vessel, medium and supplement lots, inoculation quantity, passage, timing, samples and acceptance. Cell count, viability and contamination checks gate the next stage. If a stage misses its window or fails a criterion, the approved response is recorded against that culture rather than in a comment on the eventual production batch.

The same chain works in both directions. A freezer excursion or characterisation concern traces forward from the affected vial population to every seed, culture, harvest, pool and drug-substance lot. A released-lot investigation traverses it backward without a separate genealogy spreadsheet. The cell bank and seed lot blueprint covers the bank lifecycle in detail.

3Prepared solutions and single-use assemblies are part of the batch.

Media, feeds and buffers have their own formulas, source lots, preparation equipment, adjustments, filtration, samples, hold limits and destination. Seal can execute preparation as a linked record, so the prepared lot retains its consumed materials, actual quantities, preparation values and release. At the bioreactor or purification step, scanning verifies the correct lot, status, expiry and destination, and a raw-material finding traces into every culture or pool that received it.

Bags, tubing sets, filters, sensors and connectors carry identity, lot, expiry, sterilisation and integrity requirements. Seal defines the approved assembly pattern and instantiates the physical assembly for the run: scanning checks each component and position, and connection, integrity testing, use and disposal stay linked to the equipment train and exposure window. A wrong component, expired lot or failed integrity test blocks the normal path. An authorised replacement keeps both the removed and installed configuration and the product-contact interval each experienced, so a supplier issue traces to every culture, harvest or pool the component lot contacted.

4Upstream execution carries the process state.

Control systems capture temperature, pH, dissolved oxygen, agitation, gas flow, feed and weight at high frequency. The GMP record still has to show which recipe phase was active, which data supported a decision and what accountable action followed. Seal orchestrates the approved operation while control systems and historians remain authoritative for automation data. Critical events, phase summaries, excursions, additions and source references enter the batch record; manual connections, additions, observations and transfers receive contemporaneous attribution and prerequisite checks. Reviewers navigate from the accountable step to the relevant trend rather than to a few hand-selected numbers.

Process samples are created from the active culture, pool or hold with their method, criteria and next decision attached. The approved result returns to the waiting step without being emailed or retyped, and can permit harvest, release a pool to the next operation or open an investigation.

If a historian or controller interface is unavailable, the batch shows the missing evidence and follows the approved continuity path. Recovery reconciles message identity and time range; an interface running again does not mean all batch data has been recovered.

5Pools, columns and viral-safety steps keep their own evidence.

Harvest, clarification, capture, polishing, concentration and final filtration change the shape of the batch. Seal records source and destination containers, actual quantities, yields, location, storage condition and time limits. Pooling is a controlled many-to-one transformation and splitting a one-to-many transformation; neither becomes a generic inventory receipt.

Purification depends on more than the skid program. Column packing, resin lot and reuse history, sanitisation, pressure, cycle count, prior products and lifetime limits determine eligibility. Seal links each column, resin or membrane instance to the cycle and to the fractions or pool it produced, and enforces campaign and lifetime limits from actual exposure. A later resin concern identifies every cycle, load, pool and batch in the affected history.

Column / cycles accumulate / capacity trend decides retirement
Column
CAP-3 / Protein A
Cycles run
95
Current capacity
29 g/L
Retire limit
28 g/L
Column capacity trend chartRetire ≤ 28 g/L2638 g/Lcycles
Approaching retire limit / retirement planned at cycle 100
Retirement evidence: cycles run, volume processed, sanitisations and packing tests.
Figure 3. A column’s binding capacity, recorded cycle by cycle, trends towards its retirement limit

The records of viral inactivation and removal steps show that the approved safety strategy was executed. An inactivation step records start condition, setpoint range, mixing, exposure interval, end condition and review; a virus filter records identity, use conditions, throughput, differential pressure and integrity. Clearance studies support the control strategy.² The executed batch shows that the defined conditions were achieved for the actual pool. A failed or interrupted condition identifies the exact pool and downstream material requiring assessment. The viral safety blueprint covers the study side.

6Hold clocks and cold state travel with the container.

A pool held within temperature for too long is not acceptable because the current reading looks correct. Seal starts each hold clock from its defined event and carries the deadline with the container. Harvest holds, pool holds, filter-use limits, ambient exposure, freeze-thaw allowances and shipping windows can apply at once; Seal identifies the next limiting condition, and pause or reset behaviour is part of the approved rule rather than an operator assumption.

Storage and transport observations map to the affected interval. When an excursion occurs, impact assessment begins with the exact containers, exposure period, process stage and downstream lots. Scheduling sees material approaching a limit before it becomes an exception, so a delayed test or equipment outage shows which downstream slots remain viable.

7Change, monitoring and release read the same lineage.

Biologics processes are sensitive to changes in banks, media, single-use components, equipment, scale, methods, sites and suppliers. Seal links controlled configuration to its source documents and validation evidence, so a proposed material change identifies the recipes, stages, specifications, active batches and training that depend on it. Execution history shows which lots ran under which approved state, which supports comparability assessment and tech transfer.

Process validation continues through commercial production.³ Because parameters, attributes, yields, holds, deviations and results keep their process version, bank, material and equipment context, they can be trended by the right population, and a changed method or process version stays visible rather than mixed into one chart. A signal can open an investigation, CAPA or change with the source lots attached.

Release brings together bank and seed genealogy, materials, upstream execution, pools, viral-safety evidence, testing, equipment state, holds, deviations and changes. QA reviews completed stages while manufacturing continues, and exceptions appear against the transformation where they occurred. Disposition remains the quality unit’s decision.⁴ Later evidence, such as a supplier issue or stability trend, attaches to the original genealogy without rewriting the historical disposition.

After: review, not compilation1 screen
Unified batch view
Execution
Steps with timestamps
Operators identified
Materials linked
Progress tracked
Test results
Results inline
Specs checked
OOS flagged
CoA follows results
Deviations
Linked to step
Full context shown
Resolution status
Impact assessed
Equipment
Calibration status
Usage logged
Quals verified
Training current
One review record
Focus on judgement, not assembly
Figure 4. Execution, test results, deviations and equipment status reviewed together in one batch view rather than compiled at the end

8Start with one bank-to-release lineage.

Prove one representative lineage rather than configuring upstream, downstream, laboratory and quality as separate modules. Select one bank, seed train, production culture, harvest, purification path, final pool and release panel, with representative single-use assemblies, automation data, samples and holds.

Exercise the failure cases: a wrong bank vial, failed seed acceptance, missing historian interval, single-use integrity failure, pool quantity discrepancy, failed viral-safety condition, exceeded hold and a post-release supplier finding. The operating model is ready when each scenario blocks or permits the correct transition and identifies every affected downstream object, and when forward trace from the bank and backward trace from a released container both hold.

References

  1. 1EudraLex Volume 4, Annex 2, Manufacture of Biological active substances and Medicinal Products for Human Use (2018). European Commission
  2. 2ICH Q5A(R2), Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin (2023). ICH
  3. 3FDA, Process Validation: General Principles and Practices, guidance for industry, Revision 1 (2011): defines process validation as the collection and evaluation of data, from the process design stage through commercial production, in three stages: process design, process qualification and continued process verification. FDA
  4. 421 CFR 211.22, Responsibilities of quality control unit: a quality control unit must have the responsibility and authority to approve or reject components, in-process materials, packaging, labelling and drug products, and to review production records. eCFR

AOperating model

Included in this blueprint

  • Commercial batch execution
  • Cell bank and material genealogy
  • Process data integration
  • Process and release testing
  • Equipment and single-use state
  • Deviations and change
  • Process lifecycle
  • Concurrent batch release
  • Prepared solutions and purification assets
  • Continued process verification

Connected across Seal

BCapabilities

Table B.1. What the Biopharma MES and Biologics Manufacturing blueprint covers. Linked capabilities are blueprints of their own.
CapabilityWhat it covers
Commercial batch executionApproved bank-to-release processes become guided execution with phases, parameters, additions, samples, holds, signatures and controlled branches.
Cell bank and material genealogyBank vials, seed expansions, materials, single-use components, cultures, pools and final containers stay connected through each transformation.
Process data integrationControl-system and historian events, summaries, critical values, alarms and source references enter the accountable batch context.
Process and release testingSamples, specifications, methods, instruments, raw data, calculations, OOS handling, stability and CoAs are linked to the process decisions they support.
Equipment and single-use stateEquipment eligibility, calibration, maintenance, cleaning, assemblies, filters, integrity checks and product-contact history gate execution.
Deviations and changeEvents and changes begin with bank, material, equipment, phase, signal, sample and downstream impact already attached.
Process lifecycleDevelopment knowledge, scale-up, characterisation, validation, technology transfer and commercial configuration remain traceable across process versions.
Concurrent batch releaseGenealogy, execution, viral-safety evidence, laboratory results, holds, equipment, exceptions and approvals mature into one disposition record.
Prepared solutions and purification assetsMedia, feeds, buffers, columns, resins, membranes, filters, cycles, holds and product-contact histories remain connected to each culture and pool.
Continued process verificationVersion-aware parameters, quality attributes, yields, durations, alarms, holds, deviations and results become comparable commercial evidence.

CConnected records

Entity hierarchy
What it records
Kind
Biologic Product
Approved product definition connecting the manufacturing process, control strategy, specifications, stability and release.
entity
Commercial mAb Drug Substance
Approved product pattern with cell substrate, process, control strategy, specifications, stability and release requirements.
template
BM-01 Drug Substance
Effective commercial product state used for the BIO-DS-024 manufacturing lineage.
record
Cell Bank
Master or working bank with origin, characterisation, passage history, storage, vials and use authorisation.
entity
Working Cell Bank
Reusable bank structure for characterised vials, storage positions, use authorisation, withdrawal and remaining population.
template
WCB-3F / Vial 071
Exact authorised working-bank vial withdrawn to begin the BIO-DS-024 lineage.
record
Seed Train
Controlled lineage of culture expansions from a bank vial to production inoculum.
entity
Three-Stage Seed Train
Approved thaw, flask, seed-bioreactor and production-inoculum sequence with acceptance gates.
template
SEED-024
Executed culture expansion from WCB-3F / Vial 071 to the production inoculum.
record
Bioreactor Batch
Production culture with recipe phases, materials, process signals, additions, samples and decisions.
entity
2,000 L Fed-Batch Culture
Approved production-culture phases, feeds, parameters, automation evidence, samples and harvest criteria.
template
BIO-DS-024
Commercial production culture with linked bank vial, seed train, materials, equipment, samples, harvest and disposition.
record
Process Pool
Harvest, clarified material, chromatography fraction, viral-safety pool or final bulk with quantity and state.
entity
Protein A Capture Pool
Approved capture-pool transformation with column, fractions, yield, sample, storage and hold requirements.
template
POOL-024-CAP
Accepted capture pool generated from BIO-DS-024 and column cycle COL-PA-017/C42.
record
Material Lot
Medium, feed, buffer, resin, filter, supplement or other material introduced to the lineage.
entity
Single-Use Assembly
Approved component configuration and physical lot genealogy for product-contact assemblies.
entity
2,000 L Production Assembly
Approved single-use bag, tubing, connector, filter and sensor configuration for production culture.
template
SUA-024-04
Physical production assembly built, checked, connected, used and disposed for BIO-DS-024.
record
Process Sample
Sample tied to a culture, pool, operation, time, tests and the decision it supports.
entity
Figure C.1. Record types, templates and the relationships between them in this blueprint.

DQuestions and answers

What software systems are needed for biologics manufacturing?

Commercial biologics manufacturing generally needs manufacturing execution, bank and material genealogy, process automation or historian integration, laboratory and instrument data, equipment and single-use component control, quality workflows, training, stability and batch disposition. Seal connects those concerns through shared cultures, pools, samples, materials, equipment and decisions.

How is cell-bank genealogy connected to the commercial batch?

The exact bank vial withdrawal creates the first lineage event. Each seed expansion references its source culture, materials, vessel, conditions, samples and acceptance. The production culture, harvest, purification pools and final containers continue that same genealogy, allowing forward tracing from a vial and backward tracing from a released lot.

Can Seal integrate with bioreactor control systems and historians?

Yes. Seal can orchestrate accountable GMP execution while a control system or historian remains authoritative for high-frequency automation data. The integration brings critical events, summaries, values, alarms and source references into the batch step and defines acknowledgement, failure and recovery behaviour.

How are single-use assemblies controlled?

An approved assembly pattern defines positions and eligible component types. The physical run records component and lot scans, expiry, sterilisation state, assembly, connection, integrity checks, use window and disposal. Product-contact genealogy traces to each culture or pool the assembly touched.

How are splits and pools represented in biologics manufacturing?

Each split or pool is a controlled transformation with source and destination containers, quantities, yields, status, time, location, storage, samples and accountable execution. The genealogy therefore represents many-to-one and one-to-many transformations rather than only a parent-child lot list.

How does the system control viral inactivation and virus filtration?

The approved process defines conditions, timing, equipment and filter identity, integrity evidence, sampling, ranges and exception behaviour. Execution captures the actual exposure or filtration course and links any failure to the exact pool and downstream material requiring assessment.

How are in-process analytical results returned to manufacturing?

The active process operation creates the sample with its source, test panel, method, action criteria, priority and waiting decision attached. Approved results return to that operation and can permit continuation, require an approved adjustment, extend a hold or open an investigation.

How are hold times and freeze-thaw cycles managed?

Defined events start hold clocks on the affected containers. Storage, transport, freeze, thaw, sample, transfer and return events update the material history. Scheduling sees approaching limits, and excursions identify the exact exposure interval and downstream lots.

Does Seal support biologics process validation and comparability?

Seal connects process versions, materials, equipment, methods, parameters, validation evidence, changes and executed lot history. It supports controlled execution and data retrieval for validation and comparability work; scientific conclusions and regulatory strategy remain the manufacturer’s responsibility.

What is the best first scope for a biologics implementation?

Prove one complete bank-to-release lineage with a representative seed train, production culture, harvest, purification pools, single-use assemblies, automation data, process samples, holds, deviations and final disposition. Include failed criteria and forward and backward trace exercises, not only the happy path.

Is biopharma MES different from a standard pharmaceutical MES?

The same MES principles apply, but biopharma execution must represent living starting systems, seed expansions, splits and pools, time-sensitive intermediates, prepared solutions, single-use configurations, automation-rich cultures, purification assets, viral-safety steps and lineage across drug substance and drug product. Generic order-and-step records are not enough.

How are chromatography columns and resin reuse controlled?

The selected column or resin carries packing, lot, configuration, storage, sanitisation, cycle count, prior products, method, performance, lifetime limits and product-contact history. Each executed cycle links the load, automation evidence, fractions, pool, yield, cleaning and disposition so later concerns identify the affected population.

Can Seal support continued process verification for biologics?

Yes. Seal retains parameter, phase, process version, scale, bank, material, equipment, method, hold, deviation, yield and quality-attribute context across lots. Approved populations can be trended without mixing incompatible versions, and signals can open investigation, CAPA, change, characterisation or validation work.

What happens if historian or automation data is unavailable?

The interface and expected evidence remain visibly incomplete. The approved continuity procedure defines safe holds, any permitted alternate capture, source recovery, message reconciliation, review and release impact. Recovery verifies the required time range and message identities rather than assuming that restored connectivity means complete batch data.

See your process in Seal.

Bring a procedure or a recurring problem. See how your team can use Neil to build the workflow, investigate the results and improve the next version.

Book a demo