Add Setup and Unit Cycle Time Across a Small Production Batch — Free
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.
The proof surface
Dispatch-capacity tools check how many jobs fit a service window. This ticket totals setup plus cycle time for each manufacturing batch, without claiming that jobs can run continuously or without changeovers.
Why the flat version breaks
Multiplying setup by every unit
Setup is counted once per row in this model.
Entering cycle time in minutes
The third setting is seconds per unit; labels are explicit to prevent a sixty-fold error.
Scheduling 100 percent of a shift
A theoretical cycle total leaves no room for real interruptions.
How to work the setup-and-run time ticket
Setup minutes occur once per job row. Cycle time is seconds per unit and applies to each planned piece.
Enter the number planned for this run. The result is setup minutes plus units × cycle seconds ÷ 60.
The summary pools the estimated minutes across the batch. Split jobs when they use different lines or non-overlapping shifts.
Breaks, maintenance, changeovers, inspection, staffing and material waits can extend the window. The result is a baseline for discussion, not a promised completion time.
What the setup-and-run time ticket replaces
| Question | Before | Visible working |
|---|---|---|
| Multiplying setup by every unit | Setup is counted once per row in this model. | Use a stable unit count |
| Entering cycle time in minutes | The third setting is seconds per unit; labels are explicit to prevent a sixty-fold error. | Add rows that share one production window |
| Scheduling 100 percent of a shift | A theoretical cycle total leaves no room for real interruptions. | Add real interruptions before scheduling |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
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.
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.
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.
Go deeper: the companion app files the same reading as a index card with a stamped header
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the setup-and-run time ticket reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The setup-and-run time ticket reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the add setup and unit cycle time across a small production batch companionBoundary
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.
What this is built on
- 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.
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.
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.
Walk three labelled examples
First reading. The invented sample Short run | 15 | 40 uses cycle seconds per unit = 45. The displayed total planned production time is 45.00000 production minutes. Follow the row note back to the measurements and conversion rather than treating the headline number as a recommendation. The sample is deliberately concrete so the reader can reproduce the arithmetic by hand.
Changed assumption. The alternate input Second job | 20 | 20 produces 35.00000 production minutes for the displayed summary. Compare it with the first reading to see which entered quantity moves the result. In a real plan, change only the assumption that has a traceable source; do not tune a value just to make a row pass.
Boundary case. With No setup batch | 0 | 40 and the same setting, the worked result is 30.00000 production minutes. This case shows how the arithmetic behaves at a useful edge, not that the underlying process has been measured or verified. Check the boundary statement beside the result and confirm any consequential input with the responsible person before acting.