Add Setup and Unit Cycle Time Across a Small Production Batch
A shop’s production window is consumed by setup and repeat work. Keep the one-off setup minutes separate from per-unit cycle time, then add the job rows to see the planned run length.
1 · job | setup minutes | planned units
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the setup-and-run time ticket: your job | setup minutes | planned units stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: Setup is counted once per row in this model. After: the setup-and-run time ticket shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the setup-and-run time ticket
Time-estimation arithmetic only, not a capacity promise, occupational-safety plan or production release. Use observed cycle data, include required breaks and checks, and have the production lead approve the schedule. It cannot account for every interruption on a real production line.
Paid layer: setup-and-run time ticket print and history
one-time step · the free reading above stays complete
Free tier
- one complete setup-and-run time ticket run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the setup-and-run time ticket with its row workings
- CSV of production minutes and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the setup-and-run time ticket, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Time-estimation arithmetic only, not a capacity promise, occupational-safety plan or production release. Use observed cycle data, include required breaks and checks, and have the production lead approve the schedule. It cannot account for every interruption on a real production line.
- Method: the equation is stated next to the result and uses only quantities entered by the reader.
- All sample records are invented examples. No standard, tariff, product rate, schedule or policy is fetched or represented as verified.
- For any threshold or rule, use the current value from the provider, handbook or qualified professional responsible for it.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this setup-and-run time ticket, an external AI text tool may help format non-sensitive notes if you already use one. No AI service or account is required: manual entry completes the same free core calculation. Do not paste private or sensitive data. Review every value against the source before using it.
Format my non-sensitive notes for a setup-and-run time ticket. Return plain rows only: job | setup minutes | planned units. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: job | setup minutes | planned units. No AI response is executed as code.