A user interface built specifically for operators on the floor. Every action taken becomes a record, complete with a timestamp, the user's identity, and its link to the order, the material lot, and the resource in use.
A terminal built for operators. Each action becomes a record with time, person, order, lot and resource attached.
Today Operators fill in paper travellers.
With VECHR MES MOVE IN and MOVE OUT at the terminal, timestamped.
Today The oldest lot is picked by memory.
With VECHR MES FEFO and FIFO are recommended, and expired stock is blocked.
Today Process values are retyped from the machine.
With VECHR MES Sensor readings arrive straight from the equipment.
| Entry path | How it works |
|---|---|
| By Production Order | Pick the order, follow the routing stepper, choose a unit, then act. |
| By Station | Pick the work center, see its queue of scheduled slots, then follow the execution wizard. |
| By Unit | Scan a unit and act on it directly. |
All three lead to the same transactions and the same rules.
The work instructions for each step appear in the user interface exactly when the operator needs them. There is no paper, no separate binder, and no doubt about which revision is current.
If the equipment can already report its own data, operators should not have to key the same value in by hand.
The right material is selected under the applicable rule, while expired lots are blocked outright.
| Lot | Quantity | Expiry | Status |
|---|---|---|---|
| COCO-2026-A01 | 200 kg | in 275 days | Recommended |
| COCO-2026-A02 | 250 kg | in 335 days | Second choice |
| COCO-2026-A03 | 150 kg | in 360 days | Third choice |
| COCO-2025-X01 | — | expired 3 days ago | Blocked |
Example: cocoa mass under FEFO with a 365-day shelf life.
What production teams usually want to confirm about the operator user interface.
No. The operator user interface shows one step at a time, complete with its instructions, materials, and checks. The interface is deliberately simple; the configuration complexity stays on the admin side.
Conflicts are prevented at transaction level, so one unit cannot run the same step simultaneously from two different interfaces.
Yes, as long as the reason is recorded in the audit trail. An expired lot, however, stays blocked and cannot be overridden.
The system raises a non-conformance automatically. If its severity is critical, the affected unit is held immediately without waiting for anyone to act.