Ecopy-CP 83-2-2000

Licensed by SPRING Singapore to LINH/MS, SYNECTICS CONSULTING CORPORATION
Singapore Standards eShop Order No: 6800025511/Downloaded:2014-01-17

Single user licence only, copying and networking prohibited

CP 83 : Part 3 : 2001
(ICS 35.240.10)

SINGAPORE STANDARD
Code of practice for construction

computer-aided design (CAD)
– Part 3 : Organising and naming of CAD files
Published by

CP 83 : Part 3 : 2001
(ICS 35.240.10)
SINGAPORE STANDARD
Code of practice for construction computer-aided
design (CAD)
– Part 3 : Organising and naming of CAD files
All rights reserved. Unless otherwise specified, no part of this Singapore Standard may be
reproduced or utilised in any form or by any means, electronic or mechanical, including
photocopying and microfilming, without permission in writing from SPRING Singapore at the
address below:
Standards
SPRING Singapore
1 Fusionopolis Walk,
#01-02 South Tower, Solaris
Singapore 138628
Email : standards@spring.gov.sg
ISBN 9971-67-832-2

CP 83 : Part 3 : 2001
This Singapore Standard was approved by the Information Technology (IT) Standards Committee on
behalf of the Standards Council of Singapore on 9 January 2001.
First published, 2001
The IT Standards Committee appointed by the Standards Council consists of the following members:
Name Organisation
Chairman : Mr Wilson Tan Standards Council
Executive
Secretary : Ms Pee Gim Onn Infocomm Development Authority of Singapore
Secretary : Ms Ho Buaey Qui Infocomm Development Authority of Singapore
Members : Assoc Prof Chi Chi-Hung National University of Singapore
Ms Susan Chong Singapore Productivity and Standards Board
Prof Robert Gay Singapore Computer Society
Assoc Prof Angela Goh Nanyang Technological University
Mr Kan Siew Ning Infocomm Development Authority of Singapore
Dr Low Hwee Boon Kent Ridge Digital Labs
Mr Alvin Ong Information Technology Management Association
Mr Wee Tew Lim Singapore Information Technology Federation
The Technical Committee on Construction Industry IT Standards appointed by the IT Standards

Committee and responsible for the preparation of this standard consists of representatives from the
following organisations:
Name Organisation
Chairman : Mr Edward D'Silva Singapore Institute of Architects

st
1 Deputy
Chairman : Mr Lee Chuan Seng Institution of Engineers, Singapore
nd
2 Deputy
Chairman : Mr Yeo Eng Chang Housing & Development Board
Secretary : Mr Wong Wai Ching Building and Construction Authority
Members : Mr Goh Ngan Hong Singapore Institute of Surveyors and Valuers
Mr Desmond Hill Singapore Contractors Association Limited
Mr Christopher Ho Real Estate Developers Association of Singapore
Ms Kee Bee Kheng Singapore Institute of Surveyors and Valuers
Mr Khor Poh Hwa Society of Project Managers
Mr Simon Lee Singapore Contractors Association Limited
Ms Lily Leong Housing & Development Board
Mr Shaun Leong Jurong Town Corporation
Mr Samsul Muarif Lokman PWD Consultants Pte Ltd
Mr Steven Neo Real Estate Developers Association of Singapore
Ms Ong Sim Lian Real Estate Developers Association of Singapore
Mr Ajay Sankaran Urban Redevelopment Authority
Ms Rita Soh Singapore Institute of Architects
Ms Irene Tan Building and Construction Authority
2
CP 83 : Part 3 : 2001
Members : Dr Tan Kee Wee Building and Construction Authority

Mr Tan Tian Chong Building and Construction Authority
Mr Tay Leng Chua Defence Science and Technology Agency
Dr Teo Ho Pin Singapore Institute of Surveyors and Valuers
Mr Teo Kong Poon Institution of Engineers, Singapore
Mr Eddie Wong Real Estate Developers Association of Singapore
The Design Working Group appointed by the Technical Committee to assist in the preparation of this
Singapore Standard comprises the following members:
Name Organisation
Convenors : Mr Lee Chuan Seng Institution of Engineers Singapore

