How do you calculate starved and blocked time?

Divide the minutes a station was starved or blocked by total observed line minutes, then multiply by 100. With 48 lost minutes over a 480-minute shift, that's 48 ÷ 480 × 100 = 10% flow loss.

What is the difference between starved and blocked?

A station is starved when it has no incoming part to process and blocked when its output buffer is full so it can't release a finished part. Both stop the station from doing useful work even though it is up and running.

What is a good starved/blocked time percentage?

Many high-volume lines aim for under 5% combined starved plus blocked time. The 10% in our example is double a 5% target, leaving a 5-point gap that signals a real buffering or balance problem.

Does starved/blocked time count as downtime?

No. It is flow loss, not equipment downtime. The machine is available but idle for lack of work or outlet, which is why it shows up separately in OEE-style analyses as a performance or availability-flow issue.

How do I reduce starved and blocked time?

Re-balance cycle times across stations, resize buffers ahead of and behind the constraint, and stabilize upstream feed. Even a small accumulation conveyor before the bottleneck often removes several points of loss.

Starved/blocked time vs OEE — how do they relate?

Starved/blocked time is one contributor to the performance and availability portions of OEE. Lowering it directly raises OEE because more of the available run time is spent producing instead of waiting.

Conveyors calculator

Starved and Blocked Time Calculator

Starved and blocked time is the share of a conveyor line's running minutes lost because a station has no part to work on (starved) or nowhere to send a finished part (blocked). Line balancing engineers and production supervisors track it to find where buffers are mis-sized and where a single slow station is choking the whole line. Unlike pure downtime, this loss happens while equipment is healthy and powered — the asset is available but flow has stalled. Cutting starved/blocked time is often the cheapest way to lift line throughput because it requires buffer and pacing changes, not new equipment.

What this calculator does

Calculate the percentage of observed line time lost because equipment was starved for product or blocked downstream.
a line performance team needs to quantify flow losses between machines
It computes the percentage of observed line minutes lost to starving or blocking, plus how far that result sits from your acceptable flow-loss target.

Formula used

Starved/blocked time = starved or blocked minutes ÷ total observed minutes × 100
Gap to target = target flow-loss time − actual flow-loss time

Inputs explained

Starved or blocked minutes:
Total observed line minutes:
Maximum acceptable flow-loss time:

How to use the result

Use it after a timed line study or from PLC state logs when you suspect a bottleneck or buffer is robbing throughput even though machines aren't failing.
It treats all starved/blocked minutes equally and won't tell you which station caused the loss — pair it with per-station state logging to locate the root constraint.

Current U.S. benchmarks

The U.S. has 21,668 machinery manufacturing establishments employing about 1,086,146 workers (Census County Business Patterns, 2023).

Common questions

How do you calculate starved and blocked time? Divide the minutes a station was starved or blocked by total observed line minutes, then multiply by 100. With 48 lost minutes over a 480-minute shift, that's 48 ÷ 480 × 100 = 10% flow loss.
What is the difference between starved and blocked? A station is starved when it has no incoming part to process and blocked when its output buffer is full so it can't release a finished part. Both stop the station from doing useful work even though it is up and running.
What is a good starved/blocked time percentage? Many high-volume lines aim for under 5% combined starved plus blocked time. The 10% in our example is double a 5% target, leaving a 5-point gap that signals a real buffering or balance problem.
Does starved/blocked time count as downtime? No. It is flow loss, not equipment downtime. The machine is available but idle for lack of work or outlet, which is why it shows up separately in OEE-style analyses as a performance or availability-flow issue.
How do I reduce starved and blocked time? Re-balance cycle times across stations, resize buffers ahead of and behind the constraint, and stabilize upstream feed. Even a small accumulation conveyor before the bottleneck often removes several points of loss.

Last reviewed 2026-05-12.