Staged Changes on the EDGEBIC Planner Board

Every change you make on the EDGEBIC by User Solutions Planner board is staged, not written. Drag as many operations as the situation needs, look at the result, then commit the whole set with Save Changes or walk all of it back with Discard. And when a change is machine-only, saving it writes no actual dates and no planned pin at all.

Those two properties together are what make the board safe to experiment on. You can try a rearrangement without committing to it, and you can move work between machines without inventing progress that never happened.

Staging: Nothing Happens Until You Say So

Grab an operation on the Planner board and drop it on a machine lane. The bar turns to the Overridden state, stays on its job lane where you can still see it, draws on the new machine's lane, and the pending-change count on the toolbar ticks up by one.

At that moment the database knows nothing. The change exists on your screen.

Keep going. Move a second operation to a different mill, pull a third two hours later, reassign a fourth. All of it stages together as one set. Then:

• Save Changes writes the whole set in one batch.
• Discard snaps every pending bar back to where it was, with no database write.

Two consequences to burn in. First, pending changes live only in memory. Leave the screen or close the application without saving and they are gone. Save or discard before you go. Second, Discard is all or nothing across the pending set. There is no per-bar undo inside it.

There is one useful exception to that second point, and it is specific to machine assignments: dragging an operation back onto the machine the engine originally chose un-stages that assignment on its own. If nothing else about the bar is pending, it stops being an override entirely and leaves the pending set while your other staged moves survive. Details in dropping an operation back on its own machine.

Because the board draws each operation twice, it is worth stating explicitly: a pending change is counted once, not twice. One operation changed, so the counter moves by one. More on the doubling in why an operation appears twice.

A Machine-Only Change Writes No Dates

This is the rule that separates the Planner board from a drawing tool.

When you move an operation from one machine to another without changing its time, saving records the machine and nothing else. No actual start. No actual end. No planned pin. The engine's planned window is left exactly as it was.

The reasoning is simple and worth saying out loud: you chose a machine, not progress. Deciding that Tuesday's mill work should happen on the second mill instead of the first is a statement about where, and it carries no claim about whether the work started, when it started, or whether it finished. Software that recorded actual dates for that decision would be putting words in your mouth, and those words would show up in every progress figure and variance report downstream.

If your drag also moved the operation in time, then the time half is recorded according to the Drag writes: mode on the toolbar: actual start and end, actual start only, or a planned start pin. The machine half still records no dates on its own. Set that selector before a diagonal drag, using the rule of thumb from how to change the drag mode: past work is Actual Start & End, running work is Actual Start, future work is Planned Start.

What Saving Actually Records

Saving Is Not Re-Planning

The honest limit to internalize: saving does not re-run the capacity math and does not re-balance the plant.

Move an operation onto a machine that is already full and EDGEBIC will let you, because you may have a reason it does not know about. That is the override-and-warn contract the whole Gantt runs on, described in drag-and-drop rescheduling. It is also why a saved machine change leaves the rest of the job's dates exactly where they were: the save recorded a decision, it did not re-plan anything.

The second step closes the loop. Press Re-Schedule and the engine re-plans just the jobs you touched, leaving the rest of the plant alone. The downstream steps of the job move to fit the new machine's reality, and completed work is preserved as it is. See what a targeted reschedule is and how to reschedule only the jobs that changed.

The habit is worth stating as a rule: manual override, then targeted re-plan. That mirrors standard practice in advanced planning systems, where an override is followed by a bounded recalculation rather than left dangling.

A Worked Sequence

JOB-2026-0101's milling operation is planned on CNC-Mill-1 for Tuesday 08:00 to 16:00. That mill is also carrying another job all Tuesday, and the Planner board shows both at once.

1. You click the milling bar. CNC-Mill-2 floats up under the job lanes and is visibly free on Tuesday.
2. You drag the operation from JOB-2026-0101's job lane down onto CNC-Mill-2, dropping it at Tuesday 08:00. The bar turns Overridden and stays on its job lane. One pending change.
3. You press Save Changes. The bar becomes Resource Replaced. No actual dates are written, because the time did not move. CNC-Mill-1's Tuesday load drops by eight hours and the other job now has it to itself.
4. You press Re-Schedule. The engine re-plans JOB-2026-0101 with the milling step on CNC-Mill-2, and pulls the downstream paint operation forward accordingly.

Four steps, and each one records exactly what it claims to record.

Why This Design Holds Up

The staging model and the no-dates rule solve the same underlying problem from two directions: a schedule is only worth reading if everything in it was put there on purpose.

Staging protects against the accidental commit. You can move five operations, look at the plant with those moves in place, and decide the whole arrangement was wrong without a trace of it reaching the database.

The no-dates rule protects against the accidental record. It ensures that when your reports say an operation started at a particular hour, somebody meant that, rather than it being a side effect of a machine decision made three weeks earlier.

Between them they let a planner use the board the way it should be used, which is fast and often, without the schedule slowly filling up with statements nobody made.

See the full EDGEBIC platform, read staging Gantt changes with save and discard, or bring last week's worst rearrangement to a demo and let US stage it, look at it, and discard it in front of you.