Weighing, Dosing & Loss-in-Weight Feeding worked example

Feeder Capacity at 99% feeder mechanical uptime: a worked example

This scenario runs the feeder capacity calculation on the strong side: 99% feeder mechanical uptime, with every other input held at its documented default. Use it when feeder capacity in weighing, dosing and loss-in-weight feeding is being asked to take on more work and you need to know if there is room.

The inputs for this scenario

  • Doses delivered per feed cycle: 4 units / cycle (unchanged)
  • Feed cycles available per shift: 480 cycles (unchanged)
  • Feeder mechanical uptime: 99 % (raised for this scenario; the documented default is 90)
  • In-spec dose yield: 97 % (unchanged)

Working through the calculation

  • Applying the documented formula (Gross feeder capacity capacity = units per cycle × available cycles) to the inputs above produces each figure below.
  • At this operating point the engine returns 1,844 units for good output capacity, the number this scenario is built around.
  • At this operating point the engine returns 1,920 units for gross capacity.
  • At this operating point the engine returns 19.2 units for uptime loss.
  • At this operating point the engine returns 57.02 units for yield loss.

How this compares with the baseline

  • Against the tool's baseline example, where feeder mechanical 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 when sizing or auditing a loss-in-weight feeder against a per-shift demand, or when reconciling why delivered doses trail the nameplate cycle rate. 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 output capacity: 1,844 units (headline result)
  • Gross capacity: 1,920 units
  • Uptime loss: 19.2 units
  • Yield loss: 57.02 units

Run it with your numbers

  • Every input above is editable in the live Feeder Capacity calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.