Arc Hi Cad Big Building Whitepaper

7/31/2019 Arc Hi Cad Big Building Whitepaper

1/31

1

Big Bu i l d ing W h i t epape r


2/31

2

Table of Content

1 Preface ...............................................................................................................................42 Challenges .........................................................................................................................43 Definition of Big Buildings ...............................................................................................4

3.1 3D Polygon Count ...................................................................................................43.2 The Project File size................................................................................................53.3 Layout Book Size ....................................................................................................63.4 Team Size ................................................................................................................63.5 No. of stories ...........................................................................................................63.6 Summary..................................................................................................................7

4 Hardware and Software Requirements..........................................................................74.1 Suggested configuration ........................................................................................8

4.1.1 Archicad NetworkKey Servers...........................................................................84.1.2 File Servers..........................................................................................................84.1.3 Archicad Workstations .......................................................................................84.1.4 Rendering and Visualization Workstations......................................................8

4.2 Memory Requirements ...........................................................................................94.2.1 Windows XP Professional..................................................................................94.2.2 Windows XP Professional x64 Edition ..............................................................94.2.3 Mac OS X..............................................................................................................9

5 Speed Issues ...................................................................................................................105.1 3D Rebuild and Navigation ..................................................................................10

5.1.1 The Polycount add-on ......................................................................................105.1.2 How to reduce the 3D model size? ................................................................115.1.3 Sections and Elevations...................................................................................13

5.2 Rendering...............................................................................................................135.3 Floor Plan Regeneration.......................................................................................14

6 Setting up the Project Team .........................................................................................146.1 Mid-size Office .......................................................................................................156.2 Large Office............................................................................................................15

7 The Modeling and Documentation Workflow ..............................................................167.1 Small Projects Single File Concept..................................................................177.2 Medium Size Projects Model File and Document File Separated .................187.3 Big Projects Hierarchal File Structure..............................................................18

8 Sharing the Project.........................................................................................................208.1 1. Teamwork..........................................................................................................208.2 2. Hotlinked Modules............................................................................................218.3 3. Xrefs...................................................................................................................228.4 4. Documentation Separated from the Model File ...........................................23

8.4.1 Master file Method............................................................................................248.4.2 Complex and Distributed methos...................................................................24

9 Company Standards.......................................................................................................259.1 The Company Template File................................................................................259.2 Library Management.............................................................................................259.3 Archiving and Data Safety...................................................................................26

10 Case Studies ..............................................................................................................2610.1 Campus Buildings / Orcutt Winslow Partnership..............................................26

10.1.1 About the Company .....................................................................................2610.1.2 Project Details...............................................................................................2710.1.3 Use of PlotMaker...........................................................................................27


3/31

3

10.1.4 Use of TeamWork .........................................................................................2810.1.5 Use of Hotlinked Modules ............................................................................2810.1.6 Use of Templates..........................................................................................2910.1.7 Use of Details ................................................................................................2910.1.8 Use of Libraries .............................................................................................29

10.2 Offices and Retail Units /John Robertson Architects........................................29

10.2.1 About the Company .....................................................................................2910.2.2 Project Details...............................................................................................2910.2.3 The Project Workflow...................................................................................3010.2.4 For Planning:.................................................................................................3010.2.5 For Tender:....................................................................................................30


4/31

4

1 Pr eface

The size and complexity of projects and other important factors like short deadlinesor big project teams can significantly influence the design and documentationworkflow in an architectural office. To find the most effective Archicad approach foryour practice requires lot of experimenting and refining of your working methods.

The main goal of this white paper is to provide strategy for using Archicad effectivelyon big projects. You may also find case studies in this document that illustrate howArchicad can be implemented successfully in large firms.

Furthermore it is important to call your attention that the integrated layoutingfeatures of Archicad 10 require the complete revision of the documentation workfloweven in those firms where Archicad has been used successfully for a long time. Wehope that experienced Archicad users will also find useful information in this book.

2 Ch al len gesWhat are the possible problems that you have to face when designing big buildings?

The project team size Communication with other team members (teamwork) Communication with partners (DWG-DXF) Office organization Document management File size Size of the 3D model (Polygon count) Hardware requirement

3 Def in i t io n o f Bi g Bu i l d i ng sThere is no exact definition for which building is big however we can say that thefollowing project attributes have to be carefully examined so that you can find thebest Archicad approach:

3D Polygon count File size Layout book size Team size No. of stories

3 .1 3 D Po l y g o n Co u n tToo many 3D polygons in the Archicad model can significantly slow down theregeneration of 3D, section and elevation windows that in worse case can freezeArchicad. The 3D polygon limitation of Archicad depends on many factors includingthe computers memory, the graphic cards memory and the type of the active 3D


5/31

5

window (internal engine, OpenGL, rendering, section/elevation etc.). For the detaileddescription of Archicads memory requirements please read chapter 4.2.Generally speaking we can say that more that 2 0 0 .0 0 0 p o l yg o n s results a bigmodel in 3D views and in this case you have to make sure that your computershardware configuration is suitable for the project. Projects with more then 2 millionpolygons can be unacceptably slow in 3D and may cause Archicad to freeze.

Please note that large polygon count or huge file size not necessary means bigbuildings. In most of the projects significant part of 3D polygons are generated fromlibrary parts. The model of a room interior can easily contain as many polygons as amultistory building if the room is furnished with very detailed GDL objects. Pleaseread chapter 5.1.2 for advice how to limit the polygon count.

3 . 2 The P ro j ec t Fi l e si zeIf the project file exceeds a certain size the input-output operations (e.g. save, saveas etc.) can be significantly slower. Furthermore the send and receive times inTeamwork will also increase. Again we can say that there is no explicit number todescribe big files. The type and number of Archicad elements placed in the model,

