Key takeaways
It has to produce evidence on demand for four things. One, a complete and structured asset register, with a hierarchy that reflects how the plant is really built and criticality recorded as a field you can sort and filter on. Two, a traceable line of sight, so an auditor can follow an organisational objective down to a maintenance plan and then to individual jobs on real assets. Three, execution evidence, meaning planned versus completed work with dates, durations and the person who did it, not a tick in a column. Four, performance data that is measured, reviewed and demonstrably fed back into the plan.
Fabrico covers these through a machine registry holding documents and full history per asset, annual preventive maintenance planning with recurring templates, conditional tasks and approval workflows, and analytics for downtime, MTTR and MTBF, task distribution and top problem machines, all exportable to Excel for an audit pack. Multi-plant views and cross-plant benchmarking cover a multi-site scope, and an audit log records who changed what. The company itself holds ISO 9001, ISO 27001 and ISO/IEC 20000-1.
ISO 55001 sets out the requirements for an asset management system. It sits inside the ISO 55000 family alongside ISO 55000, which gives the overview and vocabulary, and ISO 55002, which gives application guidance. The family grew out of the British standard PAS 55 and was first published in 2014, with a revised edition issued in 2024. Certification is available from accredited bodies, and unlike ATEX or CE marking it applies to your organisation, never to a supplier's product.
The standard follows the Harmonised Structure, the common 10 clause skeleton shared with ISO 9001, ISO 14001, ISO 45001 and ISO 27001. If you are already certified to one of those, your context analysis, leadership commitments, competence records, internal audit process and management review cycle are largely transferable. That is the single biggest cost saving available and most teams discover it late.
Four ideas do the real work.
Value. Assets exist to deliver value against organisational objectives, not to be maintained for their own sake. In practice this means you must be able to explain why a given maintenance regime exists in terms of what the business is trying to achieve.
Alignment, or line of sight. The organisational plan drives a strategic asset management plan, which drives asset management objectives, which drive asset management plans, which drive the work that actually happens. An auditor will pick one job at random and walk backwards up that chain. If the chain breaks, the finding is written against alignment.
Leadership. Top management has to own the policy and the resourcing, which is why ISO 55001 projects that live entirely inside the maintenance department stall.
Assurance. You have to demonstrate that assets will perform as required, which means monitoring, measuring and reviewing, not asserting.
Alongside those, clause 7 on support carries the requirement that has the sharpest software consequence: information requirements. You must determine what asset information you need, specify its quality and how it will be managed, and keep it consistent and traceable across the organisation. A spreadsheet where three plants use different naming conventions and nobody knows which version is current does not satisfy this clause, and it is the most common reason a first audit produces findings.
1. Asset hierarchy with real depth. The register must model site, area, line, machine and component, because criticality and cost roll up through that structure. A flat list of machine names cannot answer the question "what does this line cost us to maintain", which is a question an auditor will ask in some form. Our asset hierarchy guide covers how to design one that survives contact with a plant.
2. Criticality as a structured field. ISO 55001 expects risk to drive decisions. That means criticality has to be a value on the asset that you can filter and report on, derived from a documented method rather than from opinion. See our guide to asset criticality analysis for the scoring approaches. The auditor's question is rarely "is your criticality right", it is "how did you arrive at it and is it applied consistently".
3. Plan versus actual, with history. Preventive maintenance compliance is the workhorse metric of an asset management audit. You need to show scheduled work, completed work, completion dates against due dates, and the reason where work was deferred. A system that overwrites the schedule when a job is rescheduled destroys exactly the evidence you are being asked for, so check how deferrals are recorded before you buy.
4. Performance measurement and review. Clause 9 requires monitoring and evaluation of both asset performance and the performance of the management system itself. Downtime, MTTR, MTBF, backlog age and cost per asset are the usual set. The important test is not whether the software can display them but whether it can produce them for a defined period, filtered to a defined scope, and export them into a review pack.
5. Export and traceability. Auditors work in documents. A system that shows beautiful dashboards but cannot export the underlying records to Excel with dates and user attribution creates work rather than removing it. Confirm export at record level, not just chart level.
Question 3 is the sleeper. Many systems treat a reschedule as an edit rather than an event, which quietly erases the deferral history an auditor wants to see. Ask for a demonstration rather than a yes.
Fabrico is a combined CMMS and OEE platform. Against the five capabilities above: a machine registry with hierarchy, files and full history per asset; an annual preventive maintenance plan with recurring templates, conditional tasks, approval workflows and defined work shifts; analytics covering downtime, MTTR and MTBF, task distribution, top machines and per-employee productivity, with Excel export and customisable dashboards; an audit log; and multi-plant views with cross-plant benchmarking for organisations certifying more than one site.
Inventory is included, covering catalogue, minimum and maximum levels, deliveries, consumption tied to work orders and stock-takes, which matters because ISO 55001 treats spares as part of the asset system rather than as a separate procurement problem. Data can move in and out through Excel import and export, a REST API, webhooks and a bidirectional SAP PM sync including S/4HANA.
On the OEE side, availability, performance and quality are calculated from PLC data, with IoT sensors or AI cameras where a machine offers no usable signal. That gives asset performance evidence measured at the machine rather than reported by a person, which is a materially stronger form of evidence in an audit.
Setup on the CMMS side is quoted as 3 days of Fabrico-side work covering configuration, users, roles and bulk import of your register, with bulk import support included. Machine connection for OEE is a separate exercise paced by your equipment and by line access, so plan those two as separate timelines. Support response is contractually under 2 hours, and the interface is available in English, Bulgarian, German, French and Polish.
Two limits worth stating so they do not surprise you during a gap analysis: Fabrico does not include a production planning module, and failure prediction is delivered as custom work for specific clients rather than as a standard feature. Neither is required by ISO 55001, but both appear on many internally written requirement lists, so check whether yours actually needs them.
Take a manufacturer with two plants, roughly 1,400 assets between them, maintenance run on a mix of a legacy work order tool and spreadsheets. Certification is targeted for the following year, driven by a customer requirement rather than by internal enthusiasm.
A gap analysis against ISO 55001 typically returns the same shortlist. The asset register is incomplete and the two sites use different naming, which fails the information requirements clause. Criticality exists as a colour in a spreadsheet at one site and not at all at the other. Preventive maintenance compliance cannot be reported for a past period because deferrals overwrote the schedule. There is no traceable link from the business plan to the maintenance regime. And no one can produce twelve months of MTBF for the top twenty assets.
Every one of those five is a data and system problem before it is a documentation problem. The sequence that works is: agree one taxonomy across both sites first, then import the register into a single system with criticality as a required field, then build the preventive plans inside that system so compliance is measurable from day one, and only then write the strategic asset management plan, because it is far easier to write once the data underneath it is real.
Teams that write the documents first almost always rewrite them, because the plan describes a system that the data cannot support. The documentation is the last step, not the first, and this is the single most useful piece of sequencing advice in the whole exercise.
No. ISO 55001 specifies requirements for an asset management system within an organisation, and certification is issued to organisations by accredited certification bodies. Software is not in scope for certification under the standard. A vendor can legitimately say its platform supports ISO 55001 requirements or is used by certified organisations. A vendor claiming to be ISO 55001 certified software has either misunderstood the standard or is relying on you doing so.
Not the same, but directly related. PAS 55 was a British Standards Institution publicly available specification for physical asset management and was the main input into the ISO 55000 family. Organisations certified to PAS 55 generally transitioned to ISO 55001. The ISO standard is broader in the types of asset it addresses and uses the common management system structure shared with ISO 9001 and others.
Not strictly. The standard requires outcomes and evidence, not a specific tool, and a very small organisation with a handful of assets can meet it with disciplined records. In practice, once you pass a few hundred assets across more than one site, producing consistent, traceable, period-specific evidence by hand costs more effort than the software does and it fails more often. The audit is annual, but the evidence has to be continuous.
They share the Harmonised Structure, so clauses 4 through 10 follow the same skeleton: context, leadership, planning, support, operation, performance evaluation and improvement. Your existing document control, internal audit programme, corrective action process, competence records and management review can be extended to cover asset management rather than rebuilt. What is genuinely new is the strategic asset management plan, the line of sight requirement, and the treatment of asset information as a managed thing in its own right.
Broken line of sight. Organisations produce a good policy and a good strategic asset management plan, and separately run a competent maintenance operation, but cannot demonstrate the connection between them. The fix is not more documentation, it is making the maintenance plans in the system explicitly reference the objectives they serve, so that walking backwards from a work order to an objective is a matter of reading fields rather than reconstructing intent.
If you are scoping a register import or need to see plan versus actual reporting against a real hierarchy, start with how the performance side is calculated or book a demo and bring a sample of your asset list.
Last updated: 7 August 2026.
Login
Blog