Real-Time OEE for Each Machine: Record, Formula and Dashboard Checks

Real-time OEE becomes useful when people trust the inputs. A live percentage alone is not enough. The supervisor needs to see whether planned time, run time, ideal cycle and good count are complete for the machine being reviewed.

Optiwise can combine production records and IoT machine signals so OEE is tied to work orders, shift output and quality decisions.

Direct answer

Real-time OEE needs one checked record per machine: planned time, run time, ideal cycle, total count, good count and a visible missing-data flag.

Factory example

A press shows 68% OEE at noon. The supervisor opens the record and sees planned time, run time, ideal cycle, total count and good count. One hour of quality results is still pending, so the live score is useful for shift action but not yet final for management review.

Implementation path in Optiwise

1. Validate planned time, ideal cycle and counter source.
2. Review availability, performance and quality separately.
3. Aggregate OEE only after missing-data flags are resolved.

Worksheet for your factory

Use this as the working checklist before you change software settings, write SOPs or ask the team to follow a new report.

Record	What to capture	Why it matters
Planned production time	Shift time minus planned stops	Base for availability
Run time	Actual running time from machine state or approved entry	Numerator for availability
Ideal cycle time	Standard time per good unit	Base for performance
Total count	All produced pieces or batches	Needed before quality split
Good count	Accepted output after inspection	Base for quality
Missing-data status	Sensor, counter, quality or plan missing	Stops false precision

How Optiwise supports this workflow

• Use live OEE, runtime, downtime, load, cycle and efficiency dashboards where machine data is connected.
• Tie machine data to production and quality records so good count is not assumed from pulses alone.
• Show downtime and missing data as separate issues instead of hiding them inside one score.
• Use machine-wise and shift-wise views before rolling numbers into a plant average.

Explore the connected Optiwise workflows for production, inventory, purchasing, quality, IoT, and AI agents.

Checks before you use the number for decisions

• Confirm the owner of the record and the person who reviews exceptions.
• Write the unit of measure, time period and source system beside every number.
• Mark missing, stale or manually corrected data instead of hiding it inside the final score.
• Keep approval evidence for changes that affect stock, production, quality or customer commitments.

Reference source

For general manufacturing ERP and MRP context, compare this workflow with Deskera MRP resources, then adapt the records to your own factory process.

FAQs

Should factory OEE be averaged across machines?

Use weighted aggregation. A simple average gives the same weight to a small auxiliary machine and a bottleneck production line.

What makes real-time OEE unreliable?

Missing planned time, wrong ideal cycle time, unclassified downtime and quality results posted later can all distort real-time OEE.