Big Building Whitepaper

8/8/2019 Big Building Whitepaper

1/31

1

Big Building Whitepaper


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 .................177.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 methods.................................................................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 P reface

The size and complexity of projects and other important factors, like short deadlinesor big project teams, can significantly influence the workflow of design anddocumentation in an architectural office. To find the most effective ArchiCADapproach for your practice requires experimenting and refining your workingmethods.

The main goal of this white paper is to provide a strategy for using ArchiCADeffectively on big projects. You will also find case studies in this document thatillustrate how ArchiCAD can be implemented successfully in large firms.

Furthermore it is important to note that the integrated layouting features ofArchiCAD 10 require the complete revision of the documentation workflow even inthose firms where ArchiCAD has been used successfully for a long time. We believe

that experienced ArchiCAD users will also find useful information in this document.

2 ChallengesWhat are the possible issues 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 Definition of Big BuildingsThere is no exact definition of what makes a building big, however we recommendthat the following project attributes are carefully assessed so that you can find thebest approach in ArchiCAD:

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 downregeneration times and in the worst case can freeze ArchiCAD. The limitation on 3Dpolygons depends on many factors including the computer memory, the graphic cardmemory and the type of active 3D window (internal engine, OpenGL, rendering,


5/31

5

section/elevation, etc.). For a detailed description of ArchiCADs memoryrequirements please read chapter 4.2.Generally speaking weve confirmed that more than 200.000 polygons produces abig model in 3D views, and you have to make sure that your computers hardwareconfiguration is suitable for the project. Projects with more then 2 million polygonscan be unacceptably slow in 3D and may cause ArchiCAD to freeze.

Please note that a large polygon count, or huge file size, does not necessarily mean abig building. In many projects a significant proportion of the 3D polygons aregenerated from library parts. The model of a room interior can easily contain asmany polygons as a multistory building if the room is furnished with very detailedGDL objects. Please read chapter 5.1.2 for advice on 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 confirm 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 all significantlyinfluence the file size.According to the feedback from large clients the maximum file size that ArchiCAD 9and earlier versions could handle easily was about 100-150 MB. If the project fileexceeded this size these firms usually divided them into smaller logical parts to avoidany performance drawbacks. They also found that files bigger then 250-300 MB wereslow to redraw in 2D and 3D views and in the case of TeamWork files the send andreceive time increased significantly.

The handling of large projects has improved substantially in ArchiCAD 10 due to thefollowing new program features:

1. File compression: ArchiCAD 10 can save the plan files in compressed formatresulting in less hard disk space being required for project file storage.

2. Integrated layouting: 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 is shortened significantly, especially with bigprojects. Furthermore the workflow of editing placed views on layouts is nowmuch smoother. Our tests have revealed 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 into ArchiCAD 10 the content of abig PlotMaker 9 file (about 150MB) and a large ArchiCAD 9 project file (about120 MB). We found that the size of the resulting AC10 plan file dropped to 70MB due to the file compression and the merging of the identical project

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

3. Scalable project setup handling multiple project files: The new userinterface provides a transparent overview of the hierarchal file structure withmultiple model and document files. You can see the structure of all currentlyrunning ArchiCAD files in all sessions of 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 on how to curb file size.The following project elements can extend the file size by 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 greatly increase the file size, and ifthere are too many auto rebuild drawings the update process for the entire layoutbook can be unacceptably slow. You also have to consider that managing 100+

drawings from one file is likely to be more complicated than if the drawings weredivided into multiple PLN files. User experience shows that for 50 -100 layouts itsworth separating 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 concepts for documentation in ArchiCAD 10please refer to the appropriate chapters in the ArchiCAD 10 Reference Guide and theMigration Guide.

3 .4 Te am Si ze

Sharing and coordinating the tasks between the project team members is one of themost challenging responsibilities for the project leader regardless of which CADsoftware is being used. Graphisofts TeamWork technology offers an effectivesolution this problem even though TeamWork has its limitations, mainly because ofthe send and receives times. If this process takes, lets say, 5 minutes for one teammember, it is evident that in the case of 10 team members sending and receivingchanges for the entire team would take almost an hour. In addition to that theproject leader has to regularly check and approve the changes made in theTeamWork file, which prevents the other team members signing in during the timethe project is being checked. On this basis a consensus among our TeamWork usersis that a maximum of5-6 users can work effectively on one TeamWork file. If youhave a bigger team we recommend you apply other working methods, like thehotlink-TeamWork combination suggested at chapter 7.3

