The screen beside the line, built for a hand in a glove.
The operator picks the machine once, then runs the shift from one screen: start an order, qualify a stop in three taps, declare rejects on a numpad, run the checks that are due and call maintenance. It computes nothing itself, and it keeps working when the Wi-Fi does not.
Ask the person at the machine only what the machine cannot know.
Counts, cycle times and machine states come from the controller. What is left for the operator is the part only they can supply: why it stopped, what was rejected, which material lot went in, whether the check passed. The terminal is built around asking that quickly, at the machine, and then getting out of the way.
Four rules the terminal is built on.
Each one is about trust: in the figure on the screen, and in the screen when the network is not there.
- 01
The terminal computes nothing.
OEE, states and counts are computed on the server. The terminal sends what the operator declares and shows what the server returns, so two screens on the same machine cannot disagree.
- 02
Losing the Wi-Fi loses nothing.
When the network drops, an amber banner says so and the operator carries on. Declarations are stored on the device and sent in the order they were made once the link is back.
- 03
A refused declaration is shown, not dropped.
If the server refuses a queued declaration (because the order was closed from an office in the meantime, say), it stays on screen with the reason and exactly what was entered, until someone re-enters it or sets it aside.
- 04
Every target is at least 44 pixels.
Buttons sit in the same place on every screen and are large enough for a gloved hand, and quantities go in on a large numpad rather than a keyboard.
One screen for the shift, at the machine.
Take a post
The operator picks the workshop, the line and the machine, and the tablet stays on that machine. If the network is down at that moment, the machines it already knows are still offered.
Start an order, or a quick run
Start a planned work order, or a quick run when production cannot wait for one. The nominal rate for that article on that machine loads with it.
Stops in three taps
Family, component, reason, from the list set for that machine. A stop longer than 60 seconds turns the screen orange and asks.
Rejects, material and checks
Rejects on a numpad with their reason, material lots scanned or typed against the order, and the checks and forms that are due, most urgent first.
Call maintenance
A request goes to maintenance with the machine, the component and the severity attached, from the screen the operator is already using.
The shift, shown back
The timeline of the last hours and the output hour by hour against the target rate, so the people being measured are the first to see the figure.
What the terminal commits to.
- Touch targets
- At least 44 px
- Input
- Touch, large numpad, barcode scanner
- Network loss
- Declarations queued, replayed in order
- Calculations
- None on the device; server only
- Hardware
- Tablet or touch screen with a browser
- Stop prompt
- After 60 s, by default
Frequently asked questions.
Tell us what your operators fill in today, and ask the engineers what would change.
Book a callA tablet or touch screen with a current browser, on the plant network. Nothing is installed on it, and a USB or Bluetooth barcode scanner works in keyboard mode.
An amber banner appears and the operator keeps working. Declarations are stored on the device and replayed in order when the network returns, and one the server refuses stays on screen with its reason.
Yes. They can reclassify or split a stop on their own machine and correct a count after a physical recount. Each correction is audited, and larger changes after the shift are a supervisor’s.
Yes, as a quick run when production cannot wait for an order. Counts that arrive with nothing running at all go to a separate counter rather than to an order.
Yes, with their own account and the operator role, so every declaration carries who made it.
Plan the change before it reaches the line.
Request a demo and an engineer looks at how your production runs today, shows how the software would fit around it, and where a pilot on one line would start.
01Pick a time
Choose a slot in the calendar, and note what you make and what reads your machines today.
02Screen shared with an engineer
A video call with someone who builds the software, in English or French.
03What would connect
For each machine, its path: native (OPC UA, MQTT or HTTP push), through a gateway, or nothing to build.