OEE Lab / Tools / Buffer Size Calculator

Buffer Size Calculator: Protect the Constraint

Size the buffer or accumulation conveyor between two machines, so a short stop on one does not starve or block the constraint. See how fast it refills, which of your stops it absorbs, and the downtime it keeps off the constraint each shift. Updates as you type.

Two machines and the buffer between them

The defaults are an example can line, not a benchmark. Replace them with your own numbers.

The line
The constraint sets the line's output. Downstream: the buffer stops it starving. Upstream: the buffer stops it being blocked.
The speed the constraint really runs at.
Top speed of the machine that feeds the constraint. The overspeed refills the buffer.
The stops to absorb
Stops on the other machine, from your log or a tally sheet. Separate with spaces, commas or semicolons. 0,5 also works for 0.5.
The 90th percentile and the longest stop come from your list.
min
Used when there is no list, or when you size by hand.
How often the other machine stops.
min
Planned production time of one shift.
%
Turns protected run time into OEE points. Use 100% to see availability points only.
The buffer, optional
Pitch is the length one unit takes on the conveyor, gap included. Value is the cost of one unit of work in progress.
Leave 0 to use the size the tool works out. Enter your real buffer to see what it covers.
Defaults: a can line, filler fed by a depalletiser
Buffer needed
- units
Stop length to absorb × line rate
0%of listed stops absorbed
Refill time
-
Run time to next stop
-
Downtime kept off / shift
-
OEE points protected
-
Conveyor length
-
WIP value held
-

Which of your stops the buffer absorbs

Each bar is one stop length from your list. Green is the part the buffer covers. Red is the part that still reaches the constraint.

Percentiles use the nearest-rank method on your list: the 90th percentile is the stop that 90% of the stops are at or below.

