Menu
Sensor Fusion for OEE: When PLC Data Alone Is Not Enough

Sensor Fusion for OEE: When PLC Data Alone Is Not Enough

PLC data captures most of OEE but misses certain losses. How sensor fusion (vision, vibration, audio) fills the gaps modern plants need to close.
Sensor Fusion for OEE: When PLC Data Alone Is Not Enough
Sensor Fusion for OEE: When PLC Data Alone Is Not Enough

Key takeaways

  • Sensor fusion = combining multiple data sources (PLC + vision + vibration + audio + power) into one OEE signal.
  • PLC-only OEE captures roughly 70-85% of true loss; the gap is mostly micro-stops, slow cycles, and visual quality issues that PLCs do not see.
  • Vision systems catch cycle counts on older machines without count outputs and identify visual defects.
  • Vibration and power monitoring catch degradation (Performance loss) that PLC state does not.
  • Fusion is most valuable on older equipment that lacks modern PLC instrumentation — the cheapest path to high-fidelity OEE without retrofitting.

Short answer: Sensor fusion combines PLC signals with vision, vibration, audio, and power data to compute OEE more accurately than any single source can. PLC data captures most losses but misses micro-stops, visual quality issues, and degradation invisible to discrete state changes. Adding non-PLC sensors closes that gap, especially on older equipment that was not designed for modern OEE instrumentation. See also OEE vs Utilization.

Why PLC-only OEE leaves loss on the table

A PLC reports what its logic was designed to report. Modern PLCs expose run state, cycle counts, fault codes — enough for solid OEE. But three categories of loss are typically PLC-invisible:

  • Micro-stops below the PLC threshold. The line paused for 8 seconds because the operator cleared a jam. PLC sees no fault, just a momentary state blip.
  • Visual quality issues. A part is dimensionally good but visually flawed. PLC says good; downstream rejects it.
  • Gradual degradation. A motor is drawing more current than it should but is still in spec. PLC reports normal; the asset is in fact approaching failure.

These losses are real and PLC-invisible. Sensor fusion catches them.

What sensor fusion adds

Vision. Cameras count parts when the PLC does not. Cameras catch visual defects. Cameras detect operator presence and jam-clearing micro-stops. Cheap to deploy, high-value addition.

Vibration. Accelerometers on motors and bearings catch degradation before PLC faults fire. Performance loss often shows up as elevated vibration weeks before MTBF moves.

Audio. Acoustic monitoring picks up cavitation in pumps, bearing degradation, valve hammer. Cheap, retrofittable, often overlooked.

Power. Current and power monitoring on motors detects load anomalies, jams that did not throw a fault, and energy waste during slow cycles.

Temperature. Thermal cameras and discrete sensors catch overheating before failure.

How fusion actually works

The OEE platform ingests signals from all sources, time-aligns them, and applies rules or models:

  • If PLC says running AND vision says no parts coming off, the line is in a micro-stop. Tag as Performance loss.
  • If vibration spikes for 5 minutes followed by PLC fault, attribute the fault to the underlying degradation, not the discrete event.
  • If power draw is high but cycle time is normal, the asset is approaching failure even if it has not faulted.

Some platforms use simple rules; more sophisticated ones use ML models trained on historical data per asset.

When sensor fusion pays off

  • Older equipment without modern PLC instrumentation.
  • Visual-defect-heavy processes (assembly, finishing, packaging).
  • Plants with frequent micro-stops that PLC does not log.
  • Predictive-maintenance use cases adjacent to OEE.

For greenfield plants with modern PLCs, the marginal benefit is smaller. For brownfield retrofits, sensor fusion is often the cheapest path to high-fidelity OEE without changing the PLC.

Common mistakes

1. Over-sensoring. Adding vibration, vision, audio, power, and temperature without a clear question for each is a budget sink. Pick the sensors that close specific known gaps.

2. Skipping calibration. Vision systems need lighting consistency. Vibration sensors need proper mounting. Audio needs ambient calibration. Skip these and the data is noise.

3. Treating fusion as automatic. Combining signals requires rules or models. Buying sensors without a fusion strategy gives you data, not OEE improvement.

4. Ignoring data volume. Vision and vibration generate orders of magnitude more data than PLC tags. Storage and bandwidth planning is real.

How an OEE platform supports fusion

A modern OEE platform accepts multi-source input — PLC via OPC UA, vision via REST or RTSP, vibration via MQTT or proprietary protocols — and time-aligns them into the unified time-state model. The platform applies rules or models to interpret combined signals as Availability, Performance, or Quality events.

Fabrico's OEE module supports multi-source data ingestion (PLC + vision + vibration + power) with time alignment and rule-based interpretation, plus an extension point for custom ML models per asset — designed for brownfield plants where pure PLC OEE leaves loss invisible.

See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.

Related reading

Frequently asked questions

Do I need sensor fusion if my PLCs are new?

Less so. Modern PLCs expose enough for solid OEE. Sensor fusion most pays off on older equipment or visually-driven processes.

What is the cheapest sensor to add?

Usually vision (a USB camera or industrial cam plus inference). Catches micro-stops and visual defects at low cost.

Does sensor fusion require AI?

Not necessarily. Many fusion rules are simple logic. AI is useful for visual defect detection or vibration anomaly classification.

How much data does vibration generate?

At sampling rates of 10 kHz+, several MB per hour per sensor. Plan storage and processing accordingly.

Is sensor fusion the same as IIoT?

Related but not the same. IIoT is the connectivity layer. Sensor fusion is what you do with the data — combining multiple sources into useful signals.

Das Neueste aus unserem Blog

Definieren Sie Ihren Zuverlässigkeitsfahrplan
Überzeugen Sie sich selbst!
Definieren Sie Ihren Zuverlässigkeitsfahrplan
Indem Sie auf die Schaltfläche „Akzeptieren“ klicken, erklären Sie sich mit der Nutzung einverstanden.Cookies beim Zugriff auf diese Website und bei der Nutzung unserer Dienste. Erfahren Sie mehrWeitere Informationen zur Verwendung und Verwaltung von Cookies finden Sie in unserem Datenschutzrichtlinie und Cookie-Erklärung