If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.
The header
The figures are rolled up per asset per month every night, from work orders and asset status
history. The month in progress is recomputed each night, so its figures move until it closes — read
the trend over the window rather than the newest month.
What to do about it
The recommendations come first, even though this is the smallest section, because it is the only part of the screen that says something ought to happen — and so the only part you can disagree with. The header says how many are open. Each recommendation shows its kind, a severity colour, the asset, the site and the period it looked at, then reads as an argument:P-102 has cost $8,851 to maintain in 12 months — 120% of what it cost to buy — and failed 7 times. Replacement is worth costing.
A Repeat fault is the natural starting point for an investigation on
Root cause, where the pattern is worked through and the actions that come
out of it are followed until somebody can say whether they worked.
Worst first
The assets costing you the most, ranked, with a percentile beside each figure.
The percentiles are the point. “Seven failures” means nothing until it is “seven failures — worse
than 96% of the fleet”. The ranking is worked out across the whole fleet on the server, not across
the rows on screen. worst in the fleet marks the top of each measure.
Month by month
One row per month: Assets counted, Available, MTBF, MTTR, Failures, Emergencies, Planned share (planned work against unplanned), Rounds on time, and Cost.The measures
Every figure comes from the same computation the dashboards and each asset’s
Health tab use, so two screens never disagree about the same machine.
What feeds it
Reliability is only as good as what is recorded:- Failures, classified on the work orders that fixed them — a repair with no failure mode teaches nothing. See failures on Root cause.
- Downtime, from the asset being moved into a status that counts as downtime, such as Breakdown. See the asset lifecycle.
- Costs — labour booked and parts issued on the work orders.
- Closed work orders. Work left open never reaches these figures.
- Purchase cost and Replacement Value on the asset, which the Replace recommendation compares against.
The failure taxonomy
A failure recorded as free text is a paragraph, not a pattern. Under Administration → Failure taxonomy (in the Assets and inventory area) your administrator keeps three separate lists that technicians choose from when they classify a failure:
The screen counts the entries in each list and how many failures have been classified, and shows
whether each entry is in use. Keep modes distinct: two names for the same failure split one problem
into two smaller ones and neither reaches the top of the ranking. A new organisation starts with a
working set in each list that can be renamed, added to or retired. See also
administered lists.