ARCHICAD+BIM+Implementation+Guide+2015

Prévia do material em texto

BIM Implementation Guide 
 
 
 
 
ARCHICAD BIM Implementation Guide 
 
3rd Updated Edition 
 
 
 
 
 
 
 
 
 
 
 
GRAPHISOFT Registered Consultant and GRAPHISOFT Partner Confidential! 
 
 
 
Created by GRAPHISOFT 
Special thanks to everyone, who contributed to the content of this book. 
 
 
 
2 
 
BIM Implementation Guide Page 2 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
GRAPHISOFT 
Visit the GRAPHISOFT website at http://www.GRAPHISOFT.com for 
local distributor and product availability information. 
BIM Implementation Guide 
(International English Version) 
Copyright © 2015 by GRAPHISOFT, all rights reserved. Reproduction, paraphrasing or translation 
without express prior written permission is strictly prohibited. 
Trademarks 
ARCHICAD® is a registered trademark of GRAPHISOFT. 
All other trademarks are the property of their respective holders. 
Credits 
Courtesy of GRAPHISOFT 
 
 
http://www.graphisoft.com/
 
 
3 
 
BIM Implementation Guide Page 3 
 
Table of Contents 
 
Chapter 1 - Introduction .......................................................................................... 8 
Chapter 2 - Preparations ......................................................................................... 9 
BIM Implementation Strategy ..................................................................................................................................................................................................... 9 
Office Evaluation .......................................................................................................................................................................................................................10 
BIM Implementation Plan ...........................................................................................................................................................................................................11 
Chapter 3 - The Pilot Project ................................................................................. 12 
Type of Project ...............................................................................................................................................................................................................................12 
Management Commitment .......................................................................................................................................................................................................12 
Project Team ...................................................................................................................................................................................................................................12 
Potential Project Risks .................................................................................................................................................................................................................12 
Chapter 4 - Human Resources ............................................................................... 14 
Structure of the Teams ................................................................................................................................................................................................................14 
Typical Structure of a Large Practice ..................................................................................................................................................................................14 
Roles and Responsibilities ..........................................................................................................................................................................................................15 
Setting up the Project Team ......................................................................................................................................................................................................16 
Chapter 5 - Project Setup ....................................................................................... 18 
Project Templates .........................................................................................................................................................................................................................20 
Project Template Strategies ..................................................................................................................................................................................................21 
Content of the Project Template File .................................................................................................................................................................................22 
Starting to Create Your Own Custom Project Template ..............................................................................................................................................23 
Naming and Path ......................................................................................................................................................................................................................24 
Project Structure (Navigator, Organizer) ...........................................................................................................................................................................25 
Story Settings .................................................................................................................................................................................................................................34 
Element Attributes........................................................................................................................................................................................................................34 
Building Materials .....................................................................................................................................................................................................................36 
Layers ............................................................................................................................................................................................................................................37 
Layer Combinations .................................................................................................................................................................................................................40 
Layers vs. Layer Combinations .............................................................................................................................................................................................41 
Pens and Pen Sets .....................................................................................................................................................................................................................42 
Line Types ....................................................................................................................................................................................................................................45 
 
 
4 
 
BIM Implementation Guide Page 4 
Fill types .......................................................................................................................................................................................................................................47 
Surfaces ........................................................................................................................................................................................................................................48 
Renovation Styles ......................................................................................................................................................................................................................50Attribute Management ...........................................................................................................................................................................................................50 
Favorites .......................................................................................................................................................................................................................................50 
DXF-DWG Translators ..............................................................................................................................................................................................................53 
IFC Translators ............................................................................................................................................................................................................................54 
Libraries ............................................................................................................................................................................................................................................55 
Attributes and Third Party Libraries ....................................................................................................................................................................................56 
Converting Symbol Libraries .................................................................................................................................................................................................56 
Object Catalog ...........................................................................................................................................................................................................................56 
Most Common Library Types ................................................................................................................................................................................................56 
Project Template Tricks ...............................................................................................................................................................................................................60 
Basic Attributes In tpl, Extended Attribute Set In .aat ..................................................................................................................................................60 
2D Favorites and Pen Set Descriptions On Worksheet .................................................................................................................................................60 
Layout Title Blocks And Legends On Worksheets ..........................................................................................................................................................61 
Chapter 6 - Project Workflows .............................................................................. 63 
Project Lifecycle .............................................................................................................................................................................................................................63 
Creating the Design Model ........................................................................................................................................................................................................63 
Schematic Design .....................................................................................................................................................................................................................63 
Design Development ...............................................................................................................................................................................................................65 
Construction Documentation ...............................................................................................................................................................................................65 
As Built Model ............................................................................................................................................................................................................................66 
Sharing the work ...........................................................................................................................................................................................................................66 
Small Projects --- Single File Concept ..................................................................................................................................................................................66 
Medium Size Projects --- Model File and Document File Separated .........................................................................................................................67 
Big Projects --- Hierarchal File Structure .............................................................................................................................................................................69 
Teamwork ........................................................................................................................................................................................................................................69 
Evaluation of the Teamwork 2.0 Technology ..................................................................................................................................................................70 
Hotlink Modules ............................................................................................................................................................................................................................72 
XREF ...................................................................................................................................................................................................................................................74 
Combined workflow ....................................................................................................................................................................................................................76 
Documentation Separated from the Model File .............................................................................................................................................................76 
Master File Method ...................................................................................................................................................................................................................76 
 
 
5 
 
BIM Implementation Guide Page 5 
Complex and Distributed Methods ....................................................................................................................................................................................76 
Coordination ...................................................................................................................................................................................................................................76 
DXF-DWG .....................................................................................................................................................................................................................................78 
IFC ...................................................................................................................................................................................................................................................80 
Structural Design, Analysis and Production .....................................................................................................................................................................81Energy Analysis ..........................................................................................................................................................................................................................84 
Chapter 7 - Project Management .......................................................................... 87 
Folder Hierarchy ............................................................................................................................................................................................................................87 
IT Infrastructure .............................................................................................................................................................................................................................88 
Suggested Configuration .......................................................................................................................................................................................................90 
ARCHICAD Network Key Servers ..........................................................................................................................................................................................90 
File Servers...................................................................................................................................................................................................................................90 
ARCHICAD Workstations.........................................................................................................................................................................................................91 
Rendering and Visualization Workstations ......................................................................................................................................................................91 
BIM Server ....................................................................................................................................................................................................................................91 
Network requirements ............................................................................................................................................................................................................92 
Memory Requirements............................................................................................................................................................................................................92 
Data Safety ......................................................................................................................................................................................................................................92 
Saving ............................................................................................................................................................................................................................................92 
Printing and Plotting ....................................................................................................................................................................................................................96 
Updates & upgrades .....................................................................................................................................................................................................................96 
ARCHICAD Updates ..................................................................................................................................................................................................................96 
Library Hotfixes ..........................................................................................................................................................................................................................97 
Project migration ..........................................................................................................................................................................................................................97 
Chapter 8 - Best Practices ...................................................................................... 99 
Modeling Strategies .....................................................................................................................................................................................................................99 
Large Projects .................................................................................................................................................................................................................................99 
Polygon Count ........................................................................................................................................................................................................................ 100 
Project File Size ....................................................................................................................................................................................................................... 100 
Layout Book Size .................................................................................................................................................................................................................... 101 
Team Size ............................................................................................................................................................................ Error! Bookmark not defined. 
Number of Stories .................................................................................................................................................................................................................. 101 
Summary ................................................................................................................................................................................................................................... 101 
Hardware requirements ....................................................................................................................................................................................................... 102 
 
 
6 
 
BIM Implementation Guide Page 6 
Speed Issues ................................................................................................................................................................................................................................. 102 
3D Rebuild and Navigation ................................................................................................................................................................................................. 102 
The PolyCount add-on ......................................................................................................................................................................................................... 103 
How to Reduce the 3D Model Size ................................................................................................................................................................................... 104 
Sections and Elevations ....................................................................................................................................................................................................... 107 
Rendering ................................................................................................................................................................................................................................. 108 
Floor Plan Regeneration...................................................................................................................................................................................................... 109 
Lines/Arcs coming from DXF/DWG Files ........................................................................................................................................................................ 111 
Morphs and Shells.................................................................................................................................................................................................................. 111 
Curtain Walls ............................................................................................................................................................................................................................ 111 
Embedded Groups ................................................................................................................................................................................................................. 111 
GDL Objects ............................................................................................................................................................................................................................. 111 
API Add-Ons ............................................................................................................................................................................................................................. 112 
Project Sharing Strategies ....................................................................................................................................................................................................... 112 
Example 1 ................................................................................................................................................................................................................................. 112 
Example 2 ................................................................................................................................................................................................................................. 113 
Managing Design Options ...................................................................................................................................................................................................... 114 
Design Options in the Main File ........................................................................................................................................................................................ 114 
Design Options in External File ......................................................................................................................................................................................... 115 
The Teamwork approach ..................................................................................................................................................................................................... 116 
Creating Custom ARCHICAD Installers ............................................................................................................................................................................... 116 
Cleaning ARCHICAD Preferences .......................................................................................................................................................................................... 116 
Enabling the ARCHICAD Special Menu ............................................................................................................................................................................... 116 
Crash Detection and Troubleshooting ............................................................................................................................................................................... 116 
Chapter 9 - Appendix ........................................................................................... 117 
GRAPHISOFT Websites ............................................................................................................................................................................................................. 117 
ARCHICAD Forums ..................................................................................................................................................................................................................... 117 
ARCHICAD Knowledgebase .................................................................................................................................................................................................... 117 
ARCHICAD Training Materials ................................................................................................................................................................................................ 117 
3rd Party Products ....................................................................................................................................................................................................................... 117 
ARCHICAD Blogs ......................................................................................................................................................................................................................... 117 
ARCHICAD Links ......................................................................................................................................................................................................................... 118 
GDL Libraries................................................................................................................................................................................................................................ 118 
Free ............................................................................................................................................................................................................................................. 118 
 
 
7 
 
BIM Implementation Guide Page 7 
Commercial .............................................................................................................................................................................................................................. 118 
For GDL Developers .............................................................................................................................................................................................................. 118 
Books about ARCHICAD ........................................................................................................................................................................................................... 118 
Books about BIM ......................................................................................................................................................................................................................... 119 
Online Cad Magazines .............................................................................................................................................................................................................. 119 
Office Evaluation Questionnaire Sample ........................................................................................................................................................................... 120 
 
 
 
 
8 
 
BIM Implementation Guide Page 8 
Chapter 1 - Introduction 
 
This document was created to provide help for the architectural offices considering the implementation of ARCHICAD-based 
Building Information Modeling (BIM)workflow. We would like to ease the migration process by discussing issues necessary to 
consider in the project-planning phase of BIM projects. The book also covers the most important topics that are mission critical in 
forming the best workflow for the given project in the given practice. 
Since architectural practices and the projects vary widely, this document only lists issues to consider and offers strategies to solve 
them, rather than suggesting a single ‘best solution’. This document is not a feature training material; thus, feature-level knowledge 
of ARCHICAD is necessary to understand the concepts described here. 
Each chapter starts with a problem description and its implications. Next, strategies to solve the problem are explained with 
recommendations for different situations. Where appropriate, we finish with relevant project examples. 
 
 
9 
 
BIM Implementation Guide Page 9 
Chapter 2 - Preparations 
 
Successful transition to BIM requires careful preparations and well-defined implementation strategies. It is important that the entire 
organization is involved in this process so that all members of the staff can contribute and understand the goals of the 
migration. 
BIM Implementation Strategy 
Having a roadmap for the implementation of ARCHICAD can ease the transition process from 2D CAD to BIM. The following or similar 
strategies have been proofed to be successful in many large firms. 
1 Form the BIM Implementation Team involving representatives of the management team, CAD managers, team leaders 
and other key stakeholders. 
2 Appoint the responsible person for managing the BIM transition process. Typically this role belongs to the BIM Manager 
or an external BIM consultant. 
3 The appointed BIM Implementation Manager thoroughly evaluates the office focusing on the following main areas: 
office structure, current workflow, adopted CAD standards, human resources and future expectations about BIM. [See 
Chapter 2 for more details.] 
4 The results are documented in the office Evaluation Document and published for the BIM Implementation Team. 
5 Based on the findings, the BIM Manager creates the detailed BIM Implementation Plan for management approval. 
6 The BIM pilot project is selected; the members of pilot project team are appointed and trained for advanced ARCHICAD 
usage. 
7 The BIM Manager creates the first draft of the office BIM Manual and the prototype of the office BIM Template. 
8 The BIM Manager and the responsible Team Leader set up the pilot project environment and prepare the pilot project 
plan. 
9 The pilot project is carried out with the close assistance and support of the BIM Manager. 
10 The BIM Implementation Team thoroughly evaluates the results of the pilot project. 
11 The office BIM Manual and the office BIM templates are updated. 
12 Project teams are gradually migrated to the new BIM workflow. This process involves the project staff’s ARCHICAD 
training and the education of the office BIM standards. 
13 The office BIM workflow, BIM Manual and BIM standards are regularly reviewed and fine-tuned by the BIM 
Implementation Team. The changes are documented and published for the project team members. 
 
 
10 
 
BIM Implementation Guide Page 10 
Office Evaluation 
The first step in implementing the new workflow should always be the thorough evaluation of the office. Typically the company’s 
CAD/BIM Manager or an external BIM consultant is in charge of this process. The results of the interviews and questioners should be 
documented in the office evaluation document. This book describes the firm’s current operations and at the same time discloses 
the expectations of the office staff. The key elements of the office evaluation document are the following: 
Visions and goals 
 Company vision 
 Expected benefits of BIM 
 Concerns about the new workflow 
 BIM implementation roadmap 
Human Resources 
 Current office team structure 
 Current project staff skills 
 Required skills and trainings 
 Personal concerns and gains 
Project Workflow 
 Project input sources 
 Project phases and deliverables 
 Project team setup and team collaboration 
 Coordination with the consultants 
 Issues/problems with the current (2D) workflow 
Office Standards 
 Current office CAD standards and regulations 
 Current office templates and the underlying concepts 
 Requirements of the new BIM standard 
Pilot Project 
 Potential BIM pilot projects in the office 
 Timeline and major milestones 
 Available resources 
 Evaluation criteria of the project’s success 
 Note: It is recommended to prepare an office evaluation questionnaire and have it filled out with the key stakeholders of the 
migration process including principals, CAD Managers, Team Leaders and the representatives of the project teams. [A sample 
questionnaire is available in Appendix.] 
 
 
 
11 
 
BIM Implementation Guide Page 11 
BIM Implementation Plan 
The office evaluation document must be carefully studied by the key stakeholders of BIM implementation team and based upon 
their findings a detailed BIM implementation plan has to be developed by the BIM manager. The plan must be explicit about the 
expected benefits and should cover potential risk factors as well as recommendations for managing those risks. 
The key questions to be answered in this document are the following: 
 Who will be ultimately responsible for managing the transition and running the pilot projects? 
 What are the major milestones of the BIM implementation process? 
 What are the major roles and responsibilities of the key project participants? 
 What is the resource pool that can be used to staff the project team? 
 What are the training requirements (if any) for the members of the project team? 
 Which project is selected for the pilot and for what reasons? 
 What are the main deadlines and related deliverables of the pilot project? 
 When are the main checkpoints and what criteria are used to measure progress of the project? 
 What will be the main project structure and project sharing strategy? 
 Who is involved in the project collaboration and communication (internal/external) and what will be the main 
communication channels? 
 How will the transition process be evaluated? 
Information provided in later chapters of this document will help you find the right answers to these questions. 
 
 
 
12 
 
BIM Implementation Guide Page 12 
Chapter 3 - The Pilot Project 
The most efficient way to learn and implement ARCHICAD is to start and complete a new project with it. The features of the 
software are easiest to explore parallel with the development of a project, starting with site assessment and schematics followed by 
design development, project documentation and detail drawings. 
Type of Project 
Choosing the appropriate pilot project is one of the most important factors for implementing the new model-based workflow. 
The key consideration in choosing a pilot project is the following: 
 Size and complexity 
 Deadlines and deliverables 
 Available human resources 
 Project budget 
 Business importance 
 Note: The most important criterion is that the pilot is representative of the scale and nature of the typical projects of the 
practice. 
Management Commitment 
A senior person (partner) should be the pilot ‘champion’, who ensures that the appropriate evaluation criteria are applied, 
organizational and process problems are resolved, and the rest of the senior management is kept informed to prevent derailment 
of the pilot. 
Project Team 
The pilot team will be the first group in the firm to be trained on the new software and will be a great resource for their colleagues in 
the later stages of implementation. The team charged with starting the pilot must be enthusiastic about BIM and at least one 
team member must be an established and proficient user of the software. Theirimpressions during the pilot project evaluation 
have a big impact on how the firm will perceive the software. 
Potential Project Risks 
The following circumstances seriously endanger the success of the BIM pilot projects. With careful preparations and close 
management support these risks can be minimized. 
 Lack of communication about the project objectives and benefits. 
 The project has already been started using the old workflow. 
 There is not enough time for preparation work. 
 The project has a tight schedule in terms of interim and final deadlines. 
 There is too much pressure on the team because of the project’s business importance. 
 
 
13 
 
BIM Implementation Guide Page 13 
 The project is not supported with an appropriate budget. 
 The complexity or the scale of the project exceeds the capabilities of the pilot project team. 
 
 
14 
 
BIM Implementation Guide Page 14 
Chapter 4 - Human Resources 
Implementing BIM has many implications in the office organization, since new roles are being created while previous ones are 
changed which might result in tensions that the HR Department of the practice has to handle. 
Structure of the Teams 
Architectural practices employ different approaches for the setup of their team structures. This is essential information when 
planning the workflow and the project team of the pilot project. Each setup has advantages and disadvantages in the process of 
migrating to a fundamentally new workflow: 
 Architectural Studios --- operate as individual organizations within the company. 
 In this setup typically the technologically most advanced team will work on the pilot project. 
 Specialized Teams --- are most common in larger architectural practices. In these setups, the project is started by team ‘A’ and 
at a given point - usually when the conceptual design is finished -, transferred to team ‘B’ for detailed documentation. 
 Dynamic Teams --- are flexible groups that adjust to the project phases and requirements. 
 Note: Being a part of the pilot team should be perceived as a privilege; the selected individuals should feel that by 
leading this change they have profound responsibility for the overall success of the office. 
The applied project workflow determines not only the structure of the project teams but also the organizational hierarchy of the 
entire architectural office. Next we’ll highlight the structural differences in the organization of different sized firms. 
Typical Structure of a Large Practice 
The large architectural office workflows shown in the next figures present a typical workflow using the ‘2D CAD’ workflow and the 
‘BIM’ workflow. 
The large office structure using the BIM workflow is subdivided into three teams. The first two are working on a large project, and a 
Project Director coordinates their tasks. The Project Director and the leaders of the other two project teams report to the Design 
Director. In this example a full-time IT Manager and BIM Manager assist the project teams. 
The main differences between the two workflows are: 
 There is no need for a Documentation Team in the BIM workflow, since most of the construction documentation 
information is derived directly from the central design model. The project teams might have dedicated persons focusing on 
fine-tuning the documentation. 
 The BIM Manager has a more extensive and responsible role than the CAD Manager in the conventional workflow. 
 The BIM workflow does not include a stand-alone Visualization Team; the personnel responsible for this task is part of the 
design project teams. 
 
 
15 
 
BIM Implementation Guide Page 15 
 
Organizational chart using 2D CAD workflow (large office) 
 
Organizational chart using BIM workflow (large office) 
Roles and Responsibilities 
Success of the new model-based workflow greatly depends on the identification of the key roles and responsibilities of the 
project. The structure of the architectural design team largely depends on the profile of the firm and the preferred design workflow. 
The titles of the team members can also be very different from firm to firm. Some of these roles might not exist in medium or small 
size firms; many times the same person fulfills multiple roles. The following job descriptions are typical for large BIM-based firms. 
 Project Director (PD) - the architect or team member responsible for overall management of the project. The PD should 
understand the business benefits and opportunities of object model CAD, but is not necessarily familiar with the operation of 
the software. 
 Design Leader (DL) - the architect or designer responsible for creating the concept. This architect should understand the 
principles of the virtual building, and be able to work with the software, at least in broad terms. 
 
 
16 
 
BIM Implementation Guide Page 16 
 Team Leader (TL) --- a senior architect or team member responsible for the management of a designated part of the 
project. The team leader should have a good working knowledge of the model and understand the different resource 
implications of creating object models. 
 Model Manager (MM) - the person responsible for establishing and maintaining the project model and any possible 
associated document output. For a large project as envisaged in this discussion, the model manager, as an expert and highly 
experienced ARCHICAD user, is a key member of the team and essential to a successful project 
 Documentation Manager (DM) - the person responsible for the definition, output and management of project 
documents authored from the building model. The DM is an experienced architect or technician who understands in detail 
the needs of documentation and ARCHICAD and works closely with the PD and project leaders. 
 BIM Manager (BM) - the person responsible for setting model building guidelines and policy, supporting project teams 
and coordinating with other office experts (documentation, specifications, QA, etc.). The BIM manager is an expert in the 
technology and works with the senior office management on the office project IT systems and strategic direction. In smaller 
companies, the role of the BIM manager might coincide with the Model Manager and/or Documentation Manager. 
 Project Architects (PA) - Team members responsible for the design development and building of the model according to 
their particular roles. They have an in-depth working knowledge of all aspects of the software. 
 Project Technician (PT) --- Technical person skilled in object model usage, with an in-depth working knowledge of all 
aspects of the software and CAD documentation drafting. 
 
 
 
The organizational hierarchy of the previously described jobs in a large practice 
Setting up the Project Team 
After identifying the main team structure and the key roles, you must define the main project workflow before setting up the actual 
project team. The following are recommendations for setting up the human resources part of the pilot project. 
 Top management support is a necessity for the success of the project. Involve at least one of the partners/principals by 
sharing the detailed project plan and getting their approval for it. 
 Members of the project team must be enthusiastic about BIM and the new workflow. 
 
 
17 
 
BIM Implementation Guide Page 17 
 At least one team member must be an established and proficient user (champion) of the software. If there is no suitable 
person inside the firm, try to hire someone from outside. 
 The only universal recommendation in model-based workflows is that there should be full-time BIM or Model Manager 
dedicated to managing the BIM model and providing support to the ‘producing’ architects and engineers. 
The workload of the different project team members can change significantly during the lifecycle of the project as illustrated in 
the following chart. This has to be considered when planningthe human resource requirements of the BIM office. 
 
 
 
18 
 
BIM Implementation Guide Page 18 
Chapter 5 - Project Setup 
In a model-based workflow, project setup significantly exceeds the simple configuration of the 2D drawing standards for the project. 
In a BIM project, you must virtually replicate the real building with its physical and logical structure, within the computer 
environment. Intelligent project setup that supports the model-based project workflow is a prerequisite for the success of a 
BIM pilot project. 
 
BIM Workflow does not require the re-creation of design information --- ‘organic design development’ 
 
 
19 
 
BIM Implementation Guide Page 19 
 Note: The difference of the two workflows may have effects on project costs also. Usually, offices are paid at the end of 
project milestones, so the company has to be aware of internal efforts. 
 
Ideally, in the project setup phase, you define: 
 The skeleton (template) of your project, including its story structure and the main Navigator View Sets, Layers, Layer 