the number of layouts or the attributes defined in the project can largely influencethe file size.According to the feedback that we received from large clients the maximum file sizethat Archicad 9 and earlier versions could handle easily was about 1 0 0 -1 5 0 MB. Ifthe project file exceeded this size these companies usually divided them into smallerlogical parts to avoid any performance drawbacks. They also found that files biggerthen 250-300 MB were slow to redraw in 2D and 3D views and in case of TeamWorkfiles the send and receive time increased significantly.

The handling of large projects has changed positively in A r ch i ca d 1 0 due to thefollowing new program features:

1. Fi le compression : Archicad 10 can save the plan files in compressed formatthus less hard disk space is required for project file storage.

2. I n t a g ra te d l a yo u t i n g: The layouting functions of PlotMaker are nowavailable in Archicad 10 with fully compatible user interface and interactionstandards. With the integration we eliminated the need for a BackgroundArchiCAD to manage the update process of placed views on layouts. As aresult the update time of views are shortened significantly especially with bigprojects. Furthermore the workflow of editing placed views on layouts is nowmuch smoother. According to our tests Archicad 10 is able to handle evenvery big projects that contain the 3D model and the complete documentationin one file. In one of our tests we merged the content of a big PlotMaker 9file (about 150MB) and a large ArchiCAD 9 project file (about 120 MB) inArchicad 10. We found that the size of the resulting AC10 plan file dropped to70 MB due to the file compression and the merging of the identical project

attributes. More importantly Archicad 10 was able to work smoothly with theproject in plan, 3D and layout views.

3. Sca lab le p ro j ec t se tup handling multiple project files: The new userinterface provides a transparent overview of hierarchal file structure withmultiple model and document files. You can see the structure of all currentlyrunning Archicad files of all sessions in the Navigator. This makes it easier tobuild up the Layout Book and navigate through different files. Layouts can bemore easily linked to view data from several source model files.


6/31

6

No matter which Archicad version you are using it is very important to control thesize of the project files. See chapter 5.1.3 and 7.3 for advice how to curb file size.The following project elements can extend the file size with tens of megabytes so its

highly recommended to purge the unused ones from the project: Sections and elevations High resolution pictures placed on the floor plan and layouts Attributes (materials, fills, line types etc.). Note that the unused attributes

can be easily deleted with the Attribute manager Merged DXF/DWG drawings including many lines, fills and polygons

3 .3 La y o u t B o o k Si zeSeveral layouts in one Archicad project can heavily expand the file size and in case oftoo many auto rebuild drawings the update process for the entire layout book can beunacceptably slow. You also have to consider that managing 100 drawings from one

file could be more complicated then if the drawings were divided into multiple PLNfiles. Our users experience show that in case of more then 5 0 -1 0 0 l a yo u t s itsworth to separate the documentation from the model file. This way thedocumentation team can work independently from the design team. If the number oflayouts exceeds 100 we suggest subdividing the documentation into two or morefiles.For more information about the new documentation concept of Archicad 10 pleasestudy carefully the corresponding chapters of the Archicad 10 Reference Guide andthe Migration Guide.

3 .4 Te am Si ze

Sharing and coordinating the tasks between the project team members is one of themost challenging jobs of the project leader regardless of which CAD software is usedin the firm. Graphisofts TeamWork technology offers an effective solution for thisproblem even though TeamWork has its limitations mainly because of the send andreceives times. If this process takes lets say 5 minutes for one team member, it canbe easily calculated that in case of 10 team members sending and receiving changesfor the entire team would take almost an hour. In addition to that the project leaderhas to regularly check and approve the changes made in the TeamWork file, whichprevents the other team members to sign in during the project is being checked.Thus there seems to be a consensus among our TeamWork users that a maximum of5 -6 u se rs can work effectively on one TeamWork file. If you have bigger team werecommend you to apply other working methods, like the hotlink-TeamWorkcombination suggested at chapter 7.3

3 .5 N o . o f st o r i e sDesigning high rise buildings in Archicad sets the following problems:

many drawings needs to be created and maintained in the layoutbook typical stories should be generated automatically from the master floor due to the complex nature of these buildings usually there are many polygons

generated in the 3D model


7/31

7

Considering these points we can say that projects with more then 20 s to r iesrequires special attention from the project leader and the CAD manager. In case ofmore the 50 stories you very likely have to divide the project by different stories(e.g. basement levels, entrance level, typical floors etc.) and make a separate modelfile of the whole building for visualization purpose containing only the most important

visible elements.

3 .6 Su m m ar y

The following spreadsheet gives you a short summary of this chapter.

Size is b ig Size is cr i t i ca l So lu t ions

3D Po lygon

Count

200.000-1M 2-3 M 1. Reduce the polygoncount. See chapter 5.1.22. Split the project file intosmaller parts

Pro jec t Fi le Size 100-150 MB 250-300 MB 1. Divide the project intosmaller parts2. Separate thedocumentation from themodel file

Layout Book Size 50-100layouts

200 > 1. Separate thedocumentation from themodel file2. Subdivide thedocumentation into morefiles

Team Size 4-5 8-10 1. Split the project into

smaller parts2. Combine the TeamWorkfile with hotlink modules

No. o f s to r ies 20-40 100> 1. Make a separate modelof the whole building forvisualization containingonly the necessaryelements2. 1. Split the project intosmaller parts (e.g.basement levels, typicalfloors etc.)

4 Har d w a r e an d So ft w ar e Req ui r em e n t s

Before Archicad is implemented in the office the existing infrastructure such ashardware, software, and network solutions, should all be evaluated by the CADmanager. This process is even more critical if the company works with large projectson a regular basis.


8/31

8

4 .1 Su g g e st e d c o n f ig u r a t i o n

4 .1 .1 Ar ch ica d N et w o r k Ke y Ser v er s

In case the office is using Archicad network licenses a WIBU key server machine hasto be installed. This server has to fulfill relatively low hardware requirements:

The server should support the minimum HW requirements of the operatingsystem

