The Factory in the Box / One connected run
Can the next batch
help in time?
A shipment is late. Plan B starts with 300 usable containers and needs 150 a day. Can local batches clear review before stock runs short?
Fictional supply exercise with invented quantities and timing.
Count what’s ready that day. Use stock carried forward and whole batches cleared after their wait and review. The walkthrough’s reserve covers days 1 and 2.
The calculation is loading. Controls and setup links become available when it is ready. Your linked setup remains in the address if loading fails.
Walk through one supply gap
Ready by day 3?
Compare extra filling with more review capacity. You can return to your own setup afterward.
One change, followed through the whole system
Where does the extra batch go?
Plan A is kept for comparison. Change plan B; both face the same daily need.
The scene follows current plan B. Illustrations group equipment and trays; the labels give exact quantities.
A 1,400 / B 1,400
A 900 / B 900
A 0 / B 0
Change current plan B
Which constraint would you move?
Each completes one 100-unit batch per day.
Review stands for checking a batch and its records. Each needs 100 imagined work units. Partial work carries forward; partial batches cannot be released.
Waiting, starting stock and shelf life
Added to the day a batch is made. It may then queue for review capacity.
Expiry removes remaining material at the start of that day. Review never restarts the shelf-life clock. Starting stock is assumed fresh at day 0.
This changes the shared situation, leaving each plan’s settings intact.
Inspect kept plan A
A stays fixed while you edit B. The shared daily need applies to both runs.
Same ledger, one day at a time
When does the gap appear?
Drag or tap the plot to inspect a day. Arrow keys on the day slider do the same.
Today’s usable stock in B
Follow one actual batch in current B
One batch, one record.
What the connection reveals
Capacity needs a calendar.
A rate ceiling cannot tell you what is available today. A newly filled batch may still be waiting. Finishing some of its review creates no usable units until the whole batch is cleared. Stock can also expire while later batches wait.
This is useful when thinking about any process with work arriving, a limited shared review step and something that must be ready in time. It does not establish a real factory’s speed or quality. The original Batch, Supply and Capacity rooms keep their own assumptions and richer equipment views.
Inspect the daily ledger, exact rules and limits
One event order for both runs.
- Expire held material and remaining usable stock whose life ends today.
- Complete one 100-unit batch per pod.
- Use up to the daily review-work limit on eligible batches, oldest first. Each batch needs 100 work units, which can span days.
- Release each whole batch as soon as its review finishes. Its original expiry still applies.
- Serve today’s need from the earliest-expiring usable stock. Record any shortfall as missed need for today. Later stock cannot undo it.
Day 0 starts with a fresh, already released lot; there is no production or need that day. All values and event days are integers. A batch made on day 1 with a shelf life of 8 expires at the start of day 9. If its minimum wait reaches that same day, expiry happens first.
The native Capacity room uses arbitrary work-equivalent units per cycle. This new profile explicitly declares a cycle to be one day, makes batches of 100 product units, and assigns each batch 100 review-work units. The old Supply room’s separate timing defaults are not carried into this model.
Qualified inputs and utilities, complete records and successful reviews are assumed. No outside deliveries, uncertain failures, transport, pricing or professional release decision is simulated. These fictional Product A numbers are not actual medicine quantities, operating instructions, clinical results or a production forecast.
| Day | Made total | Review work today | Released today | Held | Stock left | Need served today | Missed total | Expired total |
|---|
Conservation and timing are checked against a separately written, one-work-unit scheduler with expiry buckets. Agreement checks this declared model; it does not validate a real production process.