Combinations, the basic building-blocks you will work with, including Favorites for the building elements and intelligent 
parametric objects. (See detailed description in chapter 5.1 Project Templates) 
 The way the project is shared. 
 The main communication protocols you will use to communicate with the internal and external members of the project 
team and the client. The main structure of your documentation, including your Layout Book and your Publisher Sets. 
Before you start the actual project setup in the software application, you should have an answer to the following questions: 
 What are the deliverables of the project? 
 What types of materials are available to start the project with? 
 What are the drawing standards to be used? 
 What are the main design principles of the project? 
 What building materials and structures will be used? 
 At which project stage will the BIM implementation start? 
 What are the communication protocols with the consultants? 
In this chapter we will discuss these questions and offer different project setup strategies based upon the various possible scenarios. 
 
 
 
20 
 
BIM Implementation Guide Page 20 
Project Templates 
The project setup starts with creating the template file for the project. Project templates are predefined empty project files that 
contain all the necessary information for starting a new project. These templates may contain only some basic guidelines, or they 
may contain very detailed predefined company/state CAD standards. Special projects (e.g. healthcare, medical, etc.) also have 
specific compulsory standards that have to be collected and included in the project template. 
The following figure shows the project template’s effect on the project workload. It is easy to see and also calculate how many hours 
can one spare project by project with an appropriate template. Consider also, that without a good template usually the time to add 
new content for the next phase is exactly the same as to publish the deliverables of the current phase, which is the most stressful for 
the design team. 
 
The project template file has to meet the following criteria: 
 Appropriate for the given project type (size, usage, project sharing etc.) 
 Has to be approved by the project architect and the BIM Manager 
 Requires minimal further customization from the project team 
 Number of attributes is minimized 
 The most recent version is always available on a public server 
 Elements of the project template are carefully documented 
 Regularly maintained and updated by the BIM Manager 
 Content is documented and updated by the BIM Manager 
 
 
 
21 
 
BIM Implementation Guide Page 21 
Project Template Strategies 
Different architectural practices can have the following basic setups: 
 There is one company-level template used for every single project 
 There are several company-level templates, one for each main project type 
The BIM Manager may decide to have only one template for all projects or to create a series of individual template files for each of 
the different project types. The two solutions can be used in different cases. 
You can find useful template setting tips at the end of this section. 
Single Project Template File 
This solution is recommended if the architectural office specializes in one building type (e.g. hospitals or residential houses) and if 
one generic template can support most of the projects without further customization, 
Pros: 
 Easier management of the template file 
 Only one template has to be maintained 
 Less documentation needed 
 No risk of starting a new project from the wrong template 
Cons: 
 Too many attributes in the template file, since one template has to support many projects 
 Template file size can be bigger 
 Difficult to navigate among too many attributes 
 Not able to support different project types (other than the typical one) 
Multiple Project Template Files 
This option is best for multidisciplinary firms with different project types. Project templates can be differentiated by project types 
(residential/commercial), project size (single story-multi story) or project phases (SD, DD, and CD). 
Pros: 
 Template files are customized for the project type 
 The number of attributes is minimized 
Cons: 
 More template file management is needed 
 More documentation is required 
Commercial Template Files 
Purchasing predefined template solutions from third-party developers might be a good option for companies and individual users 
who do not want to create their own template from scratch and would prefer to use a proven solution instead. 
 
 
 
22 
 
BIM Implementation Guide Page 22 
 Content of the Project Template File 
In ARCHICAD a special file type called a template or TPL file is used for this purpose. When opening a TPL file to start a project, 
ARCHICAD makes an untitled copy with the same settings. When saving this project the first time, a prompt asks for a name and 
location for the project file, which prevents the users from accidentally overwriting the template file itself. The ARCHICAD template 
file includes the following elements: 
 Project structure (Navigator) 
• Project Map 
• View Map 
• Layout Book 
• Publisher Sets 
 Model View Options 
 Project Preferences 
 DXF/DWG Translators 
 Project Info 
 Tool default settings 
 Favorites 
 Attributes 
• Layers and Layer Combinations 
• Markup styles 
• Operation profiles 
• Pens and Pen Sets 
• Line Types 
• Fill Types 
• Building Materials 
• Surfaces 
• Zones 
• Profiles 
• Composites 
• Complex profiles 
 Renovation filters 
 Embedded library parts 
 
 
23 
 
BIM Implementation Guide Page 23 
These are, of course, dependent on each other. The following figure shows the most important dependencies. The order of 
definition has to be top to bottom. 
 
In addition to the project template file, company project standards may incorporate the following elements: 
 Work Environment sets 
 External Favorite files 
 Detail drawings (ARCHICAD, DXF-DWG or PDF formats) 
 ARCHICAD Module files 
 Company and project libraries 
 Company object libraries 
Starting to Create Your Own Custom Project Template 
Before we actually go into the detailed description of setting up a project there are some basic guidelines for your consideration: 
 As a first step, you should analyze the standards that are in place in the office. Try and distill the main concepts and 
directions instead of concentrating on the details. What you should be looking for is the level at which standardization is 
necessary in your office (e.g. whether there are strict rules to follow that will help your work by providing a clear framework 
for project setup; or - in contrast - non-standard project types or the leeway given to projectarchitects to create things in 
their own style will allow you to create an optimal project setup without predefined rules). 
 Once you fully understand the situation in the office, you should understand as much of your pilot project as possible. It is 
a good way to start backwards from the required deliverables and derive requirements for the project templates from 
what needs to be accomplished by the end. You should try and ‘model’ the physical deliverables in the project structure. 
This will give you a good idea about the requirements for the different viewpoints, Views, Layout Book elements and 
Publisher Sets. 
 The next step is to understand the actual design of the project to be able to set up the project attributes. In model-
based projects, intelligent building elements can be configured to a very high degree, making the whole process highly 
automated. When setting up the attributes of the pilot project, it is a good idea to completely remove the default settings 
 
 
24 
 
BIM Implementation Guide Page 24 
of the application and to try to include only the elements and attributes that will actually be used, so as to minimize 
the number of project attributes. 
 The last step is to setup the library structure. Libraries contain parametric objects that are used for more complex or custom 
building elements. ARCHICAD is shipped with an extensive default library of intelligent parametric GDL objects. However, 
most projects require the creation of additional, custom library content. The main consideration here is that libraries should 
be easily accessible to all project participants at any moment, yet should be maintained by a central authority (in most the 
cases, the BIM manager). 
Naming and Path 
Use descriptive name for the project and project templates that describes its main properties. Avoid using automatic names 
(Untitled1, Untitled2, etc.) or incidental names (e.g. final1, version3, yesterday, etc.). 
 
example on template naming 
 
 
 
25 
 
BIM Implementation Guide Page 25 
Create a complete file and folder structure for each project, so users can save and files the documents easily. This is important not 
only for ARCHICAD files, but also all project related documents. 
 
example on project folders 
Project Structure (Navigator, Organizer) 
One of the most powerful capabilities of ARCHICAD is that even very complex project structures and extensive documentation 
sets can be overviewed and controlled from the Navigator Palette. Moreover, the combined use of Navigator, Hotlink Manager, 
XREF Manager and Drawing Manager allows the Project Architect to continuously monitor the status of not only the main project file 
but also the external files linked into it. The Navigator serves several basic functions in the project workflow: 
 The Project Map allows navigation within the BIM model. 
 The View Map stores different views of the model organized by various categories. 
 The Layout Book gives access to the entire project documentation. 
 The Publisher Sets is the primary tool for communicating the BIM project data in printed and electronic format. 
 
Elements of the ARCHICAD Navigator Palette 
 
 
26 
 
BIM Implementation Guide Page 26 
 Note: Finding the right balance between strict office standards and flexible project structures is not easy, usually it requires 
the extensive evaluation of the application on several pilot projects. As a rule of thumb, the default Navigator structure 
should be kept as simple as possible; the Project Architect and BIM Manager can fine-tune it as the project evolves. 
Following is an overview of the Navigator components. 
Project Map 
The Project Map contains the basic structure of the project. The View Map, the Layout Book and ultimately the Publisher Sets are 
all based upon this structure. Since buildings differ in size and shape, the default Project Map cannot be used for starting new 
projects without further customization. 
Usually it’s the responsibility of the Project Architect to define the following elements in the project file: 
 Story Settings (story heights and names) 
 Default Elevations (the four main elevations are usually included in the default template) 
 Main Sections (further sections can be added later as the project evolves) 
 Worksheets (these are 2D documents used, for instance, to host the basic plans of the building plot) 
 Company-standard list templates (these are usually defined in the standard template file) 
 
 Note: The BIM Manager must regularly check the consistency of the Navigator structure and make sure that any modification 
in the Project Map is also reflected in the View Map and Publisher Sets. 
 
 
 
27 
 
BIM Implementation Guide Page 27 
View Map 
The View Map in the Project Navigator contains all the custom views you have saved from your project. Views are special 
representations of your model viewpoints. For instance, you have a floor plan of your first floor in the Project Map. Accessing this 
(the viewpoint) from the Project Map will always show you the floor plan according to the current view settings. However, you can 
save any number of views of your floor plan with different view settings such as zoom, scale, and layer settings. 
 
The Organizer allows the easy creation of Views from the Project Map viewpoints 
These views are stored and organized in the View Map. Opening one of these views from the View Map will show you the floor 
plan using the settings you saved in this view. 
Depending on your office requirements, views can be organized into a folder hierarchy by various categories: 
 Project phases (e.g. SD, DD, CD) 
 Disciplines (site, landscaping, structural, architectural, MEP etc.) 
 Scale (1:100, 1:50, 1/4’, 1/8’ etc.) 
 Design Options 
No matter what principles are used for the View Map organization, it is crucial that the views and folders are named and numbered 
according to strict and well-documented standards. 
 
 
28 
 
BIM Implementation Guide Page 28 
 Note: One possible view and view map folder naming strategy can be the following: 
Code of discipline-Scale-Drawing type-Project phase 
[A-100-Floor Plans-DD], meaning: Architectural, 1:100 scale, Floor Plans, Design Development 
It is highly recommended that the same numbering and naming convention is used for all parts of the Navigator, including the 
Project Map, View Map and Layout Book. 
 Note: Clone Folders. The clone folder feature allows the direct and automatic mirroring of all or parts of the Project Map 
structure in the View Map or the Layout Book. 
 
Pros: 
This feature can be used effectively to clone the content of certain folders of the Navigator. For instance, you can create a 
whole set of different scale floor plan views even before you know how many floors your building will have. If the View Map 
contains cloned folders of your floor plans, whenever you add a new floor plan it will be replicated automatically in 
all the clone folders with the appropriate view settings. This really makes the BIM workflow fast and efficient even in the 
documentation phase. 
Cons: 
We strongly recommend that you do not use the clone feature to clone entire documentation sets, especially in case of large 
design projects: 
 If a clone folder has to be identical to the original, use the original instead 
 There are always certain differences between the final documentation set and the view map. Designers use views dedicated 
for construction purposes as well as to store other project related geometry information, which should not be included in the 
final documentation set. Such issues and differences cannot be managed using the clone folders features 
View Settings 
Views can be used for various purposes; including the creation of working views where only a certain part of the building is visible, 
allowing you to focus on your editing. Also, views are mostly used to create customsettings for the different deliverables. 
Views include the following settings: 
 Layer Combination 
 Scale 
 Structure Display 
 Pen Set 
 Model View Options 
 Renovation Filter 
 Floor Plane Cut Plane Settings (projected views only) 
 Dimensions (projected views and 3D Document only) 
 Zooming (projected views and 3D Document only) 
 3D window/Rendering window (3D views only) 
 Rendering Scene (3D views only) 
 
 
29 
 
BIM Implementation Guide Page 29 
 
View Settings 
Naturally the above attributes have to be defined in the project template file prior to the creation of the views. It is highly 
recommended that you assign descriptive names to the named view settings (e.g. saved Model View Options Combinations and 
Layer Combinations assigned in view settings) so that they can be easily identified in the quick options dialog. 
 Note: Avoid the use of unnamed ‘Custom’ options in the projects, as they are difficult to identify and manage and can slow 
down navigation among views. ARCHICAD stores only one ‘Custom’ settings combination. If you change these settings 
without saving them as a named settings combination, all views using the ‘Custom’ settings will change. 
The easiest way to match the layer combinations, display options and project views is to call them by the same name. This method 
may not be applicable for complex projects with too many views. 
Manual rebuild of sections and elevations can significantly reduce the regeneration time of the View Map and the Layout Book in 
case of very large projects. The downside of this solution is that the project views have to be updated manually before the Layout 
Book is published, which can be a time-consuming process if you have an extensive documentation set. 
 
 
30 
 
BIM Implementation Guide Page 30 
Layout Book 
The Layout Book is the electronic equivalent of your physical documentation set. ARCHICAD has many features that help 
automate the documentation process, such as automatic drawing arrangement functionality on layouts, intelligent cross-
referencing between drawings and Master Layouts for automatic layout formatting. 
 
The following simple rules will help you utilize the Layout Book to best advantage: 
 The Layout Book is an integrated part of the Navigator. For best performance, all drawings on the layout should refer to 
views located in the View Map. 
 The Layout Book’s folder structure, naming and numbering has to be based on the same principles as that of the View 
Map and Project Map. The BIM Manual should contain clear guidelines for the organization of these Navigator elements. 
 The automatic update of drawings can significantly slow down the Layout Book regeneration in case of large projects. The 
update status of the drawings has to be carefully set by the BIM Manager prior to the start of a new project. Although 
manual drawing updates may require more management from the project architect, it can speed up navigation in the Layout 
Book for the entire project team. 
 The standard parts of the Project Info dialog (e.g. Company Name or Address) should be filled out in the company 
standard project template file. Other fields have to be filled out by the project architect when the new project is started. 
 
 
31 
 
BIM Implementation Guide Page 31 
You can use these values in Autotext elements to speed up annotation work for example on layout titles. 
 
Master Layouts 
Practical advice for the intelligent use of Master Layouts: 
 The default project templates should contain Master Layouts for the most common paper sizes. These templates should be 
based on the company’s documentation standards. 
 Master layout should contain the Revision History object. 
 To simplify the annotation of layouts, drawing titles and Master Layouts should exploit the capabilities of the AutoText 
feature. 
 Different project phases may require different Master Layouts, due to the different scale, titles, orientation and size of 
drawings. 
 Certain sheet types may benefit from of the Master Layout's Auto arrange and Align and assign to a Grid functions. For 
example, the Master Layout used for Interior Elevations should be defined using the Auto arrange radio button and settings, 
while the Master Layout applied for Details should be defined using the Grid radio button and settings. 
 
 
32 
 
BIM Implementation Guide Page 32 
 
Master Layout’s Auto Arrange and Align and Assign to a Grid options 
 Also, project-wide settings may need to be defined, such as display/hide a title to drawings placed on Layouts. 
 The name of the Master Layout should clearly indicate its purpose (paper size, scale, project phase etc.) 
 Note: In large projects, you may have several master layouts for different design phases/page sizes/page 
orientation/discipline. Consult the users and set the names so they find the right master layout easily in the list. 
For example: 
 
 
 
33 
 
BIM Implementation Guide Page 33 
Publisher Sets 
The Publisher Set function in ARCHICAD is really the key element to ‘one-click documentation generation’. Once your Publisher 
Sets are arranged you do not have to worry about the repetitive task of creating hundreds of drawings in different scales or file 
formats, ARCHICAD Publisher does it for you automatically. ARCHICAD performs best with predefined Publisher Sets made for the 
most typical output formats including printouts, PDF, IFC, DWG, etc. drawings. 
 
The company-standard template file for a large firm should include predefined Publisher Sets for the common output formats 
with the appropriate folder structure naming, numbering and export settings. There are a few important rules for the creation of 
Publisher Sets: 
 Publisher Sets must be closely coordinated with the Layout Book. The standard template file has to contain the most 
typical drawing types and the project architect or the BIM Manager is responsible for customizing it according to the current 
project. 
 Since the Publisher Sets are based on Views (that can be placed on Layouts), it is highly recommended to create proper 
Views in the project template file for all your drawings that you intend to publish. 
 The folder structure, naming and numbering of Publisher Sets has to be harmonized with those in the View Map and Layout 
Book for easier project management. 
 The output files have to be saved on a publicly accessible server that is regularly backed up by the IT team. 
 Transferring existing 2D CAD standards from their 2D environment to ARCHICAD without adjustments and modifications is 
strongly not recommended. This would suggest that the conventional 2D CAD working methods could still be applied 
without any changes. It takes more efforts to adjust to the new standards, but the overall transition will be faster. 
 
 
34 
 
BIM Implementation Guide Page 34 
Story Settings 
Stories are primarily used to vertically divide the building in the BIM project and to host the elements of each floor plan. In certain 
cases, special stories can be used to host temporary model elements, template content, source of objects, etc. Story heights 
are the most important settings of stories. In ARCHICAD, you can flexibly create new stories and add them to the structure or insert 
them between existing stories. 
 
Story Settings with intermediate service levels 
Element Attributes 
Element attributes are a generic term for the typical settings of the intelligent building elements in the BIM model. Element 
attributes include: 
 Layers and Layer Combinations 
 Line Types 
 Fill Types 
 Building Materials 
 Composites 
 Pens and Pen Sets 
 Surfaces 
 Zone Categories 
 Mark-Up Styles 
 
 
35 
 
BIM Implementation Guide Page 35 
 Custom Profiles 
 Renovation Override Styles 
 Operation Profiles (EcoDesigner) 
Well-managed and consistent attribute sets will increase productivity, reducethe chance for documentation and modeling errors 
and enhance communication within and outside the architectural office. The final attribute set of a BIM template file is usually 
the result of a long evaluation process that includes the revision of the existing office CAD standards and the implementation of 
new BIM guidelines. There are some important points to consider before you start defining the attribute sets for a company: 
 Existing CAD Attributes: Transferring the existing CAD attribute standards into the ARCHICAD environment will help the 
office staff to switch to the BIM workflow. There is no need to re-invent the wheel; if there is already a working solution in 
the office try to adapt it to the BIM environment. 
 Lack of CAD Attributes: If there were no commonly accepted attribute guidelines in the architectural office prior to the 
implementation of the BIM software, a new standard has to be defined by the BIM Manager. This is usually a complex 
process that requires the active participation of the project leaders and the representatives of the consultant offices 
(construction engineers, HVAC designers etc.) 
 Number of Attributes: It is recommended to constrain the number of attributes to the absolute minimum necessary. 
The more attributes collected in a project, the more complicated it becomes. Lots of layers, unused fills, line types can slow 
your work down as you might spend too much time selecting attributes from their lists. You should be more careful with 
deleting from the default ARCHICAD attribute set since many of these attributes are used by the default ARCHICAD 
Library. Removing or changing these attributes may cause problems in the default library objects. Some users may start a 
new project by opening an existing one and launching File/New/New…. This will inherit all attributes of the project just used 
- even the unnecessary ones. 
 Naming of Attributes: If the name of the attribute starts with special character like ‘@’, it will be displayed at the beginning 
of the alphanumeric list. This helps find and track the most important attributes used in the project. The use of punctuation 
characters is very bad practice. Naming conventions should be established and adhered to. 
 Attribute Management Across Projects: Another good idea is to start the project with few attributes and load additional 
ones with the Attribute Manager later on as needed. Using this function can save precious time for the BIM Manager. 
There is no need for manual re-entering of layers, pens and other attribute info if they already exist in another project file. 
 Coordination with Consultants: To minimize the risk of data exchange problems it is highly recommended that the 
consultants and the architectural office are using the same attribute set for documentation. Some CAD attributes may 
not be implemented in ARCHICAD due to the functional differences between CAD and BIM applications (e.g. ARCHICAD has 
no layers for doors and windows). The BIM Manager is responsible for maintaining the consistency of attributes during the 
import and export of drawings. ARCHICAD offers various tools for this purpose, for instance the DXF/DWG Translator allows 
the automatic assignment of AutoCAD layers to doors and windows during DWG export. 
 
 
 
36 
 
BIM Implementation Guide Page 36 
Building Materials 
Elements of the BIM model are intelligent, meaning they are primarily represented with the Building Material attribute. Further 
element attributes and properties regarding 2D or 3D appearance are controlled by this super-attribute as follows. 
 
The appropriate Building Materials define the behavior of elements --- either Basic or Composite structures --- in junctions and 
energy evaluation through Intersection Priority values or the assigned Thermal Properties. 
The assigned Cut Fill controls 2D and 3D representation and Surface attributes. In some cases, you may need to override the 
surface of elements to represent their final appearance, without generating multiple instances. This comes in handy when creating 
quantity takeoffs of different surfaces (like different paint colors) on the same construction elements. 
Since Cut Fills are assigned to Building Materials, and appear automatically on floor plan and section views. You can override the cut 
fills on element level, in the elements settings dialog if necessary, and use the Find and Replace to find them later on. However, we 
recommend creating as many building materials as used in the project instead. 
 Note: Besides regular 2D Fills, Building Materials can also appear as Fills, for example when creating a Custom Profile in 2D or 
when Thermal Bridge Simulation is run on 2D detail drawings. In this case the Fill will use the Fills assigned to the Building 
Material. For Building Material-type of Fills you can only override the pen color of the Fills, but not the patterns in the Fill 
Settings dialog. 
 
The Cut Fill - Building Material option in the Fill Settings dialog 
 
 
37 
 
BIM Implementation Guide Page 37 
The handling of Building Materials requires extra care from the BIM Manager. The following guidelines have to be taken into 
consideration when creating a template or organize the Building Materials: 
 Make a strategy: Make a list of all commonly used building materials. Find an appropriate naming system and find the 
intersection priority ranges in order to create an initial logic. Additional Building Materials can be more easily fit into the 
project if there is a framework. 
 Organize by priority ranges: Leave priority gaps between priorities, this way additional Building Materials created 
throughout the project will not require the reorganization of existing attributes. 
 Create dedicated Cut Fills: It is suggested to create separate Fills for each Building Material. In case the same pattern is 
used for multiple Building Materials create duplicates otherwise more Building Materials may change their appearance than 
expected. Avoid generic Fill names and make them as descriptive as possible. 
 Limit the use of Surface Overrides: Unnecessary number of Surface Overrides might cause project inconsistencies and 
makes scheduling/listing more complex. 
Layers 
Layers and Layer Combinations are a well-known concept and the most common tools for data organization in the CAD world. In the 
conventional 2D world they serve basically two purposes: 
 They control the visibility of elements 
 They provide higher level control over element attributes 
With these basic functionalities they still serve as the core ‘intelligence’ in the CAD application. They control almost everything 
including basic functions like the style of a drawing is being plotted or more advanced problems such as mimicking the entire ‘floor-
system’ of the building. 
In a BIM environment, layers have similar basic functionality but since there is much more intelligence inherently built into the 
model itself, layers and layer combinations are primarily the main ‘logical control’ over the elements of the BIM database. 
This means that in addition to controlling the visibility of elements, they serve to filter elements in quantity takeoffs or to reserve 
workspaces in a Teamwork project. Layers can also control whether two intelligent elements, such as walls, will join at intersections 
or not. In general, BIM projects require fewer layers then CAD drawings; consequently, layer conversion between CAD and BIM has 
to be precisely controlled by the BIM Manager. 
 
