Block layers vs BIM classification: Uniclass and Omniclass
Why a DWG block's layer name and a BIM object's classification code solve different problems, and how to make the two systems agree.
Saumyajit MaityUpdated 18 April 20265 min read
Two systems that were never built to talk to each other
A CAD layer and a BIM classification code look like they're doing the same job, sorting building content into categories, but they come from genuinely different eras of practice and solve genuinely different problems. A layer name like A-DOOR or FURN-WORK exists to control what's visible, printable and editable together on a 2D sheet, it's a drafting convenience going back decades, well before BIM classification systems existed. A Uniclass or Omniclass code attached to a BIM object exists to classify what the thing actually is, for cost planning, facilities management, and data exchange, completely independent of which sheet it happens to print on. Confusing the two, or worse, assuming one automatically implies the other, is where most hybrid offices get into trouble.
I've reviewed enough drawing sets to know the mismatch is common, a door block sitting correctly on an A-DOOR layer that, once brought into the BIM model, gets classified under entirely the wrong Uniclass group because whoever placed it just picked the nearest sounding family type rather than checking the actual classification table.
What a layer name is actually good for
Layer naming conventions, the AIA CAD layer guidelines being the most widely referenced one in North America, are built around graphic control, line weight, color, visibility, plot behavior, grouped by discipline and rough content type. A downloaded block, a window, an iron gate, a workstation, generally arrives with its own layer already set by whoever drew it, and the first real task after inserting it is renaming that layer to match your project's own convention rather than leaving a foreign layer name sitting in your drawing.
This matters more than it sounds like it should, because layer names drive what shows or hides per viewport, what plots at what weight, and what a downstream user searching the drawing can actually filter for. None of that carries any classification meaning on its own, a layer called DOOR tells you nothing about fire rating, cost code, or facilities management category, it just tells you what to do with it graphically.
What Uniclass and Omniclass are actually classifying
Uniclass, used widely in the UK and increasingly elsewhere following ISO 19650 adoption, and Omniclass, its rough US counterpart, classify building content by function and system, not by how it's drawn. A door gets a code under something like Uniclass's Products table regardless of whether it's drawn as a simple 2D block or a fully parametric BIM family, because the classification describes what the object is and does, not which software produced it or which layer it lives on.
This is genuinely useful information that a layer name was never designed to carry, it feeds cost estimation, facilities management handover, and structured data exchange like COBie, so when a 2D block gets promoted into a BIM environment, someone has to deliberately assign that classification, it does not arrive automatically just because the layer name sounds similar.
Where the reconciliation actually has to happen
In practice, reconciling the two systems is a manual mapping exercise that most offices do once and then reuse, a simple table matching your internal layer naming convention to the correct Uniclass or Omniclass code for each recurring content type, door blocks map to this code, workstation and office furniture blocks map to that one, site elements like gates map to a landscape or external works classification. Build that table once, keep it with your CAD standards document, and reference it every time content moves from 2D drafting into the BIM model.
The catch here is that this mapping has to be maintained by someone who actually understands both systems, not delegated silently to whoever is fastest at placing families, because a wrong classification quietly propagates into every schedule, every cost report, and every facilities management extract built off the model later.
A practical example working through both systems
Take an office workstation block downloaded and inserted at layer FURN-WORK in a 2D layout drawing. In the BIM model, that same content, whether kept as linked 2D reference or rebuilt as a native family, needs a classification code from the furniture and furnishings table in whichever system your project standard specifies, plus whatever project specific parameters your BIM execution plan requires, cost center, supplier, warranty data. The layer name and the classification code are both correct simultaneously, they're just answering different questions.
A conference table for twenty follows the same pattern, layer name controls how it plots and displays on the 2D furniture plan, classification code controls how it's counted, costed and handed over in the structured data deliverable. Neither one substitutes for the other, and treating them as interchangeable is exactly where classification errors creep into an otherwise clean model.
Keeping the mapping table from going stale
Standards documents like this rot quietly if nobody owns them, so assign the layer to classification mapping table an actual owner and a review point, ideally whenever your office's BIM execution plan gets revisited or a new classification version is adopted, since Uniclass in particular has gone through several published revisions. A mapping table built against an old classification version will keep technically working while quietly drifting out of compliance with whatever the current project standard actually requires.
At the end of the day this is a small amount of upfront documentation work that saves a much larger cleanup job later, reclassifying a hundred objects in a finished model is a miserable afternoon nobody wants, checking a mapping table once a year is not.
A short worked example of the mapping table in use
Say your office's internal layer standard uses FURN-WORK for workstation blocks, DOOR for door blocks, and EXT-GATE for site gate elements. A simple mapping table sitting alongside your CAD standard might read something like this, FURN-WORK maps to the furniture and furnishings group under whichever classification system the project specifies, DOOR maps to the appropriate doors group, EXT-GATE maps to an external works or landscape group depending on which system is in use. None of this requires special software, a shared spreadsheet or a page in your standards document is genuinely sufficient, the value comes from consistency, not sophistication.
What this table actually prevents is the scenario where three different people, working on three different projects over a year, each independently guess at a classification for the same recurring block and land on three different answers, none of which get caught until a cost report or a facilities management extract pulls oddly inconsistent numbers for what should be identical furniture across the portfolio. A five minute lookup against a shared table costs nothing, three inconsistent guesses cost someone a confusing afternoon reconciling data that should never have disagreed in the first place.
Further reading
Questions
Frequently asked
Do I need to reclassify every downloaded block before using it?+
Only once it enters a BIM deliverable that requires classification, like a model feeding cost planning or facilities management. For a purely 2D layout drawing, correct layer naming is generally sufficient on its own.
Is Uniclass or Omniclass required on every project?+
No, it depends on your contract and, on public UK work in particular, whether ISO 19650 information management applies. Many smaller or purely 2D projects never touch a formal classification system at all.
Can one block have both a layer name and a classification code at the same time?+
Yes, and it usually should once it's part of a BIM deliverable. The layer name controls graphic display, the classification code carries the structured data, they coexist without conflict.
Free downloads from this article
Free CAD block library
Download the blocks from this article — free, no signup