The working

    This is a first sizing, not a simulation. The maths treats stops as evenly spaced and assumes the buffer is full (or, for a blocking buffer, empty) when each stop starts. On a real line, stops come at random, two can come close together, and the constraint stops too. Before you buy a conveyor, check the size with a simulation of your line or a trial with real stop data.

    A buffer protects the OEE of the constraint. It does not fix the stops on the other machine. They still happen just as often, and that machine's own OEE does not change.

    Get a second opinion on this result

    Send it to the OEE Lab team. A Fabrico OEE specialist reads your numbers and gets back to you by email. To keep the result, use Copy link or Print above.

    Sent. A Fabrico OEE specialist will read your numbers and get back to you by email.

    No newsletter, no spam. What you enter here, this result and its link go to the OEE Lab team. Privacy

    A buffer is only as good as the stop data behind it.

    A buffer sized from a guess at how long stops last protects the wrong stops. Fabrico records them. Stops come live from the PLC or IoT sensors, so every short stop is timed, and the operator gives the cause. Where a machine has no usable signal, AI cameras count the output. You see OEE per line and per shift, so you can size a buffer from real stop lengths and then check that the constraint stopped starving.

    See every short stop on your line: book a demo with a Fabrico consultant.

    Request a demo
    Our tools stay free either way.

    What a buffer between two machines does

    On a line, machines are linked. When one stops, the machine after it runs out of product and is starved, and the machine before it has nowhere to put product and is blocked. A buffer breaks that link for a while. It is a stock of units between the two machines: an accumulation conveyor, an accumulation table, a bi-flow table or a WIP rack.

    The buffer matters most next to the constraint, the machine that sets the line's output. A minute lost at the constraint is a minute of output lost for the whole line. A minute lost on a faster machine next to it can often be made up, if there is a buffer to bridge the stop and spare speed to refill it afterwards.

    This tool sizes that buffer. It answers four questions: how many units the buffer must hold, how long it takes to refill, which of your recorded stops it absorbs in full, and how many minutes a shift it keeps off the constraint. Short stops are the usual target, because they are frequent and short enough for a buffer to bridge. For more on them, Fabrico has a guide to micro-stops, and OEE Lab has a micro-stop counter to record them.

    The formulas

    Buffer units = stop length to absorb × line rate

    While the machine next to the constraint is stopped, the constraint keeps running and uses the buffer at the line rate. To ride through a stop of a given length, the buffer needs that many minutes of the constraint's rate. Round the result up to whole units.

    Refill time = buffer units ÷ (rated speed of the other machine - line rate)

    After the stop, the other machine must feed the constraint and refill the buffer at the same time. Only its overspeed, the speed above the line rate, goes into the buffer. If the other machine is not faster than the line rate, the buffer never refills.

    Run time to next stop = shift length ÷ stops per shift - average stop length

    The buffer must refill inside this time, or the next stop finds it part empty. This run time between stops is the mean time between stops of the other machine. If refill is too slow, the cover you really get is only what the overspeed can put back in that time:

    Cover in minutes = smaller of (buffer ÷ line rate) and (run time to next stop × overspeed ÷ line rate)

    • Downtime kept off the constraint per shift = stops per shift × the average of (each stop length, capped at the cover).
    • OEE points protected = minutes kept off ÷ shift length × performance × quality at the constraint.
    • Conveyor length = buffer units × pitch ÷ lanes.
    • WIP value held = buffer units × value per unit.

    The same maths works the other way round. If the upstream machine is the constraint, the buffer protects it from being blocked when the downstream machine stops. Then the buffer must run mostly empty, so it has room to fill, and the downstream machine needs the overspeed to empty it again.

    Worked example: the default numbers

    The defaults are an example, not a benchmark. A can filler is the constraint and runs at 120 cans a minute. A depalletiser feeds it and can run at 150 a minute. Over a shift, the depalletiser stopped 10 times for 0.5, 0.5, 1, 1, 1, 1.5, 2, 2.5, 3 and 6 minutes. On a normal shift it stops 12 times. The shift is 480 minutes.

    StepWorkingResult
    Stop length to absorb90th percentile: 9th of 10 sorted stops3 min
    Buffer needed3 × 120360 cans
    Overspeed150 - 12030 / min
    Refill time360 ÷ 3012 min
    Average stop19 ÷ 101.9 min
    Run time to next stop480 ÷ 12 - 1.938.1 min
    Stops absorbed in fullall up to 3 min9 of 10
    Minutes absorbed per stop(0.5+0.5+1+1+1+1.5+2+2.5+3+3) ÷ 101.6 min
    Kept off the filler12 × 1.619.2 min / shift
    OEE points19.2 ÷ 480 × 90%3.6 points
    Conveyor length360 × 70 mm ÷ 1 lane25.2 m
    Without a buffer the filler loses 12 × 1.9 = 22.8 minutes a shift to depalletiser stops. With 360 cans it loses 3.6: the part of the 6 minute stop that is longer than the cover.

    The buffer refills in 12 minutes, well inside the 38.1 minutes of run time before the next stop. So each stop finds it full. It absorbs every stop up to 3 minutes in full. The 6 minute stop is cut to 3 minutes at the filler.

    To absorb the 6 minute stop too, the buffer would need 6 × 120 = 720 cans, about 50.4 m of single-lane conveyor, and 24 minutes to refill. That doubles the conveyor for one stop in ten. Finding out why the depalletiser stopped for 6 minutes is likely to pay back sooner.

    Where to put buffers on a line

    • In front of the constraint, kept full. It protects the constraint from starving when a machine before it stops. This is the buffer the default example sizes.
    • After the constraint, kept with room. It protects the constraint from being blocked when a machine after it stops. Size it with the upstream option in the tool.
    • Both sides need spare speed. The machines around the constraint should run faster than it, so buffers refill and empty between stops. That is the idea behind the V-graph of line speeds.
    • Not everywhere. A buffer between two machines that are not the constraint mostly adds WIP and floor space. Put the money next to the constraint first. To find the constraint, see the guide to bottleneck analysis.
    • Mind the product. Some products cannot wait: short shelf life, product that gets damaged on an accumulation table, or a product change that means flushing every unit in the buffer. Then a smaller buffer and fewer stops is the better path.

    Common mistakes

    • Sizing for the average stop. Every stop longer than the average still reaches the constraint, and on most lines that is a good share of them. Size for a high percentile of your recorded stops.
    • No overspeed. If the feeding machine is not faster than the constraint, the buffer drains on the first stop and stays empty. A bigger buffer does not help.
    • Ignoring refill time. A big buffer behind a machine with little overspeed may never refill before the next stop. Check refill time against the run time between stops.
    • Sizing for breakdowns. A buffer for a 30 minute breakdown holds a lot of WIP for an event that is rare. Buffers are for short stops. Breakdowns need a fix.
    • Thinking the stops are gone. The constraint's OEE rises, but the feeding machine still stops as often. Keep counting its stops, for example with the hidden factory calculator.
    • Guessing the stop lengths. People remember long stops and forget short ones. Time them from the machine signal or a tally sheet before you size anything.

    Buffer size FAQ

    How do you calculate the buffer size between two machines?

    Buffer units = the stop length you want to absorb × the rate of the constraint. If the downstream constraint runs at 120 units a minute and you want to ride through a 3 minute stop upstream, the buffer must hold 3 × 120 = 360 units, and be full when the stop starts.

    How long does a buffer take to refill?

    Refill time = buffer units ÷ (speed of the feeding machine - rate of the constraint). A 360 unit buffer behind a filler at 120 a minute, fed by a machine that can run 150 a minute, refills at 30 a minute and takes 12 minutes. It must refill before the next stop, or the next stop finds it part empty.

    What if the upstream machine is not faster than the downstream one?

    Then the buffer never refills. Every stop drains it and nothing tops it up, so after the first stop it sits empty and protects nothing. The machine that feeds the constraint needs spare speed above the line rate before any buffer size can work.

    Which stop length should I size the buffer for?

    Not the average. Every stop longer than the size you pick still reaches the constraint, and with the average many stops are longer. A common choice is a high percentile of your recorded short stops, such as the 90th, so most short stops are absorbed in full. Long breakdowns are better handled by fixing them than by a buffer big enough to cover them.

    Does a buffer improve OEE?

    It protects the OEE of the constraint, because short stops on the machine next to it no longer stop it. It does not remove those stops. The feeding machine still stops just as often, and its own OEE does not change. Fixing the stops is still the bigger prize.

    How long should an accumulation conveyor be?

    Conveyor length = buffer units × pitch per unit ÷ lanes. 360 cans at a 70 mm pitch on one lane need 360 × 70 = 25,200 mm, about 25.2 m. A wider accumulation table with several lanes holds the same units on a shorter length.

    ← All OEE Lab tools · Open the OEE calculator