To record a partially finished operation in EDGEBIC by User Solutions, log the real hours and then decide one thing: is the work done or still running? If it is done with fewer hours than planned, mark the operation complete, which makes it a short-confirm. If it is still running, leave the actual end blank so the step stays in progress. Either way the logged hours are locked as history, and the next reschedule handles the remaining hours.
The reschedule mechanics that act on all this are in how EDGEBIC preserves completed work on reschedule.
Before You Start
| Prerequisite | Why |
|---|---|
| You know whether the part is physically finished | It decides whether you stamp an end or leave the step open |
| The site's partial-confirm behavior is set | It decides what the next reschedule does with the missing hours |
| Actuals for the days worked are ready to enter | The engine plans the remainder from what is logged |
The Two Cases
They look similar and behave differently. Get this distinction right and the rest follows.
| Case | What you do | What the engine does next reschedule |
|---|---|---|
| Short-confirm (work done, fewer hours than planned) | Log the hours, mark the operation complete | Keeps the logged hours, forward-shifts the planned-minus-actual gap per site policy |
| In progress (work still running) | Log the hours, leave the actual end blank | Keeps the logged hours, forward-allocates the routing requirement minus what is logged |
Path A: Record a Short-Confirm
- Open Log Actuals for the operation.
- Enter the hours actually worked. Six hours against a planned ten, for example.
- Tick the option to mark the operation complete.
- Optionally supply a completion time. Without one, the end snaps to 23:59 of the last day with logged hours.
- Click Save.
The operation now has an actual end and reads as complete. The six logged hours are history. On the next reschedule the four-hour gap is treated according to the site's partial-confirm behavior.
Path B: Record an In-Progress Operation
- Do not stamp an actual end.
- Open Log Actuals, enter the hours worked so far on their real days, and save.
- The operation stays in progress: an actual start, logged hours, no end.
On the next reschedule the step keeps its work center and its logged hours, and the remaining routing hours are forward-allocated from the resume point. The step stays open until the operator or planner closes it.
Set the Site Policy Once
What a short-confirm does with the missing hours lives under Options, as the partial-confirm behavior. Set it as a shop, not per job.
| Option | What the next reschedule does |
|---|---|
| Trust the operator's Actual End | The stamp is the truth. Downstream queues behind the recorded end and the unfinished hours are written off. |
| Forward-shift the remaining hours (default) | The logged portion stays on its real days. The gap re-plans onto the next free slot, and downstream queues behind that. Standard APS practice. |
| Trust Actual End unless the step is flagged short | Trust the stamp by default, forward-shift only steps the planner flagged on the BOR editor. |
Step: Reschedule
Recording the partial completion does not move the plan. Run a targeted Re-Schedule for the job so the remainder gets a real slot and downstream steps re-queue. The safe procedure is in how to reschedule safely.
What Changes When You Reschedule
| Surface | Effect |
|---|---|
| The logged hours | Preserved verbatim on the days they happened |
| The operation's row | One row: history and remainder merged, with a schedule window that spans both |
| The remainder | Placed on the next free slot on the same work center |
| Downstream steps | Re-queued behind the remainder plus any queue or transit time |
| The audit trail | A reschedule event is appended with old and new dates |
How to Check It Worked
Open the operation's Log Actuals grid: the days with real hours carry them, and the operation shows exactly one row rather than two. On the Job View, the operation's schedule window now extends past its logged days to cover the re-planned remainder, while the actual start and any logged hours are unchanged. After the reschedule, run the anomaly report and confirm the split-op check comes back empty, which is how you know the history and remainder were merged into one database row rather than left as a stray pair. What the anomaly checks actually look for covers that check.
Common Mistakes
- Stamping an end when the work is still going. That turns an in-progress step into a short-confirm and forces the gap through the site policy prematurely. Leave the end blank while work continues.
- Leaving a genuinely finished step open. An in-progress step with fewer hours than planned never crosses the coverage threshold, so it can show Running forever. If the part is done, complete it.
- Deciding the policy per job. The partial-confirm behavior is a site setting. Flipping it around individual jobs is how a plant ends up unable to explain its own numbers.
- Over-logging. Logging more hours than planned leaves no remainder to forward-shift, which is correct, but it also means the routing estimate was low and the next job will be planned short.
Next Steps
The two building blocks are how to complete an operation and how to enter actual hours for yesterday. To watch a short-confirm play out end to end, read the partial completion reschedule walkthrough. If a job jumped further than you expected afterward, why did my job jump after a reschedule explains the resume point.
Every task in this library is indexed on the EDGEBIC how-to hub. Bring a step that ran short to a demo of EDGEBIC and we will short-confirm it and reschedule around it live.
Expert Q&A: Deep Dive
Q: How do I decide whether the missing hours are real work or plan fat?
A: Ask the operator one question: is the part done? If the part is finished and off the machine, the missing hours are plan fat, and the routing estimate for that step is too high. If the part is not finished, the missing hours are real work still owed and the operator closed the step early. The two answers point at different fixes. Plan fat means correct the routing so the next job through that step is not planned long as well, because otherwise you will keep seeing the same gap. Real work owed means the forward-shift default is doing exactly what you want, and the only thing to check is that the remaining hours landed on a sensible slot.
Q: We set the policy to forward-shift but sometimes want to trust the operator on specific steps. Is that possible?
A: Yes, that is the third policy option: trust the operator's actual end by default, and forward-shift only steps the planner has flagged as short on the BOR editor. It inverts the burden, so the routine case writes the gap off and only the exceptions carry a remainder forward. Which of the three fits is a shop-culture question more than a technical one. Shops where the floor's word is final tend to trust the stamp. Shops running standard APS practice tend to forward-shift by default. The flag-driven middle option suits shops where most steps are trustworthy but a few known-fat operations always over-run their estimate. Pick one under Options and stay with it, because deciding job by job is where the confusion starts.
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.