CAD Drawing Standards

Civil Infrastructure Traffic Engineering Open Space

Engineering Services

Table of Contents
1Introduction................................................................................................................3 2Source Information....................................................................................................5 3Drawing Standards.................................................................................................... !. "t#er Information..................................................................................................15 ATTAC$%E&TS.........................................................................................................1'

Introduction

To ensure that a consistent level of quality is maintained when preparing engineering drawings, Engineering Services Branch (ESB has esta!lished specific "rawing Standards for C#" (Computer$#ided "esign % They are to !e fully complied with for all drawings prepared !y, on !ehalf of or supplied to Engineering Services Branch%

1.1 $istor(
C#" drawing standards are designed to esta!lish a consistent approach to the preparation of all engineering drawings% ESB has operated a C#" system of drawing production since the &'()*s% "uring the mid &'')*s, the +ictorian ,overnment*s introduction of Compulsory Competitive Tendering resulted in Council outsourcing its civil and traffic engineering design function in &''- (together with its associated drawing production , however, the resulting environment did not permit effective control of drawing standards with a consequential lac. of consistency arising for all C#" drawings% Su!sequently, in &''- Council introduced an integrated electronic document management system to ensure documentation that was the su!/ect of the 0u!lic 1ecords #ct was properly identified, recorded and archived% #ll current C#" software development is !ased on the AutoCAD product% #utoC#" files can now !e saved in Council*s document management system ("2 The C#" standards have also !een modified to include changes to the spatial definition of a num!er of asset types, principally pavements% These have !een upgraded from !eing simply line$wor. to polygons in order that they can !etter represent assets in Councils ,IS and #sset management systems% In an effort to provide ongoing assistance to drafters, productivity tools such as chec.ing routines have !een developed for use with AutoCAD using the AutoLISP programming language% C#" Standard documentation can !e downloaded from City of 2el!ourne corporate we!site including3 a standard set of C#" !loc.s standard drawings for specific asset types 1equired attri!ute data Survey limits standards and 0ar.ing 0lans "esign and "rafting guidelines for "esign, Construction and 4#s Built5 drawings 6IS0 chec.ing routines

1.2 Sco)e
These C#" guidelines set out drawing standards for 4"esign5, 4Construction5 and 4#s Built5 drawings for all C#" files supplied to ESB% "rawing requirements will vary depending on its source% eg internal service provider or an e7ternal organisation% This document sets out the requirements for the provision of C#" drawings to Council% These vary according to the type of drawing eg "esign, Construction or #s Built% 8or 9#s Built5 drawings, C#" files must conform to all required elements of Co2*s C#" standards%

Source Information

2.1 *ol(gonisation
To facilitate the supply of !ase information for asset management, polygonisation and attri!ution of all surface !ased assets was completed in :)&& using :))( aerial images, e7isting C#" drawings and ground survey% The compiled polygons are now updated regularly and stored in #rcCatalog% Council customers may request data from the current !ase map as need arises% In addition, a suite of Parking Plans has !een compiled showing the layout of par.ing spaces throughout the City% #lthough many of these plans are in electronic format a large num!er remain as hardcopy%

2.2 +eogra)#ic Information S(stem ,+ISIt is Council*s intention, that all relevant physical infrastructure assets are represented in its ,eographic Information System (,IS % #ccordingly, Council*s ,IS system, needs to capture spatial and attri!ute information a!out recently created;acquired;modified assets% To facilitate this process, all engineering wor.s underta.en !y third parties that result in a 4changed5 asset must !e accompanied !y an 4#s Built5 C#" drawing% This drawing must conform with Council*s C#" drawing standards such that it can !e easily uploaded to Co2*s spatial and #sset 2anagement systems%

Drawing Standards

3.1 Drafting +uidelines

,uidelines for the preparation of engineering drawings have !een compiled for use !y Engineering Services, service providers and organisations providing C#" data in 9Engineering Services Branch "esign and "rafting ,uidelines documents* Attac#ment 1% These C#" "rawing Standards supplement those guidelines% 2odifications to engineering drawing protocols including the control and maintenance of 4master5 documents, !loc.s, layer structures and AutoLISP routines must !e approved !y the 0rincipal Engineer, Infrastructure, Engineering Services Branch% # template C#" file and associated 6IS0 routine can !e found on the City of 2el!ourne we!site under Engineering Standards and #pprovals% http3;;www%mel!ourne%vic%gov%au;0ar.ingTransportand1oads;1oads;EngineeringStandards;0ages;E ngineeringStandards%asp7

