Docs/Production Station Kiosk

Production Station Kiosk

Public no-login kiosk for production-line operators to test and provision devices

Last updated: 2026-05-26

The Production Station Kiosk is the public, no-login UI the production line uses to test and provision devices. Mount it on a tablet next to a test fixture, an operator scans or types a device serial / IMEI / MAC, walks through the test template, marks pass or fail, and the result lands on the device record in S3Suite.

No accounts, no passwords, no dashboard access from this surface - just a single-purpose flow gated by a per-lot or per-station token URL.

Open the kiosk by visiting /station/ in a browser. The token comes from the lot's Multi-Station setup (see Manufacturing Suite).


Why a separate surface

  • Speed: no login means the operator hits the URL and is testing in seconds. Tablets stay logged in for the whole shift.
  • Scope: a leaked or photographed token only exposes one lot's test flow, never the rest of S3Suite.
  • Discipline: the kiosk does only test-and-submit. It cannot read other projects, see secrets, or change settings.

Concepts

TermWhat it means
Station tokenA 30-day URL token bound to a lot or a multi-station kiosk. Public; gives access to this lot's test flow only.
Multi-station kioskOne physical tablet bound to one named station (e.g. "ICT Station 1", "Final QC"). Each station picks its own test template at creation.
Test templateThe pass/fail / numeric / text / checkbox steps the operator walks through per device. Defined in the Engineering Suite.
IMEI validationPer-template toggle: when on, a 15-digit IMEI is required (cellular products). When off, any free-form serial is accepted.
Test reportThe record S3Suite creates from each kiosk submission - device serial, who tested (the station name), every step result, timestamp. Pinned to the device.

Operator quick start (90 seconds)

1. Open the kiosk

The production manager prepared a station URL. They sent it as a link, a QR code stuck on the bench, or pre-loaded the tablet's home screen. Open it.

Top of the screen shows:

  • The lot number and variant
  • The station name (multi-station setups) or just "Production Station" (legacy lot-level token)
  • Live counters: Manufactured, Passed, Failed

2. Enter device info

Type or scan the device's IMEI (cellular) or MAC address. If both fields are shown, fill at least one.

Tip: Most kiosks pair a USB barcode scanner with the tablet so the operator never types. The IMEI / MAC field gets focus on each new device, scan into it, the scanner appends Enter, and the kiosk advances automatically.

3. Run the test steps

The test template's items show one screen at a time:

Item typeWhat the operator does
Pass / FailTap the green tick or red X
NumericType the measurement; the kiosk shows the acceptable range and flags out-of-range values
TextType a free-form note (e.g. firmware version, calibration value)
CheckboxTick that the step was done
Required items block the next button until they're answered.

4. Submit

Add any final test notes, tap Submit.

  • If every required step passed -> the device is recorded as Passed, counters update, the kiosk returns to the device-info screen for the next unit
  • If any required step failed -> the device is recorded as Failed, same return-to-start
The operator sees a clear pass/fail confirmation banner with the device serial for half a second before the screen resets.

Production manager: setting up a kiosk

  1. Open the lot detail page in S3Suite (Manufacturing -> Production Lots -> click the lot)
  2. In the Stations section, click Add Station
  3. Fill in:
- Station name (e.g. "ICT Station 1") - Code (short label printed on the bench) - Test template - pick from the lot's variant-aware templates
  1. Save. S3Suite generates a token-bearing URL.
  2. Copy the URL (or display the QR code) and load it on the kiosk tablet.

Rotating a station's token

When the lot wraps up, or when a tablet is repurposed, rotate the token:

  1. Open the lot detail page
  2. Find the station in the list
  3. Click Rotate link
  4. Confirm
The old URL stops working immediately. The kiosk tablet needs the fresh URL to keep going. Tokens also expire 30 days after the most recent rotation, so a forgotten kiosk URL will auto-disable rather than stay live forever.

Multi-station vs legacy single-station

Legacy lots (created before the multi-station feature) have a single stationToken on the lot itself. The kiosk still works for those URLs - it falls back to the lot's default test template. New lots should always use the Stations section to add named stations; one tablet per station.


What gets recorded

Every successful submit creates / updates a Device record under that lot:

  • First submit for an IMEI / MAC -> new Device record, test history starts here
  • Repeat submit with the same IMEI / MAC -> a new test report is appended to the same device's history. The device is not duplicated. This is what makes multi-station testing work: the same unit can pass ICT, fail FCT, get reworked, pass FCT - one device with four test reports.
Per-template IMEI validation, when on, refuses ill-formed serials at the kiosk before the submit even reaches the server.

Pitfalls

  • "The kiosk says token expired." The 30-day window since the last rotation passed. Production manager rotates the token, kiosk gets the new URL.
  • "Two stations are submitting for the same device and the results overwrite." They shouldn't - submits append, they don't overwrite. If you genuinely see this, file a Bug Report with the device serial and both station codes.
  • "My out-of-range numeric step is being marked passed." Numeric range steps need both min and max set on the template. If the template was saved with one missing, the range check is disabled. Check the template in the Engineering Suite.
  • "My operator keeps scanning the same barcode twice." The kiosk's auto-clear-on-submit is the friction here. Add a 1-second "Submitted - serial X" confirmation toast as feedback - already in the UI but easy to miss if the tablet is mounted at an awkward angle.

Security model

  • The station URL is the entire credential. Treat it like a password.
  • The token is bound to one lot; a leaked URL exposes test submission for that lot only.
  • Tokens expire 30 days after the latest rotation; rotate at the end of a lot, when a tablet is moved, or whenever the URL might have leaked.
  • The kiosk has no read access to other projects, settings, secrets, or device records outside the bound lot.

Related docs