AEC (UK) BIM protocol for Revit by Revit MEP Design

AE EC (UK K) B BIM Protoco ol fo or Au utod desk k Re evit Addiitional dettail and enhancem e ments for impleme entation o of the AEC C (UK) BIM Protocol for Autod desk Revvit users. Versio on 2.0

Septemberr 2012

Re-publish hed as a suupplementary documentt to the geneeric AEC (U UK) BIM Protocol

AEC (UK K) BIM Protoco ol for Autodesk k Revit

AE EC (U UK) BIM B P Prottocoll for Au utode esk Revit R t Conttents 1

Intrroduction

1.1

d Background

1.2

The Committtee

1.3

Disclaimer

1.4

Scope

1.5

Update Proccedure

1.6

References

1.7

Definitions

Besst Practice

2.1

BIM

2.2

oduction Drawing Pro

Pro oject BIM Execcution Plan

3.1

Roles and Responsibilities R s

3.2

Project BIM M Execution Pla an

3.3

Project BIM M Meetings

Collaborative BIM M Working

4.1

Common Da ata Environme ent (CDE)

4.2

Preparation n for publicatio on

4.3

Legal Stuff

4.4

Data Security & Saving

4.5

B Data Reviewing BIM

Inteeroperability

5.1

n Introduction

5.2

Incoming CA AD/BIM Data Managementt

5.3

Intended Usse of Model

5.4

Data Transffer between Packages

Datta Segregation n

6.1

General Prin nciples

6.2

Division

6.3

g Referencing

Mo odelling Methodology

14 4

7.1

Model Deveelopment Metthodology

7.2

Graded Com mponent Creation

7.3

Drawing Co ompilation

7.4

Spatial Loca ation & Co-ord dination

7.5

Units and Measurement M

Fold der Structure and Naming Conventions

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

16 6 Pa age 2 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

8.1

Introduction n

8.2

Project Fold der Structure

8.3

General Nam ming Conventtions

8.4

Model File Naming N

8.5

Division Nam ming

8.6

Library Objeect Naming

8.7

Object Prop perty Naming

8.8

View Namin ng

8.9

View List Sccheduling

8.10

Data Organ nisation

8.11

Sheet Namiing

Preesentation Styyles

21 1

9.1

Introduction n

9.2

AEC (UK) Co ompliant Mate erials

9.3

Annotation

9.4

ment Text Assignm

9.5

Line Weightts

9.6

Line Pattern ns

9.7

Line Styles

9.8

nd Filled Regio ons Hatching an

9.9

View Templlates

9.10

Dimensionin ng

9.11

Drawing Bo orders and Titlle Blocks

9.12

Symbology

9.13

Ressources

26 6

10.1

n Introduction

10.2

Software

10.3

nt / Resource Libraries L BIM Conten

10.4

Keynotes

10.5

Custom mettadata

10.6

Keyboard Sh hortcuts

App pendices

27 7

11.1

N Codess Model File Naming

11.2

Project Fold der Structure

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 3 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

1 In ntrodu uction n 1.1 B Backgrou und The AEC (UK) BIM Standard S wa as released in Novemb ber 2009. Version 2.0 of the AE EC (UK) BIM M Protocol was w publish hed in Septeember 2012 2 to improve th he process of design in nformation production, managemeent and exc change. This re-pu ublished sup pplement prrovides spe ecific applica ation of thosse protocols for Revit Arch hitecture, Revit R Structu ure and Rev vit MEP. Copyrightt Notice: It is imporrtant to note e that this sttandard will only becom me truly useeful if as ma any companie es adopt it as a possible. To that exttent, it may be freely diistributed an nd used in any form mat necess sary, provide ed credit is given to the e committeee.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 4 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

1.2 T The Com mmittee The Bentley sub-com mmittee hass representa atives from architectura a al, engineerring and construction compan nies in the U UK, large an nd small, he ence the adooption of the AEC (UK) moniker. The BIM committe ee is workin ng together to realise a unified, us sable, co-ordinatted approac ch to Buildin ng Information Modellin ng in a desiign environm ment. Committe ee Paul Wodd dy (Chair)

White Fro og Publishing g

paul@whitef p frog.co

Lewis Wen nman

Pascall+W Watson Archiitects

lewis.wenmaan@pascalls s.co.uk

Ray Purviss

Atkins Glo obal

ray.purvis@a r atkinsglobal.com

David Light

HOK

david.light@ d @hok.com

Nigel Davie es

Evolve Co onsultancy

e-consultanc nigel@evolve n cy.com

Contributtors Andrew Co oombes

Hampshirre County Co ouncil

Chris Hobb bs

CADline

Chris Senio or

Revit Facttory

Chris Tate

BDP

Gavin Skid dmore

Mott MacD Donald

James Ausstin

BIM Tech nologies

Joe Stott

Aedas Arcchitects

Michael Ba artyzel

Buro Hap pold

Mike Farmer

Haskoll

nt Scott Gran

Soluis

Steve Wrig ght

Ramboll U UK

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 5 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

1.3 D Disclaimer All the advvice outlined in this do cument is fo or information only. Thhe authors and a contributin ng companiies take no responsibility for the utilisation of these procedures and guide elines. Theirr suitability sshould be considered c carefully c beefore embarrking upon any integration into your cu urrent work king practice es. None of th he recomme endations in n this docum ment are inttended as a replaceme ent for companie es who alrea ady have an n AEC (UK))-based or BS1192-com B mpliant systtem.

