What Is Throughput in Manufacturing? EDGEBIC Definition

Throughput is the rate at which a plant converts raw materials into finished goods, or into revenue: an assembly line finishing 20 chairs per shift has a throughput of 20. In Theory of Constraints the definition sharpens to revenue minus direct material cost per unit of constraint time, because the bottleneck sets the pace for the entire plant. EDGEBIC surfaces throughput as completed order quantity over a rolling window, and rolls it up into a units-per-week rate per plant.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. For the general KPI framing, see the throughput rate overview.

How Throughput Works

Throughput measures output, not effort or intention. A machine can be busy without adding throughput if it is building parts that no order needs, and a plant can be at high capacity while shipping little if a constraint is starving the rest of the line. What counts is finished goods that leave the plant.

Theory of Constraints goes further and says throughput should be measured at the constraint, in money net of material. The reasoning is simple: the bottleneck caps how fast the whole system can finish work, so an hour saved anywhere except the constraint does not raise throughput at all. That is why the constraint deserves protection and priority, and why speeding up a non-bottleneck machine feels productive but changes nothing that ships.

Throughput and capacity are easy to confuse. Capacity is the ceiling, what a resource could do. Throughput is the reality, what the plant actually delivers. The gap between them is where lost material, queue time, and misrouted work hide.

A Concrete Example

Take an Exec dashboard on a Monday morning. The orders table shows recent completions:

Throughput (7 days), with today at Jun 13, sums the quantities of jobs completed in the last week: J-101 (200), J-102 (150), and J-103 (300), so the tile reads 650 units. In-progress J-104 does not count; it has not finished.

Rolled up over a 90-day trend window, if those jobs ran primarily through the Machining department, the plant's throughput per week is 650 divided by (90 divided by 7), which is roughly 50.6 units per week. That units-per-week rate is what an executive compares across plants and across months.

How EDGEBIC Shows Throughput

Throughput is one of the four hero tiles on the Exec tab of the Dashboard Cockpit. EDGEBIC computes it as the sum of order quantities for jobs whose status is Completed and whose end time falls in the last seven days. A few product behaviors:

• The tile carries a Plan chip, because completion end time is the scheduler's projected end until kiosk actuals fully replace it. It becomes more truthful as the floor logs real completions.
• The multi-plant rollup uses the dominant-department rule. Each job is assigned to the single department whose work centers logged the most scheduled hours for it, then quantities and on-time counts aggregate per plant, and throughput-per-week is total quantity divided by the number of weeks in the window.
• A 30-day sparkline on the tile shows the daily quantity trend, so a slowing or accelerating plant is visible at a glance.

Because the constraint caps throughput, the same dashboards keep the bottleneck utilization metric close by: a machine stuck at CRITICAL load is the ceiling on how much the plant can finish. The EDGEBIC dashboards guide shows how the Exec, Planner, and Standup tabs assemble these numbers, and the reasoning behind flagging and scheduling around the constraint is covered in production bottleneck identification.

Read throughput with capacity utilization: utilization tells you how loaded the machines are, throughput tells you how much of that load turned into shipped goods.