Reading the Kiosk Punch History Drawer in EDGEBIC

In EDGEBIC by User Solutions, the punch history drawer is the record of everything that happened on an operation: every punch, every piece undo, and every supervisor correction, each stamped with who did it and when. It is where a lead reviews the minute-by-minute story of a job at the machine, and it is where a wrong punch gets fixed, always with a reason and never by erasing what came before. The drawer turns raw taps into a trustworthy, auditable history, which is the foundation of clean shop floor data collection.

Most shops keep corrections informal: a supervisor scribbles a new number on the traveler and the original is gone. That loses the one thing an audit needs, which is what changed and why. The history drawer keeps both.

What the Drawer Shows

Open the drawer from the kiosk header or from the planner, on a given operation. It lists the operation's punches grouped by kind, with filters so you can focus on one type at a time.

Each row is one punch: a single uninterrupted stretch of one state, with the operator name that rode on it. Together the rows are the operation's true timeline, built from taps as the state changed rather than reconstructed from memory at shift end. For how each of those taps is created, see how the kiosk captures a production punch.

Correcting a Punch

Operators make mistakes. A Complete tapped an hour early leaves a run punch with too few hours. The history drawer is the sanctioned place to fix it, and only a supervisor can.

1. Open the drawer on the operation and find the closed punch.
2. Edit the field, for example changing the logged hours from 4.83 to 5.83.
3. Type a mandatory reason, such as "operator tapped Complete one hour early, corrected from time-study sheet."
4. Recompute the daily breakdown so the rollup picks up the corrected value.

When you save, EDGEBIC does not overwrite the punch in place. It writes a separate adjustment record that captures the change.

The original punch row is left unchanged. The adjustment is the only record of the edit, and the daily breakdown is rebuilt from the corrected figures. A day that read 4.83 hours now reads 5.83, and the provenance of the change is permanent.

Why Edits Are Append-Only

The single most important property of the drawer is that adjustments are append-only. There is no delete path. If a supervisor needs to reverse a previous correction, they add another correction with the counter-value, and both entries remain in the record. Nothing is ever removed.

This is what makes the history drawer a forensic record rather than a scratchpad. You can always read the original entry, every change since, the author of each, and the reason for each. When a customer asks "prove this part ran when you say," or an auditor asks "why was this number changed," the answer is in the drawer, not in someone's memory. It is the same discipline that lets EDGEBIC schedule work where "prove it ran when you say" is not optional, the way User Solutions software has scheduled the 26,000-plus tasks of a US Navy Nimitz-class carrier overhaul.

Operator undos land in the same trail. The 10-second undo that takes back a mis-tapped piece writes its own visible adjustment, so a fat-fingered count cannot be hidden. The tap, the undo, and the net result all show.

Zero-Hour Punches and Other Oddities

Not every odd-looking row is a data problem. If an operator taps the same button twice quickly, a punch can open and close in the same instant. EDGEBIC clamps its duration to zero rather than writing a negative number, so it contributes nothing to the daily rollup. It is harmless. If you want the record to read cleanly for the next person, add an adjustment with a reason such as "duplicate tap." The row stays, annotated, and the history is both accurate and clear.

The drawer also surfaces the setup phase breakdown for a changeover, so you can see, for example, that teardown alone ran long. That granularity is what setup-variance reporting is built on, and it exists only because live punches record each phase separately.

How the Drawer Fits the Loop

The history drawer sits at the point where raw taps become the actuals the rest of the platform trusts. Corrections flow through it into the daily breakdown, which feeds the Job View, the progress reports, and the next reschedule. Because completed work is immutable in the scheduling engine, a deliberate correction through the drawer is the proper way to fix a wrong actual, and that correction is itself audited. The engine never silently rewrites finished work, and a supervisor can only change it on the record.

Larger, day-level cleanups belong in the planner's Log Actuals dialog, which shares the same append-only history. The two surfaces are consistent: whether a change is made at the machine or from the office, it is tracked with who, when, old, new, and why.

The Bottom Line

The punch history drawer is where a shop's real story lives: every punch, every piece undo, every correction, each with an author, a timestamp, and, for edits, a mandatory reason. Corrections are append-only, so the original and every change survive forever, which is what makes the record defensible. Use it to review what happened, to correct a wrong punch honestly, and to keep the actuals underneath your plan clean. See how those actuals drive the plan in the shop floor execution guide, and explore the platform at EDGEBIC.