How to See a Work Center Group's Pooled Load in EDGEBIC

A work center group's pooled load lives on the Resource Calendar in EDGEBIC by User Solutions, where each machine pool appears as a summary row you expand into its members, with per-day cells for capacity against booked load. The group row is a live sum of its member machines, so it reads the pool at a glance while the machines underneath hold the real hours. It is the view you open to answer whether a pool can absorb more work.

If you have not built the pool yet, start with how to add a machine to a pool. This page is the load view for an existing pool, one of many tasks mapped on the EDGEBIC how-to hub.

Before You Start

• The work center group exists and has at least one active member. A group with no members has nothing to sum.
• The member machines have shifts assigned. Capacity on the calendar comes from those shift calendars, and a machine with no shift reads as having no capacity.
• Jobs have been scheduled. Load is the hours the plan booked, so an unscheduled plant shows capacity and no load.

Step 1: Open the Resource Calendar

Open the Workcenter tab from the main navigation. The area has three inner tabs: Workcenters, Workcenter Groups, and Resource Calendar. Select Resource Calendar.

The screen lists your groups, each as a summary row with a group badge. This is a reading surface. Nothing you do here edits capacity or moves a job; it only shows what the schedule has already booked against what the calendars make available.

Step 2: Set the Date Window

Set the window with the From and To date pickers, or use the This Week shortcut for the current week. Choose the span that matches your question: one week to check whether a pool can take a rush order, the next month for a capacity conversation.

The cells refresh to the window, so a narrow window gives you day-by-day detail while a wider one gives you the shape of the load over time.

Step 3: Expand the Group Row

Click a group to expand it into its member machines. Now you see two levels: the group summary row, which is the live sum, and one row per member with its own per-day capacity and load cells.

Read the summary row first for the pool total, then drop to the members to see where the slack actually sits. A pool that looks comfortable at the group level can hide one member running hot and another idle, which is exactly the imbalance a machine pool is meant to smooth on the next run.

Step 4: Read Capacity Against Load

Each per-day cell pairs the machine's available capacity with the hours the plan booked on it that day. A member near or above its capacity every day has no room; a member with capacity and little load is where a new job or a re-shopped step can go.

Remember the pool has no capacity of its own. Every hour on a group row belongs to a member machine, so a machine shared between two groups shows the same hours under both group rows. Read group rows as views, not as additional capacity, or you will double-count a shared machine.

What Changes When You Open It

Nothing. The Resource Calendar is a read-only view of the current schedule and the shift calendars. It never edits a machine, a group, or a booking.

What changes is what you decide next: a per-day capacity override, a job moved on the Gantt, or a scheduler run that re-shops not-yet-started group steps across the pool. None of those happen from this view.

How to Check It Worked

After a change, such as adding a member or moving a job, re-open the Resource Calendar with the same window. The group summary row should reflect the new pooled total, and a re-shopped step should show its hours land on a different member. If you added a machine to the pool and then ran Drive Schedule, the not-yet-started steps that moved to the new member show up as load on its row where before there was none.

Common Mistakes

• Double-counting a shared machine. A machine in two groups shows its hours under both; the hours exist once.
• Expecting the group to add capacity. The pool is a routing choice, not a machine. Capacity is always on the members.
• Reading pooled slack as schedulability. If the group or all members are inactive, a bound step still fails despite comfortable load.
• Using too wide a window for a rush question. A comfortable month can hide two oversold days. Narrow the window for day-level truth.

Next Steps

To control which member the scheduler picks from the pool, set the rule in how to set a pool selection strategy. See how machine pools fit the wider engine on the EDGEBIC product page.