An asset registry is the list of equipment the maintenance team is responsible for, with enough about each item to schedule work against it and to find it. It is the first record a CMMS needs and the one most sites have never made, because equipment arrives over years and nobody wrote it down. This page says what the registry holds, how it is built by walking the site, and how cmms asset management uses it as the spine that the schedule, the work orders and the history all hang off.
What the registry holds per asset
A unique asset number. A name a technician recognises. Make, model and serial. Location, as a tree: site, area, line, position. Criticality, from the consequence of failure. The maintenance strategy chosen and why. Meter type, if the asset is on run-hour intervals. Spares held and where. The date installed and, later, the date scrapped. Everything else, the schedule, the history and the certificates, is attached to the asset rather than stored in it.
Building it by walking the site
There is no other way. Start at one end with a numbered label roll and a sheet, and record every item worth a work order: anything that can fail and stop something, anything with a statutory test, anything the team services. Skip what is never maintained. Give each a number and a label. A few hundred assets is a few days for two people, and the walk finds equipment nobody knew was there. The maintenance log worksheet on this site has the registry columns as its first section.
The hierarchy
Assets sit in a tree so that work orders against a component roll up to the machine and the line. A bearing failure on the drive motor of conveyor C2 in packing is recorded against the motor and reported against the conveyor, the packing area and the site. The tree is what lets a manager see which line eats the hours; a flat list cannot. Most CMMS products import the tree from a spreadsheet with a parent column.
How the CMMS uses it
Every preventive task is against an asset in the registry, so the schedule exists only for assets that do. Every work order is against one, so the history accumulates per asset. The reporting rolls hours and downtime up the tree. When an asset is scrapped, its tasks stop; when one arrives, its tasks start. A registry that is not kept current produces work orders against things that no longer exist and none against things that do, which is why keeping it is a task on the schedule itself.
Questions people ask about asset registry
Is an asset registry the same as a fixed asset register?
No. The fixed asset register is finance's list for depreciation; the maintenance registry is the team's list for scheduling. They overlap and are kept for different reasons.
How detailed should the registry be?
Down to the level a work order is raised against. A motor that is replaced as a unit is one asset; its bearings are findings, not assets.
What if the registry is out of date?
Then the schedule is wrong. Walk the site again for the areas that changed, and make registry updates part of the process for installing and scrapping equipment.