Ms Rita Soh Singapore Institute of Architects
Members : Mr T K Asokan Defence Science and Technology Agency
Mr Vincent Han Parsons Brinckerhoff Consultants Pte Ltd
Ms Shirley Foo Maunsell Consultants (S'pore) Pte Ltd
Ms Angela Lee Building and Construction Authority
Mr Leong Kar Tshon Jurong Town Corporation
Ms Lily Leong Housing & Development Board
Mr Albert Lim PCR-Perdana Consulting Pte Ltd
Ms Belinda Lim RDC Architects Pte Ltd
Mr Khalid Mahmood Maunsell Consultants (S'pore) Pte Ltd
Mr Ajay Sankaran Urban Redevelopment Authority
Mr M K Sunil PWD Consultants Pte Ltd
Dr Tan Guan Association of Consulting Engineers Singapore
Dr Tan Kee Wee Building and Construction Authority
Ms Serene Tham RSP Architects Planners & Engineers Ltd
Mr F K Woo Parsons Brinckerhoff Consultants Pte Ltd
Mr Yeo Eng Leng Housing & Development Board
The Technical Committee acknowledges the contributions of the following consultants from the Ngee
Ann Polytechnic in preparing this standard:
1. Mr Tsang Pui Sum

2. Mr Teo Hin Chuan
The Technical Committee also acknowledges the contribution of Dr Tan Kee Wee from the Building
and Construction Authority, in helping to co-ordinate the preparation of this standard.
3
CP 83 : Part 3 : 2001
(blank page)
4
CP 83 : Part 3 : 2001
Contents
Page
Foreword 6
CODE OF PRACTICE
1 Scope 7
2 Purpose 7
3 Definitions 7
4 Concept, formats and codes 8
5 Examples 14
ANNEXES
A List of type-of-work codes by discipline 16

B List of type-of-work codes in alphabetical order 19
TABLES
1 Description of fields in filename format A 9

2 Description of fields in filename format B 9
3 Description of fields in filename format C 10
4 Codes for the first character of author field 11
5 Codes for view plane field 12
6 Examples for view plane field 12
7 Forms of information and codes 12
8 Directory structure and examples 13
FIGURES
1 Filename format A 9
2 Filename format B 10
3 Filename format C 10
5
CP 83 : Part 3 : 2001
Foreword
This Singapore Standard was prepared by the Technical Committee on Construction Industry IT
Standard under the direction of the Information Technology Standards Committee.
In preparing this Singapore Standard, reference was made to BS 1192-5 : 1998 – ‘Construction
drawing practice – Guide for the structuring and exchange of CAD data’. Acknowledgement is made
for the use of information from the British Standard.
NOTE
1. Singapore Standards are subject to periodic review to keep abreast of technological changes and new
technical developments. The revisions of Singapore Standards are announced through the issue of
either amendment slips or revised editions.
2. Compliance with a Singapore Standard does not exempt users from legal obligations.
6
CP 83 : Part 3 : 2001
Code of practice for construction computer-aided design (CAD)

Part 3 – Organising and naming of CAD files
1 Scope
This code is to establish the general principles and formats for naming of construction computer-aided
design (CAD) files.
2 Purpose
The purpose of this code is to enhance uniformity in the naming of CAD files for the construction
industry in Singapore. This is to facilitate communication and management of CAD files by
representing important attributes in filenames and/or other forms of documentation.
3 Definitions
For the purposes of this code, the following definitions shall apply:
3.1 CAD file
CAD file is a digital file containing CAD models or related information.
3.2 Filename fields
The following fields are used in the filename. Each field represents an independent concept.
3.3 Author
The word “Author” is used in this code to refer to the individual/company/organisation responsible for
creating the CAD file which may include layers from a few different originators of layers.
3.4 Project identification
Project identification refers to common characters used in the filenames for the purpose of identifying
CAD files under the same project.
3.5 Type-of-work
Type-of-work refers to the nature and scope of work in the CAD file.
3.6 View plane
View plane refers to the section of the physical construction represented by the CAD model in the file.
It can be the level in a multi-storey building or the orientation of the elevation view.
3.7 Zone
Zone refers to the construction zone or block number of the project.
7
CP 83 : Part 3 : 2001
3.8 Version
Version refers to the major revisions of the CAD file.
3.9 User-defined
User-defined field refers to the field for users to provide additional information of the CAD file.
4 Concept, formats and codes
4.1 General
When CAD files are transferred between different systems and organisations, their contents need to
be understood to locate information, for identification of the source and to manage files. These
processes will be enhanced if all parties involved in a project use a commonly understood filename
convention.
The concepts, formats and codes covered in this code are used to name CAD files in building and
construction projects. Parties involved in projects using this code shall agree on the level of
conformance, format to be used, and document any variations.
This code covers three filename formats and a recommended directory structure. All the filename
formats and directory structure can be further sub-divided into fields. Each field describes certain
attributes of the file or directory.
4.2 Conformance
To cater for the diversity of construction projects, two levels of conformance are allowed in this code,
namely, full conformance and conceptual conformance.
4.2.1 Full conformance
A filename convention is in full conformance to this code if it complies with the formats and codes
specified in this code. Additional codes or user-defined fields not covered in this code are to be
documented and communicated between different parties in the project.
4.2.2 Conceptual conformance
A filename convention is in conceptual conformance to this code if it captures the information required
in the fields and codes in this code, though the sequence and format of fields and codes may be
different. Deviations and additional codes shall be documented and communicated between different
parties in the project.
When it is not practical to include all the information in the filename, a filename reference table or
other means of documentation can be used to provide the information required.
4.3 Formats of filename
This clause outlines three filename formats. Format A is for computer systems that can handle
filenames with more than 8 characters. Formats B and C are two alternatives for computer systems
that can handle filenames with maximum of 8 characters.
All formats contain a number of mandatory fields and an optional user-defined field.
8
CP 83 : Part 3 : 2001
The difference between formats B and C is in the first field of the filename. Format B uses the field to
describe the author while format C uses it for project identification.
4.3.1 Filename format A
This format requires 6 mandatory fields and an optional user-defined field. The length of project
identification filed may vary from 3 to 5 characters depending on the user’s need. To enhance
computer processing and readability, the project identification field is to be separated from the
remaining fields by means of an underscore character “_”.
Table 1 – Description of fields in filename format A
Name of field Description of field Number of

characters
Project Represent files of the same project. 3 - 5;
identification 4 is recommended
Author Individual/company/organisation 2
responsible for creating the file.
Type-of-work Nature and scope of work. 2
View plane Level in a multi-storey building or orientation 2
of an elevation view.
Zone Zone of the construction site 2
Version Major revisions 2
User-defined User-defined code for in-house -
applications. (optional field)
The seven fields in filename format A are to be arranged in the format as shown in Figure 1.
Project Author Type- View Zone Version User-defined*

I.D. of-work plane
_
Figure 1 – Filename format A
4.3.2 Filename format B (alternative - for computer system that can only handle 8.3 filename
format)
This format works with a file directory structure to separate files from different projects. Therefore
CAD files from different projects may have identical filenames. An alternative approach is to utilise
the user-defined field for project identification code.
Please refer to 4.5 for the recommended directory structure.
Table 2 – Description of fields in filename format B

characters
Author Individual/company/organisation responsible 2
for creating the file.
View plane Level in a multi-storey building or orientation of 2
an elevation view.
User-defined User-defined code for in-house applications. -
(optional field)
9
CP 83 : Part 3 : 2001
The five mandatory fields and an optional filed in filename format B are to be arranged in the format
as shown in Figure 2.
Author Type- View Z V User-defined*

of-work plane
(NOTE: Z - Zone field, V - Version field, * - Optional field)
Figure 2 – Filename format B
4.3.3 Filename format C (alternative - for computer system that can only handle 8.3 filename
format)
The only difference between Format C and Format B is that the first field in Format C is used for
project identification. As such, it does not need a file directory structure to separate files from different
projects.
Table 3 – Description of fields in filename format C

characters
Project Represent files of the same project. 2
identification
View plane Level in a multi-storey building or orientation of 2
an elevation view.
User-defined User-defined code for in-house applications. -
(optional field)
The five mandatory fields and an optional filed in filename format C are to be arranged in the format
as shown in Figure 3.
Project Type- View Z V User-defined*

I.D. of-work plane
(NOTE: Z - Zone field, V - Version field, * - Optional field)

Figure 3 – Filename format C
4.4 Filename fields
4.4.1 Author
Author field represents the individual/company/organisation responsible for creating the CAD file.
Two (2) alphanumeric characters are used for this field.
For CAD file where another party prepares part of the information, please refer to CP 83 : Part 1 -
"Organisation and naming of CAD layers" for details of using layers/levels to segregate different
originators of information.
10
CP 83 : Part 3 : 2001
4.4.1.1 First character
This first character indicates the discipline of the originator of the layer. It is a single alphabet in
capital letter as shown in Table 4.
Table 4 – Codes for the first character of author field
Code Author description

A Architect
C Civil Engineer
E Electrical Engineer
L Land Surveyor
M Mechanical Engineer
N Equipment Supplier
S Structural Engineer
T Telecommunication/Signal Engineer
V Other disciplines
X Contractor
4.4.1.2 Second character
The second character provides further definition of the author whenever necessary. If the first
character is sufficient to define the author of the layer, a hyphen "-" shall be used as the second
character of this field. Example: A- for architect and S- for structural engineer.
This second alphanumeric character can also be used to denote different authors from the same
discipline involved in the same project. Example: A1 & A2 represent two different architects working
on the same project.
4.4.2 Project identification
Project identification field represents files under the same project. For Format A, the user may use
between three (3) to five (5) alphanumeric characters to describe the project identification. Four
characters for format A is recommended. For Format C, the user can only use two (2) alphanumeric
characters for project identification.
4.4.3 Type-of-work
Type-of-work field represents the nature and scope of work in the CAD file. Two (2) alphanumeric
characters are used for this field. Please refer to Annex A for the list of codes.
4.4.4 View plane
View plane field represents the level in a multi-storey building or the orientation of the elevation view.
Two (2) alphanumeric characters are used for this field.
In Table 5, numeric variables are represented by "1".
11
CP 83 : Part 3 : 2001
Table 5 – Codes for the view plane field
Code Description
11 Numeric – Level of storey or lowest
level of a typical level (11).
A- Attic
B1 Basement 1
M1 Mezzanine 1
R- Roof
-- Whole project (two “dashes”)
N- North elevation view
E- East elevation view
S- South elevation view
W- West elevation view
NE Northeast elevation view
SE Southeast elevation view
SW Southwest elevation view
NW Northwest elevation view
3D 3-dimensional/isometric view
AA Duplicated alphabet - Section view (AA)
LX Longitudinal section for civil works
DT Details
Table 6 – Examples for the view plane field
Code Description
05 Level 5
B3 Basement 3
M2 Mezzanine 2
CC Section view CC
When the CAD file contains only page information such as notes, legend, diagrams, or schedules
instead of CAD models, the view plane is no longer relevant and the two characters can be used for
description of the form of information presented.
Table 7 – Forms of information and codes
Code Forms of information

DG Diagram
LG Legend
NT Notes
SH Schedule
SD Standard drawings
4.4.5 Zone
Zone field represents the construction zone or block number of the project. One (1) alphanumeric
character is used for this field. The codes allowed this field are A to Z, 1 to 9 and the hyphen
character (-). “-“ represents all the zones in the project. If the three characters allocated for the view
plan and zone fields are not relevant to the type of construction, they can be used for further
12
CP 83 : Part 3 : 2001
description of the type-of-work with in-house codes. However, these codes are required to be
documented and communicated between different parties of the project.
4.4.6 Version
Version field represents major revisions of the CAD file. One (1) alphanumeric character is used for
this field. The sequence of codes denoting the version is A, B, C ... Z, 1, 2, 3, … 9. The character “X”
is reserved for referenced files so that the filename does not have to be amended each time it is
updated.
4.4.7 User-defined
User-defined field can be used for further identification or to provide additional information. The
filename will be more than 8 characters if this field is used.
4.5 Directory structure
A logical directory structure is necessary for the management of files for different projects, at various
stages of construction, and between different parties in multi-disciplinary project. The directory
structure becomes critical when filename format A is used and project identification is not captured in
the user-defined field. Directory structure in this code is not mandatory and the following examples
are for illustrative purpose.
Table 8 – Directory structure and examples
Directories Examples
1st Level
Project identification (Year_Project Name) /1999_East Wood/
2nd Level /PD/ for Preliminary design
Project stage /DC/ for Development control approval
/BP/ for Building plan approval
/TD/ for Contract tendering
/CO/ for Construction
/AB/ for As-built drawings
3rd Level /Architectural/
Discipline or type-of-work /Civil/
/Structural/
/Electrical/
/Mechanical/
13
CP 83 : Part 3 : 2001
An example of a directory structure for files under the "East Wood" project for building plan
submission of civil works is as follows:
/1999_East Wood/BP/Civil/
4.6 Coding conventions
4.6.1 For indication of no further subdivision of the information or for all the possible variation of
field, hyphen characters (-) shall be used.
4.6.2 Alphanumeric characters allowed are the letters A to Z, the digits 0 to 9, in addition to the
hyphen (-) and underscore ( _ ) characters.
4.6.3 All fields are left justified.
5 Examples
Filename format A
Example 1: EW00_A2FP31B2C-
A file of the East Wood project in the year 2000 (EW00 in the Project Identification field), prepared by
a second architect (A2 in the Author field), containing floor plans (FP in the Type-of-work field), at
level 31 (31 in the View Plane field) of zone B2 (B2 in the Zone field), and is the third version of the
file (C- in the Version field).
Example 2: EW01_C-RDXX12B-
A file of the East Wood project in the year 2001 (EW01 in the Project Identification field), prepared by
a civil engineer (C- in the Author field), containing road works (RD in the Type-of-work field) of section
“XX” (XX in the View Plane field) in zone 12 (12 in the Zone field), and is the second version of the file
(B in the Version field).
Filename format B
Example 3: A-FP12BC
A file prepared by an architect (A- in the Author field), containing floor plan (FP in the Type-of-work
field), at level 12 (12 in the View Plane field) of zone B (B in the Zone field), and is the third version of
the file (C in the Version field).
Example 4: A2SP---X
A file prepared by a second architect (A2 in the Author field), containing site plan (SP in the Type-of-
work field), covering the whole site (“--“ in the View Plane field and “-“ in the Zone field), and is
used as file to be referenced by other CAD files (X in the Version field).
Example 5: S-B205BB_EW302
A file prepared by a structural engineer (S- in the Author field), containing beam-details sheet 2 (B2
in the Type-of-work field), at level 5 (05 in the View Plane field) zone B (B in the Zone field), and is the
second version of the file (B in the Version field). This file includes project identification and drawing
number (EW and 302) in the user-defined field.
14
CP 83 : Part 3 : 2001
Example 6: E-EL04BA_EL012
A file prepared by an electrical engineer (E- in the Author field), containing electrical supply
installations (EL in the Type-of-work field), at level 4 (04 in the View Plane field) of zone B (B in the
Zone field), and is the first version of the file (A in the Version field). This file includes drawing number
(EL012) in the user-defined field.
Filename format C
Example 7: EWDNR-2A
A file of the East Wood project (EW in the Project Identification field), containing drainage work (DN in
the Type-of-work field), at the roof (R- in the View Plane field) of block 2 (2 in the Zone field), and is
the first version of the file (A in the Version field).
Example 8: EWAC04BC
A file of the East Wood project (EW in the Project Identification field), containing air-conditioning
installations (AC in the Type-of-work field), at level 4 (04 in the View Plane field) of zone B (B in the
Zone field), and is the third version of the file (C in the Version field).
15
CP 83 : Part 3: 2001
Annex A
List of type-of-work codes by discipline
Type-of-work codes in this list are classified according to the major construction disciplines.
Note: In Annexes A and B, numeric variables are represented by "1".
Drawing subject Code

Common to all disciplines
Floor plan FP
Floor plan – Elevation view FE
Floor plan – Cross section view FX
Site plan SP
Site plan – Elevation view SE
Site plan – Cross section view SX
Architectural
Access details AD
Aluminum works AL
Amenities plan AP
Area calculation AR
Bin centres BC
Buildings BD
Cabinets/wardrobes CB
Curtain walls CU
Doors DR
External works EW
Gondolas GD
Ironmongery IM
Kitchen cabinets KC
Lifts and escalators LE
Landscape LS
Miscellaneous – Architectural MA
Parking lots PK
Railings RL
Ramps RP
Reflective ceiling plan CP
Refuse chutes RE
Roofs RF
Signage SG
Staircases SC
Substations SN
Swimming pools SM
Toilets TL
Windows WD
16
CP 83: Part 3: 2001

Civil
Bore holes BH
Bridges BR
Bus shelters/bays BS
Drainage DN
Demolition DM
Earth works EA
Landscape LS
Miscellaneous – Civil MC
Parking lots PK
Piling layout PL
Road works RD
Reclamation RM
Signage SG
Survey plan SV
Sewers SW
Utilities plan UP
Water works WW
Structural
Beams BM
Beam details sheet no. B1
Columns CL
Core walls CW
Footings FT
Loading plan LP
Miscellaneous – Structural MS
Pilecaps PC
Piling layout PL
Retaining walls RW
Roofs RF
Slabs SB
Slab details sheet no. S1
Staircases SC
Steel works SL
Stumps SU
17
CP 83 : Part 3: 2001

Mechanical
Air-conditioning & mechanical ventilation AC
Building automation systems BA
Combined services CS
Compressed air CA
Fire services FS
Fuel oil installation FO
Gas supply GS
Mechanical handling systems MH
Miscellaneous – Mechanical MM
Plumbing services PS
Process works PW
Sanitary services SA
Scrubbers SR
Sewage treatment ST
Steam services SS
Structural coordination SD
Swimming pool SM
Electrical
Electrical power supply EL
Extra-low voltage installation EV
Lifts and escalators LE
Lighting LT
Lightning and earthing LN
Miscellaneous – Electrical ME
Telecommunication TC
18
CP 83: Part 3: 2001
Annex B
List of type-of-work codes in alphabetical order
Type-of-work codes in this list are arranged in alphabetical order.
Note: In Annexes A and B, numeric variables are represented by "1".
Codes Types of Work Discipline

AC Air-conditioning & mechanical ventilation mechanical
AD Access details architectural
AL Aluminum works architectural
AP Amenities plan architectural
AR Area calculation architectural
B1 Beam details sheet no. structural
BA Building automation systems mechanical
BC Bin centres architectural
BD Buildings architectural
BH Bore holes civil
BM Beams structural
BR Bridges civil
BS Bus shelters/bays civil
CA Compressed air mechanical
CB Cabinets/wardrobes architectural
CL Columns structural
CP Reflective ceiling plan architectural
CS Combined services mechanical
CU Curtain walls architectural
CW Core walls structural
DM Demolition architectural/civil
DN Drainage civil
DR Doors architectural
EA Earth works civil
EL Electrical power supply electrical
EV Extra-low voltage installation electrical
EW External works architectural
FO Fuel oil installation mechanical
FE Floor plan – Elevation view common
FP Floor Plan common
FS Fire services mechanical
FT Footings structural
FX Floor plan - Cross section view common
GD Gondolas architectural
GS Gas supply mechanical
IM Ironmongery architectural
KC Kitchen cabinets architectural
LE Lifts and escalators architectural/ electrical
LN Lightning and earthing electrical
19
CP 83 : Part 3: 2001
LP Loading plan structural

LS Landscape architectural/civil
LT Lighting electrical
MA Miscellaneous – Architectural architectural
MC Miscellaneous – Civil civil
ME Miscellaneous – Electrical electrical
MH Mechanical handling systems mechanical
MM Miscellaneous – Mechanical mechanical
MS Miscellaneous – Structural structural
PC Pilecaps structural
PK Parking lots architectural/ civil
PL Piling layout civil/structural
PS Plumbing services mechanical
PW Process works mechanical
RD Road works civil
RE Refuse chutes architectural
RF Roofs architectural/ structural
RL Railings architectural
RM Reclamation civil
RP Ramps architectural
RW Retaining walls structural
S1 Slab details sheet no. structural
SA Sanitary services mechanical
SB Slabs structural
SC Staircases architectural/structural
SD Structural coordination mechanical
SE Site plan – Elevation view common
SG Signage architectural/civil
SL Steel works structural
SM Swimming pools architectural/mechanical
SN Substations architectural
SP Site plan common
SR Scrubbers mechanical
SS Steam services mechanical
ST Sewage treatment mechanical
SU Stumps structural
SV Survey plan civil
SW Sewers civil
SX Site plan – Cross section view common
TC Telecommunication electrical
TL Toilets architectural
UP Utilities plan civil
WD Windows architectural
WW Water works civil
20
CP 83 : Part 3 : 2001
ABOUT SPRING SINGAPORE
SPRING Singapore is an agency under the Ministry of Trade and Industry responsible for helping
Singapore enterprises grow and building trust in Singapore products and services. As the national
standards and accreditation body, SPRING develops and promotes an internationally-recognised
standards and quality assurance infrastructure. SPRING also oversees the safety of general
consumer goods in Singapore. As the enterprise development agency, SPRING works with partners
to help enterprises in financing, capability and management development, technology and innovation,
and access to markets.
SPRING Singapore
1 Fusionopolis Walk
#01-02 South Tower, Solaris
Singapore 138628
Tel: 6278 6666
Fax: 6278 6667
E-mail: enterpriseone@spring.gov.sg
Website: http://www.spring.gov.sg
ABOUT THE NATIONAL STANDARDISATION PROGRAMME
Under the national standardisation programme, SPRING Singapore helps companies and industry to
meet international standards and conformity requirements by creating awareness of the importance of
standardisation to enhance competitiveness and improve productivity, co-ordinating the development
and use of Singapore Standards and setting up an information infrastructure to educate companies
and industry on the latest developments.
SPRING Singapore is vested with the authority to appoint a Standards Council to advise on the
preparation, publication and promulgation of Singapore Standards and Technical References and
their implementation.
Singapore Standards are in the form of specifications for materials and products, codes of practice,
methods of test, nomenclature, services, etc. The respective committee or working group will draw
up the standards before seeking final approval from the Standards Council or the relevant Standards
Committee. To ensure adequate representation of all viewpoints in the preparation of Singapore
Standards, all committees appointed consist of representatives from various interest groups which
include government agencies, professional bodies, tertiary institutions and consumer, trade and
manufacturing organisations.
Technical References are transition documents developed to help meet urgent industry demand for
specifications or requirements on a particular product, process or service in an area where there is an
absence of reference standards. Unlike Singapore Standards, they are issued for comments over a
period of two years before assessment on their suitability for approval as Singapore Standards. All
comments are considered when a technical reference is reviewed at the end of two years to
determine the feasibility of its transition to a Singapore Standard. Technical References can
therefore become Singapore Standards after two years, continue as Technical References for further
comments or be withdrawn.
In the international arena, SPRING Singapore represents Singapore in the International Organisation
of Standardisation (ISO), the Asia-Pacific Economic Co-operation (APEC) Sub-committee for
Standards and Conformance (SCSC) and in the ASEAN Consultative Committee on Standards and
Quality (ACCSQ). The Singapore National Committee of the International Electrotechnical
Commission which is supported by SPRING Singapore, represents Singapore in the IEC.
21
COPYRIGHT

The Singapore Standardisation
Programme
is managed by
SPRING Singapore
1 Fusionopolis Walk,
#01-02
South Tower, Solaris
Singapore 138628

Tel : +65 6278 6666
Fax : +65 6278 6667

www.spring.gov.sg

Ecopy-CP 83-2-2000

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ecopy-CP 83-2-2000

Uploaded by

Copyright:

Available Formats

Licensed by SPRING Singapore to LINH/MS, SYNECTICS CONSULTING CORPORATION

Singapore Standards eShop Order No: 6800025511/Downloaded:2014-01-17

Code of practice for construction

First published, 2001

The Technical Committee on Construction Industry IT Standards appointed by the IT Standards

Chairman : Mr Edward D'Silva Singapore Institute of Architects

Members : Dr Tan Kee Wee Building and Construction Authority

Convenors : Mr Lee Chuan Seng Institution of Engineers Singapore

1. Mr Tsang Pui Sum

A List of type-of-work codes by discipline 16

1 Description of fields in filename format A 9

Code of practice for construction computer-aided design (CAD)

3.1 CAD file

CAD file is a digital file containing CAD models or related information.

3.2 Filename fields

3.4 Project identification

3.6 View plane

Zone refers to the construction zone or block number of the project.

Version refers to the major revisions of the CAD file.

4 Concept, formats and codes

4.2.1 Full conformance

4.2.2 Conceptual conformance

4.3 Formats of filename

4.3.1 Filename format A

Table 1 – Description of fields in filename format A

Name of field Description of field Number of

Project Author Type- View Zone Version User-defined*

Figure 1 – Filename format A

Please refer to 4.5 for the recommended directory structure.

Table 2 – Description of fields in filename format B

Name of field Description of field Number of

Author Type- View Z V User-defined*

(NOTE: Z - Zone field, V - Version field, * - Optional field)

Figure 2 – Filename format B

Table 3 – Description of fields in filename format C

Name of field Description of field Number of

Project Type- View Z V User-defined*

(NOTE: Z - Zone field, V - Version field, * - Optional field)

4.4 Filename fields

4.4.1.1 First character

Table 4 – Codes for the first character of author field

Code Author description

4.4.1.2 Second character

4.4.2 Project identification

4.4.4 View plane

In Table 5, numeric variables are represented by "1".

Table 5 – Codes for the view plane field

Table 6 – Examples for the view plane field

Table 7 – Forms of information and codes

Code Forms of information

4.5 Directory structure

Table 8 – Directory structure and examples

Project identification (Year_Project Name) /1999_East Wood/

2nd Level /PD/ for Preliminary design

Project stage /DC/ for Development control approval

/BP/ for Building plan approval

/TD/ for Contract tendering

/CO/ for Construction

/AB/ for As-built drawings

3rd Level /Architectural/

Discipline or type-of-work /Civil/

4.6 Coding conventions

4.6.3 All fields are left justified.

List of type-of-work codes by discipline