Skip to main content

QMS. EBR. MES. ELN. LIMS. One platform. Change it. Stay validated.

Lab, manufacturing and quality on one record, configured from your procedures. Each change your team makes is tested before your QA approves it.

Seal open on lot 26-0917, with the systems it runs in its index, by area, each linking to its blueprint, over the system in hand: the lot's batch record, lab results, deviation, CAPA, change, SOP, training, audit trail, filler, materials, experiment and stability study.
Manufacturing › Batch records
Record in review

Lot 26-0917

mAb-24, filled Fri 6 Nov on Line 2
SOP-FIL-007 v128 of 8 steps signed, 1,912 entries
  1. 1 DispenseWed 4 Nov 11:05168 entriesC-17
  2. 2 FormulateWed 4 Nov 18:40224 entriesC-08
  3. 3 FilterFri 6 Nov 03:24128 entriesC-33Bulk hold
  4. 4 FillFri 6 Nov 10:00816 entriesDEV-041C-36
  5. 5 CapFri 6 Nov 11:30112 entries
  6. 6 InspectSat 7 Nov 16:10208 entries
  7. 7 LabelMon 9 Nov 14:25112 entries
  8. 8 PackMon 9 Nov 17:58144 entries
  9. QA reviewIn reviewC-41

QA confirms all 50 of Blubber's checks and decides seven: five not met, and two findings outside them

Neil reviewed the record overnightBrief ready for QA, Tue 00:18

Lot 26-0917 results

QC, mAb-24 drug product
Assay98.7%95.0 to 105.0%
pH6.05.7 to 6.3
Osmolality291 mOsm/kg270 to 330
EndotoxinRetest dueup to 0.5 EU/mL
SterilityDue 20 NovNo growth
EM platesDue 11 NovGrade A, 0 CFU

Endotoxin run R-1005-02 invalid: spike recovery 31%, limit 50 to 200%

Neil found the invalid endotoxin runRetest due

DEV-041 Line 2 stop

Opened by S. Amato, Tue 08:30
  1. Found
  2. Drafted
  3. Opened
  4. Reviewed
  5. Lots assessed
  6. Closed

Lots assessed

What happened
F-02 stopped 21 min, 6 Nov 02:08
The record says
No interventions, step 4.3
Product
61 vials rejected at the stop
Earlier lots
26-0905, 0908, 0912, 0914
Bulk hold
29 h 40 min, studied to 26 h
Escalated
E. Marchetti, QP, and site head
Seal Edge, F-02 feed track current
2.7 A, then stopped 02:08 to 02:29
Line 2's shift channel in Teams, 02:11“stopper bowl jammed again”
Neil found the stop and drafted DEV-041On Blubber's form, for QA

CAPA-019 Stopper bowl jams

Opened by DEV-041's review, Tue
  1. Opened
  2. Actions
  3. Effectiveness
  4. Closed

Actions

Why it happens
  1. Line 2 stops
  2. The stopper bowl jams
  3. The feed track is wearing: 1.9 A to 2.6 A over five lots
  • Bowl check every hour, v13Effective 21:34
  • Replace the feed trackSat 14 Nov, T. Nakamura
  • Alert on the track over 2.2 AFrom Sat 14 Nov
  • Ten lots without a jamDue with lot 26-0930
Jams on Line 25 since August
Neil found four earlier jams since AugustNone was raised as a deviation

Changeset #15

SOP-FIL-007 v12 to v13
  1. Proposed
  2. Tested
  3. Approved
  4. Trained
  5. Effective

Effective

SOP-FIL-007, step 4.3 Stopper feed

Bowl check: every 2 hours hour during filling.

Drafted from
DEV-041's review, 09:07
If it jams
INT-07 before restart
Applies from
Lot 26-0918
  • 3 new test cases, R. Haldane09:52
12 of 12 test cases passed on v13, 09:54
  • Production, K. Brandt10:40
  • QA, S. Amato11:20
Neil drafted v13 from the review's decisionApproved by S. Amato, 11:20

SOP-FIL-007 Aseptic filling

Production, approved by QA
SOP-FIL-007 Aseptic fillingSection 4

