Entry 0063·May 11, 2026·Reliability

The Ghost Capacity Hiding Inside Your Single-Shift Plant

When a plant misses rate, the visible failure mode is at the line, but the actual loss is rarely there; throughput hides in changeover sequencing, second-shift
Truth · modeled scenario

The plant that thought it had a capacity problem

A regional sliced-meat processor came in convinced they had a capacity problem. Four cook-and-package lines on a single shift, roughly $5-6M of revenue, growth conversations they could not see how to fit through the current footprint. The question on the table was whether to consolidate to two newer high-efficiency lines, add a shift, or start a CapEx case for new capacity outright.

We pulled a year of production data, built a digital twin, and ran thousands of scenario variations against it. The model came in 98% accurate to floor reality. The answer the model returned was not the answer anyone in the room expected.

The plant could triple in size, from $5-6M to roughly $18M annually, before it hit a real constraint. The real constraint, when it finally bound, was cook capacity, and that was not going to bind for a long time. Everything in between was Ghost Capacity, throughput that already existed, hidden inside choices nobody had modeled.

What the floor sees and what the model finds

When a plant misses rate, the visible failure mode is always at the line. Stops cluster. Crews stretch. Operators ask for more headcount. The plant manager submits a CapEx ask. It feels honest because the symptoms are real.

But the actual loss is rarely on the line itself. On the sliced-meat job, the lift came from three places, none of them new equipment.

Auto-loaders on the existing four lines eliminated significant manual loading labor. Same boxes, same cook, same finished product, just less head-touching at the front of the line.

Changeover sequencing recovered minutes nobody was tracking, because individual changeovers looked fine in the spreadsheet. Stacked back-to-back in the wrong order, three of them ran twelve minutes instead of the budgeted six. Same shift, same crew, an hour of lost run time inside a single Tuesday.

Two-shift operation on three of the four lines outperformed every aggressive consolidation scenario we modeled. The instinct is to shut lines down. The math says keep them, run them longer, build staffing depth.

Total hard-dollar savings: $800K to $1M depending on which scenario the client picked. CapEx required: $1.3M to $1.5M for the auto-loaders, with 12-plus month lead times that drove the financing structure as hard as the equipment selection itself. A new line never came up again.

The same pattern, two miles deeper into the supply chain

Around the same time, we walked the floor at a Tier-1 protein processor running marinated-meat lines for a major QSR program. The conversation there was the same shape from the other direction: capacity was tight, headcount was up, leadership was already modeling a 12-15% line-rate reduction tied to a pre-marinated process change coming in April.

The pack-off station planned at 11,000 pounds per hour. The combined upstream feed planned at roughly 8,300 pounds per hour, 4,400 from one line and 3,900 from the other. The pack-off crew was sized to a rate the front end could not hit. End-of-line was burning labor waiting on product that was not going to arrive.

End-of-line belt timing and stacking issues were absorbing more of the day than anyone counted. Trim line conveyor pacing was uncontrolled, sending bursts to the cutters instead of one item every 42 seconds. Five operators in deep boxing where role-and-time studies pointed at two. Total waste, including leakers and giveaway, sitting at 1.78%.

The OEE dashboard said the lines were running 82-83%. Some weeks the dashboard showed 112-117%, which is a data integrity problem (rework double-counted, break coverage spilling onto the wrong line), not a real number. The system nobody trusted was telling a story nobody could act on.

How to find the capacity you already bought

If your plant feels capacity-constrained, run three checks before you sign a CapEx request.

First, time the changeovers individually. Not the average. The actual stacked sequence on a representative shift, in the order it ran. If three transitions in a row blew through their budgets, you are looking at scheduled scrap, not a slow line.

Second, walk the upstream-to-downstream rate balance. Pick the station with the highest planned rate and trace backward. If the feeder lines cannot hit the consuming station's plan, you have staffed and equipped a constraint that does not bind. That labor and that capacity are both buyable back.

Third, check whether your shift structure is capping latent capacity. Single-shift plants almost always have Ghost Capacity in the second shift before they have it in another line. The hard question is staffing sustainability, not equipment.

There is one more pattern worth naming. In a third client conversation last week, the question came up about how to net savings against the quality cost they create. If a thinner film saves $1M but the leaker complaints from the field cost $500K, the savings number on the slide is not $1M, it is $500K. Ghost Capacity has a sibling: Ghost Savings. Both come from the same failure to model the system end to end.

The lens flip

The CapEx ask is almost never the right starting question. The right starting question is: where is the constraint actually binding, and what is it costing me, today, to be wrong about that.

If the answer comes back as cook, or as the sequence inside an existing shift, or as a feed-rate mismatch nobody put on a dashboard, you do not need to spend money. You need to model what you already own.

Continue reading in Reliability