Knowing what you own: asset management that holds up

Enterprise asset management is running the equipment you own across its whole life: what you bought, what it costs to keep, what condition it is in, and when to replace it. Maintenance is one chapter of that story. The register underneath it is the part everything else depends on.

Almost every asset list is wrong in the same three ways: it contains equipment that was scrapped years ago, it is missing equipment nobody ever recorded, and half the entries have no location precise enough to walk to. This guide is about building one that stays true.

What an asset record actually needs

Vendors will offer you sixty fields. Nine of them do work. Everything else can be added later by somebody who has a specific reason.

• •A name in the pattern everybody uses, not the one on the nameplate
• •Where it is, precise enough to find without asking anybody
• •What it is: a type from a short list, so you can group and compare
• •Make, model and serial number, for parts and for warranty claims
• •When it went into service, and its expected life
• •What it cost, and what replacing it would cost today
• •A scannable code fixed to the thing itself
• •Who is responsible for it
• •Its criticality band

The naming rule that saves years

One pattern, applied everywhere, even where it looks silly. Something like building, system, type, number. AHU-3 in the second floor plant room of Building B becomes B-L2-AHU-03 and stays that way forever.

The reason is not tidiness. It is that a consistent name sorts, groups and searches, and an inconsistent one means you can never count how many air handling units you own. Teams that get this wrong spend a fortnight fixing it two years later, always.

Put the code on the thing

A code fixed to the machine that opens its record does three jobs at once: work gets filed against the right equipment, a scan proves somebody was there, and the manual and history arrive at the moment somebody needs them. It also makes the register self-correcting, because equipment nobody can scan gets noticed.

How deep to go

The common mistake is recording every component. A pump is one asset. Its seal, bearing and motor are parts, not assets, unless you maintain them separately and want their own history.

The test: would you ever raise a job against this on its own, and do you want to see its failure history separately? Two yes answers make it an asset. One or none makes it a part.

Build the hierarchy so rollups work

Site, then building, then floor or area, then system, then equipment. That structure means a question like "what did the heating in Building B cost last year" is answerable without anybody tagging things by hand, and it survives a building being sold.

The four things a good register lets you answer

• •What is this, when was it last touched, and by whom
• •Which of these have failed more than twice this year
• •What do we own that is past its expected life, and what would replacing it cost
• •If this building closed tomorrow, what is in it

Keeping it true

A register decays about as fast as a building changes. Three habits stop that.

• •Nothing gets installed without being added, which means the person accepting the work adds it
• •Nothing gets removed without being marked removed, with a date, rather than deleted
• •One walk a year per building, list in hand, looking for both kinds of error

Where to start if your list is a mess

Do not clean everything. Take the equipment that has failed in the last year, get those records right, and put codes on them. That is the equipment your record needs to be true about, and the rest can be corrected as work touches it.