- Home
- Blog
- EDGEBIC How-To
- How to Complete an Operation in EDGEBIC
To complete an operation in EDGEBIC by User Solutions, stamp its actual end: tap COMPLETE OPERATION at the shop floor terminal, or set the Actual End on the planner desktop. Completion is explicit. Logging hours never closes a step by itself, and that separation is deliberate, because a completed operation becomes immovable history that the next reschedule will not touch.
The full logging workflow around this one action is in how to log actual hours and pieces.
Before You Start
| Prerequisite | Why |
|---|---|
| The operation has an actual start | An end without a start is a logically inconsistent state |
| The hours you intend to record are logged | Completing does not stop you logging later, but the end-of-day snap uses the last day with hours |
| The job is not already marked complete | A completed job locks actuals entry until it is reopened |
Path A: Completing at the Terminal
- Tap COMPLETE OPERATION on the running screen. The same action is available as COMPLETE from the paused screen.
- If earlier operations on the job have no actuals, the prior work centers check runs here exactly as it does at run start. Cancel to log them properly, or OK to auto-log them from plan.
- The open punch closes, the day-by-day production hours roll up, and the operation's actual end is stamped at that moment.
- The terminal returns to its idle screen showing the next queued job.
Server time is used throughout. The operator never types a completion time from the terminal.
Path B: Completing on the Planner Desktop
Three routes write the same value.
The grid cell. Double-click the row's Actual End cell in the Job View grid. The Edit Actual Dates dialog offers End = Now for the current moment and Use Sched End to copy the planned end. Save.
The Log Actuals dialog. Open Log Actuals for the operation, enter any remaining hours for the final day, tick the option to mark the operation complete, optionally supply an exact completion time, and click Save.
The Gantt. Right-click the operation's bar on the Schedule View tab and take the Edit Actual Dates route.
Step 3: Understand What Time Gets Stored
Two rules govern the stored end.
- Supply a time and that time is used. No adjustment is applied.
- Complete without a time and the end snaps to 23:59 of the last day that has logged hours. This is why a step started at 08:00 and completed the same afternoon never ends up finishing before it began.
An end that is not strictly after the start is refused at every entry point. An inverted pair is always a data-entry error, most often a date picker sitting on the wrong year.
What Changes When You Save
| Surface | Effect |
|---|---|
| The operation's state | Completed: both actual dates now present |
| The Gantt bar | Takes the completed shade |
| Actual Live card | Status badge flips to Complete |
| Job View header | Actual hours, remaining, and percent complete recompute from the roll-up |
| The audit trail | A completion event is appended with actor and timestamp |
| The next reschedule | The operation is preserved verbatim: dates, hours, and work center all untouched |
| Downstream steps | They re-plan from this operation's real end rather than the planned end |
The end-product roll-up only reports 100 percent when every operation is done, so finishing one step early never flags the whole job complete. Closing out the order itself is a separate action, covered in how to mark a whole job complete.
How to Check It Worked
Open the Job View grid and read the operation's row: the Actual End column carries the value you expect and the bar shows the completed shade. In the Actual Live view the step's card reads Complete rather than Running. Then run your reschedule and check the same row again. The actual start and actual end must be identical to what they were before the run. That comparison is the whole promise, and it is described in how EDGEBIC preserves completed work on reschedule.
Common Mistakes
- Assuming logged hours close the step. They mark it as covered on screen. They do not stamp an end, and reports that filter on the end date will not see it.
- Completing before the hours are entered. The end-of-day snap uses the last day that has logged hours, so a premature completion can land on the wrong day. Enter the final day's hours, then complete.
- Completing an operation whose predecessors were never logged. The prompt will tell you. Accepting the backfill stamps planned values as facts on steps that may not have run.
- Fixing a mistaken completion by rescheduling. A reschedule will faithfully preserve the wrong completion. Reopen the operation first, then reschedule.
- Completing a step that shows Running forever. If the planned hours exceed what the job really needed, the step never crosses the covered-hours threshold. Stamp the end explicitly, or correct the routing so the next job is planned honestly.
Next Steps
If the completion was wrong, how to reopen a completed operation reverses it. If the completion was right but the dates were not, how to correct a wrong actual date covers the fix. If the step finished with fewer hours than planned, read how to record a partially finished operation.
The whole task library is indexed on the EDGEBIC how-to hub. Bring a job that is halfway through its routing to a demo of EDGEBIC and we will close a step and reschedule around it live.
Expert Q&A: Deep Dive
Q: An operator tapped COMPLETE OPERATION on the wrong job. How much damage is that?
A: Recoverable in about a minute, as long as you catch it before the next reschedule. The wrong job now carries an actual end, so the engine will treat that step as finished history and plan everything downstream from it. Nothing is corrupted; the classification is simply wrong. Clear the actual end on the wrongly-closed operation to put it back in progress, then complete the operation that really finished. If hours were logged against the wrong job too, zero those day rows before you move on. [How to reopen a completed operation](/blog/how-to-reopen-a-completed-operation-in-edgebic) walks the exact sequence.
Q: A step is planned for 16 hours, the part is genuinely finished, and only 10 hours were logged. Do I still complete it?
A: Yes. Completion is a statement about the physical work, not about hitting the hour estimate. Stamp the end and let the six-hour gap tell you something. What happens to that gap is a site policy, set once under Options as the partial-confirm behavior. The default forward-shifts the remaining hours onto the next free slot on the same work center, which is right when the operator closed early. Trusting the operator's actual end writes the gap off, which is right when the routing was simply fat. Decide it as a shop rather than job by job, and see [how to record a partially finished operation](/blog/how-to-record-a-partially-finished-operation-in-edgebic).
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.
