OEE on Legacy Machines Without PLCs: Sensors, Cameras, Retrofits

Many manufacturers want reliable, real time OEE across the plant, but a large part of their asset base has no PLCs, no native connectivity and sometimes no digital signals at all.

These legacy machines are often where the biggest losses hide, yet they are the hardest to monitor. The question is not if you can measure OEE on them, but how to do it in a way that is accurate, sustainable and scalable.

This article explains the practical options for capturing OEE from legacy equipment using sensors, cameras and retrofit kits, and what MES and OEE buyers should watch for when selecting a solution. It focuses on plants that want to move beyond manual spreadsheets into an integrated machine monitoring system where OEE, losses and actions are connected.

Fabrico is a cloud based MES and OEE platform with built in maintenance management. It collects production and downtime data directly from machines, calculates OEE in real time and turns each loss into structured maintenance and production actions that can be tracked to completion.

What You Actually Need To Measure For OEE

Before talking about sensors and cameras, it is worth clarifying what signals you really need. For OEE, at minimum, you need:

• Run / stop status to know when the machine is producing or not
• Speed / cycle count to know how many units are produced, or how many cycles run
• Good vs scrap to separate quality losses from performance and availability losses

On modern machines, a PLC or controller can often provide these signals over an industrial protocol. On legacy machines without PLCs, you must create these signals with external hardware, then feed them into an MES and OEE platform like Fabrico.

Option 1: Simple Sensors On Legacy Machines

For many older machines, the most robust approach is also the simplest: add discrete sensors that create clean digital signals which represent the machine state.

Typical sensor types

• Proximity or inductive sensors that count each part or cycle by detecting motion of a cam, shaft, wheel or mechanical part
• Photoelectric sensors that see a passing part or detect presence / absence at a checkpoint
• Current transformers or power sensors that detect when the motor is drawing current, often used as a proxy for run / stop
• Limit switches that detect end of stroke or certain positions in mechanical presses or forming lines

These sensors are wired into an I/O module or small edge device. The device timestamps and counts events, then sends them to the cloud. Fabrico ingests these signals, correlates them with shift schedules and orders, and calculates OEE in real time.

For more context on how this fits into an overall strategy, see how IoT and machine data can drive OEE improvement in this article: Fabrico: Driving OEE Excellence Through IoT and Smart Manufacturing.

What works well with simple sensors

• Machines with a clear, repetitive motion that maps cleanly to one part or cycle per movement
• Lines where a single sensor can count good units leaving the cell
• Equipment where a power signal is a reliable indicator of run vs idle

Pitfalls to avoid

• Counting the wrong motion: If one cycle of the sensor is not equal to one part, your performance numbers will be wrong. Clarify exactly what a count represents and configure the MES accordingly.
• Missing micro stoppages: If the sensor is on a slow moving part of the mechanism, brief stoppages might be invisible. Place sensors where they reflect true machine state with minimal delay.
• Signal quality problems: Electrical noise, loose mounting or poor alignment can cause double counts or missed counts. Ensure proper installation standards and validation tests.

In Fabrico, once the sensor data is stable, OEE is calculated automatically and losses are classified as availability, performance or quality. The built in maintenance management can then convert recurring downtime reasons into work orders and inspections, so the data leads to corrective action, not just dashboards.

Request a demo

Option 2: Cameras And Computer Vision

Cameras and basic computer vision can provide machine signals where physical sensors are impractical. Examples:

• Counting parts on a conveyor when mounting a sensor is difficult
• Reading stack height or bin fill to estimate throughput
• Detecting machine state by monitoring indicator lights or HMI screens

A camera stream can be processed at the edge or in the cloud to produce digital events: part passed, light is green, alarm is active and so on. These events are then fed into your MES and OEE system.

When cameras make sense

• Highly flexible lines with frequent changeovers where fixed sensors would need constant repositioning
• Legacy machines with no easy mechanical sensing point but clear visual indicators of operation
• Situations where quality characteristics can be detected visually at the same time as counting parts

What to watch out for with cameras

• Lighting and environment sensitivity: Changing ambient light, dust, glare and vibration can affect accuracy. You need stable mounting and some control of environmental conditions.
• Maintenance overhead: Lenses need cleaning, and camera positions can drift. Someone must own this.
• Complexity vs benefit: For simple run / stop or counting, a sensor is often simpler and more reliable than a camera.

Cameras become more compelling if you want to combine OEE measurement with automated visual inspection. Then one device both measures output and flags defects. Fabrico can ingest events from vision systems alongside other sensor data, aligning all of it with OEE and downtime analysis.

Option 3: Retrofit Kits And Edge Gateways

Between simple sensors and full control system upgrades, many plants adopt retrofit kits or edge gateways. These devices gather signals from multiple sources and provide a structured interface to your MES.

A typical retrofit on a legacy machine might include:

• A small I/O module that reads sensors and pushbuttons
• A simple operator panel or tablet for downtime and scrap reasons
• A gateway that sends data to the cloud over Ethernet or Wi Fi

Some machines can also expose partial data via analog signals or old fieldbuses. The edge gateway normalizes these signals into a clean data model for the MES.

