Marking a Job Complete From the Floor in EDGEBIC

Tapping Complete Operation on the EDGEBIC by User Solutions kiosk closes the open punch, rolls up the day's production hours, and stamps the operation's actual end, all in one action. From that moment the operation counts as finished everywhere in the plan, and no later reschedule will move it. Completing a job from the floor is how the shop hands the plan a permanent, honest record of what happened, and it is a pivotal moment in shop floor data collection.

A completion is more than a status flip. It closes an open time segment, computes the operation's daily productive hours from its run and rework punches, and gives the operation a real finish time that downstream planning anchors to. This article walks through exactly what the tap writes, the safeguards around it, and the clever end-of-day rule that keeps same-day completions valid.

What the Tap Writes

When an operator taps Complete Operation (available from both the running and paused screens), EDGEBIC performs three steps:

1. Closes the open punch. Its end time is stamped and its hours are computed from open to close.
2. Rolls up the day. The run and rework punches are grouped by date and their hours summed into the operation's daily production hours. Setup, idle, down, and teardown are excluded, so the rollup is productive time only.
3. Stamps the actual end. The operation's actual end is set to the current server time.

The kiosk then returns to its idle screen, showing the next queued job for the work center. On the planner side, the operation now reads as completed on the Job View, the Actual Live card flips to Complete, and progress reports pick up the finished state.

The Prior-Work-Centers Check

Complete runs the same guard as the start of a run: if an earlier step of the same job on another work center has no actuals yet, EDGEBIC shows a warning rather than silently completing a downstream step over an unlogged upstream one. The operator has two honest choices:

• Cancel and log the earlier steps properly first, or ask the planner to.
• Continue, which auto-fills the missing upstream steps from their planned dates and tags them as system-filled, so the planner can review them later.

Those auto-filled days carry a distinguishing badge on the Log Actuals grid, so a planner can always tell backfilled days from hand-entered ones. This is the same handshake documented in how partial completions carry forward.

The End-of-Day Snap

Here is a subtle rule that prevents a whole class of data-entry failure. When an operation is marked complete without an explicit end time, EDGEBIC does not simply use the day's calendar date as the finish, because a bare date carries a midnight time. If an operation started at 08:30 in the morning and its finish were recorded at 00:00 that same day, the end would fall before the start, and the platform's inverted-date guard would reject it.

Instead, EDGEBIC snaps the actual end to the last instant of the latest day that has actual activity: one tick before the next midnight, effectively 23:59:59 on that day. So an operation that started at 08:30 and finished the same afternoon gets an actual end late that evening, comfortably after its start. The snap makes "mark complete the same day you started" always safe, and it is why same-day partials never trip the guard. That guard, in turn, keeps every downstream reschedule working from clean dates.

What the Rollup Excludes

It is worth being precise about what "the day's production hours" means at completion, because the exclusions are deliberate. Only run and rework punches feed the productive rollup. Setup, idle, down, and teardown time are all recorded on their own punches, and they matter for downtime and setup-variance analysis, but they never enter the operation's production hours. So an operation that spent two hours in setup, six hours running, and forty minutes down for a coolant alarm completes with six productive hours, not eight-plus. That separation is what keeps a long changeover or a machine fault from quietly inflating an operation's apparent output, and it is why the completion figure a planner reads is a clean measure of work done rather than time elapsed.

Completion Is Permanent

Once an operation has both an actual start and an actual end, it is completed history, and immutability applies. No reschedule, no scheduling mode, and no configuration setting moves it. The engine re-emits the completed row exactly as recorded and plans only the remaining steps forward from the real finish. This is why completing work from the floor matters so much: it is the shop's permanent statement of record. For the full guarantee, see why actuals are immutable.

That permanence is not a cage, though. If an operator tapped Complete an hour early, a supervisor corrects the finish in the history drawer with a mandatory reason, and the original value is kept beside the correction forever. The engine never rewrites a finish on its own; a human can, and the edit is audited.

A Worked Example

Schedule 55, started 08:30 on January 12. The operator logs three hours of run time across the morning and taps Complete at 11:30 without specifying an explicit end in any dialog.

• The open run punch closes and its hours stamp.
• The day rolls up: about three productive hours for January 12.
• The end-of-day snap resolves the actual end to January 12 at 23:59:59, comfortably after the 08:30 start.
• The inverted-date guard checks 08:30 against 23:59:59 and passes.

Had the snap not fired and the bare date been used, the finish would have read midnight, before the start, and the save would have failed. The operation now shows as completed, and tonight's reschedule plans the next work center forward from January 12, not from the original plan.

The Bottom Line

Marking a job complete from the floor is one tap with three effects: the open punch closes, the day's productive hours roll up, and the operation gets a real actual end. A prior-work-centers check keeps the loop honest, the end-of-day snap keeps same-day completions valid, and immutability keeps the finished record permanent while still allowing an audited supervisor correction. That is how an operator's final tap turns into a trustworthy anchor for finite capacity scheduling. See the whole cycle in the shop floor execution guide, or explore the platform at EDGEBIC.