04.5
Predictive action
Does the organisation act on what it expects to happen, or only on what has already happened?
What goes wrong without it
This is the clearest signal of intent in the 2024 revision. Preventive action, which asked what might go wrong, has been renamed predictive action and rewritten, which shifts the question towards when to intervene rather than whether to. For an asset-owning organisation that is a different discipline: it requires condition data, deterioration modelling and a funding mechanism that can act before failure. Most organisations have none of the three and describe their run-to-failure regime as risk-based.
What to examine
- Ask for one intervention whose timing was set by predicted condition rather than by failure, calendar or budget availability.
- Check whether renewal, replacement and disposal timing is optimised together or handled by separate teams on separate cycles.
- Establish whether the data required to predict anything is actually being collected, and at what interval.
- Test whether deferred maintenance is quantified and reported anywhere the board sees it.
Required by
- ISO 55001:2024, Clause 10.3, predictive action, renamed from preventive action and fully technically revised, and listed by ISO among the main changes from the 2014 edition.
- ISO 55001:2024, Clause 10.1, continual improvement, and Clause 10.2, nonconformity and corrective action.
Read the sources
- ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.
In the asset lifecycle method
The steps of the two methods that this domain examines.