Recipes. Procedures. Specifications. Studies. PLM. Every version, and where it runs.
A product is its recipe, procedures, specification and studies, each with versions of its own. Seal keeps them as one record across its lines.
mAb-24 for Rookery Bio
Every lot keeps the versions it was made to.
A lot takes its recipe's version when it is created, and a procedure's when the step starts. Neither is rewritten by a later version.

Lots mAb-24, Line 2
Lot 26-0909 filled Tue 22 Sep
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v11v12 from Fri 2 Oct, v13 from Tue 10 Nov
FP-24 v3
Lot 26-0910 filled Tue 29 Sep
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v11v12 from Fri 2 Oct, v13 from Tue 10 Nov
FP-24 v3
Lot 26-0911 filled Thu 1 Oct
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v11v12 from Fri 2 Oct, v13 from Tue 10 Nov
FP-24 v3
Lot 26-0912 filled Thu 8 Oct
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0913 filled Wed 14 Oct
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0914 filled Tue 20 Oct
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0915 filled Tue 27 Oct
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0916 filled Mon 2 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0917 filled Fri 6 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v12v13 from Tue 10 Nov
FP-24 v3
Lot 26-0918 filled Wed 11 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v13
FP-24 v3
Lot 26-0919 filled Thu 12 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v13
FP-24 v3
Lot 26-0920 filled Fri 13 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v13
FP-24 v3
Lot 26-0921 filled Mon 16 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v13
FP-24 v3
Lot 26-0922 filled Tue 17 Nov
MB-24 v7v8 from Wed 18 Nov
SOP-FIL-007 v13
FP-24 v3
Lots from 26-0923 created from Wed 18 Nov
MB-24 v8
SOP-FIL-007 v13
FP-24 v3
A study, and everything that rests on it.
EXP-332 studied the bulk hold to 26 h. Both lines' recipes, their test cases, a deviation and the next study rest on that.

