- Home
- Blog
- EDGEBIC How-To
- How to See a Machine's Job History on the Kiosk in…
How to See a Machine's Job History on the Kiosk in EDGEBIC
To see a machine's job history on the EDGEBIC by User Solutions kiosk, tap History on the header to open the history drawer, which lists every punch and every edit for the bound machine with who made it and when. The drawer filters by Run, Setup, Down and Idle, and Edits, and it is where a supervisor reviews what actually happened at the machine and corrects a punch. Corrections never delete the original: they add an adjustment record with the old value, the new value, and a mandatory reason.
This is the history and correction task. The wider operator workflow lives in the shop floor execution guide.
Before You Start
| Prerequisite | Why |
|---|---|
| The kiosk is bound to the machine you want to review | The drawer shows the bound work center and instance's activity |
| The punches you want to review are closed | Open punches show as in progress; closed punches carry final hours |
| You have supervisor authority to correct a punch | Editing a closed punch is a supervisor action and requires a reason |
Step 1: Open the History Drawer
Tap History on the kiosk header. The history drawer opens over the current screen and lists the punches and edits for the bound machine, most recent first. Opening the drawer changes nothing: it is a review surface. An operator can open it to see the shift so far, and a supervisor opens it to make a correction.
Step 2: Filter to What You Are Looking For
The drawer offers filter tabs so you are not scrolling through everything at once.
| Filter | What it shows |
|---|---|
| Run | Production run punches with their hours and piece counts |
| Setup | Setup punches, including the phase-by-phase changeover records |
| Down / Idle | Pauses and downtime with the reason code each carried |
| Edits | Every correction made, including operator piece undos |
The Edits tab is the audit view. It shows every change anyone made, which is how a job's record stays honest: an operator's ten-second piece undo appears here just as a supervisor's hour correction does. How these punches roll up into the numbers a planner reads is covered in actuals tracking explained.
Step 3: Review a Punch
Select a punch to see its detail: the state, the start and end times, the hours computed on close, any piece counts, the reason code if it carried one, and the operator name stamped on it. Because timestamps come from the shared clock at the moment of each tap, the times are what actually happened, not what someone typed.
Step 4: Correct a Punch (Supervisor)
To fix a wrong punch, a supervisor edits the field, for example the hours on a run punch that was completed early, and types a reason before saving. The reason is mandatory. Saving writes an adjustment record that carries the old value, the new value, the field changed, and the reason, while leaving the original punch row in place.
Step 5: Rebuild the Daily Totals
After a correction, rebuild the daily breakdown so the corrected hours reach the planner. The rebuild recomputes the machine's daily hours from its current set of closed run punches, so the edited value flows into the totals that show up in Job View and the reports. The adjustment record and the rebuilt total are two separate things: the adjustment documents the change, the rebuild applies it.
What Changes When You Correct a Punch
| Surface | Effect |
|---|---|
| The original punch | Unchanged; it stays in the record |
| The Edits filter | Gains an adjustment row with old value, new value, and reason |
| The daily hour breakdown | Recomputed on rebuild to reflect the corrected hours |
| Planner screens | Show the corrected hours once the breakdown is rebuilt |
How to Check It Worked
The Edits tab shows your adjustment with the reason you typed, and the original punch still appears with its original value. After the rebuild, the affected day's hours match the correction. If the planner's Job View still shows the old number, the breakdown rebuild has not run yet for that schedule.
Common Mistakes
- Expecting the original punch to disappear after a correction. It never does. The adjustment sits alongside it. That is the point of an append-only trail.
- Editing a punch without rebuilding the daily totals. The adjustment is recorded but planners keep seeing the old hours until the breakdown rebuilds.
- Trying to delete a confusing zero-hour punch. It cannot be deleted. Annotate it with a reason like duplicate tap instead, and coach against double taps.
- Letting operators attempt corrections. Beyond the ten-second piece undo, corrections are a supervisor action with a mandatory reason.
Next Steps
To see the shift-level rollup of the same punches, read how to handle a shift handoff on the kiosk. If a wrong date needs fixing on the planner side rather than the floor, see how to correct a wrong actual date.
Every task in this library is indexed on the EDGEBIC how-to hub. To watch a correction flow from a kiosk edit into a live planner schedule, book a walkthrough of EDGEBIC.
Expert Q&A: Deep Dive
Q: An operator hit Complete an hour early and the day now shows too few hours. How do we fix it from the floor?
A: This is exactly what the History drawer is for. A supervisor opens History on that machine, finds the closed run punch for the day, edits the hours to the correct value, and types a reason such as tapped Complete an hour early, corrected from the time-study sheet. The daily breakdown then rebuilds and the corrected hours appear in the planner's Job View. The original punch with the wrong hours stays in the record, and the adjustment sits next to it with the old value, the new value, and the reason. So the correction is transparent: anyone reviewing the job later sees both the mistake and the fix, not a silently altered number.
Q: We keep seeing zero-hour punches in the history and it is confusing people. Where do they come from?
A: A zero-hour punch usually comes from a double tap: the same button pressed twice quickly, which opens and immediately closes a punch. The kiosk clamps any negative or zero duration to zero rather than writing a negative number, so the row is harmless in the daily rollup, it just contributes zero hours. It looks odd in the drawer, though. A supervisor can annotate it by adding an adjustment with a reason like duplicate tap, which does not delete the row but explains it for anyone who reviews the history later. The cleaner fix is upstream: coach operators to single-tap, since the zero-hour rows are almost always fat-finger artifacts.
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.
