How Capacity Visibility Prevents Missed Ship Dates

You cannot fix an overload you discover on ship day. By the time a job that was supposed to leave the building is not ready, every option to save it is already gone. EDGEBIC by User Solutions prevents the miss by making capacity visible weeks ahead: the overload that will make a job late shows up as a red week on the capacity view the moment it forms, while there is still room to move work, add a shift, or requote.

This post explains why a late job is almost always visible long before it ships late, shows the arithmetic of catching it early, and is honest about the misses visibility cannot prevent. For the visibility mechanism itself, see how EDGEBIC improves capacity visibility, its sibling. This post sits under the EDGEBIC results guide and follows the visibility all the way to the ship date it saves.

A Late Job Is an Old Overload

Trace a missed ship date back and you almost never find a surprise. You find an overload that existed in the plan for weeks before anyone reacted to it. Two jobs got promised into the same hours on the same machine, or a fuller queue than the week could hold, and the collision was baked in the day the work was booked. The job did not become late on ship day; it was going to be late from the moment the overload formed. Ship day is just when the shop finally noticed.

That is the crucial reframe. The problem is not that the miss is unpredictable. The problem is that nothing is watching capacity between the day the overload forms and the day the job is due. In a shop planning by spreadsheet or by an infinite-capacity list of wishes, capacity is invisible until the floor hits the wall, so a knowable overload gets discovered at the one moment nothing can be done about it.

The Mechanism: See the Red Week When It Forms

A finite capacity schedule makes capacity a live, visible number. Every operation is placed into real hours on a specific work center, so the moment demand on a machine exceeds its available hours in a week, that week shows as overloaded. The planner sees a red week weeks before the affected job is due, not on the day it ships. See how to read the capacity heatmap and reading a red day on the capacity view.

The view has to be granular to work. An average utilization number hides exactly the thing that causes the miss. A plant can run at a comfortable 80 percent for the quarter and still have one work center loaded to 140 percent in week three, and that single overloaded week is where the late ship comes from. A day-by-day, work-center-by-work-center view shows that peak directly instead of smoothing it into a reassuring average. The miss does not live in the average; it lives in the peak the average hides.

Pair the capacity view with the reports that answer whether you are on track, and the warning becomes actionable. See the reports that answer are we on time and how to run the late jobs report. The late-jobs report is the point: it lists the jobs the plan already knows will miss, weeks before they do, so the list is a to-do rather than a post-mortem.

The Arithmetic of Early Warning

The value of visibility is measured in the options it keeps alive. Consider a job due in three weeks whose path runs through a work center that is overloaded in week two.

Discovered on ship day, the option set is empty: the hours are spent, the job is late, and all you can do is apologize and expedite the recovery, which costs freight and overtime and still ships late. Discovered when the red week forms, the option set is rich: move the job to an alternate work center, split the lot so part ships on time, authorize a planned Saturday, or requote the customer honestly with a date you can hit. Some of those options cost money, but every one of them beats a missed ship date, and you get to choose the cheapest one that works because you have three weeks to choose.

The heritage record shows the aggregate effect of running the shop on visible capacity. In the documented User Solutions track record, GE Railcar took on-time shipping from 30 percent to over 90 percent across its repair network. A shop at 30 percent on-time is a shop discovering its misses on ship day; a shop at over 90 percent is a shop seeing the overloads early enough to act. The mechanism connecting the two is the capacity view that turns a knowable overload into a warning with runway.

You can size your own prize by counting. For two weeks, log every late ship and trace each back to the week its overload formed. Most will have been visible, in principle, well before the due date. The count of those (the misses that were knowable and not caught) is the number a capacity view addresses directly, because those are exactly the ones early warning converts into a decision.

What the Software Cannot Do Alone

Three honest limits keep this from being a promise of a perfect record.

Visibility is not action. A red week you see and ignore ships just as late as a red week you never saw. The view puts the decision in front of the planner early; the planner still has to make it. A shop that watches overloads form and does nothing about them gets the same result as a shop that was blind, minus the excuse. The value is realized only when the warning drives a response.

Some overloads have no cheap fix. Seeing a red week three weeks out is worth a great deal, but if that week is genuinely oversold and there is no alternate work center, no available overtime, and no room to requote, then the honest early answer is still a hard one: the job slips, and you tell the customer early instead of late. Visibility makes the bad news timely and gives you the best available response, but it cannot invent capacity that does not exist.

The view is only as true as the data. The capacity picture depends on real routings, setup times, and machine calendars. If a work center's available hours are wrong, or a holiday is missing from its calendar, the view shows a green week that is actually red, and the miss surfaces late again. Keeping the master data honest is the price of trusting the warning. See why a holiday did not reduce capacity for a common data trap.

A missed ship date is almost always a warning that arrived too late to matter, and the fix is not to work harder on ship day but to move the discovery weeks earlier. Capacity visibility does exactly that: it shows the collision in the plan while you can still change the outcome. To see the underlying mechanism, read how EDGEBIC improves capacity visibility; to see the full set of results, start from the EDGEBIC results guide; and to see EDGEBIC itself, visit the product page.