How to Start a Job on the Shop Floor Kiosk in EDGEBIC

To start a job on the shop floor kiosk in EDGEBIC by User Solutions, bind the terminal to your work center, type your name in the Operator box, tap START SETUP on the NEXT UP job, step through the setup phases, and tap START RUN. That final tap is the one the schedule cares about. It opens the run punch and stamps the operation's actual start from the shared clock, so every planner screen sees the job as running within seconds.

This is the single task. The wider operator workflow, including what the kiosk deliberately refuses to do, lives in the shop floor execution guide.

Before You Start

Step 1: Bind the Terminal to a Work Center

1. Launch the kiosk. The Select Work Center dialog opens and asks you to pick the work center this session is bound to.
2. Choose the work center from the list.
3. Set Instance to the physical lane or machine within that work center. Instances are numbered from 1.
4. Tick Remember this selection if this terminal always serves this machine.
5. Click OK.

The header's Switch WC button re-opens this dialog later, which is how one terminal covers neighboring machines mid-shift.

Step 2: Put Your Name on the Punches

Type your name in the Operator box on the main screen. It is stamped on every punch you make and it is the only identity the kiosk carries: there is no login, PIN, or badge scan. A blank name makes the history drawer useless six weeks from now, so type it once at shift start and forget it.

Step 3: Read the Idle Screen

Three panels tell you what happens next.

If the queue looks stale because the planner just rescheduled, tap REFRESH rather than guessing.

Step 4: Clear the Routing Change Banner If One Appears

A yellow banner reading BOR HAS CHANGED SINCE THIS JOB WAS SCHEDULED means the routing was edited after this job was planned. The banner lists what changed: work center, setup, cycle, or queue time. Read it, tell your planner if it looks wrong, then tap Acknowledge. The banner is informational and never blocks the start. Why the routing carries a per-job snapshot at all is covered in routing snapshots explained.

Step 5: Tap START SETUP and Step Through the Phases

1. Tap START SETUP. The setup ribbon opens on its first phase, TEAR DOWN, with an elapsed clock for that phase only.
2. Tap the advance button as each phase finishes. The button always names the next phase: TEAR DOWN, then FIXTURE, TOOLS, FIRST ARTICLE, QA HOLD, RUN-OFF.
3. On the last phase the advance button reads START RUN.

Each phase closes its own punch and opens the next one, so a changeover that took 50 minutes arrives in reporting as six honest numbers instead of one opaque total. Six taps per changeover is the entire cost of setup variance reporting.

Step 6: Tap START RUN

Tapping START RUN closes the setup punch, opens the run punch, and stamps the operation's actual start at that moment if nobody has recorded one yet. From here the screen shows a running elapsed clock and the GOOD and SCRAP counters.

If earlier operations on this job have no actuals, the prior work centers warning appears first. Cancel stops so the earlier steps can be logged properly. OK auto-logs them with their planned values, tagged as system auto-filled. The full decision, including when accepting is defensible, is in how to backfill actuals for earlier steps.

What Changes When You Tap START RUN

How to Check It Worked

The elapsed run clock is counting and the GOOD and SCRAP counters are live. On the planner side, the job's Job View row shows an actual start equal to the time you tapped, and the Actual Live card for your step reads Running. If the counters refuse to increment, you are still in a setup phase or a paused punch: pieces only count during a run.

Common Mistakes

• Punching before switching the work center. A terminal that opens on yesterday's machine records real work against the wrong capacity. Check the header label before the first tap of the shift.
• Skipping the setup phases to save taps. Total setup time still gets recorded, but the breakdown that makes changeover improvement measurable is gone.
• Accepting the prior work centers prompt reflexively. It stamps planned values as facts on steps that may not have run. Accept it when the work happened, cancel it when it did not.
• Leaving the Operator box blank. Punches still record, but nobody can trace a correction back to a person later.

Next Steps

Counting output is the next task: how to record a piece count. When the machine stops, how to pause a job with a reason code covers the downtime side. Closing out is how to complete an operation.

Every task in this library is indexed on the EDGEBIC how-to hub. To see a terminal running beside a live schedule, book a walkthrough of EDGEBIC and bring one job you would punch today.