Asset Register Template

Most organizations believe they have an asset register and actually have an asset list, and the difference is not how many rows it has. A list tells you what exists. A register tells you what to do about it, and that only happens when four specific columns are populated: a unique code that never changes, a parent so things roll up, a criticality rating that decides the regime, and an assigned maintenance regime that follows from the rating. Strip any one of those out and the file stops driving anything. Without the code and the parent you cannot attach history or roll cost up to a system. Without criticality every asset competes equally for attention, which in practice means attention goes to whatever broke most recently. Without a PM regime the register is a description of a building rather than a plan for it. This is why section five scores the register against itself rather than simply counting rows: a file with two hundred assets and ninety percent of the serial numbers missing is not ninety percent of a register, it is a list with aspirations. The second thing worth stating plainly is that criticality has to come from a written rule rather than from the judgment of whoever happened to do the survey. Surveyors are not wrong so much as inconsistent: the person who walks the plant room rates the chillers critical because they are standing in front of them, and the person who walks the roof rates the extract fans critical for the same reason. Rated by rule, against consequence of failure, the distribution usually comes out somewhere near a tenth critical and the rating starts deciding things again.

Eighty five percent and ninety two percent look like good scores, and the thirty two assets with no serial number are the ones that will cost somebody a warranty claim. Completeness percentages are seductive because they are high by construction: the easy fields, asset ID, description, location, are filled in during the survey and carry the average. The fields that get skipped are skipped for a reason, which is that capturing them is tedious and the person doing it cannot see who benefits. Serial numbers are the clearest case. Reading one means getting behind the unit with a flashlight, and the value only appears later, when a manufacturer asks which unit failed, or when two identical machines sit in the same plant room and only one of them keeps tripping. Thirty two unserialized assets in a register of this size is not a rounding error, it is a specific afternoon of work with a known payoff, and section five is what turns it into that rather than a vague sense that the data could be better. The eighteen assets with no maintenance regime are the same argument in a more urgent form, because those are the ones nobody has decided how to look after. Eleven assets beyond expected life is the figure to take to a budget conversation, since it is the only forward-looking number here. Replacement value is recorded for renewal planning: what it would cost to put the same capability back today, which is the only figure a maintenance budget can act on. The service history and lifetime cost that attach to each of these assets live on the maintenance log, the regime the criticality rating drives is built on the PPM schedule, and the condition survey that feeds the condition column is the property condition assessment.

The most expensive mistake on this document is not an empty column, it is a coding convention invented on the first morning of the survey. Asset codes propagate immediately and invisibly. They are written onto labels, quoted in work orders, stored against every history record, embedded in reports, referenced in contracts and typed into whatever system the register is eventually loaded into. By the time anybody notices the convention cannot accommodate a second building, or has no room for sub-assets, or encodes a department that has since been reorganized, the cost of fixing it is not the renaming but everything that referenced the old name. This is the one decision in the document worth taking slowly and taking to other people, because the surveyor is rarely the person who will live with it. A convention that handles site, building, floor, room, system, asset and sub-asset, with a stated owner for each level, survives reorganizations and acquisitions in a way that a convention built around the current org chart does not. The second thing worth protecting is the disposal rule. When an asset goes, the instinct is to delete the row, and the row is carrying the entire cost and failure history of that asset, which is the only evidence you have about how that model behaves in your buildings. Marked disposed it remains available for the next purchasing decision. Deleted it takes everything it taught you with it. The service history itself lives on the maintenance log, and the routine work the register's criticality drives is scheduled on the preventive maintenance plan and checked with the equipment maintenance checklist.