Sie sind auf Seite 1von 19

SINGAPORE STANDARD

CP 83 : Part 3 : 2001
(ICS 35.240.1 0)

CODE OF PRACTICE FOR

Construction computer-aided design (CAD)


Part 3 :Organising and naming of CAD files

Published by SPRING Singapore 2 Bukit Merah Central Singapore 159835 SPRING Singapore Website: www.spring.gov.sg Standards Website: www.standards.org.sg

SPRING sr ngapore

CP 83 : Part 3 : 2001

Contents
Page
Foreword

CODE OF PRACTICE
1
2
3 4

Scope Purpose Definitions Concept, formats and codes Examples

ANNEXES

List of type-of-work codes by discipline List of type-of-work codes in alphabetical order

16 19

TABLES
Description of fields in filename format A Description of fields in filename format B Description of fields in filename format C Codes for the first character of author field Codes for view plane field Examples for view plane field Forms of information and codes Directory structure and examples

FIGURES
1
2
3

Filename format A Filename format B Filename format C

9 10 10

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. Compliance with a Singapore Standard does not exempt users from legal obligations.

2.

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.

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.

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/organisationresponsible 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.

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-storeybuilding or the orientation of the elevation view.

3.7

Zone

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

CP 83 : Part 3 : 2001

3.8

Version

Version refers to the major revisions of the CAD file.

User-defined field refers to the field for users to provide additional information of the CAD file.

4
4.1

Concept, formats and codes


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.

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


Numberof characters 3 - 5; 4 is recommended 2
2 2 2 2
-

~ a m of field e

Project identification Author Type-of-work View plane Zone Version User-defined

1 Description of field 1 I Represent files of the same project. I 1 I Individual/company/organisationresponsible I


.
-

for creating the file. Nature and scope of work. Level in a multi-storey building or orientation of an elevation view. Zone of the construction site Major revisions User-definedcode 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 I.D. Author meof-work View plane Zone Version User-defined'

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


Name of field Author Type-of-work View plane Zone Version User-defined Description of field Number of characters 2
2

Individual/company/organisationresponsible for creating the file. Nature and scope of work. Level in a multi-storey building or orientation of an elevation view. Zone of the construction site Major revisions User-defined code for in-house applications. (optional field)

2
1 1
-

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 Typeof-work View plane

User-defined*

