Find any asset in two clicks
Every asset classified by what it is and where it is - so "all cooling systems portfolio-wide" and "everything in Room 203" are both one filter away.
Ask from either direction
Every cooling system across the portfolio, or everything in one mechanical room - the same database answers both, because every asset carries both classifications.
Roll up costs at any level
Spend, condition, and counts aggregate at class, group, system, or asset - so "what does HVAC cost us portfolio-wide?" is a report, not a project.
Standards first, your language second
Start from UNIFORMAT II-aligned defaults, then rename and reshape the hierarchy to match how your team actually talks about the building.
Classify by what it is
Four levels - System Class → Group → System → Asset - describe every piece of equipment from broad category down to individual component. Analyze all HVAC portfolio-wide, just cooling systems, one chiller, or a single compressor.
- UNIFORMAT II-aligned system classes out of the box
- Rename and reshape every level to your terminology
- Cost and condition rollups at any level of the tree
- Cross-site comparisons of the same system type built in
Classify by where it is
Site → Building → Location places every asset precisely in the real world. A technician finds what's in the room they're standing in; a manager sees everything across a campus - from the same data.
- Unlimited sites, buildings, and locations
- Asset counts and costs visible at every level
- Scope work orders and reports to any place in the tree
Combine both - that's the unlock
Traditional CMMS make you pick one organizing principle, then fight it with tags and exports. Because AssetLab keeps both dimensions on every asset, questions like "total electrical costs at the South Facility" are a filter, not a spreadsheet afternoon.
- Filter by either dimension or both at once
- Switch perspective instantly - no reorganization
- Reports and dashboards analyze from any angle
And everything else you'd expect
“When an inspector comes through and wants documentation on something like our fire suppression systems, I can pull a report through the Systems view in a few seconds rather than hunting for our old physical log book.”
Stop Choosing One Dimension.
Use Both.
Every asset classified by what it is and where it is. Find anything in two clicks. Analyze from any angle - without reorganizing your database.
No credit card required
Keep Learning About Asset Classification
Smart Asset Classification
How hierarchical classification lets you see your entire portfolio at a glance.
UNIFORMAT Classification
The elemental classification standard behind condition assessments and capital plans.
How to Create an Asset Management Plan
A comprehensive guide to building classification into your management plan.
Asset Classification FAQ
Common questions about 2D classification, UNIFORMAT II, and how AssetLab organizes your asset data.
What is asset classification in a CMMS?
Asset classification gives every asset a defined place in a structured hierarchy so it can be found, grouped, and reported on consistently. In AssetLab each asset is classified twice - by what it is (system hierarchy) and by where it is (location hierarchy) - so searches and reports work from either angle.
What is 2D asset classification?
Most CMMS force one organizing principle: a location tree OR an equipment tree. 2D classification keeps both on every asset - System Class → Group → System → Asset for what it is, and Site → Building → Location for where it is - and lets queries combine them, like "all electrical systems in the South Facility."
Does AssetLab follow UNIFORMAT II?
Yes - AssetLab's default system classes follow the UNIFORMAT II elemental classification used in facility condition assessments and capital planning, so your asset data lines up with how consultants, assessors, and standards already describe buildings.
Can I customize the classification hierarchy?
Fully. Administrators can create, rename, and reorganize system classes, groups, and systems to match your organization's terminology - fume hood systems for a university, medical gas zones for a hospital. Start with the defaults, import your assets, and refine over time without disrupting existing data.
Do I have to reorganize my data to change how I search?
No. Both classifications live on every asset from day one, so switching from a location view to a system view is a filter change, not a migration. The reorganization projects that traditional CMMS require simply don't exist here.
How is this different from tags or custom fields?
Tags are flat and optional - they answer queries only as well as people remembered to apply them. A hierarchy is structured and enforced: every asset has exactly one system path and one location path, which is what makes rollups, comparisons, and reports reliable instead of approximate.