DEL AEROPUERTO EL DORADO, BOGOTA D.C. ( ) CADD STANDARDS. Version Date Revision Description Pages modified

Transcription

1 Version Date Revision Description Pages modified V1 22/12/2006 First issue - V2 15/02/2007 Drawing types (A & P) modified Appendix I V3 18/04/2007 Title block modified Page 24 V4 22/08/2007 Revised text All pages Proyecto de Modernización y Expansión del Aeropuerto el Dorado, en la ciudad de Bogota D.C. CADD Standards Author : D. PENNA ADPI CAD Manager Date : 22/12/2006 Visa : Page : 1/28 Checked by: D. PENNA ADPI CAD Manager Date : - Visa : Approuved by: F. Starling Date : - Visa : Diffusion by : Date : - Ref.: CADD Standards-en Page 1/28

2 Page 2/28

3 SUMMARY A GENERALITIES 5 A1. OBJECTIVE 6 A2. INTRODUCTION 6 A3. GENERAL ORGANISATION 7 A3.1 MODEL FILES 7 A3.1.1 NON-INDEXED MODEL FILES (FILE IN EVOLUTION) EX: AFP-C100-L1.DWG 7 A3.1.2 INDEXED MODEL FILES (FIXED FILE) EX: AFP-C100-L1-003.DWG 7 A3.2 SHEET FILES 8 A3.2.1 SHEET FILE ANNOTATIONS 8 A3.3. PLOT FILES 9 A3.4 SUPPORT FILES 9 A3.5 THE «ADDED VALUE» SYSTEM 9 A3.6 PLOT FILES (READY TO PLOT) 9 A4. GENERAL REQUIREMENTS & QUALITY OF CAD FILES 10 A4.1 CREATION OF MODEL FILES 11 A4.1.1 DRAWING UNITS 11 A4.2 CREATION OF SHEET FILES AND LAYOUT 12 A4.2.1 OBJECT SPACE: MODEL FILES AND ANNOTATIONS 12 A4.2.2 PAPER SPACE: PRESENTATION ELEMENTS 13 A4.2.3 UTILISATION OF CALLOUS AND TITLE BARS 14 A4.3 UTILISATION OF TEXTS 16 A4.3.1 THE THREE CATEGORIES OF ANNOTATIONS 17 A4.4 UTILISATION OF DIMENSIONS 18 A5 PLOT CONFIGURATION 19 A5.1 THE CTB FILE 19 A5.2 SECONDARY COLOURS 19 A6 INDEXATION AND DRAWING SUBMISSIONS 19 A6.1 OFFICIAL SHEET FILE REVISIONS 19 A6.2 QUALITY CONTROL 20 A6.1.3 WORK IN PROGRESS (WIP) 20 A7. DOCUMENTS EXCHANGE 21 A7.1 INCOMING DOCUMENTS 21 A7.2 OUTGOING DOCUMENTS 22 B PROJECT SPECIFICITIES 23 Page 3/28

4 B1. FILE CLASSIFICATION AND NAMING 24 B1.1 MODEL FILE NAMING 24 B1.1.1 MODEL FILE INDEXATION 25 B1.2 SHEET FILE NAMING 25 B1.2.1 FILLING OUT THE TITLE BLOCK 26 B REVISION TABLE ENTITIES & TABLE OF PARTICIPANTS 26 B TITLE BLOCK CONTENTS 27 B2. PROTOTYPE 28 B3. PROJECT CTB FILES 28 B4. IDENTIFICATION SYMBOLS 28 B5. DRAWING TEMPLATES 28 Page 4/28

5 A GENERALITIES Page 5/28

6 A1. OBJECTIVE This document has for objective the harmonisation of elements affecting production, verification and communication of drawings on the project Modernizacion y Expansion del Aeropuerto el Dorado, en la ciudad and the methodology used for the production of these drawings within the framework of the ADPi Quality Management System (QMS) and ISO 9001 standards. Quality Management System documents aim to provide a well-controlled and efficient production process within ADPi. This procedure applies to all ADPi entities, subconsultants and subcontractors. A2. INTRODUCTION Large and complex projects require rigorous and structured drawing management. Strong homogeneity between documents is vital for their communication, comprehension and exploitation. Within the framework of a uniform system, this document establishes conditions under which ADPi will take delivery of electronic CAD documents at the time of submissions. These standards are directly based on existing procedures of ADP and ADPi as well as the United States National CAD Standards (NCS) Version 2 (published by Institute of Building Sciences) and the CADD Data Standard from Los Angeles World Airports (LAWA) for specific airport information. The use of known international standards facilitates the understanding and transfer of project information between entities. Page 6/28

