Skip to content
Jump to navigation
Jump to footer
Alle Videos

Video

The “why” and “how” of OEE recording

Manual entry — useful as a start

Manual OEE recording generally works well and is even recommended as a start: It forces everyone involved to actively deal with the system and makes it visible whether this actually happens.

However, it has typical weaknesses: discrepancies in allocation (e.g. how long a standstill really lasted), loss of confidence in the recordings and, in the case of manual Excel entries, additional data problems and complex evaluation.

Automated recording — recommended for multiple systems

If you want to collect OEE at several systems, you should rely on automated systems that pick up signals directly from the system. This enables reliable data and real-time response via an operator interface.

Engaging employees — not just reporting

A common mistake: The OEE is recorded, a reporting tool spits out figures — but the results are never reflected back to the machine operators. It's no use.

The goal is real involvement: employees should contribute domain knowledge and discuss together what has happened. To do this, they must see for themselves how their system is running — and develop a sense of whether or not reducing the speed really helps.

At the same time, employees should not be able to manipulate the data. The combination of transparency and protection against manipulation creates a common truth — a database that is no longer disputed. Instead of “the cleaning machine normally runs better,” it is clear: The OEE is 48%, and that is undeniable.

What can be recorded

Typical key figures in such a system: quantities, downtime, number of microstops, OEE by shift — as well as the system flow in minute resolution.