You can get OEE data from an old machine without opening its controller. A clamp-on current sensor gives run state, and a proximity or photo sensor counts parts. Add a reject count and you have availability, performance and quality. Join the signals, because a motor can run with no output.
When you need a retrofit
Many machines can give you OEE data on day one. Some cannot. A retrofit is the answer when:
- The machine is old and has no controller output you can read.
- The controller is closed or the vendor will not open it.
- You do not want anyone to touch the control logic, for good reason.
- You want a quick pilot before you spend on integration.
The idea is simple. Instead of asking the machine for its state, you watch it from outside.
Two sensors are enough to start: one for run state, one for parts.
Which sensor for which signal
| Signal | Sensor | How it works | Watch out for |
|---|---|---|---|
| Run state | Clamp-on current sensor on the main motor cable | Current above an idle level means the machine is working | A machine can draw current while making nothing |
| Run state | Light sensor on a stack light | Green, amber or red maps to a state | Lights show the operator's view, not always the truth |
| Part count | Inductive proximity sensor | Pulses when a metal part or cam passes | Needs metal and a stable gap |
| Part count | Photoelectric sensor | Beam is cut by a package or bottle | Dust, glare and gaps in the product stream |
| Reject count | Second sensor at the reject chute | Counts what leaves the line as waste | Count each part once |
| Speed or cycle | Pulses per minute from the count sensor | Gives cycle time without extra hardware | Averages hide slow cycles |
| Run state on a quiet machine | Vibration sensor | Motion above a level means the machine is on | Needs a test on each machine type |
The current sensor and the part sensor are the core pair. They are quick to fit and can be clamped or mounted without cutting a wire.
Opening an electrical cabinet to place a clamp is still a job for a qualified electrician. For the signals a PLC can give you instead, see PLC signals for OEE.
Example: an old press line with two sensors
Example: a press has no network port. A current sensor sits on the main motor cable, and a proximity sensor counts strokes.
Idle current is 2 A, working current is 11 A. The team sets the "running" threshold at 5 A, held for 10 seconds, so a brief spike does not count.
A reject sensor at the chute counts bad parts. The ideal rate is 60 strokes a minute (a 1.0 second cycle). Here is one 480-minute shift:
| Measured by sensors | Value |
|---|---|
| Scheduled time | 480 min |
| Run time (current above 5 A and strokes counted) | 372 min |
| Strokes counted | 20,800 |
| Rejects counted | 416 |
| Good parts | 20,384 |
Performance = 20,800 / (372 x 60) = 93.2%
Quality = 20,384 / 20,800 = 98.0%
OEE = 77.5% x 93.2% x 98.0% = 70.8%
Check: (20,384 / 60) / 480 = 70.8%
The method follows Overall Equipment Effectiveness (R. C. Hansen, 2001). For the steps in more detail, see how to calculate OEE.
The trap: current is not output
A motor that spins with no product still draws current. If you use current alone, a press that runs empty for 20 minutes counts as running.
That hides a real loss.
The fix is a rule that joins both signals. Treat the machine as running only when current is high and a part has been counted in the last N seconds.
If current is high and nothing is counted, log it as a stop with the cause to be added, for example "starved".
How to fit sensors safely
Decide what you must know: run, count, reject. Do not buy sensors before you know this.
Clamp-on current sensors and bracket-mounted proximity or photo sensors do not alter the machine.
Never tap an emergency stop or guard interlock. Let a qualified electrician do any wiring.
Record idle and working values, then set the threshold between them with a margin.
Watch one hour. Compare the sensor count with a hand count. Fix gaps before trusting the data.
Getting the signal out
The sensors need a small gateway that reads them and sends the data on. Check three things before you buy one:
- It keeps data when the network drops. A gap in the log looks like a long stop.
- The clock is right. Every record needs a correct time stamp, or shifts will not match.
- It reads often enough. To catch a stop of a few seconds, the gateway must see each change, not a minute average.
Wired links are the safe default on a noisy floor with motors and drives. Wireless can work, but test it where the machine sits, close to steel and cabinets.
Common mistakes
- Counting at the wrong place. Count good output at the end of the machine, not at the infeed.
- Double counts. A part that passes the sensor twice, or a sensor that bounces, doubles the count. Test with a known batch.
- A threshold that is too low. A cooling fan can fool a current clamp. Test on the real machine.
- No cause for stops. A sensor sees that the machine stopped, not why. Add an operator choice. See how to track downtime.
- Ignoring dirt. Photoelectric sensors need cleaning. Put it in the daily check.
For a wider view of data options, see OEE data collection methods. If the cause matters more than the count, look at computer vision for OEE. For problem sensors, see proximity sensor troubleshooting and photo-eye troubleshooting.
Fabrico reads stops, speed and counts live from PLCs or from IoT sensors, which are external sensors on older machines, so a machine with no output can still join your OEE view. See how Fabrico connects older machines.
What people ask next
How many sensors do I need per machine?
Two to start: one for run state and one for the part count. Add a third for rejects if you want quality from the sensors. Anything else can come later.
Do I have to stop the machine to fit them?
Clamp-on current sensors and bracket-mounted proximity or photo sensors usually need little or no stop time. Wiring a power supply may need a short stop and a qualified electrician.
Can a sensor tell me why the machine stopped?
No. It tells you that it stopped and for how long. The cause comes from an operator choice or a camera. See downtime reason codes.
What if the machine runs at different speeds?
The count sensor still counts parts, so speed follows from counts per minute. Set the ideal rate per product. See ideal cycle time.
Is a retrofit as good as a PLC signal?
For run state and counts it can be, once you have tested it against a hand count. A PLC can give more, such as fault codes and mode. See PLC signals for OEE.
Related guides: Stack Light Monitoring: Downtime From Tower Lights · Sensor Fault Stops: Find and Fix False Trips · IIoT Gateway: What It Does and When You Need One · MES PLC Integration: Routes, Tag List and Tests