7 A3. GENERAL ORGANISATION Graphical documents are to be organised within the project so as to guarantee easy and immediate accessibility, and to ensure the traceability of evolutions amongst safeguarded documents. CAD files on ADPi projects are of five types: - Non-indexed Model files - Indexed Model files - Sheet files - Plot files - Support files A3.1 MODEL FILES A3.1.1 NON-INDEXED MODEL FILES (FILE IN EVOLUTION) EX: AFP-C100-L1.DWG Non-indexed model files are the working files used on a daily basis by design teams. They contain graphical elements corresponding to a study group or precise functional element (ie: A level, a section, an elevation, a detail or a zoning) or any other type of drawing which may be overlaid such as recurring text, lighting layout or utilities network. The purpose of project division into various Model files: Prevent files becoming overloaded with seldom used information Avoid drawing redundancy Reduce file sizes Classify graphical information within files around related topics Avoid problems generated by multiple users trying to access a single file. By definition, non-indexed Model files are in perpetual evolution and represent dynamically the progress of project design. A3.1.2 INDEXED MODEL FILES (FIXED FILE) EX: AFP-C100-L1-003.DWG Indexed Model files represent the state of the design frozen at a given moment and carry an index making it possible to identify them individually. They are instances of draft files at predefined milestones. Files received from subconsultants should not be indexed, ADPi will assign an index after validation. They are primarily intended for communication of updated project data to partners, subconsultants, subcontractors and clients. It is therefore important to carry out checks at the time of their creation, in particular to make sure that data is coordinated, and that the project Drawing Standards have been respected. Note: Only Indexed Model files should be communicated to other companies. Page 7/28

8 A3.2 SHEET FILES Sheet files are the source of plotted contractual drawings. They consist of an assembly of Model files and annotation within a page layout (Title block, frame, legends, texts, etc. : see chapter A4.2). They include a revision table on the Title block indicating the revision index, the date and the description. They must systematically be "ready to plot", with a minimum of intervention. 1 Sheet files Principe of Sheet and Model files Model files Each model file can be referenced multiple times A B C D Sheet files 1 sheet file = 1 drawing + n external references Sheet files and Model files Both file types (model and sheet) are produced separately. Model files represent a library of elements that may be referenced, without constraint, by sheet files when necessary. Sheet files may reference as many model files as necessary. 1 SHEET FILE = 1 DRAWING Fig A3.2.1 SHEET FILE ANNOTATIONS IMPORTANT: The same text must never appear in more than one model file. Different text sizes for different scales must never be found in the same file. See Section A4.3 Utilisation of texts for more information. The separation of text from the model file offers the following advantages: - Production of clean Model files more easily exploitable by other disciplines. - Reduction of errors related to page layout (overlapping texts from different files, offscreen texts, bad text sizes, etc). - Reduction of errors related to an incorrect manipulation of layers within the sheet file. - Simplification of drawings preparation. - Simplified understanding and reuse of drawings for the client. Page 8/28

9 A3.3. PLOT FILES Plot files are non-modifiable digital presentations of paper plans. They are created from Sheet files, preferably in Portable Document Format (PDF). A3.4 SUPPORT FILES Support files are files necessary for the production of Model files and Sheet files. They would typically include: Drawing standards, project specific procedures, CTB files, title block, symbols and templates. These files are available on request. A3.5 THE «ADDED VALUE» SYSTEM The basis of this system works on the principle of "added value": each CAD designer may use other disciplines Model files inserted into their own drawing as external references, once these references are detached, only the Added Value is conserved (the part of the drawing that is unique). This system avoids repetition of information between drawings and reduces file sizes. Only the discipline originator for a drawing has the right of modification. A3.6 PLOT FILES (READY TO PLOT) N.B: This section is only applicable to ADPi. RTP files [or PAT files (Prêt à Tracer)] are the draft copies of future Sheet files, used for plotting control or validation. Available for the duration of the project, they indicate the progression of a Sheet file at any moment. These files use Model files as external references, (therefore non indexed files), allowing pagesetting for contractual plans. Page 9/28