3.2 .a(ering
Council has esta!lished a layering protocol for the preparation of all C#" engineering drawings% The layering protocol provides settings for appro7imately <=< layers in the following :< classifications% 1efer to Attac#ment 2 / C#" 6#>E1S 8O1 CO?@CI6 I@81#ST1?CT?1E%

Table 1: Top Level of CAD layering classification

&o C.ASSI0ICATI"& & : < C E = ( B1I",ES B?I6"I@,S "1#I@S "1#DI@, E6ECT1IC#6 ,#S 6I,FTI@, 2#1I@E &o C.ASSI0ICATI"& ' 2CCA2ISC &) O?T"OO1 8?1@IT?1E && 0#1BI@, CO@T1O6S &: 1#I6D#>S &< 1E6IE8 &C 1O#"S &E SEDE1 &= SI,@ &o C.ASSI0ICATI"& &- S?18#CES &( S?1+E> &' TE6ECO22?@IC#TIO@S :) T1#88IC CO@T1O6S :& T1#2D#>S :: +E,ET#TIO@ :< D#TE1

8or completeness, an additional BOUNDARIES layer classification can !e sourced from Council*s property maps% The Council*s 0roperty Services (in City 0lanning G Infrastructure maintains the !oundary data H request for current property data for su!/ect area from the manager concerned% 6ayers for !oth e7isting and proposed assets may !e created for each asset;drawing classification% To facilitate proper usage of the ES, layers, a %CC.a(ers AutoLISP routine has !een developed and can !e setup using instructions contained in the file3

901OCESS 8O1 6O#"I@, 6IS0 1O?TI@ES I@TO #?TOC#"3 2CC 6#>E1S SCFE2E* H 1efer Attac#ment 3. 8or the macro contact the 0rincipal Engineer City of 2el!ourne%

3.3 .a(er %anagement

The following points set out the requirements for layer management% "rawings are not to contain empty layers or invalid, unused or unassigned o!/ects% The AutoCAD 0?1,E command (or similar should !e used to remove such references once the drawing is finalised% To prevent potential amendments to Council*s design;construction drawings, e7ternally referenced documents (ie% I$1E8 commands or em!edded lin.s to other drawings are not to be included in drawings that are prepared for civil infrastructure or traffic engineering purposes% #ny layers created !y software that is e7pressly used to capture survey data or to prepare or compute engineering designs must !e renamed in accordance with Council*s layer scheme% #s$!uilt drawings are not to include any 4proposed5 layers%

Drawings containing non/standard la(er names will be re1ected and will re2uire resubmission in t#e correct format. @on$standard layer (1efer Section <%:) names will !e identified !y the 2CCChec.s 6IS0 routine%

3.! *ro1ect 3oundaries

The !oundary defining the scope of wor. that is the su!/ect of the drawing is to !e delineated on the "1,$I$01OJAB"> layer% (8or information concerning the requirements for pro/ect !oundaries, refer Attac#ment ' $ S?1+E> 6I2ITS #@" #CC?1#C> ST#@"#1"S 8O1 EIISTI@, CO@"ITIO@ "1#DI@,S @B3 The "1,$I$01OJAB"> layer can !e turned O88 on all drawings su!mitted to Council%

3.5 Standard S(mbols

Design Drawings 4 Civil 5 Traffic Engineering # suite of sym!ols has !een developed for Civil Engineering and Traffic Engineering designs% They are contained in the files3 E@,I@EE1I@, SE1+ICES #?TOC#" B6OCB S>2BO6S3 CI+I6 E@,I@EE1I@, ,Attac#ment !and E@,I@EE1I@, SE1+ICES #?TOC#" B6OCB S>2BO6S3 T1#88IC E@,I@EE1I@, ,Attac#ment 58or a "D, format contact the 0rincipal Engineer City of 2el!ourne% Only these standard sym!ols are to !e used for preparation of engineering designs and as$!uilt drawings% 0eature Surve( Drawings 4 Including 6As 3uilt7 8eature surveys shall use 9E@,I@EE1I@, SE1+ICES #CCE0T#B6E B6OCBS 8O1 CI+I6 #S B?I6T "1#DI@,S* ,Attac#ment -, which include linetypes and surfaces%

3.

Titlebloc8s
final drawings for presentation or construction purposes, standard drawings and reference material e7isting conditions drawings and 4#s$Built5 drawings

Title!loc.s shall !e used in the following circumstances3

Third 0arty organisations preparing engineering design plans are to do so using their own Title!loc.s and corporate logos% Common Requirements In all cases, drawing Title!loc.s must contain the following information (as a minimum and may need to !e prepared specifically for the pro/ect at hand%

Com)onent #mendment panel #pproval date #pprover name

Details 1efer Section <%&: The date the dra ing 1efer Section <%&C as signed approved

#uthorisation details C#" file name Chec. date Chec.er name CouncilKs "2L Cross$reference to Concept 0lan "esigner name "rawing num!er "rawing scale "rawing siMe "rawing status "rawing Title ,raduated !ar 2ap reference @orth 0oint

Any re!uisite authorisation by Co" The dra ing file na#e $ here relevant% The date the dra ing as checked

The na#e of the person checking the dra ing 1efer Section C%& 1efer Section <%&& The na#e of the person responsible for design 1efer Section <%&& The scale ratio used to prepare the dra ing 1efer Section <%= 1efer Section <%&= 1efer Section <%&& &or #icrofil#ing or scaling purposes $in ##'% Derived fro# "(A coordinates &or locating direction of True )orth

@otation a!out horiMontal;vertical 1efer Section <%-, <%(, C%: datums (ie% 2,#, #F" and reference to origin @um!er of sheets 1evision num!er Survey reference num!er 1efer Section <%' 1efer Section <%&: The survey file*dra ing no' $ here relevant%

Title!loc.s and associated te7t must !e placed on the relevant Council "rawing layer% (ie% "1,$I$TIT6EB6OCB or "1,$I$TEIT

3.' $ori9ontal Coordinates and Drawing :nits

"rawings may !e compiled using layout (paper space !ut if plan information !ased on 2ap ,rid #ustralia (2,# coordinates is included, the model space shall not !e rotated, shifted or otherwise transformed% The datum must !e in 2,#$EE, ,"#'C coordinates% #ll "rawings are to quote the coordinate origin as 2,#$EE, ,"#'C% "rawings are to !e prepared in metres with &3& drawing units%

3.; .evels
Design Drawings 8or design drawings, level information relevant to the design is to !e placed on the "1,$I$CO@ST1?CTIO@ @OTES layer% This includes not only levels related to cross$sections and longitudinal sections !ut also any levels that need to !e shown in plan view% N$a7is coordinates are not required for design drawings% E<isting Condition *lans or As/3uilt Drawings

E7isting condition plans shall show N$a7is coordinates for all features% #s$!uilt drawings shall show N$a7is coordinates of any 4new5 wor. and, if necessary, may show N$a7is coordinates for all features% The height datum for all levels noted in design drawings shall !e !ased on #ustralian Feight "atum(#F" The inclusion of te7t to descri!e spot heights is only necessary where clarification of terrain levels is required (ie% 1E6$I$S0OTAFT or to descri!e a representative height value for floor levels, roof levels or water levels (ie% B6"$I$86OO1A6E+E6, B6"$I$1OO8A6E+E6, "1$I$ D#TE1A6E+E6 %

Surve( %ar8s Coordinate values for all survey mar.s shall include a N$a7is coordinate% Ouoted level values for survey mar.s are also to !e noted in the S+>$I$TEIT layer%

3.= %ulti)le Drawing S#eets

#ll drawings of the same class shall !e compiled in a separate, single file% i%e% all Civil 2echanical Electrical 6andscape

"rawings shall !e compiled in a single file !ased on the class of drawing%

3.1> &aming Conventions

Drawing T()es Codes for "rawing Types are shown !old in the ta!le !elow and are to !e used as a prefi7 in the drawing num!er The codes are derived from the type of drawing%

E 0 : +

E7isting Conditions survey 8ield Survey ?tilities ,IS E7tract

C D S ?

Concept "esign "etailed "esign Standard "rawing 1eference "rawing

@or8s Drawings #ll Dor.s "rawings are to !e identified !y a com!ination ofP a prefi7 derived from the type of drawing, The organisation*s 4/o! identification5 num!er a suffi7 identifying the num!er of the drawing sheet

Standard Drawings and ?eference Drawings #ll Standard "rawings and 1eference "rawings are to !e identified !y the file num!er for the relevant 4"esign G Construction Standards5 in City of 2el!ourne De!site, Engineering Standards, specifications and approvals%

3.11 Drawing Title

The drawing title (drawing name is to comprise < levels of detail3 Other Suppliers of Drawings 1 # PRO EC! NA"E $OCA!ION &OR'S O% $ $ Pro+ect )a#e Property address including na#e of street, street nu#ber and suburb'

!I!$E O% DRA&IN)

Description of the nature of the orks' -g $ $ $ $ $ De#olition Plan. Construction Plan. Setout Plan. Landscape Plan. etc

3.12 Amendment *anel 5 Aersion Control

.a(out of Amendment *anel Other Suppliers of Drawings
/ersion )u#ber to be consecutive starting at 1 Description of a#end#ent $If /ersion 1 in organisations syste#, then Description to be 01riginal2 ID of drafter #aking a#end#ents Date of a#end#ent

RE*ISION

DESCRIP!ION

B+

DA!E

Drawings are to !e versioned using a numerical identifier (ie% &, :, etc%% with the first version always !eing named 4Original5 in the amendment panel% "rawings shall !e saved into a system capa!le of retrieving them efficiently and effectively% As 3uilt drawings are to !e shown with all previous entries in the #mendment 0anel removed% 1evision num!ers are to !e su!stituted with a hyphen and the "escription field is to show 4#s$Built5%

Dhere drawings are created and supplied to Council outside of the "2 environment, the data file is to !e named according to the su!division permit num!er (where relevant or else the drawing I" num!er contained in the organisations drawing management system and versioned as follows3 8irst version Su!sequent versions 6ast or final version # B, C, " etc%% N

3.13 Te<t 0ontsBSt(les

#ll drawings are to use the ISO$C0 font supplied with AutoCAD' Customising of fonts or standard shape files (%SFI is not allowed% @o other font types or te7t styles (other than a logo are to !e used in the drawing% Only shape files (%SFI forming part of the standard AutoCAD suite are to !e used%

3.1! Drawing Aut#orisation

Dhere evidence of approval is required, the name of the person responsi!le for that approval is to !e inserted in the relevant field in the Title!loc.% This can include an electronic signature if desired% Initials are not to !e used for this purpose%

3.15 3loc8s and .inet()es

Only !loc.s and linetypes authorised for use !y ESB are to !e used in a drawing% If a new !loc. or linetype is required, permission to create and use the !loc. or linetype must !e o!tained from the 0rincipal Engineer, Infrastructure, Engineering Services Branch !efore !eing referred to the Team 6eader, #sset 2anagement to action% The standard suite of civil engineering and traffic engineering !loc.s is held in City of 2el!ourne De!site, Engineering Standards, specifications and approvals ,Co% @ebsite-% The 42CC$Services%lin5 file is the source of 4special5 linetypes for all ES, drawings (01OCESS 8O1 6O#"I@, 6IS0 1O?TI@ES I@TO #?TOC#"3 2CC 6#>E1S SCFE2E $ ?efer Attac#ment 3#ll other linetypes are to comply with the standard linetypes contained in the 4acadiso%lin5 file provided with AutoCAD% Dherever possi!le, !loc.s are to remain on their designated layer and are not to !e e7ploded% If a !loc. is e7ploded, the !loc.*s o!/ects are assigned to 6ayer ) and must then !e recreated on the correct layer%

As/3uilt Drawings Bloc.s used in as$!uilt drawings are to !e selected from the standard suite of civil engineering and traffic engineering !loc.s ,?efer Attac#ments Dhere the dimensions of an asset e7ceed )%<= sq meters (=)) I =))mm , the as$!uilt !loc. must properly represent the dimensions of the asset !eing depicted% Scalea!le !loc.s may !e used for this purpose% @evertheless, due to the comple7ity of asset shapes, some asymmetrical !loc.s will need to !e included in an as$!uilt drawing if only to improve legi!ility and clarity%

#symmetric !loc.s such as those used to represent lighting (SE60, SE60&, SE60&T , logos mar.ing !i.e paths or disa!led par.ing (BIBE, "IS#B6E , lane arrows (#11OD&, #11OD:, #11OD< , !uoy or channel mar.ers (B?O>, CF#@@E6$2#1BE1 are all allowa!le !loc.s%

3.1 Drawing Status

The status of the drawing is to !e identifia!le at all stages of the drawing*s development% In "2, the 4Status5 field in the document profile must also !e maintained to properly reflect the drawing status% #ccepted definitions of drawing status are3 "raft 8inal Signed Issued for Tender Issued for Construction #s$Built

3.1' 0ile 0ormats

#ll C#" drawings depicting civil infrastructure or traffic engineering that are prepared in accordance with this document must !e filed in Council*s document management system as an AutoCAD#,,format document or earlier version%

3.1; *lotting and *en Tables

0en ta!les may !e customised to suit specific plotting requirements !ut they s#all not alter pen settings esta!lished for each layer !y the %CC .a(ers 6IS0 routine%

3.1= Data "wners#i) and Co)(rig#t

Dhere a Third 0arty supplies Council with an 4#s Built5 drawing, Council is to !e ac.nowledged on the drawing as the owner of the relevant data and documentation% "isclaimers used !y Third 0arties shall not negate Council*s rights to ownership of the drawing or the data contained in the drawing%

3.2> C#ec8ing
The 6IS0 routines C%CCC#ec8sD and C%CC0i<D shall !e used to confirm that layering requirements complies with ESB*s drawing layer protocols and that all !loc.s used in the drawing are properly assigned to the correct layer% 6IS0 routines are availa!le for use !y providers of spatial data % "ata providers shall utilise the 6IS0 chec.ing routines prior to su!mitting final drawings% 1efer to Attac#ment 3 for a copy of the 6IS0 routine and e7planatory notes

!.

"t#er Information

!.1 Surve( .imits and Accurac(

"ata contained within drawings must comply with the standards for data capture descri!ed in 4S?1+E> 6I2ITS #@" #CC?1#C> ST#@"#1"S 8O1 EIISTI@, CO@"ITIO@ "1#DI@,S 0repared By Engineering Services5 ,?efer Attac#ment '-% Coordinates are to !e referenced to 2ap ,rid #ustralia(2,#$EE using ,"#'C and #ustralian Feight "atum (#F" for heights% .ocal or arbitrar( coordinates are not )ermitted in as/built engineering drawings %

!.2 Data E<c#ange

Other Suppliers of Drawings The format in which drawings are supplied to Council will vary according to the drawing status% Dra ing Status Type "raft 8inal Signed Issued for Tender Issued for Construction #s$Built &or#at 3e!uire#ent 0"8 H 2andatory, "D, $ Optional 0"8 H 2andatory, "D, $ Optional 0"8 H 2andatory, "D, $ Optional 0"8 H 2andatory, "D, H Optional 0"8 G "D, $ 2andatory 0"8 G "D, H 2andatory

Fardcopy drawings must !e supplied if requested !y Council%

!.3 Attribute Data

Su!mission of 9#s Built* plans must include detailed asset register which categorises assets !y the C#" standards layer name% 8or $ $ $ 0oint assets (eg outdoor furniture the num!er of assets of each layer class must !e recorded% 6ine assets eg drains and all attri!utes associated must !e recorded along with the o!/ect I" 0olygon assets eg road carriageways and all attri!utes associated must !e recorded along with the o!/ect I"

The asset register must !e supplied in the form of an e7cel spreadsheet%

?eference Documents
#ll design drawings are to !e prepared with reference to3 Council*s Construction Specification 1elevant Technical @otes, and Standard "rawings for relevant assets%

0or instructions on t#e w#ereabouts of t#is information c#ec8 Co% website http3;;www%mel!ourne%vic%gov%au;0ar.ingTransportand1oads;1oads;EngineeringStandards;0ages;E ngineeringStandards%asp7

!.! %anaging Trees 4 As/3uilt Drawings

Street Trees Trees within the road reservation are to !e represented !y the T1?@B !loc. on the +@$I$T1EE layer with the outline of the canopy shown on the +@$I$T1EEAC#@O0> layer 8or street trees, the canopy can !e shown either circular (if prepared using ground survey methods or QtrueQ (if prepared using aerial photogrammetry methods *ar8 Trees Dithin par. areas, trees with canopies less than : metres in diameter are to !e represented !y the T1?@B !loc. on the +@$I$T1EE layer with the letter QTQ placed near!y on the +@$I$TEIT layer Trees within par. areas having canopies greater than : metres in diameter are to !e represented !y the T1?@B !loc. on the +@$I$T1EE layer with the outline of the canopy shown on the +@$I$ T1EEAC#@O0> layer

!.5 Surface
Surfaces within council spaces i%e% road reserve, par.s, council owned !uildings and other pu!lic spaces will !e denoted !y the polygons surfaces in 9#ccepta!le Bloc.s 8or As 4uilt Civil "rawings* ,Attac#ment -.

ATTAC$%E&TS
#ttachment &3 Engineering Services Branch "esign and "rafting ,uidelines #ttachment :3 C#" 6ayers for Council Infrastructure #ttachment <3 0rocess for 6oading 6isp 1outines into #utoC#" #ttachment C3 Engineering Services #utoC#" Bloc. Sym!ols3 Civil Engineering #ttachment E3 Engineering Services #utoC#" Bloc. Sym!ols Traffic Engineering #ttachment =3 Engineering Services #ccepta!le Bloc.s for 9#s Built* Civil "rawings #ttachment -3 Survey 6imits and #ccuracy Standards for E7isting Condition "rawings

#ttachment (3 #sset 1egister for C#" 6ayering Standard for E7ternal Organisation