Skip to main content
An asset has a life: it is bought, commissioned, run, repaired, eventually retired. The status records where in that life it is right now. These are the defaults. Like every lifecycle in the product, they are configurable.

The states

Down against Under Maintenance

The difference matters, and it is the one people get wrong.
  • Under Maintenance — you chose to stop it. Planned work.
  • Down — it stopped on you. This is what counts as downtime, and what availability and MTBF are computed from.
Taking a machine off line for a preventive round and marking it Down will make your availability figures worse than the plant actually is.

Allowed moves

Retire and Dispose require approval, and are irreversible. An asset with open work orders cannot be retired — clear the work first.

Where states get changed

  • On the asset, from the action bar.
  • From a work order — reporting a breakdown against a machine takes it Down; returning it to service brings it back.
  • From the field app, where a technician can put a machine down or return it to service at the machine.
Every change is recorded on the asset’s Lifecycle tab with who made it and when.

Retirement and replacement

Reliability is where the argument for retiring a machine gets made: cost to maintain against cost to replace, failure count against the rest of the fleet, and a recommendation you can accept or dismiss.