IEMSuite

Production & performance

OEE & downtime

Know where the shift went.

See availability, performance and quality by production line.

For production managers and shift leads

Discuss your workflowSee it in a working day ↓
Example shift Illustration, not customer results
One result.
Three different questions.

480 planned minutes
60 units/hour configured rate

420 min running60 min stopped

420 running minutes480 planned minutes

60 minutes of unplanned stops leave 420 running minutes from a 480-minute planned shift.

Availability × performance × quality. Rounded display values; OEE uses the unrounded ratios.

A working day · example scenario

The shift is over. The target was missed.

The final unit count tells you what happened, but not why. Was the line stopped, running below its expected rate, or making units that could not be used? Each answer calls for a different next step.

  1. Give the shift a fair baseline

    Set the line rate and planned working minutes. A shortened shift should not be judged against a full working day.

  2. Record the interruption where it happens

    An operator opens the line’s QR link, selects a stop reason and records the start and finish. Unplanned stops feed the availability calculation.

  3. Bring evidence to the handover

    Review availability, performance and quality separately, then compare the leading downtime reasons. Decide which loss deserves investigation before the next shift.

What you leave with

A production conversation about the cause of lost output, with the underlying records to investigate it.

Why we connect
these records.

We put OEE alongside production records because a percentage should lead somewhere useful. Planned time, recorded stops, output and scrap provide the context for the number. A missing line rate stays undefined instead of becoming a reassuring but misleading score.

Connect the baseline to shift planning →

Inside the workflow

OEE components

Review availability, performance and quality separately, together with the resulting OEE.

Downtime causes

Find the leading stop reasons. Unplanned downtime reduces availability.

QR stop entry

Open a line-specific link on a phone, select a reason, and start or finish a stop.

Scheduled summaries

Configure OEE thresholds and review daily alerts and weekly summaries.

Anonymous benchmarks

Participating organizations can compare rounded sector aggregates when the minimum cohort is met.

Before you bring
it to your team.

What does OEE measure?

Overall equipment effectiveness combines availability, performance and quality. In IEMSuite, unplanned downtime reduces availability, the configured line rate provides the performance baseline, and recorded output and scrap determine quality.

Do we need connected machines to start?

No. This workflow uses recorded production data and manual downtime entry, including the line-specific QR flow. It does not collect machine signals. OEE requires Scale; configure planned time and a line rate for meaningful results.

Can we review performance beyond one shift?

Use line and date filters, leading downtime causes, configured threshold alerts and weekly summaries. Anonymous sector comparisons are available only for participating organizations when the minimum cohort is met.

Continue exploring production & performance

Production & recipesShift planning & dispatchAndon production board
View all features