There are many factors that determine the layering standards of the architectural firm, such as the existing CAD standards in the 
office, the consultant’s requirements and naturally the type and complexity of the projects. Depending on the profile of the 
architectural firm the applied layering standards can be very different, but we can distinguish three main strategies. 
Use of the Default ARCHICAD Layers 
ARCHICAD is shipped with an extensivegeneric layer set that is appropriate for most project types. You can start your project with 
the default settings and then adjust to the needs of your project on the fly. However, we recommend this approach if the project has 
serious time constraints and it has average size and complexity. Even then, it is advisable to review the layer usage after an initial 
period of time and try to merge/eliminate unused or rarely used layers. Furthermore, Layer Combinations must also be revised if 
new layers are added to the layer list, since new layers will be hidden in all existing Layer Combinations. 
 
 
38 
 
BIM Implementation Guide Page 38 
 
NCS-compliant layer list in the ARCHICAD USA Commercial template 
Use of Layers Complying with National CAD Standards 
In some countries, state organizations, institutions and CAD manufacturers have developed local CAD Standards to improve 
productivity and enhance the interchange of CAD documents among different offices and applications. The most popular national 
CAD standards are the following: 
UK 
 BS 1192:2007 - Collaborative production of architectural, engineering and construction information. 
• BS EN ISO 13567-1:2002 Technical product documentation. Organization and naming of layers for CAD overview and 
principles. 
• BS EN ISO 13567-2:2002 Technical product documentation. Organization and naming of layers for CAD overview, format 
and codes used in construction documentation. 
USA 
 National CAD Standard (NCS) 
 National BIM Standard 
The complete US National CAD Standard (NCS) layer name format is divided into 5 parts: the Discipline Designator, the Major 
Group, two Minor Groups, and the Status fields. 
Discipline Major Group Minor Group Minor Group Status 
A I - W A L L - F U L L - D I M S - N 
One benefit of this very flexible system is that it keeps similar elements grouped in lists, minimizing the need to scroll and 
search for the correct layer. 
INT’L and Europe 
 ISO 13567 (International) 
 ÖNORM A 6240-4 (Austria) 
 Statsbygg BIM Manual (Norway) 
http://en.wikipedia.org/wiki/BS_1192
http://www.nationalcadstandard.org/ncs6/
http://www.nationalbimstandard.org/
http://en.wikipedia.org/wiki/ISO_13567
https://www.austrian-standards.at/produkte-leistungen/kostenlose-downloads/supplements-zu-normen/oenorm-a-6240-4/
http://www.statsbygg.no/Files/publikasjoner/manualer/StatsbyggBIM-manual-ver1-2-1eng-2013-12-17.pdf
 
 
39 
 
BIM Implementation Guide Page 39 
 BIPS (Denmark) 
 HKIBIM BIM Standard (Hong Kong) 
 Note: There are no global CAD/BIM standards available. The to-be-used standard has to be chosen properly depending the 
actual projects and locations. See more on international BIM developments here ». 
The main advantage of using national standards is that they offer a generally applicable layering guideline for different project types, 
disciplines and software applications. This solution can be recommended for multidisciplinary firms and those companies whose 
partners or clients have already adopted this standard. The downside of using national standards is that they might be too generic 
for those companies that specialize in one specific project type. 
Create and Use Custom Company Layers 
For most large firms, this is the recommended solution as it allows fully customized Layers and Layer Combinations for the given 
project type. Custom company layer sets increase productivity and reduce the chance of using incorrect layers. In the following 
paragraphs we collected important recommendations for creating your own layering system: 
 Number of Layers is critical for usability. You should try and keep it to the minimum. The optimum number of layers for 
an average-size project is 50-100. Naturally this number can be significantly more if justified by complex structures or 
systems. In this case, a layer naming system must be designed to make it easier to locate individual layers. In any case, before 
creating a new layer for a group of elements, consider whether another function (e.g. renovation, revision management) 
might be able to solve the problem. 
 Note: If you regularly need to select a certain set of elements for editing them as a group, you don’t need to set up a layer for 
that sub-group: instead, create and save a ‘Criteria Set’ for this task. 
 
 Layering Logic can depend on various factors, such as the different building structures, building element types or their 
function or location in the building. As a rule of thumb, layers should be created as the smallest reasonable logical group 
of elements you need to handle together on a regular basis. 
 Note: A good analogy for layers is the concept of ‘building systems’. For instance a layer called ‘walls’ maybe too generic 
while ‘concrete wall_25cm_plaster-on-both-sides’ maybe too specific. Try a logic based on functions, such as ‘load bearing 
walls’ for defining the appropriate scale of elements on a given a layer. 
 Layer Naming and Extensions: The proper naming and numbering of the layers will help the users to easily find the 
desired layers even in a very long list. Naming conventions similar to the one used in the NCS allow logical organization of 
even very long layer lists. In addition to using layer names as a means of managing data, another useful technique of 
organizing layers is to add extensions to layer names. By structuring layers using extensions, one can get a quick overview of 
http://bips.dk/v%C3%A6rkt%C3%B8jsemne/tegningsstandarder#0
http://www.hkibim.org/?p=1937
http://en.wikipedia.org/wiki/Building_information_modeling#International_BIM_developments
 
 
40 
 
BIM Implementation Guide Page 40 
all layers of the same extension by clicking the filter button to the right of the Extension column header in the Layer Settings 
dialog box. 
 
 Note: Layer extensions can be used effectively for project phasing and option management as well. The most important use 
of layer extensions is in identifying layers from Hotlinked Modules in a Teamwork environment. 
Layer Combinations 
Layer Combinations provide you with pre-saved combinations of layer settings/states. This is one level up in the hierarchy of 
the layering logic. As opposed to the guiding logic for creating layers where you want to create element groups based upon their 
functional similarity, layer combinations are ‘snapshots’ of layer states for various purposes. For example, when editing the load 
bearing structure of your building, you want all layers that contain load-bearing structures (walls, columns, beams and slabs) to be 
visible, but you normally don’t want to see the furnishings. 
Well-defined layer combinations help the user to manage the content of the BIM project views without having to access the Layer 
Settings dialogs box constantly. Properly set layer combinations are essential for consistency in controlling the content of the 
View Map and Layout Book in the Navigator. Layer Combinations can be used to filter the project elements by various criterias: 
 Scale 
 Discipline (Architectural, Structural, MEP, etc.) 
 Project phases (SD, CD, DD, etc.) 
 View types (floor plan, section, details, etc.) 
 or any combination of the above factors… 
The Project Template file should contain properly named Layer Combinations for each view types in the Navigator. Custom 
(unnamed) layer combinations should be avoided, not only because users don’t know which layers are visible in the current project 
view, but also because custom layer combination can slow down the navigation among views. It is recommended to establish a 
policy for naming layer combinations so that users can find them easily. 
The use of temporary layer combinations to show/hide large groups of elements can be effective in very large projects, when too 
much information on the screen can prevent users from working effectively during modeling. 
The following Layer Combinations might be used to filter the views of large projects: Show 3D elements only (for modeling and rendering) 
 Show 2D elements only (for detail drawings) 
 Show exterior only (for elevations) 
 Show load-bearing only (for IFC output) 
Please note that options ‘Show 3D’, ‘Show 2D’ and ‘Show exterior only’ should be used just as temporary filters, rather than as view 
names. 
 
 
41 
 
BIM Implementation Guide Page 41 
Layer Combinations usually identify a type of output (floor plan, reflected ceiling plan, etc.). It is critical that Layer Combinations are 
defined properly in sequence before views are created. 
Layers vs. Layer Combinations 
Both Layers and Layer Combinations are logical grouping of elements. However, they are used for completely different purposes, 
so you need to clearly understand when to use Layers and when to use Layer Combinations. Being part of the View settings, 
Layer Combinations are more intended to be a secondary filter to set the shown/hidden/locked status of elements, while layers are 
for grouping by type, structural function, etc. 
Large projects may contain long list of Layer Combinations, so it is very important to document what layer is on/off/locked in a 
written template document, updated regularly by the BIM manager. 
The matrix below shows the status of the Layers in typical Layer Combinations. As in any other CAD program, the elements 
belonging to a particular layer can be locked or hidden. Furthermore, the layers control the visibility of the model elements in the 3D 
views (solid or wireframe mode). For example, the wireframe option can be useful when you want to check the result of solid 
element operations. 
 
 
 
42 
 
BIM Implementation Guide Page 42 
Pens and Pen Sets 
Pens are a well-known concept in the CAD world. Their primary function is to control the line weight in physical outputs such as 
plotting or printing. While the element’s color and line weight information are separated in AutoCAD for example, the pens in 
ARCHICAD store multiple data: 
 Thickness and color of lines on the screen 
 Thickness and color of lines on paper 
 Thickness and color of lines during file export 
This fundamental conceptual difference requires close attention from the BIM Manager, as it can be difficult for new ARCHICAD users 
having a 2D CAD background. The BIM Manual must give clear guidelines for how the pen conversion should be made during 
DWG import and export. 
Predefined Pens and Pen Sets are needed to control the output of drawing elements both electronically and on paper. Even the 
most carefully designed Pen Sets are useless if they are not coordinated with the following project template elements: 
 View Sets (Pen Sets) 
 Drawing settings (Pen Set, color) 
 Tool defaults (Pens) 
 Library Part default Pens 
 DXF-DWG Translator (Pen-color conversion) 
The ARCHICAD pen table contains up to 256 pens and you can store several Pen Sets in your template file. 
General Rules for Pens and Pen Sets 
 You need pen tables for on-screen work and for outputs. 
 Keep the pen table simple, do not use more pens than required in the project. 
 The first 10 pens should be reserved for the most commonly used elements. 
 Add a short description to each pen. This will help users remember the function of the given pen. 
 Include the most commonly used pen sets in the company standard template file. 
 Apply easy to understand names to the pen sets. 
 Make sure that the views are saved with the appropriate Pen Sets in the Navigator. Avoid the use of ‘Custom’ pen sets. 
 Pen 91 in older ARCHICAD versions was used for white background for the library parts. For library compatibility reasons we 
do not recommend changing the white color of this pen in template files. 
Exploiting the capabilities of Pen tables offers many advantages for ARCHICAD users: 
• Different views of the same model content can have different pen representations 
• Similar drawings can be shown with different pen sets on the layouts 
• DXF-DWG file output can be simplified 
There are many different pen table concepts adopted among our users, here we would like to mention just a few of them. 
 
 
43 
 
BIM Implementation Guide Page 43 
The ARCHICAD Pen Table 
This pen set is optimized for on-screen design. The different colors help to distinguish element types. The Pen Set in the standard 
ARCHICAD template is based on a matrix system. The vertical columns represent ARCHICAD element types while the horizontal rows 
define the 2D symbol types belonging to these elements. 
 
The Standard ARCHICAD Pen table 
The main advantage of this concept is that the ARCHICAD tool defaults and ARCHICAD library default pens are optimized for 
this pen table so there is no need for manual pen adjustment when you place the element with their default pen setting. 
The downside of this solution is that it requires the users to remember the dedicated function of 140 pens. Moreover they 
have to assign them correctly to every model element. Naturally this is not a realistic workflow in a large office and we strongly 
recommend that large practices use a simpler and more straightforward solution. 
 
 
 
44 
 
BIM Implementation Guide Page 44 
Pens by Pen Weight 
This is a very common and simple solution that is optimized for black & white paper output. The pen table usually contains no 
more than 10 pens, since the architects are not able to distinguish more pen weights in a common documentation set. Each pen has 
different pen weights and usually the pen weight is assigned in descending order to the pen numbers. This solution is 
recommended for those offices that would like to optimize their workflow for black & white printed documentation. Consultants 
may also require the architectural office to produce the DWG documentation this way. The major drawback of this solution is that 
the different ARCHICAD model element types are not differentiated by color on screen. 
 
Floor plan view in black and white 
Pens by Element Types 
This is basically a simplified version of the ARCHICAD standard Pen table. There are many variations of this solution but usually it 
works with less than 50 pens. Pens can be organized by different categories: 
 ARCHICAD element types 
 Disciplines 
For each category there can be a few pens assigned allowing the architect to use different pen thicknesses or different shades of the 
same pen color for similar elements. 
Pens for DWG output (optimized for DWG file exchange) 
ARCHICAD provides different methods to convert layers. For the best result, consult the engineers and perform some test 
import/export before starting a new project. 
 
 
45 
 
BIM Implementation Guide Page 45 
 
Pen-color conversion table of the DXF-DWG Translator 
Line Types 
Lines and Fills (hatches) are the most standard elements in CAD. They are similarly used in BIM workflows. In the following section 
we explain some basic techniques for use in the BIM implementation process. 
ARCHICAD supports three types of lines: 
 Solid 
 Dashed 
 Symbol 
While the solid and dashed lines are self-explanatory, symbol line types require more consideration. The basic problem concerning 
symbol line types is whether you can define a certain pattern for them on the Floor Plan at the scale you are currently working or you 
need to modify the scale or the size of the line type stencil. 
Please consider the following when you create line types in your project template files: 
 Too many line types makes the browsing of lines very difficult and can significantly increase the file size. 
 Symbol lines composed of many line segments can slow down the redraw of drawings that use many of these line types. 
 Use the LTScale option in the DWG-DXF Translator to get the correctly sized dashed or dotted lines after DWG export. 
 
 
46 
 
BIM Implementation Guide Page 46 
 
The LTScale Option in the DXF-DWG Translation Setup dialog 
 AutoCADsupports special line patterns that include texts and numbers. These cannot be converted directly into ARCHICAD 
Line Types. You have to use the Linetype-linetype conversion in the DWG Translator to match them with their ARCHICAD 
counterparts. 
Custom line types allow the definition of scalable lines that are particular to the firm’s practice. Because they can be created 
using lines and arcs, it is possible to inject more information into an item as simple as a line. For instance, lines can contain numbers 
or letters (use the Line/Arc/Polyline tools to draw these items) as well. 
Lines created this way can be easily selected and copied from any viewpoint, then pasted as line components into custom symbol 
Line Types. 
When creating a Line Type, it is best to change the drawing scale to 1:100. This allows the line to be scaled using percentages. 
 
 
47 
 
BIM Implementation Guide Page 47 
 
Text Line made of 2D segments. 
Fill types 
Custom ARCHICAD Fills can be created to convey more accurate drawing information with less effort. The use of custom Fills 
simplifies the task of drawing accurate floor coverings and/or wall texturing information. Fills are also essential for defining 
Building Materials and they can also be used for filtering (e.g. with Find & Select) and listing the elements in the BIM model. 
The fills in ARCHICAD are divided into 4 categories: 
 Solid (including gradient fills) 
 Vectorial 
 Symbol 
 Image 
Similar to symbol line types, the definition of symbol fills requires close attention from the BIM Manager. 
Please keep in mind the following when you create custom fills: 
 Too many Fill Types makes the browsing of fills very difficult and can significantly increase the file size. 
 
 
48 
 
BIM Implementation Guide Page 48 
 Symbol Fills composed of many line segments can slow down the redrawing of drawings. 
 It is recommended to convert Symbol Fills to Solid Fills during DWG export to avoid expanding DWG file size. 
 Make sure to develop and insert fills for the Vectorial Hatching properties of Surfaces so that they match the orientation and 
scale of the corresponding surface texture. 
 Check the resolution and size of images before adding them to image fills. Too dense image fills or large attached image files 
can slow down the regeneration of views they are visible. 
In case of Vectorial Fills, when you have many Symbol Fills/Line Types or complicated Fills/Line Types, it can increase processing time. 
Again, make these as simple as possible and load only as many as needed. 
Surfaces 
Surfaces are the basis of any model-based design and visualization of the project. Besides creating a nice look in photo renderings, 
Surfaces also define how the elements’ surfaces are represented in different project views. Surfaces are also needed for quantity 
takeoffs and room inventories. 
ARCHICAD Surfaces contain color, texture and light information and can be displayed in the 3D Window, Section/Elevation/IE 
Windows and in photo renderings. The special thing about them is that they can be used with different rendering engines, so one 
surface can have completely different attribute sets: the various rendering engines in ARCHICAD have different capabilities for 
displaying materials. 
Internal 3D engine 
 Hidden line view 
 Shading 
 3D Vectorial Hatching 
 Textures (bitmap only) 
 Transparency 
 Bump Mapping and other Alpha Channel Effects 
CineRender by MAXON engine 
 Surface Catalog 
 Global Illumination 
 Lamps and IES Lights 
 HDR images 
 Weather Presets 
 Shaders 
 Effects, post-effects 
 Grass effect 
 White Model/Cardboard Sepia Effect 
 Physical Renderer 
 
 
49 
 
BIM Implementation Guide Page 49 
Sketch engine 
 Textures 
 Transparency 
 Highlight 
 Emission 
The BIM Manager has to tackle the following issues regarding surfaces: 
 Too many Surfaces increase file size (especially high quality Surface Catalog items) and make the browsing of Surfaces more 
difficult. It is recommended to have just a limited number of Surfaces in the company standard template file and add custom 
ones to the project files as the need arise. 
 Please pay special attention to the size of the texture images. Large image files can significantly increase the size of the 
texture libraries and slow down the rendering process without noticeably improving the quality of the rendered pictures. 
 The naming of Surfaces is critical for keeping them organized. 
 Please note that Surfaces are identified by their index number and not by their names. Removing ARCHICAD Surfaces from a 
project file will cause all library parts that reference those deleted attributes to revert to some other default Surfaces if they 
are opened in another template or project environment for example. Loaded third party libraries often bring their custom 
and/or redundant Surfaces that could result in conflicts and errors. 
 Avoid inconsistencies between the CineRender and the Internal engine surface representations. 
 Note: A recommended method of applying new textures for CineRender that does not require rendering expertise: Add the 
texture and modify its settings using the Internal engine, it contains very few parameters compared to the CineRender engine. 
Then switch to CineRender mode and use the CineRender to match from Internal button. 
 
 
 
50 
 
BIM Implementation Guide Page 50 
Renovation Styles 
As part of the template files, check and set the renovation override options that meet your local standards. Using renovation styles 
you can reduce the number of layers and create appropriate schedules of the existing, to-be-demolished and new building 
structures. 
Attribute Management 
Attributes can be easily revised, managed or transferred between different projects from the Attribute Manager dialog. Be 
aware that ARCHICAD stores attributes by their index numbers and not by their names. This rule has to be considered when you 
import or export attributes between two files, or create new ones. You have to be extremely cautious when you want to overwrite 
attributes with similar names but different indexes. When new attributes are loaded from existing projects, the empty ‘holes’ of the 
attribute index list are not filled the new entries are added to the end of the list. Furthermore, different types of attributes can 
include associated sub-attributes, like Cut Fills, Surfaces, Vectorial Hatches, etc. 
Before making any changes, create a backup .aat file on a safe location, so you can restore the original attribute set if things go 
wrong. 
 
Use the buttons in the middle of the dialog box to manage the attributes between the two files: 
 Append: Adds the attribute to the end of the list of the other file, with a new index number. 
 By Index: Overwrites the attribute in the other file that has the same index number, or creates the attribute if that index 
number does not exist. 
 By Name: Overwrites the attribute in the other file that has the same name, or creates the attribute if the name does not 
exist. 
Use these buttons to rearrange the order of ID-s by creating a list on the right, and then appending or overwriting the file content on 
the left. 
Favorites 
Favorites can be described as an extensive catalog of predefined building elements. By having a full favorite list of the 
construction elements used in your project, we can say with a bit of simplification that your task is just ‘putting building blocks 
together’ in a LEGO fashion. As a more technical explanation, Favorites allow frequently used standard settings for any tool or 
 
 
51 
 
BIM Implementation Guide Page 51 
element type to be recalled at a moment's notice, speeding up both modeling and documentation. It’s a very powerful resource 
that improves both efficiency and the consistency of the project. 
Note: as Favorites contain mostly attribute settings, ALWAYS check each ofthem after migrating a project. If the new version of 
ARCHICAD contains attribute-related changes, Favorites may change ot missing attributes may appear in the settings. 
There are basically two ways to implement the favorite concept in ARCHICAD. 
Working with the Standard Favorites Palette 
Pros: 
 Integrated ARCHICAD feature. 
 Dedicated interface. 
 Favorites can be stored in external files. 
 Favorites can be transferred between projects. 
Cons: 
 No graphical preview and description. 
 No folders in the Favorite palette (difficult to organize too many Favorites). 
 You have to pay special attention during the import and export of favorites to the attributes indexes stored in the favorite 
elements. If the attribute index of the host file is different from those that are stored in the favorites you might have problems 
using the imported favorites in your project (e.g. elements appear with unexpected fills or surfaces). 
 
The Favorites dialog showing only the saved entries for different tools/elements 
This method is recommended if the number of Favorites is limited in the projects or if the users can easily identify the required ones 
just by their names. 
Working with ‘Graphical Favorites’ 
A useful variation of the Favorites is creating a visual legend of the typical wall types, doors and windows, objects, etc. Visual 
legends can include explanatory text notes to clarify each element to aid quick selection and can even have elevation or 3D views 
alongside them. 
Pros: 
 Graphical previews can be assigned to favorites. 
 Detailed descriptions can be added. 
 Favorites can be organized. 
 
 
52 
 
BIM Implementation Guide Page 52 
Cons: 
 This is not a standard ARCHICAD feature, thus it is not described in the ARCHICAD documentation. 
 Too many graphical favorites may increase file size. 
 Graphical favorite elements have to be hidden in the final documentation otherwise they may have effect on schedules. 