1.4 S Scope This supp plement is intended tto support all BIM wo ork undertaaken using Autodesk k Revit acro oss a practtice, or on a specific project, un nless otherrwise dictated by b the clien nt. The AEC (UK) BIM Protocol P for Autodesk Revit R builds on the proccedures and d methodolo ogies define ed in the AE EC (UK) BIM M Protocol and a should be read in conjunctio on with that document. Terminolo ogy and refe erence to fu unctionality is based around the Auutodesk Re evit platform.

1.5 U Update Procedu P ure Proposed changes and addition s to this sta andard shou uld be subm mitted in writting with accom mpanying examples, e d discussion, or o other sup pportive maaterial to the e Bentley su ub-committe ee. Feedba ack will be gathered g and continuouusly reviewe ed; they will be colllated to form m new revissions at app propriate inttervals. It is expeccted that this standard will undergo a relatively rapid evoolution process, as the industtry adapts to o the impliccations and advantages s of BIM meethodology.

1.6 R Referencces This stand dard is writtten with refe erence to th he following documentss: • BS1192:2007 2 • PAS1192-2:2012 011 • BS8541-1 and BS8541-2:20 ( BIM Protocol v2.0 0 • AEC (UK) • AEC (UK) ( CAD Standard S fo r Layer Nam ming v3

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 6 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

1.7 D Definition ns

2B Best Practic P ce 2.1 B BIM • The Central C file shall s never b be opened, only copied to create local files. • The Central C file should s be re ecreated at regular inte ervals in ordder to elimin nate redun ndant data retention. r

2.2 D Drawing Producttion

3P Projecct BIM M Execcution n Plan n 3.1 R Roles an nd Responsibilit ies 3.2 P Project BIM B Execution P Plan 3.3 P Project BIM B Mee etings

4C Collaborativ ve BIM M Wo orking 4.1 C Common n Data Environm E ment (CD DE) 4.1.1 Work In Progress (W WIP) 4.1.2 Shared 4.1.3 Publication n and Document Issu ue 4.1.4 Archiving

4.2 P Preparattion for publicati p ion Sheets fro om the BIM M shall be published to DWF (p preferred), P PDF or oth her noneditable format, f whe ere they ca an be chec cked, appro oved, issuedd and arch hived as traditionall documents s. Key Points 

Arre Sheets an nd Views to o be include ed?

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 7 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

Notes 

al is very im mportant, if the recipien nt of the Detaching the model file ffrom Centra del works on o the sam me network as the issu uer, and if the model has not mod bee en detach, the t model w will be treatted as a loc cal copy annd the recip pient will be able a to upda ate the issu uer’s model..



If co ontractually pressured to deliver a model con ntaining sheeets then the e sheet bord ders should d be swappe ed for a tran nsmittal borrder.



If Design options and pha sing are contained with hin the moddel a detaile ed exp planation of these is req quired.



Upd date the “Prroject Issue Date” and “Project Sta atus” Param meters to record verssion issue.

4.3 L Legal Stu uff 4.4 D Data Seccurity & Saving • Maxim mum numbe er of Revit b back-ups sh hall be set to o 3. • Revit LOCAL file es shall be ssaved back to CENTRA AL hourly. nder intervall shall be se et to 30mins s. • Revit save remin s view w within all m model files is i to be set to a non-scchedulable Sheet S • The starting View. The startin ng view title block has been includ ded in the aassociated templates. These e shall be re etained and d the file info ormation coompleted for each mode el issue. • Userss shall open n the Splash h Page view w and close all others w when saving g in order to improve the efficien ncy of file op pening. It is recommennded to utilis se the Revit 2012 feature to force tthis.

4.5 R Reviewin ng BIM Data D Outstanding issues shall s be disccussed at th he project co-ordinationn meetings.. This process may m be aide ed by using Navisworks s on larger projects p to kkeep the 3D D informatio on managea able.

5 In nterop perab bility 5.1 In ntroducttion 5.2 In ncoming g CAD/B BIM Data a Manag gement

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 8 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

5.3 In ntended d Use of Model 5.4 D Data Tra ansfer be etween Package es

6D Data Segre S gation n 6.1 G General Principles A numberr of methods s exist whicch enable co ollaborative e working in a BIM environme ent, includin ng working practices and team ma anagement as well as the technolog gical solution ns covered by the remit of this doc cument. This section deals wiith the princciples of sub bdividing a model for thhe purposes s of: • multi-user access s, • opera ational efficie ency on larg ge projects, • inter-d disciplinary collaboratio on. The terminology refers primarilyy to the Revit subjects of o Worksets ts and Linking (sections Error! Refe erence sou urce not fou und. & Erro or! Referen nce source not found.), both b of whic ch are referrred to herein as model sub-divisioon. The follo owing practices shall be folllowed: m ado opted for da ata segrega ation shall ta ake into acccount, and be b • The methods agree ed by, all internal and e external disc ciplines to be b involved in the mode elling. • In line e with the model m develo opment metthodology described d inn section 7, models shall initially i be created c as issolated, sin ngle-user file es. The moddel will be subs divide ed as it beco omes largerr or addition nal memberrs of the dessign team are a introduced. • No mo ore than on ne building sshall be modelled in a single file. • A mod del file shall contain da ata from one e discipline / project staakeholder only(a although exceptions ma ay apply forr Building Services S wheere multiple e discip plines conve erge). • Furthe er segregattion of the g geometry may be required to ensuure that mod del files remain workable on availablle hardware e. (As a bas sic guide, onn a machine e built to the e Autodesk recommend r ded hardwa are specifica ation, files eexceeding 100MB shall be b reviewed d with respe ect to perforrmance and d possible fuurther sub-d division. Ideallyy files shall not exceed d 200MB; fo or projects containing c m more than 1200 sheets within a single s projecct, the perfo ormance of the ‘synchro ronize with central’ c will drramatically decrease). d • In ord der to avoid duplication n or co-ordin nation errors s, clear defiinition of the e data ownership throug ghout the liffe of the pro oject shall be defined aand docume ented. AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pa age 9 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

ent ownersh hip may tran nsfer during g the projec ct time-line – this shall be Eleme expliccitly identifie ed in the Pro oject BIM Execution E Plan. • Where e multiple models m makke up a sing gle project, a container model should be consid dered, whos se function is to link the various assemblies ttogether forr coordination/clas sh detection n purposes.

6.2

Division Worksets allow multiple users to o simultaneo ously work on a modell file through h use of a CENTR RAL file and synchronissed LOCAL copies. Pro operly utiliseed, worksetts can significanttly improve efficiency a and effective eness on la arge and muulti-user pro ojects. • Appro opriate work ksets shall b be establish hed and elements assiggned, either individ dually or by y category, llocation, tas sk allocation n, etc. • To improve hardw ware perforrmance only y the required worksetss shall be opened. o Revit ensures tha at elementss contained in closed worksets w aree still update ed if chang ges made in n open Worrksets impac ct them during model rregeneration. • Once worksets are a enabled , filenames shall be suffixed with eeither –CEN NTRAL or –LO OCAL as defined in se ection 8.4. • Due to o potential data d degrad dation, the local l file should be creeated each time t you close down the lo ocal file. It iss considere ed bad practice to returrn to an old local file. • A LOC CAL copy of o the modell shall be crreated by COPYING thhe original onto o a local hard-drive h via v Window ws Explorer – not by allowing Revvit to autom mate the process. See section 8 .2.1 for loca al folder stru ucture.

Warning! At no po oint after cre eation shou uld the CENTRAL file be b opened oor edited dirrectly. All required operations can be e, and thereffore shall be e, performeed via the LO OCAL files.

From release 2010 onwards, o au utomated fea atures allow w the user too generate a local file with a reduced lik kelihood of a accidental opening o of the t CENTR RAL file. The ese new tools are to t be encou uraged, alth ough the ab bove points s still apply. • Worksset allocatio on shall be ccarried out in a logical manner thaat allows for other memb bers of the design d team m to collabo orate and/orr assist withh the model develo opment with hout recourrse to comp plicated intro oductions too the projec ct metho odology.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 10 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• A projject shall be e broken intto a sufficient number of o Worksetss to avoid conge estion in wo orkflow. Thiss also provides the means for adeequate control over the effficiency of the t model. • The model m shall be split into o worksets, such as described in thhe above ta able. • The borrowing b pe ermissions and workse et ownership shall be m managed. Worksets shall be na amed follow wing the conventions de efined in secction 8.5. am memberrs shall ‘Savve to Centra al’ hourly. • All tea • The Project P Coorrdinator sha all allocate a pre-define ed, unique sslot for each h team memb ber to ‘Save e to Central’’. This avoid ds machines hanging w whilst severral users try to save simultaneo ously. Work-sharin ng Monitor” tool could be used to coordinate ‘Save to Ce entral’ • The “W comm mands acros ss the team m. • Userss shall not le eave the sa ave to centra al process unattended, u , and shall resolve r any isssues which h arise to avvoid delays to other tea am memberrs.

6.3

Refere encing Two meth hods exist fo or setting pe ermissions which enab ble multi-useer access to oa model file through us se of workse ets: Two meth hods exist when w using w worksets to o enable mu ulti-user acccess to a mo odel file: ‘borrowing g elements’ and ‘ownin ng worksets s’. Typically,, ‘borrowin ng’ shall be used. However, ‘ownership’ shall be u used when:: • Restricting acces ss of a partiicular aspec ct of the building to a ssingle user, • A use er needs to operate o aw way from the e network an nd still be aable to work, althou ugh caution is required d to ensure that t only ‘ow wned’ workssets are edited, • Workiing collaborratively overr a slow or remote netw work. In practicce, these methodologie m es take the following fo orm: Element Borrowing B • Userss work as th hough in iso olation on a single-userr file. • Permission to mo odify an ele ement is sou ught and eitther given oor denied by y a live link to o the Centra al file. • All pe ermissions collated c in th his manner are relinquished durin g the ‘Save e to Centrral’ process.. Workset Ownership p

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 11 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• A use er takes own nership of a an entire wo orkset. • The LOCAL L file does d not ne eed to query y the CENTRAL file forr permission n to modiffy any eleme ent allocate ed to that wo orkset.

e OWNERS SHIP of Take an n entire worrkset

BORROW W elements s ffrom workset as requirred

Users only need n to NB/ U open required worksets

6.3.1 Inter-Disciplinary Mo odel Refere encing When wo orking within a Multi-d discipline environmen e t / large ccomplex pro ojects it advised to o break dow wn the mode el into a number of sub b-models, thhe extents of o which are to be agreed witth the proje ect team an nd documen nted within the BIM Ex xecution Plan. A Model Ma atrix see the suppo orting docu ument AEC C(UK)BIMP ProtocolModelMattrix-v2.0 will w be req quired to explain e an nd communnicate the linking methodolo ogy with a key k diagram m to assist. Linking model m files enables e add ditional geo ometry and data to bee referenced into a model. Th his may be either otherr parts of a project whiich are too big to manage in a single file, or data fro om another discipline or o external company. c Some pro ojects requirre that mod els of single e buildings are split intto multiple files f and linked bacck together in order to maintain manageable model file ssize. Key pointss to conside er when linkking files are e: • Task allocation shall s be con nsidered when dividing the model sso as to minimise the ne eed for userrs to switch between models. m • Divisio on shall be determined d by the lead architect / engineer iin conjunction with the Co oordinator. • Mode el Lines shall be used to o create cro oss-hairs in open spacee prior to dupliccation of the e model. Th hey then serrve as a quick-check too ensure tha at the sub-m models are aligned a afte er Linking. • When n first linking g the modells back toge ether, ‘Origin to Origin’ shall be us sed as the insertion mec chanism. Before split and link ked models are shared with the rest of the teaam: • The re eal-world co o-ordinates of a point on o the proje ect shall be defined and d publisshed to all linked mode els using the e ‘Shared Coordinate’ C ttools. AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 12 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• Each sub-model shall be reo opened and d the other sub-models s s Linked in as a requirred using th he ‘By Share ed Coordina ates’ insertion method.. • The re elationship between Trrue North and Project North N is corrrectly estab blished. When sp plitting a file into sub-m models the below b workflow shall bee followed:

Each sepa arate discip pline whethe er internal or o external, involved in a project sh hall have its own model and a is respo onsible for the contents s of that moodel. A disciipline can Link in another discipline’s d S Shared mod del for referrence. • Share ed Coordina ates and Pro oject North rotation sha all be agreeed and docum mented at th he outset. N No deviation n from these e shall occuur without permission of the e Coordinattor. • Detaills of any dis scipline-spe ecific require ements, suc ch as the diifference be etween Finish hed Floor Le evel (FFL) a and Structural Slab Lev vel (SSL), sshall be fully y docum mented in th he Project B BIM Executiion Plan. • The Copy C and Monitor toolss in Revit sh hall be used to duplicatte and relate e Levels and Grids G only. • The Copy C Monito or tools sha ll not be used for otherr element caategories without w a full un nderstanding of limitatio ons, such as a the creatiion and upddate of certa ain eleme ents is not reflected in tthe monitorring process s. • Owne ership of ele ements shalll be properrly communicated and ttracked thro ough the prroject time-line (e.g. flo oors may be e created by y the Architeectural team m, but are th hen adopted d by the Stru uctural team m to form pa art of the loaad-bearing structure). • Each discipline shall s be con nscious that referenced d data has bbeen produc ced from the t perspec ctive of the a author and may not be e modelled tto the required speciffication for other o purpo oses. In this case, all re elevant partties, with inp put from the BIIM Manager(s) shall co onvene to discuss the potential p re--allocation of o ownership. • Shoulld a team de evelop a ‘sttarter mode el’ for a partn ner disciplinne, such as defining the struc ctural mode el in conjunc ction with th he architectuure, this sha all be done in a separa ate model w which shall th hen be linke ed in.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 13 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• This starter s mode el may be p passed to th he partner discipline d whho shall then assum me ownersh hip of it. The e partner dis scipline sha all open thiss starter model and link in n, by shared d co-ordinattes, the orig ginator’s model as a refference. With models produce ed for Buildiing Services s, several disciplines d m may be colla ated in a single model, m as a single piece e of equipm ment may require conneection to va arious services. In this scen nario, the mo odel may be split in va arious ways.. The Coord dinator shall be consulted in defining the e project-sp pecific strate egy.

7M Modellling Metho M odolog gy 7.1 M Model De evelopm ment Me ethodology Standard templates have h been ccreated to facilitate, f a Model M Deveelopment Methodolo ogy which shall s be use ed to develo op projects in i early stagges as it en nables rapid mod del developm ment and a llows for ve ery large mo odels to be ccreated with h low hardware requiremen nts. emplates prrovide only one examp ple of each element, e suuch as ‘Doors’. • The te These e concept (G Grade 1 - se ee section 0) 0 elements s shall be ussed to form categorised place e-holders in n the modell. components. Errors can c occur iin swappin ng one EXCEPTION for MEP system c onent for a nother and d so the above metho odology shall be MEP systtem compo used only y on components wh ich are nott system re elated.

7.2 G Graded Compon C nent Cre eation • In add dition to the e grading, a componentt may make e use of Coaarse, Mediu um and Fine levels of dettail to contro ol graphical representa ation. • A corp porate sharred parametter file is en ncouraged in order to m maintain consisstency of va ariable nam ming during content c creation. (Refeer to Section n Error! Referrence sourc ce not foun nd.) • Where e multiple grades g of th e same element do ex xist, care sh ould be tak ken to ensurre that the same s Share ed Paramete ers are inco orporated innto the objec cts, in order to maintain n data integrrity.

7.3 D Drawing Compila ation • When n CAD or BIM data is L Linked into a project, the design teeams shall ensure e that th he latest validated / che ecked desig gn information is accesssed directly from the Prroject Share ed area whe en composiing drawing g sheets.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 14 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

7.3.1 Sheet com mposition direct d from within the BIM Drawing sheet s composition from m within a BIM environm ment shall bbe establish hed through th he linking off views, calllouts, eleva ations and drawing sheeets fully within Revit softw ware. Care shall be taken to t ensure th hat any linke ed data is available andd visible prior to the publiccation of doc cumentation n from the BIM. B

7.3.2 Sheet com mposition frrom Viewss/Output file es Views exp ported from the BIM forr sheet com mpilation in CAD, C or forr use as a backgroun nd to other drawings in n CAD, shalll be placed on a plain border whic ch clearly ind dicates the following: f • The data d is provided for info ormation purposes only y • Detaills of the orig gin of the da ata • The date d of production or isssue Where ou utput files arre exported from the BIM for furthe er 2D detailling in CAD, originatorss shall ensu ure that cha anges occurrring within the BIM aree correctly reflected and a updated within the e CAD files used to pro oduce the finnal drawing g. If it is a re equirement to t export da ata from Re evit in ‘Real--World’ co-oordinates, th hen the export ope eration mus st be perform med from a working vie ew (such ass a floor-pla an) and not from a compiled sheet s view. Warning g: The inte egrity of exported viewss/output files from withiin a BIM ennvironment must m be checked for accuracy and ccontent prio or to drawing g compilatioon.

7.4 S Spatial Location L & Co-ordination As defined d in BS1192:2007, BIM M projects shall: s • Use re eal world co o-ordinate ssystems: • Be pro oduced to true height a above proje ect datum. • Adoptt the establiished Proje ct Shared Coordinate C system m across alll BIM data ffiles to allow w them to be refferenced without modiffication. Whilst the e above rule es are sacro osanct, Rev vit workflow dictates th hat individua al building m models are always created orrthogonal to o the screen n and at zerro elevation. The locatio on of the bu uilding in terrms of real-world d co-ordinates, true hei ghts and sh hared coAEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 15 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

s are e all establisshed and managed within the site model. ordinate systems CAD files that use real-world co--ordinates whereby w da ata is more tthan 1 mile from the origin (in any plan ne) need to o be modifie ed prior to im mport into R Revit and informatio on shall be shifted s close er to 0,0,0. This shift shall be agreeed, consistent and Execution Plan. documentted in the Project BIM E P Real-world co-ordina ates are then n re-established in the Revit envirronment and site / true locatiions are ma anaged with hin. Data expo orted from Revit R can th hen be eithe er real-world d or local annd whilst the e majority of o data will need n to be d delivered in OS co-ordinates for thhe purposes s of collaborattion and cro oss-referenccing, some software (e.g. certain sstructural an nalysis software) requires da ata to be loccated at 0,0 0. For exporrt to such sooftware, local coordinate e systems can c be utilissed.

7.5 U Units and d Measu urementt

8 Folderr Struc cture and Nami N ng C Conve entions 8.1 In ntroducttion 8.2 P Project Folder F Structure e 8.2.1 Central Re esource Fo older Struccture â&#x20AC;˘ Stand dard templates, titlebloccks, families and otherr non-projecct-specific data d shall be b held with hin the servver based Central C Reso ource Librarry, with resttricted accesss. -

<SE ERVER NAM ME>\Resou rce\Autodesk_Revit + Titleblocks andards + Sta + Tem mplates [Refer to + Fam milies t Section E Error! Reference ot found.] source no All locatio ons for the storage s of F Family comp ponents sha all be sub-diivided as fo ollows: -

Fam milies + 2 2009 2 2010 Architec cture Mechanical_Servicces Structurre General -

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

[Exists s in severall locations]] [The ve ersion of thee software] [The ve ersion of thee software] [Archite ectural compponents] [MEP componentss] [Structu ural componnents] [Non discipline-speecific eleme ents] Pag ge 16 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

Autodes sk_Metric_L Library Material_Library

[Default supplied ccomponents s] es libraries and images s for [Texture render output]

8.2.2 Local Project Folder Structure Local cop pies of centrral project m models do not need to be b backed uup as chang ges are regularly synchronise s ed with the central mod del. They sh hall be storeed on the us ser’s hard drive e – not in ‘M My Docume ents’– acco ording to the e folder struucture below w. -

D:\ -

[Standa ard local drivve] [Storage of Revit loocal projectts] [Name of project]

BIM_Projectts B <Projectt Name>

8.3 G General Naming g Conventions 8.4 M Model File Namiing 8.5 D Division Naming g Worksets should be named n in a consistent and logical manner to aid navigattion through th he project.

Note: As these are a created,, the ‘Enabl ed in All Vie ews’ option shall be chhecked in ev very case except Furniture e. (This can not be chan nged later)

Zo one

Description

Field 1: Zone Z (Optio onal) Larger proje L ects can be divided horrizontal or vertically intoo zones/lev vels and s this should be inden so ntified in the workset na aming where re applicable e. Field 2: Description D n Description of workset ccontent; used in isolation in smalleer projects, or in D c combination n with one o or both of Zo one and Lev vel on largeer projects. Should tyypically be one o of the ffollowing: Ceilings

Cei lings and atttached com mponents

s Cores

Arc hitectural co omponents of core

Furnitture

Furrniture and equipment e

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 17 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

Interio ors

Inte erior walls and doors

Shell

Exte erior walls and a opening gs

Slabs

Horrizontal elem ments includ ding roofs

Circullation Sta irs, ramps and a landings Structture

Stru uctural slabs and colum mns

Exampless:

8.5.1

Worksett Name

Exa ample of us se

L01-Mod del

Pro oject broken n by levels

L01_14-Internals

Mullti-Level Inte ernal layoutt

East_Lvll26-Partition ns

Verry large projject broken into zones,, levels and systems

Core

Sm all project; core span levels

East-Corres

Larg rge project; cores span levels

Workset Not Define ed Some elements do not require e explicit work kset definitio ons due to tthe standarrd behaviourr of Revit. • Grids s

These are included in the Shared d Levels andd Grids.

• Areas s

View speciffic and don’t require a workset.

• Anno otation

View speciffic and don’t require a workset.

8.6 L Library Object O Naming 8.7 O Object Property P g Naming 8.8 V View Naming This stand dard is limited to draug ghting views s and sheet views (althhough the Project P Browser in ncludes oth her kinds of elements). • The Revit R functio onality that a allows for th he Title on Sheet to bee different to the view name n shall not be use ed. Exceptio ons for struc ctural modeelling: • A view w to be used as a subsstructure or superstructture sectionn. In this ins stance, the vie ew property y "Title on S Sheet" shall be rename ed to "SECT TION". • A view w to be used as a wall or framing elevation. In this instannce, the vie ew prope erty "View Name" N shall be similar to t "VB-2" an nd the view w property "T Title on Sheett" shall be renamed sim milar to "Fra aming Eleva ation – VB-22".

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 18 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• Level names are e spelled ou t as they ne eed to appe ear in a room m schedule (as well as a how they will appearr in sections s and elevations.) Do nnot pad the level numb ber with lead ding zeros. • Viewss shall not be named iin order to make m them sort or grouup more log gically in the Prroject Browser as the g grouping an nd filtering settings s takee care of tha at autom matically (ie the prefixin ng of level names n by se equential nuumbers). • View names shall be written n in UPPER RCASE. Creation of o temporarry working vviews is enc couraged. The T filtering described in i Section Error! Referrence sourc ce not foun nd. will ensure these reemain in the e top ‘views’ section of the project bro owser.

8.8.1

Special Views V Plan view ws differ in Revit R from otther views because b the ey can be dduplicated (w without reproducin ng their refe erence marrk as is nece essary with elevations and section ns.) This resullts in many special-purrpose plans that are tem mporary or maybe nev ver placed on n title-sheets s. The follow wing are exc ceptions to the view na aming conve entions desscribed abov ve. View w Type

Colourr Plans

Naming Convention n COLOUR - <modifierr>

Examp ples COLOUR – L1 COLOUR – LEVEL L 1 PRIMAR RY

Views crreated in ord der to comm municate a information relating to elements which w meet a specific s crite eria.

EXPOR RT – L1

Export Views

EXPORT - <modifier> >

EXPOR RT – LEVEL L 1 ELECTRIICAL BACKG GROUND

Special configuratio c ons may be required for supplying graphical innformation which is specifiic to a partic cular discusssion. These views sha all show infoormation relating to the oriigin and datte/time of th he extract as a described d in Sectionn 7.3.2.

IMPOR RT – L1

Import Views

IMPORT - <modifier> > IMPOR RT – LEVEL 1 ELECTRIC CAL

A dedica ated view sh hould be use ed for attac ching linked and importted material that needs to o be segrega ated from o other views. (This requirement helpps to avoid technical problems and make itt easier to control c visib bility.)

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 19 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

8.9 V View Listt Scheduling Two pre-d defined sche edules are included in the templattes to manaage the view ws, namely th he Publication View L ist and the WIP View List, which contain columns for the folllowing data a:

Publ ication Vie ew List View N Name

Title on Sheet

Sccale Value 1:

Sheet Number

Sheet Na ame

WIP View w List View w Name

Scale Va alue 1:

Detail Leve el

Views are e grouped by type withiin both sche edules in orrder to aid nnavigation. It is recommen nded that th hese sched ules remain n unchanged and that nnew schedu ules are created, should s the need n arise tto make this s information available externally in a different fo ormat.

8.10 Data Orrganisattion al structuree to the view The Proje ect Browser in Revit pro ovides an organisation o ws and componen nts within th he BIM enviironment. The T following g rules are defined with hin the templatess to automattically sort W WIP views from f Public cation views ws. • View folders shall be groupe ed by Family and Type and sorteed by Assoc ciated Levell in Ascend ding order. • The Views V shall be filtered b by Sheet Na ame which should be E Equal to a value of None e. View section will now w show only y views not allocated a too a drawing sheet. • Sheett folders sha all be group ped by Shee et Number using 1 Leeading Character and sorted by Sh heet Numbe er in Ascen nding orderr. • No filtters shall be e applied to o the Sheets s.

8.11 Sheet Naming N

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 20 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

9P Presen ntation Styyles 9.1 In ntroducttion This section defines the criteria which ensu ure the plotted appearaance of draw wing output from the BIM is i consisten nt and of the e highest qu uality. Thesse criteria arre embedded d within the e associated d discipline--specific tem mplate files which acco ompany this docum ment.

9.2 A AEC (UK K) Comp pliant Ma aterials Three disccipline-spec cific Revit p project temp plates are av vailable as part of this Standard.. They can be b obtained d from the www.aec-uk w k.org web siite and are maintaine ed by the AE EC (UK) BIM M committe ee. Additionallly, a numbe er of family templates are a included d. These te mplates pro ovide an alternative e basis for new n familiess, consisten nt with the content c of thhis standard d.

9.3 A Annotatio on 9.4 T Text Asssignment All text sh hall be restriicted to the following sizes: Text heigh ht (mm) Plotted d fu ull size

Line Weig ght Allocatio on

Usage

1.8

Gen neral text, dimensions, notes – used on A3 & A4 A size drawings

2.5

General text, Dimensiions notes

3.5

Sub-headingss,

3.5

General text, dimensions, d nottes – A0 drawings

5.0

Norma al titles, drawingg numbers

7.0

Major titles

9.5 L Line Weiights Line weights control the graphiccal display of o on-screen n data as weell as all pu ublished output. Lin ne weights assigned to o Model elements are scale s depenndent whilstt those associated with Anno otation obje ects are fixed. There are e 16 model line l weightss. Each can be given a plotted thicckness acro oss the range of drawing d sca ales as defin ned below. • Thin Lines L mode shall not b be used as this distorts s the producction requirements of pub blication outtput and pro omotes ove er-modelling g and over-ddetailing. • Line weights w are assigned p project-wide e by categorry of compoonent and can be overridden by vie ew and by e element. Ind dividual lines on elemeents can also be overridden. Overrriding shou uld be kept to t a minimu um to aid coonsistency. AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 21 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

• The plotted p appe earance of m modelled co omponents shall be reppresented in na manner that prov vides ‘depth h’ to the drawing and allows for addequate differe entiation of elements ccut in section n, profile vie ew and prioority elemen nts. Pen

1:10

1:20

1:50

1:10 00

1:200

1:500

Perspecctive

Annotation A

0.1300

0.1 1300

0.060 00

0.0600

0.06000

0.0600

0.1500

0.1 1500

0.130 00

0.0600

0.13000

0.1300

0.1800

0.1 1800

0.150 00

0.1300

0.0600

0.15000

0.1500

0.2000

0.2 2000

0.180 00

0.1500

0.1300

0.18000

0.1800

0.2500

0.2200

0.2 2200

0.200 00

0.1800

0.1500

0.20000

0.2000

0.3500

0.2500

0.2 2500

0.220 00

0.2000

0.1800

0.22000

0.2200

0.4000

0.3500

0.3 3500

0.250 00

0.2200

0.2000

0.25000

0.2500

0.5000

0.4000

0.4 4000

0.350 00

0.2500

0.2200

0.35000

0.3500

0.6000

0.5000

0.5 5000

0.400 00

0.3500

0.2500

0.40000

0.4000

0.7000

0.6000

0.6 6000

0.500 00

0.4000

0.3500

0.50000

0.5000

1.0000

0.7000

0.7 7000

0.600 00

0.5000

0.4000

0.60000

0.6000

1.4000

1.0000

1.0 0000

0.700 00

0.6000

0.5000

0.70000

0.7000

2.0000

1.4000

1.4 4000

1.000 00

0.7000

0.6000

1.00000

1.0000

3.0000

2.0000

2.0 0000

1.400 00

1.0000

0.7000

1.40000

1.4000

4.0000

3.0000

3.0 0000

2.000 00

1.4000

1.0000

2.00000

2.0000

5.0000

4.0000

4.0 0000

3.000 00

2.0000

1.4000

3.00000

3.0000

9.6 L Line Pattterns The supp plied templa ates contain n a number of defined d Line Pattterns for us se in all draughting g productio on work. T These Line e Patterns are defineed below and a any additional Line Patte erns shall be e created by b the Coorrdinator andd named ac ccording to the nam ming conven ntions desccribed in Sec ction 0. Pattern Name

Type Value Type Value T Type Value Typ pe Value Type e Value Type V Value Type Va alue Type Valu ue Demolish hed

Dash

Space 1.5

Elevation n Swing

Dash

Space

Grid Line e

Dash

Space

Hidden

Dash

Space

Overhead d

Dash 2.5 Space 1.5

Window S Swing

Dash

Space

AEC_Centre

Dash

Space

AEC_Dash 1.5mm

Dash 1.5 Space 1.5

AEC_Dash 3mm

Dash

Space

AEC_Dash 3mm Loose

Dash

Space

D Dash

Spa ace

D Dash

Spa ace

D Dash

Spa ace

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 22 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

AEC_Dash 9mm

Dash

Space

AEC_Dash Dot 3mm

Dash

Space

Dot

Spa ace

AEC_Dash Dot 6mm

Dash

Space

Dot

Spa ace

AEC_Dash Dot Dot 6mm m Dash 6 Dot AEC_Dot 4mm

Space

Dot

Spa ace

Space

AEC_Dot 1mm

Dot

Space

AEC_Dot 2mm

Dot

Space

AEC_Double Dash

Dash

Space

AEC_Hid dden 2mm

Dash

Space

AEC_Trip ple Dash

Dash

Space

Dot D

Space

D Dash

Spa ace

Dash h

Space

D Dash

Spa ace

Dash h

Space

Dash

Space

9.7 L Line Styles Line Style es are define ed in the su upplied templates as a project settting. These styles are docum mented belo ow and any additional Line L Styles shall be creeated by the e Coordinattor and nam med accordi ng to the na aming conv ventions desscribed in Section S 0. Category y

Li ne Weight

Line Colour

Line Pattern

RGB 000-161-000

Solid S

Area Boundary

RGB 128-000-255

Solid S

Beyo ond

Black

Da ashed

Centtreline

Black

AEC C_Centre

Demolished

Black

Dem molished

Hidde en

Black

Hidden

Overrhead

Black

Ove erhead

Room m Separation

Cyan

AEC_D Dash 3mm

Sketcch

Mag genta

Solid S

Spacce Separation

Grreen

AEC_D Dash 3mm

Axis of Rotation

Blue B

AEC C_Centre

Hidde en Lines

RGB 000-161-000

AEC_D Dash 3mm

Insulation Batting Lin nes

Black

Solid S

Liness

RGB 000-161-000

Solid S

Mediium Lines

Black

Solid S

Thin Lines

Black

Solid S

Wide e Lines

Black

Solid S

AEC_ _1-Solid

Black

Solid S

AEC_ _3-Solid

Black

Solid S

AEC_ _5-Solid

Black

Solid S

AEC_ _6-Solid

Black

Solid S

AEC_ _7-Solid

Black

Solid S

AEC_ _8-Solid

Black

Solid S

AEC_ _9-Solid

Black

Solid S

P Projection

Lines

General

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 23 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

AEC_ _10-Solid

Black

Solid S

Architec ctural AEC_ _10-DPC

Mag genta

Solid S

AEC_ _10-DPM

RGB 000-128-000

AEC_Double Dash

AEC_ _8-RNF_Mesh

Black

AEC_Da ash Dot 6mm

AEC_ _11-Rebar

Black

Solid S

Structurral

9.8 H Hatching g and Fillled Reg gions Default Fill F Patterns s for Model a and Draugh hting, which h are loadedd into the de efault template es, should be used. • Altern native Fill Pa atterns shalll be used only o with the e approval oof the Coord dinator. • Hatch hing/patterning shall be e created us sing the rele evant tools aavailable within w the softwa are. • Where e possible, hatch patte erns should be assigne ed to the releevant materials for the elements, ratther than asssigned as 2D 2 patches. • Care shall be tak ken to ensurre that the draw d order and transpaarency settiings of filled regions r are appropriate e to the situ uation so as s not to coveer required graph hical informa ation.

9.9 V View Tem mplates The defau ult templates have a nu umber of pre e-defined View V Templaates and associated View Filte ers as descrribed below w. • View Templates shall be use ed to mainttain consiste ency acrosss published output. • Adjusstments to th he settings of the View w Templates s shall be caarried out only with the ag greement off the Coord inator. • Adjussted View Te emplates m must be re-a applied to all relevant viiews in orde er to propa agate chang ges.

Name Fire Rating – 30min

Fire Rating – 60min

Categ gories

Filter By

C Criteria

Value

Ceillings Flo oors Do oors Wa alls Ceillings Flo oors Do oors

Fire Designatio on

C Contains

Fire Designatio on

C Contains

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 24 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

Fire Rating – 90min

Fire Rating - None

Acoustic - Hig gh

Acoustic - Low w

Acoustic - No one

Wa alls Ceillings Flo oors Do oors Wa alls Ceillings Flo oors Do oors Wa alls Ceillings Flo oors Do oors Wa alls Ceillings Flo oors Do oors Wa alls Ceillings Flo oors Do oors Wa alls

Fire Designatio on

C Contains

Fire Designatio on

Dooes Not C Contain

Acoustic A Designa ation

Is grreater than or equal to

Acoustic A Designa ation

Is lless than

Acoustic A Designa ation

Dooes Not C Contain

9.10 Dimenssioning No supple ementary information iss required.

g Borderrs and T Title Bloc cks 9.11 Drawing • Corpo orate titleblo ock are ava ilable from the Families area of thhe central re esource folderr. • Altern native client-specific ve ersions may y also be available from m the same locatio on. • Projecct-specific titleblocks s hall be crea ated and sto ored in the P source Project Res folderr.

9.12 Symbology Standard symbols su uch as North h point, sec ction marks and call-upps are availa able from within the discip pline-specifi c template files and sh hall be usedd by default.

9.12.1 Section an nd Detail Marks M Section an nd Detail marks m shall b be accessed d from withiin standard template files, Revit’s de efault repository or the Central BIM M library.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 25 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

9.13 Copyrig ght

10 Reso ources s 10.1 Introducction 10.2 Softwarre 10.3 BIM Content / Resourc R ce Librarries Revit deffault family libraries are e available through the e Central Reesource Lib brary as read-onlyy. Any elem ments from tthis library which w require modificattion prior to o utilisation n shall be copied c to the e Project Re esource Lib brary.

10.3.1 Project BIM M Resourc ce Library This shall be the repo ository for th he storage of project specific stanndards wherre deviation from this sttandard is re equired due e to project or client reqquirements. • Stand dards, templates, titlebllocks, families and other data prodduced in the e proce ess of completing the p roject shall be held witthin the Proj oject BIM Re esource 1.2). Librarry (refer to Appendix A 11

10.3.2 Central BIM Resourc ce Library • Conte ent shall be segregated d by softwarre product and a versionn. When co ontent is upd dated for usse in newerr product ve ersion: • The original o data a shall be m maintained, • The updated u vers sion of the ccontent sha all be create ed in the apppropriate lo ocation for tha at product & version. T This avoids ‘forwards in ncompatibili ty’ when us sing content with the version v of t he software e for which iti was originnally created.

10.4 Keynote es A defaultt Keynote file is include ed as part of o this Stand dard and caan be found in the Standard ds folder witthin the Cen ntral Resou urces. • This file f shall be copied to th he project’s s Resource> >Standards folder for each e new project. p • Modiffications to the t project- specific verrsion are to be manageed by the Coord dinator.

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 26 of 27

AEC (UK K) BIM Protoco ol for Autodesk k Revit

10.5 Custom m metada ata The corp porate Shared Parametter file is he eld in the Sttandards follder within the t central re esource. Th his is mainta ained by the e BIM Mana agement Teeam â&#x20AC;˘ When n the creatio on of projecct-specific fa amilies requ uires the deffinition of sh hared param meters, a file e shall be ccreated within the projectâ&#x20AC;&#x2122;s resourcce folder. Once O this content is approv ved for the ccorporate library, the associated a S Shared Para ameters will be e appended d to the centtral Shared Parameters.

ard Shorttcuts 10.6 Keyboa Only de elivered Auttodesk Reviit keyboard shortcuts shall s be used

11 Appe endice es 11.1 Model File F Nam ming Cod des 11.2 Project Folder Structure e S

AEC(UK))BIMProtocolF ForAutodeskR Revit-v2.0.docxx

Pag ge 27 of 27