Clearing an operation's actual start date in EDGEBIC by User Solutions returns it to not started, which is the only state in which the scheduler is free to move it again. Somebody punched the wrong job, a terminal was bound to the wrong machine, or a start got recorded on the step below the one that ran. This is the correction, and the order to do it in.
For editing rather than removing a date, see how to correct a wrong actual date. Every task in this library is mapped on the EDGEBIC how-to hub.
Before You Start
- You are certain the start is wrong. Recorded work is protected everywhere else in the product, and this is one of the few places that protection is deliberately lifted.
- You know whether hours were also logged against the operation, because dates and daily hours are corrected separately.
- The job is not marked complete. A completed job locks actuals entry until you reopen it.
Step 1: Find the Operation
Open the Job View tab and select the job. The grid lists one row per operation with its scheduled dates beside its actual dates, so the wrong row is usually obvious: it carries an actual start that the shop floor never made.
The Gantt tells the same story in color. An operation with only a start recorded shows the started state rather than the default one.
Step 2: Clear the Actual Start
Clear the Actual Start Date cell so it is blank, and save. The operation reverts to not started.
Two things are worth knowing about this path:
- Clearing a start does not trigger the prior-operations prompt, because removing a start cannot create a gap upstream.
- Clearing a start does not clear an actual end. If an end is present, the operation is left claiming a finish with no beginning, which is an inconsistent state that reports badly everywhere.
Step 3: Clear the End as Well, if There Is One
If the operation also carries an actual end, clear it too. Two routes do the same thing:
| Route | When to use it |
|---|---|
| Blank the Actual End cell on the Job View row | You are already in the grid correcting the start |
| Right-click the bar on the Gantt and clear both the actual start and end date and time for the operation | You are working visually and want both gone in one action |
If you only want to reopen a finished operation and keep its start, use the menu item that clears the actual end only. That is a different task, covered in how to reopen a completed operation.
Step 4: Deal With the Hours
Dates and hours are separate records. If hours were logged on days that never happened, open the Log Actuals grid for the operation and correct or remove those day rows. When you change values that had been reported before, the dialog asks for a reason, which is stored in the logging history with the old value, the new value, and your name.
Give a real reason. "Fix" tells the next person nothing. "Punched onto wrong job, moved to JOB-2026-0104" tells them everything.
Step 5: Reschedule
Press Re-Schedule to re-plan the affected job, or run the full schedule if the correction spanned several jobs. The un-started operation is now treated as not started, so the engine plans it from where the job really is, and it can place it on an alternate work center where the routing allows one.
What Changes When You Clear
| Surface | Effect |
|---|---|
| The operation | Returns to not started once both actual dates are gone |
| The Gantt bar | Falls back from the started state and, after a reschedule, to the engine's planned position |
| Progress figures | Percent complete, remaining hours, and every report built on logged work recompute |
| The next reschedule | The operation is freely re-planned, including onto an alternate work center |
| Audit trail | The change is recorded, so the correction itself is inspectable |
How to Check It Worked
Look at the Job View row: Actual Start and Actual End should both be empty, and the hours header should no longer count work the operation never did. Then run the reschedule and check the bar's state. A bar still showing a recorded state after a clear usually means one of the two dates survived, or a planned start pin is holding it.
Common Mistakes
- Clearing the start and leaving the end. The operation then reports as finished with no beginning, and the health checks will flag the inconsistency.
- Clearing the dates and leaving the hours. Progress figures still count work against an operation that claims it never started.
- Clearing instead of correcting. If the work genuinely happened an hour earlier than recorded, edit the date rather than removing it.
- Forgetting the other job. A start recorded on the wrong operation usually means a real start is missing on the right one. Record it before you reschedule.
- Expecting the plan to move on its own. Clearing a date changes the record. The plan changes when the scheduler runs.
See how recorded work is protected through every replan on the EDGEBIC product page.
Expert Q&A: Deep Dive
Q: An operator punched onto the wrong job for two hours this morning. What is the clean fix?
A: Fix the wrong job first, then the right one. On the job that was punched by mistake, clear the actual start on that operation and remove the day's logged hours in the Log Actuals grid, giving a real reason when it asks, because that reason is what the audit history will show later. Then go to the job that actually ran and record the start and the two hours there. Finally run a reschedule so both jobs re-plan from where the shop genuinely is. Doing it in that order matters: if you log the right job first and leave the wrong one started, two operations claim the same two hours and every progress and utilization figure double counts them until somebody notices.
Q: I cleared the start but the bar has not moved back to where the engine planned it. Why?
A: Three things commonly hold a bar in place after a clear. The actual end is still set, so the operation still carries recorded work and stays protected. A planned start pin was saved on that bar from a drag, which the engine honors on the next run exactly like an actual would until a real start is logged. Or nothing has re-planned yet, since clearing a date does not run the scheduler. Check the bar's state color first, then clear the end if it exists, remove the pin if there is one, and press Re-Schedule. The bar should land back on the engine's own position for the remaining work.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.