10 A4. GENERAL REQUIREMENTS & QUALITY OF CAD FILES Problems can be generated by the nonconformity of CAD files. In general any file, submitted or exchanged within the framework of the project must be structured so as to satisfy this protocol and to be free from any malfunction or error preventing normal use of all or part of the file. This includes any file that is considered, by extension, as unusable or any file or group of files to which the associated files necessary to their exploitation are not attached. AutoCAD files must be: Saved in format AutoCAD 2004 or posterior. Because of compatibility difficulties between various data formats, the only file format accepted for the creation of files intended for communication with ADPi (or other companies related to the project) is AutoCAD version 2004 or posterior. All software used should be in compliance with laws present in the country of origin. All External References must be inserted in mode Overlay Purged, of minimum file size and free of surplus objects. The absence of unneeded elements makes comprehension easier and increases transfer speeds. As an indication please take care that file sizes do not exceed 2Mo. Free of 'proxy' objects. Prohibition of objects created with the applications ARX and any objects that cannot be created within AutoCAD, such as customized objects of Mechanical Desktop or Architectural Desktop. These entities do not allow for parametric edition within AutoCAD and often require a difficult decomposition. Free of Xdata. No extended data attached to objects is permitted. Free of macros. No macros or automations should be present in the files received by ADPi. Free of layer filters. These filters can quickly become a large part of the file size. They are not affected by purging. They can be inserted with blocks but remain within the drawing after the removal of the block. A preliminary cleaning of blocks is advised. Without line thickness assigned to layers. Only the project CTB file is used to calibrate line thicknesses. Free of 3D objects and 3D surfaces. The drawings will be exclusively 2D with no 3D objects (including blocks). All entities must be at zero in the Z axis. Conform to the project CADD Standards. In accordance with indications given within these projects Standards. This last point includes key elements of drawing design that must be respected: - The nomenclature of the model files and sheet files (see part B) - The use of dedicated layers respecting the nomenclature, colour and line type (cf Appendix II & III) - The composition of sheet files, the use of title bars and referent blocks for sections, elevations and details (described hereafter). - The use of text within drawings (see section A4.3) Page 10/28

11 A4.1 CREATION OF MODEL FILES All model files must be named in accordance with the adopted naming procedure of the project (described in part B Specificities of the project). All drawing elements must be on a dedicated layer of which the name must equally respect the adopted nomenclature (cf Appendix II Layers). Line types used must be those indicated in the Appendix III Line types". The main UCS (WCS) must be used for every plan view. New drawings must be based on the point zero of the UCS of the corresponding architectural plans. It is sometimes necessary to create a personalised UCS to facilitate the work. Nevertheless, drawings must be saved in the main UCS (WCS) before submittal to avoid base point modifications. The main UCS (WCS) must be used for sections, elevations, details, schedules and diagrams. A4.1.1 DRAWING UNITS Drawing units will be metric with a precision of 4 decimal places. Angular units will be in decimal degrees and have a precision of 4 decimal places. 1 drawing unit is equal to one metre. Dimensions will have a precision of 2 decimal places. If the dimension shown is less than 1 then the dimension will have a zero in front of the decimal point. Or 1 drawing unit is equal to one millimetre. Dimensions will be shown in whole numbers. Page 11/28

12 A4.2 CREATION OF SHEET FILES AND LAYOUT Sheet files are composed of the following elements: - Object space: (i) Model files inserted as Xrefs (External references). (ii) Annotation elements (texts, dimensions, symbols) specific to the sheet file are: either created directly in the sheet file, or inserted as an Xref from a file uniquely containing annotations. - Paper space: The Presentation elements, such as the title block or its attributes, inserted as an Xref or block. Note: All new sheet files can be created from the project template file. A4.2.1 OBJECT SPACE: MODEL FILES AND ANNOTATIONS Every file used as an Xref must be in accordance with the quality requirements quoted herein. For plan views Xrefs should be inserted in mode overlay at the coordinate 0,0,0 in the main UCS (WCS) with neither rotation nor scale modification. All external references must be inserted on a dedicated layer, named X- [name of the Xref]. Page 12/28