4.3 Stopper feed

Bowl check: every 2 hours hour during filling.

If it jams: Stop the line. Clear it as intervention INT-07. Record it before restarting.

4.4 Restarting after a stop

Open vials in the zone at the stop are rejected at the restart and counted in the batch record.

Neil drafted the redline of step 4.3Effective by the rule on SOP-FIL-007

Line 2 operators

What each is trained on
Training by operator
FIL-007 v12FIL-007 v13GowningAsepticF-02
A. Okafor
J. Lindqvist
M. Rossi
R. Mensah
T. Nowak
L. Ferreira
TrainedDue before their next shiftAnd five more operators
Neil read step 4.3's change with each of the four3 questions each, signed by them

Lot 26-0917 audit trail

Who, when, what and why
Lot 26-0917, every entry1,912 entries, 1 changed after it was made
  1. Step 1.6Drug substance weighed, 21.02 kgT. Nowak
  2. Step 1.6Changed to 21.20 kg. Reason: “typo”T. NowakC-17
  3. Step 3.2Filter integrity test passedJ. Lindqvist
  4. Step 3.2Verified, 3 h 12 min after the workM. RossiC-33
1,912entries, each with who and when
1changed after entry, with its reason
0deleted
Neil read every entry and its historyC-17 and C-33, for QA

Filler F-02

Line 2, aseptic filling
QualificationOQ and PQ, March 2026
Calibration14 Oct, in date to 14 Jan
MaintenanceStopper bowl serviced 21 Oct
LogbookStopped 02:08, Fri 6 Nov
Work orderFeed track, Sat 14 Nov
75vials a minute
20days since service
1work order open
Neil drafted the 02:08 stop for the logbookFor T. Nakamura to sign

What went into lot 26-0917

7 material lots, 4 shown
  • Drug substanceDS-26-033121.2 kgReleased
  • Vials, 10RVL-220142,000Released
  • Stoppers, 20 mmH-2271442,000Released
  • Caps, flip-offCP-090742,000Released
Filled
41,860
Rejected at the stop
61
Rejected at inspection
318
Sampled and retained
142
Held by QA
41,339
Neil checked 7 certificates against their specificationsEach lot released by QC

EXP-332 Bulk hold before filtration

Process development, mAb-24

AimFind how long the bulk can wait before filtration without bioburden rising.

MethodSix holds from 6 to 26 hours at 2 to 8 °C, sampled at the end of each.

Witnessed byN. Farrow, 2 Nov

Bioburden against hold, CFU
Lot 26-0917, 0 CFU
Neil found lot 26-0917's hold past this studyHeld 29 h 40 min; the study covers 26 h

ST-0412 mAb-24

Three conditions, 24 months
Months01369121824
5 °C
25 °C, 60% RH
40 °C, 75% RH
10:006-month pull, today
12vials of 26-0917 for ST-0431
0out of trend
Neil drafted the 6-month pull listAccepted by J. Achterberg

Where the work runs, not where it is filed.

People carry the evidence, and every change, between a separate LIMS, MES and eQMS. On Blubber's Line 2, Seal runs the work itself.

Compared onBefore SealSeal
Going live14 months to stand up Blubber's last system38 days to take Line 2 off paper, with a Seal strategist on site
Fill to QA release27 days, 11 of them record review17 days, 14 of them the sterility test
Changing the filling SOP15 weeks, waiting between signatures30 hours, with the same steps signed

Validated, not frozen.

Every change runs its test cases before your QA approves it. New cases are approved before they run.

The test cases of changeset #15 to SOP-FIL-007, aseptic filling, version v12 to v13. 9 are standing cases Blubber's Validation wrote for go-live; 3 are new, drafted by Neil with the change at 09:31 and approved by R. Haldane in Validation at 09:52, before any ran. All 12 test cases passed on v13 at 09:54. One case is open in full: what it sets up, what it does, what it expects and what happened.
Changesets › SOP-FIL-007 › Changeset #15
Tested 09:54
TC-10New, approved 09:52

Clearing a jam needs a recorded intervention