Benefits of retrofit kits

• Standardized hardware and wiring patterns across similar legacy machines
• Faster rollout compared with designing each connection from scratch
• Secure, one way connectivity from the machine area to your cloud MES and OEE platform

Selection criteria for buyers

• Compatibility with your MES: Ensure the retrofit or gateway speaks modern protocols or APIs so that data flows cleanly into your OEE and OEE tracking dashboards.
• Support for hybrid input: You likely need both automatic signals and manual inputs for reasons and scrap. Confirm the kit supports operator terminals or integrates with tablets.
• Security and manageability: Look for remote configuration, versioning and secure connectivity so your OT and IT teams can own the solution at scale.

Fabrico typically consumes data from sensors and retrofit gateways using lightweight, secure protocols. It maps inputs into a standard data model, so legacy and modern machines appear side by side in OEE views, downtime analyses and maintenance backlogs.

Request a demo

Where Manual Input Still Matters

On most legacy machines, you will not get a pure, fully automatic data stream. Some information still needs human input, especially:

• Downtime reasons that sensors cannot distinguish, for example changeover vs material shortage
• Scrap reasons or defect codes
• Setup confirmation and shift level comments

A practical model is:

• Automatic: run / stop, cycle counts, basic alarms
• Manual: reason codes, scrap categorization, comments

This hybrid approach keeps operators involved where their context is essential, while letting the automation handle high volume event capture. In Fabrico, operators can enter reasons and scrap codes on simple, guided screens directly linked to the real time machine timeline. This keeps data entry quick and improves the quality of OEE analytics.

Data Quality: What To Check Before Scaling Up

MES and OEE buyers often underestimate the effort to validate data quality on legacy equipment. Before rolling out across the plant, consider a pilot that focuses explicitly on:

• Count accuracy: Compare sensor or vision counts with manual tallies over several runs.
• State transitions: Verify that start and stop events line up with reality when observed on the shop floor.
• Reason capture discipline: Check that operators consistently select appropriate downtime and scrap codes.
• Time synchronization: Ensure device clocks and MES timestamps are aligned, or that the platform corrects for drift.

Only when these are stable should you rely on OEE numbers for decision making. Fabrico helps here by giving you a detailed event timeline. You can drill into questionable periods, compare with shift logs and quickly identify measurement issues before expanding to more machines.

Request a demo

From Data To Action On Legacy Machines

Once OEE is reliably measured on legacy equipment, the real value comes from acting on the losses. For typical plants, this means:

• Targeting chronic, short stoppages that were previously invisible
• Reducing slow cycles and minor speed losses on older machines
• Linking frequent breakdowns on specific legacy assets to maintenance plans

Because Fabrico includes maintenance management as part of the same platform, patterns in downtime can be directly translated into maintenance tasks, inspections and improvement actions. For example:

• A recurring micro stoppage on a legacy press can become a standard lubrication task at a defined interval.
• A chronic speed loss on an old filler can trigger a focused engineering study with clear before and after OEE data.

Over time, this creates a structured improvement pipeline for legacy assets. Plant managers and heads of maintenance see not only current OEE but also which actions are underway and how they affect availability, performance and quality.

How To Prioritize Legacy Machines For OEE Rollout

Budget and time rarely allow you to retrofit every legacy machine at once. A practical prioritization approach is:

1. Value at stake: Start with machines that constrain throughput or produce high value products.
2. Feasibility: Choose equipment where sensors or retrofit kits can be installed quickly and safely.
3. Influence: Include at least one line where engaged supervisors and operators will champion the change.

This staged rollout lets you prove the approach, refine your standards for sensors and gateways, and show tangible improvement. You can find more context on how machine data supports continuous improvement and OEE programs here: Machine Monitoring System: From Data To Decisions.

Request a demo

Buyer Checklist: Evaluating MES And OEE For Legacy Machines

When you evaluate MES and OEE vendors for plants with many non PLC legacy machines, consider questions like:

• Can the platform ingest data from simple sensors, cameras and retrofit gateways without custom engineering each time
• Does the vendor provide clear guidance on sensor placement, signal mapping and validation, or will your team have to design everything
• How are manual inputs for downtime and scrap integrated with automatic data in the UI
• Can you see an event level machine timeline to debug data quality issues
• Is maintenance management integrated so that recurring losses on legacy machines convert into tasks and improvements
• What is the rollout path from a few assets to a plant wide or multi site deployment

Fabrico is designed for exactly this scenario. It connects to both modern and legacy machines, calculates OEE and losses in real time and turns loss patterns into concrete production and maintenance actions that can be tracked. This gives plant managers and operations leaders a unified view across their full asset base, not just the newest equipment.

Next Steps

If you are planning OEE on legacy machines without PLCs, the key is to:

• Choose the right mix of sensors, cameras and retrofit kits per asset
• Validate data quality early
• Ensure your MES and OEE platform can turn that data into actions, not just charts

To explore how Fabrico can support your legacy and modern machines in one environment, including real time OEE, actionable losses and integrated maintenance, you can Request a demo or Contact us.