How to Set Up a Maintenance Asset Register

Define the purpose before the fields

Decide which decisions the register must support: locating equipment, planning PPM, reviewing failures, finding manuals or controlling spares. Every field should serve one of those decisions.

Avoid asking technicians to populate data merely because a template contains a column. Empty optional fields are better than unreliable values.

• Named register owner
• Agreed inclusion rule
• Criticality definition
• Minimum required fields

Build a hierarchy people recognise

Begin with Site, then use areas, systems, parent assets and components only where those levels match the physical operation. A compressor package may be the parent of a motor, pump and dryer; an office chair probably needs no hierarchy.

Walk the proposed structure with an engineer. If they cannot find an asset quickly, simplify it.

Choose codes that survive change

Use short, unique codes that do not depend too heavily on a temporary location or employee. Record manufacturer serial numbers separately; they identify the manufactured unit, while your code identifies it inside your maintenance system.

• Unique internal asset code
• Plain-English name
• Site and location
• Parent asset
• Criticality
• Make, model and serial where useful

Import, sample and improve

Clean obvious duplicates before import, then load a small representative batch. Raise work against several assets, generate labels and check the resulting history. Correct the pattern before importing the remainder.