Why an Operation Appears Twice in the EDGEBIC Planner View

On the EDGEBIC by User Solutions Planner board, every operation appears twice, and that is the design rather than a defect. It draws once on its job's lane in the upper block and once on its machine's lane in the lower block. There is one operation underneath, drawn in two places, and the two drawings can never disagree.

New users almost always read the second bar as a duplicate and go looking for the mistake. It is worth ten minutes to understand why the doubling exists, because it is the mechanism that makes the whole board work.

The Problem the Doubling Solves

Every other lane arrangement on the Schedule View puts an operation on exactly one lane. Lane by machine and the operation lives on its machine. Lane by job and it lives on its job. One lane, one bar, no ambiguity.

The Planner view carries both blocks at the same time, which is the entire reason to use it: you read the routing along the top and the plant's load underneath. But an operation belongs to a job and runs on a machine. If it drew only on the job lane, the machine block would be empty of it and you could not see the load you came to look at. If it drew only on the machine lane, the job block would have holes in exactly the routing you were trying to read.

So it draws in both. The doubling is not a rendering shortcut, it is the requirement.

They Are Not Copies

The important word is drawn, not duplicated. There is a single operation in the schedule. The board renders it twice.

That distinction has consequences you can see:

• Both bars carry the same caption, the same state color and the same window. If the machine bar is amber, the job bar is amber. If the machine bar runs Tuesday 08:00 to 16:00, so does the job bar.
• Move one and the other follows immediately. Not on the next refresh, not after a save. In the same instant.
• A pending change is counted once. Drag either bar and the pending-change count on the toolbar goes up by one, because one operation changed. If it counted twice the number would be a lie and every save would look twice as big as it was.
• Save Changes and Discard act once. Discard puts the operation back once. There is no half-reverted state where one drawing moved back and the other did not.

The practical version of all this: you never think about the second bar. You think about the operation.

Which Bar Do I Drag?

Either. The board decides what you meant from where the bar landed, not from which bar you picked up.

That table is the whole grip question answered. Pick up whichever bar is closer, and aim the drop carefully. The assignment gesture is walked through in how to assign an operation to a machine, and the two same-machine outcomes get their own treatment in dropping an operation back on its own machine.

The Job Bar Stays on Its Job Lane

Here is the behavior that surprises people the first time and reassures them ever after.

Drag an operation from JOB-2026-0101's job lane down onto a different machine and drop it there. When the drag completes, the job-lane bar is still on JOB-2026-0101's lane. It did not follow your cursor into the machine block and disappear from the job's routing.

This is correct and it is deliberate. The operation's job did not change, so its job lane must not change. What changed is the machine it runs on, and that is exactly what the machine block now shows: the bar has left its old machine's lane and drawn on the new one. The job block still reads the routing end to end, with the moved step in its proper place in the sequence.

Put simply: an assignment changes an operation's machine, never its job. The board reflects that in both blocks at once.

One Bar Per Operation, Not One Bar Per Job

Worth stating explicitly, because it is the sharpest difference from the Job lane mode.

In Job mode, a job draws as a single consolidated bar spanning its whole routing, and dragging it pins the job through its first operation. There are no machine lanes on that board at all.

In Planner mode, a job lane carries one bar per operation. Three routing steps, three bars, reading left to right. That is what lets you pick up a single milling step and put it on a different mill without disturbing the saw step before it or the paint step after it. If the job lane consolidated its operations you would be back to moving whole jobs, which is not the problem the Planner view exists to solve.

When an Operation Draws Only Once

There is one documented case where the doubling does not happen: an operation that belongs to no job.

Without a job number there is no job lane for it to mirror onto, so it draws once, in the machine block, and that is correct. Everything you would normally do with it on the Workcenter board still works. The only practical limit is that you cannot drag it out of the upper block, because it is not up there. Change its machine by dragging it between machine lanes in the lower block instead.

Two other kinds of bar also stay in the machine block only: end-item lead time tails and the optimizer's proposal ghosts. Neither is an editable operation, so neither needs a job-lane drawing.

Reading the Board With Confidence

The reassurance to carry away is a small one but it matters when you are moving real work under time pressure. There is no state in which the two bars disagree. The board cannot show you a machine bar on Tuesday and a job bar on Wednesday for the same step, cannot show one as overridden and the other as clean, and cannot leave one behind when the other moves.

That means you can trust whichever block you happen to be reading. If the job lane says the mill step runs Tuesday, the mill lane says so too, and both are saying what the operation actually holds. For the vocabulary behind the colors on those bars, see gantt colors and labels and reading the Gantt planned versus actual.

See the full EDGEBIC platform, read the Planner view overview, or bring your board to a demo and let US walk a real operation across both blocks with you.