The line ran the whole shift, yet output fell short. Where did the time go: stoppages, slow running or rejects? OEE (Overall Equipment Effectiveness) splits the loss into three parts, and each part tells you what to tackle.
What is OEE?
OEE is the product of three factors:
OEE = availability × performance × quality
- Availability
- Run time divided by planned production time. Stoppages, breakdowns and changeovers reduce it.
- Performance
- The quantity produced divided by the quantity the run time would have produced at the ideal rate. Slow running and short stops reduce it.
- Quality
- Good units divided by all units produced. Rejects and rework reduce it.
A worked example
Take an eight-hour shift with an ideal rate of one unit a minute:
| Planned production time | 480 min |
|---|---|
| Run time | 420 min → availability 87.5 % |
| Produced | 380 units, 420 at the ideal rate → performance 90.5 % |
| Good | 370 units → quality 97.4 % |
| OEE | 87.5 % × 90.5 % × 97.4 % ≈ 77 % |
The same result comes out directly: good units times the ideal cycle time divided by the planned time, that is 370 × 1 min / 480 min ≈ 77 %. This form is useful because it needs only three figures.
What data does OEE need?
- Planned production time: shifts, breaks and planned maintenance. This often lives in the shift plan, not in the automation system.
- Run state or run time: the PLC's running/stopped signal or a run-hours counter.
- Unit count: the PLC's unit counter.
- Good or rejected: a separate counter for good or rejected units.
- Ideal rate: the product's nominal rate, which may vary by product.
- Stoppage reasons: why the line stopped. Without them OEE tells you that time was lost, but not where.
The factors of OEE with DataPortia
DataPortia™ has no ready-made OEE function. An OEE feature is in development: availability and production reporting first, then OEE. This article describes what can be done today. The factors of OEE can still be calculated when the automation system provides the signals they need. This section shows how.
DataPortia reads the signals from the PLC's or the control room's OPC UA server and stores them as time series. The factors are calculated with calculation points, that is formulas evaluated separately for every period of a report:
| Figure | Inputs | Formula |
|---|---|---|
| Quality, % | IN1 good (counter), IN2 total (counter) | IN1 / IN2 * 100 |
| Share of time running, % | IN1 run state 0/1 (instantaneous) | IN1 * 100 |
| Performance, % | IN1 units (counter), IN2 run hours (counter), ideal rate 60 units/h | IN1 / (IN2 * 60) * 100 |
| OEE, % | IN1 good (counter), IN2 planned hours (counter), ideal rate 60 units/h | IN1 / (IN2 * 60) * 100 |
The practical limits are worth knowing in advance:
- One kind per formula. A calculation point treats all its inputs the same way, either as counters (the change in the period) or as instantaneous values (the period's average). Performance and OEE therefore need run time or planned time as a counter. If the PLC has only a running/stopped signal, you get the share of time running, but performance is then calculated, for example, from the Excel export, or a run-hours counter is added to the PLC.
- The ideal rate is a constant in the formula. With many products at different rates, one constant is not enough.
- Planned time is not in the automation system. Shifts and breaks usually live in the shift plan. If the planned time is the whole period, the share of time running equals availability.
- The saving interval limits the resolution. A stop shorter than the saving interval may not show in the run state.
- A steadily rising counter is the safest. Prefer a counter that only rises over one that is reset at every shift change.
Stoppage reasons from alarm history
DataPortia does not record stoppage reasons in OEE loss categories. The alarm history still tells a lot: a Pareto analysis shows which alarms become active most often, and a duration analysis which stay active longest. A short disturbance can recur dozens of times in a shift and still take less time than one long stop. Both show up when alarms are stored with the timestamp the automation gave them. The method is covered in Root cause analysis from alarm history.
Production monitoring and reporting
The same signals give you production monitoring even without an OEE figure: unit counts, run times and consumptions per hour or per day in trends, on dashboards and in scheduled reports. A daily production report is scheduled, and a single shift is fetched in the report view. Reporting is covered on the automated reports page.
Try DataPortia for 30 days with your own line's signals: the trial includes every feature except the HA add-on and commits you to nothing. A week of data shows whether the PLC's signals are enough for the factors.