Setting Up the EDGEBIC Kiosk for Your First Shift

Setting up the EDGEBIC by User Solutions kiosk means binding a terminal to one work center and one physical machine lane, optionally remembering that choice, and typing an operator name, after which the terminal is ready to punch the work the scheduler has queued there. The whole process takes under a minute per terminal and needs no server, because the kiosk shares the planner's database directly. Getting the binding right is the foundation of clean shop floor data collection, because every punch a terminal writes inherits its work center and instance.

A kiosk is an execution terminal that lives at the machine. Standing one up for a first shift is deliberately simple, but a couple of decisions (which work center, which instance, whether to remember) shape how the terminal behaves every day after. This guide walks the setup and the two settings worth getting right the first time.

Before You Start

Three things need to be true before a terminal is useful:

• The kiosk app is installed on the terminal and points at the same database as the planner. The kiosk is a separate application that shares the planner's database directly, with no separate server. You point it at the shared data source and it works.
• Work is scheduled onto the work center. The kiosk's queue only offers work the scheduler has placed at the bound work center. An empty schedule means an empty queue.
• You know the work center and, if it has several machines, the instance. Each session binds to one work center and one physical lane.

Binding the Terminal

Launch the kiosk and the Select Work Center dialog opens with the prompt to pick the work center this session is bound to.

1. Pick the work center from the list, for example CNC-Mill-1.
2. Set the instance to the one-based physical lane within that work center. A work center with three identical machines has instances 1, 2, and 3. The instance is what stamps each punch with the exact machine that produced the work.
3. Optionally tick Remember this selection so the terminal always opens on this work center and instance. This writes the terminal's default so an operator never has to rebind at the start of a shift.
4. Click OK.

On the main screen, type your name into the Operator box. That name rides on every punch you make during the session. The kiosk trusts the floor here: there is no login, PIN, or badge scan, just a free-text name.

The Two Settings Worth Getting Right

Instance. Bind to the correct physical lane. If two identical machines share a work center and you bind both terminals to instance 1, their punches will not distinguish which machine actually ran the work. Give each its own instance so capacity and history stay accurate per machine.

Remember this selection. For a fixed terminal at a fixed machine, tick it. The kiosk then opens on the right machine every morning with no operator action. If a terminal ever starts on the wrong machine, it means the remembered selection is stale: rebind with Switch WC and tick remember again.

Your First Punch

With the terminal bound, the idle screen shows the queue for the work center: NEXT UP with the first job, COMING UP behind it, and YOUR DAY summarizing the shift. For the full screen tour, see what an operator sees at the kiosk.

To start the first job, tap Start Setup, step through the setup phases, and tap Start Run. The first Start Run stamps the operation's actual start from the shared clock, and within seconds the planner's Job View reflects it. From there the operator counts pieces, records pauses with reasons, and taps Complete Operation when done. For the mechanics, see how the kiosk captures a production punch.

One Terminal, Neighboring Machines

A single terminal can serve machines that sit close together. The Switch WC button in the header reopens the work center picker mid-shift, so an operator can rebind to whichever machine they are running and punch that work. This is handy when one screen covers two adjacent machines that run at different times.

Where both machines run in parallel, though, each needs its own session so their punches carry the correct instance. A dedicated terminal per machine is the cleaner arrangement whenever two machines produce at once.

What the Kiosk Will Not Do

Setting expectations for the first shift also means knowing the terminal's deliberate limits:

• No schedule editing. Operators punch work; they do not move, re-sequence, or reassign it. That stays with the planner.
• No plant-wide browsing. The terminal works its bound work center's queue only.
• No offline mode. The kiosk reads and writes the shared database live. If a terminal loses its connection, an operator punches when it returns or uses Manual Entry afterward. See what the kiosk does when the network drops.

These limits are why the kiosk is fast to learn: there is very little an operator can do wrong.

A First-Shift Checklist

• Terminal installed and pointed at the shared data source.
• Bound to the correct work center and instance.
• Remember this selection ticked for a fixed terminal.
• Work scheduled at the work center, so NEXT UP shows a job.
• Operators know to type their name in the Operator box.
• Everyone knows to tap Refresh after a reschedule and to pick honest pause reasons.

With those in place, the floor is ready to feed real actuals into the plan from day one. How many terminals to put out in the first place is a separate siting question, worked through in how many kiosk terminals your floor actually needs.

The Bottom Line

Standing up the EDGEBIC kiosk is a one-minute job: bind the terminal to a work center and physical instance, remember the selection for a fixed machine, and type an operator name. The kiosk needs no server, only the shared database, and every punch inherits the binding you set. Get the instance and the remembered selection right the first time and the terminal opens on the correct machine every shift, ready to feed clean actuals into finite capacity scheduling. See the whole loop in the shop floor execution guide, or explore the platform at EDGEBIC.