The EDGEBIC Resource Load View Explained: Seeing Load Against Capacity

EDGEBIC by User Solutions provides a resource load view that draws each work center's booked hours against its real available hours, day by day, so finite capacity is something you see rather than something you calculate. The whole premise of finite capacity planning is that machines do not have infinite hours, and the load view is where that premise becomes visible: demand on one axis, genuine supply on the other, and the gap between them colored so overload and idle time both jump out.

This is the interactive planning half of a pair. The work center utilization report carries the same numbers as a filterable, exportable report; the load view is the board you scan while you plan. Both read the same load and the same capacity, so they always agree.

Load Against Real Supply

The number that makes the load view trustworthy is the available-hours figure it measures against. It is not a coarse assumption that a machine has twenty-four hours a day. It is the same capacity calculation the scheduler relies on, which reads the work center's shift calendar, its instance count, its efficiency, and any per-day capacity overrides in force. For the full mechanics, see how EDGEBIC calculates work center capacity.

The practical consequence is that supply follows reality. A day the plant is closed shows zero available hours, so any work sitting on it reads as an instant overload. A day with a daily capacity override for overtime shows the raised number, so the extra shift you planned is reflected in the headroom. You are never leveling against a fictional supply.

Reading Overload and Idle

The load view earns its place because two failure modes are equally expensive and equally invisible in a list of dates. Overload is the obvious one: a day where booked hours exceed available hours is a day something will not get done on time, and the view colors it so you cannot miss it. Idle is the quieter one: a resource sitting mostly empty while its neighbors are pinned is capacity you paid for and did not use.

Seeing both on one board changes the planning conversation from reactive to deliberate. Instead of discovering an overload when a job comes up short, you see the red day while it is still a plan and you have room to move. Instead of learning about idle capacity in a month-end review, you see the empty lane today and route work into it.

The Three Levers on an Overloaded Day

When the board shows a resource over its capacity, there are exactly three honest responses, and the view helps you pick.

Move the demand: reschedule a job so an operation shifts to a day with headroom. Add the supply: apply a daily capacity override if you are genuinely running overtime or bringing an extra instance online, which raises the available hours for that specific day. Or reroute: send an operation to an alternate work center or to another member of a machine pool that has room. The load view shows which lever a day needs; the reschedule and capacity tools apply it. What the view never does is pretend the overload away, because finite capacity means the hours have to come from somewhere real.

Leveling a Week, Not Just a Day

The higher-value use of the load view is leveling a profile rather than firefighting a day. Read a resource's whole week as a shape. A healthy shape fills the working days fairly evenly. A lumpy shape, some days pinned over capacity and others nearly empty, is a leveling opportunity even when no single day is a crisis.

Moving discretionary work from the pinned days into the slack days, within the limits of due dates and dependencies, finishes the same total work with less overtime and less late-delivery risk. That is load leveling, and doing it against a visible profile is far faster than doing it against a spreadsheet of dates.

Where It Fits

The load view sits between the schedule and the capacity reports in the daily loop. You run the scheduler, glance at the dashboard for the plant-wide health read, then open the load view on any resource the dashboard flagged to see its profile and decide the lever. When a decision needs documenting, the utilization report exports the evidence. For the whole system these surfaces observe, start with the complete EDGEBIC guide.

The Point of Load Beside Capacity

Finite capacity is only meaningful if you can see it. A schedule that respects machine limits but hides them behind a table of dates leaves a planner guessing about where the pressure is. Drawing booked hours next to real available hours, colored and day by day, turns the abstract promise of finite capacity into a working surface, one where overload is a red day you fix and idle time is an empty lane you fill.

Want to see your own machines loaded against their real calendars? Bring an export to a demo and we will show you where the pressure is.