All the machines receive a sachet together and discharge onto Conveyor Out together, once every machine cycle — but Conveyor In, Conveyor Out and Buffer all still run continuously (no stop-start on the transport belts themselves). Only the Case Packer indexes intermittently, pocket by pocket. See Option 1 (companion file) for the staggered single-file version.
Conveyor In, Conveyor Out and Buffer are all plain constant-speed belts here too — nothing about them stops or indexes. What makes this "synchronized batch" is timing: sachets are pre-spaced on Conveyor In exactly one machine-width apart, so a fresh row of 10 arrives in register under every pusher at the same instant, is pushed in together, and — one machine cycle later — is discharged onto Conveyor Out together. The belts themselves never pause; only the case packer does.
This is the one speed that must be exact: it's what makes a sachet placed one machine-width behind its target arrive there exactly one cycle later, in register with every other machine's sachet at the same instant. Run it faster or slower and the synchronized pickup breaks down.
It's tempting to assume Conveyor Out can run as slow as Conveyor In's per-machine share, since each machine's sachets start out in their own lane, 760 mm apart. In practice, with 10 machines all feeding the same belt, that separation doesn't hold up: sooner or later two sachets from different machines' streams get close enough to trigger the belt's own minimum-spacing rule, and once that happens they stay linked, moving together at the belt's speed rather than drifting back apart. Run the simulation for a minute and you'll see Conveyor Out settle into pitch-spaced packing almost everywhere — so it needs to carry the full combined throughput, the same as Option 1's conveyor. The genuine speed advantage of this layout belongs to Conveyor In, which only has to deliver one machine-width of travel per cycle, not the whole merged flow.
The Buffer is still worth running faster than Conveyor Out — once sachets are packed at minimum pitch, a higher belt speed pulls them apart again, opening a gap between rows before they reach the case packer, so the hand-off there isn't fighting the same congestion.
Same logic as the companion file: the case packer loads one sachet, indexes one pocket forward, and can't accept the next one until that's done. If its speed is set below the combined throughput, sachets queue at its entrance regardless of which upstream feeding strategy delivered them — and if the queue fills the whole downstream pipe, the machines pause together (they're synchronized either way).
A stoppage packs sachets at minimum pitch wherever they're sitting when it happens — in the buffer or
the accumulation conveyor — so what matters for hold-up is their combined length, not the buffer alone. The
total_mm_needed figure is exactly Option 1's buffer formula (same throughput, same pitch, same
target); what's new is that the accumulation conveyor's own length now covers part of it, so the buffer itself
can be shorter by that same amount. Change the accumulation length and the recommended buffer figure updates
with it — make accumulation longer and buffer's share shrinks; make it shorter (or zero) and buffer needs to
carry the full total again, same as if accumulation didn't exist.
Between Buffer and the case packer sits a short accumulation conveyor, running even faster than Buffer. Its job is twofold: it keeps opening the gap between rows right up until the last moment before the intermittent pockets, and — as above — its length counts directly toward the line's total stoppage hold-up. Sizing it is a trade-off: longer gives more resilience and more separation (and lets the buffer be shorter for the same target), but adds footprint and cost, so 3–5 m is a common practical range for this stage.
| Quantity | Value |
|---|---|
| Cycle time | |
| Required Conveyor In speed | |
| Minimum Conveyor Out speed | |
| Minimum case-packer speed to keep up | |
| Recommended buffer length (net of Accum.) |