Real-time OEE or a post-shift report? Reduce production losses
Real-time OEE helps you respond while the loss is still occurring. The post-shift OEE report, on the other hand, is used to identify the cause of the loss, compare incidents, and verify whether the actions taken were effective. In this article, you’ll learn which view should be shared with the operator, shift leader, and production manager, and how to assess whether the data is arriving on time.
In short: the OEE dashboard supports decisions made in a matter of minutes. The OEE report supports decisions made after a shift, on a weekly or monthly basis. A company needs both if it wants to reduce current losses and prevent them from recurring.
The response window determines the value of the data
The response window is the period during which information can still affect the outcome of ongoing production. It ends when the stoppage is resolved, the defective batch is allowed to proceed, or the shift is closed.
During an incident, the recording serves as a call to action. A few hours later, it becomes material for analysis.
ISO 22400 describes production KPIs in terms of, among other things, their trends over time and user groups. The metric should be communicated to the person who can make the appropriate decision at that moment.
| View | The question it answers is | A typical decision |
| OEE Dashboard | What’s not going according to plan right now? | Response to a stoppage, a slowdown, or shortages or lack of material |
| OEE Report | Where does the loss recur, and what is it related to? | Changes to standards, inspection schedules, process settings, or the setup of changeovers |
The boundary between these views does not lie at the end of the change. It is marked by the point after which the team can no longer limit the effects of the event.
When losses continue, OEE monitoring is necessary
The line has a target rate of 40 good units per minute. The stoppage lasts 12 minutes, which corresponds to 480 units of planned production. If the foreman receives a reliable signal after 3 minutes and shortens the downtime by the remaining 9 minutes, the difference will be 360 units.
This is only an approximate calculation, because the actual effect depends on the startup phase, buffers, bottlenecks, and the ability to catch up. However, it illustrates a simple relationship: the later the information reaches the person in charge, the smaller the portion of the consequences that can still be mitigated.
The OEE dashboard should help you find out:
- what has changed,
- How long has the deviation been going on?
- how does it affect the plan,
- Who should respond, and according to what rule?
However, the red indicator alone is not enough. This is where Jidoka—a concept known from lean manufacturing—can be useful. It involves detecting irregularities and triggering a machine shutdown or operator intervention. The signal will be effective only if it triggers a predetermined response.
A well-designed OEE visualization can show the line status, event time, progress relative to the schedule, the number of good and defective units, and the cause of the stoppage. The most important factor is time: can the user spot a deviation before the window of opportunity to take action closes?
After closing the reaction window, you’ll need the OEE report
The report after the change should not simply replicate the screen from the hall, because its purpose is to combine individual events into a repeatable pattern.
The production manager then needs an answer:
- Does the downtime recur with the same product, tool, or setting,
- Which category of losses takes up the most time on a weekly basis,
- Did the repair reduce the number of stops,
- Does the slower cycle apply to a single shift or to the entire process,
- how the result changed after adjusting the parameters or the operating standard.
OEE reporting provides a reliable basis for such decisions when each record includes a start and end time, a cause, a machine, a shift, a product, or an order. Without this information, the OEE percentage remains a figure devoid of context.
NIST data show that the improvement in performance is not due to the mere display of the metric. At Trenton Pressing, older machines were connected to the MES to track production, productivity, and downtime in real time. The project also included training, planning, and the work of technical teams. NIST reports an OEE increase of nearly 40 percentage points over the course of a year and a 50% increase in units shipped, while reducing operations from two shifts to 1.25 shifts.
Another plant, L&P, focused on the causes of breakdowns and maintenance work. After implementing TPM, productivity increased by about 22%, OEE rose from 39% to 45%, and the company avoided an investment valued at $250,000.
In both cases, the measurement led to work on the loss, and the result was later verified using the data.
The link between signals and accountability is where things most often go wrong
An alert may arrive immediately and still not change anything. This happens when it is unclear who is supposed to receive it, when the incident should be escalated, or how to confirm that the root cause has been resolved.
Before starting monitoring, determine the following:
- Response threshold: After how many seconds or minutes does an event require action?
- The person in charge: an operator, a team leader, a maintenance technician, a quality control specialist, or a logistics specialist.
- Escalation procedure: what happens when the set time limit is exceeded.
- Closing an incident: Who provides the reason and confirms that the process has returned to normal.
- Effect verification: Which report should you check to see if the event recurs?
OEE monitoring and reporting then become a single process. Data from the production floor describes the course of an event, and the history shows whether the response merely eliminates the effect temporarily or prevents future occurrences.
See how you can reduce losses with explitia.OEE
One test will show which view is missing
Just start with a line where the cost of downtime, idle cycles, or shortages is known.
Over the course of several consecutive shifts, check the following:
- How long does it take for the team to find out about the deviation,
- How much time is left then to limit the loss,
- Is the cause recorded immediately, or is it retrieved from memory,
- Does the report allow you to link an event to a product, an order, and a change,
- After performing the action, can you compare the result before and after the change?
If the information is not included until the change summary, the company knows the extent of the loss but can no longer influence how it unfolds. If the screen displays alerts without subsequent analysis, the same events may recur without the root cause being identified.
When evaluating the system, check to see if it combines real-time monitoring of the plan, OEE, and downtime with a unified record of causes. This functionality is offered, among others, by explitia.OEE, which automatically collects data from machines, analyzes downtime, and displays plan performance in real time.
Data is useful as long as there is a decision to be made
The OEE dashboard should reduce the time from deviation to response, and the OEE report should reduce the number of recurrences of the same loss. If either of these views does not lead to a decision, the scope, audience, or presentation method needs to be adjusted.
The best first step is to measure the time from the start of an incident to the moment the appropriate person is notified. The result will show you whether you need faster monitoring, a better response process, or a more detailed historical report.
FAQ
Does real-time OEE replace the OEE report?
No. Real-time data supports decision-making during production. The report is used to compare time periods, identify recurring causes, and evaluate the actions taken.
What should the OEE dashboard display?
Line status, event duration, plan implementation, pace, availability, efficiency, quality, and the information needed to initiate a response. The scope should depend on the recipient’s role.
When is an OEE report sufficient after a change?
When the goal is to analyze trends, review causes, and plan actions, it is not enough for the team to simply react to ongoing downtime, speed drops, or increases in shortages.
Where should you start when implementing OEE monitoring?
Starting with a single line and a single measurable loss. Determine the data source, the alert threshold, the person responsible, and the report where you can check the results.
Improve the OEE monitoring in your production.
See how else you can support your plant with other articles on the explitia blog
