How to Handle a Shift Handoff on the Kiosk in EDGEBIC

To handle a shift handoff on the EDGEBIC by User Solutions kiosk, tap Handoff on the header and read the Shift Handoff summary: Setup, Run, and Down hours, good and scrap piece totals, and the recent pauses with their reason codes. It is the open issues and the productive-time picture the oncoming shift inherits, on one read-only screen. Nothing is written and nothing moves, so an operator can open it any time to check where the shift stands.

This is the handoff task specifically. The full operator workflow around it lives in the shop floor execution guide.

Before You Start

Step 1: Open the Shift Handoff Summary

Tap Handoff on the kiosk header. The Shift Handoff summary opens. This is a read-only screen: opening it collects and displays data, it never writes any. That means the outgoing operator can open it early to preview the shift, and the oncoming operator can reopen it to confirm what they are inheriting.

Step 2: Read the Hour Buckets

The top of the summary splits the shift into three hour buckets.

Run is the productive number. Setup and Down are shown alongside it, not folded into it, so the shift's output time and its lost time are legible separately. How that hour split feeds the wider schedule is covered in actuals tracking explained.

Step 3: Read the Piece Totals

Below the hours, the summary shows the shift's good and scrap piece totals. Good pieces are the produced quantity; scrap is tracked separately, and every scrap piece carried a reason when it was recorded. The two numbers together tell the oncoming shift how far along the current job is and whether quality has been an issue.

Step 4: Read the Recent Pauses

The Recent Pauses list shows the most recent Down and Idle events with the reason code each carried, drawn from the four categories: Machine, Material, Quality, and Waiting. This is the part that carries open issues across the shift change. A coolant problem that paused the machine is on the list with its category, so the next operator inherits the problem instead of rediscovering it.

Step 5: Pass It On

Read the summary to the oncoming operator, or print it. Because the screen is a snapshot of real punches, there is no verbal step where an issue can be forgotten: if it paused the machine, it recorded a reason, and the reason is on the list.

What Changes When You Open the Handoff

Nothing in the database. The handoff is a projection over the shift's closed punches. It reassigns nothing and reschedules nothing, because the kiosk cannot edit the schedule. Any real movement of work is a planner action back in the scheduling application, informed by what the handoff shows.

How to Check It Worked

The three hour buckets sum to roughly the elapsed shift time minus any open punch, the piece totals match what the operator remembers tapping, and the Recent Pauses list names the interruptions the shift actually had. If a running job's hours look low, its current punch is still open and will roll into the totals when it closes.

Common Mistakes

• Reading Run and expecting it to equal the whole shift. Run is productive time only. Add Setup and Down for the elapsed picture.
• Expecting an open job's hours in the totals. Open punches are excluded until they close. Complete or pause the job first if you need it counted.
• Skipping pause reasons during the shift. A pause with no honest reason leaves the Recent Pauses list uninformative, which is the one thing the handoff exists to provide.
• Treating the handoff as an action screen. It reports; it does not move work. Rescheduling is a planner task.

Next Steps

To dig into any interruption on the list, open how to see a machine's job history on the kiosk. Closing out a job before the shift ends is how to complete an operation.

Every task in this library is indexed on the EDGEBIC how-to hub. To see a handoff summary build itself from live punches, book a walkthrough of EDGEBIC.