Material shortage, changeover, mechanical — ranked by minutes lost this shift.
42mTop loss
7Stops
100%Coded
1Open
Module
Downtime
Know why the machine stopped — before the shift report is written.
- Operator stop codes in ≤2 taps on tablet
- Pareto of unplanned losses by reason, line, and shift
- Alerts when chronic reasons repeat
Illustrative sceneOutcomes
What you'll gain
- Categorized downtime instead of “other”
- Faster standups with facts on screen
- Clear Availability drivers for OEE
- Work-order drafts from recurring patterns
Product tour
Inside Downtime
Timeline + Pareto on the same Core as OEE — no separate spreadsheet.
Illustrative product scenario — not a customer deployment or live plant feed.
Deterministic sample values show the interaction pattern. Production deployments bind this view to governed Industrial Core signals.
| Module signal | 42m |
|---|---|
| Context | Deterministic sample values show the interaction pattern. Production deployments bind this view to governed Industrial Core signals. |
Every stop with reason, duration, and machine — ready for root cause.
Day on the floor
How it changes your day
- Operators log reasons without leaving the line
- Supervisors attack the top bar on the Pareto first
- Maintenance gets evidence, not anecdotes
Accuracy
Availability you can defend
Planned vs unplanned downtime follows site policy. OEE Availability stays honest.
- Stop reason taxonomy per site
- Minutes feed Availability in A×P×Q
- Same events visible in Console and Operator
Review your factory improvement case
Bring one production line, its current data sources, and a priority loss. We will map the measurement, workflow, and proof of value.