How should finite experimental and pilot capacity be allocated to maximise expected milestones without blocking contracted production work?
Independent model study · DBTL portfolio
Protect production milestones while the experimental portfolio keeps learning
Allocate screening, confirmation, pilot and analytical capacity when programmes differ in technical-success probability, information value and due date.
DesignBuildMini-reactorsAssayConfirmPilotCMO handoff
Decision model
A bounded question with a complete plant consequence.
Design queue through mini-bioreactor experiments, assays, confirmation, pilot run, data package and external manufacturing handoff.
Equations and accounting rules
Screen capacity = reactor count × runs/day × availabilityExpected milestone value = probability-weighted accepted gatesScale fidelity compares kLa, P/V, tip speed, mixing and heat marginQueue age and repeat demand update after every gateBase, alternative and stress cases
- FIFO versus value-weighted allocation
- Protected urgent-development capacity
- High failure/repeat portfolio
- Additional pilot slot or lower repeat rate
Engineering brief
Model the complete decision, not an isolated unit operation.
Ginkgo Bioworks historically disclosed a Design–Build–Test–Learn foundry loop, scale-down work and translation to external manufacturing. The current study uses that public historical pattern, not a description of present asset operation.
Every programme, priority, probability and result is synthetic. The article may mention Ginkgo in its evidence section, but the durable search intent is biotech-foundry capacity planning.
01 · Model basis
What the Acatian model needs to resolve
Inputs, mechanisms, limits and outputs remain reviewable on one declared basis.Inputs
Programme priority, due date and stage-gate criteria
DoE size, replicates, duration and repeat rate
Reactor, pilot and analytical calendars
Scale criteria, CMO windows and milestone value
Mechanisms
Screen capacity = reactor count × runs/day × availability
Expected milestone value = probability-weighted accepted gates
Scale fidelity compares kLa, P/V, tip speed, mixing and heat margin
Queue age and repeat demand update after every gate
Constraints
Mini-reactor and pilot slots
Analytical turnaround and sample queues
Scale-down identifiability
External CMO window and due dates
Outputs
Programme throughput and expected milestones
Queue age, repeats and asset utilisation
Pilot demand and transfer timing
Value of added capacity or better fidelity
02 · Acatian workflow
Build it in six controlled steps
Each step creates a reviewable object, not a hidden spreadsheet assumption.- 01
Define programmes and promotion gates.
- 02
Map experiment designs and resource demand.
- 03
Add uncertain outcomes and repeats.
- 04
Test scale-fidelity criteria.
- 05
Schedule pilot and transfer windows.
- 06
Compare throughput, delay and expected value.
03 · Decisions
Questions the model should answer
Which programme receives the next slot?
Where does analytics—not fermentation—queue?
How many replicates reduce downstream risk?
Is another pilot asset economically justified?
04 · Evidence boundary
Validate before the result carries weight
Validation
Back-test stage duration, repeat rates and gate predictions against authorised portfolio history; report calibration error rather than only expected value.
Limitations
This is not a current Ginkgo operating model or a promise of technical success. Historical public disclosures must not be presented as current universal capability.
Public evidence
What the company context supports—and what it does not.
Sources establish the public process architecture. They do not reveal private operating parameters, site performance or an Acatian relationship.Frequently asked questions
Practical modelling questions
Is this the named organisation's real plant model?
No. It is an independent hypothetical Acatian study based only on the cited public process architecture. It claims no affiliation, endorsement, deployment, confidential data or actual plant performance.
Where do the numerical inputs come from?
Every input must be marked as a public fact, literature estimate, transparent engineering assumption or authorised customer input. The public article does not invent private operating values.
Can the model be calibrated to a real facility?
Yes, when the operator supplies authorised process, equipment, schedule and utility evidence and agrees the intended use, acceptance criteria and validation plan.