Uniclass (currently Uniclass 2015) is a classification system for the built environment maintained by NBS in the UK and free to use. It gives every kind of thing on a project — from a whole hospital to a single door closer — a code in a consistent structure.
The tables
Uniclass is split into tables, each with a two-letter prefix:
| Table | Covers | Example |
|---|---|---|
| Co | Complexes | a hospital campus |
| En | Entities | a building |
| SL | Spaces / locations | a ward |
| EF | Elements / functions | walls |
| Ss | Systems | a partition system |
| Pr | Products | a plasterboard sheet |
| Ac | Activities | |
| TE | Tools and equipment | |
| PM | Project management | |
| FI | Form of information | |
| Ro | Roles |
Codes are hierarchical: each pair of digits adds detail, for example Ss_25_10 and deeper levels below it.
Why it matters for coordinators
- It gives model elements a common language across disciplines and software.
- It links models to specifications, cost plans and asset data.
- It makes checks and schedules possible by classification instead of by family or layer names, which differ between teams.
In practice
Agree in the BEP which tables are used and at which level of detail (often Ss for systems and Pr for products). Add the classification code as a column in your LOD matrix and as a property in the models. Uniclass is updated regularly, so record which release the project uses.
See also OmniClass, the North American equivalent.