Configure and run your USP protocols in Seal: inoculation, feeding, sampling and harvest. Keep actual conditions and results with each execution. Use neil to help configure the workflow, compare cultures and investigate performance.
Configure reusable inoculation, feeding and sampling workflows. Record actual additions, observations and sample links as the study runs—not only in the final comparison.
Compare culture profiles alongside the feed strategy and harvest results.
Two feed strategies. Same cell source.
┄ USP-028 / daily━ USP-029 / split
2 L fed-batch · fictional studyInspect the study records
Cell source CL-04 / bank WCB-02, starting working volume 2 L, basal medium M-06 v01 and feed formulation F-03 v02. Recipes UP-08 v02 and v03 differ in the planned feed schedule. Compare actual additions and control histories before treating this as a matched experiment.
Viable cell density (10⁶ cells/mL)
Day
USP-028
USP-029
0
0.5
0.5
2
2.2
2.3
4
6.5
6.8
6
12
12.5
8
17
17.5
10
18
19
12
16
18
14
12
16
Viable cell density and viability: CELL-02 v03. Glucose: MET-04 v02. Harvest titre: TTR-02 v03; USP-028 3.6 g/L, USP-029 4.1 g/L. One observation at each time, not replicate means. No complete product-quality panel is supplied.
Did the new feed strategy improve the culture?
neil
The cultures separate late in the run.
USP-029 retains more viable cells after day 10. Compare the glucose and viability profiles before attributing the difference to the feed schedule.
Two runs suggest a question—not an optimum.
Read the draft process comparison ↗
Test whether the pattern repeats.
The split-feed run has a higher observed day-14 titre (4.1 versus 3.6 g/L) and viability (89% versus 78%). The sampled glucose profile also differs. These observations do not isolate a feed effect.
Proposed follow-up
Reconcile delivered feed, seed history, pH, dissolved oxygen and temperature records for both runs.
Design a replicated feed comparison with matched cell source, media, sampling and harvest criteria.
Assess product quality and harvest suitability alongside titre and viable cell density.
Draft based on fictional USP-028 and USP-029, recipe versions and sample results. No feed strategy or scale-up is approved.
From the seed train to the harvest.
Each study should inform the next—not become another disconnected spreadsheet.
Culture conditions & control
Compare the process that actually ran: pH, dissolved oxygen, temperature, gases and interventions.
What stays connected
Align setpoints, measured signals, alarms and manual changes with process age and sample times. Retain vessel and sensor context rather than treating an overlay as proof of comparable conditions.
Media & feed development
See the formulation and actual additions behind the performance—not just the recipe name.
What stays connected
Retain material lots, formulation versions, feed timing and amounts, sample results and deviations. Separate intended changes from what happened in the run.
Seed train & culture
Follow the starting vial through expansion and into the bioreactor. Compare the run in context.
What stays connected
Keep inoculum age, viability, vessel, working volume, setpoints, actual signals and interventions with the samples they affect. Preserve time windows for fed-batch and perfusion analysis.
Scale-up & harvest
Carry the process rationale to the next scale, then hand downstream a traceable harvest.
What stays connected
Record geometry, mixing and transfer assumptions, operating ranges, confirmation studies and harvest conditions. Connect the resulting material to purification results without treating scale-up as a copy of setpoints.
The harvest is a handoff. Not the end of the record.
Let downstream see which culture, conditions and samples produced its starting material. Bring purification findings back into the development decision.
Work from Ambr, bench-scale bioreactor and historian exports, analytical results and existing study records. Scope the connection around the question your team needs to answer.
Yes. Configure reusable protocols with instructions, fields, calculations, linked samples and review steps. Each execution retains the version used, recorded values, observations and results. neil can help prepare the configuration and analyse the resulting evidence; your team tests the workflow and defines the review and approval requirements for its intended use.
Cell line development evaluates and selects the biological candidate. Upstream process development establishes how to culture that cell line or strain: media, feeds, seed train, control strategy, process mode, harvest and scale-up. The records connect, but they answer different questions.
Start with permitted exports or an agreed connection. Keep vessel geometry, working volume, cell source, media and feed versions, process age, actual control profiles and sampling methods in view. An overlay alone does not establish that scales or conditions are equivalent.
No. It shows two fictional 2 L fed-batch runs with different feed schedules and one reported observation at each sample time. There are no replicate estimates or complete quality results. The pattern supports a follow-up comparison, not a causal claim or an approved feed strategy.
Yes. Connect exchange and bleed rates, cell retention, filter state, viable cell density, sample times and harvest intervals. Use calculation bases appropriate to the mode; a perfusion harvest interval is not interchangeable with a final fed-batch harvest.
A source-linked run comparison, differences in recipe and actual execution, open analytical questions and a draft follow-up study. Scientists review the interpretation, choose the design and decide which process to advance.
The selected recipe, materials, operating ranges, scale criteria, equipment assumptions, analytical methods and supporting studies. Keep receiving-site differences and verification work explicit. Copying setpoints does not demonstrate equivalent process performance.