Conveyors worked example
Part Spacing Speed Check at 99% expected spacing efficiency: a worked example
Push expected spacing efficiency up to 99% and the picture changes. This example computes every intermediate figure at that operating point. a line layout planner needs to test whether the planned part spacing forces the conveyor above its practical speed range
The inputs for this scenario
- Target finished-part output: 900 parts / hr (unchanged)
- Proposed leading-edge part spacing: 10 in (unchanged)
- Expected spacing efficiency: 99 % (raised for this scenario; the documented default is 92)
Working through the calculation
- Applying the documented formula (Required throughput rate = target output รท spacing efficiency) to the inputs above produces each figure below.
- At this operating point the engine returns 12.63 ft / min for belt speed required by spacing, the number this scenario is built around.
- At this operating point the engine returns 909 parts / hr for adjusted throughput target.
- At this operating point the engine returns 10 in for proposed product pitch.
- At this operating point the engine returns 99 % for spacing efficiency.
How this compares with the baseline
- Against the tool's baseline example, where expected spacing efficiency sits at 92% and the headline result is 13.59 ft / min, this scenario comes in 7.07% below the baseline at 12.63 ft / min.
- It computes the belt speed in feet per minute required to pass parts at a chosen leading-edge pitch fast enough to meet a target hourly output, after derating for spacing efficiency. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.
Results at a glance
- Belt speed required by spacing: 12.63 ft / min (headline result)
- Adjusted throughput target: 909 parts / hr
- Proposed product pitch: 10 in
- Spacing efficiency: 99 %
Run it with your numbers
- Every input above is editable in the live Part Spacing Speed Check calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.