Measure OEE in real time: Identify stoppages and losses immediately
When machine stoppages become apparent only in the daily report or weekly meeting, the loss has already occurred. Production managers need up-to-date data on which plants are running, where orders are stalled, and why productivity is lost.
OEE only becomes a true control metric when machine states, feedback, scrap, cycle times, and order data are brought together. It is this transparency that provides the basis for detecting stoppages faster, reducing losses more precisely, and driving data-based continuous improvement on the shop floor.
The problem: Why OEE in many manufacturing facilities only becomes visible when it's too late
In many manufacturing companies, OEE is theoretically known but difficult to use in practice. The metric is meant to show how effectively machines and equipment are actually functioning. For this, it considers availability, performance, and quality. But these three dimensions depend on data that in day-to-day operations are often not complete, not up-to-date, or not in the right context.
The problem usually doesn't start with the formula. It starts with the data foundation.
A machine is idle, but the downtime is reported only later. A job runs slower than planned, but the deviation is only visible after the end of the shift. Scrap occurs, but the cause remains unclear. Setup times take longer than planned, but they are not cleanly separated from the production run. Production progress is reported back manually, sometimes delayed, sometimes incomplete.
As long as this information is time-delayed, manual, or in separate systems, OEE remains a retrospective analysis. For manufacturing managers, that's too late. Anyone who detects downtime, performance losses, and quality deviations only days later cannot manage them in real time. Then OEE becomes a reporting metric, but not an instrument for better decisions.
The gap is especially critical in medium-sized manufacturing companies. Machines, orders, materials, staff and deadlines are tightly interconnected. If a piece of equipment fails unexpectedly or runs slower, it affects not only that machine. It affects delivery dates, capacity planning, material flow, rework, costs and customer commitments.
The real challenge, therefore, is this: manufacturing companies must not only know how high their OEE was but also understand why losses occur, where they are currently occurring, and what impact they have on ongoing orders.
Typical warning signs in daily operations
Missing OEE transparency rarely appears as a single large disruption. More often the problem arises in day-to-day operations through many small uncertainties. Teams notice that something isn't running smoothly, but the causes are hard to grasp.
A typical signal is that the shop floor and the planning have different pictures of reality. In the ERP, an order is planned; on paper the machine runs, but in production there were setup delays, stoppages or quality problems. The feedback comes late or not detailed enough. This creates a gap between plan and reality.
Typical warning signs are:
- Machine stoppages become visible only after the shift ends or in the daily report.
- Production managers do not immediately know which line/machine is currently down or why.
- Downtime reasons are recorded manually, incompletely, or not at all.
- OEE is calculated in Excel but not monitored continuously.
- Scrap and rework are documented but not cleanly linked to the order, machine, or cause.
- Production progress is only reported back to the ERP with a delay.
- Teams discuss causes instead of accessing reliable data.
- Continuous improvement measures are based on experience rather than real-time data.
- Machine run times, setup times, and downtime cannot be clearly separated.
- It is unclear which losses affect availability, performance, or quality the most.
Particularly critical is when these symptoms are accepted as normal manufacturing reality. Then a culture of reacting develops: problems are corrected as soon as they are visible, but not systematically prevented. OEE remains backward-looking, rather than enabling operational control.
Causes: Why downtimes and losses often remain undetected for days
OEE problems arise not only from technical disturbances. Often the cause lies in a lack of integration between shop floor, machines, BDE, MES and ERP.
Machine data remain isolated
Many machines provide data, but this data is not automatically linked to orders, operations or ERP information. A machine can report that it is running or stopped, but without context it remains unclear which order is affected, what the standard time is, what quantity was expected, or whether scrap occurred.
Machine data alone therefore answer only part of the question. For OEE you need the connection between machine, order, time, quantity and quality.
Operational data are collected too late or manually
If feedback is collected only at the end of a shift and entered afterwards, the data basis for real-time OEE is weak. Downtime, setup times, good units, scrap and rework are thus documented retrospectively, but not visible at the moment they occur.
Reasons for downtime are not captured in a structured way
For OEE it's not enough to know that a machine was down. What matters is why it was down. Was it a technical defect, missing material, setup, operator shortage, quality inspection, tool change or an external disruption?
Without structured downtime reasons, losses are hard to prioritize. The manufacturing sees that OEE is low, but not whether availability, performance or quality is the biggest lever.
ERP and shop floor do not speak the same language
The ERP knows orders, operations, articles, target times, deadlines and costs. The shop floor knows machine states, run times, disruptions, quantities, scrap and actual sequences. If these levels are not integrated, two separate truths arise.
This means OEE can be visible at the machine level but not cleanly traced back to orders, articles, shifts or cost centers. For continuous improvement this is problematic, because improvement measures without context quickly remain imprecise.
Continuous improvement gets decoupled from day-to-day operations
Continuous improvement only works when improvement measures are based on robust data. But if OEE is calculated only with a delay or manually, the proximity to the actual problem is missing. Teams then discuss past values instead of eliminating current root causes.
Continuous improvement requires recurring patterns: Which machine is often down? Which orders cause especially a lot of rework? Which setup processes take longer than planned? Which shift loses performance? Which items lead to scrap? Without a consistent data basis, these questions are hard to answer.
Impact: What missing real-time OEE does to production, revenue, and profit
Missing OEE transparency affects not only machine metrics. It influences the overall performance of manufacturing.
Unplanned Downtimes stay invisible for too long
If downtimes are not detected immediately, no one can respond in time. A plant is down, but escalation occurs only later. As a result, productive minutes or hours are lost without countermeasures being initiated.
This is especially critical for bottleneck machines. When a central plant fails, downstream processes, assembly, shipping, and delivery dates shift. The later the downtime becomes visible, the harder it is to correct it.
Production plans lose their reliability
Planning is based on assumptions about available capacity, run times and feedback. If the actual machine performance does not feed back in real time, the company plans with outdated data. Schedules appear stable in the system, even though production is already deviating.
Without real-time feedback from production, even the best planning quickly becomes obsolete. For this reason, shop-floor data capture at Abas is standard.
Costs arise, without becoming visible
Downtimes, setup losses, speed losses, scrap and rework cause costs. If these losses are not properly recorded and allocated, they remain unclear in controlling. The company may see a worse margin, but not know exactly where it originated.
This also weakens post-calculation. If actual times, scrap quantities and causes are not reliably captured, future offers, work plans, or target times are hard to improve.
KVP loses its effectiveness
KVP relies on problems being measurable, comparable and prioritizable. If data foundations are missing, improvement projects are often started by gut feeling. That may work, but rarely leads to systematic improvement.
Real-time data, by contrast, allows patterns to be identified: recurring downtimes, frequent quality problems, overly long setup processes, bottleneck machines, or deviations between target and actual. Only then does continuous improvement become concretely steerable.
Delivery dates and customer commitments come under pressure
If downtimes and performance losses become visible too late, delivery dates are also adjusted too late. Sales and customer service learn only with delay that an order is at risk. This reduces responsiveness to customers.
Therefore, manufacturing managers need not only an OEE metric. They need the link to orders, operations and delivery dates. Only then can one determine which disruption is truly critical.
What Real-Time OEE Must Deliver
Measuring OEE in real time does not mean simply adding another metric to a dashboard. What matters is that the metric becomes explainable and actionable.
Make Machine States Visible in Real Time
Production managers must be able to see at a glance which machines are running, which are idle, which are in setup, and where disruptions are occurring. A pure status display is not sufficient. The status must be linked to order, operation and cause.
Capture Feedback Directly at the Point of Origin
Data should originate where the work happens: on the shop floor. This includes feedback on processing times, quantities, rejects, rework, downtimes and material consumption.
The digitization of manufacturing through a modern BDE enables workers to work process-oriented via the work-in-progress list and to directly report activities such as setup, material withdrawals, good quantities, scrap or rework.
Connect OEE with Order Data
An OEE evaluation is significantly more valuable if it can be analyzed not only per machine but also per order, item, shift or operation. Only then does it become visible which products, processes or orders cause particularly many losses.
MDE-/OEE software with ERP integration: By linking machine data from production and order data from the ERP, productivity becomes detailed per order, item and shift.
Separate Losses by Cause
OEE consists of availability, performance and quality. Therefore a system must support clean separation of losses: downtime, reduced speed, scrap, rework, setup time or organizational disruption.
Only when these causes are shown separately can the company take targeted countermeasures. Otherwise OEE remains a number without clear course of action.
Deriving Continuous Improvement (KVP) Directly from the Data
Real-time OEE should not end with monitoring. The data must enable improvements. That means: identify trends, make deviations visible, analyze causes and prioritize actions.
With suitable software support, data can be collected systematically and used for precise analyses. This quickly shows where processes are not running as planned, so that, based on shop-floor data capture, targeted efficiency-boosting measures can be initiated.
The Solution: How Abas and Prodaso Support Companies with Real-Time OEE
To sustainably improve overall equipment effectiveness (OEE), shop floor and commercial processes must work together seamlessly. This is precisely where the combination of ABAS ERP and Prodaso comes in: while ABAS maps the complete ERP-, manufacturing-, BDE-, and process side, Prodaso acts as an intelligent Production Intelligence component for machine data, IoT and live dashboards. The result is a seamless data chain where OEE values are created and analyzed exactly where shop floor and ERP meet.
Integrated BDE as the data basis for production
With the ABAS BDE, operating data is recorded directly in the ERP context. Through the digital work-inventory list, workers can view additional information such as drawings or work instructions and immediately report a wide range of activities. These include the setup at the machine, material withdrawals, partial and final confirmations of good quantities, rejects and rework, as well as reporting and ending machine downtimes. This creates an immediate link between the manufacturing reality and the ERP data base — an essential prerequisite to evaluate downtime and losses directly in the context of the order.
Real-time shop-floor feedback
The Abas shop-floor application makes the work-inventory list available flexibly on touch terminals or mobile devices. Workers are clearly informed about upcoming steps and enter their feedback in real time, which is immediately automatically processed into BDE data. The key advantage: deviations and downtimes are visible at the exact moment and are not hidden until the next daily report.
Machine integration with Abas Connect
To ensure the continuous digitization of the value chain, the integration tool Abas Connect ensures smooth data flow to and from the machines and enables tailor-made plant couplings. This allows machine data to be integrated directly into the ERP system's deep process landscape.
Prodaso for OEE, machine status and live dashboards
To maximize transparency and automatic machine data capture (MDE), Prodaso's real-time integration with ABAS ERP ensures the complete production networking makes it possible to map metrics in 24/7 live dashboards. Machine status, downtimes, order progress, OEE and other KPIs are available in real time and form the ideal basis for data-driven optimizations directly in production.
Real-time synchronization between ERP and shop floor
The Abas-Prodaso Connector guarantees continuous real-time data exchange between the two systems, so that production and ERP data are always synchronized. Among other things, manufacturing orders, operations, machines, operators, items, scrap reasons, as well as MDE and BDE feedback are reconciled. This deep integration builds the professional bridge between OEE and ERP: Overall equipment effectiveness is not viewed in isolation but is inextricably linked to the respective order, the machine, the concrete machine state and the feedback.
Planning and production control with current feedback data
The real-time data obtained are not only essential for OEE, but also drive the entire planning and control. Advanced Planning and Scheduling (APS) visualizes production workloads, identifies bottlenecks and optimizes sequences. In parallel, the production hub serves as a central control cockpit. Here, production proposals and production orders can be monitored to immediately identify and resolve issues such as missing parts, bottlenecks, or unbooked BDE records — for more efficient processes and consistently high delivery capability.
Practical relevance: When production managers finally see what is really happening
Franz Kunststoff: Better understand the productivity of individual machines
At Franz Kunststoff, production planning, master data, and shop floor feedback are integrated and linked with abas. The company aimed primarily to gain more reliability in planning and to make the productivity of individual machines more transparent. By combining abas with Production Intelligence, the exact transparency needed for well-founded decisions in daily production is available.
We want to know exactly how productive each machine is.
Deharde: Real-time capture of material and machine data
At Deharde, digital production data capture with abas provides significantly more transparency in production. Employees can report work steps directly and capture material and machine data in real time. As a result, workflows become immediately visible, and those responsible for production always have an up-to-date overview of their processes.
“Every movement in the system is immediately visible; that's a great advantage.”
These case studies show how companies use production data in real time with abas to create transparency and to identify downtimes, losses, and optimization potential more quickly.
Discover more practical examples: Learn how manufacturing companies use abas ERP, shop floor data, and Production Intelligence to run their production more transparently, make better-informed decisions, and identify potentials early.
Advantages at a glance: What real-time OEE improves in manufacturing
| Everyday challenges | What real-time OEE enables |
|---|---|
| Everyday challenges Machine downtime is detected too late | What real-time OEE enables Downtime and machine status are currently visible |
| Everyday challenges OEE is calculated manually in Excel | What real-time OEE enables Key metrics are available more quickly via live dashboards |
| Everyday challenges Causes of downtime are unclear | What real-time OEE enables Causes can be captured and analyzed more systematically |
| Everyday challenges Shop floor and ERP provide different pictures | What real-time OEE enables Machine-, production-, and order data are linked |
| Everyday challenges Continuous improvement process (KVP) is based on gut feeling | What real-time OEE enables Improvements can be prioritized more data-driven |
| Everyday challenges Production plans become outdated | What real-time OEE enables Feedback from production flows back faster |
| Everyday challenges Scrap and rework remain hard to explain | What real-time OEE enables Quality losses can be linked more effectively to order and its cause |
| Everyday challenges Production managers see problems only in hindsight | What real-time OEE enables Deviations become detectable earlier and controllable operationally |
The most important advantage does not lie in a single KPI. The value arises from the interconnection: machine status, order, quantity, time, quality, and cause are viewed together. This turns OEE from a retrospective KPI into a management tool for the ongoing production.
Conclusion: OEE is only as good as the data behind it
OEE can help manufacturing companies better understand productivity, availability and quality. But for that the KPI must be based on robust, current and contextual data. If downtimes, setup times, rejects or production progress are only recorded later or manually, OEE remains a backward-looking metric.
For production managers, that is not enough. They need to see what is happening now: Which machine is running? Which order is affected? Why is the loss occurring? What impact does the disruption have on deadlines, capacity and on-time delivery?
That is precisely why the integration of ERP, BDE, shop floor, machine connectivity and MES or Production Intelligence is so important. Abas ERP provides the ERP, manufacturing and BDE base for this. With shop floor feedback, Abas Connect and the combination of Abas + Prodaso, production data, machine data, OEE, downtimes and order information can be brought together more effectively.
Thus OEE becomes more than just reporting. It creates an operational basis to detect downtimes faster, to reduce losses more precisely, and to support continuous improvement on real production data.
Abas & Prodaso: Detecting downtime before it slows down your productivity
When machine stoppages, performance losses and scrap only become visible in hindsight, you lose valuable time. With Abas ERP, integrated production data capture, shop floor data and Production Intelligence, you create the foundation to understand OEE and production metrics in real time.
See how Abas and Prodaso make machine status, downtimes, order progress, OEE and other KPIs transparent and connect ERP data with the reality on the shop floor
What does OEE stand for in manufacturing?
OEE stands for Overall Equipment Effectiveness, in German: Gesamtanlageneffektivität. The metric considers how effectively machines or plants are used. Typically, the basis is availability, performance, and quality. However, what matters is not only the calculation, but the quality of the data on which OEE is based.
Why is real-time OEE more important than a daily or weekly report?
Daily or weekly reports only show losses in hindsight. For operational decisions, that's often too late. Real-time OEE helps manufacturing managers detect downtime, performance losses, and quality issues more quickly, while there is still time to react.
Why do machine downtimes remain undetected in many companies?
Downtime often remains undetected when machine states are not automatically captured, the reasons for downtime are not documented in a structured manner, or feedback is only transferred to the ERP after the end of the shift. Disconnected systems between the shop floor, BDE, MES and ERP also lead to information being delayed or incomplete.
What data is needed to measure OEE meaningfully?
For a robust OEE evaluation, data on machine run times, downtimes, setup times, production quantities, good quantities, scrap, rework, orders, operations, and causes are needed. OEE becomes particularly valuable when this data is linked with ERP information such as order, item, planned time, and delivery date.
What is the difference between BDE, MDE, and MES?
BDE stands for production data collection and encompasses feedback from production, such as times, quantities, scrap, or activities.
MDE stands for machine data collection and relates more to automatic data from machines and equipment.
An MES is a Manufacturing Execution System and serves the operational planning, control, monitoring and documentation of manufacturing processes at the shop floor level.
MES System: MES is a software solution that plans, controls, monitors and documents manufacturing processes in real time.
How does an ERP system help with OEE?
An ERP system provides the business and order-related context: orders, items, operations, standard times, deadlines, materials and costs. OEE becomes more valuable when machine data and operating data are linked to this context. This makes it possible not only to see that a machine is down, but also which order was affected and what impact arises.
How does Abas ERP support BDE and machine downtimes?
With the BDE in Abas ERP, all relevant manufacturing steps can be reported back precisely—from setup and material withdrawal to good quantities, scrap, and rework. In addition, employees can interrupt ongoing activities at any time, and machine downtimes can be recorded and ended flexibly.
How does ABAS + Prodaso support real-time OEE?
With Prodaso and Abas ERP you benefit from 24/7 live dashboards that transparently visualize the machine status, downtime, order progress, OEE and other KPIs in real time. Through automatic machine data capture and seamless real-time integration, MDE, BDE, IoT, APS and the ERP system merge into a seamlessly connected production unit.
Why is OEE important for CIP?
KVP needs a robust data foundation. Only when downtime, losses of output, and quality problems are accurately recorded and analyzed by their root causes can improvement measures be sensibly prioritized. Without up-to-date data, KVP is often driven by experience rather than by data.
What is the first step to make OEE measurable in real time?
The first step is to analyze the current data basis: Which machine states are captured? What feedback arises on the shop floor? When do data flow back into the ERP? Are downtime reasons documented in a structured way? Only when this foundation is clear can one decide whether BDE, MDE, MES integration, or a solution like Abas + Prodaso is the appropriate next step.