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 Scope

2 Purpose

3 Definitions

4 Concept, formats and codes

5 Examples

ANNEXES

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

B List of type-of-work codes in alphabetical order 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 Filename format A 9

2 Filename format B 10

3 Filename format C 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.

2. Compliance with a Singapore Standard does not exempt users from legal obligations.

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.

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.

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

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

r ~ a m e of field 1 Description of field 1 Numberof I characters

Project I Represent files of the same project. I 3 - 5; identification 1 4 is recommended

Type-of-work View plane

The seven fields in filename format A are to be arranged in the format as shown in Figure 1.

Author I Individual/company/organisation responsible I 2

Zone Version User-defined

. -

for creating the file. Nature and scope of work. Level in a multi-storey building or orientation

Figure 1 - Filename format A

2 2

of an elevation view. Zone of the construction site Major revisions User-defined code for in-house applications. (optional field)

4.3.2 Filename format B (alternative - for computer system that can only handle 8.3 filename format)

2 2 -

Project I.D.

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.

User-defined' View plane

Author

Table 2 - Description of fields in filename format B

m e - of-work

Zone Version

Number of characters

2

Name of field

Author

Type-of-work View plane

I (optional field)

Description of field

Individual/company/organisation responsible for

Zone Version User-defined

creating the file. Nature and scope of work. Level in a multi-storey building or orientation of

2 2

an elevation view. Zone of the construction site Major revisions User-defined code for in-house applications.

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.

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

Figure 2 - Filename format B

Author

4.3.3 Filename format C (alternative - for computer system that can only handle 8.3 filename format)

Z

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.

Type- of-work

Table 3 - Description of fields in filename format C

View plane

V User-defined*

Name of field

Project identification Type-of-work View plane

Zone

The five mandatory fields and an optional filed in filename format C are to be arranged in the format as shown in Figure 3.

Description of field

Represent files of the same project.

Version User-defined

Number of characters

2

Nature and scope of work. Level in a multi-storey building or orientation of an elevation view. Zone of the construction site

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

Figure 3 - Filename format C

2 2

1 - - - ~

Project I.D.

4.4 Filename fields

Major revisions User-defined code for in-house applications. (optional field)

4.4.1 Author

1 -

' m e - of-work

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.

View plane

Z V User-defined'

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

I E I Electrical Engineer 1

Code A

C

I L 1 Land Surveyor 1

Author description Architect

Civil Engineer

