Skip to main content

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.

Product mAb-24 in Seal on Thu 3 Dec at 10:00, made for Rookery Bio, the client. Both lines share its specification, SPEC-DP-24 version 3; studies EXP-318, EXP-321 and EXP-332, which N. Farrow decided on Thu 19 Nov cover Line 1 too; its 10R vial and 20 mm stopper; and the formulation vessel, V-201. Line 2 runs master recipe MB-24 version 8, effective for lots from 26-0923, on filler F-02 with fill program FP-24 version 3 and filling procedure SOP-FIL-007 version 13; a fill takes 9 hours 40 minutes, and lots 26-0909 to 26-0922 were made to version 7. Line 1 is in transfer, T-022: its recipe is a draft copied from version 7, 22 of its 26 steps as copied, on filler F-01 with fill program FP-24-L1 version 1; its filling procedure SOP-FIL-009 is with QA; a fill there takes 14 hours 30 minutes and waits for study EXP-341, results Tue 8 Dec; and it has made no lot, with PPQ from Mon 11 Jan. Nothing in Line 1's draft is approved.
Products › mAb-24
Thu 3 Dec, 10:00

mAb-24 for Rookery Bio

Two lines, one in transfer

Both lines
Specification
SPEC-⁠DP-⁠24 v3What a lot is tested against
Studies
EXP-⁠318Mixing, uniform from 25 min
EXP-⁠321Filter, 3.4 bar with mAb-⁠24
EXP-⁠332Bulk hold, 6 to 26 h
Vial and vessel
20 mm stopper
V-⁠201Formulation vessel
Line 2Line 1 in transfer, T-022
Master recipe
MB-⁠24 v8Effective, lots from 26-⁠0923
MB-⁠24 for Line 1Draft, 22 of 26 steps as copied
Filler
F-⁠024 pumps, 75 a minute
F-⁠012 pumps, 50 a minute
Fill program
Named by step 4.1
Named by the draft's step 4.1
Filling procedure
SOP-⁠FIL-⁠007 v13Effective Tue 10 Nov
Fill time
Inside its 12 h media fill
14 h 30 minWaits for EXP-⁠341, Tue 8 Dec
Lots
14 made to v726-⁠0909 to 26-⁠0922
PPQ from Mon 11 Jan
What both lines share is one record, not a copy on eachLine 2 runs v8. Every lot made to v7 keeps v7Line 1's is a draft. Nothing in it is approved, and no lot runs itEvery record that defines mAb-⁠24: the product's once, each line's on its lineA lot is made to its recipe and tested against its specificationEXP-⁠318 covers Line 1: the same vessel, V-⁠201. N. Farrow, Thu 19 NovEXP-⁠321 covers Line 1: the same filter type. N. Farrow, Thu 19 NovEXP-⁠332 covers Line 1 with v8's rule past 26 h. N. Farrow, Thu 19 NovThe same vial and stopper on both lines. Line 1 already fills them for other clientsBoth lines' bulk is mixed in V-⁠201 and goes through the same filter typeChangeset #17, approved Tue 17 Nov 11:05 by S. Amato, QA, for lots created from Wed 18 NovCopied from Line 2's v7 by K. Brandt, Mon 16 Nov. Nothing in it is approvedF-⁠02's record. Seal Edge reads it and sends it nothingF-⁠01's record, read by Line 1's Seal EdgeStep 4.1 of MB-⁠24 names F-⁠02's fill program and its versionF-⁠01's own program, in the draft since its steps changed on Fri 27 NovChangeset #15: v13 in force from Tue 10 Nov 21:34SOP-⁠FIL-⁠009: signed for Production by K. Brandt on Wed 2 Dec, and with S. Amato, QAA night's fill on Line 2 runs 00:20 to 10:00No study holds filtered bulk that long. EXP-⁠341, N. Farrow, started Mon 23 NovLots 26-⁠0909 to 26-⁠0922 were made to v7 and keep itThree PPQ lots from Mon 11 Jan, once every difference is closed, the draft is approved and Rookery Bio has approved the move

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.

