OEE Dashboard: What to Show Operators, Managers and the CEO
Most factories moving away from Excel and paper logs hit the same wall: production data arrives too late to fix the shift. Short stops get missed, downtime reasons are guessed after the fact, and OEE becomes a number teams discuss after the shift. That delay costs real output. GlobalReader's own OEE guidance shows factories can lose 20-30% of throughput to downtime, speed losses, and scrap, while even a 5% OEE lift can create major savings.
A useful OEE dashboard gives each role the view they need. Operators need the current job, live pace, stop reason, and improvement cue. Production managers need live machine status. Maintenance needs machine history and alerts. CEOs need one weekly email in euros.
In this guide, we will cover:
What an OEE dashboard should show.
How operators, managers, maintenance, and CEOs use different views.
Which dashboard elements turn OEE into action.
Where Excel reporting breaks down compared with live data.
If you want to see this workflow inside GlobalReader, start the free demo. No financial commitment.
What is an OEE dashboard?
An OEE dashboard is a real-time visual display combining Availability, Performance, and Quality metrics into a single equipment-efficiency score.
That score comes from three percentages multiplied together. In the ISO 22400 standard for manufacturing operations management, OEE = Availability × Performance × Quality.
ISO matters because every line, shift, and factory uses the same calculation. Fewer formula arguments means more time spent fixing losses.
Availability measures actual running time compared with planned production time, so teams can see how much time stops, setups, and delays are taking.
Performance measures actual output speed against the ideal cycle time, which shows whether the machine is running slower than expected.
Quality measures good parts compared with total parts started, so scrap and rework are included in the final score.
A 100% OEE score means the machine only makes good parts, at ideal speed, with no stop time. Treat that as the theoretical ceiling, not the daily target.
A score around 85% is widely treated as world-class for discrete manufacturing. Plants without live tracking often land closer to 40-60%, which means there is room to recover output before buying new capacity.
TEEP is the next capacity metric to know. OEE measures performance during planned production time, while TEEP looks at total calendar time.
For a deeper walkthrough of the formula, see GlobalReader's OEE guide.
The more useful question is whether the score is improving and which pillar is pulling it down.
OEE belongs on a live dashboard because losses happen during the shift. If a report arrives after the shift ends, teams can only discuss what already went wrong.
With real-time tracking, a stop, slowdown, or quality issue becomes visible while there is still time to respond.
One factory, four dashboard views (why one view fits nobody)
Operators, production managers, maintenance teams, and CEOs all use OEE data, but they make different decisions with it.
Show every role the same screen and the dashboard becomes noise. Operators miss the job cue, managers miss urgency, maintenance misses machine history, and leadership gets percentages when it needs euros.
The operator view: a TV screen on the line (current job, live pace, stop reasons)
The operator view belongs on a large TV near the line, not buried inside a laptop. The point is fast recognition while work is happening.
Current job: Operators see what should be running now, so there is less confusion during changeovers or shift handovers.
Live pace vs. target: The line team spots slowdowns early, before the gap becomes a shift-end surprise.
Stop reasons: When a machine stops, the operator selects the reason while the event is fresh, not hours later from memory.
Improvement framing: The screen shows the gap as something the team can fix, not as a scoreboard used to blame people.
Operator screen test: keep the display to four or five live elements. A good cue says, "10 minutes behind target, check feed speed now."
A bad screen shows shift OEE, weekly trend, finance loss, and five reason codes at once. Operators stop reading that within a week.
The production manager view: live machine status + downtime reasons on your phone
The mistake managers make is checking the dashboard at shift end, when the losses are already locked into the schedule.
In practice, a manager works through the same four checks:
Which machine needs attention right now? Running, stopped, waiting, or underperforming should be visible at a glance.
What is the reason? Categorised downtime reasons help decide whether to call maintenance, support the operator, or adjust the plan.
Is this a pattern? If the same stop reason appears across machines this week, the issue belongs in the daily meeting.
Can the shift target still be saved? Live progress shows how much output is at risk before the miss becomes permanent.
This is where downtime data becomes daily management. The manager needs the next place to go, not every detail on one screen.
The maintenance view: machine history, alerts, and task status
Maintenance teams need to know which machine is failing, how often the failure repeats, and what task comes next.
A live alert when a machine stops cuts the time between breakdown and fix. The stop reason gives maintenance a starting point before someone walks to the line.
Machine history changes the conversation with production. Instead of another fire drill, maintenance can show repeated stops, repair timing, and whether the fix held across the next shift.
The CEO view: one weekly email in euros
The CEO does not need to log into a production dashboard every morning. The right format is one weekly email that translates factory performance into euros.
Percentages are useful inside operations.
Leadership decisions usually happen in financial terms. A weekly email should show whether downtime, scrap, and speed losses are costing less than before.
A weekly email can look like this:
| Signal | Weekly view |
|---|---|
| Money impact | Estimated [add number of euros] value of downtime, scrap, and speed losses this week |
| Trend | Lower or higher than last week, with the main reason named |
| Decision | Keep improving, invest in the bottleneck, or review why losses are growing |
The useful signal for leadership is simple: are production losses shrinking in money terms, or are they still leaking margin?
The 6 elements every production dashboard needs
OEE tells you what happened. The six elements below turn that score into something teams can act on during the shift.
The mistake is treating OEE as one big number. A useful dashboard shows the loss, the reason, and the next place to look.
| Dashboard element | What it measures | What is missing without it |
|---|---|---|
| Availability | Percent of scheduled time the machine was running | Breakdown, waiting time, and changeover losses stay blurred |
| Performance | Actual output rate vs ideal cycle time | Speed losses and micro-stops stay invisible |
| Quality | Good parts as percent of total parts started | Scrap and rework appear after the batch is already at risk |
| Current job | Active order, target quantity, parts made, and ETA | Operators rely on paper notes or verbal handovers |
| Stop reasons | Why the machine stopped, logged in real time | Root-cause work runs on memory instead of downtime history |
| Trend vs target | OEE or loss metric over time against a goal | Teams cannot see whether yesterday's fix changed today's result |
Dashboard flow: Machine signal → OEE pillar → loss reason → next action.
What gets missed when one element is weak:
Availability gap: Managers cannot tell whether the lost hour came from a breakdown, a missing material, or a slow changeover.
Performance gap: Speed losses and micro-stops, two of the Six Big Losses, make the line look busy while it misses target every hour.
Quality gap: Defects need to be visible during the batch, before delivery is already at risk.
Current job gap: Operators working from paper notes or verbal handovers can run the wrong version of the plan.
Stop reason gap: End-of-shift recall is unreliable. The reason needs to be logged while the stop is still visible.
Trend gap: Teams need to know whether yesterday's fix moved the number before next week's review meeting.
Excel dashboards vs live dashboards
Excel OEE dashboards are useful for historical review. They are too slow for correcting production losses while those losses are still recoverable.
Excel is where factories often start, and it still makes sense in specific situations. The question is whether the spreadsheet keeps up with what the team needs during the shift.
Quick test: if a stop happens at 10:00 and the reason is typed in after lunch, the dashboard is already reporting history.
| Area | Excel dashboard | Live dashboard |
|---|---|---|
| Timing | Updated after manual entry | Updates during the shift |
| Data capture | Typed from notes | Machine signals and operator reasons |
| Accuracy | Prone to copy errors | One shared data source |
| Planning | Separate schedule files | Plan vs actual view |
| Action | Review after the shift | Intervene during production |
Say a machine starts running at 85% of ideal speed at 10 a.m. With a spreadsheet, the issue shows up after someone enters the data.
With live tracking, the production manager sees the loss while the feed system can still be checked.
OEE losses build in small pieces: micro-stops, slow cycles, late starts, scrap, and rework.
A machine running at 90% of target speed for one 8-hour shift loses around 48 minutes of output. Across 5 machines and 3 shifts, that becomes more than one full shift of lost capacity.
With GlobalReader, machine data is collected automatically. Operators add stop reasons and scrap counts while the work is happening.
Managers see downtime reasons, machine status, and plan gaps before the shift ends. The time to know what happened drops from hours to minutes.
Excel still makes sense in the right situation:
Early OEE tracking: Use the GlobalReader Excel OEE template to learn availability, performance, quality, and basic loss categories.
Small production setups: A simple spreadsheet works when there are fewer machines, fewer shifts, and low reporting pressure.
Monthly improvement reviews: Excel still works for finance checks, summaries, and one-off analysis after production ends.
Before software budget approval: A template is better than guessing, if the team agrees on definitions.
Move to a live dashboard when the same data starts appearing in two places: the spreadsheet and the factory floor.
That is usually the point where one source of truth matters more than another manual report.
Setting this up with GlobalReader
GlobalReader shows where production is losing time and money while the shift is still running. Retrofit hardware captures machine data automatically, and the cloud view breaks losses down by machine, shift, and reason.
Start with one goal: put the right number in front of the person who can act on it.
With GlobalReader, you can start small with retrofit hardware and Analytics, then add the modules that connect live production data to daily decisions.
Connect the machines: ScoutBox retrofit hardware captures machine signals and sends them to the cloud, so you are not waiting for paper logs or end-of-shift updates.
Build the live OEE view: Analytics turns Availability, Performance, Quality, and downtime into a real-time view by machine, line, shift, or reason.
Capture the reason behind the number: Operator lets the shop floor add stop reasons, scrap input, and production feedback while the event is still fresh.
Put the dashboard where work happens: Smart LiveView shows real-time reports and graphs on screens, including TV links for line-side visibility.
Line-side view: A good Smart LiveView screen shows current job, live pace, OEE score, and stop reason on one TV.
Connect planning and reporting: Planner compares planned work with live progress, while Smart Factory helps connect production data with ERP and other systems.
Review losses every week: Use the same data to discuss downtime, output, quality, and plan vs actual gaps with production, maintenance, planning, and leadership.
For most teams, the value is one view per job role:
Operators: The TV shows the current job, live pace, and stop reason. No spreadsheets after the shift.
Production managers: The phone view shows stops, slowdowns, and shift losses while there is still time to react.
Maintenance teams: Machine history and alerts show what failed, how often, and what needs attention next.
Planners: Planner compares the schedule with real progress, so customer promises are based on factory reality.
Leadership: A weekly email shows where time and money are being lost across lines, shifts, and orders.
When you are ready to start, the entry point is low.
The Starter Bundle starts from €109/month per machine, with hardware and software included. You can check the latest details on the pricing page, then add Operator, Planner, Smart Factory, and add-ons as your factory needs them.
When you want to check the workflow, start the free demo. Sign in with Google, take the guided tour, and see how GlobalReader turns OEE data into daily action without a financial commitment.
If you still have role-by-role questions, the FAQ below covers the common ones.
FAQ
-
An operator should see the information that helps them run the current job better: current job, live pace, stop reason, and one clear improvement cue.
They should not see CEO-level finance, long reports, or every KPI from every plant. That view creates noise, not action.
-
Yes, an OEE dashboard can run on a normal TV if the screen has an internet-connected device attached, such as Android TV or another browser-capable setup.
GlobalReader's Smart LiveView uses TV links for real-time production screens, so teams can keep live pace and status visible on the line.
-
The best OEE data comes from two sources: machine signals for what happened, and operator input for why it happened.
Hardware can capture counts, stops, and machine states automatically. Operators then add context such as stop reasons, scrap, or production notes, so the dashboard shows reality instead of guesses.
If you want to see the workflow before changing your line, try GlobalReader's free demo.
