Why the EDGEBIC Kiosk Has No Login (and Why That Is Deliberate)

The EDGEBIC by User Solutions shop-floor kiosk deliberately has no login, no PIN, and no badge scan. Operators type their name in a trusted free-text box, and that name is stamped on every punch they make. This is not an oversight or a feature waiting to be built. It is a design decision that keeps the terminal fast, keeps the floor moving, and puts the rigor where it belongs: on the planner side, where scheduling decisions are actually made. Kiosk no login manufacturing is a choice about friction, and this article explains the reasoning.

Every second an operator spends fighting a terminal is a second not spent making parts. A login screen, a forgotten PIN, a badge that will not scan with oily gloves: these are small frictions that add up across a shift and, worse, tempt operators to stop logging altogether. The kiosk is built to be the path of least resistance, because data that is easy to capture is data that actually gets captured.

What the Kiosk Is (and Is Not)

The kiosk is EDGEBIC's operator terminal: a touch-first application that lives at the machine and shares the same database as the planner application directly, with no separate server in between. It is bound to one work center and one physical instance per session. For the full introduction, see what is a shop-floor kiosk and how to set up a shop-floor kiosk.

The kiosk is kept small on purpose. It deliberately does not do several things:

• No schedule editing. Operators cannot move, re-sequence, or reassign work.
• No job browsing. It works its bound work center's queue, not a plant-wide viewer.
• No offline mode. It reads and writes the shared database live.
• No operator accounts. The Operator box is a trusted free-text name.

That last point is the subject here, and it follows directly from the first three. Because the kiosk cannot change the plan, there is nothing for a login to protect.

Why No Login Makes Sense

Authentication exists to control access to things people should not touch. On the kiosk, there is nothing of that kind. An operator cannot alter the schedule, cannot see other machines, cannot reassign work. The only thing they do is report what happened at their own machine. Guarding that behind a login would add friction to protect nothing.

What the kiosk needs instead is attribution: a record of who claimed each piece of work. The free-text Operator name provides exactly that. The name is stamped on every punch (setup phases, run time, pauses with reasons that feed your machine downtime tracking, piece counts, and completion) and it is visible to supervisors in the history drawer. When a supervisor corrects a punch, the correction requires a reason and is kept forever alongside the original as an append-only adjustment. So the history drawer becomes a full forensic record: who claimed the work, and who changed it and why.

The distinction is attribution versus authentication. A shop floor needs to know who ran a job; it rarely needs to cryptographically verify their identity at the machine. The kiosk provides the first and does not pretend to provide the second. That honesty about scope is what keeps it frictionless.

Where Operator Identity Actually Matters

None of this means EDGEBIC ignores operators as a scheduling concept. It means operator identity lives where it does real work: on the planner side.

Operator-level scheduling with skills and certifications is a distinct planner-side capability. There, an operator is a modeled resource with certifications, a roster, and availability, and the scheduler can require that a step needing a certified welder is only planned when that welder is on shift. That is a scheduling constraint, a decision about who is allowed to do what and when, and it belongs in the plan, not in a login prompt on the floor.

Keeping these separate is the elegant part. The kiosk stays a fast execution terminal that anyone at the machine can use in seconds. The scheduling rigor, the "only certified people run this operation" logic, sits with the planner where it can actually influence the plan. One place for speed, one place for control.

A Worked Example

Tuesday morning, a shared terminal between two neighboring mills.

• 07:55. Operator C. Diaz starts a session bound to CNC-Mill-1, instance 1. Diaz types "C. Diaz" in the Operator box. No login screen, no PIN.
• 08:50. Diaz taps Start Run on the queued job. The run punch opens carrying the name C. Diaz, and the actual start is stamped.
• 11:30. A coolant alarm. Diaz taps Pause, picks Machine, then the coolant reason. The pause punch carries the name and the reason.
• 12:00. Shift break relief. Operator M. Ruiz takes over the same terminal, types "M. Ruiz" in the Operator box, and taps Resume. From here every punch carries M. Ruiz. No logout ritual was needed because there was nothing to log out of.
• Later. A supervisor reviewing the history drawer sees the run and pause under C. Diaz and the resumed run under M. Ruiz, each with its server timestamp. When one piece count needs a correction, the supervisor edits it with a reason, and that edit is preserved beside the original.

The whole day is fully attributed, and no operator spent a second authenticating.

The Guardrail Around It

The no-login model works precisely because the kiosk's scope is tight. It is worth stating the guardrail plainly: the reason a free-text name is safe is that the kiosk cannot do anything a login would need to prevent. It reports reality; it does not shape the plan. All the authority that could cause harm (moving work, changing due dates, reassigning machines) stays with the planner. See the wider separation of roles in the daily rhythm of a kiosk-run shop and how those reported actuals then steer planning in how a reschedule uses last night's actuals.

If your traceability needs go beyond attribution, the answer is not a kiosk login. It is the planner-side operator model, where certified assignment becomes a scheduling constraint. The kiosk deliberately does one job well: capturing what happened, with as little friction as possible, so the floor never has a reason to stop reporting.

For the full punch-to-plan picture, see the shop floor execution guide, and explore the platform at EDGEBIC.