3 .5 N o . o f st o r i e sDesigning high rise buildings in ArchiCAD creates the following issues:

many drawings need 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 recommend that projects with more then 20 storiesrequire special attention from the project leader and the CAD manager. In the caseof more the 50 stories its very likely you will have to divide the project by differentstories (e.g. basement levels, entrance level, typical floors, etc.) and make aseparate model file of the whole building for visualization purposes 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 big Size is critical Solutions

3D PolygonCount

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

Project File 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. of stories 20-40 100> 1. Make a separate modelof the whole building forvisualization containingonly the necessaryelements2. Split the project intosmaller parts (e.g.basement levels, typicalfloors etc.)

4 Hardware and Software Requirements

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 ArchiCAD Network Key Servers

Where 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 supports cross platform networks thus a Windows key

server can support MAC and Windows versions of ArchiCAD 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 File Servers

File servers are primarily used to store TeamWork files, company libraries, templatesor any other materials that are required for the daily operation of the firm. 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 does 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 ArchiCAD WorkstationsMost of the project architects 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 Rendering and Visualization Workstations

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 supportthem

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 a substantial amount of memory in ArchiCAD, theapplications responsiveness can drop significantly, thus making it 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 likelihood of these problems we stronglyrecommend you buy the maximum memory that ArchiCAD can handle, just in caseyou need to work with large projects (See below). The maximum memory thatArchiCAD can utilize depends on the Operating System and the available memoryslots on the computers motherboard.

4.2.1 Windows XP Professional

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 2GB of memory.

4.2.2 Windows XP P rofessional x64 Edition

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 of4GB 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 Issues

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 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 theArchiCAD model. One can easily draw a building on the floor plan and in the sectionwindows which 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 the 3D window especially when the entire model is

visible.If the model contains approximately 3-4 million polygons three dimensionalnavigation is impossible and the render projection outputs a blank image. Where themodel contains more than 4 million polygons, theres a high likelihood is that theapplication crashes thus preventing ArchiCAD from generating a 3D view of theentire model. These limits, of course, are highly dependent on the hardwareconfiguration, and other specific circumstances, so they cannot be determinedexactly.The conclusion is that for big buildings its essential to keep the models polygoncount in an acceptable range. The following chapters will give you useful tips for howyou can reduce the number of polygons within your projects.

5.1.1 The Polycount add-onPolycount is an ArchiCAD 10 goody add-on that helps to control the number of 3Dpolygons in ArchiCAD models. This tool can be used if the project size, or the limitedphysical memory of your computer, makes the 3D model size a critical factor in yourmodeling decisions. Polycount can display the number of 3D polygons grouped byelement types (walls, slabs doors, windows, objects etc.) and also their percentagecompared 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 include a 3D Detail Levelparameter with options for Detailed, Simpleand Offrepresentations. The SetLevel of Detailfunction allows you to toggle between these values.The Polycount add-on can be downloaded from the Graphisoft ArchiCAD 10 Goodies

website or by clicking on the Goodies link in the ArchiCAD 10 Help menu. Aftersuccessful installation the Polycount menu can be activated fromWindow/Palettes/Polycount.


11/31

11

The interface of the Polycount add-on

5.1.2 How to reduce the 3D model size?

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

1. Make layer combinations! 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 to external views,such 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 the marquee! Where you need to create a section, elevation orrendering of only a small part of the building (e.g. a room or a story) select itwith a marquee. This simple trick can speed up the navigation in 3D views

3. Turn OFF the 3D of unwanted objects! 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 elementsgenerate a considerable number of polygons in 3D. You can overcome this byturning off their 3D representation with the corresponding parameter on theobjects parameter list. Since all library parts in the ArchiCAD library have thesame parameter name for this function you can select multiple objects on thefloor plan and collectively turn off their 3D. You can also use the Set LODfunction of the Polycount add-on for this purpose.

4. Control the objects level of detail! Most library parts in the ArchiCADlibrary have a parameter for 3D detail level (simple, detailed, off) and curveresolution. Set these parameters to the minimum possible that is appropriatefor the required 3D view.

5. Avoid using memory intense library part options! Some optionalelements of ArchiCAD objects can generate a significant number of 3Dpolygons without producing noticeable differences on the final drawings. Usethe following parameters with care:

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. Check the model with Polycount! 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 for use inhigh end renderings instead of architectural visualizations.