There should be a free USB port available for the network dongle The server should be accessible from the Archicad terminals through a

network connection for 24 hours a day The WIBU technology support cross platform networks thus a Windows key

server can support MAC and Windows Archicad versions simultaneously The WIBU driver should be installed as a service, so network users can see it

even if no one is logged into the server

4 .1 .2 Fi le Se r v er s

File servers are primarily used to store Teamwork files, company libraries, templatesor any other materials that are required for the daily operation of the company. Fileserver requirements:

High storage capacity Preferably redundant file storage (RAID) Fast data access Fast network connection to terminals High stability and continuous operation 24/7 Graphisoft do not recommend using cross platform file servers in order to

avoid any compatibility problems (e.g. Windows servers for Mac terminals orLinux servers for Windows terminals)

4 .1 .3 Ar ch icad W o r k st a t io nsMost of the project architect will need the following computer configuration:

RAM: 1-4 GB (depending on the project size) For more details please readchapter 4.2

HD: Min. 10 GB of free space on the system volume CPU: Min. PIV 3 GHz or equivalent Display: 1280x1024 pixels or higher Graphic Card: Standard OpenGL card with 128MB or more onboard video

memory. For compatibility info, please visit: Archicad-talk.graphisoft.com/Compatibility.php

Archicad 10 supports the following operating systems:Windows XP Pro

Windows XP Pro x64 editionMacintosh OS X 10.3Macintosh OS X 10.4

4 .1 .4 Re n de r in g a n d Vi su a li za t io n W o r k s t at i o n s

Rendering and visualization requires the most powerful computers. Luckily only a fewof these special configurations are needed in a typical architectural office.Requirements:


9/31

9

RAM: 2-4GB (depending on the project size) For more details please readchapter 4.2

HD: Min. 10 GB of free space on the system volume CPU: Fast dual processors are highly recommended since most of the

rendering engines (including Lightworks) and imaging applications supportsthem

Display: 19 monitor or bigger (1280x1024 minimum screen resolution) Graphic Card: Standard OpenGL card with 128MB or more onboard video

memory. For compatibility info, please visit: Archicad-talk.graphisoft.com/Compatibility.php

4 .2 M em o r y Re qu i r em e n t s

If a requested operation consumes considerable amount of memory in Archicad, theapplications responsiveness can drop significantly, thus making impossible to workeffectively with the project. Furthermore if Archicad hits the limit of the availablememory address space, the application and/or the operating system will most likely

freeze or crash. To minimize the chance of these problems we highly recommend youto buy the maximum memory that Archicad can handle in case you need to workwith large projects (See below). The maximum memory that Archicad can utilizedepends on the Operating System and the available memory slots on the computersmotherboard.

4 .2 .1 W i n do w s XP Pr o fe ssi on a l

Windows XP is 32 bit operating system that supports a maximum of 4GB RAM. Out ofthe 4GB, the OS allows only 2GB to be assigned to one application. ConsequentlyArchicad cant address more then 2 GB o f m e m o r y .

4 .2 . 2 W i n d o w s X P Pr o f e ss io n a l x 6 4 Ed i t i o n

The 64 bit Windows OS supports up to 128 gigabytes (GB) of RAM and 16 terabytesof virtual memory. In this case the computers motherboard primarily determines themaximum physical memory. AC10 and AC9 (Build 2172 and above) can address amaximum of4 GB out of the total memory

4 .2 .3 Mac OS X

The latest MAC OS is also a 64 bit system therefore the similar memory limitationsapply as for windows XP x64. A maximum of4GB memory can be addressed fromArchicad.


10/31

10

5 Speed I ssu es

5 .1 3 D Re b u i ld a n d N a v i g at i o nThe most critical speed problems can occur when opening three dimensional views -including sections and elevations- since these operations require the largest amount

of physical memory. There are two risk factors to be considered:1. not enough physical memory available to complete the 3D operation2. the OpenGL card doesnt have enough RAM for 3D navigation

Both hardware requirements depend mainly on the 3D polygon count of the Archicadmodel. One can easily draw a building on the floor plan and in the section windowswhich cannot be visualized in 3D due to the excessive number of polygons.The memory consumption at rendering depends on more factors, and the number ofpolygons is only one of them: problems can occur at lower polygon counts as well(ca. 200.000 polygons) depending on the texture and image quality. If the polygoncount increases the next symptom will be the slow conversion to 3D and theunbearably slow navigation in 3D window especially when the entire model is visible.

If the model contains approximately 3-4 million polygons the three dimensionalnavigation is impossible and the render projection outputs a blank image. In case themodel contains more than 4 million polygons, chances are high that the applicationcrashes thus preventing Archicad from generating a 3D view of the entire model.These limits of course highly depend on the hardware configuration and otherspecific circumstances so they cannot be determined exactly.The conclusion is that in case of big buildings its essential to keep the modelspolygon count in an acceptable range. The following chapters will give you useful tipsfor how you can reduce the number of polygons within your projects.

5 .1 .1 Th e Po l yco u n t a dd - o n

Polycount is an Archicad 10 goody add-on that helps to control the number of 3Dpolygons in Archicad models. This tool can be used effectively if the project size orthe limited physical memory of your computer makes the 3D model size a criticalfactor in your modeling decisions. Polycount can display the number of 3D polygonsgrouped by element types (walls, slabs doors, windows, objects etc.) and also theirpercentage compared to the complete model size.The add-on also allows you to change the 3D detail level of certain library parts inyour projects. Most objects in the Archicad library includes a 3D Detail Levelparameter with options for Detailed , Simple and Off representations. The SetLevel of Detail function allows you to toggle between these values.The Polycount add-on can be downloaded from the Graphisoft Archicad 10 Goodieswebsite or by clicking on the Goodies link in the Archicad 10 Help menu. After thesuccessful installation the Polycount menu can be activated from

