ThingConnect

Factory overview

The plant missed target. Which machine?

Most plant dashboards answer the first half of that question and stop. Factory Overview pools every machine into a plant-level read, then lets you walk down the same three panels — OEE, production, downtime — through line and cell to the machine that actually lost the time, and the reason it stopped.

Plant → line → cell → machine same three panels at every level worst-first ranking

The problem

The gap between knowing and finding

  • The morning meeting agrees the plant is behind, then spends forty minutes arguing about which line it was.
  • OEE is reported per machine, so nobody can say what a line is doing without adding up a spreadsheet by hand.
  • Downtime totals arrive alphabetically, not worst-first — the biggest loss is somewhere in row nine.
  • By the time the cause is traced to one cell, the shift it happened in is over and nobody remembers the stop.

How it works

From the whole plant to one machine, in four steps

Every step is the same three panels at a narrower scope. Nothing new to learn on the way down — only fewer machines in the number.

Step 1

The whole plant, in one read

Every machine pooled into a single read.

Facility · summary
PlantToday · all shifts · by hour
OEE69%A90%P77%Q99%
Production326 / 47069%
Lines3
Downtime5h 55m
Step 2

Which line owns the gap

One card per line, naming the machine holding it back.

Facility · line rollup
Line

Turning

3 machines · Bottleneck: Lathe-02
OEE
Overall
Current
—
Average
62%
Availability
Current
—
Average
92%
Performance
Current
—
Average
69%
Quality
Current
—
Average
97%
Step 3

Inside the line, down to the cell

The last grouping before equipment — its downtime names machines.

Line · cell breakdown
Turning · cell

Cell C — Turning

2 machines · Bottleneck: Lathe-02
OEE
Overall
Current
—
Average
57%
Availability
Current
—
Average
90%
Performance
Current
—
Average
65%
Quality
Current
—
Average
97%
Step 4

The machine, and why it stopped

Every machine in the cell, and the reasons it stopped.

Cell · machine detail
Machine

Lathe-02

Alarm: 17m · 4 stops
OEE
48%
↓ 6.2pp
Utilization
82%
↓ 4.4pp
Parts
26
Expected 55
Downtime
1h 28m
Alarms
11
OEE breakdown
Availability
86%
Performance
58%
Quality
96%
48%OEE
  • Availability1.1 h · 27%
  • Performance2.9 h · 69%
  • Quality0.2 h · 4%
OEE
Overall
Current
48%
Average
48%
Availability
Current
86%
Average
86%
Performance
Current
58%
Average
58%
Quality
Current
96%
Average
96%
Operations
OperationGood vs exp.OEE %
O1240 Rough turn14 / 3046%
O1265 Finish turn12 / 2551%

What each panel shows

Three panels, read side by side

OEE tells you how well the time ran, production tells you what came out of it, and downtime tells you where it went. Splitting them across three screens is what makes the cause hard to find.

Three numbers that only mean something together

Availability, performance and quality each get a reading and the hour-by-hour shape beside it. High availability next to low performance is a completely different problem from the reverse — and you can only see which one you have when they sit on the same row.

Measured against expected by now, not by end of shift

The headline count and its percentage are the easy part. The bar strip is the one that changes behaviour: real output for each hour against that hour’s own target, rejects stacked in red where they happened, and the hours still to come left visible rather than dropped.

Downtime arrives already ranked

Total lost time, broken down by line and ordered by loss — not an alphabetical list you have to scan. On the live screen each bar is also the way down a level, so the ranking and the navigation are the same control.

Why it works

Built on your own plant structure

One shape, every level

OEE, production and downtime sit side by side for the plant, a line, a cell and a single machine — the same three panels at all four scopes, so you never re-learn a screen on the way down.

Pooled, not averaged by hand

A line's numbers are computed from its own machines' telemetry against the shift calendar. Nothing is typed in, so the line rows and the plant total cannot disagree.

The bottleneck, named

Each line card names the machine holding it back, so the drill-down starts from an answer rather than an alphabetical list of everything you own.

Questions

Common questions

Your own plant structure. You group machines into cells and cells into lines during setup, and every rollup on this screen is computed against that hierarchy — so a line means what your supervisors already call a line, not a fixed category we impose.

Because a pooled figure across several lines has no single live reading to attribute to one instant. The window's real pooled average is shown instead of a separately-derived number that could quietly disagree with it. Drill into one line and Current fills in.

That hour's own planned rate. Each bar is the real output for that hour, with rejects stacked in red, so a bad hour is visible while there is still shift left to react to it. Hours that have not started yet are dimmed rather than hidden.

Yes — the whole screen is driven by one window-and-shift filter: today, a named shift, yesterday, a week, or a custom range. The drill-down carries your filter down with it, so opening a line does not reset you back to today.

No. The drill-down ends on a machine’s own rollup and its stop reasons, which is enough to know where to go and why. The dedicated machine screen is still where you see its hour-by-hour timeline and classify individual stops.

Get started

See your own plant on this screen

A 30-minute demo, then a pilot on your own floor if it fits.