OEE¶
OEE (Overall Equipment Effectiveness) tells you how much useful output a machine actually produced during a shift, compared with what it could have produced had it run the whole shift, at full speed, with nothing rejected.
The one rule worth knowing first¶
OEE is never typed in. It is always worked out from what was logged: stoppages on the Downtime Log, counts on Production Entry, and the cycle times set up under Cycle Time Standards. There is no field anywhere to enter an OEE figure by hand, and no way to adjust one after the fact — you change the figures by correcting the underlying log entries.
This is deliberate: an OEE number that can be edited is a number nobody can trust.
A shift can have more than one row¶
Some shifts aren't one continuous block — a shift can be split into separate rows, each with its own start and end time. For example, a shift called "Production" might be made up of "Shift A" running 09:00–17:00 and "Shift B" running 17:00–01:00. Where that's the case, Enture works out OEE separately for each row, not blended into one figure for the whole shift.
This means every place you pick a shift in OEE — the Summary, Downtime Log, Production Entry and Machine Production Planner — also asks you to pick the Shift Row for that date, once more than one exists. Each row gets its own Availability, Performance, Quality and OEE figure, its own downtime breakdown, its own plan, and its own "Close Shift" — a changeover between Shift A and Shift B is treated the same as a changeover between two different shifts, not pooled into one number.
If your organisation's shifts are each a single block with no further rows, this makes no practical difference — there is always exactly one row to pick, and Enture selects it for you automatically.
Which shift's rows show up at all is set once, under Shift Mapping.
Which machines appear in the Machine list¶
If you've assigned machines to a shift in your Shift settings — the "add machine" option on a shift — then the Machine list across OEE shows just those machines once that shift is selected. The Summary, Downtime Log, Production Entry and the Machine Production Planner's New Plan form all behave this way.
This is a convenience, not a restriction: it keeps the list short and relevant on a site with dozens of machines, so an operator isn't scrolling past equipment that has nothing to do with their shift.
If no machines have been assigned to that shift, the list shows every machine in your organisation — exactly as it did before. So there's nothing you have to set up for OEE to work, and you'll never find the list empty. Assigning machines to shifts simply makes it tidier.
Machine and product lists are searchable — just start typing
Every Machine and product (SKU) list across OEE opens with a search box at the top: start
typing and the list narrows to what matches, so you don't have to scroll to find a machine on a site
with dozens of them. It matches anywhere in the name, not just the beginning — typing press finds
Hydraulic Press 2.
This applies on the Summary (including its history heatmap), the Downtime Log, Production Entry (both logging and Reconcile), Cycle Time Standards — where the Line list is searchable too — and the Machine Production Planner, in its New Plan form and its machine filter.
Two things worth knowing:
- A machine you've already selected stays in the list, even if it isn't assigned to the shift you've since switched to. This matters on the Downtime Log: the Open Downtime panel lists stoppages still running on any machine, and choosing Resume on one needs to work regardless of how that machine is assigned.
- The Machine Production Planner's list filter is not narrowed — it shows every machine, because you're filtering plans you've already saved, and those may include machines that are no longer assigned to that shift.
If a machine you expect is missing from the list, check whether it's been added to that shift in Shift settings — or pick a different shift.
This assignment decides what Auto Generate OFFERS
In the Machine Production Planner's Auto Generate, the machines assigned to the shift are the ones its Machines list offers — and they all start selected, so leaving the list alone plans every one of them.
If the shift has no machines assigned, the same fallback applies: every machine in your organisation is listed, and Auto Generate says so in those words rather than claiming they're assigned. Worth reading that line before clicking Review.
Either way you can untick machines on the screen itself, so assigning them to the shift is a way to keep the list short rather than the only way to narrow a run.
How the three parts fit together¶
| Part | Question it answers | How it's worked out |
|---|---|---|
| Availability | Was the machine running when it was supposed to be? | Running time ÷ planned production time |
| Performance | When it was running, did it run at full speed? | What the logged output should have taken at the standard cycle time, ÷ the time it actually ran |
| Quality | How much of the output was right first time? | Good pieces ÷ total pieces |
OEE = Availability × Performance × Quality. All three are percentages, so a shift that scores 90% on each has an OEE of about 73% — which is normal, and is the point of the measure.
Rework counts against Quality, not Performance
A piece that has to be reworked is counted in the total but not as good, so it pulls Quality down. The machine still gets credit for having produced it, so Performance is unaffected. This is the standard treatment and matches how the rest of the industry reports it.
How each figure is actually worked out¶
This section walks through the full calculation in plain terms, with a worked example at the end. You don't need to do any of this maths yourself — Enture does it every time a gauge is shown — but understanding it makes the numbers something you can act on rather than just read.
1. Planned time — how long the machine was meant to be producing¶
Every shift has a length (its start and end time, set up in Shift settings). But a shift's planned time — the figure Availability is measured against — isn't always the same as the raw shift length. It comes from one of two places:
- Normally: the shift length, minus any stoppage marked as a planned stop. A scheduled changeover or planned maintenance window is still a real stoppage, but it isn't a loss the way a breakdown is — it was always part of the plan. Enture tells the two apart by the category set on the stoppage's reason code: a reason whose category is Planned shrinks the planned time instead of being counted as lost running time. Everything else (a breakdown, waiting for material, anything unplanned) reduces running time instead — see step 2.
- If you've set up a Machine Production Planner entry for that exact machine, shift and date, Enture uses the production time you planned for ahead of the shift instead of working it out from the shift length. This only happens when a plan exists for that specific machine + shift + date — any shift without one is measured against the shift length as before.
Why a plan is treated as more reliable than the shift length
A plan you entered ahead of the shift already accounts for things the shift length alone doesn't know about — a short-staffed shift, a planned equipment check, a shift deliberately cut short. Once you've told Enture what you actually planned to produce, that becomes the yardstick instead of the shift's raw hours.
This is per Shift Row, not per shift
Where a shift is made of more than one row (see above), "that exact machine, shift and date" means that exact Shift Row — a plan set up for "Shift A" has no effect on "Shift B"'s figures, even though both sit under the same shift.
2. Running time — how long it actually ran¶
Running time is the planned time from step 1, minus every stoppage not marked Planned — breakdowns, waiting for material, anything that wasn't supposed to happen. This is the only kind of downtime that counts as a genuine loss.
Availability = Running time ÷ Planned time.
3. The standard it's measured against — and what happens when more than one product ran¶
Performance compares what was actually produced against what the Cycle Time Standard says should have been possible in the time the machine actually ran.
If a shift only ever made one product, this is simple: standard time per piece × pieces made, divided by running time.
If more than one product ran in the same shift (a changeover partway through, say), Enture doesn't average the two products' standard times evenly — it blends them in proportion to how much of each was actually made. A shift that made mostly the faster product is judged mostly against the faster product's pace, with only a small pull from the slower one. This keeps Performance fair: a shift isn't penalised or flattered just because of which two products happened to run together.
Performance = (blended standard time per piece × total pieces made) ÷ Running time.
A Performance over 100% is possible, and isn't an error — it means the shift genuinely beat the standard. If this happens often for a product, it's usually a sign the standard was set too conservatively; see Cycle Time Standards.
4. Quality¶
Quality = Good pieces ÷ Total pieces (good + scrap + rework). See Production Entry for what the three counts mean.
5. Putting it together¶
OEE = Availability × Performance × Quality.
A worked example¶
An 8-hour shift (480 minutes) on a machine with a standard cycle time of 1 minute per piece:
| Step | Figure | Running total |
|---|---|---|
| Shift length | 480 min | |
| Less a 30-minute scheduled changeover (reason category Planned) | −30 min | Planned time = 450 min |
| Less a 60-minute breakdown (reason category Unplanned) | −60 min | Running time = 390 min |
| Availability | 390 ÷ 450 | 86.7% |
| Production Entry logged 350 good, 30 scrap, 20 rework | 400 pieces total | |
| Performance | (1 min × 400) ÷ 390 | 102.6% |
| Quality | 350 ÷ 400 | 87.5% |
| OEE | 86.7% × 102.6% × 87.5% | ≈ 77.8% |
Nothing here was typed in by hand — every figure traces back to a Downtime Log entry, a Production Entry count, or a Cycle Time Standard. Change any of those and the figures above change with them, immediately.
When a figure is blank¶
A blank is not a zero. If something needed to work a figure out is missing, Enture leaves it blank and tells you what's missing, rather than showing 0% and letting you draw the wrong conclusion:
| What you see | What it means |
|---|---|
| No production count logged | Nothing was logged for that machine, shift and date, so Performance and Quality can't be worked out. Availability still can |
| No cycle time standard configured | The machine and product pair has no standard time set up, so Performance can't be worked out. See Cycle Time Standards |
| No cycle time standard for the line | The same thing on Line OEE: a line's Performance needs a standard set for that line and product. A machine's standard is deliberately not used in its place, because it describes something different |
| No runs recorded | On Line OEE, the line recorded no runs for that shift and date, so Performance and Quality can't be worked out |
| A shift with unreadable start or end times | The shift's start or end time can't be interpreted, so Enture can't tell how long it was meant to run. Correct it in Shift settings and reload. This is reported plainly rather than shown as 0% — a zero would read as "nothing ran", when the truth is that the planned time is unknown |
| Not measured for OEE | The step is desk work — design, drawing, GTP preparation — so it has no OEE at all. It is also left out of its Work Order's figure, because planned hours with no machine behind them would read as perfect uptime. See Job Cards |
| Some cards left out of a Work Order's figure | The order's OEE covers only the steps actually done on the shopfloor. Enture shows how many cards were measured alongside the total, so the two can be told apart |
| A step with no planned time | The shifts worked on that card have no start and end times set up, so there is nothing to measure the runtime against. Correct it in Shift settings |
| Performance shown as 0% | This is a real zero — it means the machine was logged as stopped for the entire shift |
| A plan expected downtime that was never logged | You set up a Machine Production Planner entry that forecasts some planned downtime, but nothing has actually been logged on the Downtime Log with a reason marked Planned for that shift. Enture flags this rather than guessing — either the planned stop hasn't happened yet, or it happened and nobody logged it |
In this section¶
- Summary — Plant-wide OEE at a glance, the worst-performing machines, a history grid and trend charts, and a drill-down into any single machine
- Line OEE — The same score for a whole production line, built from the runs the line itself recorded
- Downtime Log — Start and stop stoppages, and give each one a reason
- Production Entry — Log good, scrap and rework counts from the shop floor
- Reason Codes — The list of downtime reasons operators pick from
- Cycle Time Standards — The standard time per piece for each machine and product
- Machine Production Planner — Plan production ahead of a shift, then compare it against what actually happened. One plan at a time, in bulk from a spreadsheet, or a whole week generated from your cycle time standards
- Shift Mapping — Set which shift, and which of its rows, OEE is measured against for your organisation
OEE elsewhere in Enture¶
The same figures appear where the work is, not only on the OEE dashboard:
- A Work Order shows its own OEE, covering just that order, on its detail page.
- A Job Card shows OEE for that one routing step, on its own machine and shifts — see Job Cards. Steps that run for days on engineered, one-off work are measured against their schedule instead, since a pieces-per-minute figure means nothing for them.
These can legitimately differ from the shift figure for the same machine and day: a shift can carry work from more than one order, while a work order's figure counts only its own.