This content can be part of the template file (usually on a dedicated story wide below the model that is not part of the sections and 
elevations, or a separate module file that is hotlinked into the project for the time it is needed. 
Users can use the trace/reference to pick up parameters without opening the container story itself. 
Separate Graphical Favorites for On-demand Use 
You can create separate .pln files and hotlink them into the central project template, so users can load and display/hide them any 
time they need. We recommend that you create files for each structure type separately based on the same (central) template. 
Pros: 
 Users can simply pick up all parameters needed 
 Easy to use 
 Visual 
Cons: 
 More template parts to maintain and update/migrate 
 All attributes have to be the same in all files to avoid missing or changed appearance 
 Have to unload all modules before creating schedules 
 
 
 
Module based favorites 
 
 
53 
 
BIM Implementation Guide Page 53 
DXF-DWG Translators 
DWG is still one of the most widely used 2D data exchange formats among the participants of the building design process. Because 
of the conceptual differences between AutoCAD and ARCHICAD, it is essential to use conversion rules for correct translation 
of elements and parameters. These rules are stored in a so-called translator file (extension XML). You can create any number of 
customized Translators to correspond to different types of data exchange, saving time by not having to set these rules at every 
single file conversion. 
 Note: Using a common Translator is effective at firms, which save files for different exchange partners, and all coworkers need 
access to a common conversion rule. So it is recommended to keep the specific translators on servers. 
Since there are some fundamental differences between the handling of attributes in ARCHICAD and AutoCAD, the BIM Manager has 
to pay special attention to the translation of these elements. Prior to the implementation of the company standard Translators, we 
recommend to test them on a sample file that includes all company standard Layers, Fills, Line and Pen Types. Below we highlight 
the most common issues with DWG conversion. 
Adding a short description to your Translators is a good idea in case there are many of them in the company template file. 
Saving DWG from Layouts while Keeping the Original ARCHICAD Layers of Elements 
Users often want to save DWGs from their ARCHICAD layouts for further editing in other CAD systems. For this, they need the original 
ARCHICAD layers of the elements in the DWG, not the layer of the drawings on the layout. This is how you can do this: 
If you have up-to-date drawings on the layout, choose these settings in the translator (works in ARCHICAD version 10 and up): 
 - Save Layout into: ‘Paper Space with Full /Cropped Drawing's Content’ and 
 - Place drawings into: ‘Single DXF/DWG file’ 
 If you have outdated drawings on the layout, choose one of these options in the translator (works in ARCHICAD version 11 
and up): 
 - Save Layout into: ‘Paper Space with Drawings as Blocks’ or 
 - Save Layout into: ‘Model Space’ 
Converting DWG-DXF Colors and Line Weights 
The Translator import and export functions are slightly different for colors and line weights. When you open a DWG in ARCHICAD, 
the translator converts the colors to correspond to ARCHICAD, but because ARCHICAD has pens matched to colors, the lines have 
ARCHICAD pen weights. This is useful for matching to ARCHICAD drawing standards. 
When you export a drawing to DWG, the translator converts the colors, but the line weights will correspond to the ARCHICAD values, 
not to the values in the table. So line weights in the Translator dialog take no effect to the generated DWG. It appears that you 
cannot set different line weights as ARCHICAD defaults. The easiest way to set different Line weights as in ARCHICAD is to assign line 
weights to layers or colors. To simplify the process in AutoCAD: 
 If objects require identical line weight by layers, check the Set All Elements' Colors to BYLAYER box in Translator Setup > 
Attributes > Pens and Colors > Methods tab. When you open the file in AutoCAD, you can set the line weight using the 
Layer settings dialog. 
 If you want to assign line weights to colors, save the DWG using ARCHICAD colors. When you open the DWG in AutoCAD you 
can select the elements by color, and set the object line weight, or you can create a Plot style table, which contains 
parameters used by printing/plotting. Here you can assign pen weights to the corresponding colors. 
 Note: Plot styles have no effect on the display of the objects on the screen. 
 
 
54 
 
BIM Implementation Guide Page 54 
In ARCHICAD it is possible to place DWG files by drawings --- thus avoiding their attributes being imported to your file (in this case the 
DWG cannot be modified within the file). 
Round trip Workflow Support 
In most cases DWG files are the common platform between 3D and 2D applications, so data exchange is continuous. To reduce file 
size and simplify the import/export process, we recommend using two options: 
Open Extras/Store original blocks: this feature prevents generation of new ARCHICAD library parts from DWG blocks each time 
you open the file. This results smoother workflow, since it is easier to refer the file content and identify objects when questions pop 
up regarding the design. 
Save Extras/Reduce number of created blocks: this feature creates only one block of each ARCHICAD library part, and applies 
resize of custom settings. For example, zone stamps are saved as only one DWG block, but the text inside will be various for each 
instance. 
 
IFC Translators 
IFC --- Industry Foundation Classes --- is a neutral file format that makes it possible to exchange information between different CAD 
systems and other systems in the building and facility management sectors. 
The IFC languageinterprets the descriptions of 3D building model elements (such as slabs, walls, columns, beams etc.) between 
various software applications during the design process. In comparison to DXF, which is merely a graphic element format, IFC files 
also define the full properties of architectural objects, such as their 3D geometrical characteristics, materials and their relationship to 
other objects. 
IFC is the only open and standard 3D object-oriented exchange format used by BIM and is available free to all software vendors 
therefore making it the key exchange format. 
Applications used by the different disciplines can easily and quickly filter and identify the relevant, discipline-specific information 
from the IFC database. 
Importing and exporting model data using IFC takes place according to the settings of the IFC Translator you are using. ARCHICAD 
provides predefined, factory-default IFC Translators, but you can define your own ones as well similarly to DWG/DXF Translators. 
Due to the iterative process of the collaboration it is recommended to set up dedicated IFC Publisher Sets for the different disciplines 
by using the relevant translators, this way the revised model versions can be exported and shared through a one-click solution. 
 
 
55 
 
BIM Implementation Guide Page 55 
 
Geometry Representation settings of the IFC Translator Setup 
Exported geometries can be represented in various ways during IFC export. Certain materials are required to be handled specially, 
for example air gaps should be handled as ‘empty’ geometries, meaning they are not handled as a solid volume when collisions are 
detected, but should still be included for energy performance evaluation. If these kinds of Building Materials are excluded from 
collision detection (Building Material setting), the same materials can also be excluded from the export resulting in a consistent 
collision detection outcome in external programs as well. 
Furthermore, Composite and Complex Profile elements can be exploded, enabling the target programs to handle the different skins 
individually, for example in listings and scheduling while the skins are still kept as a group of elements. 
 Note: Successful IFC export/import depends on a combination of Layer combinations, IFC translator setup, MVO, PSD, 3D 
view filters. It is strongly recommended to consult and test the workflow with the representatives of co-workers on test 
projects BEFORE a new one starts, and establish the rules in a written document. 
Libraries 
In BIM projects, intelligent parametric objects are used to model and represent more complex elements. These objects can store 
nearly unlimited variations on that object through their parameters. For instance, one window object can represent dozens of 
windows, thus making their usage very efficient. 
Libraries are a crucial part of ARCHICAD projects. ARCHICAD is shipped with an extensive default library, but you can create 
additional library objects to serve any imaginable need of your project. 
 
 
56 
 
BIM Implementation Guide Page 56 
Attributes and Third Party Libraries 
Controlling the number of attributes in a project file can be a problem if you are using Third Party Libraries or add-ons. Many times, 
these third parties create their own attribute set and load them with their libraries using MASTER GDL files (MASTER GDL files can 
contain fill, line type and surface definitions). This can increase the attribute set unnecessarily. One solution could be to unload the 
MASTER GDL file of the third party, so those attributes are not used (in this case the Third Party library parts will not find their 
attributes) or modify the MASTER GDL so only the most important attributes are added to the default attribute set. 
Converting Symbol Libraries 
When migrating from CAD software to ARCHICAD or implementing ARCHICAD alongside another CAD system, it is practical to 
convert existing symbol or block libraries to ARCHICAD Library Part format, if possible. If the current software uses or can translate 
common file formats such as DXF or DWG, conversion is relatively easy and is worth the effort. AutoCAD blocks can even be 
converted in batches. 
 Note: Detail drawings such as eaves, foundation details or standard drawing symbols such as insulation or electric symbols 
should be saved and used in ARCHICAD as Library Parts with 2D symbol only. If appropriate, some symbols, e.g., a kitchen 
sink could be completed with a 3D object. 
Object Catalog 
Though ARCHICAD provides several tools to browse object libraries, it is recommended that the BIM Manager regularly issues a 
printed or electronic, e.g., Acrobat PDF, object catalog for ARCHICAD users in the office. 
ARCHICAD is capable of searching in object description. Use this place and enter the most important keywords to ensure users insert 
the most appropriate objects to the design. 
It could also be useful to publish the current libraries on an FTP server, to coordinate the work of remote offices. 
Most Common Library Types 
 Standard ARCHICAD Library is the most current version of the ARCHICAD object library or 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. 
 Office Standard Library is a collection of those objects that have been developed to meet the office requirements. This 
library typically includes annotation elements (e.g. markers, labels, drawing frames etc.) and 3D objects (e.g. doors, windows, 
curtain wall elements, typical furniture etc.). 
Project-specific Libraries consist of custom elements developed specifically for the actual project. Typically the project team 
members create these objects without GDL scripting. 
 A number of Third Party Libraries that can be found on the Internet with useful objects that is not present in the 
ARCHICAD library. 
The above four libraries can reside on the company file server or on a team member’s computer. For the best performance we 
suggest the following strategy for library storage: 
 ARCHICAD Library and Office Standard Libraries are installed on a central server by default, so it is quick and easy to 
update. Libraries are stored in a container file format (LCF) and users are not allowed to modify them. Only BIM Managers 
have the right to update them. 
 Project-specific Libraries are stored on the company file server. The library is not compressed and project team members 
can freely edit its content. 
 
 
57 
 
BIM Implementation Guide Page 57 
 The location of Third Party Libraries depends on how often they are used. Regularly used objects should be installed on the 
user’s computer, while the others can be stored on the company file server. 
 Location Format Owner 
Standard 
ARCHICAD 
Library 
Server BIM Server Library BIM Manager 
Office 
Standard 
Library 
Server BIM Server Library BIM Manager 
Project-
specific 
Libraries 
Server (Project File) Embedded Object Project Team 
Third Party 
Libraries 
Server (Project File) 
BIM Server Library 
or 
Embedded Object 
BIM Manager 
Standard ARCHICAD Library 
The Standard ARCHICAD Library should always be loaded by default with the office template file(s) and with each project, as it 
contains all of the required macros and necessary components to make all objects function properly. The ARCHICAD Library is 
usually located on the local hard drive and updated centrally by the IT or BIM manager. Due to the ARCHICAD library’s large size, it is 
better to store it locally to reduce the library loading time. The central update of ARCHICAD libraries will prevent users from loading 
outdated library versions. 
Office Standard Library 
The Office Standard Library is defined as the library that - in addition to the ARCHICAD Object Library -, will be loaded with 
each and every project within an office. The Office Standard Library will contain all of the objects created, editedor adapted by 
the firm as a standard to suit specific needs. Like the ARCHICAD Office Library, it is best if the Office Standard Library is accessed as a 
container file (LCF) rather than in extracted form (GSM objects); this decreases loading time and maintains the integrity of the library. 
The BIM Manager along with assigned office staff should determine a workable Office Standard Library based upon staff skills, 
project types and firm-provided services and be responsible for its maintenance. 
Content of the Office Standard Library: 
 Standard annotations 
 Details 
 Typical structural elements and furniture 
Project-specific Library 
The project library contains project-specific elements only. These can be: 
 StairMaker stairs 
 Custom door/window panels 
 Background images 
 
 
58 
 
BIM Implementation Guide Page 58 
 Texture images 
 Custom model elements used only in the project 
The Project-specific Library is defined as the individual library folder that is created specifically for each project within an office. It is 
included within every project’s directory/folder at the time it is created and is maintained as a GSM library to allow the easy 
modification of the objects. The Project-specific Library is the storehouse for all custom parts created for the particular project, 
including textures, stairs, etc. The Project-specific Library is effective in an office because it gives the user the flexibility of 
customization, while maintaining the integrity and office standardization contained within the Office Standard Library. Once 
created, custom parts can be evaluated as to their relevance for inclusion into the Office Standard Library at any time. 
Third Party Libraries (Custom Parts) 
In addition to the more than 1000 highly parametric objects included in the Standard ARCHICAD Library, you can find several 
custom GDL objects and libraries over the Internet. Some of these libraries and objects must be purchased while others can be 
downloaded free. 
There are thousands of generic and manufacturer-specific objects available with the cloud-based BIMcomponents.com database. 
Architects and designers can share, upload, and download their objects, and members can discuss and rate the content of the portal. 
Free membership is available for everyone. 
 
For more information, please visit the websites of object manufacturers, who provide content in various formats, like 3DS, SKP, Rhino, 
etc. ARCHICAD allows the opening or conversion of various 3D model formats into GDL objects. The file formats created the most 
widely used freeform modeling tools, like 3D Studio Max or SketchUp can be easily opened by ARCHICAD either natively or through 
add-ons. 
Use the File/File Special/Merge… menu command to open SKP or KMZ files (Google Earth) and the 3D Studio In add-on for 
ARCHICAD (available here »). 
note.jpg Note: ARCHICAD is capable of saving and opening various other file formats, the full list of 3D model formats is described in 
details in the GRAPHISOFT Help Center. 
 Note: Objects converted from other applications may contain a lot of polygons that can cause serious performance leak. We 
recommend that you open a new project to convert and try the third-party object before embedding it into the live design. 
http://www.bimcomponents.com/
https://www.graphisoft.com/downloads/goodies/index.html
http://helpcenter.graphisoft.com/guides/archicad-18-int-reference-guide/interoperability/file-handling-and-exchange/file-types-saved-by-archicad/model3d-formats-saved-by-archicad/
 
 
59 
 
BIM Implementation Guide Page 59 
Even if you are not familiar with GDL scripting, you can create your own custom doors, windows and other objects by saving 
ARCHICAD models as GDL library parts. Complex elements can be created from simple elements, like slabs or walls and saved as GDL 
objects. 
 
When converting 3D objects to library parts, ARCHICAD creates a temporary floor plan symbol from the top view of the object. In 
case of complex forms --- vehicles, people, curved shapes - the temporary symbol may require manual editing. Delete unnecessary 
lines or contours from the symbol to speed up the redraw of plans using the Linework Consolidation feature. 
Teamwork Library Solutions 
Proper management of libraries is extremely important when working in teams. To avoid missing or outdated library parts in the 
Teamwork project, you should understand the three major library-handling strategies in ARCHICAD. 
Embedded Objects 
Specialized user-configured library parts will be automatically embedded into the project. Embedded objects will also be part of 
Teamwork projects; they can be reserved individually from the Library Manager, modified and sent to the server like other elements 
in Teamwork. Embedded objects created and accessed by you (such as when creating or editing a Stair with Stairmaker) will 
automatically belong to you. 
Because these objects are embedded in the shared project, all users regardless of location can see and access these specialized 
library parts without running into difficulties. 
The Library Manager lists all the embedded objects of the project. Users can select and reserve these objects one by one. 
BIM Server/BIMcloud Libraries 
BIM Server/BIMcloud Libraries are housed on the Teamwork/BIMcloud servers. Each user automatically obtains a cached copy of 
these linked libraries; any updates to these libraries are received by all users. Any user having the proper access rights can add a new 
linked library to the shared project; this linked library will henceforth also be located on the servers. The authorized users can 
remotely update and maintain the Teamwork libraries on the server thus the chance for using outdated libraries in the office can be 
reduced to the minimum. 
Local Libraries 
Separate local libraries were used frequently in the past, but they are not used any longer due to increasing LAN speed and network 
stability. This traditional method also required massive management efforts to make sure that all teammates are using the latest 
library content. 
Pros: 
 Does not put an extra burden on the network and can be used in a network-down situation 
 Modifications are easier to monitor and manage in case of one computer 
 
 
60 
 
BIM Implementation Guide Page 60 
 This is the traditional ARCHICAD method and thus more familiar to users 
Cons: 
 The preparation takes longer 
 Requires local computers with very large hard disk capacity 
 Requires disciplined workflow 
Central Library 
The library is located on a server, which can be the Teamwork project server or a standalone data server. The library is directly loaded 
with the PLC file on every team member’s computer. 
When working with a Central Library, new elements created by any user can be immediately used by the other 
Project Template Tricks 
In this section, you find some good examples on how a project template can support the design team effectively. Use these ideas 
carefully since they are not applicable for all cases. 
Basic Attributes In tpl, Extended Attribute Set In .aat 
This is an easy way of reducing the number of attributes at the project start, and adding more as the project goes on. Users make less 
inconsistency and mistakes. On the other hand, you have to be careful with stored favorites and library parts, so there are no missing 
attributes at any stage of the project. The BIM manager is in charge of the attribute management. 
Pros: 
 a filtered list of attributes is available to choose from 
 in case of company level attribute changes, it is enough to change the .aat file instead of the whole template 
Cons: 
 adding custom attributes is not allowed because it changes the ID order of additionally added attributes. This may cause 
appearance problem of objects, which identify attributes by IDs instead of names. 
2D Favorites and Pen Set Descriptions On Worksheet 
In analogue with the module favoritesmentioned above, you can also store graphical favorites for 2D elements like pens and fills. 
You can also store the detailed explanation of the different pen sets here. 
 
 
61 
 
BIM Implementation Guide Page 61 
Pen set descriptions on a Worksheet 
Layout Title Blocks And Legends On Worksheets 
Title blocks contain constant information written on each layout published from the project. Usually a project needs at least a 
Portrait and a Landscape version of the same title block, which appear in several layout masters. If anything changes on the title 
block, you have to edit each master one by one. To avoid this, you can draw the title blocks on worksheets, and place the on the 
 
 
62 
 
BIM Implementation Guide Page 62 
layout masters as drawings. Thanks to ARCHICAD’s intelligent Autotext feature, all automatic fields will behave correctly. 
 
 Note: The Revision History object works only if it is placed on a layout or layout master. Do not place it on a worksheet! 
 
 
 
63 
 
BIM Implementation Guide Page 63 
Chapter 6 - Project Workflows 
In this chapter we explain the backbone of the model-based design workflow. We will give you recommendations on issues such as 
‘How detailed should my model be?’ Also we provide you with strategies to tackle the most important issues. The big question is 
how to share projects that cannot be finished by a ‘one-person’ team. ARCHICAD provides various robust yet flexible solutions to this 
problem. 
Project Lifecycle 
The following table shows the generic project lifecycle with the most important and typical actions taken in the architect’s office. 
Implementing BIM in the design process requires a new, 3D way of thinking. This means that the old linear processes will be replaced 
with parallel ones. To manage these processes and keep the project on time and in budget, the project leaders and the BIM manager 
have to think at least one step ahead to ensure the most effective design environment for the whole team. 
 
 
Creating the Design Model 
The new design workflow is based on a 3D BIM model that is continuously elaborated throughout the different phases of the project. 
Let’s review the three main phases of the architectural design process in the BIM office. 
Schematic Design 
This project phase is typically initiated by the project architect. The design team is usually limited to 2-3 architects or designers. 
Overall the project architect is responsible for the consistency of the BIM model. 
It is important, that the team creates as much as possible in ARCHICAD, and uses other solutions to support special design situations 
only. 
 
 
64 
 
BIM Implementation Guide Page 64 
Schematic design methods 
ARCHICAD users have adopted three fundamentally different schematic design methods over the course of time. 
1 Paper Based Design: This is the traditional paper based design method that involves the creation of many hand 
sketches and drafts; there is no BIM modeling involved in this process. Modeling starts at the DD phase with scanning 
and placing the materials to Worksheets. Using the Trace and Reference feature it is easy to remodel the structures in 
ARCHICAD. 
2 Design Software: There are a number of conceptual design applications available on the market. Many times it is easier 
to remodel the building in ARCHICAD due to the lack of accuracy in the original model. 
Third patry solutions, like Rhino, or point clouds can ease the design process by add-on based and native support. 
3 Schematic Design with ARCHICAD: This workflow allows the smoothest transition from SD to DD. It also supports 
preliminary cost estimation and various building performance analysis and rich visualization capabilities. However it 
requires an experienced BIM modeler who can quickly convert the architect’s design ideas into an ARCHICAD model. 
ARCHICAD offers programmatic design and massing capabilities with the help of zones, morphs and shells. ARCHICAD’s 
3D zones provide quick and easy access to basic volume and area schedules as well as to basic cost estimations at the 
schematic design stage. ARCHICAD’s zones can also be converted to ARCHICAD elements (walls, slabs and roofs) with a 
single click using the Magic Wand. Even in this early phase it is important that the ARCHICAD model is based on the 
standard project template. 
 
Schematic Design Modeling with the ARCHICAD Zone Tool 
 
 
65 
 
BIM Implementation Guide Page 65 
 
Schematic Modeling with the ARCHICAD Morph Tool 
 Note: Point clouds of the environment imported to the model can serve as a good context for the building mass. 
Design Development 
The approved schematic design is further developed into real architectural plans, elevations etc. with material finishes and 
dimensions. The final DD documentation is submitted for review and approval by the building committee. The transition from SD to 
DD can be different depending on the schematic design methods used in the company. 
Paper based and external application: The project architect together with the BIM manager plans the BIM project structure including 
Teamwork, project sharing methods and the collaboration of the modeling and documentation teams. Most often the BIM manager 
and the project architect develop the main BIM model file based on the SD sketches, which is then subdivided into Teamwork files or 
modules according to the size and complexity of the project. Then, they make several tests to find the best conversion method 
between the existing files (including scanned paper drawings) and the ARCHICAD project. 
If the SD phase was developed in ARCHICAD, the team just continues working on the existing ARCHICAD files. The project architect 
and the BIM manager control the sharing of the project. 
Usually, this is the phase Revision numbers are added to the released documentation sets. We recommend using the built-in 
Revision management workflow to keep it consistent and up-to-date. 
Construction Documentation 
The approved definitive design documents are developed into comprehensive construction drawings and specifications used to 
secure a building permit, to competitively bid the work among qualified contractors and ultimately as the basis for the construction 
of the project. 
This is the most time-consuming part of the architectural design process and requires the highest-level collaboration within the 
design team. Furthermore there is an increased need for data sharing between the architects and the consultants. 
There should be one dedicated person who is responsible for the consistency of the project. 
 
 
66 
 
BIM Implementation Guide Page 66 
Transition between the Project Phases 
The shift between the major project phases is always a critical period in the lifecycle of a project. The smooth transition between the 
Schematic Design, Design Development and Construction Documentation phases requires a detailed plan of how the project files 
will be converted or carried through to the next project phase. Should SD/DD/CD phases be created in the same file or should a new 
file be saved under a new name and work continued in that afterwards? Generally we can say that it’s mainly the size of the project 
and the documentation that defines how the project files should be handled between the project phases. Including two or more 
project phases in one ARCHICAD file will increase the file size, which can cause serious performance problems in large and complex 
projects. Furthermore, navigation between the views and layouts can be very difficult due to the large number of Navigator items. 
Thus, we recommend creating separate files for the main project phases in big or complex projects. 
As Built Model 
To take the advantage of stored information in the BIM model, the architect or the construction companies are more often hired to 
create the model of the final building for facility management purposes, and as a source offurther refurbishments. Point cloud of the 
building and its environment can be a good tool to make sure the model reflect the reality. 
 Note: If there are separate files for DD and CD, and major changes in CD require creation of a new DD version, how are the 
two file versions synchronized? One possible solution is to save CD floor plans as ARCHICAD modules (MOD) and place them 
as Drawings on DD Floor Plans so that differences are visible and can be carried through. Further tips for managing design 
variations can be found in Chapter 6.5. 
Sharing the work 
Collaboration is essential for making the project team function effectively and moving projects forward as quickly as possible. 
Effective collaboration and project sharing techniques are able to adapt to the project team size and the office organization. 
ARCHICAD offers various solutions for project sharing that can be used alone or in combination. 
The single file concept of ARCHICAD is well proven in small firms with small to medium sized projects. Larger firms with larger 
projects have to divide projects into several files for many practical reasons. Those reasons include performance drawbacks of the 
single file method and workflow bottlenecks where multiple users are working with one file. ARCHICAD supports different scale 
projects by providing a transparent method of handling multiple sessions and views to this complete collection of files. Basically 
there are three typical workflows in ARCHICAD, which can be combined depending on the actual project: 
Small Projects --- Single File Concept 
This is the suggested ARCHICAD workflow for small to medium scale projects. The complete 3D model (virtual building data) with its 
representations (floor plans, sections, 3D views, schedules, etc.) and the final drawing sheets (layouts) are included in one ARCHICAD 
file. 
 
 
67 
 
BIM Implementation Guide Page 67 
 
The ARCHICAD Virtual Building Concept 
This method can fully exploit the advantages of the Virtual Building Concept such as easy file management, automatic drawing 
updates and listings. However, above a certain project size and complexity, the ARCHICAD plan file must be divided into smaller 
parts to avoid speed and project management problems. Our tests show that ARCHICAD projects can be handled in one PLN file if 
the uncompressed file size doesn’t exceed 150-200MB. 
 
The ARCHICAD Single File Concept 
Medium Size Projects --- Model File and Document File Separated 
The next figure shows that the project documentation (Layout Book) can be separated from the project model file to reduce the 
ARCHICAD file size or to allow two teams (e.g. a modeling team and a documentation team) to work simultaneously on one project. 
If your project contains more than 100 layouts, you are advised to consider this method. 
Note: to speed up drawing update, use the Drawing Manager instead of opening all layouts one by one. 
 
 
68 
 
BIM Implementation Guide Page 68 
 
Separate Model and Documentation File 
 Note: If the drawing update is slow in the documentation file, you can use a semi-automatic workflow by publishing PMK files 
from the model file, and placing these files as drawings in the layout book file. PMK files contain only 2D data and pen 
information, so they are fast to save and fast to update. On the other hand, this method requires extra attention to make sure 
the layout book drawings reflect the current model state. 
In this case there is no direct link between the model file and the document file, thus the drawings on the layout do not 
automatically follow the changes in the model file. This method is only recommended if the PMK files are rarely updated, or if the 
automatic drawing update from the model file is too slow. This might be the best solution for very large projects with extensive 
documentation sets. If this method is used the BIM Manager or Documentation Manager has to control the saving and 
linking/updating of these PMK files. 
 
Manual PMK Saving and Linking to the Document File 
Drawings are imported into the Layout Book directly from one or more building model files and other external file sources (DWG, 
DXF, PDF-s, image files, PMK-s, etc.). For a very complex building, the documentation file can also be subdivided into two or more 
parts for easier drawing management. 
This is a complex system but very powerful, and in some cases may be the only way to handle large projects. Where complex 
documentation structures are used in the office, it is crucial that the BIM Manager/project leader develops the proposed file 
hierarchy and distribute this to the project team members prior to starting the construction documentation phase. 
 
 
69 
 
BIM Implementation Guide Page 69 
Big Projects --- Hierarchal File Structure 
In the case of very big and complex buildings, a combination of different file sharing methods is needed that are appropriate for the 
office organization and the size of the project. In the following example a multi-story office building is in the construction design 
phase. The building consists of two towers. From the very early stage a 3D model of the whole building was built, containing only 
those elements essential for visualization and conceptual design. Based on this model, two Teamwork files were created (one for 
each tower) that served as the basis of the construction documentation. The Teamwork files refer to external hotlinked modules and 
XREFs such as column grids, land surveys and other consultant drawings. The documentation is stored in two Layout Book files to 
reduce the size of the Teamwork projects and to allow the project documentation team to work in parallel with the 
designers/architects. 
 
Complex File Hierarchy 
Teamwork 
The Teamwork (TW) concept has been GRAPHISOFT’s primary solution for sharing the BIM data among the project team members 
since 1997. Over the course of time the collaboration requirements of the architectural practices has been significantly changed due 
to the increasing file size, project complexity and the extensive use of Internet based communication. 
Teamwork 2.0 represents an entirely new approach to collaborative project work, specifically designed to meet the demands of a 
modern, international team effort. Teamwork for ARCHICAD is based on client-server architecture and is designed to ensure 
maximum flexibility, speed and data safety to enable teams - even those spread out around the world - to collaborate on large 
projects. 
Details of the TW approach are explained on the accompanying figure. 
 
 
70 
 
BIM Implementation Guide Page 70 
 
The GRAPHISOFT Teamwork Concept 
 The keystone of this concept is the client-server technology, which in case of ARCHICAD consists of the GRAPHISOFT BIM 
Server and ARCHICAD as a client. The intelligent server application maintains the complete and up-to-date BIM model of a 
project. Team members work on local computers and regularly send and receive project changes between the server and 
their local ARCHICAD. During send and receive only modified elements of the project are sent over the network that results 
much faster data communication and the parallel working of the entire team. 
 Other key element of this concept is the flexible reservation system. Individual model elements and other project related data 
like project attributes or view sets can be reserved and released on the fly allowing a very dynamic and flexible workflow. 
There is no need to reserve large areas in the project prior to starting the actual work. Only the currently used elements need 
to be reserved and they can be easily released after the work is done. 
 The team communication is backed up by a built ---in, element and task based messaging system. 
 The BIM Server Manager application allows the CAD managers to remotely manage projects, servers, users, roles and 
responsibilities across the entire firm. 
Evaluation of the Teamwork2.0 Technology 
Benefits 
 Effective: Team members can work on the same project simultaneously, and there is no need to divide it into smaller 
physical parts 
 
 
71 
 
BIM Implementation Guide Page 71 
 Organized: No overlapping workspaces; only one user can work on one project element at one time. Team members have 
dedicated roles and rights. 
 Transparent: Team members can check the actual status of the project at any time. 
 Easy: Collaboration techniques are really easy to learn. There is no need for extensive training. 
 Fast: Due to the revolutionary DELTA-serverTM technology only the changed elements are sent between the client and the 
server. Average data package size shrinks by an order of magnitude from megabytes to kilobytes. As the size of data 
transferred is small it is not dependent on the file size and you can work through any kind of network and even Internet. 
 Flexible: Due to the on-demand element reservation system and the fast data access team members will feel that they have 
access to any element any time regardless the size of the firm or the complexity of the project. 
 Data Safety: The server becomes a dynamic component in the process. The intelligent server application doesn’t allow 
corrupted data to be merged. When the client’s data gets damaged on the network the server filters it out and doesn’t merge 
it to the server database. 
 Offline Work: Users can create new elements or modify those ones that belong to their workspaces even if there is no online 
connection between the BIM Server and their local ARCHICAD. Once the online connection is established they can send and 
receive changes again. 
Suggested usage 
Teamwork should be your primary method for sharing the content of the virtual building as it has many benefits compared to other 
file sharing solutions. In case of very large or complex project you might have to consider dividing the project into smaller parts in 
order to avoid any performance drawbacks caused by the large file size. Big buildings can be split into several smaller Teamwork files 
using the hotlink file methods allowing you to significantly reduce the regeneration time of the 3D model and the project 
documentation. 
GRAPHISOFT’s award winning Teamwork technology provides an effective method for sharing ARCHICAD projects. Teamwork allows 
your office to define different team roles, such as ‘team leader,’ ‘team member,’ ‘administrator’ and ‘visitor.’ Depending on the 
function assigned to them, team members have specific rights to access and modify the central project file. 
Advantages 
 Team member roles are clearly defined 
 Team members can continuously check the work of other members 
 No conflicts can occur in the architect’s workspace 
 The Teamwork file is always up to date 
Remote access to Teamwork projects requires additional network settings; these are described in a separate ‘Networking Basics’ 
document, available on ARCHICAD WIKI at http://helpcenter.GRAPHISOFT.com/technotes/next-generation-
Teamwork/?redirect=ARCHICADwiki 
 Note: Once you have joined a Teamwork Project, you can open or close the project as many times as you like, without losing 
your reservations or dumping your local copy. When you finish working for the day, do not leave the project; just close it. The 
next day, you will not have to join the project (you are already joined in); just open it. However, once you leave the project (as 
opposed to closing it), you lose your reservations and dump your local copy. It is recommended that you do not leave the 
project unless you do not plan to work on it any more in the foreseeable future. 
You should only reserve an item/data type for as long as you need to work on it. Once you are done working on it and have sent your 
changes, you should release your reservation. 
http://helpcenter.graphisoft.com/technotes/next-generation-teamwork/?redirect=archicadwiki
http://helpcenter.graphisoft.com/technotes/next-generation-teamwork/?redirect=archicadwiki
 
 
72 
 
BIM Implementation Guide Page 72 
To get started with BIM Server and BIMCloud, see BIMCloud and BIM Server Help. 
Hotlink Modules 
With Hotlink Modules external ARCHICAD files such as modules, plan files and even Teamwork projects can be inserted into the 
currently open Project (host). Elements inserted into the host reflect all modifications made to the source files. The elements of 
hotlink modules are included in the Project, which means that even if the hotlink source file is not currently available, the Modules 
are still present and visible, although they cannot be updated as long as the referred source file is absent. 
ARCHICAD also supports the hotlinking of a module into other modules. These modules are called nested modules. 
 
The Hotlink Module Concept 
The hotlink manager dialog in ARCHICAD allows the project leader to easily overview the hierarchy of even very complex hotlink file 
structures; furthermore the status of the individual modules (updated, outdated, broken) can also be checked at any time. Updating 
of the entire hotlink module structure or just individual hotlinks is very easy it requires only a click of the mouse. 
http://helpcenter.graphisoft.com/guides/archicad-18-bimcloud-and-bim-server-help/
 
 
73 
 
BIM Implementation Guide Page 73 
 
The Hotlink Manager 
Hotlink Modules in ARCHICAD, for example, can be used to manage the repetitive structures of buildings, such as hotels or offices, 
which have a large number of identical rooms by modifying all instances in a single step. Moreover, the same structures can be used 
in multiple Projects. This is also a good way to subdivide large Projects into easier-to-handle smaller files and to reduce the file size of 
the host project. 
If there are identical stories in a building you can hotlink the typical story of the host file into the other stories. In this special scenario 
the hotlink modules are contained within the host file. 
We also recommend this technique to place external content, e.g. IFC or Rhino models to the project. This way, you can check the 
model and its attributes before you place it to the live project. This way, you can avoid performance leak and attribute overload 
problems. 
Advantages 
 Module files can be updated automatically or manually 
 Updating a module is fast and easy 
 
 
74 
 
BIM Implementation Guide Page 74 
 The host project file size can be much smaller when repetitive elements are placed as modules, since ARCHICAD stores them 
only once 
 They are useful if larger models that has to be divided into smaller, easier-to-handle logical parts 
 Repetitive elements of the project can be controlled and modified easily 
 Teamwork files can also be hotlink to each other. This way the size of the TW project files and the regeneration time of the 3D 
models and the documentation can be reduced significantly 
 Comprehensive user interface provides a clear overview of Module instances and hierarchy; allows you to open separate 
ARCHICAD with the source file from the Hotlink Manager 
Limitations 
 Owner of the host file doesn’t have automatic control over the content of the hotlinked files 
 Changes to the hotlink file can cause conflicts in the host project 
 Moving or deleting the hotlink file from its original location will break the hotlink in the Host file. This may have effect on 
archiving processes, or when you want to move the entire project to a new server. 
 Access rights to the content of the modules can’t be controlled from ARCHICAD 
 A detailed module organization chart has to be created by the project coordinator before the project is started. Changing of 
the hotlink structure can be difficult in the later stage of the project. 
 Matching of attributes needed between the host file and the modules 
 The story height of the master project and of the hotlink modules should be the same 
 No protection against workspace conflictsNote: The creation and also the editing of hotlink modules should be done in the host project to avoid the creation of 
unnecessary and unwanted layers, pens, line types, fills, etc. (also known as ‘attribute pollution’) 
Suggested Usage 
Although 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 hotlink modules), they can’t provide the same flexibility and security as Teamwork. The main purpose of 
using hotlink modules should to manage repetitive elements and to divide very large projects into easy-to-handle smaller parts. 
XREF 
External References (XRef’s) are also based on the file hotlink concept however they can only be used to reference 2D drawings. 
XREFs provide an easy way to manage and merge the consultants’ DWG/DXF drawings into the ARCHICAD project. External 
DWG/DXF drawings will be updated in the ARCHICAD project if they are referenced as an XREF. Note that XREFs can also be located 
on an internal or ftp server. 
 
 
75 
 
