Manufacturing run
RUN-214
- Hold duration
- 7.8 h
- Yield
- 75%
Understand the difference. Improve the process.
Give Manufacturing Science and Technology the development knowledge, batch history and site context behind the process. Ask neil to investigate variation and prepare the technical work needed to improve it.
Bring your process question
Why did yield fall after transfer?
You: Yield has fallen since transfer. Compare the manufacturing runs with development and tell me what to investigate.
neil
The three manufacturing runs have longer holds and lower yields than the development reference. RUN-214 has the longest hold and lowest yield. That is a lead worth examining—not evidence that the hold caused the loss.
Yield (%)
Hold duration (h)
Hollow point: development median. Solid points: individual manufacturing runs.
View all values
| Record | Hold duration (h) | Yield (%) |
|---|---|---|
| DEV-REF | 0.8 | 90 |
| RUN-201 | 6.4 | 79 |
| RUN-207 | 6.9 | 77 |
| RUN-214 | 7.8 | 75 |
You: Should we shorten the hold limit?
neil
Not from these summaries alone. I would first verify the hold definitions and yield basis, then compare temperature, materials, scale and transfer conditions. A controlled follow-up can test the hold hypothesis. Changing an operating limit needs its own technical assessment and authorised review.
You: Write the technical assessment and the evidence requests.
neil
I’ve kept the observation separate from the hypothesis and assigned the missing evidence to the relevant teams. The assessment is ready for MSAT review; it does not change the process or decide batch disposition.
ASSESS-014 / post-transfer yield assessment
DraftInvestigate the hold alongside the other transfer differences.
- Observation
- Lower yield with longer holds
- Hypothesis
- Hold-related loss; not established
- Next evidence
- Matched run data and transfer conditions
From lab scale to commercial production.
MiAlgae brought its electronic lab notebooks, quality processes and batch records into Seal as it scaled its algae production.
See how MiAlgae uses SealThe work does not end with an investigation.
Use the same process context for today’s support question, the next transfer and the longer-term improvement.
Manufacturing support
An assessment with alternative explanations and evidence requests.
Manufacturing support
An assessment with alternative explanations and evidence requests.
Bring batch execution, historian, laboratory and material evidence into the same technical investigation.
Explore manufacturing supportTechnology transfer
Transfer gaps, technical rationale and an acceptance package for review.
Technology transfer
Transfer gaps, technical rationale and an acceptance package for review.
Compare the sending process with the receiving site’s scale, equipment, materials and methods.
Explore technology transferContinued process verification
A trend assessment with exclusions, source data and follow-up work.
Continued process verification
A trend assessment with exclusions, source data and follow-up work.
Review trends with their process version, population and operating context. Investigate the signal, not just the chart.
Explore continued process verificationChange impact across sites
A site-specific impact assessment and proposed verification work.
Change impact across sites
A site-specific impact assessment and proposed verification work.
Trace a proposed material, parameter or equipment change to the processes and evidence it affects.
Explore change impact across sitesWork across the systems you already use.
Connect permitted records from your ELN, LIMS, historian, ERP and documents—or start with supplied data. neil brings the relevant evidence into the work in Seal.
Procedures & quality records
Samples & analytical results
Materials & production context
Development & transfer documentsHow access and connections work
Connections and available actions depend on the source system, API and configured permissions. Agree the records and access for the job; retain source references and versions in the output. Connecting a system does not grant neil unrestricted access or permission to change it.
Explore the connectionsFollow a batch through Seal.
In this product walkthrough, example batch B-041 links its recorded hold to sample IPC-041 and investigation DEV-018. Open the records to see the evidence and the review still needed.
The batch carries its readings, lab sample and investigation together.
Keep the reviewed conclusion with the process version. A proposed change can carry its affected records and verification work forward; it does not rewrite the original batch.
Follow the change into implementationQuestions from MSAT teams.
Seal connects development knowledge with manufacturing experience. Ask neil to compare permitted batch, laboratory, historian and document evidence, prepare a technical assessment and prepare the follow-up work in Seal. MSAT retains responsibility for the scientific conclusion and proposed process change.
No. It can run parts of those workflows, but the MSAT blueprint primarily connects their evidence to a controlled process model and the technical decisions, changes and commitments that evidence supports.
New batches, trends, studies, investigations, transfers and changes propose structured changesets. Technical owners review each addition, modification, removal or conflict before a new knowledge version becomes effective.
Yes. A support case assembles the batch, operation, materials, equipment, process data, samples, tests, alarms, interventions, deviations and prior knowledge, then records evidence requests, actions, technical response and closure.
Dataset and population, features, transformations, algorithm, assumptions, version, fit, diagnostics, intended use, applicability, validation, monitoring, reviewer, changes and retirement remain controlled.
CPV signals arrive with the population, baseline, stratification and batch context. MSAT evaluates technical meaning, investigations, model or control updates, actions, changes and commitments against the process knowledge model.
Yes. A global process model owns common intent while each site configuration records equipment, automation, scale, materials, methods, procedures, local controls, applicability, evidence and effective dates.
An approved decision identifies affected recipes, records, monitoring plans, validation requirements, specifications, training, methods, reports, transfers, risks and regulatory content. Each consumer receives tracked implementation work.
Yes. Historical reports, spreadsheets, statistical files and system records can seed proposed structured objects. Human technical owners review extraction and applicability before anything becomes approved process knowledge.
Bring one technical question, the relevant process version and a bounded set of records. For a post-transfer yield question, that might include development and manufacturing run summaries, source calculations and the transfer assessment. Agree the comparison and desired output, then inspect whether each finding is supported and whether the follow-up work is useful. Expand the scope after that evaluation.