Sets up
A test lot on v13 at step 4.3, and a 3 min stop of the line
Does
Signs the next fill entry with no intervention recorded
Expects
Refused until intervention INT-07 is recorded for the stop
Happened
Refused, naming the stop. Accepted once INT-07 was recorded
Evidence
The refusal as shown, and INT-07's entry

Passed on v13

TC-11New, approved 09:52

Its start, end and rejected vials are required

Sets up
A test lot on v13 with intervention INT-07 open for a stop
Does
Signs INT-07 three times, leaving out one field each time
Expects
Each signature refused until the field left out is entered
Happened
3 of 3 refused: start, end, rejected vials
Evidence
Each refusal as shown, and the signed INT-07

Passed on v13

TC-12New, approved 09:52

A stop over 10 min opens a deviation for QA

Sets up
A test lot on v13 with stops of 9 min and of 11 min
Does
Records INT-07 for each stop
Expects
A deviation for QA on the 11 min stop only
Happened
One deviation, assigned to QA, for the 11 min stop
Evidence
The deviation and both INT-07 entries

Passed on v13

TC-01Standing since go-live

The check falls due after 60 min

Sets up
A test lot on v13, its last bowl check just recorded
Does
Moves the lot's clock on 59 min, then 60
Expects
Not due at 59 min, due at 60: v13's interval
Happened
Not due at 59 min. Due at 60
Evidence
The lot's due times at 59 and 60 min

Passed on v13

TC-02Standing since go-live

An overdue check is flagged on the record

Sets up
A test lot on v13, its bowl check 1 min overdue
Does
Signs the next fill weight entry
Expects
The overdue check flagged, for the signature to explain
Happened
Flagged, then signed with the explanation
Evidence
The flag, and the explanation signed with it

Passed on v13

TC-03Standing since go-live

Steps 4.1 and 4.2 are unchanged

Sets up
Steps 4.1 and 4.2 of v12 and of v13
Does
Compares each instruction, limit, field and signature
Expects
No difference
Happened
No difference
Evidence
The two versions' steps, compared field by field

Passed on v13

TC-04Standing since go-live

Steps from 4.4 on are unchanged

Sets up
Every step from 4.4 on, in v12 and in v13
Does
Compares each instruction, limit, field and signature
Expects
No difference
Happened
No difference
Evidence
The two versions' steps, compared field by field

Passed on v13

TC-05Standing since go-live

Fill weight limits are unchanged

Sets up
A test lot on v13 at step 4.2, pump 2
Does
Enters pump means of 9.99, 10.00, 10.40 and 10.41 g
Expects
10.00 and 10.40 g in limits, 9.99 and 10.41 g out, as on v12
Happened
As expected, all four
Evidence
The four entries and each one's limit result

Passed on v13

TC-06Standing since go-live

Lot 26-0917's record stays on v12

Sets up
A copy of lot 26-0917's record, filled on v12
Does
Makes v13 effective in the test environment
Expects
The record stays on v12 and no entry reopens
Happened
On v12, its 1,912 entries unchanged
Evidence
The record's version and entries, before and after

Passed on v13

TC-07Standing since go-live

The next fill starts on v13

Sets up
A new test lot, opened after v13 is effective
Does
Opens step 4.3
Expects
v13's step, the bowl check every hour
Happened
v13, the check every hour
Evidence
Step 4.3 as the new lot opened it

Passed on v13

TC-08Standing since go-live

An untrained operator is flagged at 4.3

Sets up
Two test operators, one trained on v13 and one only on v12
Does
Each takes step 4.3 on a test lot on v13
Expects
The first is checked; the second is flagged
Happened
Checked. Flagged: not trained on SOP-FIL-007 v13
Evidence
Each check, and the flag as shown

Passed on v13

TC-09Standing since go-live

The audit trail records both versions

Sets up
An entry at step 4.3 on v12 and one on v13
Does
Reads each entry's audit trail
Expects
Each names its version, who, when and why
Happened
v12 and v13 named, each with who, when and why
Evidence
Both entries' audit trails

Passed on v13

Test cases

All 12 passed on v13

3 newDrafted by Neil, approved by R. Haldane 09:52

9 standingWritten by Blubber's Validation at go-live

