Key takeaways
Short answer: An asset hierarchy is the structural map of your equipment — site to area to line to machine to component — and it is how the CMMS organises history and cost. Asset criticality is a ranking of each asset by failure consequence, used to set maintenance strategy. The hierarchy tells you what exists and how it connects; criticality tells you what matters most. Build the hierarchy first. See also why asset tags matter more than people think.
An asset hierarchy is the parent-child structure of your equipment, from site down to component. It is the organising backbone of the CMMS — every work order, cost and failure record attaches somewhere on it, and it lets you roll information up from a component to a line to a plant.
Asset criticality ranks each asset by the consequence of its failure — weighing safety, production impact, cost and replacement lead time. It is the priority layer laid over the structure, telling you where to spend maintenance effort and which strategy each asset deserves.
A plant tries to rank asset criticality before it has a clean hierarchy, so technicians log work against "the line" and the rankings float free of real equipment. Once they build the hierarchy properly — every pump, motor and valve with its own node — the criticality assessment finally has something to attach to: pump P-204 is critical (single point of failure, long lead time), while the redundant cooling fan is not. Structure first gave the priorities a home; without it, criticality was just a spreadsheet nobody could act on.
You cannot rank what you have not mapped. A clean hierarchy gives every asset a place to attach work, cost and criticality. Rank before you map and the ranking floats free of real equipment, impossible to act on or maintain as the plant changes.
The hierarchy organises; criticality prioritises. Together they tell maintenance where to focus and let OEE roll up from component to line to plant correctly — the structure carries the data, the criticality directs the effort.
1. Ranking criticality before mapping the hierarchy. The rankings have nothing to attach to.
2. A hierarchy too shallow. Logging to "the line" hides asset-level reality.
3. Criticality set once and forgotten. Consequences change as the plant changes.
4. Different structures in CMMS and OEE. The two cannot be joined.
OEE rolls up the asset hierarchy, weighted by where the critical constraints sit. A clean hierarchy plus criticality is what makes plant-level OEE meaningful rather than an average of unlike things — and what lets you find the critical asset dragging the number down.
Fabrico keys OEE and downtime to a consistent asset hierarchy, so per-asset and rolled-up views both work and criticality has somewhere to live. Book a demo to see structured asset analytics.
The hierarchy — you must map equipment before you can rank it.
Failure consequence: safety, production impact, cost and replacement lead time.
Yes — it is how history and cost attach to assets.
It lets OEE roll up correctly across the plant and find the critical bad actor.
Deep enough to log work at the asset, not just the line — usually to maintainable component level.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