BIM Implementation Guide Page 75 
 
The XREF Concept 
Advantages 
 DWG and DXF drawings of the consultants can be easily integrated into the Virtual Building as XREfs 
 Repetitive DWG/DXF files (such as detail drawings) can be controlled and modified easily 
 Modifications of the consultants are automatically updated in the ARCHICAD project. Collisions and design conflicts can be 
easily located with the Virtual Trace. 
 The content of the Xref drawing is saved with the ARCHICAD project. If the hotlink to the DWG/DXF file is broken, the drawing 
content is still visible. 
Disadvantages and limitations 
 Xrefs can’t be used to hotlink 3D data into the ARCHICAD project 
 DWG Translator has to be set manually prior to linking the DWG/DXF files 
 The location and the name of the Xrefs shouldn’t be changed otherwise the link will be lost 
 Matching of attributes needed between the host file and the modules 
 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 
 Doesn’t reduce the size of the master file 
 
 
76 
 
BIM Implementation Guide Page 76 
Suggested Usage 
XREFs should be used almost exclusively for merging consultants’ drawings, legacy AutoCAD projects or standard manufacturer 
details into the ARCHICAD project. We recommend placing the XREFs on Independent ARCHICAD worksheets instead of the floor 
plan in order to keep the BIM model intact. 
 Note: Unused XREFs should always be ‘Unloaded’ in order to remove all XREF related layers and other attributes from the 
master project. In other words: you should always ‘unload’ unnecessary XREFs to avoid attribute pollution in the master 
project. 
Combined workflow 
Documentation Separated from the Model File 
The documentation and design teams can work simultaneously on the project if the documentation file is separated from the model 
file. The size of the master file can also be reduced if you adopt this method. ARCHICAD fully supports this workflow since you can 
control complex file hierarchies in the Navigator palette. There are two strategic ways of separating the documentation from the 
model. 
Master File Method 
In this scenario there is a master ARCHICAD file that contains the complete ARCHICAD model, and the corresponding views. The 
separate documentation file refers to the views of the model file and automatically updates the drawings if the model file is changed. 
This method is applicable for medium to large-scale projects. 
Complex and Distributed Methods 
Due to size and speed issues, very complex or large projects usually do not have a master file that contains all the drawings. 
Consequently the building model is stored in multiple project files (some of them can be Teamwork files; others can be simple 
ARCHICAD project files that refer to hotlink modules). There are two ways to import the drawings into the documentation file. 
Coordination 
Designing, constructing and maintaining a building is a very complex process that requires the close co-operation of several people 
working in various fields. One of the key problems of contemporary architectural practice is that different project participants 
require different types of information from the architect. For instance the data that the structural engineer needs is quite different 
from those required by the HVAC designer. ARCHICAD allows smooth communication with other applications via several file formats. 
The most important ones include IFC for sharing the Virtual Building model and DWG and PDF for exchanging 2D drawings. 
Furthermore the ARCHICAD Application Interface (API) allows 3rd party developers to provide native connection to other software. 
Coordination of project trades in the BIM office also requires intelligent filtering of the BIM model data and finding inconsistencies 
and collisions between the consultants’ work. ARCHICAD offers effective solutions for both problems. ARCHICAD model views can be 
filtered with the combination of the following options: 
 Layer combinations 
 Model View Options 
 Partial Structure Display 
 Filter Elements in 3D 
 
 
77 
 
BIM Implementation Guide Page 77 
ARCHICAD’s built-in Trace Reference feature helps the users to visually identify any differences between two views or layouts. This 
tool can be used effectively to compare the architectural documentation with the consultant’s drawings. 
 
Comparing Structural and Architectural Floor Plans with the Trace Reference 
The BIM workflow also allows the architect to find any collisions in the 3D model with the help of 3rd party model checker 
applications such as Solibri or Navisworks. Model checkers are mostly used to find collisions between the structural elements and 
the MEP systems, especially in large and complex buildings with extensive ductwork and piping layouts. 
 
 
78 
 
BIM Implementation Guide Page 78 
 
Collision Detection between the MEP Systems and the Load Bearing Structure 
DXF-DWG 
DXF and DWG are still the most common 2D drawing exchange format between architects and other disciplines. Changing data 
between different applications is never easy and there is always a chance for translation errors due to the conceptual differences 
between the programs. Since DWG file sharing is a necessity, ARCHICAD makes it possible to create configuration files, which filter 
attributes of file data during conversion. These DWG Translators can be associated with Publisher items in the Navigator. 
DXF-DWG Translator Setup 
The carefully developed DXF-DWG translator will ease the communication between the architect and the other parties during the 
entire design process. Defining and developing DXF-DWG translator files requires extensive knowledge of ARCHICAD and AutoCAD 
and the careful consideration of many circumstances: 
 Existing DXF-DWG standards in the office (layers, pens, fills, naming etc.) 
 Requirements of the partners (structural designers, engineers, facility managers, builders etc.) 
 Conceptual differences between ARCHICAD and AutoCAD: 
• No layers for doors and windows 
• No separate layers for composite structure skins 
• BIM model+Layout Book vs. model space+paper space 
• Pen weights vs. pen colors 
 Goals of the translation: 
 
 
79 
 
BIM Implementation Guide Page 79 
• For as is output (on printing or on screen) 
• For further editing and re-importing to ARCHICAD (attributes has to be preserved during the conversions) 
• Complete translation (attributes are completely changed) 
Most of the time, a single template file can’t fulfill all these needs. We recommend the use of fully customized DWG translator sets for 
different purposes. To avoid the incorrect DWG output, the translators have to be carefully named and documented in the company 
BIM guidelinesdocument and the proper translators have to be assigned to the DWG publisher items in the standard template files. 
Using DWG-DXF files in ARCHICAD 
There are three ways to incorporate DWG/DXF files into ARCHICAD Projects. The first is to Merge the DWG/DXF file. The second is to 
Attach the DWG/DXF file as an XREF file. The third one (available in ARCHICAD 10 and later) is to place the DWG/DXF file as an 
External Drawing. 
The following table shows the differences in the three methods: 
 Merge XREF Place as Drawing 
Attributes 
(Layers, Line types, Fill types) 
Yes, created during Merge Yes, created during Attachment 
(XREF layers are separated in the 
layer list) 
No attributes created 
Deletion of created Attributes Must be deleted individually When Detaching, all attributes can 
be deleted in one step. 
No attributes, no 
such problem. 
Can individual layers of the DWG/DXF 
file be turned ON/OFF? 
Yes Yes No 
Can file be placed in Model Views? Yes Yes Yes 
Can file be placed on Layouts? Yes No Yes 
Can file have its own Pen Set? No No Yes 
Can its elements be snapped to? Yes Yes Yes 
Can its drawing content be resized? Yes Yes Yes 
Can its contents be incorporated into 
and saved with the project? 
Yes, immediately becomes 
part of the project 
Yes, use Bind command in XREF 
Management Dialog Box. 
Yes, use Explode 
command. 
 
Based on the above table, the solutions for the most common scenarios/requirements are: 
 1. Cleanness of attributes. When a DWG/DXF file is Merged/Attached, dozens of attributes may be created. If you wish to 
avoid that (e.g. lots of Layers in the Layer Settings Dialog), use the Place External Drawing method. 
 2. Cleaning up created attributes. The XREF method is preferable to the Merge method, because when you Detach an XREF 
file from the Project, ARCHICAD offers to delete all attributes coming from the XREF file in one step. 
 3. Ability to turn Layers ON/OFF individually. When using the Place External Drawing method, all DWG/DXF data are 
handled as a single unit and are placed on a single layer. Therefore you should use either the Merge or XREF methods, so you 
can turn off the layers (and thereby control the visibility of those elements) individually. 
 
 
80 
 
BIM Implementation Guide Page 80 
 4. Placement on Layouts. XREF files may not be directly placed, so if you need to place DWG/DXF files onto Layouts, you 
should use either the Merge or the Place External Drawing method. (You can place them in Model Views with any of the 
methods.) 
 5. Use Pen Set from DWG/DXF file. If you wish to make the Pen Set of the DWG/DXF file part of the Project, use the Place 
External Drawing method. Then you can save the Pen Set of the Drawing generated from the DWG/DXF file. 
 6. Making DWG/DXF data permanently part of the Project File. The Merge method is the one, which immediately results 
in DWG/DXF data becoming part of the Project. An External Drawing must be exploded. As for XREF files, the Bind command 
is required to achieve the same result. 
IFC 
Industry Foundation Classes (IFC) is a universal language to interpret descriptions of 3D building model elements (for example slabs, 
walls, columns, beams etc.) between various software applications during the design process. In comparison to DXF, which is merely 
a graphic element format, IFC files also define the full properties of architectural objects, such as their 3D geometrical characteristics, 
materials and their relationship to other objects. 
 
Sharing the BIM Model via IFC 
The Industry Foundation Classes (IFC) data model is a neutral and open specification that is not controlled by a singular vendor or 
group of vendors. It is an object-oriented file format with a data model developed by the International Alliance for Interoperability 
(IAI) to facilitate interoperability in the building industry, and is a commonly used format for Building Information Modeling (BIM). 
The IFC model specification is open and available. Because of its focus on ease of interoperability between software platforms, some 
governments plan to make the use of IFC format(s) compulsory for publicly aided building projects. 
http://wikipedia.org/wiki/Industry_Foundation_Classes 
The IFC file is a text file providing 3D info, properties, relations, stories and all the project information. 
http://wikipedia.org/wiki/Industry_Foundation_Classes
 
 
81 
 
BIM Implementation Guide Page 81 
Advantages of using IFC 
Companies that have products supporting the IFC protocol enable you to rethink the way you solve common business problems. 
Benefits of using the IFC protocol can include: 
o Access object data for improved design and coordination in ARCHICAD --- getting a building service engineer’s HVAC 
ductwork or water piping layout as 3D objects 
o Export your design for analysis by another specialist --- such as a thermal analysis enabling better understanding of your 
building performance, or advanced visualization, analysis of the logic of the design etc. 
o Export a model for costing, estimation bidding or procurement --- the integrated nature of the IFC information makes your 
database more valuable because your information is easy to access and analyze by such packages as costing applications. 
For more details please read: 
http://helpcenter.GRAPHISOFT.com/?s=IFC&versions=version-18&redirect=ARCHICADwiki 
http://www.GRAPHISOFT.com/support/ifc/downloads/ 
Structural Design, Analysis and Production 
A building’s architectural design and its physical structure are closely interrelated: on one hand, the architectural design of the 
building defines the structure; on the other hand, the structural design of a building reflects the overall architectural design. 
As structure has become a visual and aesthetic part of the design in modern architecture, structures must be as light as possible 
while maintaining complete integrity. Also, the structure must be optimized for performance and price. 
ARCHICAD provides sophisticated design information along with the necessary level of model detail. This information can be directly 
imported through Industry Foundation Classes (IFC) or other special connection formats into specialized software to run structural 
analysis and design. 
 
Structural Analysis with bi-directional IFC Connection 
IFC allows the ARCHICAD model to be shared with major structural solutions such as Scia Engineer, FEM-Design, ETABS, TEKLA 
Structures, AxisVM or SAP 2000. 
For the complete description of ARCHICAD’s structural solution please read: 
http://helpcenter.graphisoft.com/?s=IFC&versions=version-18&redirect=archicadwiki
http://www.graphisoft.com/support/ifc/downloads/
 
 
82 
 
BIM Implementation Guide Page 82 
http://www.GRAPHISOFT.com/products/ARCHICAD/solutions/structural.html 
Structural Related ARCHICAD Features 
ARCHICAD advises tools and IFC specific settings to help in main segments of the architectural-structural model exchange. 
ARCHICAD offers a solution to view the simplified load-bearing structure of architectural models in Partial Structure Display. 
 
The Partial Structure Display 
Please note that the veneers of the ARCHICAD columns are not hidden when the ‘Core Only’ option is activated. 
In addition, layer settings can be customized in Layers and Layer Combinations. Settings of IFC export can be customized to save 
a structural view containing only the objects, which are important to structural engineers. 
 
