An asset register is the central list of all the installations, machines and components you maintain, structured as a hierarchy from site down to component, with a fixed set of data for each asset. Everything in maintenance rests on it: work orders, failure history, costs, preventive tasks and spare parts all hang off a record in the register. A good register also separates the place in the plant, known as the position or functional location, from the physical unit installed there. This article explains how to build such a register, what data belongs in it and how to keep it up to date.
What an asset register is and why everything depends on it
An asset register answers three questions: what do we have, where is it and what do we know about it. Every notification, every work order and every spare part issued is booked against a record in that register. If the register is incomplete or unreliable, so is everything built on it. A pump that appears twice spreads its failure history over two records. An asset that is missing has no preventive task, so that task is never carried out.
The register is also the basis for decision-making. Cost per installation, metrics per asset type and a well-founded replacement decision all need the same backbone, and asset management under ISO 55000 and ISO 55001 relies on the same information. For sites covered by the Seveso III Directive, the directive goes further and explicitly lists an inventory of the establishment's equipment as part of the safety management system, together with a strategy for monitoring the condition of that equipment.
The asset hierarchy: from site to component
An asset hierarchy organises the register as a tree. Every record except the site at the top has exactly one parent, so failures, hours and costs for a pump roll up to the system, the line and the site. A typical structure looks like this:
| Level | Waste-to-energy plant | Manufacturing plant |
|---|---|---|
| Site | North site | East factory |
| Installation or line | Incineration line 2 | Packaging line 3 |
| System | Boiler feedwater | Compressed air |
| Position | Boiler feed pump A | Compressor 1 |
| Asset | Pump with serial number | Screw compressor with serial number |
| Sub-asset | Electric motor | Drive motor |
Torn between a spatial structure (building, floor) and a functional one (installation, system)? Use the functional structure for the tree, because failures and maintenance follow the process. Record the physical location and the cost centre as attributes of the record instead.
How deep you go is decided per asset type. The question each time is: at what level do you plan maintenance, analyse failures and want to see costs? A 250 kW electric motor that you overhaul separately and whose history you want to follow deserves its own record. A €40 bearing that you replace at every pump service belongs in the bill of materials and in the stores, not as an asset in the tree.
A useful reference is ISO 14224, the standard for collecting and exchanging reliability and maintenance data in the petroleum, petrochemical and natural gas industries. It uses a taxonomy of nine levels, from the industry at the top to individual parts at the bottom. The top five levels describe use and location, the bottom four the subdivision of the equipment itself. You don't have to adopt it wholesale, but it helps with a question every register has to answer: where does one asset end and the next one begin? Agree per asset type whether the motor, the coupling and the baseplate belong to the pump or get records of their own, and apply that everywhere. There is more on the standard in the article on failure codes based on ISO 14224.
Position versus asset: the distinction that pays off most
The position, also called the functional location, is the place in the installation that has a fixed function. The asset is the physical unit performing that function at a given moment, identified by its own asset number and the manufacturer's serial number. The position stays; the asset can change.
Take position P-101, the cooling water pump in cooling water circuit 1 at the South site. The pump running there has serial number 21-0457. When it is due for an overhaul, it goes to the workshop and a previously overhauled pump from stores, serial number 19-3318, takes its place. In the register, P-101 simply remains; only the link between position and asset changes. The diagram below shows the swap.
This builds up two kinds of history. The position holds everything to do with the location and the process: how often P-101 fails, the process conditions it pumps under and the drawings that apply to it. The asset holds everything to do with the unit: overhauls, replaced parts, test reports and the running hours of that particular pump.
Keeping the two apart sharpens your analysis. If P-101 keeps failing whichever pump is installed, the problem probably lies in the location: the process, the set-up or the way it is operated. If the same unit keeps failing wherever it goes, the problem lies in the pump itself. Without the distinction between position and asset you cannot tell those two situations apart.
Not everything needs a position. Mobile equipment such as forklift trucks, and portable equipment such as welding sets, is linked to a site or department rather than to a fixed place in a process installation. To see how a maintenance system keeps positions and assets apart, take a look at asset management software.
Tagging and labels in the field
Every position and every asset gets a unique code that is never reissued, not even after an asset has been disposed of. There are two schools of thought. A meaningful code such as P-101 for the first pump in area 1 tells the technician something in the field and matches the drawings. A sequential number says nothing, but never has to change when the installation is rebuilt. Many companies combine the two: a meaningful tag for the position and a neutral sequential number for the asset, because a unit can move.
Power plants often use the KKS identification system for this. If you are designing your own system, IEC 81346 sets out the international rules for reference designations. According to the standard, a reference designation marked on the component itself is the key to finding information about that object across different kinds of documents. More important than which system you choose is that the code on the drawing, in the register and on the label in the field is the same.
Use two kinds of label in the field. The position sign is fixed to the installation, for example on the plinth or the pipework, and stays put when the pump is swapped. The asset label sits on the unit itself and goes with it to the workshop. A QR code or barcode on the label opens the right record on a phone. Choose a label material that can cope with whatever happens at that spot: heat, oil, cleaning agents or sunlight.
What data to record for each asset
Start with a core set that applies to every asset, and make those fields mandatory.
| Field | Why you need it | Example |
|---|---|---|
| Asset number | Unique key that never changes | A-004812 |
| Description | Recognition and search | Centrifugal pump, cooling water |
| Asset class | Sets the template and tasks | Centrifugal pump |
| Position | Where the unit is now | P-101 |
| Manufacturer, model, serial number | Parts, warranty, recalls | Serial number 21-0457 |
| Commissioning date | Age and service life | 14 May 2021 |
| Status | In service, standby, in overhaul, disposed of | In service |
| Criticality | Priority, strategy and stock | A |
You determine criticality with an asset criticality analysis. Without that field you cannot prioritise work and spare parts on solid grounds.
For each asset class, add the technical attributes you need for maintenance and for ordering parts. For a centrifugal pump that might be flow rate, head, speed, impeller diameter and seal type; for an electric motor, rated power, voltage, speed and bearing types. Create a fixed template per class with mandatory and optional fields, and use pick lists wherever you can. ISO 14224 treats equipment attributes as a standard category of data and lists the equipment it covers in an annex, which makes it a useful starting point for your own templates.
The record also carries the related technical documentation, the bill of materials with spare parts, warranty details and the supplier. How documents and assets are linked is shown under technical document management.
How to set up an asset register in seven steps
- Define the purpose and scope. Which decisions should the register support, and which sites, installations and asset types are in scope? Start with what you maintain and leave things like office furniture out of the first round.
- Set the hierarchy and coding rules. Describe the levels you use, how deep you go per asset type, how codes and descriptions are built and what counts as a position and what as an asset. This short document stops three people doing it three different ways.
- Take stock. Gather what already exists: existing lists, maintenance records, purchasing data and P&IDs with their tags. Then check everything in the field with a walkdown per system: walk the installation, photograph the nameplate and record what is actually there. Lists and drawings almost always lag behind reality.
- Fill in the core data. First the core set for all assets, then the class-specific attributes, starting with the critical installations. If you are moving the data into a new system, clean it up beforehand; otherwise duplicate records and obsolete assets simply come along (see CMMS implementation).
- Label in the field. Fit position signs and asset labels with exactly the same codes as in the register. Label each system straight after its data has been entered, so that label and register match from day one.
- Link documents and parts. Manuals, drawings, certificates and the bill of materials. Only then can a technician find everything the job needs, starting from the label.
- Make it stick. Set out who may make changes, who owns each area and what happens on replacement, relocation, extension and demolition. Make updating the register a fixed step when closing work orders and in every modification project.
Data quality: complete, correct and current
A register is never finished. Monitor its quality on three points:
- Completeness. What share of the mandatory fields is filled in, per asset class? A register that knows every pump but lacks the model for half of them is no help to the buyer.
- Accuracy. Does the record match reality? Check with a sample, for example twenty random assets every quarter, and compare record and field.
- Timeliness. How long does it take between a change in the field and the update in the register? Days is fine, months is a problem.
If you want a more structured approach, ISO 55013 gives guidance on managing data so that it keeps supporting your asset management objectives.
Common mistakes when setting up an asset register
- Too detailed or too coarse. Every bearing as an asset makes the register unmanageable; only "line 3" as an asset makes history per machine impossible.
- No distinction between position and asset. After the first swap the history is wrong: the record is overwritten with the new serial number and the old pump's failures are attributed to the new one.
- Duplicate records. The same pump twice, for example after a migration or because one department enters "P-101" and another "P101". History and costs end up scattered.
- No owner. If everyone can make changes and nobody is responsible, the register degrades quickly.
- The register lags behind. A replaced motor or a new pump that never gets recorded makes every subsequent work order at that position less reliable.
- Free text where a pick list belongs. "Pump", "pmp", "CP" and "centrifugal pump" as asset classes make any analysis by type impossible.
Frequently asked questions
What is the difference between an asset register and a fixed asset register?
The maintenance asset register describes what you maintain, down to the level at which you plan work and analyse failures; the fixed asset register in your accounts describes what the company owns and depreciates. Finance often records an installation as a single investment, while maintenance wants to book down to the pump and the motor. Link the two through an asset or investment number so maintenance costs land on the right investment, but keep them as separate lists, each with its own level of detail.
Can you keep an asset register in Excel?
For the initial inventory and a small installation, yes, and many registers start out that way. The limits arrive quickly: Excel or any other spreadsheet keeps no history per position and per asset, does not record who changed what, and is disconnected from work orders and stock. Use a spreadsheet as a working file to collect and clean the data, then manage the register in a system where work orders and history hang off the same records.
What is the difference between an asset register and a CMMS?
The asset register is the structured list of what you maintain; a CMMS is the system in which you manage that register along with notifications, work orders, preventive tasks and stock. The register is the foundation the rest of the system runs on. A CMMS with a poor register therefore delivers little, and a good register that is not linked to work orders remains a list that quickly goes out of date.
Who should be responsible for the asset register?
Appoint an owner for each area or installation who looks after the content, plus one administrator who guards the rules for structure, coding and templates. Technicians and planners report discrepancies they spot in the field, but do not make structural changes themselves. That keeps the register consistent without every correction having to go through one person, and everyone knows where a change request ends up.
What do you do with an asset that is disposed of?
Don't delete the record; set its status to disposed of, with the date and the reason. The history of that unit then remains available for analysis, warranty claims and later questions, and the asset number is never reissued. If the position stays because a new unit is coming, link the new asset to the same position. If the function disappears as well, close the position in the same way.