You can get real-time Overall Equipment Effectiveness (OEE) metrics by establishing a direct hardware and software data pipeline from machine controls to analytics dashboards , using modern Manufacturing Execution Systems (MES) or specialized machine monitoring platforms that interface directly with Programmable Logic Controllers (PLCs) via industrial protocols like OPC UA, MQTT, or Ethernet/IP.
Data Source (PLCs / Sensors): PLCs track raw machine states (running, faulted, idle, speed, and part count).
Industrial Connectivity Layer: Protocols like OPC UA or MQTT stream raw tags from the PLC edge.
MES / OEE Engine: Software parses signal changes into discrete events, matching machine stop signals to predefined state logic.
Automated Categorization: When a machine stops, the system logs the timestamp and reads PLC alarm or recipe registers (e.g., "Error Code 402: Jammed Feeder") to pre-populate the downtime reason. If an automated reason cannot be derived from PLC data, it triggers a prompt on an operator touchscreen terminal for rapid manual code selection.
To get real-time OEE (Overall Equipment Effectiveness), the best approach is to connect your machine PLCs directly to a manufacturing execution system (MES) or a production monitoring platform that collects machine-state signals automatically, identifies downtime, and calculates OEE continuously.
The key distinction is that collecting machine data automatically is not the same as automatically categorizing downtime. A strong solution does both: it detects machine stops from PLC signals and uses machine states, fault codes, operator input, and production context to assign meaningful downtime reasons.
1. How real-time OEE works
PLCs and machine controllers
Run/stop signals, cycle counts, fault codes, actual speeds
OPC UA · EtherNet/IP · Modbus TCP · industrial gateways
Edge data collection
Timestamp, normalize and buffer machine events
MES / OEE platform
Determine production state, classify downtime and reconcile counts
Live dashboards and alerts
OEE, availability, performance, quality, downtime Pareto and shift reports
Availability: planned production time minus downtime, divided by planned production time.
Performance: actual output relative to the ideal output possible during operating time.
Quality: good units divided by total units produced.
For useful real-time metrics, the system also needs the planned production schedule, ideal cycle times, and good-versus-reject counts—not just PLC run/stop signals.
2. Which MES platforms integrate directly with PLCs?
These are the strongest candidates to evaluate based on documented machine-data and downtime capabilities.
1. Sepasoft MES + Ignition
(Strongest fit for PLC-driven downtime)
Sepasoft's OEE Downtime Module uses real-time equipment-state values, commonly from PLC tags, to track machine states and assign configured downtime reasons. It supports automatic, manual, or combined downtime collection.
Downtime automation: Yes, using configured state values and reason mappings.
Live OEE: Yes, including production efficiency and downtime dashboards.
Best for: Manufacturers wanting configurable PLC-to-MES integration, detailed downtime analysis, and control over their industrial data architecture.
Tulip's Machine Monitoring connects to machine data through configured connectors, including OPC UA, and uses machine states, triggers, and downtime reasons for monitoring and analytics.
Downtime automation: Yes, when machine triggers and state/reason mappings are configured.
Live OEE: Machine monitoring and OEE analytics are supported.
Best for: Teams wanting machine monitoring combined with operator workflows, digital work instructions, and low-code manufacturing apps.
(Best match for automatic downtime categorization)
MachineMetrics is a machine-data and manufacturing execution platform designed particularly for discrete manufacturing. Its documented Automatic Downtime Categorization feature applies rule-based categories using machine states, alarms, PLC I/O, program information, and scheduled time windows.
Downtime automation: Yes, explicitly supported.
Live OEE: Yes, by machine, shift, and operation.
PLC integration: Supports multiple industrial protocols and machine-control types; exact signal availability varies by equipment.
Best for: CNC shops, machining operations, and manufacturers prioritizing rapid deployment and machine-level visibility.
Plex combines MES capabilities with industrial IoT and production monitoring. Its documented offerings include automated machine-data collection, real-time equipment performance visibility, and OEE monitoring.
Machine-data collection: Yes.
Live OEE: Supported through production monitoring and related capabilities.
Downtime categorization: Validate the specific automatic reason-assignment workflow for your machines and intended Plex modules.
Best for: Manufacturers looking for broader enterprise MES, production management, and ERP-connected operations.
This is a capability-based shortlist, not a claim that every platform supports every PLC model or feature out of the box.
4. How to automate downtime categorization properly
For example, a machine stops for 90 seconds. A useful implementation would:
Detect the stop from a PLC state or cycle-complete signal.
Capture the start time, end time, machine ID, and relevant alarm or I/O signals.
Apply configured rules, such as an alarm code mapping to Machine Fault or a tool-release signal mapping to Tool Change.
Assign a category automatically when the evidence is sufficient.
Ask the operator to select a reason only when the cause is ambiguous.
Update live OEE and downtime Pareto reports.
A critical caveat: a stopped machine does not automatically reveal why it stopped. If your PLC only exposes a running bit, you can detect downtime, but reliable root-cause categorization requires additional signals, alarm data, contextual logic, or operator input. MachineMetrics documents this distinction explicitly.
5. My recommendation
Choose MachineMetrics if your immediate goal is direct machine connectivity, real-time OEE, and automatic downtime categorization with minimal operator entry.
Choose Sepasoft MES + Ignition if you need a configurable MES tightly integrated with industrial automation, existing Ignition infrastructure, and broader plant-floor workflows.
Consider Plex if the project is part of a wider enterprise MES and ERP modernization.
Consider Tulip if operator workflows and rapidly configurable manufacturing applications are just as important as machine monitoring.
Before selecting a vendor, run a pilot on two or three machines and verify that it correctly identifies stops, assigns the expected downtime reasons, and calculates OEE against your actual production schedule.
One question to narrow this down
What PLCs or machine controls do you have on your shop floor?
