Glossary (EDGEBIC)

What Is a Bottleneck Utilization Metric? EDGEBIC Definition

User Solutions TeamUser Solutions Team
|
6 min read

A bottleneck utilization metric measures how heavily loaded the constraint work center is, expressed as its scheduled hours divided by its available capacity. Because the bottleneck sets the pace of the entire plant, its load is the single most important utilization number a planner watches: a constraint at or above 100 percent is oversold and gating delivery, while a plant-wide average can look calm and hide it. EDGEBIC shows the constraint's load as both a today figure and a seven-day average.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. The general idea of loading a machine to its available hours is covered in the capacity utilization KPI overview.

How the Bottleneck Utilization Metric Works

Ordinary capacity utilization divides scheduled hours by available hours for any machine. The bottleneck utilization metric applies the same arithmetic but only to the constraint, the one work center whose limited capacity caps the whole plant's throughput.

That focus changes what the number means. A non-bottleneck at 105 percent is a problem you can route around, because there is slack elsewhere. A bottleneck at 105 percent is a hard ceiling: the plant cannot physically finish work faster than the constraint processes it, so every hour scheduled beyond its capacity is a promise the shop cannot keep. Watching the constraint's load, rather than an averaged plant figure, points the planner at the resource where capacity decisions actually move delivery.

EDGEBIC knows which machine is the constraint because a planner flags it. Marking a work center as the bottleneck in the work center editor tells the engine to anchor scheduling around it and tells the dashboards to track its load specifically. The flag is a deliberate choice, so the metric always follows the machine you have named.

A Concrete Example

Take a Planner tab on Monday June 16 with a three-day horizon and three work centers, one of them the flagged constraint.

Available capacity per day:

Work centerMonTueWed
Mill-116h16h16h
Lathe-28h8h8h
Heat-1 (bottleneck)24h24h24h

Assigned hours from the latest scheduling run:

Work centerMonTueWed
Heat-124h26h20h

Computing the constraint's load per day: Monday 24 divided by 24 = 100 percent, Tuesday 26 divided by 24 = 108.3 percent (oversold, red cell), Wednesday 20 divided by 24 = 83.3 percent.

The bottleneck panel reports:

  • Today's load = 100 percent (Heat-1, Monday).
  • Seven-day average load = 97.2 percent, the average of the first cells (100, 108.3, 83.3).

A constraint averaging 97 percent with an oversold Tuesday has almost no room. The planner's options are to relieve the load, add capacity for Tuesday, or offload eligible work to an alternate before the red day arrives.

How EDGEBIC Computes and Shows It

The bottleneck's load surfaces in three places, all keyed off the same constraint flag:

  • The Planner tab bottleneck panel reads the flagged work center, pulls its heatmap cell for today to get today's load percent, and averages its first seven horizon cells for the seven-day figure. The panel's chip is Plan, since the numbers come from the scheduler's projection.
  • The Work Center Utilization report shows a bottleneck-status column on the per-machine grid and counts bottlenecks in its KPI strip, so the constraint's rating band (CRITICAL, HIGH, GOOD) sits next to every other machine's.
  • The Exec tab carries a bottleneck side tile that names the constraint work center.

One thing the panel does not yet report is buffer consumption: the buffer-percent field is a placeholder that reads zero until deeper Theory-of-Constraints buffer telemetry lands, so do not read a zero there as "100 percent buffer remaining". The load percentages, by contrast, are live projections of real scheduled hours against real capacity.

Read the bottleneck utilization metric with production bottleneck identification for how the constraint is found and managed, and with the EDGEBIC dashboards guide for how the Planner panel fits the wider cockpit. To see the constraint's load in the context of every machine, the EDGEBIC reports guide covers the Work Center Utilization pane in full.

A bottleneck utilization metric measures how heavily loaded the constraint work center is, since the bottleneck sets the pace of the whole plant. EDGEBIC computes it as the constraint machine's scheduled hours divided by its available capacity, shown both as today's load percentage and a seven-day average. When a bottleneck runs at or above 100 percent, it is oversold and gating delivery, which is the single most important utilization number in the plant.

Because the constraint determines maximum plant throughput. A non-bottleneck at 105 percent has slack elsewhere to absorb the overload, but a bottleneck at 105 percent means the plant physically cannot finish work as fast as it is being scheduled. Watching the constraint's load, rather than an averaged plant utilization, tells a planner whether the true limiting resource is oversold, healthy, or has room, which is where every capacity decision should start.

A work center is flagged as the constraint by setting its bottleneck flag in the work center editor. Once flagged, EDGEBIC anchors scheduling around it and surfaces it on the Planner tab's bottleneck panel, in the Work Center Utilization report's bottleneck status column, and as a side tile on the Exec tab. The flag is a deliberate planner decision, not an automatic guess, so the bottleneck utilization metric tracks the machine you have named as the constraint.

Expert Q&A: Deep Dive

Q: The Planner tab bottleneck panel shows today at 100 percent and a seven-day average of 97.2 percent. Should I act?

A: Yes, that constraint is effectively maxed. In the book's example, Heat-1 was the bottleneck, its heatmap cell for today read 100 percent, and the seven-day average of its first cells was 97.2 percent, one of which, Tuesday, was oversold at 108.3 percent and painted red. A constraint averaging 97 percent has almost no slack for setup variance or a breakdown, so the practical moves are relieving load, adding a shift, or offloading eligible work to an alternate before the oversold day arrives.

Q: Plant utilization looks fine at 68 percent, yet the bottleneck is CRITICAL. Which do I trust?

A: Trust the bottleneck. Plant utilization averages every machine, so a single overloaded constraint disappears into a calm mean. In the worked plant, eight work centers averaged 68.1 percent while Heat-1 ran 420 scheduled hours against 400 available, which is 105 percent and CRITICAL. The plant cannot ship faster than that constraint allows, so the bottleneck's 105 percent is the number that governs delivery, and the 68 percent average is the one that misleads.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together