Key takeaways
Short answer: The CMMS asset hierarchy is the parent/child structure that organizes every asset. Most CMMS rollouts get this wrong on day one and the consequences compound for years — broken rollups, inconsistent naming, restructuring nightmares. A practical hierarchy uses 4-6 levels (Site → Area → Line → Cell → Asset → Component), with explicit naming conventions, criticality fields, and parent links defined before loading any data. See also MES vs CMMS.
A CMMS without a clean hierarchy produces ugly reporting:
Restructuring the hierarchy after the CMMS is in production is painful — historical data has to be remapped, reports break, naming conventions diverge. Get it right at setup.
Some plants add a seventh level for replaceable sub-components. Most do not need it; component-level work orders cover it.
A working naming convention has four properties:
Example: ASLY-L3-CELL2-PUMP-001 — Assembly Line 3, Cell 2, Pump number 001.
Criticality is not just an asset-level attribute. The whole hierarchy should carry it:
Rolling these up lets PM prioritization happen at the right level.
Every asset must have a parent. The parent chain rolls up to enterprise. This enables:
Without explicit parent links, rollups become impossible and reporting becomes per-asset only.
These six items decided BEFORE loading prevent 90% of the restructuring nightmares.
1. Loading data first and structuring later. The structure ossifies around the load and becomes painful to change.
2. Letting every line define its own naming. Inconsistency permanent.
3. Too many levels. Above 7 levels usually means the hierarchy is doing what other fields should do.
4. No data steward. Hierarchy decays as different people add assets in different ways.
5. Component-level granularity for everything. Most plants do not need to track every bolt as an asset. Stop at the level where work orders are written.
Rule of thumb: if you write work orders against it, it is an asset. If you replace it as a spare part during a work order, it is a component (which may or may not need to be in the hierarchy depending on traceability requirements).
Rolling these up lets PM scheduling and work-order prioritization happen based on the right combination.
A modern CMMS enforces the hierarchy at data entry, supports criticality at every level, rolls up reporting by parent, and lets the data steward enforce naming conventions via templates.
Fabrico's CMMS supports configurable hierarchy depth, criticality at every level, naming-template enforcement, and rollup reporting from component to enterprise.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
4-6 levels typically. More than 7 usually means the hierarchy is doing what other fields should do.
Yes but it is painful. Historical data has to be remapped. Get the levels right at setup.
Use a "current location" field that points to a location in the hierarchy. Do not move the asset between hierarchy parents; that breaks history.
Two to four weeks for a typical plant, including cross-functional review. Skipping this work costs years.
Zaloguj
Blog