The 3 new test cases were approved at 09:52, before any case ranTC-10 was drafted by Neil at 09:31 with the change and approved by R. Haldane in Validation at 09:52, before it ranTC-11 was drafted by Neil at 09:31 with the change and approved by R. Haldane in Validation at 09:52, before it ranTC-12 was drafted by Neil at 09:31 with the change and approved by R. Haldane in Validation at 09:52, before it ranTC-01 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-02 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-03 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-04 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-05 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-06 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-07 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-08 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917TC-09 was written for go-live on 22 Sep, for any change to a step; changeset #15 ran it with v12, v13 and lot 26-0917

MiAlgae cuts documentation time by 75%.

MiAlgae moved its ELN, quality processes and batch records into Seal as it scaled from lab to commercial production.

An operator working at MiAlgae’s production facility

Keep the systems you rely on.

Blubber's drug substance site kept its LIMS, eQMS and document vault. Seal reads them, and each master stays there.

Drug substance lot DS-26-0331's batch record in Seal, at Blubber's drug substance site, and the systems the site kept: it read its master batch record and specification from Veeva Vault, a probe's calibration from Blue Mountain RAM, its crew's training from Cornerstone, the bioreactor's temperature from AVEVA PI, the low-pH hold from Emerson DeltaV, results from LabWare and a deviation's status from MasterControl. Each master stays in the system it came from. The lot was released on Thu 29 Oct, and 21.2 kg of it was dispensed into lot 26-0917 on Line 2 on Wed 4 Nov
Lots › DS-26-0331 › Connected systems
Released 29 Oct
FromThu 29 Oct, 10:06
v4The limits the 18 results were checked against
Landed on
QA review, results
Through
Vault library, read-only

Master in Veeva Vault. Seal reads the effective version.

Before you start.

Is Seal a LIMS, an MES or a QMS?

Seal covers LIMS, ELN, MES and QMS on one record that lab, manufacturing and quality all read and write. A batch links to its samples, results and quality events. Start with the processes you need and add the next to the same record. Find a GxP blueprint.

Can we change the system after it is validated?

Yes. Continuous validation means managing the validated state through change, not freezing the configuration. Keep the reason for the change, affected requirements, updated specifications, verification results and approvals together in Seal. Assess the impact and risk to determine the assurance needed. Automated checks support that assessment; they do not replace accountable review or any additional UAT your intended use requires. Read about continuous validation.

Does it support 21 CFR Part 11 and EU Annex 11?

Each record keeps its audit history and electronic signatures, with controls to support 21 CFR Part 11 and EU GMP Annex 11. Seal’s security controls are audited by an independent firm to SOC 2 Type 2, and the report is in the Trust Center. See how Seal fits GxP.

Do we need to replace our existing systems?

No. Start with a defined job and the records it needs. Neil can work with connected systems; processes you choose to run in Seal can be introduced in stages. Agree which system owns each record, what can be read or written and how the connection will be verified. See the integrations.

How is Neil itself validated?

For each job you give Neil, your team evaluates it on representative records against acceptance criteria your experts set before it is used, and again under change control after any change of model or configuration. In line with the EU’s draft GMP Annex 22, Neil decides nothing in GMP work: it reads, checks and drafts, and a qualified person reviews what it finds. See Neil at work.

Where is our data hosted, and is it used to train AI?

Seal agrees the hosting region at onboarding and confirms the AI provider, processing location, retention and model terms for your organisation during onboarding and supplier review. Under Seal’s agreements, customer data is not used to train AI models; the records Neil uses as working context are not training the underlying model. Review the AI and data controls.

How quickly can we evaluate our own process?

Once we agree the evaluation scope and receive the required inputs, we prepare the first working process and supporting validation pack within 48 hours. The pack includes source traceability, recorded test results and configuration history. Your team can execute the process and inspect its records. Production use follows your intended-use assessment and quality controls.

What do we need to share to get started?

A short outline of the work and a work email are enough for the first conversation. For a process evaluation, we agree the scope with its owner and use a representative procedure, batch record or form. You can start with a sample, or arrange an NDA before sharing your own material.

See your process in Seal.

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