AI Fusion Kiosk

Fusion Kiosk is a shop-floor terminal that puts your production schedule directly in front of the people running the work, built as part of AI Fusion Production Scheduler. Instead of operators needing a desk, a platform login, or a supervisor to relay assignments, the kiosk gives them a touch-optimized screen where they can sign in, see their assigned jobs, and report progress as work happens. It's designed specifically for the realities of a shop floor: shared terminals used by multiple operators across a shift, PIN-based sign-in that's fast and badge-scan friendly, and a "Complete Job" screen built as a large, single-purpose page rather than a small dialog meant for a desktop. Because it draws from the same schedule your planners build and adjust, changes made in Fusion Production Scheduler show up on the kiosk without any separate step, keeping the plan and the floor working from one current version of the truth.

Operators sign in at the kiosk with an Employee ID — typed in or scanned from a badge — and a PIN, rather than a full platform username and password. This means you don't need to provision a platform account for every operator just so they can report time and job progress; the kiosk credential is separate and lightweight, managed specifically for shop-floor use. Administrators set the PIN policy — minimum length and format, with a digits-only option that's friendlier on a touchscreen than a mixed-character password — and supervisors handle day-to-day credential management, like setting an operator's first PIN or resetting one after a lockout. Once signed in, the kiosk automatically signs the operator back out after they complete a job, clock out, or leave the terminal idle, so it's immediately ready for the next person on a shared device rather than staying logged in under one operator's name.

Kiosk access is built around a few layered protections. PINs themselves are hashed, meaning no one — including supervisors managing credentials — can ever view an operator's actual PIN, only reset or clear it. Every action taken on kiosk credentials, like setting, resetting, unlocking, or clearing a PIN, is logged and attributed to the supervisor who made the change. Login sessions are secured by a signing key that's generated during setup and stored encrypted in the platform's secret store; if that key is ever rotated, every active kiosk session is invalidated at once, which is why it's treated as a deliberate, infrequent action rather than routine maintenance. On top of that, repeated failed sign-in attempts trigger a lockout with a configurable threshold and duration, so a lost badge or a few mistyped PINs can't be used to brute-force access to the terminal.

Yes. Fusion Kiosk is installed as its own component alongside the core Fusion platform rather than being automatically included. During setup, it's selected as an optional component — along with things like the Automation Engine and, for Macola sites, the Macola API — and runs on its own web server address, separate from the main platform site. Because the kiosk needs to reach your Fusion platform to pull schedule data and validate sign-ins, installation includes pointing it to your platform's public URL so the two can communicate. This is typically a one-time setup step handled during your initial Fusion rollout or when you're ready to bring shop-floor terminals online, and it doesn't require re-installing or disrupting the core platform or planner-facing tools already in use. Once installed, adding additional kiosk terminals on the shop floor is largely a matter of pointing each new device at the same platform address rather than repeating the full setup process.