Operator User Interface

The MES operator screen, where shop-floor work actually gets done

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.

In short

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.

What operators do in the user interface

  • Move In / Move Out Operators start and finish each step directly in the user interface. Every timestamp is captured automatically, so a unit's whole journey can be traced back.
  • Material consumption The system recommends a lot based on FEFO or FIFO. Operators can still pick a different lot when they need to, but must give a reason, which is then recorded in the audit trail.
  • Quality data capture Measurements are recorded directly against pass/fail limits. If a value falls outside specification, the system raises a non-conformance automatically.
  • Recording a non-conformance Operators can record a deviation, choose a non-conformance code, and set its severity. At critical severity, the affected unit is held immediately.
  • Flexible by design Transaction types can be added to suit the process, rather than forcing every plant onto one fixed set.
Move In Consume material Collect data Move Out out of spec Non-conformance On hold

Three ways into the same work

Entry pathHow it works
By Production OrderPick the order, follow the routing stepper, choose a unit, then act.
By StationPick the work center, see its queue of scheduled slots, then follow the execution wizard.
By UnitScan a unit and act on it directly.

All three lead to the same transactions and the same rules.

Built for a busy shop floor

  • A refresh resumes the task The screen keeps its state in the URL, so a refresh mid-task lands exactly where the operator was.
  • You can see who else is on a unit Presence indicators and conflict alerts show when someone else is working the same unit. A warning appears if the screen is open in two tabs.
  • Checked before it is sent Every transaction runs pre-flight checks. A unit on hold blocks further action until it is released.
  • Move Out walks the operator through the rest Move Out can open a wizard that chains data collection, work-instruction acknowledgement, pallets and signatures in order.
  • Revisits follow the rules you set When a unit returns to a step through rework, the Specification decides which gates must be redone. By default acknowledgement, data collection and signatures are redone, and consumed material is kept.
  • Your own screen, the same enforcement The transaction rules live in one shared package used by the backend and the frontend. A custom operator screen gets identical enforcement, and an eligibility check reports which actions are available and why the rest are blocked.

Work instructions right in the user interface

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.

  • Step by step, in context Operators see what to do for the step they are working on, at the moment they need it.
  • Confirmed as the process runs Each step confirmation is captured automatically as part of the execution record.
  • Always the correct version Instructions come from the routing the order is using, so a process change never leaves an operator working from a stale instruction.

Process data arrives without being retyped

If the equipment can already report its own data, operators should not have to key the same value in by hand.

  • Read straight from the equipment Process parameters can be recorded automatically over OPC UA, MQTT, or Modbus TCP.
  • Attached to the right unit Every reading is tied directly to the production unit and the step being run, rather than stored separately and reconciled by hand later.
  • Checked as it is recorded Values are compared against their specification limits immediately, so a deviation is caught at the step that caused it.

FEFO and FIFO allocation

The right material is selected under the applicable rule, while expired lots are blocked outright.

  • FEFO: first expired, first out For material with an expiry date, the system recommends the lot with the nearest expiry.
  • FIFO: first in, first out For non-perishable material, the system follows receipt order so older stock is used first.
  • Override with a reason Operators can choose a different lot where there is an operational reason, but the reason must be recorded and becomes part of the audit trail.
  • Expired lots are blocked An expired lot is not merely flagged with a warning. It cannot be used in production at all.
LotQuantityExpiryStatus
COCO-2026-A01200 kgin 275 daysRecommended
COCO-2026-A02250 kgin 335 daysSecond choice
COCO-2026-A03150 kgin 360 daysThird choice
COCO-2025-X01—expired 3 days agoBlocked

Example: cocoa mass under FEFO with a 365-day shelf life.

earliest expiry first recommended expired, blocked override needs a reason

Frequently Asked Questions

What production teams usually want to confirm about the operator user interface.

Do operators need training on a complicated system?

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.

What stops two operators working on the same unit at once?

Conflicts are prevented at transaction level, so one unit cannot run the same step simultaneously from two different interfaces.

Can an operator override the recommended lot?

Yes, as long as the reason is recorded in the audit trail. An expired lot, however, stays blocked and cannot be overridden.

What happens if a measurement falls outside specification?

The system raises a non-conformance automatically. If its severity is critical, the affected unit is held immediately without waiting for anyone to act.

Keep reading

Terms on this page(6)
FEFOFirst Expired, First Out
Use the material that expires soonest first.
FIFOFirst In, First Out
Use the material that arrived first, first.
MESManufacturing Execution System
The system that runs and records production on the floor: orders, materials, steps, quality and machines.
Modbus TCPModbus over TCP/IP
A long-established industrial protocol, carried over an Ethernet network.
MQTTMessage Queuing Telemetry Transport
A lightweight publish/subscribe protocol for sending machine data.
OPC UAOPC Unified Architecture
The open standard for reading data from PLCs and machines securely.
See the full glossary →
Request a Walkthrough