OVERALL EQUIPMENT EFFECTIVENESS (OEE)

OEE shows more than a percentage: it shows where production time is lost

OEE combines three aspects of the production process: Availability, Performance, and Quality. Iwoscan helps record run time, stops, cycles, production quantities, and quality events at the workstation. This allows the overall score to be broken down into specific causes that the team can investigate and reduce.

Circle green checkmark Odoo ERP friendly
Circle green checkmark Built-in task splitting and merging
Circle green checkmark Raw data without distortion
Monitoring OEE in manufacturing with Iwoscan

What the OEE metric actually shows

OEE stands for Overall Equipment Effectiveness. It is calculated by multiplying Availability, Performance, and Quality. Each factor represents a different group of production losses.


OEE calculation formula

OEE = Availability × Performance × Quality

The three percentages are multiplied, not added. For example, 90% Availability, 95% Performance, and 99% Quality result in 84.6% OEE. The overall score shows the result; the three factors show where to look for losses.

Equipment availability and downtime data

Availability shows the impact of stops

Availability is calculated by dividing actual Run Time by Planned Production Time. Breakdowns, changeovers, material shortages, and other recorded stops reduce this OEE factor.

Production cycle performance comparison

Performance reveals speed losses

Performance compares the actual production quantity and Run Time with the Ideal Cycle Time. Slow cycles, minor stops, and workflow disruptions become visible even when the equipment is technically running.

Good parts in the OEE calculation

Quality measures good parts made the first time

The Quality factor is the ratio of Good Count to Total Count. Scrap and parts returned for rework reduce this value because production time has already been used to make them.

Consistent OEE calculation rules

Comparable OEE requires consistent rules

Planned Production Time, Ideal Cycle Time, the definition of a good part, and stop thresholds must be agreed in advance. If the rules change with the result, OEE values from different shifts or periods cannot be compared reliably.

Analysis of OEE loss reasons

The metric must lead to a specific action

An OEE percentage alone does not explain what to change. Iwoscan links a stop, slow cycle, or quality event to its time, workstation, task, and selected reason, helping the team start with the largest recurring loss.

From the first measurement to improved OEE

Reliable OEE starts with clear calculation boundaries and actual production data. The improvement cycle should show not only what changed, but why.

  • 1

    Select a specific process and period

    Start with one workstation, machine, or production line. Define the shift, Planned Production Time, and any periods that are excluded from the OEE calculation.

  • 2

    Agree on the Ideal Cycle Time

    The Ideal Cycle Time should reflect the fastest sustainable rate of the process, not a conveniently reduced planning speed. An inaccurate value can artificially improve or reduce the Performance score.

  • 3

    Record actual process events

    Iwoscan records Run Time, Stop Time, cycles, Total Count, and Good Count. At the workstation, the operator can select a stop, scrap, or another agreed reason, and the event is stored with its production context.

  • 4

    Break OEE down into its three factors

    Calculate Availability, Performance, and Quality. The team reviews not only the overall percentage but also the duration, frequency, reasons, and distribution of losses by product, shift, or workstation.

  • 5

    Verify the change using the same data rules

    After addressing the selected cause, compare periods calculated in the same way. This shows whether the specific loss decreased and whether the improvement came at the expense of another OEE factor.

Would you like to calculate OEE using actual production data?

Leave your name, email address, and phone number. We will discuss the selected workstation, available machine signals, the stops currently being recorded, and the data still needed for a reliable OEE calculation.

How Iwoscan collects the data required for OEE

The data collection method is adapted to the actual process. Machine signals, recorder inputs, RFID or barcode and QR code scans, and employee selections can be combined into a single history of production events.

Recording equipment Run Time

Run Time and Stop Time

A machine signal or workstation action records when production is running and when the process stops.

Recording a downtime reason

Downtime reasons at the workstation

The operator selects a reason configured for the process, so every stop has both a duration and an explanation.

Production cycle and quantity records

Cycles and production quantity

Cycle signals, scanning, or operator input can record Total Count and the actual production rate.

Recording Good Count and scrap

Good Count and quality events

Good parts, scrap, and units requiring rework are linked to the task, product, time, and workstation.

Local storage of OEE data

Data is retained during network interruptions

The recorder stores data locally first, so the production history is not lost during temporary network interruptions.

OEE data integration with ERP and MRP

Integration and data export

Process data can be transferred to an ERP, MRP, or another management system and used for reporting and further analysis.

Show us one production workstation

Briefly describe the process, equipment and data that is currently missing.

We will explain what can be recorded, which Iwoscan set is suitable and how the data can reach your systems.

Discuss your process

Key questions about calculating OEE

How is OEE calculated?

OEE is calculated by multiplying Availability, Performance, and Quality. Availability is the ratio of Run Time to Planned Production Time. Performance compares Ideal Cycle Time and Total Count with actual Run Time. Quality is the ratio of Good Count to Total Count.

What data is required to calculate OEE?

You need Planned Production Time, actual Run Time and Stop Time, Ideal Cycle Time, Total Count, and Good Count. To use OEE for improvement, it is also important to record the reasons behind availability, speed, and quality losses.

Is OEE an employee efficiency score?

No. OEE measures losses in a selected machine or production process during Planned Production Time. Employees help provide context for events, but the metric should not be used as a simplified score of individual performance.

What is considered a good OEE score?

There is no single universal target for every factory. The result depends on the type of process, product mix, batch sizes, and calculation boundaries. It is more useful to establish a reliable baseline for your own process and steadily reduce its largest losses.

Where should an Iwoscan OEE implementation begin?

Select one important workstation or machine, agree on the rules for Planned Production Time and Ideal Cycle Time, and define several key downtime reasons. The first stage should show whether the data is reliable and whether the team can use it to complete a specific improvement action.

; ;