Line OEE¶
Line OEE shows the same three-part score as the Dashboard, but for a whole production line rather than a single machine — and it builds the figures from the line's own recorded runs and stoppages, so there is nothing to type in.
Reading the figures¶
Pick a Line, a Shift and a Date. Four gauges appear — OEE, Availability, Performance and Quality — meaning the same things they do everywhere else in this module (see the overview).
Underneath, the same shift is broken down into the numbers behind the gauges:
| Figure | What it means |
|---|---|
| Planned | How long the shift was scheduled to run |
| Runtime | Planned time minus recorded stoppages |
| Downtime | Total time the line was stopped |
| Total Count | Everything the line produced, with the good count beside it |
| Rejected | Units that failed, counted as part of Total Count |
| Runs | How many separate runs the line recorded in the shift |
Rejected is part of the total, not on top of it
A line records what it made and how much of it failed, so the good count is the total minus the rejected count. Rejected units still count as production — the line spent time making them — which is why they lower Quality rather than Performance.
When Performance is blank¶
Performance is the figure most often blank on this page, and it is usually not a fault.
To judge how fast a line ran, Enture needs a cycle time standard set for that line and the product it was making. If no line standard covers what ran, Performance is left blank and the page says so.
A standard set against a machine is deliberately not used in its place. A machine standard describes how fast one machine runs one part; a line standard describes how fast a whole line turns out finished units. Substituting one for the other would produce a confident number that means nothing, so Enture shows nothing instead.
To fix it, add a standard for the line on Cycle Time Standards — the Applies To selector there lets a standard describe either a machine or a line.
Other blank figures
If no runs were recorded at all for the line, shift and date you picked, Performance and Quality are both blank and the page says no runs were recorded. That's different from a genuine zero — see When a figure is blank.
Downtime breakdown¶
Line Downtime Pareto groups the line's stoppages for that date by reason, longest first. It reads from the same reason list as the rest of the module, so a stoppage on a line and a stoppage on a machine are described in the same terms and can be compared directly.
Stoppages recorded only with an older, free-text reason appear as Unclassified rather than being left out. The time was genuinely lost, so hiding it would flatter the picture — but it can't be acted on until those stoppages are given a reason from the shared list.
Line OEE and machine OEE are different views¶
A line and the machines within it are measured from different records, so their figures will not match, and neither is wrong:
- The Dashboard measures one machine from the stoppages and counts people log against it.
- Line OEE measures the whole line from the runs the line itself recorded.
Use the Dashboard when you want to know which machine is holding a shift back, and Line OEE when you want the line's overall result without reconciling each machine underneath it.
There is no rework figure here
A line records what it produced and what was rejected, but not whether a rejected unit was later reworked or scrapped. That distinction is captured on job cards and on Production Entry instead.
If the page shows a message instead of figures¶
Line figures are read from the system that records line runs, so the page tells you which kind of problem it hit rather than showing a misleading zero — a zero would read as "this line never ran" when the truth is "we don't know yet". Three messages are possible:
| Message | What it means | What to do |
|---|---|---|
| Temporarily unavailable | The system holding the line's runs couldn't be reached just now | Try again shortly. Nothing is lost in the meantime — the runs are still recorded |
| The request was rejected | It answered, but refused the request. The reason it gave is shown with the message | Usually a configuration problem rather than a passing fault. Pass the wording on to whoever supports your Enture installation |
| A shift with unreadable start or end times | The shift you picked has a time period Enture can't interpret, so it can't work out how long the shift was | Correct that shift's start and end times in Shift settings, then reload the page |
A shift with one bad time period still works
If a shift has several time periods and only one is unreadable, Enture leaves that one out, works from the rest, and carries on — so the figures stay usable. It only stops if none of them can be read.