Asset Management

Why the asset register is critical

Registers rot by default. That is not a failure of diligence; it is the natural state of a document that everybody depends on and nobody owns. Kroll’s fixed-asset work finds 10–30% ghost assets — items on the books that no longer physically exist — and up to 65% of records incomplete or inaccurate on a typical register.

The consequences are not administrative. Insurance values are overstated, and so are the premiums. Property tax is overpaid on equipment that was scrapped three renovations ago. The audit arrives and the write-off is a shock to people who thought they knew what they owned. And preventive maintenance is scheduled against assets that do not exist, which means somebody is walking a floor looking for a pump that was removed — while a real asset, on no register anywhere, goes unmaintained.

And the rot starts at handover. NIST priced the cost of poor construction-to-operations data handover at $15.8 billion a year across US capital facilities, with roughly two-thirds of it landing on owners and operators — including $4.8 billion spent simply verifying asset information that should have arrived, structured, on the day the building was handed over. That study is from 2002. It is still the standard citation, which tells you how much has changed.

Read that $4.8 billion again, because it is the whole argument of this page. It is not the cost of missing data. It is the cost of an industry paying, a second time, to find out what data it already commissioned.

The role of the register in performance

• Handover is the golden moment, and it comes once. Equipment lists, warranties, PM schedules, O&M manuals — captured at commissioning, when the people who installed the plant are still standing next to it. COBie is the standard format for delivering that data from construction into operations. Structured capture at handover costs a fraction of re-surveying an operating hotel later, with a torch, at two in the morning, in a plant room nobody has a drawing for. And the warranties are the quiet loss: an asset that never made it onto the register has a warranty nobody claims, and it expires without anyone knowing it existed.

• Hierarchy and componentisation are an accounting requirement, not a preference. IAS 16 requires significant components to be depreciated separately. A register that lumps everything together as “M&E plant” makes a component replacement impossible to derecognise — so the old compressor stays on the books while the new one is added, and the same value is counted twice, permanently. Componentise deep enough that significant-value components can be separately depreciated and derecognised when they are replaced. And no deeper than you can actually maintain, because a register nobody can keep current is a register that will lie to you.

• Criticality drives the maintenance strategy. Rank assets by safety, guest impact and revenue impact against failure likelihood — and that ranking sets PM frequency, spares holding and response priority. Without it, maintenance spend gets spread evenly across everything, which sounds fair and is simply peanut-butter: the critical chiller and the corridor extract fan receive the same attention, and one of them does not need it.

• Three asset universes — and misclassifying them clogs the register. FF&E: furniture, fixtures and equipment — reserve-funded and depreciable. Building systems: plant and infrastructure, the longest lives, managed by criticality. And OS&E: operating supplies and equipment — linen, glassware, crockery — which are expensed and par-level tracked, and which are NOT register items. Put ten thousand glasses on your fixed-asset register and you have not been thorough; you have made the register unusable and distorted your depreciation at the same time.

• The register and the fixed-asset ledger drift apart by default. The register is the operational record — what it is, where it is, what condition it is in, what has been done to it. The ledger is the finance record — cost, depreciation, net book value. Different owners, different update cycles, different incentives. They will diverge unless something forces them together, and the only thing that does is periodic reconciliation backed by physical verification. Not one or the other. Both.

What happens without a real register

No structured handover, so operations rebuilds the asset list by hand from whatever it can find — and the result is incomplete from the day it is created. Missed PMs follow. Warranties expire unclaimed on equipment nobody knew was under warranty.

Disposals go unrecorded, so ghost assets accumulate, so net book value and insured value are both overstated — and the correction arrives as an audit write-off, in public, in a year nobody chose.

And the assets that were never tagged fall between every system you own. The CMMS does not know about them. The ledger does not know about them. They are in the building, running, being used every day — zombie assets, in service and on no register anywhere. Until one fails, and then a great many people learn about it at once.

How Zepth runs the asset register

Guided asset creation with a real tree hierarchy — property, system, asset, component — and lifecycle states that run from handover through to disposal rather than stopping at “active”. Warranties and documents attach to the asset itself, so the O&M manual is where the asset is, not in a folder somebody has to remember.

Maintenance and cost history live on the asset, so the question “is this chiller worth keeping?” has an answer rather than an opinion. And the register connects to the work orders, inspections, capital plan and disposals around it — one record, rather than three drifting ones that agreed on the day they were created and never again.