An asset hierarchy arranges assets in levels, where each asset can belong to a parent. A common pattern is site › area › system › equipment › component — for example, Plant A › Packaging › Line 2 › Conveyor 2B › Drive motor. The standard ISO 14224 describes such taxonomies for equipment reliability data.
Why it matters
- Costs, downtime and work orders roll up so you can see what a whole line or building costs to run.
- Maintenance can be planned at the right level — replace a motor without losing the conveyor's history.
- People navigate large registers by drilling down instead of scrolling.
Asset hierarchy vs location hierarchy
A location hierarchy says where things are (building › floor › room). An asset hierarchy says what things are part of. They often mirror each other in plants, but not for mobile assets: a laptop has a location but no parent asset.
In Asetavo
Asetavo organizes assets through a location tree (property › building › floor › room) and categories with their own fields, which is how most organizations tracking mobile equipment structure their register.