Reassigning an Operator With a Replacement Drag in EDGEBIC

On the EDGEBIC by User Solutions Schedule View in Operator mode, dragging an operation bar from one person's lane to another's reassigns the operation to that person, checked against their qualification. It is the people-mirror of the familiar machine replacement drag: instead of moving work between machines, you move it between operators. The drop writes an operator pin, and dropping on the Unassigned lane clears the pin so the scheduler restaffs the step. This gesture is part of how planners keep a staffed plan honest within the broader shop floor execution model.

Sometimes the schedule staffs a step with a qualified person, but a supervisor needs a specific individual on it, whether for a customer sign-off, a training pairing, or a judgment call about who runs a delicate job. The replacement drag makes that reassignment a direct, visual action, with one guardrail and one deliberate omission.

Switching to Operator Lanes

The Schedule View Gantt can lay out its lanes per operator instead of per machine. In the view's display configuration, set View by to Operator. Every operator with planned work in the window becomes a lane, plus an Unassigned lane collecting operations that have no crew pin. Now each bar sits in the lane of the person currently planned to run it, and moving a bar between lanes becomes the reassignment gesture.

Skill-required bars carry a person glyph, and the hover tooltip shows the required skill and the crew line, such as the operators and hours planned for that operation. This is the same crew data the Dispatch tab prints.

The Drag, Step by Step

1. Drag an operation bar from one operator's lane toward another's.
2. The drop is validated against qualification: the target person must be certified for the step's required skill. If they are not, the bar snaps back with the reason, for example that the person is not qualified for the skill. Dropping on Unassigned instead clears the pin.
3. Apply the change. The drag writes an operator pin through the same dual-source path used everywhere: it updates both the global routing and the job's preserved routing snapshot in one save. It also moves the current plan's assignment rows to the target person immediately, so the Gantt and dispatch reflect the new crew at once.

Because the pin is written to the preserved snapshot too, a later preserved-routing reschedule keeps the assignment rather than silently reverting it. For the pin's full semantics, see how the operator pin ties a named person to a job.

What It Checks: Qualification Only

The one guardrail is qualification. You cannot drop an operation onto someone who is not certified for its skill; that drop always snaps back. This prevents the most damaging mistake, assigning work to a person who literally cannot do it.

What It Does Not Check: Hours

The deliberate omission is hours. The drag does not verify that the target person has free capacity. You can knowingly drop a step onto someone who is already fully booked, and the drop is accepted and the pin written. This is intentional, and it matches the machine replacement drag exactly: the model is override-and-warn, not validate-and-reject. The human on the floor is trusted to make a deliberate call, and the system does not second-guess it in the moment.

The honesty comes at the next run. When you reschedule, the engine books operator hours truthfully against the ledger, and if the person you pinned cannot actually cover the step, it slides to a window where they can. So an overload forced by a drag is a temporary display state, not a durable free lunch: it will resolve into a real, staffable plan on the next scheduling run, which is exactly the finite capacity discipline you want.

A Worked Example

Two welders, Joe and Mia, both certified in TIG-Weld and both with lanes on the Operator-view Gantt. Sam is on the floor but not TIG-certified.

• A supervisor drags JOB-2026-0127's weld bar from Joe's lane to Mia's and applies. Mia is qualified, so the drop is accepted, the pin is written to Mia, and the assignment rows move to her lane immediately.
• The supervisor then tries to drag the same bar onto Sam's lane. Sam is not TIG-certified, so the bar snaps back with the reason. The reassignment is refused because Sam cannot do the work.
• Later, the supervisor drags a second weld bar onto Mia's lane even though Mia is already near-full that day. The drop is accepted (qualification passes), but the next reschedule finds Mia short of hours and slides the second step to her next available window.

Every outcome traces to the one rule (qualification is checked) and the one omission (hours are not), resolving to a truthful plan on the next run.

Reassign Versus Restaff

The drag pins a specific person. If instead you want the scheduler to pick the best-qualified person automatically, drop the bar on the Unassigned lane, which clears the pin. From then on the next run load-balances the step across everyone qualified. So the same gesture covers both intents: drag to a person to fix who runs it, drag to Unassigned to hand the choice back to the scheduler. For how the scheduler makes that choice, see how operator skills gate work center assignment.

The Bottom Line

The operator replacement drag reassigns an operation by moving its bar between per-operator lanes on the Schedule View, checking qualification and writing a durable pin to both routing sources. It deliberately does not check hours: it is an override-and-warn gesture, trusting the supervisor's call in the moment and letting the next scheduling run book hours honestly and slide the step if needed. Dropping on Unassigned hands the choice back to the scheduler. It is a direct, visual way to keep a staffed plan matched to reality. Explore the labor model in the shop floor execution guide, and see the platform at EDGEBIC.