S I Structural Engineer T ( Telecommunication/Signal Engineer

M N

( V I Other disciplines 1

Mechanical Engineer

Equipment Supplier

I x 1 Contractor 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 - Examples for the view plane field

Code I Description 05 1 Level 5

FCC 1 Section view CC

~3 M2

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.

Basement 3

Mezzanine 2

Table 7 - Forms of information and codes

Code I Forms of information DG IDiagram LG [ Legend NT I Notes

I SH I Schedule I I

SD I 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 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 - Directory structure and examples

Directories

1 Level

Project identification (Year-Project Name)

2nd Level

Project stage

3rd Level

Discipline or type-of-work

Examples

/PD/ for Preliminary design

/DCl for Development control approval

/BPI for Building plan approval

/TD/ for Contract tendering

/CO/ for Construction

/ABl for As-built drawings

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

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: 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 (C- in 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 "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: A2 SP - - -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-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.

Note: In Annexes A and 8, numeric variables are represented by "1 ".

Drawing subject I Code Common to all disciplines

I Amenities plan 1 AP 1

Floor plan Floor plan - Elevation view

Floor plan - Cross section view Site plan Site plan - Elevation view Site plan - Cross section view

FP FE FX SP SE SX

Buildings I BD Cabinetslwardrobes 1 CB

Area calculation Bin centres

I Curtain walls I CU I

Architectural

AR BC

Access details Aluminum works

( Gondolas 1 GD 1

AD AL

Doors External works

DR EW

-

lronmongery Kitchen cabinets

-

IM KC

Lifts and escalators Landscape Miscellaneous - Architectural

LE LS MA

Parking lots Railings

PK RL

Ramps Reflective ceiling plan Refuse chutes

I Staircases I SC I

RP CP RE

Roofs Signage

RF SG

I Toilets I TL I

Substations Swimming pools

I Windows I WD

SN SM

CP 83: Part 3: 2000

Drawing subject I Code Civil

Bore holes I BH

1 Bridges I BR I I Bus shelterslbavs 1 BS 1 I Drainage I DN I

I Landscape I LS I

Demolition Earth works

DM EA

Miscellaneous - Civil Parking lots

1 Reclamation 1 RM 1

MC PK

Piling layout Road works

PL RD

I Sewers I SW I

Signage Survey plan

I Utilities ~ l a n 1 UP 1

SG SV

I Water works I WW I Structural

Beams I BM I Beam details sheet no. I B1 I

I Core walls I CW I Footings Loading plan Miscellaneous - Structural

I Retaining walls I RW I

FT LP MS

Pilecaps Piling layout

PC PL

I Steel works I SL I

Slab details sheet no. Staircases

S1 SC

CP 83 : Part 3: 2000

I Drawina subiect I Code I

I Combined services I CS I

Mechanical Air-conditioning & mechanical ventilation Building automation systems

I Gas supply 1 GS I

AC BA

Compressed air Fire services Fuel oil installation

I Mechanical handling systems I MH I

CA FS FO

I Process works I PW I

Miscellaneous - Mechanical Plumbing services

MM PS

I Sewage treatment I ST I

Sanitary services Scrubbers

SA SR

Swimming pool 1 SM Electrical

Steam services Structural coordination

I Electrical power supply I EL I

SS SD

Extra-low voltage installation Lifts and escalators

1 Telecommunication I TC

EV LE

Lighting Lightning and earthing Miscellaneous - Electrical

LT LN ME

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 Discipline AC I Air-conditioning & mechanical ventilation I mechanical

I - I

AD ( Access details ( architectural

1 AL I Aluminum works I architectural AP AR B1 BA BC

1 BM 1 Beams 1 structural

Amenities plan Area calculation Beam details sheet no.

BD 1 Buildings BH I Bore holes

architectural architectural structural

Building automation systems

Bin centres architectural civil

I CA I Compressed air 1 mechanical I

mechanical architectural

BR BS

I CB I I

I Cabinetslwardrobes 1 architectural - - I I

CL I Columns I structural

Bridges Bus shelterslbays

civil civil

I CU I Curtain walls I architectural

CP CS

Reflective ceiling plan Combined services

CW DM

1 EA 1 Earth works

architectural mechanical

DN 1 Drainage DR I Doors

1 civil

Core walls Demolition

civil architectural

-

structural architecturallcivil

I EW I External works I architectural I

EL EV

I FO I Fuel oil installation 1 mechanical 1 ( FE I Floor plan - Elevation view I common I

Electrical power supply Extra-low voltage installation

electrical electrical

I Footings I structural

FP FS

I - I

FX 1 Floor ~ l a n - Cross section view I common - -- I I

GD I Gondolas I architectural

Floor Plan Fire services

common mechanical

1 KC 1 Kitchen cabinets 1 architectural I

GS 1 Gas supply I M I lronmongery

I LE I Lifts and escalators I architectural1 elec6ical I

mechanical architectural

CP 83 : Part 3: 2000

I LN I Lightning and earthing I electrical

I LT I Lighting I electrical 1

LP LS

1 ME I Miscellaneous - Electrical I electrical

Loading plan Landscape

MA MC

structural architecturallcivil

Miscellaneous -Architectural Miscellaneous - Civil

MH MM

architectural civil

MS PC PK

I PW I Process works I mechanical I

Mechanical handling systems Miscellaneous - Mechanical

PL PS

mechanical mechanical

Miscellaneous - Structural Pilecaps Parking lots

structural structural architectural1 civil

Piling layout Plumbing services

RD RE

I RM I Reclamation I civil I

civillstructural mechanical

RF RL

Road works Refuse chutes

1 S1 I Slab details sheet no. I structural I

-

civil architectural

Roofs Railings

RP RW

architectural1 structural architectural

Ramps Retaining walls

SA SB

1 SE I Site plan - Elevation view I common I

architectural

structural

SC SD

Sanitary services Slabs

1 SM I Swimming pools I architecturallmechanical

mechanical structural

Staircases Structural coordination

SG SL

I - .

I SN I

1 Substations I architectural

architectural/structural mechanical

Signage Steel works

architecturallcivil structural

.- I I

I ST I Sewage treatment I mechanical

SP I Site plan

SR SS

common Scrubbers Steam services

SU SV

mechanical

mechanical

SW SX TC

I WD I Windows I architectural

Stumps Survey plan

TL UP

WW I Water works 1 civil

structural civil

Sewers Site plan - Cross section view Telecommunication

civil common

electrical Toilets Utilities plan

architectural civil

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 Co- operation (APEC) Sub-committee for Standards and Conformance (SCSC) and in the ASEAN Consultative Committee for Standards and Quality (ACCSQ).