The lots of mAb-24 on Line 2 in Seal on Thu 3 Dec, each with the version of three records it was made to. Master recipe MB-24: lots 26-0909 to 26-0922 were made to version 7, and lots from 26-0923 are made to version 8. Filling procedure SOP-FIL-007: lots 26-0909 to 26-0911 were made to version 11, lots 26-0912 to 26-0917 to version 12, and lots from 26-0918 to version 13. Fill program FP-24: every lot to version 3. Lot 26-0917, filled Fri 6 Nov, was made to MB-24 version 7, SOP-FIL-007 version 12 and FP-24 version 3. SOP-FIL-007 version 13 came into force on Tue 10 Nov and MB-24 version 8 on Wed 18 Nov; the lot keeps version 12 and version 7. A later version never rewrites a lot's record. Each lot opens to the versions it was made to and the ones that came after.
Products › mAb-24 › Lots
Thu 3 Dec

Lots mAb-24, Line 2

14 made to MB-24 v7, v8 from 26-⁠0923

MB-⁠24Master recipeSOP-⁠FIL-⁠007Filling procedureFP-⁠24Fill program

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 lot created now takes v8, and v13 when its fill startsv8 was approved the day 26-⁠0922 was filled. The lot keeps v7Two versions came after 26-⁠0917. Neither changed its recordA later version never rewrites a lot's recordMB-⁠24 v7: lots 26-⁠0909 to 26-⁠0922 were made to itMB-⁠24 v8, changeset #17: approved Tue 17 Nov 11:05, for lots created from Wed 18 NovSOP-⁠FIL-⁠007 v11, in force from Mon 11 MaySOP-⁠FIL-⁠007 v12, changeset #14: in force from Fri 2 OctSOP-⁠FIL-⁠007 v13, changeset #15: in force from Tue 10 Nov 21:34FP-⁠24 v3: step 4.1 names it in v7 and in v8, which changed step 3.1 alone

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.

Study EXP-332 in Seal on Thu 3 Dec, bulk hold before filtration: six holds of 6 to 26 hours at 2 to 8 °C, witnessed by N. Farrow, process development, and being extended to 36 hours. Six records rest on it, in the order they came to. On Line 2: step 3.1 of MB-24 version 7, superseded, a limit of 36 hours studied to 26, with 14 lots made to it; deviation DEV-041, closed, for lot 26-0917, held 29 hours 40 minutes, 3 hours 40 minutes past the study; and step 3.1 of MB-24 version 8, effective, where past 26 hours filtration waits for QA. On both lines: two test cases, held 25 hours 59 minutes, filtration starts, and held 26 hours 01 minute, filtration waits for QA, which pass. On Line 1: step 3.1 of the draft, version 8's step, taken with 2 of its 3 test cases; and study EXP-341, which starts from bulk held 26 hours, results Tue 8 Dec.
Studies › EXP-332 › Used by
Thu 3 Dec

EXP-⁠332 Bulk hold before filtration

6 records rest on it, on 2 lines

Studied
Six holds of 6 to 26 h at 2 to 8 °C
Witnessed
N. Farrow, process development
Being extended
To 36 h
  1. MB-⁠24 v7Step 3.1Line 2Superseded
  2. DEV-⁠041Lot 26-⁠0917Line 2Closed
  3. MB-⁠24 v8Step 3.1Line 2Effective
  4. Test cases2 of v8's 3Both linesPass
  5. MB-⁠24 for Line 1Step 3.1Line 1Draft
  6. EXP-⁠341Fill timeLine 1Results Tue 8 Dec
v7's limit rested on it, and 14 lots were made to v7One lot went past it. Its deviation cites the studyv8 took the study's 26 h. Past it, filtration waits for QAIts test cases stand a minute either side of 26 hLine 1's draft took the same step, and the study with itThe next study starts where this one stopsSix records on two lines rest on the study's 26 h, each with its stateLots 26-⁠0909 to 26-⁠0922 were made to v7 and keep itFound by Neil on Mon 9 Nov at 22:15. QA accepted the hold on Fri 13 NovChangeset #17, proposed by Neil from DEV-⁠041 and approved Tue 17 Nov 11:05. The 36 h limit staysPassed on v8 on Mon 16 Nov at 09:42, and on Line 1's draft on Mon 30 Nov at 09:12K. Brandt, the draft's owner, took v8's step 3.1 on Wed 18 Nov 09:20. N. Farrow decided on Thu 19 Nov that the study covers Line 1EXP-⁠341, N. Farrow: bulk held 26 h, filtered, then sampled at 10, 13 and 16 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.