Architectural vs. Structural Model 
Moreover, an analyzed structural model saved as an IFC file can also be read by ARCHICAD, and the new model can be compared 
with the original. The differences (for example modified position of walls, columns, increased/decreased thicknesses and sections 
etc.) can be visualized with the Trace & Reference tool. 
For the detailed description of the above features please read: 
http://helpcenter.GRAPHISOFT.com/?s=Partial+Structure+Display&versions=version-18&redirect=ARCHICADwikihttp://helpcenter.GRAPHISOFT.com/?s=comparing+structural+and+architectural+models&versions=version-18 
http://www.graphisoft.com/products/archicad/solutions/structural.html
http://helpcenter.graphisoft.com/?s=Partial+Structure+Display&versions=version-18&redirect=archicadwiki
http://helpcenter.graphisoft.com/?s=comparing+structural+and+architectural+models&versions=version-18
 
 
83 
 
BIM Implementation Guide Page 83 
IFC Based Structural Design Workflow 
If the structural engineer’s software application supports bidirectional IFC data exchange we recommend the following structural 
design workflow with ARCHICAD: 
1 The architect creates the initial architectural model in ARCHICAD with correct composite and profile core/other/finish 
settings. 
2 Using Layer Combinations, Display Options and the Partial Structure Display, the architect generates the simplified 
structural model in ARCHICAD 
3 The model is saved in IFC according to the previously set IFC export preferences 
4 The exchange file is opened and referenced into the structural application 
5 The structural engineer opens the exported IFC model in the structural application 
6 The structural engineer analyzes and modifies the structure 
7 The exchange file is updated from the structural application 
8 Structural changes are referenced into the BIM model 
9 ARCHICAD’s Virtual TraceTM technology allows the architect to visually compare the BIM model with the structural 
engineer’s drawings 
 
Structural Design Workflow with ARCHICAD 
 Note: depending on the analysis application and engineer’s need, you can publish the IFC model of the entire building from 
the 3D window, or story by story from layout floor plans using the Publisher. 
 
 
84 
 
BIM Implementation Guide Page 84 
Energy Analysis 
Sustainable architecture is the practice of designing, constructing and maintaining buildings in a way that their environmental 
impact is minimized. One of the most important aspects of sustainable design is energy efficiency - a drive to reduce the amount of 
energy a building consumes during its life span. 
To allow the direct analysis inside ARCHICAD, you can use the Energy Evaluation feature at any time of the design process, without 
exporting the model to an external application. This feature has been designed for architects and can be used from the early design 
phases to help them make the right environmental - and legal - design decisions concerning the building’s envelope structures and 
materials. 
To create certified energy evaluation, you can purchase EcoDesigner add-on, which fulfills the ASHRAE 90.1 2007 standard 
specifications as referenced by USGBC LEED Energy 2007. 
Energy Evaluation in Different Design Phases 
Depending on the complexity and phase of the design, you may follow different techniques to analyze the model. 
Early Design Phase 
In this phase, you know only soma basic information about the building, but you can validate the glazed surfaces on each side, the 
generic external building structures, the MEP equipment in some easy steps. 
4 First, define zones for each direction (east, west, north, south) the facades are facing to, and some others for the zones 
without direct connection to the façade. 
5 Now, place the zones to fill the external shell according to their function and position on each floor. 
6 In the Energy Model Review palette, define as many thermal blocks as needed for each direction and function, and assign 
the zones. 
7 In a 3D window, with the zones visible, run the Update Energy Model Review command to recognize the placed building 
structures. 
8 Set the MEP equipment in the Energy Model Review palette. 
9 Run the Simulation. 
Detailed Design Phase 
In this phase your model is more detailed, and contains basically all information required for the report. There are a couple of things 
you have to be aware of: 
 Use automatic zones. If there is no building structure between neighboring zones, use zone boundary lines. 
 Model Zones story by story 
 Zones in the same thermal block have the same orientation, no heat transfer between them, common temperature/humidity 
controls. 
 Correctly set Building Material u values. 
External Applications 
There are also dedicated applications available that can be handled by the professionals delivering energy analysis of the model, but 
these are developed for specialists. 
ARCHICAD provides relevant design information for energy analysis experts along with the necessary level of model detail. The 
ARCHICAD Virtual Building model may include thermal zones with openings, bounding surfaces with their respective U values, 
 
 
85 
 
BIM Implementation Guide Page 85 
exterior shading devices and building location and orientation information. This data can be accessed and used for energy analysis 
in different ways. 
 
Supported Energy Analysis Applications 
The industry standard Green Building XML format (gbXML) is recognized by several energy analysis applications such as Green 
Building Studio or IES. The ARCHICAD gbXML plug-in allows the architect to directly save the thermal zone model into gbXML 
format for further analysis in these tools. The add-on can be purchased on this website: 
ArchiPHYSIK (APH) is a stand-alone tool with a plug-in to ARCHICAD to estimate, calculate and optimize the physical properties of 
the building - such as thermal insulation and storage properties, vapor diffusion and acoustic damping. An API link between 
ARCHICAD and APH allows you to export the model geometry to APH, calculate physical properties and select the best building 
structures accordingly. The calculated data can be linked back into ARCHICAD. 
http://www.archiphysik.com/ 
ARCHICAD's support for IFC provides a link for professional building performance simulation software like EnergyPlus® or RIUSKA®. 
These tools are fully integrated building and HVAC simulation programs that dramatically improve the simulation of whole-building 
approaches in design, planning, and construction, and opens new doors for energy savings, cost savings and indoor environmental 
quality. 
http://www.granlund.fi/granlund_eng/frameset_tiedonhallinta.htm 
http://www.eere.energy.gov/buildings/energyplus/ 
Using ARCHICAD with all the above tools provides great benefits to both architects and energy specialists. Because the energy 
analysis tool can directly access ARCHICAD Virtual Building models, feedback on the energy consumption of the building can be 
obtained at any time during the design process. And ongoing changes to the design do not lead to any laborious reworking on the 
simulation side - manually adjusting the geometry of the building to keep up with the alterations - because the essence of a 3D 
model means all the data is up-to-date and immediately usable. Of course, without a Virtual Building the process will be more 
painful and inefficient. 
For more information on this topic please read: 
http://www.GRAPHISOFT.com/products/ARCHICAD/solutions/analysis.html 
http://www.GRAPHISOFT.com/products/ARCHICAD/ac12/solutions/ 
http://www.archiphysik.com/
http://www.granlund.fi/granlund_eng/frameset_tiedonhallinta.htm
http://www.eere.energy.gov/buildings/energyplus/
http://www.graphisoft.com/products/archicad/solutions/analysis.html
http://www.graphisoft.com/products/archicad/ac12/solutions/
 
 
86 
 
BIM Implementation Guide Page 86 
http://www.GRAPHISOFT.com/products/ARCHICAD/solutions/energize9_whitepaper.html#lp1 
http://www.graphisoft.com/products/archicad/solutions/energize9_whitepaper.html#lp1
 
 
87 
 
BIM Implementation Guide Page 87 
Chapter 7 - Project Management 
Folder Hierarchy 
It is important that all BIM project related files are stored in a dedicated and well-organized place. Less time is spent looking for files 
if their location is predictable and carefully documented. Although the BIM workflow significantly reduces the number of project 
files compared tothe traditional 2D CAD method, there are still many project related documents and external files that have to be 
managed during the lifecycle of a project. 
Naturally the folder structure may go through a few alterations, and may change significantly according to changing software 
features and requirements. The important thing is that a structure is developed and that it is consistently used. There are some 
general categories that should be addressed in the folder/directory structure. Folders are needed to house the following 
information: 
 Virtual Building File(s) (.PLN and PLP files) 
 Project detail files (.PLN, MOD, PDF, DWG, DWF, etc.) 
 Image Files 
 Externally created text or data file 
 Object Libraries 
 Project related documents 
Folder Structure 
The project folders should have a descriptive name, which follows an overall logic (e.g. project number, name, date). 
Each project has different files, which should be grouped and stored on a clear, central location. Beside the BIM project, there are 
other documents, such as schedules, specifications, mailing, administrative files, designer manual, printed documents, consultant 
files, etc. 
The project folder hierarchy should not be conceived as the structure of the design project. The design project --- the central project 
database file --- is a single, central information database, enriched and developed by the architects, engineers and consultants 
throughput the design-documentation process. 
All project files and folders should be located --- and regularly backed up --- on a central file server, except for the standard ARCHICAD 
Library folder, which should be located on each machine. This removes 90% of the library-generated traffic from the network 
The following structure shows the minimum folder layout for the Company Standards, which may be expanded as required. 
Each Company will have their own preferences, but the illustration below shows a minimum setup. 
Once a working company structure is agreed, duplicate the folder structure the following manner: 
 Copy the company directory, 
 Remove all the files and use this as a template, 
 Copy the folder, 
 Rename it for the next new job. 
 
 
88 
 
BIM Implementation Guide Page 88 
 Note: Organize information according to a certain order. One may choose to organize from the most generic information to 
the most specific. E.g.: the most generic piece of information may be the Project name and number. The next specific piece of 
information may be all the most generic functions to be performed during the life of the project, and so on. 
IT Infrastructure 
Before ARCHICAD is implemented in the office, the existing infrastructure such as hardware, software, and network solutions should 
be evaluated by the CAD and IT Managers. This process is even more critical if the company works with large projects on a regular 
basis. 
On the image below, a typical project IT environment is shown. 
 
Office Computer Network Chart 
 
 
89 
 
BIM Implementation Guide Page 89 
 
IT Inventory 
To provide a stable IT background for smooth ARCHICAD project workflow, the IT manager must review the currently available 
hardware and software infrastructure in the office. The IT inventory has to contain the following: 
Hardware 
 Current computer configurations (workstations/servers) 
 Printers, plotters, digitizers 
 Hardware component compatibility with ARCHICAD 
 Estimated cost of hardware changes 
 
 
90 
 
BIM Implementation Guide Page 90 
Networks 
 Scheme of the existing computer networks (intranet, remote synchronization) 
 Internal and external network capabilities to support the project sharing strategy (Teamwork, hotlinks, XREFs, etc.) 
 Available data synchronization solutions 
Software 
 Existing operating systems 
 OS compatibility with ARCHICAD 
 Data exchange formats and channels with other applications (e.g. structural, rendering) 
 Are there any additions needed for ARCHICAD (add-ons or libraries, etc.)? 
 Additional software to complete the project 
 Estimated cost of the new software 
Suggested Configuration 
Based on the results of the IT inventory, the firm may decide to buy new hardware to provide the best infrastructure for the new 
workflow. The hardware and software requirements of the latest ARCHICAD version can be found on the install CD and on the 
GRAPHISOFT website. For the currently shipping ARCHICAD version we recommend the following configurations: 
ARCHICAD Network Key Servers 
For an office using ARCHICAD network licenses, a CodeMeter key server machine has to be installed. This server has to fulfill 
relatively low hardware requirements: 
 The server should support the minimum HW requirements of the operating system 
 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, so 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 access it even if no one is logged into the server 
File Servers 
File servers are primarily used to store Teamwork files, company libraries, templates or any other materials that are required for the 
daily operation of the firm. File server requirements: 
 High storage capacity 
 Preferably redundant file storage (RAID) 
 Fast data access 
 Fast network connection to terminals 
 High stability and continuous operation 24/7 
 
 
91 
 
BIM Implementation Guide Page 91 
 GRAPHISOFT does not recommend using cross platform file servers in order to avoid any compatibility problems (e.g. 
Windows servers for Mac terminals or Linux servers for Windows terminals) 
ARCHICAD Workstations 
For ARCHICAD system requirements please read: 
http://www.GRAPHISOFT.com/support/ARCHICAD/system_requirements/ 
For the graphic card compatibility info, please visit: 
http://ARCHICAD-talk.GRAPHISOFT.com/compatibility.php?&sid=2b63e6ff812e4bd302b4ade3ba13c2c3 
 
The GRAPHISOFT Video Card Database 
Rendering and Visualization Workstations 
Rendering and visualization requires the most powerful computers. Luckily only a few of these special configurations are needed in a 
typical architectural office. 
Requirements: 
 RAM: 8-16GB (depending on the project size) 
 HD: Min. 10 GB of free space on the system volume 
 CPU: Fast multicore processors are highly recommended since most of the rendering engines (including Cinerender) and 
imaging applications support multiprocessing 
 Display: 19’ monitor or bigger (1280x1024 minimum screen resolution) 
 Graphic Card: Standard OpenGL card with 1 GB or more onboard video memory. 
BIM Server 
The BIM Server can run on the same physical computer as ARCHICAD. Though, it is more prudent to run the BIM Server on a 
standalone server. A standalone server is a machine dedicated to serving data to other machines. It mainly runs processes that do 
not need a user response, runs a special operating system (but does not necessarily have to), and has hardware better equipped for 
multiple user network traffic. 
It is recommended that the operating system be 64 bit, running either Mac OS X or Windows operating systems. 
Running the bare amount of memory on the BIM Server is unwise. 4 GB of memory is the least that should be considered for a 
small office and 8 GB is the minimum that should be considered for an average office. 
A safe rule of thumb 
Each shared project with at least one teammate joined will require between 1.5 and 5 times more physical memory (RAM) on the 
server than the original pln/plp took on the hard disk. How much memory used is file-specific. A 200MB project (pln/plp format) 
http://www.graphisoft.com/support/ArchiCAD/system_requirements/
http://archicad-talk.graphisoft.com/compatibility.php?&sid=2b63e6ff812e4bd302b4ade3ba13c2c392 
 
BIM Implementation Guide Page 92 
could use anywhere between 0.3GB and 1GB of memory on the server. This memory requirement for practical purposes is not 
dependent on the number of users accessing the BIM Server. 
The BIM Server is a multi-threaded application that from the start takes advantage of every core. 
The more physical cores there are the better. A small office should use at least a dual core machine for its BIM Server. Although with 
the costs of quad cores so reasonable it is hard to justify not starting with a better machine. 
Network requirements 
http://helpcenter.GRAPHISOFT.com/technotes/next-generation-Teamwork/network-specification/ 
Memory Requirements 
If a requested operation consumes a substantial amount of memory in ARCHICAD, the application’s responsiveness can drop 
significantly, thus making it impossible to work effectively with the project. Furthermore if ARCHICAD hits the limit of the available 
memory address space, the application and/or the operating system will most likely freeze or crash. To minimize the likelihood of 
these problems, we strongly recommend you buy the maximum memory that ARCHICAD can handle, in case you need to work with 
large projects (see below). The maximum memory that ARCHICAD can utilize depends on the Operating System and the available 
memory slots on the computer’s motherboard. 
Windows 8 
The 64 bit Windows OS supports up to 128 gigabytes (GB) of RAM and 16 terabytes of virtual memory. In this case the computer’s 
motherboard primarily determines the maximum physical memory. Currently ARCHICAD can address a maximum of 4GB out of the 
total memory. 
For more details about running ARCHICAD on 64 bit operating systems please read: 
http://helpcenter.GRAPHISOFT.com/technotes/operating-systems/compatibility-notes-to-ARCHICAD-on-windows-8/ 
Mac OS X 
The latest MAC OS is also a 64-bit system; therefore the same memory limitations apply as for Windows XP x64. A maximum of 4GB 
memory can be addressed from ARCHICAD. 
Data Safety 
The following section will outline methods that should be used to ensure the proper protection and storage of data. In addition, we 
will identify ways in which the users can integrate application-based settings with practical office procedures to ensure the proper 
safety of office information. In particular, standards for manual saving, Autosave and project archiving will be discussed. 
Saving 
Manual Saving 
The first step towards Data Safety is the typical manual save using either the Save command in the File menu or the 
Command/Control-S keyboard shortcut. ARCHICAD’s special Autosave feature allows that the last state of the project is 
automatically recovered and opened after any unexpected situations. Saving highly recommended after: 
 o Major modifications are made to the project; 
 o Tedious modeling operations are performed; 
http://helpcenter.graphisoft.com/technotes/next-generation-teamwork/network-specification/
http://helpcenter.graphisoft.com/technotes/operating-systems/compatibility-notes-to-archicad-on-windows-8/
 
 
93 
 
BIM Implementation Guide Page 93 
 o The creation of custom parts; 
 o Revisions are made to layers and combinations; 
 o Additions or alterations of stories; 
 o The creation of custom line types, fills, composites, materials. 
A manual save will update the project file, which is typically located within a project folder on the network server. 
 Note: After a manual save, you can no longer cancel recent operations. 
Autosave 
Autosave is NOT a replacement for saving; however, it can be help in such cases as: 
 o System crashes; 
 o Program crashes; 
 o Accidental file deletion. 
This feature is turned on by default in ARCHICAD and can be fine tuned in the Data Safety dialog box (Options > Work 
Environment > Company Standards Schemes). 
 
 
AutoSave and Backup Options 
ARCHICAD allows the user to Autosave either by the interval-based method (time in seconds) or the action-based method (steps). 
 Note: It is our recommendation that Autosave always be turned ‘on’ and that it functions on the action-based method set to 
each step but the last 10-15 steps in any particular project file. Timed Autosave can often be distracting and disruptive, as the 
file will be saved at the specified time interval regardless of progress. ARCHICAD places the Autosave document into the set 
folder. Be sure to have enough free space in the selected volume. It is also important to understand the limitations of the 
 
 
94 
 
BIM Implementation Guide Page 94 
Autosave feature as compared to the manual save. You should be aware that the Autosave document might be older than 
the last saved plan file. 
 Note: To avoid data loss, we suggest that whenever ARCHICAD starts with the Autosave dialog box, open the presented file 
and immediately save it under a different name. Then compare it to the original project file and keep the most recent file. 
 Note: Get into the habit of saving whenever you are interrupted, when the phone rings, when you go for coffee etc. 
You can read more about Autosave on this website: 
http://www.onland.info/archives/2006/01/ARCHICADs_autos.php 
File Backups 
File backups can be activated via the Options > Work Environment > Company Standards Schemes > Data Safety dialog box 
within ARCHICAD. If the Make Backup Copy option is checked, ARCHICAD will make a file with a .BPN extension. These files will be 
updated upon each manual save and will contain the previously saved version of the project. 
 Note: Using this feature doubles the disk space needed for storing a project. We recommend deleting all backups at major 
system backups (i.e. weekly or monthly). There should also be a daily incremental backup, saving the day’s work and thereby 
allowing the previous day’s backup to be safely deleted where disk space is a concern. All backup files can be deleted after 
completing the project. 
Another way of making ARCHICAD file backups is via file iterations. Before major changes to a project are made, a duplicate file can 
be created and renamed. These files can be stored locally to minimize server storage space and to ensure that other team members 
do not work in the wrong file. These progress copies provide a record of the project’s changes and offer a means to retrace steps. 
The Teamwork function of ARCHICAD contains yet another set of backup options. 
Archiving 
The archiving of model files and project layouts can be done at any time and for many purposes. Typically, archives are performed at 
milestones such as: 
 o The close of project phases; 
 o Authority, Cost Plan, Permit, Bid or Tender Sets, i.e. where it is necessary to have digital backup of legal documents; 
 o Significant design changes; 
 o Predetermined calendar intervals; 
Archived files can be stored on specific server partitions, CD or other removable disk media, tapes, or even FTP sites. 
The ARCHICAD Archive File (.PLA) 
A .PLA is an ARCHICAD archive file that binds together the Virtual Building model, library parts, background images, properties and 
textures for a project. It is created through File > Save As> ARCHICAD Archive Project (.PLA). Since the PLA files contain all of the 
necessary information for a project as defined by the user, they allow for these projects to be worked on in the future without the 
need for old libraries, textures, etc. This is useful for: 
 o Long-term phased projects; 
 o Project additions and renovations; 
 o Uncompleted or halted projects; 
 o General archiving. 
In the Archive Options dialog box, there are several check boxes that define the contents of the .PLA, which is to be created. 
http://www.onland.info/archives/2006/01/archicads_autos.php
 
 
95 
 
BIM Implementation Guide Page 95 
 
ARCHICAD Archive Options 
The six checkboxes generally do two things --- they provide flexibility should an archive need to be revisited for future work; and they 
increasefile size. Obviously, the more pieces that are included within a .PLA, the larger that file will be. To maximize flexibility while 
minimizing file size, you should decide the intended future use of the archive, and then define the file’s parameters. 
Note: If files are being archived for general backup purposes and for record copies, it is recommended to save the archive with all 
boxes checked except Include All Parts of Loaded Libraries. 
Once the project is closed the final archive has to be created. It’s crucial that the archive project files and their content can’t be 
changed or lost accidentally. Therefore we suggest the following actions taken: 
 Keep the project archives on a high data safety server (e.g. RAID servers) 
 If the files are available on a public server, it might be useful to set their status to read-only 
 Save multiple copies of the archives on CDs or DVDs 
 Embed all drawings in the archive file and set their status to Manual Update in order to reduce the chance of making 
accidental changes to the document 
The option ‘Include All Parts of Loaded Libraries’ should be reserved for when the archiving is being done to aid transportability or 
when creating a library .PLA. Archiving a file adds portability to projects, allowing them to be worked on in remote locations and 
minimizing the burden of conflicting or missing library parts. Examples of remote locations could be a firm’s satellite offices, 
interactive design sessions with clients, or remote collaboration over the web. A .PLA could be uploaded to an FTP site, allowing 
remote users to access a project, while simplifying the library loading aspect of sharing files. 
With the use of ‘Include All Parts of Loaded Libraries’ comes the ability to extract all of the parts used within a project, which is 
particularly useful during a software update and/or library transition. 
Keeping entire superseded libraries on the network can deplete server space and complicate library navigation. In addition, using 
old parts within new projects makes maintenance extremely difficult. 
 Note: It is our recommendation that when a library is replaced, a new library be created, saved as a .PLA, then all active 
projects using the original library be opened and loaded with the new library. 
Archiving in PDF/PDF-A Format 
Over the course of time, PDF has become the most popular generic document format. The PDF file format is now widely used in the 
architectural office to make backup copies of the entire documentation set. This solution is also recommended in the BIM office 
since the PDF files are compact in size and fully accessible and printable with free applications. It is also a way of protecting your 
 
 
96 
 
BIM Implementation Guide Page 96 
intellectual rights when issuing drawings at any stage of the design process because the recipient gets a non-editable document of 
the project. ARCHICAD Publisher allows the export of the entire documentation set into PDF format with just one click of the mouse. 
 
Entire Documentation Sets can be merged into One PDF File 
Printing and Plotting 
Both Printing and Plotting are available in ARCHICAD. Since ARCHICAD 10, Printing and Plotting have been brought onto a ‘common 
platform’, which resulted in the Print and Plot dialog boxes becoming similar to each other. However, there are still differences 
between Printing and Plotting. 
Updates & upgrades 
GRAPHISOFT updates the currently selling ARCHICAD version and its standard library parts on a regular basis. According to 
GRAPHISOFT’s development policy, new ARCHICAD versions are released every year. The management of ARCHICAD updates and 
upgrades is an important part of the BIM manager’s task, and requires close cooperation with IT managers and Project leaders. 
ARCHICAD Updates 
ARCHICAD can check the availability of new updates automatically or manually. For automatic checking you should enable the 
Check for Updates option in Options > Work Environment > Web Options. 
 
 
97 
 
BIM Implementation Guide Page 97 
 