Window/ Palettes/ Polycount.


11/31

11

The interface of t he Polycount add- on

5 .1 .2 H o w t o r ed u ce t h e 3 D m o d e l s i ze ?

The following tips and tricks can help you to keep the model size in a controllablerange:

1. M ak e l ay e r c om b i n a t i on s ! They allow you to show only those elements ofthe virtual building model that are actually needed in the active 3D window.For example there can be one layer combination dedicated for external viewssuch as renderings or elevations, which turn of all the elements that arelocated in the buildings interior thus cant be seen. Other layer combos can


12/31

12

be defined for internal renderings or sections where the external, treesvehicles or other environmental elements are all hidden.

2. Use th e marqu ee ! Once you need to create a section, elevation or renderingof only a small part of the building (e.g. a room or a story) select it with amarquee. This simple trick can speed up the navigation in 3D views

3. Tu r n O FF t h e 3 D o f u n w a n t ed o b j ec t s! As a direct result of virtual building

modeling each library part that you place on the floor plan (apart from 2Dsymbols) has a representation in three dimensional views even if you onlyintend to show them on the floor plan. Moreover many of these elementsgenerates considerable amount of polygons in 3D. You can overcome thisproblem if you turn off their 3D representation with the correspondingparameter on the objects parameter list. Since all library parts in theArchicad library are having the same parameter name for this function youcan select multiple objects on the floor plan and turn of their 3D at once. Youcan also use the Set LOD function of Polycount add-on for this purpose.

4. Cont r o l the ob j ec ts l eve l o f de ta i l ! Most library parts in the Archicadlibrary have parameter for 3D detail level (simple, detailed, off) and curveresolution. Set these parameters to the possible minimum that is appropriatefor the required 3D view.

5. Avo i d u si n g m e mo ry e xce ss i ve l i b ra r y p ar t o p t i o n s ! Some optionalelements of Archicad objects can generate significant amount of 3D polygonswithout producing noticeable differences on the final drawings. Please becareful using the following parameters:

Handles for doors and windows Taps for bath tubs and lavatories Curved railings on stairs (including StairMaker stairs) Too many leaves for plant objects

6. Ch e ck t h e m o d e l w i t h Po l yco u n t ! This handy tool can identify elements ofthe model with too many 3D polygons. In addition to the previouslymentioned library parts other problematic elements can be:

MaxonForm objects

Complex Mesh models (e.g. site model) 3D people, plants and vehicle objects. Particularly elements imported

from 3Ds, which are usually very detailed models, intended to use inhigh end renderings instead of architectural visualizations.

The following table shows the polygon count of some Archicad library parts withdifferent parameter settings for your consideration. Note that one detailed officechair object (Man Hands in Pocket) generates as many polygons as 1066 walls! Letssee one more example that underlines the importance of polygon reduction. Oneoffice chair (Office Chair 01) with the default settings makes 3759 polygons in 3Dview that is the equivalent of 626 walls. Moreover there are typically many instancesof this object are placed in an office project.

Elem en t Ty p e 3 D Po lygon Cou n t

Wall without opening 6Wall with empty opening 10

D1 Door 80D1 Door with handle (Style 1) 1544

Basin 01 (Detailed) 1031Basin 01 (Simple) 685Basin with tap (Detailed) 1335


13/31

13

Basin with tap (Simple) 869

Man Hands in Pocket 6396People Bitmap 1 1

Office Chair 01 (Simple) 2594Office Chair 01 (Detailed, Resolution=8) 3759Office Chair 01 (Detailed, Resolution=16) 7433

Car 01 5583Vehicle Bitmap 1

Straight StairMaker stair with Post withBaluster railing

2093

Straight StairMaker stair with SimpleSurface railing

789

5 .1 . 3 Se ct i o n s an d El ev a t i o n s

Other problematic area of 3D views is section/elevation and detail databasehandling. If a project file has considerable amount of sections/elevations or details,then error messages might occasionally appear during open, save and rebuildprocesses: Not enough memory in heap zone Cannot read temporary section file,etc. with the consequence of data loss in the affected project parts. The limit againcannot be determined exactly, because it also depends on the model complexity. Asrule of thumb we can say that the number of the section/elevation and detailwindows should never exceed 2 0 0 .The other consequence of having excessive amount of these views is the file sizebloat. Project files with extremely complex 3D models have usually a reasonablysmall file size (20-30 Mbytes) if the number of sections and details is limited, while asimilarly complex project file can be bigger than hundred Mbytes, for instance ifthere are more than hundred section and detail views.Large files also have negative affect on the Section-elevation rebuild time. Prior to

section-elevation generation Archicad runs a pre-filtering on the floor plan.Consequently an invisible 2D view needs to be created before each section-elevationgeneration. This process can be significantly slower in case the floor plan is big orcontains slow to rebuild library parts.

5 .2 Ren der in gReducing the number of polygons with the previously shown techniques helps in twoways in case of photo rendered views:

1. The generation of the 3D view is quicker2. The calculation of the photo rendered image is also faster since the rendering

engine has to work with fewer surfaces

The major difference between a shaded view (e.g. OpenGl) and a photorenderingwindow is that the latter one calculates cast shadows and light reflections. Anymethod that reduces the number of shadow casting or light reflecting surfaces willresult faster renderings. The following techniques can be used:

Turn off the shadow casting for those library parts that dont generatenoticeable shadows in the actual view. There is a dedicated parameter for thispurpose in every Archicad library part.


14/31

14

Use texture mapping and the alpha channel effect instead of physical models.This trick can save precious rendering time in case of trees, vehicles, fencesand other complex objects are needed in the photo render image.

Reduce the number of light sources to the possible minimum. Too many lightssources can result significantly slower renderings.

Turn off shadow casting for brightener lights.

