Augos Operator Terminal

The Augos Operator Terminal is a sealed, food-grade industrial HMI with its own onboard computer, installed where the operator works. It is the brain of the line: it reads the pulse sensor, counts every cycle, detects a stop within a few missed pulses, asks the operator for the reason and times the human response, all on the unit itself. A network connection is needed only to sync to the Augos platform and to receive configuration over the air. That human response is the part of OEE a sensor alone can never see.

Reviewed 3 October 2026 · Author: Tim Stevens, Augos · Source: Augos Operator Terminal specification; hardware datasheet

What it is

The Augos Operator Terminal reads the machine and the person running it, and it does the work locally. It is an industrial human-machine interface with a quad-core 64-bit computer inside: the counting, the stop detection, the timing of every operator interaction and the local storage all happen on the unit, in real time, whether or not the network is up. The platform is where the results are reported and analysed, and where the terminal's rules are managed; the connection between the two is needed only to sync data upward and to push configuration and firmware down. One unit does the whole job, so a line needs no PLC connection. The operator signs in with a PIN, starts the job, and from then on every stop is caught by the sensor and classified by the person who was there. Because the terminal timestamps each interaction, the platform can say how quickly a stop was noticed, whether the operator cleared it alone or called a technician, and how long each stage of the response took. That record is what the Owner column is built on.

Source: Augos Operator Terminal specification; Augos Factory method, How the platform works

What it measures

Two things, from two inputs.

The first input is the pulse sensor, mounted on the line and wired to one of the terminal's two pulse inputs. Every machine cycle is a pulse; the terminal counts them to give output, running speed and, from the gaps between them, every halt down to the shortest interruption (what standard OEE calls a minor stop or micro-stop). The time between pulses is measured in milliseconds, and the terminal can be set to count on the rising edge, the falling edge or both, to suit the sensor and the line. When roughly three expected pulses fail to arrive the terminal declares a stop and starts the clock.

The second input is the operator. The terminal asks for a reason, records whether the stop was cleared on the line or escalated, and, with Augos Assist, timestamps each handover between operator and technician. Planned stops are declared before they start ("start changeover", "start cleaning") and timed against their Standard Allowed Time. Good and reject counts are captured at the end of the job. Every timestamp is system-generated and cannot be edited afterwards by any role.

Source: Augos Operator Terminal specification (stop detection, pulse inputs); Augos Factory method, Stoppage Response Stages

A shift at the terminal

The operator signs in with a PIN and selects the job: the product, the reference and the planned quantity. The line runs and the terminal counts. The line halts; after about three missed pulses the screen asks what happened. The operator picks a reason and either clears the fault and restarts, which the platform records as Operator Resolution, or calls for help, which ends Operator Evaluation and starts the technician's clock. Before a changeover the operator declares it, and the terminal times it against the standard. At the end of the shift the good and reject counts go in, the job closes, and the shift report is locked. The full walkthrough is on Using the terminal.

Specifications

The pulse sensor itself is a separate, sealed IP67 device; its specification is on the Pulse sensor page. The two ratings are often confused: the terminal is IP65, the sensor is IP67.

Source: Augos Operator Terminal specification sheet and technical specification; hardware datasheet (supplier and model not published)

When the network drops

The terminal does not depend on the network to measure, because the measurement happens on the terminal. Every pulse and every operator interaction is written to local storage first, and the live sync to the platform runs roughly every ten minutes while a connection exists. If the connection drops the terminal carries on counting and timing at full resolution, holds the backlog on board, and uploads it in order once the link returns. Local storage is sized for several months of readings.

Source: Augos Operator Terminal specification (data handling and sync)

Managed from the platform

Stop reasons, products, jobs, Standard Allowed Times, shift maps, diagnostics and firmware are all managed from the Augos platform. Configuration changes are pushed to the terminals from the platform, so a fleet across several lines, sites or regions is maintained centrally without a site visit for each change. Hardware is supplied by Augos: the sensor mounts at the bottleneck, the terminal mounts where the operator works, and because the rules arrive over the air a line is live within 48 hours of the kit arriving. See Deployment.

One terminal for every line

The Augos Operator Terminal and pulse sensor are the same hardware on every line, and Augos owns the hardware. Operators sign in with a PIN. The terminal's record feeds standard OEE, the loss breakdown, the Best Operator Benchmark and the operator dashboards. With Augos Assist, an optional extra, the terminal is also the point where operator and technician hand a stop over, which is what times the Stoppage Response Stages; those handovers are recorded only once Assist is in use. See What Augos Factory includes.

Source: Augos Factory single offer, 6 October 2026

Common questions