Depth 0 m · SurfaceModule 04 / 13

When iron stops, the clock starts.

A breakdown is reported from the field in one tap — photo attached — and the machine's status flips itself. From that second, downtime is measured, not remembered.

Down now9
Reported today4
Under repair3
Back today5
Avg response26 MIN
The Solmex breakdown register showing active breakdowns with the machine, the fault category, the current status, how many days the machine has been down and the expected return to service.
Days down is measured, not typed. The machine's status flips itself when a fault is logged.
Depth −10 m · One breakdown, measuredBD-0187
BD-0187EX-014 · HYDRAULIC FAILURE
Total downtimeREPORTED 07:42 · BACK 19:04
11 H 22 M
Reported from the field07:42 · OPERATOR · 2 PHOTOS
Machine auto-flagged “breakdown”07:42 · FLEET BOARD UPDATED
Work order WO-2026-0341 raised07:58 · PRIORITY: CRITICAL
Back in service19:04 · STATUS DERIVED FROM REPAIR
status is derived from the timelinenever hand-picked

Breakdowns

The whole site knows in seconds.

The fleet board turns red the moment the report lands — no phone chain, no morning-meeting surprise. And because status is derived from what actually happened, nobody can quietly mark a dead machine “active”.

Depth −20 m · What it carries03 STATIONS
REPORT

One tap from the field

Operators report from the mobile app with photos and a note — no forms, no radio relay. The report carries the machine, the location, and the clock, automatically.

Average time to first response26 MIN
SYNC

Status flips itself

Reporting a breakdown flags the machine fleet-wide; closing the repair restores it. Derived status means the register, the dashboard, and reality always agree.

Mean time to repair14.2 H
MEASURE

Downtime to the minute

Every breakdown carries its own stopwatch — reported to resolved. Recurring failures surface by machine and by cause, and the repair itself is tracked as a work order, so the fleet learns from every stop.

Downtime events captured100%
Depth −30 m · Questions from the surface04 ANSWERS

Questions about breakdown management

01How is downtime measured?

From the moment the fault is reported to the moment the machine is back in service, to the minute, on the machine's own record. The machine's status flips to breakdown by itself when a fault is logged and back when it is resolved, so fleet availability reflects what is actually happening rather than what somebody remembered to update.

02What if a breakdown was logged by mistake?

It is cancelled, not resolved. Resolving means the failure happened and was fixed; cancelling means it did not happen. A cancelled breakdown leaves every statistic: it is not counted as downtime, not counted in the month's completions, and not counted in the repeat-offender ranking. The record is withdrawn and kept, never deleted, because it is the evidence of what was retracted and why.

03Can we use our own failure categories?

Yes. The failure taxonomy is a tree you own, seeded with a default you can then rename, extend, re-code or archive. Renaming a code reaches every record filed under it; archiving one stops it being used on new records without changing what an existing record says.

04Is there a report for management?

Yes, an A4 landscape breakdown status report built to be read in under a minute and to survive being printed in black and white: fleet availability with its trend, the longest current downtime, an age band per breakdown, ranked insights, and one dense row per breakdown. Every age band carries a word as well as a colour, because colour alone does not print.

Depth −40 m · Below the waterlineREADINGS

Availability is won back one breakdown at a time.

Fleet availability93.5%
Mean time to repair14.2 H
Average first response26 MIN
Breakdowns that skip the record0

See a field report land, the fleet board flip, and the work order open itself — live, in a 30-minute walkthrough.

NO COMMITMENT · YOUR DATA STAYS YOURS

Prev · Work Orders Next · Inspections