13 A4.2.2 PAPER SPACE: PRESENTATION ELEMENTS A presentation is composed of: - One title block containing common elements for all project drawings (frame, texts, logos, images) must be inserted as an Xref in the paper space at the coordinates 0,0,0. THE NAME OR CONTENTS OF THE TITLE BLOCK MUST NOT BE MODIFIED. - The identification blocks containing the text (as attributes) specific to the drawing. THE NAME OR CONTENTS OF THESE BLOCKS MUST NOT BE MODIFIED. - Legends have to be inserted as Xrefs in paper space within the zone reserved for this use. This rule does not apply if: I. The Title block has no reserved zone for the legend (ex: A3 Title block). The legend may be inserted in the paper space drawing area. II. The legend is voluminous. It is necessary then to create a specific sheet file containing all symbols used and to indicate this legend from the sheet file concerned. Example sheet file layout: Model File of legend inserted as an Xréf On layer X-[name of Xref] Model File 1 inserted as an Xref On layer X-[name of Xref] Model File 2 inserted as an Xref On layer X-[name of Xref] Title and scale of view n 1: Block inserted in dedicated layer for symbols ([Discipline]-ANNO-SYMB) Point 0,0,0 of the title block (inserted as an Xref ) Title and scale of view n 2: Block inserted in dedicated layer for symbols ([Discipline]-ANNO-SYMB) Page 13/28

14 Title block zones: «Drawing Identification» block «Revision and participants» block A4.2.3 UTILISATION OF CALLOUS AND TITLE BARS CALLOUT BLOCK: A "callout" is a block that indicates the exact location of a related view in the drawing Two numbers are used to identify the location of the view required: 1 The number of the sheet file 2 The number of the corresponding view within that sheet file 2 : Number of the corresponding view 1 : Number of the sheet file Example: The above callout block appears in the sheet file number AFP0101. It refers to the view N 02 (corresponding with the N noted in the circle of the title bar, see below) of the sheet file AFP9006. Different callout symbols exist for different drawing types: - Details, sections, elevations. Page 14/28

15 Detail Coupe Elevation TITLE BAR BLOCK: The title bar is used to identify the views shown on a sheet drawing. The number in the circle indicates the number of the view and must be unique on the page. Numbering starts at the number one (and never at the number zero). This number is used in callout blocks to clearly identify the view concerned and its scale. Title bars must always be used when a sheet drawing shows several items. 2 : Title of the view 1 : Number of the view This block contains: - The number of the view - The title of the view - The scale of the view. 3 : Scale of the view Note: To avoid redundancy Callout and Title-bar blocks are only inserted in sheet files. Page 15/28

16 A4.3 UTILISATION OF TEXTS Texts and symbols must be created in dedicated layers ([Discipline]-Anno-Text or [Discipline]-Anno-Symb). All text must be in UPPERCASE The text font to be used is specified in section B of this document. Whatever the plot scales of the sheet file, text must have a height of 2.5mm when plotted (therefore the height of text in paper space). For this, text size in object space must be configured according to the plotting scale. The following table establishes the correspondence between text height in object space and plotting scale. Plot Scale (Paper space) Correspondence «Text Height in object space plot scale» Zoom XP In the view Text Height In object space Example for the text height: Object space drawn in metres, plot scale 1:25 Scale to assign in the paper space presentation view: zoom=40xp Text height in object space must be Idem, symbols must have an appropriate size to their plot scale. Example for symbols: Object space drawn in meters, plot scale 1:25 Scale factor of insertion for symbols in object space must be Scale Factor of insertion for Symbols in object space m mm m mm m mm 1 : : : : : : : : : : : : : : : : See the following section (section A4.3.1: the three categories of annotations) to identify which file the text should be created in. Page 16/28

