How to Review Which Work Center a Group Step Resolved To in EDGEBIC

To review which work center a group step resolved to in EDGEBIC by User Solutions, run the schedule and open the Job View, where every surface shows the actual machine the engine picked. A group-bound step shows a pool badge only before it is scheduled. Once you run Generate Schedule, the badge is replaced everywhere by the name of the member the scheduler chose, so the Job View, the Gantt, the grids, and the reports all display the resolved machine. When a reschedule moves a not-yet-started group step to a different member, the step carries a replacement indicator naming the old and new machine, so a move is easy to spot.

This recipe covers one specific task: confirming the pick. To route a step to a pool in the first place, see how to bind a routing step to a machine pool. For the concept, read EDGEBIC work center groups explained. If the pick looks wrong, see a work center group scheduled the wrong machine.

Before You Start

• A routing with at least one group-bound step, and a schedule run since the binding, so the step has resolved to a member.
• An understanding that the pool badge is a before-scheduling state, and the machine name is the after-scheduling result.
• Knowledge of the group's selection strategy (earliest completion, primary first, or earliest start), which explains why a given member won.

Step by Step

1. Run Generate Schedule so any group-bound steps resolve to members.
2. Open the Schedule tab and go to the Job View for the job.
3. Locate the group-bound step. It now shows the actual machine name, not the pool badge.
4. Cross-check the Gantt: the operation's bar sits on the resolved member's row.
5. To confirm a move after a reschedule, look for a replacement indicator on the step, such as Replaced followed by the previous and current machine.
6. For the pick and its reasoning, open the scheduling diagnostics, which record each group explosion with the candidate members, their effective hours, the strategy, and the final choice.

What Changes When You Save

Nothing about reviewing changes the plan; this task is read-only. What matters is the state you are reading. Before scheduling, a group-bound step displays the pool badge because no machine is chosen. After scheduling, every surface shows the resolved member, while the step quietly keeps its group binding so a future reschedule can re-shop the pool. On a reschedule, not-yet-started group operations are re-evaluated against current capacity and may land on a different member, which surfaces as a replacement indicator. Started or completed operations keep the machine that actually ran them, so they never move and never show an indicator.

How to Check It Worked

Confirm the group-bound step in the Job View shows a machine name rather than a pool badge. If it still shows a badge, the step has not been scheduled since it was bound: run Generate Schedule. To verify a reschedule move, confirm the replacement indicator names the expected old and new machine. To confirm why a member won, check the group's strategy against the machines' load on the Resource Calendar: under earliest completion, an available slower machine legitimately beats a busy faster one.

Common Mistakes

• Reading the badge as a failure. A pool badge before scheduling is normal. The machine appears after the run.
• Expecting a started step to move. Operations with recorded work stay on their machine on reschedule, by design, so they never re-shop.
• Assuming the fastest machine always wins. Under earliest completion, the engine weighs load as well as speed, so a free slower machine can beat a queued fast one. That is the point of a capacity-aware pool.
• Missing the replacement indicator. A moved pool pick shows the same Replaced indicator as a manual alternate. Look for it on the step before assuming nothing changed.

Related Reading

• How to create work center groups for setting up the pool and its strategy.
• What is a work center group or machine pool for the plain definition.
• EDGEBIC and the EDGEBIC how-to hub for the full recipe set.

Reviewing the resolved member closes the loop on pooled routing: the routing keeps the pool binding, the schedule shows the machine the engine actually chose, and a replacement indicator tells you the moment a reschedule shops the pool differently, so you always know which machine is really running the work.