Accumulating vs Non-Accumulating Conveyors —
When Transport Is Storage
Both move material from one place to another. Only one of them holds material when the next step stops — and picking the wrong one makes your line look either far more fragile or far more forgiving than it really is.
It is the most consequential modeling choice that looks like a detail. Transport is easy to treat as plumbing: material goes in one end and comes out the other, so long as the travel time is right. But a conveyor's behavior when the line stops matters more than its behavior when the line runs, because that is when it either protects the upstream machine or propagates the stoppage straight into it.
The difference in one sentence
A standard conveyor moves material. An accumulating conveyor moves material and holds it.
Why the wrong choice distorts the whole model
The error runs in both directions, and both are costly:
- A real accumulation lane modeled as a standard conveyor makes the line look more fragile than it is. Every downstream hiccup propagates instantly upstream, so the model reports stoppages the floor does not have — and you end up justifying a buffer that is physically already there.
- A plain transport belt modeled as accumulating hands the line storage it does not own. The model over-predicts throughput, absorbs stoppages that in reality propagate, and quietly makes the case for doing nothing.
The test is physical, not conceptual. Stand at the conveyor and ask: when the next machine stops, does product keep coming onto this and stack up, or does it stop dead? Roller beds, pallet conveyors and dedicated accumulation lanes accumulate. A simple transfer belt normally does not. Model what the equipment does.
What sets the capacity
Both node types are defined by the same three parameters, and it is the third that does the work:
Conveyor parameters
| Parameter | Controls | Why it matters |
|---|---|---|
| Length | distance travelled | with speed, sets transit time |
| Maximum speed | how fast material traverses | an upper limit on transport capacity |
| Height | units held per unit length | on an accumulating conveyor this is the storage — length × height is how much it can hold |
Which is the practical point: an accumulating conveyor is a buffer with a travel time attached. If you are about to size new storage, some of the capacity you are costing may already be sitting on the floor as conveyor. Work out length × height before you buy anything — see how big should a buffer be for the arithmetic on what that storage is worth.
The travel time is not free, though. Unlike a buffer, material on a conveyor still has to traverse the length before it becomes available downstream, so a long accumulating conveyor adds latency along with its storage. On a line where material ages or must be tracked, that delay is a real modeling consideration, not a rounding error.
Choosing, in practice
- Use a standard conveyor where travel time or physical layout matters but product does not queue — a straight transfer between two adjacent steps.
- Use an accumulating conveyor wherever transport also provides storage, and work-in-process builds along the line rather than in a discrete location.
- Use a buffer where the storage is a place rather than a path, and travel time is not meaningful.
- Start simple. Get the structure right with rough parameters, then refine — the same advice the docs give for every node type, and it holds here because a wrong node type is a structural error that no amount of parameter tuning corrects.
Related: How big should a buffer be? · Starved vs blocked · Accumulating conveyors in the docs
See accumulation in motion
The sandbox line includes accumulating transport. Watch what happens upstream when you stop the machine at the end.
Open the sandbox → How the method works