5 . 3 Floo r Pl an Regene ra t i onDrawing on floor plan also has its restrictions, but these are much harder to reachthen in case of 3D views. While Archicad is capable of manipulating 500.000 visibleelements on the floor plan, a more realistic number would be 100.000 in case of anaverage construction plan. Although Archicad will not crash or write enormous fileswith more then 100.000 elements, but the responsiveness will be unacceptably sloweven on cutting-edge hardware configurations. Note that more time will be taken toredraw the drawing if you zoom out from a smaller part of the project to the drawingextents. Also remember that the floor plan rebuild time influences the speed of thesection-elevation regeneration as described in chapter 7.3.Please consider the following devices:

1. Use layer combinations to control the content of the floor plan!2. Use bitmap fill representations instead of vectorial fills! Unless you need to

print a drawing select the bitmap fill representations from the on screen viewoptions dialog as it is regenerated faster then vectorial fills.

3. Avoid using symbol fills! Symbol fills can largely increase the floor planredraw time especially if the fill pattern contains many line and arc segments.

4. Only use PROJECT2 commands in library parts if its really necessary. Thoserequire the 3D view of the object to be generated for the 2D symbol thusmaking the floor plan redraw unreasonably slow. Note that MaxonFormobjects also use this GDL command. In the MaxonForm manual you can find adescription for how you can simplify the 2D of these elements.

5. Use a Symbolic 2D representation for static library parts without scripting thefloor plan symbol!

6 Set t i n g u p t h e Pr o j ect TeamSuccessful implementation of Archicad requires well documented office standards,trained office staff and proper organization of the project teams. This topic has beendiscussed in more details in the Introduction to Office Standards and in theCreating Large Building Models documents.

Here we only want to give you a few points to consider for the project team set up: How many projects run parallel in the office? How many architects can work simultaneously on one project?

How are the projects being shared (by Teamwork, hotlinked modules,layouting in separate files etc.)? Should you hire a full time CAD manager and/or IT manager? Will you need independent design and visualization teams in the firm?

Naturally there are no generally applicable answers for these questions. Moreoverthe organizational hierarchy within the office can dynamically change during thelifecycle of a project thus there is no use to set up any strict rules. Based upon ourusers feedback we suggest the following:


15/31

15

Get a full time CAD manager if more then 15-20 architects are working in theoffice

Even in case of 5-15 architects it is recommended to appoint a part time CADmanager from the project team

The CAD manager (in collaboration with the IT manager and the officeprincipals) should be responsible for developing the office standard book

As previously mentioned a maximum of5-6 users can work effectively onone TeamWork file, consequently this should be an important factor whensetting up the project teams

6 . 1 M id -si ze Of f i ceThe following charts show the organizational hierarchy of a typical mid-size and alarge office. In this example, there are two independent project teams with 2architects and 2 draftsmen working in each. The leader of the first team also servesas a part time CAD manager in the office. Due to the relatively small firm size andthe generally limited-size projects, informal communication is sufficient to handleproject coordination issues in most cases.

The typical problem for offices of this size is that they cant afford a full-time CADand IT manager, so somebody in the office has to tackle these problems part-time,which naturally decreases that persons productivity.

Mid-size architectural office (10 -15 employees)

6 .2 La r g e Of f i ceThe large architectural office shown on the next figure is subdivided into 4 teams.The first two are working on a large project therefore their tasks are coordinated bya project director. The project director and the leaders of the other two project

Principal(s)

Project Leader 2 Office Administration

Project Architect 1Project Architect 2

Draftsman 1

Project Architect 1Project Architect 2

Draftsman 1

Pro ect 1 Pro ect 2


16/31

16

teams are reporting to the Design Director. In this example a full time IT and CADmanager assist the project teams. The biggest challenge for these firms is toautomate the sharing of large projects and to ensure the adoption of office standardswithin the whole office team.

Large architectural office (30-50 employees)

7 Th e Mo d el in g an d Do cu m en t a t i onW o r k f l o w

Principal(s)

DesignDirector

ITManager

CADManager

OfficeAdministr

ProjectDirector

ProjectLeader

ProjectLeader

DesignTeam

ProjectLeader

ProjectLeader

ProjectArchitects

ProjectArchitects

ProjectArchitects

Visualization Team


17/31

17

The single file concept of Archicad has proven itself well in small firms with small tomedium sized projects. More extensive organizations with larger projects have todivide them into several files for many practical reasons. Those reasons includeperformance drawbacks of single file method and workflow bottlenecks with multipleusers working against one file. Archicad 10 supports different scale projects byproviding a transparent method of handling multiple sessions and views to this

complete collection of files. Basically there are three typical workflows in Archicad10, which can be combined depending on the actual project:

7 . 1 Sm a l l Pro j ect s Sing l e Fi l e Concep t

This is the suggested Archicad workflow for small to medium scale projects. Thecomplete 3D model (virtual building data) with its representations (floor plans,sections, 3d views, schedules etc.) and the final drawing sheets (layouts) areincluded in one Archicad file. This method can fully exploit the advantages of thevirtual building concept such as easy file management, automatic drawingupdates and listing. However above a certain project size and complexity the

Archicad plan file has to be divided into smaller parts to avoid speed and projectmanagement problems. Our tests show that projects smaller then 50-100 MB canbe handled smoothly in one project file. For more details please read chapter3.2.

The Archicad single file concept

LAYOUTBOOK

VirtualBuilding

Database

Floor plans

Sections

Details

3D views

Schedules

Layout

Layout

Layout

Layout

Layout

ARCHICAD PROJECT FILE (PLN)


18/31

18

7 .2 M ed i u m Si ze Pr o j e c t s Mo d e l Fi l e a n d D o cu m e n t

Fi le Separ at ed

The next figure shows that the project documentation (layout book) can beseparated from the project model file in order to reduce the Archicad file size or to

allow two teams (e.g. a modeling team and a documentation team) workingsimultaneously on one project. As we have noted earlier in case the project containsmore then 100 layouts you might have to consider this method.

