How to Clear Actuals for a Work Center From a Date Forward in EDGEBIC

The EDGEBIC by User Solutions Gantt carries a work-center-wide cleanup: right-click an operation and clear all actuals from that point forward for every job that uses the work center. It is the tool for the day a terminal was bound to the wrong machine, a test import landed on production, or a week of punches went to the neighboring station. This is how to use it without taking real history with it.

For single-operation corrections, 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 know which work center received the wrong actuals, and from which date. The clear works forward from the operation you right-click.
• You have decided the actuals are genuinely wrong. Recorded work is otherwise protected from every reschedule, and this menu is the one place that protection is deliberately removed.
• Any pending Gantt drags are saved or discarded. Pending changes live only on screen and will confuse the picture.

Step 1: Find the Starting Operation

Open the Schedule View tab. In the left panel, tick the jobs that touch the work center you are cleaning, or use Search jobs to bring them into view. Find the earliest operation on that work center whose actuals are wrong.

That bar is your starting point, because the clear runs forward from it.

Step 2: Pick the Right Scope

Right-click the bar. The menu offers four clear-actuals options plus the wide one, and choosing the narrowest that solves the problem is the whole discipline here.

Only reach for the last one when the problem is the station rather than a job.

Step 3: Run the Clear

Choose the work-center-wide item. The actual start and end date and time are removed from the affected operations, and each bar returns to the position the scheduling engine planned rather than the position the wrong actuals had pushed it to.

Bars that were showing a started or applied state drop back to the default state. A bar still showing an actual state after the clear belongs to a job outside your selection, or sits before the point you started from.

Step 4: Re-Record What Really Happened

Clearing removes the record. It does not create the right one. Go to the machine that actually ran the work and log it there:

• Use Log Actuals from the Gantt right-click or the Job View header to record the real start and the real hours per day.
• Or use manual entry at the terminal, which opens the same day grid an operator sees.
• Where the real hours already exist in a spreadsheet, bring them back in with how to import actuals from a file.

Log the real days before you reschedule, because the engine plans remaining work forward from your last logged position.

Step 5: Reschedule

Press Re-Schedule to re-plan the jobs you touched, or run the full schedule if the cleanup spanned the plant. Operations with no actuals are now free to be re-planned, including onto a different work center where the routing allows it. That freedom is what you were buying when you cleared the dates.

What Changes When You Clear

How to Check It Worked

Open the Job View tab for two of the affected jobs. The Actual Start and Actual End columns on the cleared rows should be empty, and the hours header should show actual hours consistent with what remains. Then open the job's audit trail from the header or the bar's right-click menu, and confirm the clear appears as an event with the right timestamp.

Common Mistakes

• Right-clicking the wrong starting bar. The clear runs forward, so a bar three days too early takes three days of good history with it.
• Using the work-center-wide option for a one-job problem. The per-job items exist for exactly that case, covered in how to clear a job's actuals from one operation forward.
• Clearing and not re-logging. An operation with no actuals reports as not started everywhere, and every progress figure that depends on logged hours drops with it.
• Clearing and not rescheduling. The bars return to their planned positions but the plan is unchanged until the engine runs.
• Clearing to make a report look better. Reports read the data honestly. Fix the data because it is wrong, never because the number is unwelcome.

See how recorded work is otherwise protected through every replan on the EDGEBIC product page.