(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


Name of field Project identification Type-of-work View plane Zone Version User-defined Description of field Represent files of the same project. Nature and scope of work. Level in a multi-storey building or orientation of an elevation view. Zone of the construction site Major revisions User-defined code for in-house applications. (optional field)
~

Number of characters 2 2 2
1 1
-

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 I.D. 'meof-work View plane

User-defined'

(NOTE: Z

Zone field, V - Version field, *

Optional field)

Figure 3

Filename format C

4.4
4.4.1

Filename fields
Author

Author field represents the individual/company/organisationresponsible 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.

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 Author description Architect Civil Engineer Electrical Engineer Land Surveyor Mechanical Engineer Equipment Supplier

Code
A

I
I

C E L M N
S

I
1

1
1

I Structural Engineer
I Other disciplines
1
Contractor

T V

( Telecommunication/Signal Engineer

1
I

I
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.

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".

CP 83 : Part 3 : 2001
Table 5 - Codes for the view plane field

Numeric - Level of storey or lowest

Basement 1

Table 6 Code 05

Examples for the view plane field Description

I 1 Level 5

FCC 1

~3 M2

Basement 3 Mezzanine 2 Section view CC

Nhen 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 Code

- Forms of information and codes


Forms of information

I
IDiagram [ Legend I Notes

DG LG
NT

SH

I
I

SD
4.4.5

Schedule Standard drawings

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 2, 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

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 ... 2,1, 2, 3, ... 9. The character "X" is resewed for referenced files so that the filename does not have to be amended each time it is updated.

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
Directories
1 Level

Directory structure and examples


Examples

Project identification (Year-Project Name)


2ndLevel

/PD/ for Preliminary design /DCl for Development control approval /BPI for Building plan approval

Project stage

/TD/ for Contract tendering


/CO/ for Construction /ABl for As-built drawings 3rdLevel Discipline or type-of-work

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:

4.6

Coding conventions

For indication of no further subdivision of the information or for all the possible variation of 4.6.1 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.

Examples

Filename format A
Example 1:

EWOO-A2FP31B2C-

A file of the East Wood project in the year 2000 (EWOO 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 82 (B2 in the Zone field), and is the third version of the file (Cin the Version field).

Afile of the East Wood project in the year 2001 (EWO1 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 " X X (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:

A2 SP - - -X

A file prepared by a second architect (A2 in the Author field), containing site plan (SP in the Type-ofin work field), covering the whole site ("--" in the View Plane field and "-" the Zone field), and is used as file to be referenced by other CAD files (X in the Version field).

Example 5:

S-B2 05BB-EW3 02

A file prepared by a structural engineer (S- in the Author field), containing beam-details sheet 2 (82 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.

CP 83 : Part 3 : 2001
Example 6:
E-ELO4BA-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 ldentification 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:

EWACO 4BC

A file of the East Wood project (EW in the Project ldentification 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).

CP 83 : Part 3: 2000

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. numeric variables are represented by "1". Note: In Annexes A and 8,

Drawing subject Common to all disciplines Floor plan Floor plan - Elevation view Floor plan - Cross section view Site plan Site plan - Elevation view Site plan - Cross section view Architectural Access details Aluminum works I Amenities plan Area calculation Bin centres Buildings Cabinetslwardrobes I Curtain walls Doors External works ( Gondolas lronmongery Kitchen cabinets Lifts and escalators Landscape Miscellaneous - Architectural Parking lots Railings Ramps Reflective ceiling plan Refuse chutes Roofs Signage I Staircases Substations Swimming pools I Toilets Windows

I Code
FP FE FX SP SE SX AD AL 1 AP AR BC I BD

1 CB I CU
DR EW 1 GD IM KC LE LS MA PK RL RP CP RE RF SG I SC SN SM I TL I WD

I 1

I I

CP 83: Part 3: 2000

Drawing subject Civil


Bore holes Bridges Bus shelterslbavs Drainage Demolition Earth works I Landscape Miscellaneous - Civil Parking lots Piling layout Road works 1 Reclamation Signage Survey plan I Sewers I Utilities ~ l a n I Water works

I Code
I BH
I BR 1 BS I DN
DM EA I LS MC PK PL RD 1 RM SG SV I SW 1 UP

1 I I

I 1 I I

1
I 1 I I I

I
Structural

WW

I I

Beams Beam details sheet no. Core walls Footings Loading plan Miscellaneous - Structural Pilecaps Piling layout Retaining walls

I BM
I B1 I CW
FT LP MS PC PL I RW

Slab details sheet no. Staircases Steel works

S1 SC I SL

CP 83 : Part 3: 2000

Drawina subiect Mechanical Air-conditioning & mechanical ventilation Building automation systems Combined services Compressed air Fire services Fuel oil installation Gas supply Mechanical handling systems Miscellaneous - Mechanical Plumbing services Process works Sanitary services Scrubbers Sewage treatment Steam services Structural coordination Swimming pool Electrical Electrical power supply Extra-low voltage installation Lifts and escalators Lighting Lightning and earthing Miscellaneous - Electrical Telecommunication

Code

I
I I I

AC BA I CS CA FS FO 1 GS

I
I I I

MH

MM PS I PW SA SR I ST SS SD SM

I EL
EV LE LT LN ME I TC

CP 83: Part 3: 2000

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

1 Types of Work
I

1 I I

AC AD AL AP AR B1 BA BC BD BH BM BR BS I CA CB CL CP CS CU CW DM DN DR 1 EA EL EV I EW I FO ( FE FP FS
-

I Air-conditioning & mechanical ventilation (

I Discipline
I
I

Access details Aluminum works Amenities plan Area calculation Beam details sheet no. Building automation systems Bin centres Buildings Bore holes Beams Bridges Bus shelterslbays Compressed air Cabinetslwardrobes Reflective ceiling plan Combined services

mechanical architectural architectural architectural architectural structural mechanical architectural architectural civil civil civil

1
I
I

1 structural
1 1
I

I I Columns
I

I structural
architectural mechanical

mechanical architectural

1 I
1 I I I

Curtain walls Core walls Demolition Drainage Doors Earth works Electrical power supply Extra-low voltage installation External works Fuel oil installation Floor plan - Elevation view Floor Plan Fire services Footings Floor ~ l a - Cross section view n Gondolas Gas supply lronmongery Kitchen cabinets Lifts and escalators

1 I 1 I

I
I

FX GD GS
- --

1 I

I
I

IM

I
1 I

architectural structural architecturallcivil civil architectural civil electrical electrical architectural mechanical common common mechanical structural common architectural mechanical architectural

1
I

1 KC I LE

1 architectural I architectural1elec6ical

I I

CP 83 : Part 3: 2000

I LN
LP LS I LT MA MC ME MH MM MS PC PK PL PS I PW RD RE RF RL I RM RP RW 1 S1 SA SB SC SD 1 SE SG SL SM SN . SP SR SS ST SU SV SW SX TC TL UP WD WW

I Lightning and earthing


I
Loading plan Landscape Lighting Miscellaneous -Architectural Miscellaneous - Civil Mechanical handling systems Miscellaneous - Mechanical Miscellaneous - Structural Pilecaps Parking lots Piling layout Plumbing services Process works Road works Refuse chutes Roofs Railings Reclamation Ramps Retaining walls Slab details sheet no. Sanitary services Slabs Staircases Structural coordination Site plan - Elevation view Signage Steel works
- .

I electrical
I
structural architecturallcivil electrical architectural civil mechanical mechanical structural structural architectural1civil civillstructural mechanical mechanical civil architectural architectural1structural architectural civil architectural structural structural mechanical structural architectural/structural mechanical common architecturallcivil structural

I Miscellaneous - Electrical

I electrical

I
-

I I

I I

I I

1 I I

I Swimming pools
I

I architecturallmechanical
I

1
I

Substations Site plan Scrubbers Steam services Stumps Survey plan Sewers Site plan - Cross section view Telecommunication Toilets Utilities plan

II architectural
common mechanical mechanical

I Sewage treatment

I mechanical
structural civil civil common electrical architectural civil

I Windows

I Water works

1 civil

architectural

CP 83: Part 3: 2000

ABOUT THE STANDARDS, PRODUCTIVITY AND INNOVATION BOARD (SPRING SINGAPORE)


The mission of the Standards, Productivity and lnnovation Board, or SPRING Singapore in short, is to raise productivity so as to enhance Singapore's competitiveness and economic growth for a better quality of life for our people. In carrying out its mission, SPRING Singapore focuses on three areas: productivity and innovation, standards and conformance, and small and medium-sized enterprises (SMEs) and the domestic sector.

Productivity and lnnovation


The Productivity and lnnovation focus has four key thrusts: promotion, business excellence, people excellence and service excellence. Under its promotion thrust, SPRING Singapore spearheads the national Productivity and lnnovation Movement. The movement aims to cultivate strong commitment to productivity and innovation in all sectors of the economy and to develop a creative workforce and innovative enterprises. SPRING Singapore serves as Secretariat to the National lnnovation Council. Using its internationally recognised Business Excellence programme, SPRING Singapore assists organisations to systematically achieve world-class standards of business excellence. At the apex of the programme is the Singapore Quality Award (SQA). Under its People Excellence thrust, SPRING Singapore initiates leading-edge programmes to enhance the capabilities of the workforce. This enables them to scale new heights and achieve higher levels of productivity. SPRING Singapore administers the Skills Development Fund (SDF), which provides incentives to help companies defray the cost of training their employees. The incentives are financed through collections from the Skills Development Levy imposed on employers. In view of the importance of service quality to competitiveness, SPRING Singapore spearheads Service Excellence in Singapore. The goal is to raise service quality levels in Singapore to world-class standards.

Standards and Quality


The focus area of Standards and Quality has two major thrusts: standardisation and conformity assessment, and measurement infrastructure development. These are aimed at enhancing productivity, facilitating market access, ensuring safety and health, and protecting the environment. As the national standards body, SPRING Singapore administers the Singapore standardisation programme, which involves the development and implementation of standards in industry. Please visit www.standards.ora.sq for more information. As standards and conformance issues can be potential barriers to trade, SPRING Singapore actively supports the government's Free Trade Agreement (FTA) strategy to ensure market access. As the national authority for the accreditation of conformity assessment bodies, SPRING Singapore audits and accredits quality systems and the competence of quality system certifiers, inspection bodies, and testing and calibration laboratories. SPRING Singapore enforces the Weights & Measures Act and Regulations to protect consumers by ensuring that market transactions based on weights and measures are accurate, fair and comply with the relevant standards. As the Safety Authority, SPRING Singapore administers the Singapore Consumer Protection (Safety Requirements) Registration Scheme to ensure that the controlled goods used by consumers in Singapore are safe. As Singapore's national metrology institute, SPRING Singapore ensures that the measurement infrastructure adequately supports the growing needs of industry. It maintains Singapore's national measurement standards for use by the industry, and provides the vital link between measurements carried out in Singapore and those in the international system.

CP 83 : Part 3: 2000

SMEs & Domestic Sector


The SMEs and Domestic Sector area of focus has two thrusts: broad-based enterprise upgrading and industry transformation. SPRING Singapore serves as the first point of contact for SMEs that need information and assistance for upgrading. As the lead agency spearheading the upgrading of SMEs, it adopts a total approach to developing SMEs into vibrant and resilient enterprises. SPRING Singapore spearheads the transformation of the domestic sector. The goal is to create a vibrant, dynamic and resilient domestic sector that is able to contribute significantly to the overall economy. SPRING Singapore administers two key financial incentive schemes for SMEs. The first is the Local Enterprise Finance Scheme (LEFS), which is a fixed interest rate loan for SMEs to expand and develop new capabilities. The second is the Local Enterprise Technical Assistance Scheme (LETAS), which is a consultancy grant scheme to help SMEs acquire new competencies in operational management. SPRING Singapore 2 Bukit Merah Central Singapore 159835 Tel: (65) 6278 6666 Fax: (65) 6278 6667 E-mail: queries@spring.gov.sg Website: http:llwww.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 standards committee will draw up the standards before seeking final approval from the Standards Council. 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 lnternational Organisation of Standardisation (ISO), the International Electrotechnical Commission (IEC), the Asia-Pacific Economic Cooperation (APEC) Sub-committee for Standards and Conformance (SCSC) and in the ASEAN Consultative Committee for Standards and Quality (ACCSQ).