Theory of Constraints in Aerospace Manufacturing

Apply the five focusing steps to aerospace machining: find the real constraint, cost an hour of constraint downtime, and set up drum-buffer-rope.

22 min read 6 sections Guide 6 of 16, The Process Architect's Blueprint Updated

1IDENTIFY2EXPLOIT3SUBORDINATE4ELEVATE5REPEAT

New to this topic?

Read these first to get the most out of this guide:

1
Constraint Rules the System
5
Focusing Steps
DBR
Drum-Buffer-Rope
$0
Cost of Exploitation (Steps 2-3)

This guide applies the Theory of Constraints to aerospace and other long-cycle, high-value production: few units a day, long routings, outside processing, and a constraint whose lost hour costs thousands. New to TOC? Start with the Theory of Constraints guide, which walks the five focusing steps through a simple factory example, then come back for the program-level math.

The ceiling, drawn Six operations with six different capacities all run at the same 22 units a day, and raising the finish mill past 30 buys nothing, because Op 50 NDT becomes the constraint there.

Capacities from Worked Example 1: Op 10 35, Op 20 40, Op 30 22, Op 40 50, Op 50 30, Op 60 45 units/day. System output is the smallest of them, 22. Capacity sitting above that rate: (35−22)+(40−22)+(50−22)+(30−22)+(45−22) = 13+18+28+8+23 = 90 units/day that exists, is paid for, and can never ship. Panel 2 plots output = min(Op 30 capacity, 30), because 30 is the next-lowest capacity in the same table, so elevating Op 30 pays one-for-one only from 22 to 30. The entire prize at the constraint is 8 units/day; at the article's $1,200 per unit, $9,600 a day. Everything past 30 is Step 5: the constraint has moved to NDT.

The Five Focusing Steps: In Depth, for Aerospace

Eli Goldratt’s Theory of Constraints rests on one insight: every production system has exactly one constraint that limits its output. Not two. Not a list. One. Everything else in the facility is either serving the constraint or generating waste. The Five Focusing Steps are the method for systematically managing that constraint.

WIP 5LEAD TIME
Little's lawWIP = throughput × lead timeThe Little's law guide

The reason this matters for the Process Architect is that it provides a decision framework: where should you invest your engineering time? The answer is always: at the constraint first. Every hour of improvement at the constraint translates directly to system throughput. Every hour of improvement at a non-constraint translates to exactly zero system throughput.

Step 1: IDENTIFY the Constraint

The constraint is the operation with the least capacity relative to demand. In theory, it is the resource with the longest queue. In practice, finding it is harder than it sounds because the apparent constraint and the real constraint are often different.

Three practical methods for identification:

Queue depth analysis: Walk the floor and measure WIP at every operation. The operation with the most WIP in front of it is likely the constraint. Be thorough: count units on machines, in queues, on hold, and in storage.

Utilization observation: The constraint is the resource that is always busy. Other machines have idle time; the constraint does not. If you can observe all resources simultaneously during a normal production day, the constraint reveals itself.

The sprint test: Temporarily add capacity at the suspected constraint (extra shift, overtime, parallel resource). If system throughput increases, you found the constraint. If throughput does not increase, the real constraint is elsewhere. Keep looking.

Step 2: EXPLOIT the Constraint

Get maximum output from the constraint without spending capital. This is the most under-executed step because organizations jump to Step 4 (buying equipment). Exploitation is free or near-free:

  • Never let it starve: Ensure material is always waiting. A 15-minute buffer of WIP in front of the constraint ensures it never stops for lack of input.
  • Run through breaks: Rotate operators so the constraint machine operates during lunch and breaks.
  • Reduce changeovers: Apply SMED to the constraint first. Every minute saved in setup is a minute of additional production capacity.
  • Eliminate rework at the constraint: Inspect before the constraint so defective parts never consume constraint time.
  • Pre-stage everything: Tooling, programs, fixtures, documentation. Everything the constraint needs should be ready before the current job finishes.
  • Prioritize maintenance: The constraint gets preventive maintenance priority over all other machines.
Step 3: SUBORDINATE Everything Else

This is the hardest step psychologically because it means non-constraint resources must deliberately operate below their maximum capacity. Non-constraints should run at the pace the constraint can absorb, no faster.

