How to Assign an Operation to a Machine in the EDGEBIC Planner View

To assign an operation to a machine in EDGEBIC by User Solutions, set the Schedule View to the Planner lane mode, then drag the operation out of its job lane and drop it on the machine lane you want it to run on. The machine change and the time you drop it at stage together as one edit. Nothing is written until you press Save Changes.

This is the gesture the Planner view exists for. For what the two blocks are and why the board is arranged this way, start with the Planner view explained.

Before You Start

• At least one job scheduled, so the board has operations on it.
• The Schedule View already switched to the Planner lane mode. Open Schedule, then Schedule View, then the Configuration sub-tab, set View by: to Planner on the General tab, and click Apply & Save.
• A decision about the Drag writes: selector on the toolbar. It governs what the time part of your drag records. A drag that only changes the machine records no dates at all, so this only matters if you are also moving the operation in time.
• Ideally, your interchangeable machines already grouped. A group-bound operation may only be assigned to an active member of its own group, as covered in EDGEBIC work center groups explained.

Step by Step

1. Go to the Scheduler sub-tab of the Schedule View. The board shows job lanes on top and the full machine block underneath.
2. Set Drag writes: on the toolbar if the drag will also move the operation in time. Rule of thumb: past work is Actual Start & End, running work is Actual Start, future work is Planned Start. Detail in how to change the drag mode.
3. Optionally click the operation's bar first. The machine block re-sorts to bring its legal alternatives to the top, which turns a hunt down a long lane list into a one-row drop. See how to float the machines that matter.
4. Find the operation on its job lane in the upper block.
5. Drag it down onto the machine lane you want it to run on, dropping it at the time slot you want.
6. Confirm the result. The bar turns to the Overridden state, stays on its job lane where you can still see it, and now also draws on the new machine's lane. The pending-change count on the toolbar rises by one.
7. Repeat for as many operations as the situation needs. All pending changes stage together.
8. Click Save Changes to commit the set, or Discard to put every pending bar back.
9. Press Re-Schedule to let the engine re-plan the jobs you touched around the new machine.

You can also drag a bar from one machine lane to another in the lower block. That works exactly as it does on the Workcenter board. The job block simply gives you a second, job-shaped grip on the same operation.

What Changes When You Save

The new machine is recorded as your intent, alongside the machine the engine had originally chosen, so EDGEBIC knows both and the substitution stays visible. The bar leaves the Overridden state and shows Resource Replaced.

A machine-only change writes no actual dates and no planned pin. You chose a machine, not progress, so the engine's planned window is left exactly as it was. If the drag also moved the operation in time, the time half is written according to your Drag writes: mode and the bar shows Applied, Actual Start Applied or Planned Applied accordingly.

Saving does not re-check capacity on the receiving machine. You may knowingly have overloaded it, which is the override-and-warn contract the whole Gantt runs on and is explained in drag-and-drop rescheduling.

On the next reschedule the engine honors your choice: the regenerated operation lands on the machine you picked, and the original machine is kept as lineage. For a group-bound step the choice is written as a pin on the routing, so the step keeps that machine on every later reschedule until you release it. Every save is recorded in the job's change history, reachable with View Audit Trail... from the bar's right-click menu.

How to Check It Worked

Look at the machine block. The operation should now draw on the new machine's lane and be gone from the old one, and the old machine's load in that window should have dropped by the operation's hours. The bar in both blocks should read Resource Replaced.

If you expected dates to move and they did not, that is correct for a machine-only change. Press Re-Schedule and let the engine re-plan the job around the new machine.

Common Mistakes

• Dropping on another job's lane. Operations belong to their job's routing and cannot move between jobs. The machine is left alone, any time shift is kept, and the status line says so. The full list is in why EDGEBIC refuses a drop.
• Aiming a group-bound step at a machine that is not a member of its group. This is refused up front, because a pin naming a non-member would quietly fail to stick on the next reschedule. Drop it on a member instead.
• Trying to reassign work that has already started. Started and completed work keeps its machine, because it is a record of what physically happened.
• Expecting the save to re-balance the plant. It records one decision. The arithmetic runs when you press Re-Schedule, which re-plans only the jobs you touched. See what a targeted reschedule is.
• Leaving the screen with pending changes. They live only in memory. Save or discard first.

Where to Go Next

Once you are assigning comfortably, learn the two same-machine outcomes in dropping an operation back on its own machine, and the staging rules in staged changes on the Planner board. If a drag does not seem to take, work through a Planner drag that did nothing. The full platform is at EDGEBIC, with more recipes in the EDGEBIC How-To Library.