Almost every industrial operation we work with has attempted to build an asset register at some point. Many have tried multiple times. And a significant proportion of those attempts have ended the same way — with an incomplete spreadsheet, a partially populated CMMS, or a database that was accurate for about three months before maintenance reality made it irrelevant. The reason asset registers fail is rarely technical. It's almost always structural.
Asset registers built without a clear criticality foundation and ownership model consistently degrade within 12 months. The failure mode is predictable — and so is the fix.
An asset register is not a list of equipment. A spreadsheet with equipment tags and descriptions is a starting point — it becomes an asset register when it includes hierarchy, criticality, technical data, maintenance history, current condition, and cost data.
Without these elements, you have a tag list. Tag lists are not worthless — they are the foundation. But confusing a tag list with an asset register leads operations to believe they have asset management capability when they don't. The gap only becomes visible when you try to do something with the data — plan a maintenance budget, prioritise a capital replacement program, or assess the reliability of a system — and discover the data isn't there.
A well-built asset register answers these questions at the individual asset level: What is it? Where is it? What does it do? How critical is it? What has happened to it? What is its current condition? What will it cost to maintain and replace? Operations with this data make better decisions, faster, with less risk. Operations without it make the same decisions with worse information — and often find out about the gap at the worst possible moment.
The most common mistake is attempting to register every asset on site before understanding which assets are critical. This produces enormous data collection effort, slow progress, and a team that loses momentum before completing the most important work. When the project stalls — which it does — the result is a partial register biased towards whatever the team happened to get to first, which is rarely the assets that matter most. Start with criticality. Define it formally, apply it to generate a ranked list, and build your asset register from the top down.
Asset registers built by engineers tend to be too detailed — capturing specification data that nobody will ever use. Asset registers built by administrators tend to be too shallow — capturing enough to identify the asset but not enough to plan maintenance or make replacement decisions. The right level of detail is: enough to plan maintenance, assign work orders, and make replacement decisions. Not more. Not less. The test is simple: could a maintenance planner use this data to plan a PM without having to go to site to collect basic information? If not, it needs more detail.
An asset register without clear ownership degrades immediately. Assets change — through modification, replacement, relocation, or decommissioning. Maintenance history accumulates. Conditions change. Someone needs to be responsible for keeping the register current as these events occur. In most organisations, this responsibility doesn't exist as a formal role — which means it falls to nobody. Defining ownership explicitly, including the triggers that require a register update and the process for making those updates, is not optional. It is what separates a register that works from one that was accurate once.
If the asset register is not connected to how maintenance work orders are raised, executed, and closed, it becomes a parallel system that nobody uses. The maintenance team does their work in the CMMS (or on paper), and the asset register becomes something that gets updated once a year when someone remembers it exists. Integration with the maintenance execution process is not a technical nice-to-have — it is the mechanism by which the register stays current. Every completed work order that is not closed against the correct asset with meaningful completion notes is a missed opportunity to build the maintenance history that makes the register valuable.
An asset register is not a project with a completion date. It is an ongoing operational discipline. The data degrades the moment it stops being maintained — and data degrades faster in industrial environments than in most others, because the physical assets change frequently. Building it is the easy part. Sustaining it requires process, culture, and accountability. Operations that treat the initial build as the goal invariably end up rebuilding it every few years — paying the cost of the initial build repeatedly without achieving the ongoing value.
A structured approach removes the failure modes above. The steps below are sequential — each one creates the foundation for the next.
Establish a consistent hierarchy before collecting any data. Site → Functional Location → System → Equipment → Component. This structure determines how you search, filter, and report. Changing it after data collection is painful — getting it right first is worth the planning time.
Define formally what makes an asset critical for your specific operation. Consider safety consequence, production consequence, environmental consequence, and cost consequence. Apply these criteria consistently across all assets using a matrix or scoring tool.
Register your top 20% of critical assets first — completely, with full technical data, specifications, and maintenance history. This is where you get the most value fastest, and it builds momentum and confidence in the process.
For each critical asset, identify the key failure modes and the maintenance tasks that address them. This is the link between the asset register and the maintenance program — the point at which data becomes operational value.
Every maintenance task should be executable as a work order linked to the asset. Every completed work order should update the asset's maintenance history. If your current system doesn't support this cleanly, this is the right moment to evaluate whether it is fit for purpose.
Define who updates the register when an asset is modified, when a failure occurs, when a replacement is made. Define the triggers, the process, and the accountability. Then train the people responsible and check compliance.
Asset registers can be built in spreadsheets, standalone databases, CMMS platforms, or purpose-built asset management systems. The technology matters less than the process. A well-maintained spreadsheet delivers more value than a poorly-maintained enterprise CMMS. That said, purpose-built systems significantly reduce the cost of keeping data current, provide better reporting capability, and make the integration with work order management more natural.
The selection of a system should follow the definition of requirements — not precede it. Many organisations purchase CMMS systems before they have a clear view of what they need the system to do, and spend months configuring a tool around a process they haven't yet defined. Start with the process. Then select technology that supports it.
A well-built asset register is the foundation of every effective maintenance and reliability program. Without it, maintenance planning is guesswork. Budget forecasting is unreliable. Reliability improvement is impossible to measure. With it, you have the visibility to plan, the data to improve, and the foundation to build a maintenance program that performs.
ASE Engineers builds asset registers and implements asset management programs for industrial operations across Western Australia.