Why this creates friction: traditional management metrics reward high utilization at every machine. Running a non-constraint at 70% feels “wasteful.” But Kingman’s Equation proves that running non-constraints below capacity provides the capacity buffer that absorbs variability shocks. And producing more than the constraint can process just builds WIP, which Little’s Law proves increases lead time for every job in the system.

Subordination in practice means:

  • Upstream operations release work at the constraint’s consumption rate (the “Rope”)
  • Downstream operations are always ready to process constraint output immediately
  • Quality checks upstream of the constraint catch defects before they waste constraint time
  • Maintenance prioritizes the constraint over all other resources
  • When a non-constraint has idle time, it does not over-produce. It uses the time for setup reduction, maintenance, cross-training, or 5S
Step 4: ELEVATE the Constraint

Only after Steps 2 and 3 are fully executed: invest to increase the constraint’s capacity. This may mean buying a second machine, adding a shift, outsourcing overflow, or redesigning the process. This is the capital step: it costs money, so it must be justified by evidence that Steps 2 to 3 have been exhausted.

Step 5: REPEAT (Do Not Let Inertia Become the Constraint)

When you elevate the constraint, a new bottleneck emerges elsewhere. Go back to Step 1. The most common failure mode is continuing to optimize the old constraint after it has moved: pouring resources into a machine that is no longer the bottleneck while the new constraint goes unaddressed.

The Five Steps Are Sequential

Organizations that jump to Step 4 (buying equipment) before completing Steps 2 and 3 have permanently wasted their capital investment. If the old constraint had 30% untapped capacity hidden in changeover waste, break starvation, and rework, buying a second machine doubles capacity that was only 70% utilized. You now have two machines at 35% utilization, the same throughput you could have achieved with exploitation alone, and a capital expenditure that cannot be recovered.

The Financial Math of Constraint Management

Lean accountingHours stack by value stream; the waiting hours peel off the topThe Lean accounting guide
Worked Example 1: Find the Constraint 6-Operation Value Stream

Scenario: A machining value stream with 6 operations. Data collected over one week:

OperationCapacity (units/day)Avg. Queue Depth (units)Utilization
Op 10: Rough Mill35874%
Op 20: Heat Treat40565%
Op 30: Finish Mill224596%
Op 40: Deburr50352%
Op 50: NDT301287%
Op 60: Final Inspect45458%

Identification: Op 30 (Finish Mill) has the lowest capacity (22 units/day), the highest utilization (96%), and the deepest queue (45 units). This is the constraint.

System throughput: The entire 6-operation value stream can only produce 22 units/day, regardless of the fact that rough milling can do 35, heat treat can do 40, and deburr can do 50. The constraint determines system output.

Worked Example 2: The Financial Cost of Constraint Downtime Aerospace Program

Scenario: The finish mill (constraint) loses 3 hours due to a tooling issue. What is the impact?

ParameterValue
Constraint throughput rate22 units/day = 2.75 units/hour
Downtime3 hours
Units lost2.75 × 3 = 8.25 units
Finished goods value per unit$1,200
Revenue impact8.25 × $1,200 = $9,900

Critical insight: Those 8.25 units are gone forever. The constraint cannot “make them up”: it was already running at 96% utilization. There is no spare capacity to recover lost production. Those units will not ship this week. If the program is on a 4-week delivery cycle, this single 3-hour event has reduced the month’s output by 8.25 units, potentially 1.5% of monthly production from one tooling failure.

Compare to non-constraint downtime: If Op 40 (Deburr) loses 3 hours, zero units of system output are lost. Deburr runs at 52% utilization: it will catch up within 2 hours of resumed operation. Non-constraint downtime is not a system event. Constraint downtime is a system event.

This is why Goldratt said: “An hour lost at the constraint is an hour lost for the entire factory, forever.”

Drum-Buffer-Rope Scheduling

DBR is the scheduling method that translates TOC theory into a working production control system. It has three components:

BREAK
Rate disruptionThe learning curve is running down when a break bumps hours back up, then it recoversThe Rate disruption guide
Drum-Buffer-Rope Scheduling
Material Release
(ROPE)
→
Op 10 → Op 20
buffer →
DRUM
(Constraint)
→
Op 40 → Ship
The Rope releases material at the Drum’s pace. The Buffer protects the Drum from upstream disruption.
ElementWhat It IsHow to Set It
DrumThe constraint’s production schedule. This is the master schedule for the entire facility.Schedule the constraint to 100% of its exploited capacity. Every other schedule is derived from this one.
BufferA time buffer of WIP upstream of the constraint. Not inventory for its own sake: insurance against upstream disruptions.Start with buffer = 50% of the lead time from material release to constraint. Adjust based on buffer penetration data.
RopeA signal from the constraint to the first operation: “I have consumed one unit. Release one unit.”Material release rate = constraint consumption rate. No more. This is what prevents WIP explosion.
Worked Example 3: Setting Up DBR Production Control