To show the effect of different parameters the following table shows the polygoncount of some ArchiCAD library parts. Note that one detailed office chair object (ManHands in Pocket) generates as many polygons as 1066 walls! A further example thatunderlines the importance of polygon reduction is another office chair (Office Chair01) which with the default settings has 3759 polygons in 3D view - the equivalent of626 walls. Typically there are many instances when this type of object is placed in anoffice project.

Element Type 3D Polygon Count

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 Sections and Elevations

Another area to consider in 3D views is section/elevation and detail databasehandling. If a project file has a considerable number 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. Again the limitcannot be specified exactly because it also depends on the model complexity. As arule of thumb we can say that the number of section/elevation and detail windowsshould never exceed 200.The other consequence of having an excessive number of these views is the file sizebloat. Project files with extremely complex 3D models usually have a reasonablysmall file size (20-30 Mbytes) if the number of sections and details is limited, whilst asimilarly complex project file can easily exceed hundreds of megabytes if, forinstance, there are more than a hundred section and detail views.Large files also have a negative affect on the section-elevation rebuild time. Prior to

section-elevation generation ArchiCAD runs a pre-filter on the floor plan with theconsequence that an invisible 2D view is created. This process can be significantlyslower where the floor plan is big or contains slow to rebuild library parts.

5 .2 Ren der in gReducing the number of polygons with the techniques described above helps in twoways with 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 photo-rendered

window is that the latter calculates and displays cast shadows and light reflections.Any method that reduces the number of shadow castings or light reflecting surfaceswill result in 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.

Use texture mapping and the alpha channel effect instead of physical models.This trick can save precious rendering time for trees, vehicles, fences andother complex objects when needed in the photo rendered image.


14/31

14

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

Turn off shadow casting for brighter lights.

5 . 3 Floo r Plan Regene ra t i onDrawing on the floor plan also has its restrictions, but these are much harder todescribe than is the case with 3D views. While ArchiCAD is capable of manipulating500.000 visible elements on the floor plan, a more realistic number would be100.000 for an average construction plan. Although ArchiCAD will not crash or writeenormous files with more then 100.000 elements the responsiveness will beunacceptably slow even on the best performing hardware configurations. Note thatmore time will be taken to redraw the drawing if you zoom out from a smaller part ofthe project to the drawing extents. Also remember that the floor plan rebuild timeinfluences the speed of the section-elevation regeneration as described in chapter7.3.Please utilize the following advice:

1. Use layer combinations to control the content of the floor plan.

2. Use bitmap fill representations instead of vectorial fills. Unless you need toprint a drawing select the bitmap fill representations from the on-screen viewoptions dialog as it is regenerates faster then vectorial fills.

3. Avoid using symbol fills. Symbol fills can greatly 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. Theserequire 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 Setting up the Project 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 pointers to consider for project team set up: How many projects run in 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 generic answers to these questions. Moreover theorganizational hierarchy within the office can dynamically change during the lifecycleof a project thus there is only limited value in establishing strict rules. Based uponfeedback from our users we suggest the following:

Invest in a full time CAD Manager if more then 15-20 architects are workingin the office


15/31

15

Even with 5-15 architects it is recommended that a part time CAD Manager,from the project team, is appointed.

The CAD Manager (in collaboration with the IT Manager and the ProjectLeaders) should develop a book of office standards.

As mentioned previously a maximum of5-6 users can work effectively onone TeamWork file, consequently this should be an important factor when

setting 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 largeoffice. In these examples, there are two independent project teams with 2 architectsand 2 draftsmen working in each. The leader of the first team also serves as a parttime CAD Manager in the office. Due to the relatively small firm size and thegenerally limited-size projects, informal communication is sufficient to handle projectcoordination 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 take on the responsibilities on a

part-time basis, which naturally decreases their productivity.

Mid-size architectural office (10-15 employees)

6 .2 La r g e Of f i ceThe large architectural office shown in the next figure is subdivided into 4 teams. Thefirst two are working on a large project therefore their tasks are coordinated by aproject director. The project director and the leaders of the other two project teamsreport to the Design Director. In this example a full time IT and CAD Manager assistthe project teams. The biggest challenge for these firms is to automate the sharing

Principal(s)

Project Leader 2 Office Administration

Project Architect 1Project Architect 2

Draftsman 1

Project Architect 1Project Architect 2

Draftsman 1

Project 1 Project 2


16/31

16