17 A4.3.1 THE THREE CATEGORIES OF ANNOTATIONS Text can be categorised as one of the following three types. After having categorised the text the method described should be used to create and present the text in the CAD file. Freezing layers within the sheet file is not permitted. Note: Where the word text is used this includes annotations, dimensions, and identification symbols. 1. Recurring text at the same scale Example: Text for an Architectural floor plan or text for a Civil site plan (to be used as backgrounds for various other plans) Method: This requires the creation of a separate model file containing only the recurring text. This provides uncluttered ( clean ) Model files for others that may use them as base drawings. MODEL FILE SHEET FILE TXT TXT Type 1 MODEL FILE TXT TXT SHEET FILE TXT TXT 2. Unique text in sheet files where the base drawings will be recurrent at different scales or used by other disciplines Example: Site plan at 1/10000 (Scale used only for one drawing) or Architectural wall finishes plan at 1/200 showing all rooms) Method: The text is created in the sheet file and is not present in the model file (that will then be inserted as an Xref therein). This simplifies the sheet file layout as text is sized and positioned directly in the sheet file and helps avoid redundancy. MODEL FILE SHEET FILE TXT Type 2 TXT Note: If text is theoretically unique but nonetheless shown in several sheet files (for example wall finishes tags where the sheet file zones are overlapping) it may be easier to categorise them as type 1 and create a separate model file. 3. Unique text not used as a base drawing and shown only at one scale Example: Detail or Diagram (Note: Certain elevations or sections may fall into this category) Page 17/28

18 Method: The text that falls into this category (and only the text that falls into this category!) can be created directly in the model file at the correct size for plotting. This is possible because it cannot interfere with other drawings and is not recurrent. Type 3 MODEL FILE TXT TXT SHEET FILE TXT TXT Note: Text from disciplines such as Plumbing, Electrical or Mechanical may fall into this category as the information is rarely repeated and is not used as a base drawing by other disciplines. A4.4 UTILISATION OF DIMENSIONS See above section A4.3 Utilisation of text to identify which file the dimensions should be created in. The Dimension style should be configured so that texts always appears at the same size when printed (2.5 mm), whatever the sheet file scale. The project proto (see Section B2) contains project dimension styles. All dimensions must be on a dedicated layer (cf Appendix II Layers Types). Page 18/28

19 A5 PLOT CONFIGURATION A5.1 THE CTB FILE When plotting in AutoCAD, each colour (object or layer) is mapped to a line thickness or colour by a table of correspondence known as a CTB file. The table below shows this relation for the project and applies to all disciplines. The modification of the CTB file without the prior agreement of ADPi is not permitted. The system colour / line thickness is very simple: 6 principal colours are used corresponding to colours 1 to 8 according to AutoCAD numbering. Line thickness grows from the colour red (01) to Magenta (06).The colour blue (05) is not used. Printed colour Category Thick. Principale Colour Secondary colours Black 1. Very fine Red Black 2. Fine Yellow Black 3. Medium Green Black 4. Thick Cyan Black 5. Thicker Magenta Black 6. Very thick Blue-green Not plotted 7. Not plotted White* Grey S1. Projection (40%) Medium grey Grey S2. Projection (20%) Thick light grey Grey S3. Projection (60%) Medium dark grey Grey S4. Projection (40%) Thin grey Grey S5. Projection (20%) Thin light grey Colour white (07) should not be used for plotted objects The project CTB file(s) apply to all disciplines, whatever the drawing type. This allows identical plot settings for all project drawings thus facilitating batch plotting of all documents with a single configuration. A5.2 SECONDARY COLOURS To make CAD Drawing more legible on the screen, in the case of several layers using the same colour, the secondary colours can be used to replace the original layer colour. The secondary colours are only applicable to layers; objects are expected to have the colour ByLayer with the exception of hatching. A6 INDEXATION AND DRAWING SUBMISSIONS A6.1 OFFICIAL SHEET FILE REVISIONS Sheet file title blocks have a revision letter (alphabetical, starting with 'A') which is incremented at each revision, the date and a comprehensive revision subject must also be stated. Page 19/28