Scenario: Constraint capacity = 22 units/day. Customer demand = 20 units/day. Lead time from material release to constraint = 6 working days.

Step 1: Set the Drum.

Schedule the constraint for 20 units/day (match demand, not max capacity: the remaining 2 units/day of capacity is your exploitation buffer for recovery from disruptions).

Step 2: Set the Buffer.

Initial buffer = 50% of upstream lead time = 50% × 6 days = 3 days. Buffer size in units = 3 days × 20 units/day = 60 units of WIP in the buffer zone.

Step 3: Set the Rope.

Release material at 20 units/day. When the constraint finishes 20 units, the rope signals the release of 20 more units at the first operation. The buffer maintains ~60 units between the first operation and the constraint.

Buffer management:

  • Green zone (buffer >67% full): Normal operation. No action needed.
  • Yellow zone (buffer 33 to 67% full): Monitor. Upstream may be falling behind. Check for disruptions.
  • Red zone (buffer <33% full): Expedite. The constraint is at risk of starving. Priority intervention at upstream operations.

Over time: If the buffer never enters the yellow zone, it is too large: reduce it. If it frequently enters the red zone, it is too small: increase it. The buffer finds its natural size through observation.

A Buffer in Front of the Constraint Is Not Waste

A buffer in front of the constraint is not waste. It is insurance against the most expensive thing that can happen in your facility: the constraint stopping. The cost of a 60-unit buffer (inventory carrying cost) is trivial compared to the cost of constraint starvation (8+ units of lost production per hour at the constraint). Size the buffer to protect the constraint, not to minimize inventory for its own sake.

Common Failure Modes in Constraint Management

UTILIZATION →WAIT
Kingman's equationWait ≈ variability × u ÷ (1 − u) × process timeThe Kingman's equation guide
Failure ModeWhat HappensWhy It HappensThe Fix
Elevating before exploitingOrganization buys a second machine while the first has 25% untapped capacity in changeover and break lossesCapital investment feels decisive; process improvement feels slowDemonstrate exploitation potential with data before authorizing capital
Improving non-constraintsKaizen events on machines that are not the bottleneck; zero impact on facility outputEach department optimizes locally; no system-level constraint awarenessEducate leadership on system-level throughput vs. local efficiency
Constraint moves undetectedAfter successful elevation, the constraint shifts to a new operation but all improvement focus remains on the old bottleneckStep 5 (repeat) is forgotten once the celebration endsMonthly constraint identification review; track queue depths as leading indicator
Subordination rejectedNon-constraint departments refuse to reduce output; managers protect their utilization metricsManagement incentives reward local efficiency, not system throughputChange the metrics. Reward throughput and delivery, not utilization. See Guide 14.

Improving a Non-Constraint Does Not Increase Output

Improving a non-constraint does not increase factory output. It creates the illusion of progress while the real constraint remains untouched. If your facility’s constraint can produce 22 units/day, no amount of improvement at any other operation will produce unit 23. The only path to unit 23 is through the constraint: either by exploiting it (Steps 2 to 3) or elevating it (Step 4).

The Bottom Line

The Theory of Constraints provides the decision framework that tells you where to focus. Little’s Law tells you what your lead time is. Kingman’s Equation tells you why queues form. TOC tells you where to act. Together, they form the complete physics of production flow. Next: CONWIP, the practical production control system that implements these physics by controlling what enters the system.

Interactive Demo

Add capacity anywhere in the line and watch what happens to throughput. Only one of the stations changes the answer.

The constraintOutput is set by the constraint; an hour lost there is lost for the systemThe constraint guide

Bottleneck Finder

Adjust cycle times for each station. The system can only produce as fast as its slowest station (the bottleneck). Try improving the bottleneck and watch throughput increase — then a new bottleneck emerges.

