1.

5
1.5.5.4 File Naming Convention
The models, component libraries, elements and drawing file names should follow a
consistent file naming convention. The client may specify a file naming convention or the
lead consultant shall recommend a suitable naming convention for the project.

BIM PXP Contents

A file naming convention similar to the existing Works Departments CAD standard
convention may be adopted. The file names may be of the form “AGENT-PROJECT-
ZONE-ID-STATUS”.
Definition Code Format Details
AGENT 3 alphanumeric the list of agent responsible codes
can be downloaded from the Development
Bureau web site at
www.devb-wb.gov.hk/cswp

PROJECT 1 to 8 alphanumeric User definable project reference coding.

ZONE 3 alphanumeric Required if project is subdivided by zones or

levels
ID 2 alphabetic Indicates the discipline. For list of ID’s refer to
table below.

STATUS 1 alphabetic A = as-built

E = existing, to remain
M = maintenance or record
N = New work
R = Remove
T = Temporary Work
W = All Work

Example = CIC-BIMS2014-POD-AR-W

31
 1.5
As an alternative, the naming of model files may be based on BS1192:2007. The file
names may be of the form and any of the fields may be omitted.

PROJECT-AUTHOR-ZONE-LEVEL-TYPE-ROLE-DESCRIPTION
Definition Code Format Details

BIM PXP Contents

PROJECT 1 to 8 alphanumeric User definable project reference coding.
AUTHOR 3 alphanumeric Can use the list of agent responsible
codes which can be downloaded from
the Development Bureau web site
ZONE 2 alphanumeric Identifier of which building, area, phase
or zone of the project the file relates to if
the project is sub-divided by zones. For
infrastructure (linear) the zone may be
replaced by a location defined as a
chainage and offset.
LEVEL 2 alphanumeric Identifier of which level, or group of
levels, the model file relates to if the
project is sub-divided by levels.
TYPE 2 alphanumeric Document type, which will be M3 for 3D
model files or QT for quantity take off.
ROLE 2 alphabetic Indicates the discipline. For list of ID’s
refer to table below.
DESCRIPTION 1 to 8 alphanumeric Descriptive field to define the type of
data portrayed in the file. Avoid
repeating information codified in other
fields. Can be used to describe any part
of the previous fields, or to further clarify
any other aspect of the contained data.

Example = BIMS2014-CIC-ZN-L3-M3-AR-FILENAME
The file naming shall not include a revision status. Revisions shall be tracked using data
added to the models or by the BIM Coordinator in a change management register.

32
 1.5
The ID or ROLE field in the above naming conventions shall be taken from the table
below:-
ID Discipline
AR Architect
BS Building Surveyor

BIM PXP Contents

CL Client
CN Contractor
CV Civil Engineer
DR Drainage Engineer
EE or EL Electrical Engineer
FM Facilities Manager
FS Fire Services Engineer
GE Geotechnical Engineer
GS Geographical Information System Engineers or land surveyors
HY Highways Engineer
IN Interior Designer
LS Land Surveyor
LA Landscape Architect
ME Building Services Engineer, MEP Engineer
MV or AC Mechanical Ventilation & Air Conditioning Engineer
PL Plumbing Engineer
PM Project Manager
QS Quantity Surveyor
SC Sub-Contractor
ST Structural Engineer
TP Town Planner

1.5.5.5 Layer Naming Convention

Each discipline should provide the Lead consultants CAD manager with a full list of all
layer names to be used on the project. This list should be published to all members of the
project team for information.

33