Why a Gantt Bar Will Not Move in EDGEBIC

When a bar on the EDGEBIC scheduler Gantt refuses to move, that is information, not a malfunction. EDGEBIC by User Solutions deliberately holds a small number of things still: display-only bars, work that already happened, operations a planner pinned on purpose, and interactions a site has switched off. Knowing which of the five cases you are looking at turns a frustrating minute into a decision.

The chart's normal contract is generous: you can drag almost anything, EDGEBIC warns about questionable moves without blocking them, and nothing reaches the database until you press Save Changes. That is the override-and-warn model described in drag-and-drop rescheduling. This post is about the exceptions.

Case 1: It Is the Lead-Time Tail, Not an Operation

At the end of a job, on the last work center's lane, you may see a slate bar labeled Lead Time. It is not an operation. It is a display-only band spanning the gap between the last operation's finish and the job's final availability date, derived from the end product's lead time.

It cannot be dragged, resized, edited, or right-clicked into a menu, and it can never be saved, because it is not a schedule row at all. It also consumes no capacity, which is the point: promised-date information should never masquerade as schedulable work. To change it, change the product's lead time, not the chart. The full behavior is in the lead-time tail bar.

The tell is the color. The tail is styled unlike any operation state precisely so it never gets mistaken for one.

Case 2: Somebody Locked That Operation

Right-click any bar and one of the menu items is Lock Single Operation Segment in Current Position. It does exactly what it says: that segment is protected from being moved, while everything else on the board stays editable.

This is the correct tool for the operation you have already promised, staffed, or built a shift around. A planner two seats over who drags across a busy lane will not accidentally take it with them. The rest of the right-click menu, including the precise Move Operation to Date/Time entry and the clear-actuals family, is walked through in the Gantt right-click operation menu.

Practical habit: lock deliberately and sparingly. A board where half the bars are locked is a board nobody can re-plan, and the engine's reschedule is usually the better instrument for holding a job together.

Case 3: The Site Switched Dragging Off

The Configuration tab on Schedule View holds an appointment permissions card, and it is a plain set of checkboxes for what the chart allows:

A read-only supervisor station usually turns off Allow Drag and Drag Between Resources. That leaves the picture fully readable, states, captions, and all, while removing rearrangement.

One warning that matters more than it looks. Turning Allow Conflicts off does not make EDGEBIC capacity-check your drags. Feasibility of a manual move is on the planner, and the next scheduling run is what resolves it. If you want per-account control over who may do what, that belongs in roles and permissions, not in this display card.

Case 4: A Capacity-Request Job With Machine Changes Disabled

Capacity-request jobs are placeholders for load you want reserved without committing a real routing to a specific machine. When a site runs them with work center replacement disabled, dragging one of those bars onto a different lane behaves oddly on first encounter: the time shift is accepted, but the bar returns to its original row.

That is deliberate, not a glitch. The status message under the toolbar tells you what happened. If the job genuinely needs to live on another machine, it needs to stop being a capacity request first. Moving ordinary operations between lanes works normally and is covered in moving an operation to another machine.

Case 5: The Bar Moves, but the State Will Not

The last case is subtler: the drag works, the save works, and the bar stubbornly keeps one color. That is the ERP Actuals state, which applies when an operation's actual dates arrived from an external feed. It outranks every other state on the chart, including a work center replacement.

The chart is not the place to fix it. Correct the source data, which reaches EDGEBIC through the same import and export masks as your other external data, and the state resolves on the next load. Trying to out-drag an external feed is a losing game by design: the feed is the authority, and the color is telling you so.

The Special Case Everyone Meets First: Completed Work

Completion is not a lock in the permission sense, but it behaves like one where it counts. A completed operation, or any operation on a completed job, is painted with an opaque shade that overrides its state color, and no reschedule will ever re-plan it. Finished work is preserved exactly as it happened, which is the guarantee described in how a reschedule protects completed work.

If completion was recorded by mistake, reopen the job from the Job View tab. The shade lifts and the operation returns to normal handling on the next run. If it was not a mistake, leave it alone: rewriting history to make a chart tidy is how variance reporting becomes fiction.

A Two-Minute Diagnostic

When a bar will not move, work down this list in order:

1. Is it slate and labeled Lead Time? Then it is not work. Change the product's lead time instead.
2. Is it opaquely shaded? Then it is complete. Reopen the job only if completion was wrong.
3. Right-click it. If the lock item reads as engaged, unlock it deliberately.
4. Check the Configuration tab's appointment permissions. If Allow Drag is off, the whole board is read-only by policy.
5. Read the status message under the toolbar. Capacity-request handling and warning messages announce themselves there.

Five checks, and each one ends in an informed action rather than a workaround.

Locks Are a Feature of a Trusted Board

Every one of these behaviors exists because a schedule people trust is worth more than a schedule people can push around freely. Display-only bars never pretend to be work. Completed work never moves. External actuals win. A planner can hold one operation still without freezing the plant. To hold a slot for work that has not started yet, a planned start pin parks a future operation on a chosen date and machine without recording an actual it never had.

User Solutions has been building schedules manufacturers actually run since 1991, for shops of ten and for organizations including the US Navy, GE, BAE Systems, and Cummins. The through-line is the same as in any serious job shop scheduling practice: freedom to plan, discipline about the past.

See the full EDGEBIC platform, start with the visual scheduling pillar guide, or bring your current board to a demo and let US show you which of your bars should be movable and which should not.