WIP:60
Cut
30s
→
WIP:30
Weld
45s
→
Paint
60s
Bottleneck
→
Assemble
35s
→
Pack
40s
System throughput: 60 units/hr
Station Cycle Times
30s
10s120s
45s
10s120s
60s
10s120s
35s
10s120s
40s
10s120s
System Performance
Paint
Bottleneck
60s
Constraint CT
60/hr
Throughput
210s
Total CT
Key insight: System throughput (60 units/hr) equals the bottleneck station's throughput. Improving any station other than Paint will NOT increase output.

Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check

TOC in Aerospace: FAQ

LISTEN · LEARN · LEADWEEK 1 → 13
First 90 daysA calendar of thirteen weeks fills in: listen, learn, then leadThe First 90 days guide

How do you find the constraint in an aerospace machining value stream?

Use three signals together: the operation with the deepest queue, the one with the highest utilization (always busy while others idle), and the sprint test: add capacity there for a week and see whether output rises. In the example on this page the finish mill has the lowest capacity (22 a day), 96% utilization and 45 units waiting, so it is the constraint.

What does an hour of constraint downtime cost?

Constraint rate times hours lost times the throughput per unit. A finish mill making 22 units a day (2.75 an hour) that loses 3 hours loses 8.25 units; at $1,200 a unit that is $9,900, and it cannot be made up later because the constraint has no spare capacity. Three hours lost at a non-constraint usually costs no output at all.

How big should the buffer in front of the constraint be?

A common starting point is half the lead time from material release to the constraint. With 6 days from release to the finish mill and a drum of 20 units a day, that is 3 days, or 60 units. Watch it in thirds: if it never drops into the yellow third, shrink it; if it often reaches the red third, grow it or fix the upstream step that drains it.

Why does improving a non-bottleneck not increase output?

Because the constraint determines system output. If a non-constraint can process 100 units a day but the constraint only 60, speeding the non-constraint to 120 does not ship one more unit. It piles more WIP in front of the constraint and, by Little's Law, lengthens lead time.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn

Take this to a room

The running order

For aerospace operations leadership. They should leave understanding that steps two and three cost nothing and that a constraint buffer is insurance rather than waste.

7 beats · 14 min
  1. 1

    The five steps are sequential

    Not a menu. Skipping to step four is a permanent waste of capital.

    • If the old constraint had 30 per cent capacity hidden in changeover waste, breaks and rework, buying a second machine doubles capacity that was only 70 per cent used.
    • You now have two machines at 35 per cent, and the same throughput you could have had for nothing.
    • Steps two and three cost zero dollars.

    Ask the room Have we ever bought capacity before exhausting exploitation?

  2. 2

    Find the real constraint, not the apparent one

    The apparent constraint is usually the busiest-looking resource. It is often not the actual limit.

    • Look for the pile, the starvation downstream, and the overtime that only happens in one place.
    • Compare each step's demonstrated capacity, not its utilisation report.
    • A resource can look busy because it is being fed badly.
  3. 3

    Exploit before you spend

    Get the maximum from the constraint with money you have already spent.

    • Run it through breaks by rotating operators.
    • Cut its changeovers with SMED. Stop feeding it defective parts.
    • Never let it process work that will be scrapped later: that is capacity destroyed.
  4. 4

    Subordinate means slower, deliberately

    Non-constraints run at the constraint's pace. That instruction is counterintuitive and it is the point.

    • Upstream that overproduces just builds WIP in front of the constraint.
    • Downstream must be ready to take the constraint's output immediately.
    • Local efficiency measures fight this, which is why they have to change.

    Ask the room Are any of our departments measured on their own utilisation?

  5. 5

    The buffer is insurance

    A buffer in front of the constraint is not waste. It protects against the most expensive event in the facility.

    • The carrying cost of a 60-unit buffer is trivial.
    • The cost of constraint starvation is eight or more units of lost production per hour.
    • Size it to protect the constraint, not to minimise inventory globally.
  6. 6

    Drum, buffer, rope

    The scheduling system that makes all of the above operational.

    • Drum: the constraint's schedule paces the plant.
    • Buffer: time-buffered WIP protecting it from upstream disruption.
    • Rope: material released only at the constraint's rate.
  7. 7

    Unit 23 only comes through the constraint

    The sentence to leave the room with.

    • If the constraint can produce 22 units a day, no improvement anywhere else produces unit 23.
    • Improving a non-constraint creates the illusion of progress.
    • The only paths to unit 23 are exploitation or elevation: in that order.

    Ask the room What are we improving now that will not produce unit 23?