Asset Hierarchy
A parent-child tree of sites, buildings, systems, equipment, and components that forms the backbone of a CMMS or EAM.
Definition
Asset hierarchy is the parent-child structure that models an organization’s physical assets — from site down through building, floor, system, equipment, and component — in a consistent, navigable tree.
A typical hierarchy
FacilityLane follows a six-level default:
- Organization
- Site / building
- Floor / area
- System (HVAC, electrical, fire, plumbing)
- Equipment (chiller, AHU, pump)
- Component (motor, bearing, filter)
You can add or collapse levels to match your operation — the structure should mirror how your team thinks about assets, not force a textbook model.
Why hierarchy matters
A well-designed hierarchy makes everything downstream work: rolled-up costs, failure-code analytics, PM rollouts to asset classes, meter inheritance, and permissions. Without it, every report becomes a special case and CBM becomes nearly impossible to scale.
Common pitfalls
Over-granular hierarchies (component-level for everything) collapse under their own weight. Flat hierarchies (equipment with no parent system) hide rollups and prevent meaningful analytics. Aim for the smallest hierarchy that answers your real reporting questions.
FAQ
Common questions about Asset Hierarchy.
Most industrial operations do well with four to six levels. Facility operations can often be managed with three to four. Add levels only when they unlock reporting or PM capability you actually use.
See FacilityLane in action
Book a walkthrough mapped to your operation — no pressure, no generic demo.
Request a Demo