Reference notes on Uniclass, OmniClass, IFC and why object classification decides whether model data is usable downstream.
Classification gives every object in a model a shared, machine-readable identity. Without it, a door is whatever the person who modelled it decided to call it.
It matters most after construction. Asset registers, maintenance schedules and space management systems all need to group objects by type, and they cannot do that from geometry alone.
Classifying at the wrong level of the hierarchy is the most common error — tagging every object at the broadest available code loses exactly the distinction the register needed.
Mapping objects to more than one system without deciding which is authoritative creates conflicts that surface only when data is exported.
Leaving classification until the end of a project means it is done by whoever has least context, usually from object names rather than from design intent.
Handover reviews, site walkthroughs and client workshops still happen in person. For project teams working across South Florida, ground transport between Miami International and the sites themselves is usually booked as corporate travel:
This site is an independent reference page. It is not affiliated with, endorsed by, or connected to any previous owner or operator of this domain, nor to any company or product that may formerly have used this name.