How a Scheduler Thinks About a Week vs a Day

A finite capacity scheduler thinks about a day and a week as two different jobs: the near term is an executable dispatch the floor can run to the hour, and the far term is a directional capacity forecast that is allowed to move. EDGEBIC by User Solutions produces both from one engine, but what you should do with each is different. Reading a plan well means knowing which part is a firm commitment and which part is a shape you are steering toward. Confuse the two and you will either over-trust the distant plan or over-manage the near one.

Two horizons, two purposes

The near horizon, the next shift and the next few days, is where the plan meets reality. Jobs are started, material is staged, operators are assigned. This part of the plan has to be precise to the hour, because people are executing it right now.

The far horizon, the weeks beyond, is where the plan is still a forecast. Nothing is committed, no material is pulled, no setup is staged. This part of the plan answers a different question: do I have enough capacity for the load I can see coming, and roughly when will things land?

Both come from the same finite capacity engine placing the same jobs against the same work centers. The difference is how much reality has already frozen. Near in, a lot has; far out, almost nothing has. That is why the two ends of the plan behave so differently and should be used for different decisions.

Why the near term is stable and the far term moves

The near term is stable by construction. Completed work is never moved by a reschedule, and in-progress work is preserved, so the days that are already underway cannot thrash. Whatever the shop has committed to stays committed. See why completed work is never moved on reschedule.

The far term moves precisely because it has none of that anchoring. A job three weeks out has no actuals, so it is free to reflow as new orders arrive, due dates change, and priorities shift. That is the plan working as intended: you want the distant future to absorb change so the near future does not have to. A stable near term and a fluid far term are not a contradiction. They are the same design serving two purposes, which is the heart of why a good schedule is boring.

Granularity: the week hides what the day reveals

A weekly view averages load across days, and that average can lie. A work center can look comfortable for the week and still be jammed on Tuesday and idle on Friday, because 40 hours of work spread evenly is fine but 40 hours all landing Tuesday is not.

The day-level plan is where the truth lives. Finite capacity places each operation on a specific shift with real hours, so the day view shows exactly where the load piles up. When the weekly picture says "you have room" and the floor feels overloaded, the day-level capacity for the tight days shows why. Read the week for whether you have enough total capacity, and read the day for whether it arrives when you need it. The capacity mechanics are covered in how a scheduler calculates work center capacity.

A worked example

A milling work center runs one shift, Monday to Friday, offering 8 hours a day, so 40 hours for the week. Five jobs need it this week, totaling 36 hours.

The weekly view is calm: 36 of 40 hours, 90 percent load, room to spare. A planner glancing at the week would promise a sixth job without hesitation.

The day-level plan tells a different story. Three of those jobs, 26 hours, are due early, so they land Monday and Tuesday and part of Wednesday. The mill is packed solid through Wednesday morning and lightly loaded Thursday and Friday. A sixth job that needs to run Monday has nowhere to go, even though the week has 4 spare hours, because those spare hours are on Friday.

Same capacity, two readings. The week said yes; the day said not until Thursday. If you had quoted off the weekly average, you would have missed. The day-level plan is what you dispatch to; the weekly view is what you plan capacity with.

Matching cadence to horizon

Because the two horizons do different jobs, you work them on different rhythms.

Reschedule the near term often, ideally at the start of each shift, so the executable window reflects the latest actuals and any overnight events. This keeps the days people are running fresh and accurate. The reschedule preserves everything already done, so frequent near-term updates are cheap and calm rather than disruptive.

Treat the weekly picture as a periodic capacity check. Run it to confirm total load, to catch an overload forming a week or two out while you still have time to react, and to see whether an incoming order will fit. You do not need to reoptimize the distant future every hour; you need enough lead time to act on what it shows.

The near term needs precision and freshness. The far term needs direction and enough runway to respond. Match your cadence to that and the plan stays both accurate where it must be and calm where it can be. See how the two horizons read on your own orders in EDGEBIC, and follow the full placement pipeline in the scheduling engine guide. For how the near-term dispatch order is set, see how a scheduler decides which job runs first.