OEE computed on the server, from the machine’s own signals.
Run, stop and count signals come from the controller; the operator adds only what a machine cannot know. Availability, performance and quality are computed on the server to AFNOR NF E60-182, so the cockpit, the TV wall and Monday’s report show one figure, not three.
Two sites, two methods, one word for both.
Where OEE is assembled in a spreadsheet, each plant decides for itself what counts as planned time, which rate is nominal and what to do with the minutes between two orders. The result is called OEE everywhere and compares nowhere. VZIAM MES applies one set of definitions on the server, to every line, and keeps the inputs behind every figure.
Four rules the figure is built on.
The server enforces them; no procedure has to. Each one closes a way the same line could produce two different OEE figures.
- 01
OEE counts only while a work order runs.
Running time, output and rejects accrue to the order in production. Counts that arrive with no order running go to a separate counter, so they never inflate the order before or after, and they stay listed as a diagnostic rather than disappearing.
- 02
Nominal rate belongs to the article on the machine.
Performance is measured against the rate set for that pair, in parts per hour or seconds per part. If a pair has no rate, the machine’s default applies and a technical alert says so, rather than the figure quietly using the wrong reference.
- 03
A planned stop is not an availability loss.
Every stop reason carries its type under the standard: closure, planned, induced, own or micro-stop. Closures and planned stops reduce the time the line was required; induced and own stops cost availability; micro-stops cost performance.
- 04
Every second has exactly one state.
A machine’s timeline has no gaps and no overlaps. When a planned break and a breakdown cover the same minutes, a fixed priority decides which one the time belongs to, so a shift’s minutes always add up to the shift.
From the signal to the review, in one record.
AFNOR NF E60-182
The engine computes the standard’s time hierarchy (opening, required, operating, net and useful time) and the three factors from it. Losses are classed by the standard’s stop types, not by a local reading of them.
Calculated on the server
Ratios are recalculated as each signal or state change arrives. The cockpit and the TV display show the server’s result and compute none of their own, so a terminal setting cannot move a published figure.
Any window you ask for
The same figures by quarter-hour, hour, shift, work order or day. An order or a stop that crosses a shift change is split at the boundary, so each shift is credited with its own running time and its own output.
Losses ranked by cause
Pareto charts of stops and rejects, trends, period comparisons and a machine summary, from the same records the OEE comes from. The largest loss arrives as a cause with a duration attached, not as a percentage.
Alerts on the figure
An alert is raised when OEE falls below a threshold you set, or when a machine runs with no order open. Every alert carries a start, an end, a type and a severity, so the list of alerts is itself a record.
Exports for your own tools
The timeline exports as CSV with its segments, a KPI summary and the counter diagnostics. OEE reports export as CSV that opens in Excel, with a PDF summary.
What the engine commits to.
- Standard
- AFNOR NF E60-182
- Calculation
- On the server, at each signal or state change
- Window
- Only while a work order is in production
- Nominal rate
- Per article and machine
- Aggregation
- Quarter-hour · hour · shift · order · day
- Exports
- CSV · PDF summary
Frequently asked questions.
A question about your own lines? Ask the engineers who configure them.
Book a callYes, to AFNOR NF E60-182: its time hierarchy and its stop types, applied the same way on every line. The OEE calculation guide works through the three factors.
They go to a separate counter. OEE accrues only while an order is in production, so counts before the first order or between two orders cannot inflate either of them, and the timeline export lists them as a diagnostic.
The nominal rate set for that article on that machine. If none is set, the machine’s default rate is used and a technical alert is raised so the gap gets filled.
Not directly. They can qualify or split a stop and correct a count after a physical recount; each change is audited and the figures are recalculated on the server. The cockpit displays OEE; it never computes it.
Performance. A stop no longer than the micro-stop threshold set for the machine is classed as a micro-stop, which the standard treats as a performance loss, and it is kept out of MTBF and the breakdown Pareto.
Yes, and by quarter-hour, hour, work order or day. Shifts follow the patterns you define, such as three or two eight-hour shifts, and anything crossing a shift change is split at the boundary.
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.