OEE monitoring tools for manufacturing, compared

The best OEE monitoring tool for your plant is the one that measures availability, performance and quality from the machines you already run, with no one retyping numbers after the shift. Tools differ mainly in where the data comes from: an operator’s log, a wired signal, a sensor on the outside of the machine, the machine’s controller, or a manufacturing execution system (MES) above all of them.

The sections below compare the five types, show what five named tools read as of October 2026, and work one shift through to show what the data source changes. They’re for engineers and plant managers choosing a first tool or replacing a spreadsheet.

What an OEE monitoring tool measures#

OEE multiplies the three factors, and each factor needs different data.^[1] Every tool on this page works the same formula, so the OEE glossary entry covers the terms once.

Run time and part counts can come straight from the machine. Quality rarely can: a mill that cuts a bad bracket runs the same cycle as one that cuts a good one, so a person or an inspection station decides which parts were scrap.

The ideal cycle time is the best cycle the process sustains for one part, and you enter it once per operation, as setting the ideal cycle time explains. For example, 1.6 minutes for a bracket on a Haas VF-2. For the arithmetic of each factor, see how to calculate OEE.

Five types of OEE monitoring tool#

Each type taps the machine at a different point. The tap decides what the tool sees on its own, and what your IT team reviews before anyone installs it.

The ISA-95 standard places PLCs and other control devices at Level 2 and the MES at Level 3, above them.^[2] The figure uses those levels.

Paper and spreadsheets#

An operator writes down stops, counts and scrap, and someone types them into a spreadsheet. It costs nothing to start and works on any machine.

It sees only what someone records. A 2-minute jam that happens 15 times a shift adds up to 30 minutes nobody stops to log, and the numbers arrive after the shift ends.

Wired signals and counters#

A cable from a machine output, such as a cycle-complete relay or the stack light, feeds a counter or display that works out run time and counts. It reads any machine with a usable signal.

An electrician wires it into the machine. It sees only what that one signal carries, so a stack light tells you running or stopped but not why.

External sensors#

A sensor on the outside of the machine reads vibration, sound, motor current or a light beam, and turns the signal into running, stopped and parts made. It needs no controller access and no wiring into the controls.

A 1990s knee mill and a new 5-axis machining center then report the same metrics, with nothing connected to either control.

Controller connections#

Software reads the CNC control or PLC directly over a protocol such as MTConnect, FANUC FOCAS or OPC UA. A control with no network port needs a wired signal instead, which carries cycles and state but none of the controller’s internals.

Controller data adds alarms, program numbers and process values such as spindle load to state and counts. Connecting to a control is a security concern for many plants, so IT usually reviews it first.

MES performance modules#

An MES runs production orders, and its performance module computes OEE from data that PLCs, SCADA systems and historians already collect. It ties OEE to the order, the product and the batch.

It works best where the controls and supervisory systems are already connected, since that’s where it gets its data. The project is scoped like any MES rollout, not like a sensor install.

Five tools and what each reads#

The 2023 version of this article listed five tools. Here is what each one reads and where it stands as of October 2026, taken from each vendor’s own pages.

FactoryTalk Metrics. Rockwell Automation describes FactoryTalk Metrics as data collection and analysis for plant equipment that reports OEE and finds the root causes of downtime and loss. Its product page also says the product will be discontinued and no longer available after September 2028, and points customers to Plex MES.^[4] If you run it today, plan the migration before you extend it to more lines.

AVEVA MES. If you know it as Wonderware MES Performance, AVEVA now says Wonderware InTouch, System Platform, Historian and MES are AVEVA solutions, and lists AVEVA Manufacturing Execution System as formerly known as Wonderware MES.^[5] Its MES page describes measuring OEE KPIs and schedule adherence in real time, with native integration for AVEVA System Platform.^[6]

TrakSYS. Parsec Automation describes TrakSYS as a modular MES that connects to equipment and PLCs, and to ERP, SCADA, LIMS and historians.^[7] Its performance solution tracks OEE, yield and downtime in real time.^[8]

MachineMetrics. Its connectivity page lists native connections over MTConnect, FANUC FOCAS, OPC UA, EtherNet/IP and other protocols, and digital I/O for equipment with outdated controls or no network interface. The same page says OEE runs on that data feed.^[3]

IoTFlows. SenseAi reads the machine from the outside, described in the section on sensors below. For a vendor-by-vendor scorecard, see the IoTFlows alternatives comparison.

Same shift, two data sources#

The data source changes which factor a loss lands in more often than it changes OEE. Vorne’s definitions put small stops in performance and stops long enough to warrant a reason in availability.^[1] Where your tool draws that line depends on what it records.

The 36 minutes don’t vanish. The operator log hides them inside slow running, where nobody can find them. The stop record shows them as 18 short stops you can count, classify and fix.

What to check before you choose#

Run these checks on the machines you know best before you trust any tool’s OEE.

The part count matters most, because it feeds two of the three factors. Count ten parts by hand at the machine and compare them with the tool’s count for the same ten cycles. If the count is off, the part-count troubleshooting checks find the usual cause in IoTFlows.

Track OEE with a sensor on every machine#

SenseAi mounts magnetically on the outside of a machine, reads vibration and sound, and decides running or stopped every second, with no PLC or controller access. It counts parts from the machine’s cycle, so IoTFlows reports OEE factor by factor: availability as uptime, performance as parts made against the ideal cycle time, and quality from the scrap operators log with a reason.

The Short Downtimes rule settles the split from the example above. Stops under a per-machine cutoff, 5 minutes by default, get a category or count as uptime, as you choose. On Enterprise, the IoTFlows edge device adds controller data from the controls you choose to connect.

Jesel, a valvetrain maker in Lakewood, New Jersey, reviews OEE daily and validates actual cycle times against its bills of material.

Which type to choose#

Pick by the machines you run and the data you need beyond OEE.

• Choose a spreadsheet when you’re proving the habit on one machine for a few weeks, before you spend anything.
• Choose a wired signal when one line has a clean cycle signal and you want a count display beside it.
• Choose an external sensor when your machines span brands and decades, or when controller connections are still under IT review.
• Choose a controller connection when the machines are networked CNCs and you need alarms, program numbers or spindle load, not only state and counts.
• Choose an MES performance module when you already run that vendor’s MES or SCADA and need OEE tied to orders, batches and genealogy.

You don’t need an MES to measure OEE. Start with the machines that limit output, read the three factors for a month, and add controller data or an MES once a question needs alarms, programs or order data.

Many plants combine types: a sensor on every machine, plus controller data on the CNCs that need it. To see what each controller protocol carries before you scope that second layer, read machine communication protocols.