ARCHICAD Update Options 
Check for Updates: Check this box if you want to be notified automatically, when starting ARCHICAD, if a new ARCHICAD or Library 
update (Hotfix) has become available. You will be notified with an on-screen alert if the Check for Update function is running. This 
function only works if you have a live internet connection. 
 Note: The Check for Updates does not download anything to your computer automatically. It only provides a notice that such 
a download is available. Check for Updates will provide automatic information about your ARCHICAD version to the 
GRAPHISOFT website. These data are limited to the data needed in order to update; they include no personal information. 
Clicking on the Check Now button allows you to instantly check the availability of ARCHICAD updates. Alternatively you can access 
the update website from Help > Check for Updates. 
It’s our recommendation to keep the Check for Update option turned on in small to medium firms where users are working alone or 
sharing the same project. In large companies with multiple projects running in parallel, we recommend the automatic update to be 
turned off. In firms of this size, the BIM manager and the IT Department have to be responsible for distributing the updates among 
the project teams. To keep the project files consistent it’s crucial that all team members are using the same version of ARCHICAD and 
libraries; thus the updates have to be installed and managed centrally by the BIM manager. 
Library Hotfixes 
Similar to ARCHICAD updates, GRAPHISOFT regularly submits fixes for the Standard ARCHICAD libraries. The Automatic Update 
function will also check the availability of new libraries if the Library option is checked in Options > Work Environment > Web 
Options. 
It is recommended that the BIM manager test the library update on the running projects before it is installed on the users’ machines. 
Project migration 
Usually the lifecycle of a project is longer than the yearly release cycle of ARCHICAD. Whenever a new ARCHICAD version becomes 
available, the BIM manager has to decide whether the project needs to be migrated or can be completed with the original 
ARCHICAD version. Project migration is recommended in the following cases: 
 There are new features in the latest ARCHICAD version that can help to finish the project faster and easier 
 Bug fixes or corrections in the new ARCHICAD version or library that were causing problems with previous ARCHICAD 
versions 
 Difficulty in maintaining multiple ARCHICAD versions in the office 
 Consultants or other teams need the project files in the latest ARCHICAD format 
If none of the above factors apply, it might be worth completing the project with the originally used ARCHICAD version. However, 
we suggest the following procedure to be followed during the migration: 
 The running projects should be transferred to the latest version of ARCHICAD consecutively. It’s not recommended to 
upgrade all projects at once. 
 
 
98 
 
BIM Implementation Guide Page 98 
 The first migrated project should be the least urgent one, so that you can spend enough time on experiencing the new 
features of the latest ARCHICAD version and to find the best migration workflow that later you can apply to other projects. 
 It’s very important to appoint somebody in the office who will be responsible for managing the migration process in the 
team. 
 Depending on the ARCHICAD version you are using and the version you wish to upgrade, it might be necessary to use an 
intermediate version of ARCHICAD to save all project files and libraries. 
 There are two areas that require special attention during the migration. 
• Libraries: We recommend to use the ARCHICAD subset libraries and to upgrade the office standard library and the 
project library to the latest version. 
• Hotlink Modules: make sure that the hotlink pathswill be converted correctly. 
 We recommend summarizing the results of the first project migration in a migration guide that will be published for the other 
project teams. 
We recommend the following safety steps before the project migration: 
 Keep the old ARCHICAD versions and project files for safety reasons. Versions as far back as version 10 can be kept because 
they use the same hardware key as ARCHICAD 19. 
 Update the office library and the project-specific library for the new ARCHICAD version 
 Load the old ARCHICAD library and the subset library of the new version 
 The BIM manager has to test the results of the project migration before the entire team switches to the new version 
 
 
 
99 
 
BIM Implementation Guide Page 99 
Chapter 8 - Best Practices 
This chapter presents solutions to common problems faced by large practices. Most of the issues described below are typical for 
large and complex projects such as increased file size and slow regeneration of drawings. 
Please also refer to the ‘Troubleshooting’ page of the ARCHICAD Wiki for further information: 
http://helpcenter.GRAPHISOFT.com/?s=Troubleshooting&versions=version-18 
Modeling Strategies 
Model Types: 
 Conceptual 
 BIM 
 Visualization 
 Civil Model 
 Architectural Model 
 Structural Model 
 MEP Model 
 Construction Model 
 Coordination 
 As-built Model 
This chapter helps answering the following questions: 
 How far should you go with modeling? 
 Productivity vs. LOD 
 Creative use of AC modeling tools 
Large Projects 
The size and complexity of projects and other important factors, like short deadlines or big project teams, can significantly influence 
the workflow of design and documentation in an architectural office. To find the most effective ARCHICAD approach for your 
practice requires experimenting and refining your working methods. 
What 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 
There is no exact definition of what makes a building „big’, but we recommend that the following project attributes are carefully 
assessed so that you can find the best approach in ARCHICAD: 
 
http://helpcenter.graphisoft.com/?s=Troubleshooting&versions=version-18
 
 
100 
 
BIM Implementation Guide Page 100 
 3D Polygon count 
 File size 
 Layout book size 
 Team size 
 No. of stories 
 Floor plan area 
Polygon Count 
Too many 3D polygons in the ARCHICAD model can significantly slow down regeneration times and in the worst case can freeze 
ARCHICAD. The limitation on 3D polygons depends on many factors including computer memory, graphic card memory and the 
type of active 3D window (internal engine, OpenGL, rendering, section/elevation, etc.). For a detailed description of ARCHICAD’s 
memory requirements please read chapter 5.2. 
Generally speaking we’ve confirmed that more than 200,000 polygons produce a big model in 3D views, and you have to make 
sure that your computer’s hardware configuration is suitable for the project. Projects with more than 2 million polygons can 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 a big building. In many projects a significant 
proportion of the 3D polygons are generated from library parts. The model of a room interior can easily contain as many polygons as 
a multistory building if the room is furnished with very detailed GDL objects. Please read chapter 7.2.3 for advice on how to limit and 
optimize the polygon count. 
Project File Size 
It is very important to control the size of the project files to keep the project up and running, especially in a Teamwork environment. 
See the next sections for advice on how to curb file size. The file size values in this document refer to the uncompressed ARCHICAD 
file size. The following project elements can extend the file size by tens of megabytes so it’s highly recommended to purge the 
unused ones from the project: 
 Sections and elevations 
 High resolution pictures placed on the floor plan, image fills 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 
An alternative way to reduce the file size can be applied only for those projects that contain many sections and elevations. The 
drawback of this solution is that live sections will be set to manual update, and the section dimensions will lose their association with 
the BIM model. The process is the following: 
 Open the Auto Rebuild Sections and Elevations and check the status of the already existing dimensions. If they are associative 
to the model (which is normally the case), select them all and set their status to Static Dimension in the Dimension Selection 
Settings dialog box, or else you’ll lose them after the process is finished. 
 Select the Auto Update Sections and Elevations in the Navigator and set them to Manual Update 
 For each view, turn off all the model layers and keep only the drawing layers active (those on which the drawing elements are 
placed) 
 Manually update all the above views in the Drawing Manager. Since all model layers are turned off now, this step will erase 
the model data from the Section Elevation views, which can be surprisingly big in a large or complex project. 
 
 
101 
 
BIM Implementation Guide Page 101 
Layout Book Size 
Several layouts in one ARCHICAD project can greatly increase the file size, and if there are too many auto rebuild drawings the 
update process for the entire Layout Book 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 were divided into multiple PLN or PMK files. User experience shows that 
for 50-100 layouts it’s worth separating the documentation from the model file. This way the documentation team can work 
independently from the design team. If the number of layouts exceeds 100 we suggest subdividing the documentation into two or 
more files. 
Number of Stories 
Designing high-rise buildings in ARCHICAD creates the following issues: 
 Many drawings need to be created and maintained in the Layout Book 
 Typical stories should be generated automatically from the master floor 
 Due to the complex nature of these buildings, many polygons are usually generated in the 3D model 
Considering these points we recommend that projects with more than 20 stories require special attention from the project leader 
and the BIM manager. In the case of more than 50 stories it’s very likely you will have to divide the project by different stories (e.g. 
basement levels, entrance level, typical floors, etc.) and make a separate model file of the whole building for visualization purposes 
containing only the most important visible elements. 
Summary 
The following table gives you a short summary of the previous chapter. 
 Size is big Size is critical Solutions 
3D Polygon Count 500.000-1M 3-4 M 1. Reduce the polygon 
count. 
2. Split the project file into 
smaller parts 
Project File Size 
(Compressed) 
400-500 MB 1-2 GB 1. Divide the project into 
smaller parts 
2. Separate the 
documentation from the 
model file 
Layout Book Size 50-100 
layouts 
200 > 1. Separate the 
documentation from the 
model file 
2. Subdivide the 
documentation into 
multiple files 
Team Size 10-20 40-60 1. Split the project into 
smaller parts 
2. Combine the Teamwork 
 
 
102 
 
BIM Implementation Guide Page 102 
file with hotlink modules 
Number of stories 20-40 100> 1. Makea separate model 
of the whole building for 
visualization containing 
only the necessary 
elements 
2. Split the project into 
smaller parts (e.g. 
basement levels, typical 
floors etc.) 
 
Hardware requirements 
http://www.GRAPHISOFT.com/support/ARCHICAD/system_requirements/ 
http://helpcenter.GRAPHISOFT.com/technotes/setup/hardware-compatibility/recommended-hardware-for-GRAPHISOFT-
products/?redirect=ARCHICADwiki 
http://helpcenter.GRAPHISOFT.com/technotes/setup/software-technologies/multiprocessing-and-
ARCHICAD/?redirect=ARCHICADwiki 
http://helpcenter.GRAPHISOFT.com/?s=Video+Cards+For+ARCHICAD 
 
ARCHICAD Version Operating system Max memory ARCHICAD can use 
ARCHICAD 19 for 
Mac 
Mac OS X 10.10 or 
later 
17,179,869,184 GB (theoretical) 
depends on Operating System and 
Hardware 
ARCHICAD 19 64-bit 
for Windows 
Windows 64-bit 17,179,869,184 GB (theoretical) 
depends on Operating System and 
Hardware 
 
Speed Issues 
3D Rebuild and Navigation 
The 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: 
 not enough physical memory available to complete the 3D operation 
 the OpenGL card doesn’t have enough RAM for 3D navigation 
Both hardware requirements depend mainly on the 3D polygon count of the ARCHICAD model. One can easily draw a building on 
the floor plan and in the section windows, which cannot be visualized in 3D due to the excessive number of polygons. 
http://www.graphisoft.com/support/archicad/system_requirements/
http://helpcenter.graphisoft.com/technotes/setup/hardware-compatibility/recommended-hardware-for-graphisoft-products/?redirect=archicadwiki
http://helpcenter.graphisoft.com/technotes/setup/hardware-compatibility/recommended-hardware-for-graphisoft-products/?redirect=archicadwiki
http://helpcenter.graphisoft.com/technotes/setup/software-technologies/multiprocessing-and-archicad/?redirect=archicadwiki
http://helpcenter.graphisoft.com/technotes/setup/software-technologies/multiprocessing-and-archicad/?redirect=archicadwiki
http://helpcenter.graphisoft.com/?s=Video+Cards+For+ARCHICAD
 
 
103 
 
BIM Implementation Guide Page 103 
The memory consumption at rendering depends on various factors, and the number of polygons 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 polygon count 
increases, the next symptom will be the slow conversion to 3D and the unbearably slow navigation in the 3D window, especially 
when the entire model is visible. 
If the model contains approximately 3-4 million polygons, three-dimensional navigation is impossible and the render projection 
outputs a blank image. Where the model contains more than 4 million polygons, there’s a high likelihood that the application 
crashes. These limits, of course, are highly dependent on the hardware configuration, and other specific circumstances, so they 
cannot be determined exactly. 
The conclusion is that for big buildings it’s essential to keep the model’s polygon count in an acceptable range. The following 
chapters will give you useful tips for how you can reduce the number of polygons within your projects. 
The PolyCount add-on 
PolyCount is an ARCHICAD goody add-on that helps to analyze and control the number of 3D polygons in ARCHICAD models. This 
tool can be used if the project size, or the limited physical memory of your computer, makes the 3D model size a critical factor in 
your modeling decisions. PolyCount can display the number of 3D polygons grouped by element types (walls, slabs, doors, windows, 
objects etc.) and also their percentage compared to the complete model size. 
The add-on also allows you to change the 3D detail level of certain library parts in your projects. Most objects in the ARCHICAD 
library include a ‘3D Detail Level’ parameter with options for ‘Detailed’, ‘Simple’ and ‘Off ‘representations. The ‘Set Level of Detail’ 
function allows you to toggle between these values. 
The PolyCount add-on can be downloaded by clicking on the ‘Goodies’ link in the ARCHICAD ‘Help’ menu. After successful 
installation the PolyCount menu can be activated from Window/Palettes/PolyCount. 
 
 
104 
 
BIM Implementation Guide Page 104 
 
The Interface of the PolyCount add-on 
How to Reduce the 3D Model Size 
The following tips and tricks can help you to keep the model size in a controllable range: 
 Make Layer Combinations: They allow you to show only those elements of the 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 off all the elements that are located in the building’s interior so they can’t be seen. Other 
layer combos can be defined for internal renderings or sections where the external trees, vehicles or other environmental 
elements are all hidden. 
 Use the Marquee: Where you need to create a section, elevation or rendering of only a small part of the building (e.g. a room 
or a story) select it with a marquee. This simple trick can speed up the navigation in 3D views. 
 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 2D symbols) has a representation in three dimensional views even if you only intend to show them 
on the floor plan. Moreover many of these elements generate a considerable number of polygons in 3D. You can overcome 
 
 
105 
 
BIM Implementation Guide Page 105 
this by turning off their 3D representation with the corresponding parameter on the object’s parameter list. Since all library 
parts in the ARCHICAD library have the same parameter name for this function you can select multiple objects on the floor 
plan and collectively turn off their 3D. You can also use the ‘Set Level of Detail’ function of the Polygon Count add-on for this 
purpose. 
 Control the Objects’ Level of Detail: Most library parts in the ARCHICAD library have a parameter for 3D detail level (simple, 
detailed, off) and curve resolution. Set these parameters to the minimum possible that is appropriate for the required 3D 
view. Too many segments in a curved shape can greatly increase the number of 3D polygons in a model. In some cases you 
can get better representation of the object with fewer polygons if you keep the 3D Detail level on ‘detailed’ and set the curve 
resolution lower. 
 
Library Part Detail Options 
 Avoid Using Memory-Intense Library Part Options: Some optional features of ARCHICAD objects can generate a 
significant number of 3D polygons without producing noticeable differences on the final drawings. Use the 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 on plant objects 
 
Door Handles can Greatly Increase the Number of Polygons 
 Pay Attention to Complex Modeling Elements: Advanced modeling tools such as Curtain Walls, Morphs, Shells and 
Complex Profiles or solid operations can produce considerable numbers of 3D polygons. Typical issues are: 
• Detailed or curved Curtain Wall frame profiles 
• Detailed Curtain Wall Accessories (e.g. shaders) 
• Complex profiles with many line segments 
• Solid operations between curved elements 
 
 
106 
 
BIM Implementation Guide Page 106 
• Lots of solid operations between model elements 
• Detailed Morph geometry (typically objects converted from other applications) 
 Check the Model with Polycount: This handy tool can identify elements of the model with too many 3D polygons. In 
addition to the previously mentioned library parts, other problematic elements can be: 
• Complex Mesh models(e.g. site model) 
• 3D people, plants and vehicle objects. Particularly elements imported from 3D Studio, which are usually very detailed 
models, intended for use in high-end renderings instead of architectural visualizations. 
 Filter the Content of the 3D Window: Use the Marquee Tool and define Layer combinations to display parts of the project in 
3D. You can also use the ‘Filter elements in 3D’ option to define which stories should be displayed in 3D. 
 
The Filter and Cut Elements in 3D Dialog 
To show the effect of different parameters, the following table shows the polygon count of some ARCHICAD library parts. Note that 
one ‘Man Hands in Pocket’ object generates as many polygons as 1066 walls! A further example that underlines the importance of 
polygon reduction is another office chair (Office Chair 01), which with the default settings has 3759 polygons in 3D view - the 
equivalent of 626 walls. Typically there are many instances when this type of object is placed in an office project. 
Element Type 3D Polygon Count 
Wall without opening 6 
Wall with empty opening 10 
D1 Door 80 
D1 Door with handle (Style 1) 1544 
Basin 01 (Detailed) 1031 
Basin 01 (Simple) 685 
Basin with tap (Detailed) 1335 
Basin with tap (Simple) 869 
Man Hands in Pocket 6396 
 
 
107 
 
BIM Implementation Guide Page 107 
People Bitmap 1 1 
Office Chair 01 (Simple) 2594 
Office Chair 01 (Detailed, Resolution=8) 3759 
Office Chair 01 (Detailed, Resolution=16) 7433 
Car 01 5583 
Vehicle Bitmap 1 
Straight StairMaker stair with ‘Post with 
Baluster’ railing 
2093 
Straight StairMaker stair with ‘Simple 
Surface’ railing 
789 
 
Sections and Elevations 
Another area to consider in 3D views is section/elevation and detail database handling. If a project file has a considerable number of 
sections/elevations or details, then error messages might occasionally appear during open, save and rebuild processes: „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 limit cannot be specified exactly because it also depends on the model complexity. As a rule of thumb we can say that the 
number of section/elevation and detail windows should be kept below 200. If the project documentation contains hundreds of 
independent detail drawings, it is highly recommended to keep them in a separate PLN file. With the help of the Trace Reference 
function, the live views of the main model can be overlaid on the 2D detail drawings so the documentation and the BIM model can 
be kept consistent during the entire lifecycle of the project. This work sharing method also allows the detailing team to work 
independently from the modeling team. 
The other consequence of having an excessive number of these views is the file size bloat. Project files with extremely complex 3D 
models usually have a reasonably small file size (20-30 Mbytes) if the number of sections and details is limited, while a similarly 
complex project file can easily exceed hundreds of megabytes if, for instance, there are more than a hundred section and detail 
views. 
Large files also have a negative effect on the section-elevation rebuild time. Prior to section-elevation generation, ARCHICAD runs a 
pre-filter on the floor plan with the consequence that an invisible 2D view is created. This process can be significantly slower where 
the floor plan is big or contains slow-to-rebuild library parts. 
Manual rebuild of sections and elevations can significantly reduce the regeneration time of the View Map and the Layout Book in 
case of very large projects. 
 
Manual vs. Auto Update Options 
The downside of this solution is that the project views have to be updated manually before the Layout Book is published. 
When working, always use one section or elevation as your working window and move it around from area to area as you need to 
update and manage the model. Many users simply create a new working section whenever they need to. This leaves a lot of unused 
 
 
108 
 
BIM Implementation Guide Page 108 
section and elevations, which do not contribute to the model or the documentation and bloat the file. The same applies to detail 
windows. 
Do not copy a generated Detail, Section or Elevation and paste it in the same window. Following this practice may easily double the 
file size without any benefit. 
 Rendering 
Reducing the number of polygons with the techniques described above helps in two ways with photorendered views: 
 The generation of the 3D view is quicker 
 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 surfaces will result in 
faster renderings. The following techniques can be used: 
 Turn off the shadow casting for those library parts that don’t generate noticeable shadows in the view. There is a dedicated 
parameter for this purpose in every ARCHICAD library part. 
 
Shadow Casting Option for Library Parts 
 Use texture mapping and the alpha channel effect instead of physical models. This trick can save precious rendering time for 
trees, vehicles, fences and other complex objects when needed in the photo rendered image. 
 
 
109 
 
BIM Implementation Guide Page 109 
 
Alpha Channel Effects 
 Reduce the number of light sources to the minimum possible. Too many light sources can result in significantly slower 
renderings. 
 Turn off shadow casting for brighter lights. 
Floor Plan Regeneration 
Drawing on the floor plan also has its restrictions, but these are much harder to describe than is the case with 3D views. While 
ARCHICAD is capable of manipulating 500,000 visible elements on the floor plan, a more realistic number would be 100,000 for an 
average construction plan. Although ARCHICAD will not crash or write enormous files with more then 100,000 elements, the 
responsiveness will be unacceptably slow even on the best performing hardware configurations. Note that more time will be taken 
to redraw the drawing if you zoom out from a smaller part of the project to the drawing extents. Also remember that the floor plan 
rebuild time influences the speed of the section-elevation regeneration as described previously. 
Please utilize the following advice: 
 Use layer combinations to control the content of the floor plan. 
 
 
110 
 
BIM Implementation Guide Page 110 
 Use bitmap fill representations instead of vectorial fills. Unless you need to print a drawing, select the bitmap fill 
representations from the On-Screen View Options dialog, as it is regenerates faster than vectorial fills. 
 
Turning off the Vectorial Hatching 
 Avoid using symbol fills. Symbol fills can greatly increase the floor plan redraw time especially if the fill pattern contains many 
line and arc segments. 
 
Symbol Fills May Contain Many Line Segments 
 Use PROJECT2 commands in library parts only if really necessary. These require the 3D view of the object to be generated for 
the creation of the 2D symbol thus making the floor plan redraw unreasonably slow. 
 Use a Symbolic 2D representation for static library parts without scripting the floor plan symbol. 
 Using the Contours Only and Symbolic Cut options can increase the regeneration speed of basic model elements such as 
walls, roofs and columns. 
 
Simplified Floor Plan View Options 
 
 
111 
 
BIM Implementation Guide Page 111 
 It is common to have maps scanned and placed Worksheets in ARCHICAD Projects. Bitmaps can also be placed into any 
window with the Figure or Drawing Tools. Watch the size of these bitmaps, as large ones can slow down redraw in these 
windows. 
Lines/Arcs comingfrom DXF/DWG Files 
Since most people using AutoCAD are working in 2D, a large number of lines can be accumulated in a single DXF/DWG file. 
Sometimes when data is read, more complex elements (BLOCKs - Library Object-like elements in AutoCAD) may be broken down 
into Lines/Arcs. Sometimes fill patterns are broken down into their primitives. This could cause data coming from these formats to 
contain up to tens of thousands of lines/arcs, which can considerably slow down your work speed in ARCHICAD. You can check this 
with Find & Select. One useful thing is to establish with consultants the format of files required by your office (e.g.: no fills, please). 
Also, it can be helpful to convert BLOCKs to ARCHICAD Library Objects, as it will prove to be a lot faster if the DXF/DWG drawing 
contains many BLOCKs. 
The Translator in the latest ARCHICAD versions also allows the intelligent conversion of AutoCAD hatches and dimensions into 
ARCHICAD fills and dimensions. 
 
