How to Find Scheduling Conflicts in the Gantt in EDGEBIC

To find scheduling conflicts in EDGEBIC by User Solutions, open the Job View, refresh it, and read the conflict count in the status message at the bottom. When two operations compete for the same capacity at the same moment, the view reports a count and flags the affected bars. A clean scheduler run respects finite capacity, so a count above zero is a signal that something was moved by hand and never reconciled.

That last point is the whole idea. EDGEBIC schedules to finite capacity, which means the engine will not double-book a machine on its own. Conflicts almost always come from manual drags, not from the scheduler.

Before You Start

• A scheduling run has produced a plan. There is nothing to check on an empty Gantt.
• You can rerun the scheduler if you need to clear a conflict.
• You understand a conflict is a warning, not a hard block.

Step 1: Open and Refresh the Job View

Open the Job View tab. If the Gantt looks stale after a scheduling run or a set of drags, click Refresh so the conflict check runs against the current plan.

The check runs as the view loads, work center by work center, comparing what is booked against what each resource can actually do.

Step 2: Read the Status Message

Look at the status message at the bottom of the Job View. If conflicts exist, it shows a count. Zero is the number you want.

Conflicting bars are also flagged in the view, so once you know a conflict exists you can hunt for the pair visually.

Step 3: Narrow to Find the Pair

On a busy full-plant Gantt, two overlapping bars are easy to miss. Use the Jobs panel on the left to reduce clutter: untick all jobs, then tick them back a few at a time and watch the count. When the count rises as you add a job, that job is one side of the conflict. Look at its work center row and find the bar that overlaps it.

Step 4: Reconcile with a Rerun

The clean fix for a conflict is almost always to rerun the scheduler. Save any pending drags, then run Re-Schedule on the affected jobs so the engine reflows them within real capacity limits. The manual move placed the bar where you wanted it in time but never checked whether the machine was free. Rerunning hands that check back to the engine.

What Changes When You Save

Finding a conflict changes nothing on its own; it is a read. The change happens when you rerun the scheduler to reconcile it. A rerun reallocates the over-booked work within finite capacity, and the conflict count returns to zero if the plan is now feasible.

How to Check It Worked

1. After the rerun, refresh the Job View and confirm the status message shows zero conflicts.
2. Confirm the two bars that were overlapping no longer occupy the same slot on the same work center.
3. If a conflict persists, check whether one of the operations has a logged actual. Completed work is never moved by a reschedule, so an over-booked in-progress step may need a manual decision rather than a rerun.

Common Mistakes

Treating a conflict as a hard error. It is a warning. The plan still prints, but it is not feasible. Rerun to reconcile.

Dragging without rerunning. A hand drag places a bar in time without a capacity check. That is the number-one source of conflicts. Save, then Re-Schedule.

Forgetting dependent parallel shares a fixture. Synchronized multi-machine operations intentionally share the same window and can inflate a utilization number without being a true conflict. Confirm the shape of the operation before assuming the plan is broken.

Next

A conflict count above zero on a finite-capacity plan means a bar was moved by hand and never reconciled, so the routine fix is a rerun. To move bars safely in the first place, read how to move a job on the Gantt chart. To rerun cleanly, read how to run the scheduler. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.