Inputs & results
Planning table
| Week | Demand | Minimum utilization | Capacity | Overtime capacity | JIT | Pull ahead | Overtime | Late load | Total load | Late due demand | Utilization |
|---|
Fixed-order sandbox: JIT → LBA pull-ahead → due-week overtime → minimum-fill → late catch-up.
Scenario view
Planner controls
Inputs & results
| Week | Demand | Minimum utilization | Capacity | Overtime capacity | JIT | Pull ahead | Overtime | Late load | Total load | Late due demand | Utilization |
|---|
Learning
Every KPI and chart segment traces back to the same deterministic sequence below. The goal is not “guessing” capacity—it is applying transparent rules so you can see cause and effect when demand, LBA, or minimums change.
For each week’s demand, the engine first loads as much as possible on regular capacity in that same week (the due week). That volume shows up as JIT. This mirrors “make what is due now” before borrowing earlier capacity.
What does not fit JIT is produced in earlier weeks using their regular capacity, stepping backward week by week. You cannot pull farther than your local build ahead setting allows. This is the core pull ahead bucket (purple in the chart).
After JIT and pull-ahead, remaining uncovered demand for that due week uses overtime capacity declared on that same week—not earlier weeks—before anything is marked late.
Demand that still cannot be placed becomes late due demand for that due week. It has not disappeared; the next phase tries to absorb it forward in time.
Separately, if a week’s total load would sit below its minimum utilization (capped by regular capacity), the model pulls future JIT into that earlier week—within the same LBA window—to lift the week toward its minimum. That movement also counts toward pull-ahead and the LBA intensity KPI (weeks early × units).
Late due units are pushed forward, consuming regular capacity first, then overtime, in chronological order in later weeks until the horizon ends. Whatever cannot be placed remains unresolved beyond the horizon—a signal that the scenario cannot close inside the simulated window.