Symbol Fills can be Exported to DWG as ‘Solid’ elements 
Exploding these elements into ARCHICAD lines should be avoided, as it can significantly increase the size of the PLN file. 
Morphs and Shells 
In ARCHICAD, it is very easy to model sophisticated organic surfaces using the Morph and Shell tools. Shells can have complex profile 
geometry and you can convert any elements to Morphs to freely edit the geometry, as you need. It is very easy to reach the critical 
polygon number accidentally, so we recommend, that you open a new empty file and copy the elements there to perform the 
Morph conversion, and check the polygon number before using these elements in the active project. 
Curtain Walls 
Curtain Walls are very flexible elements you can use to model large glazed structures, ceilings, tiling and so on. You are also able to 
model the frames and panels to the finest details, but keep in mind, that the large number of elements may also cause polygon 
overload. If the structures are visible only in large scale and far from the camera in 3D, consider simplifying the profiles to rectangular 
elements for example. 
Embedded Groups 
Grouping is a very useful productivity feature to handle elements together. However, if you have too many groups embedded in 
each other, editing an element deep in the embedding hierarchy can slow down the project. (For example, you furnish a canteen 
area, so you group chairs around a table, then the table with the chairs around, then a row of tables and chairs in the arrangement, 
then all in one room, and so on… And then, you want to edit a chair with Suspend Groups On.) 
GDL Objects 
The more complicated Library Objects are used, the more time it can take for the program to handle them. When 
creating/programming GDL Objects, you can control how complex an Object will be. Curved surfaces (with high resolution of 
 
 
112 
 
BIM Implementation Guide Page 112 
Objects using the RESOL command), extensive use of GDL Global Variables, large arrays, very complex structured scripts, and many 
file input/output operations are some factors that can make GDL Objects slower. A large number of Zones placed on the Floor Plan 
can also be a slowing factor (Zones are generally complex and have many built-in Global Variables). 
API Add-Ons 
Extremely sophisticated Objects and operations can be created and performed with ARCHICAD’s API interface. However, these could 
also affect speed, as they essentially have direct access to the ARCHICAD Project Database. So they can actually use up a lot of 
processor time to do their own tasks. It is a good idea to load only Add-Ons you need. For example, if you have an Add-On that 
creates skylights in roofs, you can unload it if your building has a flat roof. As with attributes, you can always load it when you need it. 
Project Sharing Strategies 
It is recommended that the project leader or the BIM manager define the project sharing strategy prior to the start of the new 
project. The project sharing document has to describe the hierarchy, name, location, ownership and the content of the various 
project files. Naturally as the project evolves and more people are involved in the job the project sharing concept has to be fine-
tuned to best serve the needs of the increased team. Since ARCHICAD supports different team working methods, the project sharing 
concept can be flexibly changed to best match the actual project. The size, complexity and type of the project as well as the size of 
the project team all have to be considered to find the most effective project sharing strategy. Let’s illustrate the various project 
sharing capabilities of ARCHICAD with two examples. 
Example 1 
The first project is a hospital building that is composed of four well-separated units. Since each unit is different in size, shape and 
function, the logical setup is to divide the BIM model into four separated parts. Each unit is saved as a standalone Teamwork file 
(PLP), so four independent project teams can work in parallel without disturbing each other’s work. In addition to the hospital unit 
modules, a separate TW file is created to accommodate the site plan model. The files are hotlinked into the main project model file 
that stores the entire building model. Furthermore, the individual units can be temporarily hotlinked to ensure the correct 
connection between them. The main project model is also a Teamwork file, which is managed by the project architect and the BIM 
model manager. Since the project has a very extensive documentation set that would significantly increase the size of the model file, 
the Layout book is stored in a single Teamwork File. This solution also allows the documentation team to work independently from 
the modeling team. The drawings are exported as individual PMK files into the Layout Book file in order to reduce the time needed 
for the update the entire documentation. 
 
 
 
113 
 
BIM Implementation Guide Page 113 
 
Project Sharing Example 1 
Example 2 
Our second project is a high-rise office building that consists of two towers. There are completely identical typical floor plans used 
on most of the stories moreover there are typical office units planned across the whole building. There are similarities and 
differences in the applied project sharing solution compared to the first example. Just like in the first case, there are individual 
Teamwork files used to host the site plan, the main project model and the Layout Book. What is special to these types of projects is 
that the typical stories are contained in a module file that is hotlinked to the main model file. Furthermore the typical office units are 
also saved as modules and hotlinked to the typical floor module, resulting in a multiple level hotlink hierarchy. Finally the external 
shell and the core of the building are separated in a standalone Teamwork file, so that the modeling and visualization team can work 
on a significantly smaller 3D model. 
 
 
114 
 
BIM Implementation Guide Page 114 
 
Project Sharing Example 2 
Managing Design Options 
Managing multiple design options during the schematic design and design development phases is a common practice in the 
architectural office. There are several ways to handle this issue in ARCHICAD. Each resolution has its advantages and limitations, so 
it’s important to understand when and how they can be used. Basically there are two different strategies. In the first one, all design 
variations are incorporated into the main project file; in the second, individual design options are stored in external files. Let’s see 
the different variations of the two concepts in more detail. 
Design Options in the Main File 
Layer Combinations 
This is probably the most straightforward solution but it requires significant management efforts from the project architect. The 
concept is very simple: elements of the different project variations are placed on dedicated layers and the users can toggle betweenthem with predefined layer combinations. The layers belonging to the same design options are distinguished with a unique 
identifier in their names. It can be a prefix (e.g. Opt01-Layer name) or a layer name extension (Layer Name --- Opt01). Both solutions 
allow the architect to quickly organize the layers in the Layer Settings dialog by the design options. For each design variation, a 
dedicated layer combination is saved that displays only the required layers. To make this concept work, the project architect has to 
make sure that all team members know which layers must be used during the creation of new design variations. 
Please note that layers cannot be used effectively in large projects, since the number of necessary layers might exceed the limit that 
one can efficiently overview. 
 
 
115 
 
BIM Implementation Guide Page 115 
 
Layer Combinations can be used to Manage Design Variations 
The main drawback of this concept is that it increases the file size and the number of layers, which can be a serious limitation in case 
of very large and complex projects. Thus we recommend this option only if the file size and the basic layer set are relatively small or if 
the number of design variations is limited (e.g. not more than 3-4). 
The Stories Approach 
We no longer recommend this ‘conventional’ option to handle design options. Since multi-story elements have been introduced, 
this option cannot be used effectively any longer. 
This solution used to work with floor plans only, provided that the 3D BIM model is independent from the floor plan drawings. The 
idea behind this concept was that the stories can be used instead of layer combinations to switch between the floor plan design-
variations. Users had to create multiple stories in the story settings dialog that would incorporate the different design options. Each 
story name referred to the design option that it contains. 
The major limitation of this solution is that it does not conform to the BIM modeling concept, according to which the floor plan 
drawings are derived from the 3D model. Moreover, multistory elements can’t be used, as they will be represented in each design 
variation. 
Design Options in External File 
Hotlink Modules 
Hotlink Modules allow the users to insert the contents of external ARCHICAD files into the currently open Project. Furthermore the 
currently active Hotlink Modules can be easily re-linked to other module files from the Hotlink Manager Dialog, resulting in changes 
in the main BIM model file. Alternatively, the Hotlink Modules containing the various design options can be placed on different 
master layers, so users can switch between them with layer combinations. The latter option requires more attention from the Model 
Manager due to the possible intersections between the hidden and the visible design options in case their master layers have the 
same layer intersection values. 
This Hotlink Module solution has many advantages compared to the previously described ones: design variation will not increase the 
file size and there is no need to add new layers and layer combinations to the project file. Furthermore, with the use of nested 
modules, you can manage multiple design option combinations. The only limitation is that the design options can’t be saved as 
views, since the Hotlink modules’ file names are not associated with the views. 
 
 
116 
 
BIM Implementation Guide Page 116 
The Teamwork approach 
This solution is based on the flexible Teamwork technology of ARCHICAD. 
The process is the following 
1 You sign into a Teamwork project and save a draft locally. For example, if the Teamwork is on the server, you sign into it, 
and save a PLC file to your computer's hard drive. 
2 Once you have saved the draft, you can copy it, either in the operating system, or within ARCHICAD, using Save As. 
3 You are then free to make various design changes in any of the drafts. 
4 When you have decided on a final design, you send the changes from that draft back to the main model. You will be 
warned that the draft has a different ID, but consider that a good thing rather than a bad thing and proceed. 
5 Once you have sent in your design, you are free to sign out of the project altogether. 
This approach is recommended if the project is developed in a Teamwork environment. Otherwise this solution has the same 
advantages and disadvantages as the hotlink modules concept. 
Creating Custom ARCHICAD Installers 
The ‘Installation Package Creation’ option of the ARCHICAD installer allows BIM managers to create a customized installer package 
that contains company standard settings, such as Work Environment profiles, DXF-DWG translators, and template files. At the end of 
this process, a single-file, one-click installer package is created that can be distributed over the network. 
Cleaning ARCHICAD Preferences 
In some cases ARCHICAD files can get corrupted so you cannot start the program, or you have crashes for various reasons. In this 
case you can try to make a Preference cleaning to enable ARCHICAD to reorganize the preference files. This causes no harm to the 
program: at the next opening of ARCHICAD the files will be regenerated automatically in the previously deleted folders. 
http://helpcenter.GRAPHISOFT.com/troubleshooting/setup/preferences-cleaning/?redirect=ARCHICADwiki 
Enabling the ARCHICAD Special Menu 
Special Menu is a ‘hidden’ menu in ARCHICAD that contains commands that are mostly useful for Library and API developers. By 
default, the Special menu is not available in the Work Environment. Note that features in the Special Menu are not supported by 
GRAPHISOFT. 
For more details read: 
http://helpcenter.GRAPHISOFT.com/tips/special-menu/ 
Crash Detection and Troubleshooting 
The ARCHICAD Crash detection and troubleshooting website have been created to identify, monitor, report and process crashes. 
This website is continuously updated, please visit this URL for further information: 
http://helpcenter.GRAPHISOFT.com/?s=crash 
 
http://helpcenter.graphisoft.com/troubleshooting/setup/preferences-cleaning/?redirect=archicadwiki
http://helpcenter.graphisoft.com/tips/special-menu/
http://helpcenter.graphisoft.com/?s=crash
 
 
117 
 
BIM Implementation Guide Page 117 
Chapter 9 - Appendix 
GRAPHISOFT Websites 
http://www.GRAPHISOFT.com/ 
http://www.GRAPHISOFT.de/ 
http://www.ARCHICAD.es/ 
http://www.GRAPHISOFT.co.jp/ 
http://www.GRAPHISOFT.hu/ 
http://www.GRAPHISOFT.it/ 
ARCHICAD Forums 
http://ARCHICAD-talk.GRAPHISOFT.com/ 
http://www.ARCHICADforum.com/ 
http://fc-cadlink.com/fccl-forums/ 
ARCHICAD Knowledgebase 
http://helpcenter.GRAPHISOFT.com/ 
http://www.archiradar.it/ 
http://www.onland.info/ 
ARCHICAD Training Materials 
http://www.GRAPHISOFT.com/learning/training_materials/ 
http://www.GRAPHISOFT.com/community/education/teachers/ 
3rd Party Products 
http://www.GRAPHISOFT.com/downloads/addons/index.html 
http://www.GRAPHISOFT.com/ARCHICAD/partner_solutions/ 
ARCHICAD Blogs 
http://www.bimania.blogspot.com/ 
http://www.onland.info/ 
http://blog.GRAPHISOFTus.com/ 
http://www.ARCHICADmonkey.com/ 
http://www.graphisoft.com/
http://www.graphisoft.de/
http://www.archicad.es/
http://www.graphisoft.co.jp/
http://www.graphisoft.hu/
http://archicad-talk.graphisoft.com/
http://www.archicadforum.com/
http://fc-cadlink.com/fccl-forums/
http://helpcenter.graphisoft.com/
http://www.archiradar.it/
http://www.onland.info/
http://www.graphisoft.com/learning/training_materials/
http://www.graphisoft.com/community/education/teachers/
http://www.graphisoft.com/downloads/addons/index.html
http://www.bimania.blogspot.com/
http://www.onland.info/
http://blog.graphisoftus.com/
http://www.archicadmonkey.com/
 
 
118 
 
BIM Implementation Guide Page 118 
http://www.shoegnome.com/ 
ARCHICAD Links 
http://ARCHICAD.lap.hu/ 
GDL Libraries 
Free 
http://ARCHICAD-talk.GRAPHISOFT.com/object_depository.php 
http://archibase.co/gdlhttp://ARCHICADo.free.fr/ 
http://www.gotogdl.net/ 
http://archive3d.net/ 
https://bimcomponents.com/ 
Commercial 
http://www.alfaville.com/archscene/index.php 
http://www.theobjectshop.com/ 
http://www.formfonts.com/search.php?area=Models&query=ARCHICAD 
http://bimobject.com/en-us 
For GDL Developers 
http://www.gdlalliance.com/Tools/gdl_talk.html 
http://www.nottingham.ac.uk/sbe/cookbook/CB_download/cookbook3download.html 
Books about ARCHICAD 
ARCHICAD Project Framework 
Bill Rattenbury 
http://www.amazon.com/exec/obidos/tg/detail/-/9630046059 
ARCHICAD Best Practice: The Virtual Building™ Revealed 
Martens, Bob, Peter, Herbert 
http://www.amazon.com/ARCHICAD-Practice-Virtual-Building-Revealed/dp/3211327894 
BIM for Construction Using ARCHICAD 
Tulio Sulbaran 
http://www.amazon.com/Construction-Using-ARCHICAD-Tulio-
Sulbaran/dp/1428356649/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1216035055&sr=8-2 
http://www.shoegnome.com/
http://archicad.lap.hu/
http://archicad-talk.graphisoft.com/object_depository.php
http://archibase.co/gdl
http://archicado.free.fr/
http://www.gotogdl.net/
http://archive3d.net/
https://bimcomponents.com/
http://www.alfaville.com/archscene/index.php
http://www.theobjectshop.com/
http://www.formfonts.com/search.php?area=Models&query=archicad
http://bimobject.com/en-us
http://www.gdlalliance.com/Tools/gdl_talk.html
http://www.nottingham.ac.uk/sbe/cookbook/CB_download/cookbook3download.html
http://www.amazon.com/exec/obidos/tg/detail/-/9630046059
http://www.amazon.com/ArchiCAD-Practice-Virtual-Building-Revealed/dp/3211327894
http://www.amazon.com/Construction-Using-Archicad-Tulio-Sulbaran/dp/1428356649/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1216035055&sr=8-2
http://www.amazon.com/Construction-Using-Archicad-Tulio-Sulbaran/dp/1428356649/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1216035055&sr=8-2
 
 
119 
 
BIM Implementation Guide Page 119 
ARCHICAD Migration Guide 
http://helpcenter.GRAPHISOFT.com/guides/ARCHICAD-18-int-reference-guide/migration-guide-for-ARCHICAD-18/ 
Books about BIM 
BIM Handbook: A Guide to Building Information Modeling for Owners, Managers, Designers, Engineers and Contractors 
Chuck Eastman 
http://www.amazon.com/BIM-Handbook-Information-Designers-Contractors/dp/0470185287/ref=pd_sim_dbs_b_4 
BIG BIM little bim - The practical approach to Building Information Modeling - Integrated practice done the right way! 
Finith E. Jernigan 
http://www.amazon.com/BIG-BIM-little-bim-Information/dp/0979569907/ref=pd_sim_dbs_b_5 
Building Information Modeling (McGraw-Hill Construction Series) 
Willem Kymmell 
http://www.amazon.com/Building-Information-McGraw-Hill-Construction-Mcgraw-Hill/dp/0071494537/ref=pd_sim_dbs_b_13 
Online Cad Magazines 
AECCafé 
http://www.aeccafe.com/ 
AECbytes 
http://www.aecbytes.com/ 
Architosh 
http://www.architosh.com/ 
Cadalyst 
http://www.cadalyst.com/ 
TenLinks Daily 
http://www.tenlinks.com 
 
http://helpcenter.graphisoft.com/guides/archicad-18-int-reference-guide/migration-guide-for-archicad-18/
http://www.amazon.com/BIM-Handbook-Information-Designers-Contractors/dp/0470185287/ref=pd_sim_dbs_b_4
http://www.amazon.com/BIG-BIM-little-bim-Information/dp/0979569907/ref=pd_sim_dbs_b_5
http://www.amazon.com/Building-Information-McGraw-Hill-Construction-Mcgraw-Hill/dp/0071494537/ref=pd_sim_dbs_b_13
http://www.aeccafe.com/
http://www.aecbytes.com/
http://www.architosh.com/
http://www.cadalyst.com/
http://www.tenlinks.com/
 
 
120 
 
BIM Implementation Guide Page 120 
Office Evaluation Questionnaire Sample 
Below is an office evaluation questionnaire sample, with the most important questions that have to be answered prior to developing 
the BIM implementation plan. In this example the questions are grouped according to the key stakeholders of the migration process. 
This questionnaire is a good way to make the first ‘connection’ with the participants. 
Principals/Partners/Directors 
 What is the main team structure of the office? 
 What are the main benefits expected from the new workflow? 
 Who is the best candidate for an internal champion to drive the change? 
 What are the potential projects to consider for piloting the new workflow (and why those)? 
 Who are the best potential individuals or teams for starting the pilot project? 
 What are the main milestones and metrics to measure the success of the pilot project? 
Project Leaders/Managers 
 Who are the main stakeholders in the chosen pilot project? 
 What are the primary steps and workflows for a typical project? 
 What are the main input sources to the pilot project? (paper, DWG, SketchUp, 3DS, Rhino) 
 What is the typical coordination process with the consultants? 
 What is the timeline for main milestones in the pilot project? 
 What is the availability of human resources for the pilot project? 
Project Team Members 
 What are the main issues/problems with the current 2D workflow? 
 What are the advantages of the current 2D workflow that should be preserved? 
 What are the main concerns regarding the planned BIM workflow? 
 What are the main expectations of the planned BIM workflow? 
 What will be the personal gains for them if the new BIM workflow is successful? 
CAD Manager 
 What project template system is used in the office 
 Who has access to create and modify these templates? How strictly are these rules enforced? 
 What are the main concepts behind the templates used? 
 What are the main roles of the CAD manager in the project? 
 What are the main difficulties in the current 2D workflow for the CAD manager? 
 What are the main concerns of the CAD manager regarding the planned BIM workflow? 
 What are the main expectations of the CAD manager toward the planned BIM workflow? 
 What will be the personal gains for the CAD manager if the new BIM workflow is successful? 
	Chapter 1 - Introduction
	Chapter 2 - Preparations
	BIM Implementation Strategy
	Office Evaluation
	BIM Implementation Plan
	Chapter 3 - The Pilot Project
	Type of Project
	Management Commitment
	Project Team
	Potential Project Risks
	Chapter 4 - Human Resources
	Structure of the Teams
	Typical Structure of a Large Practice
	Roles and Responsibilities
	Setting up the Project Team
	Chapter 5 - Project Setup
	Project Templates
	Project Template Strategies
	Single Project Template File
	Multiple Project Template Files
	Commercial Template Files
	Content of the Project Template File
	Starting to Create Your Own Custom Project Template
	Naming and Path
	Project Structure (Navigator, Organizer)
	Project Map
	View Map
	View Settings
	Layout Book
	Master Layouts
	Publisher Sets
	Story Settings
	Element Attributes
	Building Materials
	Layers
	Use of the Default ARCHICAD Layers
	Use of Layers Complying with National CAD Standards
	Create and Use Custom Company Layers
	Layer Combinations
	Layers vs. Layer Combinations
	Pens and Pen Sets
	General Rules for Pens and Pen Sets
	The ARCHICAD Pen Table
	Pens by Element Types
	Pens for DWG output (optimized for DWG file exchange)
	Line Types
	Fill types
	Surfaces
	Internal 3D engine
	CineRender by MAXON engine
	Sketch engine
	Renovation Styles
	Attribute Management
	Favorites
	Working with the Standard Favorites Palette
	Working with ‘Graphical Favorites’
	Separate Graphical Favorites for On-demand Use
	DXF-DWG Translators
	Saving DWG from Layouts while Keeping the Original ARCHICAD Layers of Elements
	Converting DWG-DXF Colors and Line Weights
	IFC Translators
	Libraries
	Attributes and Third Party Libraries
	Converting Symbol Libraries
	Object Catalog
	Most Common Library Types
	Standard ARCHICAD Library
	Office Standard Library
	Project-specific Library
	Third Party Libraries (Custom Parts)
	Teamwork Library Solutions
	Embedded Objects
	BIM Server/BIMcloud Libraries
	Local Libraries
	Central Library
	Project Template Tricks
	Basic Attributes In tpl, Extended Attribute Set In .aat
	2D Favorites and Pen Set Descriptions On Worksheet
	Layout Title Blocks And LegendsOn Worksheets
	Chapter 6 - Project Workflows
	Project Lifecycle
	Creating the Design Model
	Schematic Design
	Schematic design methods
	Design Development
	Construction Documentation
	As Built Model
	Sharing the work
	Small Projects – Single File Concept
	Medium Size Projects – Model File and Document File Separated
	Big Projects – Hierarchal File Structure
	Teamwork
	Evaluation of the Teamwork 2.0 Technology
	Benefits
	Suggested usage
	Advantages
	Hotlink Modules
	Advantages
	Limitations
	Suggested Usage
	XREF
	Advantages
	Disadvantages and limitations
	Suggested Usage
	Combined workflow
	Documentation Separated from the Model File
	Master File Method
	Complex and Distributed Methods
	Coordination
	DXF-DWG
	DXF-DWG Translator Setup
	Using DWG-DXF files in ARCHICAD
	IFC
	Advantages of using IFC
	Structural Design, Analysis and Production
	Structural Related ARCHICAD Features
	IFC Based Structural Design Workflow
	Energy Analysis
	Energy Evaluation in Different Design Phases
	Chapter 7 - Project Management
	Folder Hierarchy
	IT Infrastructure
	Hardware
	Networks
	Software
	Suggested Configuration
	ARCHICAD Network Key Servers
	File Servers
	ARCHICAD Workstations
	Rendering and Visualization Workstations
	BIM Server
	A safe rule of thumb
	Network requirements
	Memory Requirements
	Windows 8
	Mac OS X
	Data Safety
	Saving
	Manual Saving
	Autosave
	File Backups
	Archiving
	Printing and Plotting
	Updates & upgrades
	ARCHICAD Updates
	Library Hotfixes
	Project migration
	Chapter 8 - Best Practices
	Modeling Strategies
	Large Projects
	Polygon Count
	Project File Size
	Layout Book Size
	Number of Stories
	Summary
	Hardware requirements
	Speed Issues
	3D Rebuild and Navigation
	The PolyCount add-on
	How to Reduce the 3D Model Size
	Sections and Elevations
	Rendering
	Floor Plan Regeneration
	Lines/Arcs coming from DXF/DWG Files
	Morphs and Shells
	Curtain Walls
	Embedded Groups
	GDL Objects
	API Add-Ons
	Project Sharing Strategies
	Example 1
	Example 2
	Managing Design Options
	Design Options in the Main File
	Layer Combinations
	The Stories Approach
	Design Options in External File
	Hotlink Modules
	The Teamwork approach
	Creating Custom ARCHICAD Installers
	Cleaning ARCHICAD Preferences
	Enabling the ARCHICAD Special Menu
	Crash Detection and Troubleshooting
	Chapter 9 - Appendix
	GRAPHISOFT Websites
	ARCHICAD Forums
	ARCHICAD Knowledgebase
	ARCHICAD Training Materials
	3rd Party Products
	ARCHICAD Blogs
	ARCHICAD Links
	GDL Libraries
	Free
	Commercial
	For GDL Developers
	Books about ARCHICAD
	Books about BIM
	Online Cad Magazines
	Office Evaluation Questionnaire Sample
	Principals/Partners/Directors
	Project Leaders/Managers
	Project Team Members
	CAD Manager