of large projects and to ensure the adoption of office standards across the wholeoffice team.

Large architectural office (30-50 employees)

7 The Modeling and DocumentationWorkflow

The single file concept of ArchiCAD is well proven in small firms with small tomedium sized projects. Larger firms with larger projects have to divide projects into

Principal(s)

DesignDirector

ITManager

CADManager

OfficeAdministr

ProjectDirector

ProjectLeader

ProjectLeader

DesignTeam

ProjectLeader

ProjectLeader

ProjectArchitects

Project

Architects

ProjectArchitects

Visualization Team


17/31

17

several files for many practical reasons. Those reasons include performancedrawbacks of the single file method and workflow bottlenecks where multiple usersare working with one file. ArchiCAD 10 supports different scale projects by providinga transparent method of handling multiple sessions and views to this completecollection of files. Basically there are three typical workflows in ArchiCAD 10, whichcan be combined depending on the actual project:

7 . 1 Sm a l l Pro j ect s Sing le 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 exploit fully the advantages of thevirtual building concept such as easy file management, automatic drawingupdates and listings. However above a certain project size and complexity theArchiCAD 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 can

be handled smoothly in one project file. For more details please read chapter3.2.

The ArchiCAD single file concept

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

LAYOUTBOOK

VirtualBuilding

Database

Floor plans

Sections

Details

3D views

Schedules

Layout

Layout

Layout

Layout

Layout

ARCHICAD PROJECT FILE (PLN)


18/31

18

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 toallow two teams (e.g. a modeling team and a documentation team) to worksimultaneously on one project. As we have noted earlier where the project containsmore then 100 layouts you are advised 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 the case of very big and complex buildings a combination of different file sharingmethods is needed that are 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 TeamWorkfiles were created (one for each tower) that served as the basis of the constructiondocumentation. The TeamWork files refer to external hotlinked modules and Xrefssuch as column grids, land surveys and other consultant drawings. Thedocumentation is stored in two layoutbook files in order reduce the size of the

TeamWork projects and to allow the project documentation team to work in 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

XREF(dw

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 Sharing the ProjectCollaboration is essential for making the project team function effectively andmoving projects forward as quickly as possible. Effective collaboration and projectsharing techniques are able to adapt to the project team size and the officeorganization. ArchiCAD offers various solutions for project sharing that can be used

alone or in combination.

8 .1 1 . Te am 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 that a central project file is shared amongst teammembers. Team members can reserve their own workspaces by applying restrictionsto particular areas, stories, and/or layers: as a result, each ArchiCAD element will

have an owner with the exclusive right to modify it.

The TeamWork conceptAdvantages:

Team members roles are clearly defined Team members can continuously check the work of other members No conflicts can occur in the architects workspace The TeamWork file is always up to date

Limitations Send and receive can be slow in the 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 office hours)

The maximum number of concurrent TeamWork users is limited by the sendand receive times (Typically 5-6 architects can work effectively on oneproject)

Suggested UsageTeamWork should be your primary method for sharing the content of the virtualbuilding. For 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 host

reflect all modifications made to the source files.

Hotlinked Modules, for example, can be used to manage the repetitive structures ofbuildings, such as hotels or offices, which have 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 can't be updated as long as the referred to source file isabsent. However this also means that using hotlink modules doesnt reduce the sizeof the master project


22/31

22

The Hotlink 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/DXFdrawings into the ArchiCAD project. External DWG/DXF drawings will be

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

automatically updated in the ArchiCAD project if they are referenced as an Xref. Notethat Xrefs can also be located on an internal or ftp server.

The Xref concept

Advantages: External DWG/DXF files can easily brought into the project Repetitive DWG/DXF files 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 have 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 o cu m e n t a t i o n Se p ar a t e d f r o m t h e Mo d e l Fi l eThe 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. ArchiCAD 10 fully supports thisworkflow since you can control complex file hierarchies in the new Navigator

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

dialogue. There are two strategic ways of separating the documentation from themodel.

8.4.1 Master fi le Method

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 Complex and Distributed methods

For very complex or large projects usually there isnt a master file that contains allthe drawings due to size and speed issues. Consequently the building model is storedin multiple project files (some of them can be TeamWork files; others can be simpleArchiCAD project files that refer to hotlinked modules). There are two ways to importthe 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 do notfollow automatically the changes in the model file. 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 the 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 the case of a very complex building the documentation filecan also be subdivided into two or more parts for easier drawingmanagement. See the 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. Where complex documentation structures are used inthe office it is crucial that the CAD Manager/project leader develops the proposed file

