ISO 55001:2024 in Plain English
ISO 55001 has a reputation as a standard for water utilities, rail networks and councils with asset management departments. Most teams I talk to assume it's not for them.
That's partly true. Most organisations moving off a spreadsheet are not about to book a certification audit. But the standard is the best checklist that exists for running assets properly, and the 2024 edition made it more useful, not less. Even if you never certify, it tells you what "good" looks like.
I spent eight years on mission-critical asset management at Thales and Hitachi Rail. This is the guide I'd want if I were starting from a spreadsheet today.
What ISO 55001 is, and what it isn't
There are three documents in the family:
- ISO 55000 gives the overview, the principles and the vocabulary.
- ISO 55001 sets out the requirements. It's the one organisations get certified against.
- ISO 55002 is guidance on how to apply those requirements.
Two things trip people up.
First, ISO 55001 certifies an organisation's asset management system, not a piece of software. The "system" is your policy, your decisions, your plans, your people and your evidence. A tool can hold a lot of that evidence. It cannot be certified on your behalf.
Second, it is not a maintenance standard. It doesn't tell you how often to service a pump. It asks whether you know what your assets are for, how you decide what to do with them, and whether you can show that those decisions were made the way you said they would be.
What changed in 2024
ISO 55001:2024 replaced the 2014 edition. Certified organisations had until mid-2025 to transition. The structure is familiar. Five changes affect day-to-day work.
A decision-making framework (clause 4.5). This is the biggest change. You now need a defined, documented way of making asset decisions, with criteria that link back to the value your assets are meant to deliver. It scales: a small organisation can have a simple framework. But "the maintenance manager decided" is no longer enough on its own.
Data and information get their own clause (7.6). You need to know what information you require about your assets, and be able to trust it. Data with gaps, duplicates and no provenance is now a visible weakness.
The strategic asset management plan (SAMP) is clearer. It now has its own subclause and acts as the bridge between organisational objectives and the plans for individual asset classes.
Knowledge is an explicit requirement. You need a plan for keeping asset know-how when the person who holds it leaves.
Life cycle and climate. Operational planning now clearly covers the whole asset life cycle, from acquisition to disposal. Climate change has also been added to the things you must consider when you look at your organisation's context.
Where software helps, and where it can't
Around half of ISO 55001 is about governance and people, and half is about evidence. Software is very good at the second half.
| Area of the standard | What an auditor wants to see | Where it lives |
|---|---|---|
| Context, policy, leadership | A policy, defined scope, named responsibilities | Mostly your organisation, stored as controlled documents |
| Decision-making (4.5) | Criteria, and evidence that decisions followed them | Software can record every decision with its reasons |
| Risks and objectives | Asset risks identified, objectives with measures | A risk register and KPIs linked to real asset data |
| Data and information (7.6) | Defined information needs, data you can trust | Required fields per asset class, data quality checks |
| Competence | The right people doing the work | Qualifications linked to who gets assigned the job |
| Operations, change, outsourcing | Planned work, controlled changes, contractors managed | Work orders, PM schedules, change requests, SLAs |
| Monitoring, audit, management review | Performance measured, internal audits done, reviews held | Dashboards, audit records, generated review packs |
| Improvement | Problems found, fixed and followed up | Corrective actions linked to failures and findings |
If a vendor tells you their product makes you ISO 55001 compliant, ask them who wrote your asset management policy.
Starting from a spreadsheet
If you're still on Excel, the standard can feel like a long way off. It's closer than it looks, because most of the early work is getting your house in order, and you need to do that anyway.
1. Build one asset register you trust. One record per asset, with an owner, a location and a class. If you have three spreadsheets that disagree, that's your first job. Our guide to migrating maintenance data covers how to do it without losing your history.
2. Rate criticality. Not every asset deserves the same attention. A simple consequence-of-failure score on each asset is the foundation for risk, planning and decisions. Start with high, medium and low.
3. Keep the history. Every repair, inspection and replacement is evidence. When you move systems, bring the service history with you. An auditor will ask what happened to each asset, as well as what you have.
4. Write down how you decide. Before you need a formal framework, agree three or four criteria for repair-or-replace decisions: cost, risk, performance, and anything that matters in your sector. Then record which ones you used each time. That's the seed of clause 4.5.
5. Pick a handful of measures. PM completion, unplanned downtime, cost per asset. Measured consistently, a few numbers beat a dashboard nobody reads. See our maintenance KPIs guide.
Do those five things and you have most of the raw material the standard asks for. What remains for certification is governance and documentation, built on what you already have.
Should a smaller organisation bother?
If a client, a regulator or a tender requires certification, then yes. You'll want an experienced consultant alongside you too.
If not, I'd still use the standard as a framework, because its questions are the right ones. Do we know what we own? Do we know why we're keeping it? Can we show how we decided? Organisations that can answer those spend less on their assets and get fewer surprises.
Would ISO 55001 support in AssetOS help you?
AssetOS already covers a good part of the evidence side: asset registers, full service history, preventive maintenance, change requests, audit trails and contractor SLAs.
We're looking at going further: a decision log with configurable criteria, criticality and risk scoring, data quality checks on import, and evidence packs mapped to the standard. Nothing here is built yet, and I'd rather build it with the people who need it.
If ISO 55001 is on your roadmap, tell me where you are with it. I read every reply.
Tell us where you are
Two quick answers help us decide what to build first. We'll email you when there's something to try.
Shane Price
Writing about maintenance management, CMMS implementation, and the real challenges operations teams face.