You know what your machines should be running. Now you also know why they aren't.

Solution 01 · OEE monitoring

OEE is the only figure that captures availability, speed and quality in a single number. We measure it automatically, per machine and per shift, and show how much time each loss costs. No tally sheets, no estimates after the fact.

60%Typical OEE in discrete manufacturing. World class sits around 85%.
1 in 3Of your paid production hours is lost without anyone registering it.
6 lossesFrom changeover to scrap: every loss visible on its own, not as one lump.
Real timeYou see the shift while it runs, not in tomorrow's report.
The formula

One number, three honest questions.

OEE multiplies three percentages. That makes it strict: 90% on all three still gives you only 73%. Which is exactly why it shows where you're really leaving it behind.

A · availability

Availability

Of the time the line should have been running: how much did it really run?

  • Breakdowns and faults
  • Changeovers and setup
  • Waiting on material or operator
×
P · performance

Performance

While it was running: did it run at the pace it was built for?

  • Microstops of a few seconds
  • Deliberately reduced speed
  • Ramp-up after every restart
×
Q · quality

Quality

Of what came out: how much was right first time?

  • Rejects and rework
  • Start-up scrap per batch
  • Scrap on product changeover
Where the time goes

The six losses, each with a name and a number of minutes.

Availability

Breakdowns

The stops everyone sees and that are still rarely counted exactly. We log start, end and reason.

Availability

Changeovers

“About half an hour” often turns out to be 52 minutes in the figures, and 71 on the late shift.

Performance

Microstops

A jam, a sensor, a box askew. Twenty times a shift, never noted, hours a week together.

Performance

Speed loss

The line runs, but 12% slower than nominal speed. Invisible without measurement.

Quality

Start-up scrap

Every restart costs material. The more often the line stops, the more expensive it gets.

Quality

In-run rejects

Scrap linked to machine, product and shift, so you see the pattern instead of the incident.

One shift, unfolded

This is what an ordinary Tuesday looks like once you measure it.

Early shift · 06:00 - 14:003 lines
RunningDowntimeMicrostopChangeover
Line 171%
Line 259%
Line 383%
06:0008:0010:0012:0014:00

Line 2 had no major breakdown at all. It still lost more time than line 1: six microstops and a 34-minute changeover. That is the kind of loss that never shows up in a daily report, and that you cannot tackle without figures either.

In the portal

The same figure for the floor, the desk and the board.

portaal.aionix.be/analytics/dashboards
AIONIX portal, dashboard with OEE breakdown, microstops and lost time per line
Live on the floorA screen at the line shows the shift as it runs now, not as it ran yesterday.
How your OEE is builtAvailability, performance and quality apart, so the discussion is about facts.
AI analysisAsk why line 2 always falls back on Thursday and get the cause, not the chart.
What it is worth

Put a figure on it before you decide.

Slide from the OEE you have today to where you want to be. You immediately see how many production hours that frees up, and what they are worth.

Two shifts, 230 days ≈ 3,680 hours.

If you do not know it, take 60%. That is a common figure in discrete manufacturing.

Margin or contribution per hour the line is producing. A rough estimate is fine.

Additional value per year · per line
€ 95,000

Without a new machine, without an extra shift, without a square metre more floor.

OEE
60% → 70%
Production hours gained
380 h

An indicative calculation from your own input, not a measured result. In a two-week measurement we replace the estimate with your actual figure.

The pattern we see every time
“The machine everyone thought was the problem ran fine. The changeover before it cost us the day.

What a measurement nearly always exposes: the biggest loss is not where the attention is.

1 lineEnough to see the pattern before you roll out.
2 weeksFixed price, fixed scope, one network port from IT.
Who it helps

The same figure, four different decisions.

Operator

Sees the shift live

Marks a stop reason in two taps and knows straight away whether the line is ahead or behind.

Production manager

Stops tallying

No more assembling reports. The time goes to the line instead of to Excel.

Maintenance

Sees the pattern

Which machine stops on the same day every time, and at what hour someone should be standing by.

Management

Knows whether to invest

Before you buy capacity: first see how much is still left in the existing lines.

How it runs

From decision to first figure in one week.

Day 01

Choose

Together we pick one line: preferably the line the argument is loudest about.

Day 02

Install

An AIONIX device plus sensors on infeed and outfeed. The machine stays untouched, no machine builder needed.

Day 03

Measure

The first shift comes in. Raw, but real: this is what the line actually does.

Day 04

Name it

Together with the operators we set up a short list of stop reasons. Fifteen, not fifty.

Day 05

Adjust

The first loss is on the table. You tackle one and measure next week whether it worked.

What customers ask first

The four objections, answered honestly.

Our machines are old. Does this work on them?
Especially on those. We measure with our own sensors on infeed and outfeed, independent of the controls. A thirty-year-old machine gives exactly the same figures as a new one. If your machine does have modern controls, we connect directly later and it gets even more precise.
What does our IT have to do?
Provide one network port. No server, no VPN project, no new licences on your existing systems. The data sits in the AIONIX portal and stays yours; you export it at any time.
Will the operators use this?
Only if it's fast. That's why we keep the stop list short and registration happens on a screen at the line, not in an office application. Where it goes wrong is usually not the technology but the intent: use the figures to improve machines, never to settle scores with people.
What if it turns out there's little headroom?
Then you know that after two weeks, at a fixed price, and you can invest in capacity with peace of mind. That is just as useful an answer as the opposite.
How it connects

OEE only becomes usable with the context around it.

OEE tells you how much capacity you lose. Why you lose it sits in the other modules of the MOM platform. That is why the number is a starting point, not a final report.

Maintenance

Availability loss is usually maintenance that came too late. Add maintenance and every stop becomes an asset with a history, so you can see which machine is structurally holding your OEE down.

Quality

The quality factor in your OEE is a percentage; quality registration tells you which measurement and which order sits behind it. Without that, scrap stays a number with no cause.

Production monitoring

OEE is a look back per shift. With live monitoring you see the loss while the batch is still running, so you can still act instead of finding out on Monday.

To see an OEE figure built in real time on a real line, read how Moerman NV went from paper registration to real-time OEE in three months. More on the number itself in OEE and MES, also for SMEs.

For manufacturers in West Flanders

Put your entire shop floor on the same platform.

No 'big bang'. As a West Flanders-based team, we start at your SME with the first module on the first line, prove the value, and build out together to your full platform, at the pace and budget of an SME.