Each drawing, model or document released within a project should include a unique identifier. This basic principle has been estabish, tried and tested through the last twenty years of research and project analysis and is fundemental to reducing waste by providing the ability to find information quickly and effectively.
The following file naming convention was established through AVANTI and then incorporated into BS 1192:2007. This approach has been tried and tested and can equally be applied to the more recent ISO 19650 series.
Unique Identifier format
The container identifier shall consist of the following eight fields:
| Field 1 | Field 2 | Field 3 | Field 4 | Field 5 | Field 6 | Field 7 | Field 8 | |||||||
| Project | – | Originator | – | Zone / Volume | – | Level / Location | – | File Type | – | Discipline | – | Classification | – | Number |
| Req | – | Req | – | Req | – | Req | – | Req | – | Req | – | Opt | – | Req |
| AAAAAA | – | AAA | – | AA | – | AA | – | AA | – | TT | – | AA | – | NNNN |
Req = Required field, Opt = Optional field , A = Alphanumeric, N = Numeric, T = Text
Field 1 – Project Code
The ‘Project’ code and a possible ‘Sub project’ code (if specified) using a underscore as a separator as required by the Client provide a unique number for the project and will be independent of each organisation’s internal project number (Each independent organisations internal project number should be created as additional meta data). The ‘Sub project’ code may reflect a specific work stage or series of work stages within a project such as “Design” or “Construction”. The Length of field one should be limited to 6 Characters.
Field 2 – Originator
The ‘Originator’ fields defines the responsible organisation / company – not the owner – accountable for the delivery of the information. A unique code shall be identified for each appointed organization / company that authors models or documentation.
Field 3 – Zone / Volume
The ‘Zone / Volume’ allows for the project to be broken down into spatial zones or volumes and assists in defining each with detailed demarcation especially in three dimension and descriptions. A unique code must be defined for the building or infrastructure zone to which the file belongs. It must contain one or two characters. Special applications include:
- ZZ: All zones
- XX Zones not applicable
Field 4 – Level / Location
The Level/location fields define either the asset, project or building in a project in a file identifier locate information within the building or by linear location on civil projects by breaking the project into identifiable chunks. Levels and Locations should be defined with detailed demarcation especially in the vertical dimension and a detailed description.
- ZZ: All Levels / Locations
- XX Levels / Locations not applicable
Field 5 – Type
The remaining fields are used to uniquely identify the file by document type and discipline as well as providing an index and number. All fields shall be separated using a hyphen character. Where field values apply to all
Field 6 – Discipline
A unique code must be defined for each index or system in the project. See Discipline Table below.
Field 7 – Classification (Optional)
The Option to include a classification code based upon a single and appropriate classification system is provided. Please note that Classification assumes either a classification based upon CI/SfB or Table H or G from the original Uniclass or similar derived classifications. (The use of Uniclass 2015 is not considered appropriate).
Field 8 – Number
Each identifier should have a unique number when concatenated with file types and discipline. If a file belongs to a series that is not distinguished by any of the previous fields, a correlative number must be used. Trailing zeros should be used
Identifier Length
Due to limitation in file length is specific systems and databases the overall file length shall not exceed 32 characters. Each project should identify their field length requirements for each fied and document these.
Standard codes for information types
Code Description
DR Drawing
M2 2-Dimensional Model
M3 3-Dimensional Model
MR Model Rendering
VS Visualization
SC Schedule
SP Specification
BQ Bill of Quantity
SC Structural Calculations
IE Information Exchange (COBie)
Standard Role Codes
Code Description
A Architecture
B Building Surveying
C Civil Engineering
D Drainage, Highways Engineering
E Electrical Engineering
F Facilities Management
G Geographical and Land Surveying
H Heating and Ventilation Designer
I Interior Designer
K Client
L Landscape Architecture
M Mechanical Engineering
P Public Health Engineering
Q Quantity Surveying
S Structural Engineering
T Town and Country Planning
W Contractor
X Subcontractor
Y Specialist Designer
Z General (non-disciplinary)