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.
Allowed moves
Retire and Dispose require approval, and are irreversible. Open work no longer blocks
either move — retiring or disposing an asset now cancels what’s open on it instead. See below.
Retiring takes the asset out of circulation
Retire or dispose an asset and it disappears from everywhere a live asset shows up: the In service register, every asset picker used to raise work — work requests, inspections, maintenance plan scope — the Executive dashboard’s fleet-health average, and whatever syncs to the field app. Nothing is hidden or deleted underneath that. The asset’s own detail page, its full history, and every existing reference to it — work orders, RCAs, contracts — stay exactly as they were. The Retired tab lists everything out of service, with when it left service, why, and who recorded it. Some entries show “not recorded” instead — that’s an asset somebody deactivated directly rather than moved through a closed status, and the tab counts how many of those there are.Open work is cancelled, not left behind
Retiring or closing an asset automatically cancels its open work: open work orders, open work requests, and scheduled preventive-maintenance rounds. Cancelled, not skipped — a skipped round would still count against a plan’s compliance, a cancelled one doesn’t. Each cancellation carries an auto-generated reason referencing the retirement. Anything the status model can’t cancel is reported rather than silently forced through — for example: 2 jobs and 17 rounds cancelled, could not cancel WO-2026-00005 (Waiting for Parts). You’ll see that same result both in the bulk-action outcome (see the asset register) and on the asset’s own Lifecycle tab.The default work order status model was corrected so a job can be cancelled from any open or live
state — previously only 3 of its 9 states allowed it. Cancelling still requires a reason. If your
organisation has customized its own work order status model, this fix doesn’t
touch it — you’re on whatever moves you already configured.
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.