Key takeaways
- An asset register is the master list of every asset you maintain, with its location, identity, documents, history and costs.
- Structure matters more than volume: a clear location hierarchy and parent–child asset relationships make the register usable.
- Start with critical assets and a minimum set of fields, then enrich the register as work orders are closed against it.
- Once work is recorded against assets, the register produces reliability metrics such as MTBF and MTTR without extra effort.
What is an asset register?
An asset register is a structured record of every physical asset your team is responsible for: equipment, building systems, vehicles, tools and installations. In a maintenance context, it answers four questions about each asset: what it is, where it is, what has been done to it and what it costs.
A spreadsheet can hold a list. A register in a CMMS goes further: every work order, inspection, part and reading links back to the asset, so its record grows automatically. See Asset Management.
What to record for each asset
Split fields into what you need on day one and what you can add over time:
| Group | Minimum (day one) | Add later |
|---|---|---|
| Identity | Asset ID / tag, name, asset type or class | Manufacturer, model, serial number |
| Location | Site, building, floor or area | Room or exact position, GPS for remote assets |
| Structure | Parent asset or system (for example, AHU-03 is part of HVAC system B) | Component breakdown |
| Status | Active, standby or out of service; criticality rating | Condition score |
| Documents | Manual or datasheet, if available | Warranty, certificates, drawings, photos |
| Commercial | Install date | Purchase cost, supplier, warranty expiry, contract coverage |
| Maintenance | Assigned PM schedule | Meters, spare parts list, safety procedures (SOPs) |
Use custom fields for anything specific to your industry, such as calibration due dates for medical equipment or inspection certificates for elevators, rather than forcing it into generic fields. In e-maintain, admins add these through custom attributes without development.
Get the structure right
Location hierarchy
Agree on one hierarchy, such as Site > Building > Floor > Area, and use it everywhere. It drives how technicians find assets, how work is filtered by site and how costs roll up. Multi-site operators in the GCC often add a region or client level above Site.
Parent–child relationships
Link components to the systems they belong to. When a pump fails, you can see the impact on the chilled-water system; when you report costs, they roll up to the system and the building.
Naming and tagging
Use a consistent ID format that a technician can read on site, for example DXB-T2-L04-AHU-03. Put it on a barcode or RFID tag so technicians can scan it on the mobile app instead of searching.
Collecting the data without stalling the project
- 1
Start from what you have
Pull existing spreadsheets, handover documents, O&M manuals and old CMMS exports. Clean duplicates and agree on asset types before importing.
- 2
Prioritize critical assets
Register the assets that cause the most downtime, cost or compliance risk first. Get them on PM schedules quickly to show value.
- 3
Walk the site
Verify location and nameplate data on the ground with a mobile app, take photos and tag assets as you go.
- 4
Import, then let work orders fill the gaps
Each closed work order adds history, parts and costs. The register becomes richer through normal operations.
- 5
Assign an owner
Someone must approve new assets and retirements, or the register drifts out of date within months.
If you are moving from another system or from spreadsheets, e-maintain's team can handle data migration as part of implementation.
MTBF and MTTR: what a good register gives you
Once failures and repairs are recorded against assets, two of the most useful reliability metrics come straight out of the register:
- MTBF (mean time between failures) = total operating time ÷ number of failures. It shows how reliable an asset is. A falling MTBF means it is failing more often.
- MTTR (mean time to repair) = total repair time ÷ number of repairs. It shows how quickly your team restores an asset. A rising MTTR can point to missing parts, skills gaps or slow dispatch.
Example: a pump ran 2,000 hours in a quarter and failed 4 times, so its MTBF is 500 hours. The four repairs took 2, 3, 1 and 2 hours, so its MTTR is 2 hours. Compare those figures across identical pumps and the problem unit stands out.
Together with lifecycle cost (purchase plus all maintenance and parts), these numbers support repair-or-replace decisions. Our guide to maintenance KPIs covers more of them.
Frequently asked questions
What is the difference between an asset register and an asset inventory?
An inventory is usually a count of items. An asset register holds the full record for each asset, including location, structure, documents, maintenance history and costs, and is updated by maintenance activity.
Should every asset go into the register?
Register everything you maintain on a schedule, anything critical and anything you need to report on. Low-value consumables are better managed as inventory items than as individual assets.
How do I keep an asset register up to date?
Make it part of daily work: technicians update assets from the mobile app as they close jobs, new installations go through an approval step, and someone owns the register and reviews it periodically.
Can I track asset locations in real time?
Yes. e-maintain records asset location and updates it as assets are moved or reassigned between sites, and barcode or RFID scanning makes this quick in the field.