This document discusses the Uniclass classification system and BS1192 naming conventions that are required for BIM Level 2 in the UK and Scottish construction industries. It provides background on Uniclass, describing it as a unified classification system for construction that replaces the previously used CI/SfB system. It explains the format and hierarchical structure of Uniclass codes. It also discusses where and how Uniclass should be implemented, such as in file names, directories, models, and more. Examples of naming conventions using Uniclass codes are provided. While Uniclass provides benefits, there is some disagreement in the industry on strategy and possible changes to the standards.

1. keppie
Uniclass and BS1192 naming convention

2. What is Uniclass?Background BS1192 and Uniclass
BIM Level 2 Implementation

3. Section 1 Brief background to BIM Level 2
Review of
Scottish public
sector
procurement in
construction,
October 2013
Recommendations
presented to
government
Scottish Futures
Trust
BIM
Implementation
Plan
September 2015
Adoption of
BIM level 2,
“where
appropriate”
within
construction in
Scotland by
April 2017
Scottish
Procurement
Policy Note
SPPN 01/2017
“must assess”
“will comply”

4. Section 1 Brief background to BIM Level 2

5. Section 1 Background
COLLABORATE
Both UK and Scottish
Governments require the use
of Uniclass classification system
as the common language of
BIM Level 2
At Keppie this Replaces the
previously used CI/SfB
(construction indexing manual)
codes

6. Section 2 DEFINITION
•A unified classification system for the construction industry. For the first time,
buildings, landscape and infrastructure can be classified under one unified scheme.
•A hierarchical suite of tables that support classification from a university campus or
road network to a floor tile or kerb unit.
•A numbering system that is flexible enough to accommodate future classification
requirements
•A system compliant with ISO 12006-2 that is mapped to NRM1 and supports
mapping to other classification systems in the future
•A classification system that will be maintained and updated by NBS.
•Within the BIM toolkit a database of synonyms to make it as easy as possible to find
the required classification using standards industry terminology.
But we liked the old way...
What is Uniclass?
NBS BIM Toolkit description

7. Section 3 Who will use Uniclass
UNICLASS
FM
Client/
Owner
Contractor
Architect
Structural
Detailers
Mechanical
Electrical
Fabricators
Site Team
NBS
Toolkit
NBS
Specs

8. Section 2 What is UNICLASS
Format is longer than the previously used CI/SfB (construction indexing manual)
Each code consists of either four or five pairs of characters
•SS_30 Roof, floor and paving systems
Table Group
Sub
Group
Section Object
examples
•SS_30_10 Pitched, arched and domed roof structure systems
•SS_30_10_30 Framed roof structure systems
•SS_30_10_30_25 Heavy steel roof framing systems

9. Section 2 Access to UNICLASS
Within the NBS Toolkit there is a full set of tables
However,
use the search facility provided, link below..
https://toolkit.thenbs.com/articles/classification/

10. Section 2 Common Language - UNICLASS

11. Section 2 Applying UNICLASS
However…
These are too long, too complex to use in entirety
Use the 4 digit numerical sequence provided by the group and sub
group codes,
examples below:
Search result Code to Use
Ss_30_10_30_85
Timber roof framing systems
3010
Ss_25_10_30_35 Gypsum board partition systems 2510
Zz_85_20_20
Concept massing 8520

12. Section 3 Where to use Uniclass
PAS 1192-2 requires that the naming convention set in BS1192-2007 is used
within the BIM process
In summary: All of the following have to follow the naming convention
Directories
• Sub
directories
• Folders
Files
• Models
• Sub models
• Sheets
• Documents
• Tables
• Schedules
Containers
• Worksets
• Sections
• Symbols
• View names
• families
• Blocks

13. Section 3
Table 3.1 R = Required O=Optional *= Not Required
Container
Type
Project
Code
Originator Volume/System
Levels &
Locations
Type Role Classification
Number
Presentatio
n
Description
(Optional)
Suitability
(Optional)
Revision
(Optional)
Code
Code
Company
Code Building,
area, ph
ase or z
one
Code
Level
Code
Document
Type
Code
Role Code Uniclass Code
Examples
KEP Keppie Design XX
All zone
s
XX
No level
applicable
Drawings &
Models
A Architect
(6045) Shared Levels
and Grids
0001
Directories
/folders
R * * * * *
*
*
* *
O O
Files R R R R R R O R * * * *
Containers
within files
* * * * * R R * * O * *
Using Uniclass
The naming structure in all cases is derived from a series of fields, joined
together by hyphens and are created according to 3 patterns, as below:
To employ standard methods across projects the optional use for all files
should be employed for ease of upload to any CDE’s e.g. ASITE, CONJECT
Naming conventions and structures are further explained in Keppie
procedure sheets and Project Information Model (PIM) guidance

14. Section 3 Naming Conventions - Examples
Project Code Originator Volume/System
Levels &
Locations
Type Role Classification Number Description
Keppie File naming Examples
Models P17002-KEP-Z1-XX-M3-A-4510-0001_2017_North Block
Note: Code (4510) = residential building
Sheets P17002-KEP-Z1-GR-DR-A-7060-0001_1-100 GA Plan Ground Floor, North Building
Note: Code (7060) = Plans
Documents P17002-KEP-XX-XX-SA-A-7020-0001_Schedule of Accommodation
Note: Code (7020) = Space Planning
Tables P17002-KEP-Z3-XX-SN-A-2530-0001_Window Snagging Table East Building
Note: Code (2530) = Door and Window Systems
Schedules P17002-KEP-Z2-02-SH-A-2530-0001_Door Schedule Level 02 South Building
Note: Code (2530) = Door and Window Systems

15. Section 3 Naming Conventions - Examples
Layer naming Examples
Role Classification Description
Worksets A-7050_FireStrategy
Symbols A-7050_FireHydrantSymbol
View names A-7050_1-500FireStrategyLevel00
Families A-7050_FireHydrantType1
Blocks A-7050_FireHydrantType3

16. Section 3 Naming Conventions within Revit

17. Section 3 Naming Conventions - Examples
Not everyone in industry agrees on strategy
There is discussion/disagreement ongoing in the community
There is a possible re-write to the standards

18. Section 3
BIM Tech User Group

19. keppie

20. keppie
Diane Ramage
BIM Manager, Keppie Design
Thank You for listening