Packaging Automation & End-of-Line Systems worked example
Labeler Throughput at 99% expected labeler uptime: a worked example
This scenario runs the labeler throughput calculation on the strong side: 99% expected labeler uptime, with every other input held at its documented default. Use it when a labeler is asked to keep up with a faster filling or packing line and you need to know whether it can hold the rate.
The inputs for this scenario
- Rated label application rate: 4 units / min (unchanged)
- Available labeling run time: 480 min (unchanged)
- Expected labeler uptime: 99 % (raised for this scenario; the documented default is 90)
- First-pass label placement quality: 97 % (unchanged)
Working through the calculation
- Applying the documented formula (Gross labeled output = rated label application rate × available labeling run time) to the inputs above produces each figure below.
- At this operating point the engine returns 1,844 units for good labeled output, the number this scenario is built around.
- At this operating point the engine returns 1,920 units for gross labeled output.
- At this operating point the engine returns 19.2 units for labeler downtime loss.
- At this operating point the engine returns 57.02 units for label reject loss.
How this compares with the baseline
- Against the tool's baseline example, where expected labeler uptime sits at 90% and the headline result is 1,676 units, this scenario comes in 10% above the baseline at 1,844 units.
- Use it to set shift targets, size a labeler against demand, or diagnose whether lost output is from downtime or from label rejects. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Good labeled output: 1,844 units (headline result)
- Gross labeled output: 1,920 units
- Labeler downtime loss: 19.2 units
- Label reject loss: 57.02 units
Run it with your numbers
- Every input above is editable in the live Labeler Throughput calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.