EXP-332 Bulk hold before filtration
- Studied
- Six holds of 6 to 26 h at 2 to 8 °C
- Witnessed
- N. Farrow, process development
- Being extended
- To 36 h
Questions about PLM.
Is this only a document repository?
No. The process definition can inform executable protocols, with fields, calculations, material references and review steps. Documents and external records remain part of the supporting evidence.
How does this differ from a discrete-manufacturing PLM tool?
Discrete PLM tools model parts, assemblies and revisions. A biologics process also needs unit operations linked to parameters and quality attributes, material qualification, cell bank lineage and site versions. Seal models those as connected records that can inform execution, so the process definition and the work it governs are not maintained separately.
What does Seal not replace?
Seal does not replace control systems, historians, instrument software, ERP or eCTD publishing tools. Define which system owns process control, source measurements, inventory and orders, and scope connections around the records the workflow needs.
How does this support tech transfer to a CDMO?
The receiving site starts from a structured copy of the sponsor’s process version rather than a document package. It reviews each element and records site differences with their rationale. When the sponsor revises its version, the receiving site can decide whether to adopt the change, and that decision is recorded. Comparability evidence links to the pair of versions it bridges.
Is a transferred process ready to run at the receiving site?
No. Reusing the definition reduces reconstruction, but the site must still resolve equipment mapping and local differences. The agreed qualification, verification, training and authorisation are completed before use.
We are a CDMO running multiple sponsor programmes. Does this work for us?
Yes. Each programme can keep its own process records, change control and audit history, with access scoped to that sponsor. Your MSAT team works across programmes while each sponsor sees only its own records.
What does recipe-driven development mean in practice?
Development work links to a draft process version from early experiments rather than being translated from notebooks at the end. DOE results attach to the parameter ranges they informed. When the process moves to GMP, the master batch record is reviewed and approved from that definition rather than written from scratch.
Does this conflict with our eCTD publishing tool?
No. Seal can draft CMC content from the process record, and your publishing tool handles assembly and transmission. Regulatory authors review the content before it is filed.
How does this support ICH Q12 and established conditions?
Established conditions can be tagged on the process elements they apply to. A proposed change then shows which tagged elements it touches and any linked PACMP. Your regulatory team uses that to assign the reporting category.
What about ICH Q14 and analytical procedures?
Analytical methods can be records in the same model, linked to their validation evidence and the quality attributes they measure. When a method changes, you can see which specifications and stability studies depend on it.
How does this handle scale-down models?
A scale-down model can be recorded as a process version linked to its commercial parent, with qualification studies stating which parameters it represents. When the commercial process changes, the link shows which qualifications need review.
How do we move existing programmes onto this without halting work?
Start with one programme, usually the next one entering tech transfer or PPQ. Structure its master batch record, parameters, quality attributes, materials and cell line lineage, and link the existing validation and comparability evidence. Commercial programmes can move at a planned change cycle without disturbing the approved batch record.
Does this replace our MES?
If you use Seal for execution, the master batch record and process definition share the same records. If you keep an existing MES, Seal can expose the process definition and change impact through its API while your MES remains the execution system.
How does AI help with tech transfer?
Neil can compare the sending process version with the receiving site’s context and draft a parameter difference table or comparability plan for review. It can also compare executed batch records against the current process version and point out differences. Your MSAT and quality teams assess its output.
What about regulatory commitments tied to materials or cell banks?
A CMC commitment, such as animal-origin-free media or a specific cell bank lineage, can be linked to the record it concerns. When a supplier change notification arrives or a cell bank is reviewed, the linked commitments and submission sections can be found from that record.
In depth
The PLM guide7 sections
All 16 capabilities
- Technology transfer
- The receiving site starts from a copy of the configured process, not a document package. Neil prepares the gap assessment and the local changes.
- Manufacturing science
- Neil compares batches and sites, investigates differences and drafts process changes, with the evidence ready for your team’s technical review.
- Process development
- Run development protocols on the platform that carries them into manufacturing. Neil compares experiments and prepares the next study.
- CMC knowledge
- Every limit, method and result keeps the records it rests on, at their versions. Neil answers from them and drafts Module 3 for you to sign.
- Versioned process definition
- Unit operations, parameters, quality attributes, materials, equipment requirements and methods in one versioned definition that can inform the master batch record, site versions and CMC content.
- Recipe-driven development
- Development experiments can run against a draft process version. DOE results link to the parameter ranges they informed, so the justification for a setting stays with the studies behind it.
- Structured tech transfer
- Create the receiving site’s version from the sending definition. Record site differences with their rationale and use them to scope the comparability plan and engineering-batch work. The transferred definition is not evidence that the site is ready.
- Established conditions / ICH Q12
- Tag established conditions on the process elements they apply to. A proposed change can show which tagged elements it affects, to inform the reporting category your regulatory team assigns.
- MSAT continuity and CPV
- Link campaign learnings to the unit operation, parameter, material or equipment they concern. Continued process verification can refer to the same process version and its history.
- CPP / CQA / QbD traceability
- Link each critical process parameter to the quality attributes it may affect and the evidence behind its range, including the rationale, uncertainty and scale it covers.
- Cell line and bank lineage
- Research cell line, MCB, WCB and end-of-production cells as linked records, with characterisation, stability and passage history.
- Raw material AVL and single-source risk
- Approved sources on each material, with animal-origin status, grade, qualification and audit history. Sole-source critical materials can be identified from the same records.
- Multi-site comparability
- Each site runs a versioned instance with its recorded differences. Comparability evidence links to the versions it bridges.
- CMC content from the process record
- Draft Module 3 process sections, such as 3.2.S.2.2 and 3.2.P.3.3, from the current process definition, and compare a proposed version with the one previously filed. Regulatory authors review the content before submission.
- Change impact review
- Before approval, a proposed change can list the sites, transfers, CMC sections, validation evidence and comparability scope linked to the affected elements.
- AI impact review / Neil
- Neil can assemble the processes, materials and site versions a proposed change may affect and point out site differences or single-source materials for review. Your team assesses the impact and decides.


See your process in Seal.
Working 48 hours after we agree its scope: tested, with evidence your QA approves.