Boosting a Work Center's Capacity in a Quote Scenario in EDGEBIC

A capacity override in a quote scenario multiplies one work center's effective hours (1.5 means 150 percent, the equivalent of a second shift) so you can test how much extra capacity would pull the promised date in, without touching the live schedule. EDGEBIC by User Solutions stores the multiplier on the scenario, applies it during that scenario's finite capacity simulation, and reports the new end date and cost. The machine, the routing, and every real job stay exactly where they are.

This is the lever you reach for when the base simulation comes back late and the reason is capacity, not routing. You are not moving the work to a different machine or skipping a step. You are asking a single question: if this machine could do more per day, when would the job finish?

How the multiplier works

Each scenario carries a set of per-work-center multipliers. A value of 1.5 tells the simulation to treat that machine as having 150 percent of its normal capacity. A machine running one 8-hour shift becomes the equivalent of 12 hours a day. The multipliers are stored per machine, so you can boost one work center and leave the rest at normal, which is usually what you want.

The multiplier inflates effective hours only inside the scenario's run. It does not change the machine's real configuration and it does not persist to the live schedule.

Boost the constraint, not just any machine

The single most important habit with capacity overrides is to boost the right work center. A promised date is set by the machine the job waits on longest, so adding capacity anywhere else moves the date very little.

On the documented 200-unit Widget-A enquiry, the standard simulation ended August 14, six days past the customer's August 8 request. The mill was the constraint: it carried 101 of the roughly 151 work hours. A scenario that set the mill to 150 percent capacity, a second-shift equivalent, ended August 5, three days inside the customer's date, at a cost of $9,830 against the $9,230 baseline. The $600 premium bought nine days of pull-in.

Had the planner instead boosted the saw, which carried 20.5 hours and was never the bottleneck, the date would have barely moved, because the job was queuing on the mill, not the saw. Check your bottleneck before you pick a machine to boost. The work-center utilization view tells you where the load actually piles up.

The override respects your real calendar

A scenario is not a fantasy. It reads the same per-day and monthly capacity override tables the production scheduler uses, so maintenance downtime, holiday capacity reductions, and any daily overrides you have already configured still apply inside the scenario. The multiplier stacks on top of that real calendar. A 150 percent boost on a machine that is closed for a plant holiday still respects the holiday, and why a quote scenario respects maintenance downtime covers the rest of that real calendar. This is what separates a credible capacity scenario from wishful thinking: you are simulating "today's real shop, plus this one machine working harder," not a blank calendar.

Read the cost, not just the date

Extra capacity is rarely free, and the scenario shows you the trade. A second shift or overtime carries a premium, so the boosted scenario usually costs more than the baseline. On the Widget-A example the pull-in cost $600. A weekend-production scenario that hit the same customer date landed at $9,590, $240 cheaper than the second shift, but with zero slack instead of three days of margin. That is the kind of decision the numbers make possible: pay a little more for a machine boost and buy safety, or run the weekend for less and hit the date exactly. Neither answer is right in the abstract; the scenario just puts both on the table. For the full side-by-side, see comparing routing options for a quote.

Also read the utilization chart. A scenario that hits the date by running a machine at 150 percent for three straight weeks has no absorption left for a breakdown. A promise built on a machine pinned at full capacity is fragile, and the scenario is where you notice that before you commit.

Applying the scenario is a pricing move, not a shop change

When you apply a capacity boost scenario to the quote, its dates and its cost stamp onto the quote. That is all it does. It does not add the second shift, it does not change the machine, and it does not alter the live schedule. The promise you just priced is real only if you make the real-world change before you convert the quote to an order: schedule the actual overtime, apply the real capacity override on the machine, or line up the extra crew. Convert without doing that, and production faces the baseline capacity while the customer holds the boosted date. The scenario told the truth about what extra capacity would do; delivering on it is the next, separate step.

Where the capacity lever fits

Capacity overrides are one of a scenario's levers, alongside weekend production, priority, parallel processing across work centers, custom start dates, and per-step routing changes. They are the answer to "we are late because the machine is full," where a routing change is the answer to "we are late because the path is wrong." Both live in the scenario workbench described in the EDGEBIC quoting guide, and both rest on the same finite capacity scheduling engine that makes every simulated date one you can actually keep.

See EDGEBIC to test a capacity boost against your own bottleneck and your real load, and watch how far the honest date moves.