20 Submission dates and descriptions will be communicated. A Revision subject (see section B1.4) is a sentence, as explicit as possible, fixed for all drawings sent on a given date. This description must begin with a verb in the past tense (Examples: Issued, Modified, Updated etc ). Drawings from outside sources must reach ADPi at least 3 days before the official diffusion date (communicated beforehand by ADPi to the sub-contractor) to allow ADPI the time necessary to check and treat the files received. Note: Section A6.1.1 relates only to official and contractual submittals of Sheet files and not Draft diffusions showing work in progress. A6.2 QUALITY CONTROL Before submitting drawings to ADPI: Quality Control and Quality Assurance checks should be carried out by the originator of the drawings. All drawings should respect the project CAD standards and any other requirements imposed by ADPI. For the homogeneity of ADPi projects and in order to avoid errors within project CAD files, all received files undergo a Quality Control Inspection. Following reception of CAD files, the Quality Control Inspection will be systematically performed. The aim of this control is to check conformity of the drawings with project standards. If the CAD files are not in conformity, they may be rejected. A Quality Control Report (QCR) will be transmitted to the originator of the drawings and to the project direction. In the case of systematic non-conformity, the drawing originator may be forced to stop production whilst Quality checks are carried out. The project CAD Controller is responsible for carrying out the Quality Control Inspection of incoming CAD files and producing the QCR. Any questions relating to issues found within the QCR should be addressed directly to the project CAD Controller. Every QCR issued on ADPI projects will be stocked centrally and may be used as criteria for future selection of subconsultants, or used for justification of the nonconformity of a given subconsultant. Note: The remarks made in the QCR concern the CAD conformity of the documents received and not the technical data therein. A6.1.3 WORK IN PROGRESS (WIP) Diffusion of unfinished drawings will be marked Work in Progress or For Information Only and include the date of diffusion. A block for this purpose will be provided as necessary. Where possible, only the file format PDF will be used for submissions of unfinished drawings. Page 20/28

21 A7. DOCUMENTS EXCHANGE A7.1 INCOMING DOCUMENTS Incoming CAD files will be saved and controlled by the Project CAD Controller, a Quality Control Inspection will be performed and a Quality Control Report created. If the files are not conforming to the Drawing Standards, they may be rejected and may not be made available to other users of the drawing database. Incoming documents Schema ADP Us. Ext. Us. Deposit files on «T:/ Transferts ADP» Deposit files on to the file exchange Website Notification with document list Files Recuperated & placed in «Import» by the G.I. Notification with document list Notification Files in conformity with Drawing Standards? Yes No Q.C.R sent to the drawing expeditor Files Deposited in «Public» ADPi Us. Legend ADPi Us. User ADPi ADP Us. User ADP Ext. Us. User External Q.C.R Quality control Report G.I. CAD Controller ADPi Files Displacement NOTE: Files received from ADP will be deleted from T:\Transferts after recuperation Page 21/28

22 A7.2 OUTGOING DOCUMENTS Outgoing documents are systematically saved by the project CAD Controller in a base containing all exchanges. Outgoing Model files must be given a unique name through the use of an index. Outgoing documents Schema ADPi Us. Existings files on «G:/ Public» Légend ADPi Us. User ADPi ADP Us. User ADP Ext. Us. User External Q.C.R Quality control Report G.I. CAD Controller ADPi Files Displacement Notification Files Copied in «Export» By the G.I. Files Recuperated directly from «G:/Public» Files Deposited on to the file exchange Website Files Recuperated Notification with document list ADP Us. Ext. Us. Page 22/28

23 B PROJECT SPECIFICITIES Page 23/28

24 B1. FILE CLASSIFICATION AND NAMING Within large projects many AutoCAD files are generated. Such a large quantity of information needs to be well organised in order to treat and transmit the data rapidly. The naming system for CAD documents described below is based on three main requirements: A unique code for every file A categorisation of the content from more general to more precise information A coding flexible enough to meet all project needs B1.1 MODEL FILE NAMING Every Model file will have a unique name based on the following table: A XX - AXXX - XX - NNN A = Alpha numeric; X = Alpha numeric or numeric; N = Numeric Characters of Identification N Type of information 1 Discipline (see Appendix II). Example C = Civil 2 Drawing type (see Appendix I) 3 Dash ** 4 Entity, building or zone (see WBS S1000-GWBS doc) 5 Dash ** Separator 7 Dash ** 6 Level for a plan view* (B= Basement, GF=Ground floor, L=Upper Level, etc ). Or number for a section, elevation, diagram or detail * Characters Indexation 8 Index (added by ADPI to uniquely identify the drawing before diffusion submitting their drawing). * Codification to be determined at the beginning of the project ** The use of dashes is compulsory when the filename contains an index Example: The model file name AFP A100-L1 is composed of: [A] Architectural [FP] Floor plan [A100] New Terminal Building A100 [L1] Level 1 Page 24/28

