How to Move an Operation to an Exact Time in EDGEBIC

To move an operation to an exact time in EDGEBIC, right-click its bar on the Schedule View Gantt, choose Move Operation to Date/Time, type the start and the end, tick Move Schedule to new Date/Time, and click OK. The move stages like any other Gantt edit in EDGEBIC by User Solutions, so nothing reaches the database until you press Save Changes.

Dragging is quicker for rough repositioning. Typing is correct when the minute matters. For the drag route see how to move a job on the Gantt chart; the full task library is at the EDGEBIC how-to hub.

Before You Start

• The job is scheduled, so the Gantt has a real bar to move. The engine has to have produced the operation first.
• You know what the move should represent. The toolbar's Drag writes: selector is the control that decides what a move on this screen records: actual start and end, actual start only, or a durable planned-start pin. Set it before you move anything, and see how to change the drag mode on the Gantt.
• You have the timestamps you want. The point of this dialog is that you already know them.
• You accept that a manual move is not capacity-checked. That is deliberate, and the follow-up is a reschedule.

The Steps

1. Open the Schedule View tab and find the operation. If the bar is hard to hit, widen the columns first with the timescale zoom; a bar that is three pixels wide is a bar you will mis-click.
2. Set the Drag writes: selector on the toolbar to match your intent. Past work belongs on Actual Start & End, work that has genuinely begun on Actual Start, and a future position you want the engine to honor on Planned Start.
3. Right-click the bar to open the operation menu. The first entry is Move Operation to Date/Time....
4. Choose Move Operation to Date/Time... The dialog opens with fields for the start and the end.
5. Type the start and the end you want the operation to occupy.
6. Tick Move Schedule to new Date/Time. This is the instruction that the schedule itself should follow the values you typed.
7. Click OK. The bar redraws at the typed position and turns to the Overridden state. The pending-changes count on the toolbar goes up.
8. Repeat for any other operations you need to place precisely. Every pending change stages together.
9. Press Save Changes to write the whole set, or Discard to snap every pending bar back.

What Changes When You Save

How to Check It Worked

Hover or read the bar's caption and confirm the times are the ones you typed, not a rounded neighbor. Then open the job on the Job View tab and compare the operation's row: with an actuals mode the Actual Start and Actual End columns should show your values while Sched Start and Sched End keep the engine's originals, which is exactly the plan-versus-reality split you want.

Finally, look for the Downstream Changed state on later operations of the same job. Its presence is normal after a move and means those steps may now be out of sequence. Either place them too or run the engine, as described in how to highlight downstream operations after a drag.

Common Mistakes

Typing a future timestamp while the mode says Actual Start & End. That records that the work already happened at a time that has not arrived yet, which skews progress figures and every report that reads them. For a future position, switch to Planned Start first.

Forgetting the tick box. The dialog's Move Schedule to new Date/Time checkbox is the instruction that the schedule should follow your typed values. Entering dates and clicking OK without it is the most common reason a careful planner reports that the exact move did not take.

Right-clicking the lead-time tail. The slate band after a job's last operation is display information, not a schedule row, so it has no operation menu. Change the product's lead time instead of trying to move the band.

Expecting the typed move to fix capacity. It will not. Saving records dates and stops there. Press Re-Schedule when you want the engine to reflow the job around your placement, a distinction covered in Save versus Re-Schedule on the Gantt.

Hunting for a single-bar undo. There is none inside the pending set: Discard reverts everything pending. Save the set, then use the right-click clear-actuals entries on the one you regret. The staging model is explained in staging Gantt changes with Save and Discard.

Fighting a bar that will not move at all. Locked segments, completed work, and externally fed actuals each resist for their own documented reason. Work through why a Gantt bar will not move rather than trying harder.

Next Steps

A typed move is usually one half of a pair: place the operation, then let the engine tidy the rest of the job. Read the Gantt right-click operation menu for the neighboring entries you will reach for next, especially locking and the clear-actuals family. If the move you just typed was really a machine change, moving an operation to another machine is the shorter route.

The takeaway

Dragging is for approximate work and typing is for commitments, and EDGEBIC gives you both on the same bar with the same staging safety net. Use the dialog whenever a shift opening, a collection time, or a promise makes the minute real, and follow it with a reschedule so the rest of the job agrees with what you just fixed. See the scheduler board in context on the EDGEBIC product page, and if you are coming from the earlier User Solutions planning generation, the move from RMDB to EDGEBIC covers what carries across. Then read how to move a job on the Gantt chart for the drag route and staging Gantt changes with Save and Discard for the batch habit that makes either route safe.