Platform Features · Downtime Reasons Capture
Every stop has a reason. Now it has a record.
Stops are detected automatically to the second. Operators tag the reason in two taps at the machine. The Pareto, the trends and the accountability build themselves.
Auto stop detectionHMI touchscreen 3.5–10"QR scanningInterlocking — enforced captureWeb page loggingLCD 16×2 + keypadPareto & trends
The problem it kills
You can't fix downtime you never recorded.
MEMORY
Shift-end fiction
Downtime logged from memory at shift end is fiction with a signature. Auto-detection makes the timeline true before anyone touches it.
VAGUE
“Machine problem” is not a reason
Free-text logs produce unanalysable mush. Structured reason trees — Management, Operational, Quality, Maintenance — produce Paretos.
REPEAT
Chronic stops look normal
The same 6-minute stop, four times a shift, forever. Recurrence analysis surfaces the chronic losses everyone stopped seeing.
How it works
Downtime Reasons Capture, the MachineWise way.
Deployed software-first in under an hour, included in one subscription — no per-module licensing.
CAPTURE
Detection you don't operate
- Stops detected from machine signals automatically
- Duration accurate to the second
- Idle vs breakdown vs setup pre-classified
- Works on CNCs, lines and hardwired machines alike
EXPLAIN
Reasons in two taps
- Operator tags reason at the machine kiosk
- Custom reason trees per plant and machine type
- Photos and notes attachable to major stops
- Unexplained stops escalate automatically
ACT
Paretos that drive meetings
- Top-loss Pareto per machine, line and plant
- Trend lines: is this reason growing or dying?
- Crew and shift comparisons on identical machines
- Exports for your morning meeting, automatic
To the secondStop detection accuracy
2 tapsFor an operator to tag a reason
Self-buildingThe Pareto assembles itself
Capturing downtime
Four ways to log a stoppage reason.
Different floors, different habits, one rule: capture must be effortless at the machine. Pick per machine — mix freely across the plant, all four land in the same Pareto.
01
HMI touchscreen
3.5", 5", 7" and 10" panels mounted at the machine — big targets, glove-friendly, two taps to a reason.
02
QR scanning
Scan a printed reason code with MachineWise device alongwith Interlocking capability.
03
Web page
Log reasons from the MachineWise webpage on any browser — supervisor desk, shared tablet or the operator's own phone.
04
LCD + keypad
Simple 16×2 LCD with keypad — the lowest-cost option, rugged enough for the dustiest corner of the floor.
One QR. Four jobs.
The same scanner runs your whole floor.
QR isn't just for downtime. One scan workflow — any phone, no app training — handles the four interactions your floor repeats hundreds of times a day.
SCAN → START
Start a route card
Scan the card's QR at the machine — the batch goes live, progress starts counting from actual parts.
SCAN → SETUP
Start a setup
Scan to open the setup phase — setup time is captured separately from breakdowns, feeding changeover analytics.
SCAN → LOGIN
Assign operator to machine
Operators scan their badge QR to log in — attribution for OEE, quality and downtime, with zero passwords.
SCAN → REASON
Punch a downtime reason
Scan the reason code on the laminated sheet at the machine — timestamped against the exact stop, instantly.
Interlocking · Enforced capture
The machine waits until the reason is punched.
Voluntary logging always leaks — busy shifts skip entries, and your Pareto quietly turns into fiction. Interlocking closes the loop: after a stop, the MachineWise device holds the cycle-start until a reason is scanned or keyed. Coverage stops being a discipline problem and becomes a property of the system.
HOW IT WORKS
Scan to release
Stop detected → machine held via the MachineWise device's interlock output → operator scans the reason QR or keys it on the HMI/LCD → cycle-start released instantly. The whole exchange takes seconds.
YOUR RULES
Enforce where it earns it
Configure which stops demand a reason — by duration threshold, machine, or shift. Grace periods for micro-stops, supervisor override with attribution, and normal alarms untouched. Safety circuits are never in the loop.
THE PAYOFF
100% reason coverage
Every qualifying stop carries a reason, timestamped at the machine, by the logged-in operator. Paretos you can defend in a customer audit — and act on without arguing about the data first.
Keep exploring
Goes deeper with the rest of the platform.
Ready when you are
See Downtime Reasons Capture running on machines like yours.
A 30-minute walkthrough on a live dashboard seeded with your machine types. No obligation.
Book my free pilot → WhatsApp us