Training path: Operator

For a machine operator running a shift from the floor, you spend most of your day on one screen: a claimed station (a kiosk device claimed for your machine, or for a whole cell of machines you’re covering).

Objectives

By the end of this path you can run a full shift from a claimed station: count good/scrap units, tag downtime by reason, and hand off a clean shift to the next operator.

Walkthrough

Onboarding

1. How to sign in to Spall, get your credentials working first.
2. How to run a claimed station, the one screen you’ll live in. Learn the tiles: Now for run state and count vs. target, Job for picking the job and tapping +Good/+Scrap, and Downtime for tagging why the machine stopped.

Core workflow

3. How to run a claimed station, when the machine stops, tag downtime by reason inline without leaving the station.
4. How to track first-pass yield and top defect types, understand how the scrap you count at the station feeds first-pass yield, and how the defect-type catalog (set up by an admin) shapes the Pareto a supervisor watches.

Advanced

5. How to build a kiosk wallboard, read the “live wallboard” half only: understand what the floor TV near your line is showing, so you can sanity-check your own numbers against it mid-shift.

Checkpoint questions

1. On the Job tile, what happens when you tap “+Good”, does it save immediately or wait for you to submit a batch at end of shift?
2. If the target isn’t showing on the Now tile, what does that mean?
3. You stop the machine for a jam. What’s the fastest way to record why, without leaving the station?
4. Why might a number on the station show an em-dash instead of a value?
5. What’s the difference between what you log from the station and what a supervisor sees on the Downtime Pareto?

You can now…

…run a full shift from a claimed station: count output in real time, tag every stop with an accurate reason, and trust that an em-dash means “no data yet,” not “zero.”