Separate model and documentation file

7 . 3 B ig P ro j ec t s H ie ra rcha l Fi l e St r uc t u r e

In case of very big and complex buildings a combination of different file sharingmethods is needed that is appropriate for the office organization and the size of theproject. In the following example a multi-story office building is in the constructiondesign phase. The building consists of two towers. From the very early stage a 3Dmodel of the whole building was built, containing only those elements that wereessential for visualization and conceptual design. Based on this model two Teamwork

files were created (one for each towers) that served as the basis of the constructiondocumentation. The Teamwork files are referring to external hotlinked modules andXrefs such as column grids, land surveys and other consultantss drawings. Thedocumentation is stored in two layoutbook files in order reduce the size of theTeamwork projects and to allow the project documentation team to work parallelwith the designers/architects.

DOCUMENTATION (PLN)MODEL FILE (PLN)

VirtualBuilding

Database

Floor

Sections

Details

3D views

Schedules

LAYOUTBOOK

Layout

Layout

Layout

Layout

Layout


19/31

19

Complex file hierarchy

Hotlink

Modul

XREFdw

TeamWork File 01

l

Layoutbo

ok File

Layoutbook File

TeamWork File 02

l

XREFdw

3D ModelFile for

Visualization

Independent Detail

Drawings

Pictures(jpg, tifetc.)

Hotlink

Modul

Hotlink

Modul

Hotlink

Modul

Hotlink

Modul

Hotlink

Modul


20/31

20

8 Sh ar in g t h e Pr oj ectCollaboration is essential for making the project team function and moving projectsforward as rapidly as possible. Effective collaboration and project sharing techniquesare able to adapt to the project team size and the office organization. Archicad offersvarious solutions for project sharing that can be used alone or in combination.

8 .1 1 . Tea m w o r kGraphisofts award winning Teamwork technology provides an effective method forsharing Archicad projects. TeamWork allows your office to define different teamroles, such as "team leader," "team member," "administrator" and "visitor."Depending on the function assigned to them, team members have specific rights toaccess and modify the central project file.The basis for collaboration is a central project file shared among team members.Team members can reserve their own workspaces by applying restrictions toparticular areas, stories, and/or layers: as a result, each Archicad element will havean owner with the exclusive right to modify it.

The Teamwork concept

Advantages: Team members roles are clearly defined Team members can continuously check the others work No conflicts can occur in the architects workspace The Teamwork file is always up to date

Limitations Send and receive can be slow in case of large models (more then 100 MB)

TeamWorkFile (PLP)

LocalCopy 01

(PLC)

Send & Receive

LocalCopy 02

(PLC)

LocalCopy 03

(PLC)

Works ace

Works ace

Works ace


21/31

21

Users cant send and receive changes simultaneously therefore the CADmanager has to set up a schedule for the sending and receiving changes(Typically during lunch time and after the office hours)

The maximum number of concurrent TeamWork users are limited by the sendand receive times (Typically 5-6 architect can work effectively on one project)

Suggested UsageTeamwork should be your primary method for sharing the content of the virtualbuilding. In case of very large files and/or more then 5-6 team members we suggestdividing the project into more TeamWork files. Thus you can significantly reduce thesend and receive times.

8 .2 2 . H o t l in k e d M o d u le s

Using Hotlinked Modules allows you to insert the content of external Archicad files(sources) into the currently open Project (host). Elements inserted into the hostfollow all modifications of the source files.

Hotlinked Modules can be used, for example, to manage the repetitive structures ofbuildings such as hotels or offices with a large number of identical rooms bymodifying all instances in a single step. Moreover, the same structures can be usedin multiple Projects. This is also a good way to subdivide large Projects into easier-to-handle smaller files.

The elements of hotlinked modules are included in the Project, which means thateven if the hotlinked source file is not currently available, the Modules are stillpresent and visible, and they just can't be updated as long as the referred source fileis absent. However this also means that using hotlink modules doesnt reduce thesize of the master project


22/31

22

The Hotl ink module concept

Advantages: Module files can be updated automatically or manually Updating a module is fast and easy Repetitive elements of the project can be controlled and modified easily

Limitations Access to the content of the modules cant be controlled in Archicad Nested modules are not updated automatically No protection against workspace conflicts A detailed module organization chart has to be created by the project

coordinator before the project is started Doesnt reduce the size of the master file

Suggested UsageAlthough hotlink modules can be used as an alternative to the TeamWork technology(e.g. different floors of a multi story building can be drawn in separate hotlinkmodules) they cant provide the same flexibility and security that TeamWork can.The main purpose of using TeamWork should be the management of repetitiveelements in the projects.

8 .3 3 . Xr e f s

Xrefs provide an easy way to manage and merge the consultants DWG/DXF drawingsinto the Ac project. External DWG/DXF drawings will be automatically updated in the

Project File(PLN, PLA, PLP)

Hotlink

ModulModule File

(MOD,PLN)

NestedModule

