Reading the Resource Load View to Spot an Overload in EDGEBIC

The Resource Load view in EDGEBIC is a live bar chart that plots each work center's booked hours against its available capacity, so the single most important scheduling question, "is any machine promised more than it can deliver," becomes a bar you can read in a second. EDGEBIC by User Solutions recomputes the view on demand from the current schedule, and any bar that crosses the 100 percent line is an overloaded work center. This post shows you how to read it and what to do when a bar goes over.

The visual scheduling pillar guide covers the Gantt in depth; the Resource Load view is its capacity-side companion, answering "how full is each machine" rather than "where is each job."

Capacity Versus Load, as a Picture

Every work center in EDGEBIC has a real, finite capacity: the hours its shifts and calendars actually provide, multiplied by its number of machine instances. The Resource Load view draws that ceiling and then fills a bar up to the hours currently scheduled on the machine.

Reading it is intuitive:

Because the numbers come straight from the live schedule, the view is not a static snapshot typed at planning time. It recomputes when you open it, so a bar you fix by moving a job drops the next time you look. That is why planners reach for it after any manual change: it is the fastest confirmation that the plant, not just one bar, is in balance.

This is the visual heart of finite capacity scheduling. An infinite-capacity plan would happily stack every job on the same day and print a schedule that looks fine and cannot run. Finite capacity draws the ceiling and shows you when a machine is asked to exceed it.

Why a Bar Can Cross the Line

EDGEBIC's scheduling engine respects finite capacity, so it does not overbook a machine on its own. When you let the engine plan a job, work spreads across shifts and machine instances until it fits, and no bar climbs past 100 percent from that alone. So how do overloaded bars appear?

Two honest ways:

1. A genuinely tight resource. The engine placed every job legally, but the total demand on one machine simply fills its calendar to the brim across a stretch of weeks. That machine is your constraint, and the load bar names it.
2. A deliberate manual override. The Gantt uses an override-and-warn model. A planner can drag a bar onto an already-busy machine, EDGEBIC warns about the questionable move but does not block it, and the save records the decision. Saving a drag records dates; it does not re-run capacity math. So a hand edit can legitimately push a bar over the line.

Both are worth seeing, and neither is a defect. The load bar's job is to make the situation visible so you decide on purpose, whether the fix is a reschedule, a shift addition, or leaving a knowing overload in place because you have a plan for it.

From a Load Bar to the Jobs Behind It

A load bar tells you a machine is over the line; the next question is which jobs put it there. That is the job of the Work Center Utilization report, the deeper drill-down behind the quick bar chart. It rates every work center on a clear scale:

Its KPI strip counts your overloaded and underloaded machines and your plant-wide utilization in one line, and its per-work-center tab lets you select the CRITICAL machine and see the exact jobs stacked on it, with a daily heatmap of where the pressure lands. That is the difference between "this machine is hot" and "these three jobs, on these days, are the reason."

If you would rather see the same overload as a stack of bars in time, open the Gantt lane for that work center: spotting a bottleneck on the EDGEBIC Gantt walks through reading a jammed lane operation by operation.

Working an Overload Down

Once the Resource Load view has named the overloaded machine, you have the usual set of levers, and the view is how you confirm each one worked:

• Move work to an alternative. If the routing allows an alternate work center, drag the operation to that machine's lane on the Gantt. The load bar on the original machine drops; the alternate's rises. Trade capacity where you have it.
• Add capacity for the period. More shift hours or an extra machine instance raises the ceiling, so the same booked hours fill a shorter bar.
• Reprioritize. Push a lower-priority job's due date so its hours move to a lighter week, and the peak flattens.
• Accept it knowingly. Sometimes 102 percent is fine because you know an operator will absorb the last hour. The view lets you make that call with eyes open rather than by accident.

After any change, reopen the Resource Load view. Because it recomputes on demand, the bar you were fighting either dropped below the line or it did not, and you know immediately which.

A Reading Habit

Build the load bar into your routine:

1. After scheduling or rescheduling, open the Resource Load view before you trust the plan.
2. Scan for any bar over the line. No bar over the line means the plant is, on paper, feasible.
3. For each overloaded bar, drill into Work Center Utilization to find the jobs and days behind it.
4. Apply a lever, then re-check the bar to confirm the overload cleared.

The Gantt tells you where every job is. The Resource Load view tells you whether any machine was promised more than it can give, which is the question that decides whether a good-looking schedule can actually run.

See the full EDGEBIC platform, or bring your busiest work center to a demo and watch its load bar move as we reshuffle its queue with US.