Reliability¶
Reliability turns your failure and maintenance history into the standard equipment KPIs — MTBF, MTTR, availability, and preventive-maintenance compliance — for every asset, worst first.
Navigate to Asset Management → Reliability for the fleet-wide dashboard, or open an asset's detail page (under Asset Registry) and find its Reliability card.
Where the numbers come from¶
Reliability is built from failure events. A failure event is created:
- Manually — click Log a Failure on an asset's Reliability card and enter when it went down (and, if known, when it was restored).
- From "Report an Issue" — raising a corrective Work Order also logs a linked failure event, unless you clear the checkbox.
- Automatically from VFD trips — a VFD
triportrip-lockalarm lasting longer than a short threshold is counted as a failure for that asset, with no manual entry needed.
Scheduled preventive maintenance and overdue-maintenance reminders are not counted as failures.
Fleet-wide dashboard¶
Pick a time window (30 / 90 / 180 / 365 days) at the top right. The summary strip shows how many assets had failures, the total number of failures, and how many are still open.
The table lists every asset with a failure or an active maintenance plan, sorted so the assets needing attention are at the top:
| Column | Meaning |
|---|---|
| Failures | Number of failures in the window, with an open badge if any are still unresolved |
| MTBF | Mean time between failures. Labelled run-hours when it's based on the machine's run-hour counter, or calendar when based on elapsed time |
| MTTR | Mean time to repair — averaged only over failures that have a recorded restore time or a completed Work Order |
| Availability | Share of the window the asset was in service. For a machine also tracked on OEE, this uses the same downtime log OEE does — a truer figure, since it excludes time the machine was never scheduled to run. Otherwise it falls back to the whole calendar window. Labelled accordingly |
| PM Compliance | Share of the asset's calendar-based maintenance plans that are currently within their interval — a right-now snapshot |
| PMC (period) | Share of scheduled preventive maintenance actually completed over the selected window — a historical completion rate, shown with the completed/expected count behind it |
| PMP | Planned maintenance % — of all the labor hours logged on this asset, the share spent on planned maintenance rather than fixing failures. Shown with the planned/total hours behind it. Only counts hours that were actually entered when logging maintenance or a failure, so it shows as blank until hours start being tracked |
Downtime Breakdown¶
Both the fleet-wide dashboard and an asset's own Reliability card show a Downtime Breakdown panel — the same stoppage reasons logged on the OEE Downtime Log, ranked by time lost, for the selected window. It's blank until stoppages have been logged against that machine.
An asset's Reliability card¶
The card shows the same KPIs for that one asset over the last 12 months, plus its failure history.
Each failure row shows when it started, when it was restored (or an Open badge), its source (manual, corrective work order, VFD…), and the failure mode. With engineer access you can:
- Mark restored — set the restore time to now for an open failure.
- Edit — adjust any detail, including the failure class and mode.
- Exclude from reliability stats — for a false positive (for example a VFD trip that wasn't a real fault). Excluded rows stay visible but greyed out and don't affect the KPIs.
- Delete — remove the entry entirely.
Logging a failure¶
Click Log a Failure and fill in:
| Field | Description |
|---|---|
| Failure start | When the asset went down (defaults to now; you can back-date it) |
| Restored at | When it was back in service — leave blank if it's still down |
| Failure class | Breakdown, minor stop, or defect |
| Failure mode | Free text — e.g. "bearing seizure" |
| Stopped production | Whether the failure halted output |
| Cost | What the repair cost, if known — optional |
| Labor hours | Hours spent on the repair, if known — optional, and feeds the PMP KPI above |
| Notes | Any extra detail |
MTBF basis
Where the platform has run-hour data for a machine, MTBF is measured in running hours between failures — a truer picture than calendar time for equipment that doesn't run continuously. Otherwise it falls back to calendar time. The dashboard always labels which basis a number uses.