DOCUMENTATION (PLN)MODEL FILE (PLN)

VirtualBuildingDatabas

LAYOUTBOOK

Manualupdate


25/31

25

hierarchy and publishes this to the project team members prior the constructiondocumentation phase being started.

9 Company Standards

Well documented company standards are essential for running a large officesuccessfully. It is even more crucial for a large building where typically big projectteams are working on the same project file. It is primarily the CAD Managersresponsibility to develop and maintain the office CAD standards. Below is 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 a crucial part of ArchiCAD projects. In a typical architectural firm fourtypes of libraries are used:

1. ArchiCAD Library is the most current version of the ArchiCAD object libraryor in some cases just a subset of it. The subset library contains only those

elements of the standard ArchiCAD library that are regularly used in the firm.2. Office Standard Library is a collection of those objects that have been

developed to meet the office requirements. This library typically includesannotation elements (e.g. markers, labels, drawing frames etc.) and 3Dobjects (e.g. doors, windows, curtain walls etc.).

3. Project Specific Libraries consists of custom elements that have beendeveloped specifically for this project. Most of these objects are created bythe project team members.


26/31

26

4. A number ofThird Party Libraries that can be found on the Internet withuseful objects that are not present in the ArchiCAD library.

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

For the best performance we suggest the following strategy for library storage: 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 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

10 Case Studies

The following case-studies illustrate that entirely different ArchiCAD workflows canbeen adopted successfully in large offices. The key to success is that the selectedapproach should be suitable for the project type and the office organization.

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

P ar t ne rsh ip

10.1.1 About the Company

Orcutt Winslow Partnership (http://www.owp.com/) is located in Phoenix Arizona.This prestigious architectural design firm is more than 30 years old. OWP wasrecently recognized by Architectural Record magazine as one of the best managedarchitectural firms in the United States. The companys main focus is designingcampus type buildings (large high schools, hospitals). At the time of writing the OWP

office was using ArchiCAD 9 on MAC computers so they had no experience withArchiCAD 10.


27/31

27

10.1.2 Project DetailsOWP was working on two campus projects at the time of the interview. One was a51,000 sq ft school building and the other was also an educational complex with 4buildings and a total of 94,000 sq ft floor area. Typically campus buildings are notmore then 4-5 stories high thus the number of floors or the size of any one buildingis not critical. More important is that the final construction documentation has tocontain the complete documentation of each building. The complex hierarchy ofdrawings and the large number of layouts in the final layoutbook makes thedocumentation the most complicated part of the project

10.1.3 Use of P lotMaker

In most of their projects OWP reach the limits of live hotlinks in PlotMaker 9.Therefore they do not work with live hotlinks, but with separate PMK files instead.They found that the most critical bottleneck of PlotMaker was in the slow updating ofhotlinks with background ArchiCAD. The integrated layouting features of ArchiCAD 10have brought significant advances to resolve this issue and OWP is looking forward totesting these on its projects.

They usually work out 3 layout books for a typical project. The first book containssketches, the second book is for schematic design and the third book is for designdevelopment. The design development layout book is then converted into theconstruction 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

10.1.4 Use of TeamWork

The largest buildings they design are around 4-5 stories so size is not a critical factorfor them. They work with TeamWork files that are less than 100 MB. Theyve 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 the interior designteam. Most of the time only 1 or 2 architects are responsible for the design and theyget help for the construction documentation stage.

One example is 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.

OWP are committed to TeamWork and only the interior team prefers to use hotlinkmodules for team working. Now they have a habit of saving plc files and sending and

receiving only once or twice a day. Some of the office signs in from home over theinternet even though it takes around 20 minutes.

10.1.5 Use of Hotlinked Modules

As OWP typically designs campus type buildings, they often hotlink the differentbuilding model files into the site plan file. The Interior team use hotlink modulesmostly for 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 buildings were linked (hotlinked) to site for consistency All views of all buildings were linked to the layout book for automatic

documentation


29/31


30/31

30

10.2.3 The Project W orkflow

10.2.4 For P lanning:

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.

10.2.5 For Tender:

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 accomplished 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 was done in PlotMaker. This project has a number of layoutbooks that have direct links to views contained in the GA Model file.The main GA model file size is less than 50 MBs.

This chart represents the current ArchiCAD working method within JRA:

Documents

Big Building Whitepaper