(MOD,

HotlinkModul

HotlinkModul

Hotlink

Modul

HotlinkModul

HotlinkModul

Module

File(MOD,PLN)HotlinkModul

HotlinkModul

Hotlink

Hotlink

Hotlink


23/31

23

Archicad project if they are referenced as an Xref. Note that Xrefs can also belocated on an internal or ftp server.

The Xref concept

Advantages: External DWG/DXF files can easily brought in to the project Repetitive DWG/DXF can be controlled and modified easily

Disadvantages and limitations A detailed Xref organization chart has to be created by the project coordinator

before the project is started Xrefs hasve to be updated manually DWG Translator has to be set correctly Doesnt reduce the size of the master file

Suggested UsageXrefs should be used almost exclusively for merging consultants drawings, legacyAutoCAD projects or standard manufacturer details into the Archicad project.

8 .4 4 . D ocu m e n t at i o n Se pa r at e d fr o m t h e Mo d el Fi leThe documentation and the design teams can work simultaneously on the project ifthe documentation file is separated from the model file. The size of the master filecan also be reduced if you adopt this method. AC10 fully supports this workflow

Project File

(PLN, PLA, PLP)

Xref

Xref File(DWG,DXF)

Xref(DWG,DX

F)

Xref

Xref

Xref

Xref

Xref

Xref File(DWG,DX

F)Xref

Xref

Manual

Manual


24/31

24

since you can control complex file hierarchies in the new Navigator dialog. There aretwo strategic ways of separating the documentation from the model.

8 .4 .1 M ast e r f i le M et h o d

In this scenario there is a master Archicad file that contains the complete Archicadmodel, and the corresponding view sets. The documentation file refers to the viewsets of the model file and automatically updates the drawings if the model file ischanged. This method is applicable for medium to large scale projects.See the corresponding chart at chapter 7.1

8 .4 .2 Co m p l ex a nd Di st r i b ut e d m et h o s

In case of very complex or large projects usually there is no master file that containsall the drawings due to size and speed problems. Consequently the building model isstored in multiple project files (some of them can be TeamWork files; others can besimple Archicad project files that refers to hotlinked modules). There are two ways toimport the drawings into the documentation file

1. Drawings are saved individually as PMK files and linked to the Archicaddocumentation project file. In this case there is no direct link between themodel file and the document file, thus the drawings on the layout doesntfollow the changes of the model file automatically. This method is onlyrecommended if the PMK files are final or rarely updated or if the automaticdrawing update from the model file is too slow.

Manual PMK saving and linking to t he document file

2. Drawings are imported into the layoutbook directly from one or more buildingmodel files and other external file sources (DWG, DXF, PDF-s, image files,PMK-s etc.). In case of very complex building the documentation file can alsobe subdivided into two or more parts for easier drawing management. Seethe corresponding chart at chapter 7.3

This is a complex system but very powerful and in some cases may be the only wayto handle very large projects. In case of complex documentation structures are usedin the office it is crucial that the CAD manager/project leader develops and publish

DOCUMENTATION (PLN)MODEL FILE (PLN)

VirtualBuildingDatabas

LAYOUTBOOK

Manualupdate


25/31

25

the suggested file hierarchy for the project team members prior the CD phase isstarted.

9 Co m p an y St an d ar d s

Well documented company standards are essential for running a large officesuccessfully. It is even more crucial in case of large building when typically bigproject teams are working the same project file. It is primarily the CAD managersresponsibility to develop and maintain the office CAD standards. Below is just a shortdescription of what should be included in the CAD standard document. For moredetails please read the Introduction to Office Standards document:

9 . 1 The Com pany Tem p la t e Fi l eThe company template file is the most critical element of the office CAD standard.Whenever a new project is started the project leader must use this template as thebasis of the project master file. A comprehensive office template should contain the

following elements: Attributes

o Layerso Layer combinationso Penso Pen Setso Materialso Line Typeso Fill typeso Composites

Complex Profiles Schedules Model view options View sets Project preferences Favorites Layouts Layout Master pages

9 .2 Li b r ar y M an a g em e n tLibraries are crucial parts of the Archicad projects. In a typical architectural firm fourtypes of libraries are used:

1. Arch i ca d L ib ra ry is the most current version of the Archicad object library orin some cases just a subset of it. The subset library contains only those

elements of the standard Archicad library that are regularly used in thecompany.

2. Of f i ce Standard L ib ra ry is a collection of those objects that were developedaccording to the office requirements. This library typically includes annotationelements (e.g. markers, labels, drawing frames etc.) and 3D objects (e.g.doors, windows, curtain walls etc.).

3. Pro j ect Speci f ic Libr ar ies consists of those custom elements that weremade specifically for the actual project. Most of these objects are made bythe project team members.


26/31

26

4. A number ofTh i rd Par ty L ib ra r ies can be found on the Internet with usefulobjects that may not be found in the Archicad library.

The above four libraries can reside on the company file server or on the teammembers computer.

For best performance we suggest the following library storing strategy: Archicad Library and Office Standard libraries are installed on every users

computer by default. Libraries are stored in container file format (LCF) andusers not allowed to modify them. Only the CAD managers have the rights toupdate them.

Project Specific libraries are stored on the company file server. The library isnot compressed and project team members can freely edit its content.

The location of third party libraries depends on how often they are used.Regularly used objects should be installed on the users computer while theothers can be stored on the company file server.

9 .3 A r ch i v i n g a n d D a t a Sa f et yIt is also the CAD managers responsibility to develop the standards for: Proper use of the Archicad archive file (pla) Location of Autosave and backup files Backup and Autosave times

1 0 Case St u d ies

The following case-studies illustrate that entirely different Archicad workflows canbeen adopted successfully in many large offices. The key to success is that theselected approach should be adequate for the project type and the office

organization.

1 0.1 Cam p us Bu il d in gs / Or cu t t W in slow

P ar t ne rsh i p

1 0 .1 .1 Ab ou t t h e Com pan y

Orcu t t W i n s l o w Pa r tn e rsh i p (http://www.owp.com/) is located in Phoenix Arizona.This prestigious architectural design firm has more then 30 years of history. OWPwas recently designated as one of the best managed architectural firms in the UnitedStates by Architectural Record magazine. The companys main profile is designing

campus type buildings (large high schools, hospitals). By the time this document waswritten the office was entirely using AC9 on MAC computers, thus they had noexperiences with AC10.


27/31

27

1 0 .1 .2 Pr o j ect Det a i l s

OWP was working on two campus projects at the time of the interview. One was a51000 sqf school building and the other one was also an educational complex with 4buildings and a total of 94000 sqf floor area. Campus buildings are typically not morethen 4-5 stories high thus the number of floors or the size of one building is notcritical. More important is that the final construction documentation has to containthe complete documentation of each building. The complex hierarchy of drawing andthe large number of layouts in the in the final layoutbook makes the documentationthe most complicated part of the project

1 0 .1 .3 Use o f Plo t Mak er

In most of their projects OWP reached the limits of live hotlinks in PlotMaker 9.Therefore they do not work with live hotlinks, but separate PMK files instead. Theyfound that the most critical bottleneck of PM lies in the slow updating of hotlinks withbackground Archicad. The integrated layouting features of AC10 brought significantchanges in this field so OWP is looking forward to test it on its projects.

They usually work out 3 layout books for a typical project. They begin with one thatcontains sketches, then progress with a new one for schematic design and finallymake a separate one for design development. The design development layout bookis then converted into the construction documentation layout book.

Because OWP mostly designs campus type buildings and have many building files,they do not use the auto numbering feature of PlotMaker.


28/31

28

1 0 .1 .4 Use o f Team W or k

The largest buildings they design is around 4-5 storey ones so this is not a criticalfactor for them. They work with TeamWork files not more the 100 MB. They foundthat this is the upper limit that TeamWork can handle smoothly. If they exceed thisfile size then they often take the project apart by stories as separate PLP files.

They share the model by layers and have separate layer sets for interior designteam. Most of the time only 1 or 2 architects are responsible for the design and theyget help for CD-s and interior designs at the CD stage.

Once they had a large Patient tower hospital building where they had 10 peopleworking together on a single PLP file. This project required a full time CAD managerthat worked only as an administrator for the teamwork model.

They are committed to Teamwork; only the interior team prefers using hotlinkmodules for team working. Now they have a habit of saving plc files and send andreceive only once or twice a day. Some of the office even signs in from home overthe internet even though it takes around 20 minutes.

1 0 .1 .5 Use o f Ho t li n k ed Mod u les

As OWP typically designs campus type buildings, they often hotlink the differentbuilding model files into the site plan file. Interior team use hotlink modules mostlyfor repetitive or standard elements.

The picture below shows the Willie and Coy Payne Junior High School in GilbertArizona. The following collaboration and coordination techniques were used duringthe design:

Civil (dwg) site information was linked to Archicad site plan via x-referencing Teamwork was used on individual building files to share each building model

3D building were linked (hotlinked) to site for consistency All views of all buildings were linked to layout book for automatic

documentation


29/31

29

1 0 .1 .6 Use o f Tem plat es

OWP created an extensive template set for their practice. They have dedicatedtemplate files for:

new building remodel (for refurbishments) site plans tenant improvements general notes (sheet index, consultant names and all the project admin info is

within this file)

1 0 .1 .7 Use o f Det a i l s

OWP have standard detail files where the details are kept in detail windows. As theyhave modified the details for the actual project, they create project specific details.

1 0 .1 .8 Use of Lib r ar ies

They were just in the process of changing the office library policy. They want to havethe:

Project libraries on the server Office library on the server Archicad library on local machines

1 0 .2 Of f i ces an d Ret a i l Un i t s / Jo hn Ro ber t so n

A rch i t ec t s

1 0 .2 .1 Ab ou t t h e Com pan yJo h n Ro b e r t so n Arch it e c t s (http://www.jra.co.uk/) is a London-basedarchitectural firm with about 45 professionally qualified and support staff. JRA hasworked on different types of projects including residential commercial design andurban planning. Many of their recent projects are new or refurbished office buildingsin the City of London.

1 0 .2 .2 Pr o j ect Det a i l s

Building type: Offices and retail units in the City of London. The scheme strips a1950s office back to its frame and extends the building, doubling its size.Area: 26 000 192 m2Cost: GBP 35 700 000

Client: Carlyle GroupContractor: ISG Interior Exterior

JRA is the design architect. The project now is in tender stage. It is a 2 stage majorworks contract. JRA is currently in production of all the tender documents for allpackages.


30/31

30

1 0 .2 .3 Th e Pr o j ect W or k f low

1 0 .2 .4 For Plan n in g :

JRA has been the design architect of this project from the start.John Robertson (main partner, not working with Archicad) with a design architect(working with Archicad) worked out the scheme for planning approval. 2 otheremployees helped in creating the final CAD documents for the planning application.

At this stage there was no teamworked model. There was a main 3D model file outof which all the plans, sections, elevations and 3D views were obtained.

1 0 .2 .5 For Ten der :

When they received the go ahead from the client to produce the tender documents,they created what they call a Base Model. (see the figure below). The Base Model ,which is a teamwork file, contains the main structure of the building (columns, slabs,main external walls, etc), but no 2D information. Only the most competentArchicad users work on this part of the project (about 2 persons) and access to thisis password protected. The main reason for this is to reduce errors to the mostimportant portion of the building, the structure.

The Base Model is then hotlinked into the so-called General Architectural Model (GA).The secondary 3D information (raised floors, false ceilings, partitions, etc) is addedtogether with all the necessary 2D info for the GA plans, sections and elevations thatderive directly from this model.Sections and elevations come directly from this main GA model file, are kept in thefile, but exploded to 2D and moved away from their original place by a certaindistance. Then they are elaborated with 2D details.


31/31

All other 2D information (soft floor finishes, screed layouts etc.) is made byhotlinking out of the GA Model to linked pln files. This keeps teamworking to aminimum and avoids bloating the size of the GA Model through the addition of 2Dinformation whist ensuring that the 2D information remains up to date.

Many other parts of the building (like entrance hall, core details etc) are kept as

separate pln files and are directly hotlinked into the GA Model file.

Final layout creation is done in PlotMaker. This project has a number of layout booksthat have direct links to views contained in the GA Model file.The main GA model file size is no ~ 50 MB-s. (what do they think on AC10 integratedlayouting)

This chart represents the current Archicad working method within JRA:

Documents

Arc Hi Cad Big Building Whitepaper