The Shop-Floor Kiosk Question, and Three Patterns We See

Most shops we work with eventually ask: should we put a kiosk on the floor? The answer is usually yes, but how, when, and what for varies more than you'd think. Three patterns cover almost everything we've seen.

Pattern 1: Read-only status display

A monitor on the wall, no input device, looping through current job status, machine state, and the day's priorities. Operators look at it but don't interact.

This is the cheapest kiosk to deploy because there's no operator authentication, no input UI, no error states. A small fanless PC behind a TV running a single-page dashboard in kiosk mode. The shop gets visibility without the friction of "training everyone on a new system."

When this works: shops where the existing job flow is mostly working and the operators are already disciplined about what they do. The kiosk is observability, not control. It surfaces information the supervisor would otherwise have to walk over and ask.

When this falls short: any time the kiosk's information needs to be edited from the floor. Status changes still happen on paper or in a separate browser session on the supervisor's desk. The kiosk is decorative.

Pattern 2: Operator login + job logging

Touch-screen kiosk on the floor with badge-based or PIN-based auth. Operators sign in to a job, log time, mark completion, flag a problem. Forge's kiosk mode does this out of the box.

This is the pattern that produces real operational data — actual time on actual jobs, captured by the person doing the work, in real time. It's also where the friction lives. If badging in adds 30 seconds to a setup, operators route around it. If the touch screen is in a dirty spot, gloves don't work and operators avoid it. If the kiosk is in the wrong place physically, no one uses it.

The kiosk has to be:

• Closer to where the work happens than to the supervisor's desk
• Mounted at a height that's usable standing
• Glove-friendly — capacitive touch with a glove-compatible screen, or resistive
• Clean — air-blown dust on the screen makes it unreadable in three weeks if it's near a CNC
• Tied to a badge reader or PIN pad, not a username/password (operators don't type passwords)

This pattern works when the shop is disciplined about WIP tracking and wants real-time data. It fails when the kiosk's location is wrong or the auth flow is too slow.

Pattern 3: Multi-station, role-based access

Multiple kiosks across the floor. Different access levels at each. The CNC station's kiosk only shows the active job on that machine. The receiving dock's kiosk only shows the inbound POs. The pack-out station's kiosk only shows ready-to-ship orders.

This is the most operationally powerful pattern and the most expensive to set up. Each station's kiosk is configured for the work that happens there. Operators see exactly what they need, no more.

The investment is justified for larger shops or shops with high-throughput discrete steps. A 75-person plastics shop with mold cells running in parallel benefits enormously. A 12-person job shop doing custom one-offs probably doesn't — the operators are mostly the same three people moving between stations and the role-based filtering adds complexity without saving time.

How to decide which pattern fits

Three questions, asked in this order:

How much of the shop's friction is "we don't know what's happening right now"? A lot → Pattern 2 or 3. A little → Pattern 1 or no kiosk at all.

Do operators currently log their own time, or does a supervisor reconstruct it later? They log → Pattern 2 lands easily. Supervisor reconstructs → introducing Pattern 2 is a culture change, not just a tooling change. Plan for resistance.

Is the floor physically conducive to a kiosk? Clean machining or assembly → easy placement. Wet processes, dusty cutting, environmentally hostile → mount selection matters more than the software does.

What we usually recommend

For most first-time Forge installs at a 20-50 person shop: start with Pattern 1 in month one, Pattern 2 in months two and three. The first month is to get the data flow established in the office (jobs created, routed, costed) before adding the complication of floor-level capture. Once the data foundation is solid, the kiosk lands cleanly because there's something for it to write into.

Skipping Pattern 1 and going straight to Pattern 2 occasionally works, but usually creates a chicken-and-egg problem — the kiosk needs accurate job data to be useful, and the office processes that produce accurate job data aren't fully running yet. Operators try the kiosk on day one, find half the jobs missing or mislabeled, and decide the new system doesn't work. That decision is hard to undo.

What we don't recommend

Don't buy commercial kiosk hardware unless you have a specific reason to. A $200 industrial Android tablet on a VESA mount with a USB badge reader covers 80% of cases. The expensive industrial kiosks are usually overengineered for the shop conditions our installs actually face.

Don't try to roll out Pattern 3 (role-based, multi-station) on the first install. Get Pattern 2 working at one or two stations, learn what your operators actually use, then expand. The wrong role configuration is harder to undo than the right one is to defer.

Don't tie the kiosk to a specific operator (one badge, one screen). Operators move between machines. Stations don't. The kiosk is attached to the station; whoever signs in is who's working there.

What we recommend talking about with us first

Mounting. Mounting is where good kiosk plans become unused kiosks. The right software in the wrong physical location is failed deployment. The supervisor's instinct is usually to put the kiosk where it's easy to wire up. The operator's need is usually for it to be where the work is. Those are often different walls. We'll come look at the floor before we commit to a location.