25 B1.1.1 MODEL FILE INDEXATION The diffusion of model files is represented by a numerical index in the filename of 3 characters, starting with 001. Only checked Model files will be indexed. Model file indexes are incremented independently of the phase and the revision letter of the Sheet files, ex.: AFP-A100-L1-009 The project CAD Controller is responsible for the indexing of Model files. Files received from sub consultants should not have an index. B1.2 SHEET FILE NAMING Note: Please note that correct sheet file names can be found on the drawing list. N - AXXX - A XX - XXXX A = Alpha numeric; X = Alpha numeric or numeric; N = Numeric N Type of information Identification 1 Phase (see below) Separator 2 Dash ** Identification 3 Entity, building or zone (WBS S1000-GWBS doc)* Separator 4 Dash ** 5 Discipline (see Appendix II). Example C = Civil Identification 6 Drawing type (see Appendix I) 7 Dash ** 8 Identification code * Codification determined at the beginning of the project ** The use of dashes as separators is compulsory Example: The sheet file name 3-A100-AFP is composed of: [3] Phase [ - ] Dash (A100] New Terminal Building A100 [ - ] Dash [A] Architectural [FP] Floor plan [0102] Drawing number 0102 Page 25/28

26 B1.2.1 FILLING OUT THE TITLE BLOCK The Drawing number, title and names of participants are to be filled by the drawing originator in the title block attributes. The Title block of a sheet file indicates the following information: See B Title block contents See B Revision tables entities and tables of participants B REVISION TABLE ENTITIES & TABLE OF PARTICIPANTS Each revision corresponds to a client submittal and is indicated by the incrementation of the revision index (alphabetical, starting with 'A') in the revision table for all modified drawings. The revision is shown in the Title block (see number 17 in part B ) REVISION: B 01/01/07 REISSUED FOLLOWING CLIENTS COMMENTS A 25/12/06 ISSUED FOR PRELIMINARY DESIGN REVIEW REV. DATE DESCRIPTION OF REVISION APPROVED BY Revision Table Page 26/28

27 The names of participants involved in the realisation and verification of drawings are presented in the following manner: TITLE BLOCK CONTENTS Table of participants LEGEND : CONTENTS OF THE TITLE BLOCK : 1 Phase Name 2 Discipline Name 3 Drawing Title, line 1 4 Drawing Title, line 2 See Note below 5 Drawing Title, line 3 6 Drawing Title, line 4 7 ADPI Project Number 8 Drawing number 9 Revision Index 10 Plot Scale: - NTS (Not to Scale) if view has no scale. - AS (As Shown) if multiple views are shown at different scale 11 Revision table Note: The title of the drawing has to be filled in the following manner: 7) Drawing Title, line 1: Entity concerned (building or zone) 8) Drawing Title, line 2: Type of drawing 9) Drawing Title, line 3: More precision 10) Drawing Title, line 4: More precision (if needed) Page 27/28

28 B2. PROTOTYPE The prototype, in accordance with these Standards, contains drawing elements such as text styles, dimension styles, line types and typical variable settings, and is adapted to the project by ADPi. It may be used as a template for the creation of new drawings. This file is available from ADPi on demand, if not provided previously. Name of the Proto file: Proto_ dwg Contents: - Text styles: RomanS for text, annotations and symbols. RomanD for dimensions - Dimension Style: BOG_Standard - Line types - AutoCAD variables pre-configured The files Tsaec.lin and Tsaec.shx must be included in one of the AutoCAD support folders, these files are necessary for the use of non-standard line types. B3. PROJECT CTB FILES There are 2 CTB files for the project, 1 per plotting format: B1.ctb A3.ctb Line thicknesses are thus optimised according to the final plot scale. The respect of layer colours exploited by the CTB files allows us to obtain the same results in B1 or A3, legible at all scales by choosing the correct CTB file for plotting. B4. IDENTIFICATION SYMBOLS An identification symbol library exists and may be provided on demand. This library includes: - Title_bar.dwg: title bar blocks - Callout blocks - Graphical scales B5. DRAWING TEMPLATES Templates exist for the following types of sheet files: - Cover sheet - Drawings list - Legends - Plans - Insert sheets Page 28/28