How to Remove a Machine From a Work Center Group in EDGEBIC

To remove a machine from a work center group in EDGEBIC by User Solutions, open the work center groups tab, select the group, and either untick the member's active box or unpick it in the add and remove members dialog. The machine drops out of the candidate list that group-bound routing steps choose from, starting on the next scheduling run. Operations already started on it stay exactly where they are.

Pools change. A machine gets repurposed, a rebuild takes it out for a month, or somebody put a press in a milling group during setup and nobody noticed until the schedule looked strange. This page covers taking a member out cleanly and knowing what moves as a result.

Before You Start

• Know whether this is temporary or permanent. That decision picks the method.
• Check whether downtime is the better tool. For a known outage with dates, scheduled downtime is more precise than membership.
• Know what the machine is carrying. Started operations will not move, so look at the pool's load before you change anything.
• Check the primary flag. If the machine leaving is the group's designated primary, the group needs a new one.

If pools are new to you, how to create work center groups in EDGEBIC covers the full setup first.

Step 1: Open the Group

Open the Workcenter tab and go to the Workcenter Groups inner tab. Select the group in the list. The members grid shows every machine in the pool with its per-group settings.

The columns you care about here:

Step 2: Choose the Method

Temporary absence: untick Active. The row stays with its factor, setup override, and priority intact. The machine stops being a candidate. Tick the box again later and everything is as it was.

Permanent removal: unpick the member. Click Add / Remove Members, untick the machine in the checklist, and confirm. The row leaves the grid and its per-group settings go with it.

There is no prize for using the harder option. If there is any chance the machine returns to this pool, untick active.

Step 3: Apply the Change

Unticking active is a row edit, so use the Apply control on that row. Removing a member is done through the member picker and confirmed there.

Either way, nothing on the schedule moves yet. Master data edits do not reschedule anything on their own.

Step 4: Fix the Primary If You Just Removed It

If the machine leaving was flagged primary, set the flag on another member. Only one member per group can be primary, and ticking a second one unticks the first automatically.

A group running the primary-first strategy with no primary flagged falls back to the priority order, so check the priorities are sensible if you leave the flag unset. How to set a pool selection strategy in EDGEBIC covers which strategy reads which field.

Step 5: Reschedule and Look at the Pool

Run the scheduler. Group-bound steps that have not started are re-shopped across the remaining members, and the strategy decides where each one lands.

Two questions to answer while you are looking:

• Is the remaining capacity enough? A four-machine pool down to three carries the same work in fewer hours per day, and the honest answer may be that some jobs move later.
• Did the work spread the way you expected? If everything landed on one machine, check the factors and the strategy rather than assuming a fault.

How to Check It Worked

1. The members grid reflects the change. The row is unticked, or gone.
2. The pooled load shifted. Compare the group's load before and after: the removed machine should carry no new work.
3. Started operations stayed. Anything already under way on that machine is still there. That is correct behavior, not a leftover.
4. Check what a group step resolved to. How to review which work center a group step resolved to in EDGEBIC shows the machine each step actually landed on.

Common Mistakes

Removing the row when you meant to pause the machine. The factor and setup override are retyped from memory when it returns, and memory is optimistic about numbers like 1.25.

Expecting live work to move. Operations already started stay on their machine by design. If one genuinely has to move, that is a scheduling action rather than a membership edit.

Forgetting a pinned step. A planner's pin to a specific machine holds through reschedules. If the machine has to be vacated, the pin has to be cleared as well.

Leaving a pool with one member. A group of one still works, but it has stopped being a pool, and a routing step bound to it now has no flexibility at all. Either rebuild the membership or bind the step to the machine directly.

Removing the last active member. A group whose members are all inactive gives its bound steps nothing to choose from, and those steps fail loudly rather than silently, which is deliberate but still a schedule you have to fix.

Next Steps

The opposite job is one dialog away: how to add a machine to a pool in EDGEBIC covers bringing one in and setting its knobs correctly the first time. More task guides sit on the EDGEBIC how-to hub, and the EDGEBIC product page shows where machine pools fit the scheduling model.