Build an asset hierarchy

An asset hierarchy is the tree that organizes everything a team maintains. It decides how technicians find a machine, where work is recorded, and how costs and failures add up in reports. Changing it later is painful, so it is worth a little thought up front. It does not need to be perfect.

1. Decide what the hierarchy is for

Ask who will use it and how:

• Technicians want to find the machine in front of them quickly, usually by location.
• Planners want to see all work on a line or system together.
• Managers want costs and downtime by site, area, and line.

For most plants, a location-based tree serves all three well enough. Field service teams often use customer, then site, then installed machine.

2. Choose the levels

A common pattern for a plant:

1. Site
2. Building or area
3. Line or system
4. Machine
5. Major component (only where needed)

Four to six levels are usually enough. Each extra level makes navigation slower, especially on a phone. Write the levels down, with one or two examples for each, so everyone builds the same way.

3. Decide where to stop

Go down only to the level where you record work and want history. If you replace the motor on a conveyor and want to know how often, the motor can be its own asset. If you never track the bolts, they do not need records.

A useful test: would someone look up this item's history later? If not, it can be a spare part or a line in a checklist instead.

4. Set naming rules

Agree on names and identifiers before you enter anything:

• a short, unique tag for each asset, such as PRESS-042 or L2-CONV-03,
• a readable name, such as "Hydraulic press 42, Hall B",
• the same naming pattern at every site.

Use the tags people already use if they exist, for example numbers painted on the machines or functional locations from an ERP. Inventing new numbers that nobody uses on the floor creates two naming systems.

5. Collect the data

Walk the site. Lists from finance or old spreadsheets are a start, but they are often out of date: machines have moved, been replaced, or been scrapped. For each asset, record at least:

• tag and name,
• parent in the hierarchy,
• manufacturer, model, and serial number,
• photos of the machine and its nameplate.

The nameplate photo is worth taking every time. It holds the details you will need when ordering parts or calling the manufacturer.

6. Attach the knowledge

An asset record becomes useful when it holds what people need at the machine: manuals, wiring diagrams, safety procedures such as lockout/tagout, and the parts it uses. Start with the critical machines and add the rest over time.

7. Keep it current

The hierarchy goes stale as soon as a machine moves. Make updating it part of the work: when a machine is installed, moved, or removed, someone changes the record as part of that job. A short check during regular inspections catches what slips through.

Location or function

Some systems separate the position in the plant from the physical unit installed there. SAP, for example, uses functional locations for positions and equipment records for units. When a pump is swapped for a rebuilt one, the position keeps its history and the pump carries its own history to the workshop and back. This is useful for companies that rotate repairable units. For many smaller teams, one record per machine is simpler and enough.

Common mistakes

• Too many levels, so finding a machine takes six taps.
• Different structures at different sites.
• Records for every small component, which nobody keeps up to date.
• No owner for updates, so the tree drifts from reality.

Once the hierarchy matches the floor, labeling each machine is the natural next step. See Label machines with QR codes.