Intro To Office Standards

Introduction to Office Standards
Graphisoft
Visit the Graphisoft website at http://www.graphisoft.com for local distributor and product availability information.

Copyright 2004 by Graphisoft, all rights reserved. Reproduction, paraphrasing or translation without express prior written permission is
strictly prohibited.
Trademarks
ArchiCAD and ArchiFM are registered trademarks and PlotMaker, Virtual Building, StairMaker and GDL are trademarks of Graphisoft.
All other trademarks are the property of their respective holders.
Acknowledgements
Purpose of the Book
A special thanks to Graphisoft for providing the opportunity to share

the experiences and expertise accrued over many years, incorporating
many individuals in a design community interested in and dedicated
to changing the way that architecture is practiced, developed and
documented. To the industry of professionals who want more out of
how they produce their art, who continue to expect more and better
ideas, and who propagate those ideas through community discourse.
The purpose of this manual is to assist architectural firms in taking

advantage of ArchiCADs capabilities, and of the Virtual Building
concept. The ideas and concepts contained herein are aimed at
increasing efficiency and production, and at helping those in the
midst of change to implement and maintain their system. Even
though the title of this book may suggest that it is about the
responsibilities of a single individual, the contents of this manual
extend to standards committees, project managers, principals and the
everyday user. Object based software technology is fast becoming the
defacto method for producing architectural drawings and
visualization products. ArchiCAD is, and has been at the forefront of
object-based software for use by architects and other design
professionals. Its elegant interface design coupled with its plethora of
powerful intuitive features and advanced Geometric Description Language
(GDL), make it an obvious choice as a building modeler, presentation
tool, and construction documentation production software. The
challenge begins with its incorporation into an existing practice.
Though it is an intuitive tool that can be learned quite quickly, making
ArchiCAD perform to its maximum potential requires careful
planning of its implementation. With this manual, it is our intent to
provide a basic foundation along with the necessary tools to make
ArchiCAD an effective solution for your office. This book is
intended for use by those with at minimum, a working knowledge of
ArchiCAD and its intended workflow, and preferably by power users
capable of understanding the concepts and manipulating them into
practical solutions to suit the changing needs of their firms.
The Author
David R. Russo is an architectural professional currently based in
South Florida. He is a cofounder of Architectural Data Consultants,
L.L.C., established in 2000. One of ADCs main services is assisting
architectural firms of all sizes in their transition from traditional
two-dimensional CAD drafting methods to using object based
software technology, in particular ArchiCAD; and helping these firms
in adapting their culture and methodologies to take advantage of the
power and versatility of ArchiCAD.
ADC has assisted several large and moderately sized architectural
firms in successfully developing and implementing the Virtual
Building concept and office standardization; and, has worked with
two major U.S. national homebuilding companies to help them
streamline their residential construction documentation and sales
methods using ArchiCAD. In addition, they have traveled both in the
US and internationally presenting their work, ideas and concepts, and
providing training sessions for users while enthusiastically promoting
the Virtual Building concept.
CONTENTS
Introduction_______________________________________________ 7
Using the Virtual Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Exploiting the Virtual Building Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
A New Way of Thinking about Architecture . . . . . . . . . . . . . . . . . . . . . . . . . .8
Switching to ArchiCAD _____________________________________10
Evaluating Existing Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Office Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Managing CAD Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Technology Staff Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Project Staffing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Project Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Administrative Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
When to Use ArchiCAD within the Project Lifecycle . . . . . . . . . . . . . . . . . .12
Design Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
A New Technology in the Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Addressing the Needs of Executives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Addressing the Needs of Project Leaders and Senior Architects . . . . . . . . .13
Addressing the Needs of CAD Staff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Initial Training and Continuing Education . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Tailoring ArchiCAD ________________________________________15
The Intent of Custom Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Establishment of Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Folder Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Application Preferences & Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
The Project Template File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Where Do I Begin? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Contents of a Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Views and View Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Layer Management and Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Evaluation of Firm Project Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
The Use of Layer Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
The Use of Layer Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
When to Lock, Hide, or Show. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Display Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
The Importance of Custom Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 31
Pens Weights and Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Pen Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Line Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Fill Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Composites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Textures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
The Stories Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Strategic Ways to Use Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Setting Up the Working Environment . . . . . . . . . . . . . . . . . . . . . . . . . 37
Building the Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Pen Weights and Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Working Units, Dimensions and Calculation Units . . . . . . . . . . . . . . . . . . . .38
Work Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Font Types and Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Using Attribute Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Transferring Custom Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Using Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Library Management ______________________________________ 41
Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
ArchiCAD Object Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Office Standard Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Project Specific Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Location of Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Network Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
The Localized Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Advantages and Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Loading Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Creating and Maintaining an Office Library . . . . . . . . . . . . . . . . . . . . 49
Additive Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Updating Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Creating the Office Standard Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Transitioning Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
File/Folder Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Using FTP Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
On-Line Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Data Safety _______________________________________________ 55
Saving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Manual Saving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Autosaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
File Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Archiving Data in the Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
About the ArchiCAD Archive File (.PLA) . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Archiving PlotMaker Layout Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Staying Organized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Project Output ____________________________________________ 62
Contents
Quality and Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Output Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Printing from ArchiCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Output from PlotMaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Publishing View Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Master Layouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
View Links and Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Project Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Output Devices and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Practical Use of TeamWork __________________________________ 71
Setting Up TeamWork Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Sharing the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Strategies for Using TeamWork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Team Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Team Selection/Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Project Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Single User Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Sign In/Out; Send & Receive Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TeamWork Project Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Extending ArchiCAD_______________________________________ 77
Adding Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Sharing the Content of the Virtual Building ____________________ 79
Sharing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
How to Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
What to Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using Shared Information within ArchiCAD . . . . . . . . . . . . . . . . . . . . . . . . 80
Hotlinked Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Using Shared Information Outside of ArchiCAD. . . . . . . . . . . . . . . . . . . . . 81
Setting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Making It Look Right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Exchanging Files between AutoCAD and ArchiCAD. . . . . . . . . . . . . 83
Sharing AutoCAD Information Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
The IFC Integrated Object Model ____________________________ 85
What is an IFC?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Inter-Operability Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Why Use IFC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Planning an IFC Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Determining the Scope of a Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Set Up a Pilot or Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Useful Links for Using the IFC Exchange Protocol . . . . . . . . . . . . . . 88
Sharing GDL Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Publishing Objects Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Embedded GDL Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Download Compatibility on Other Platforms . . . . . . . . . . . . . . . . . . . . . . . . 88
The Project Cartoon Set and the Layout Book Template __________89
What IS The Cartoon Set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
How to Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Producing Sheet Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Using The Cartoon Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Project Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Index ____________________________________________________95
INTRODUCTION
Architects are design professionals responsible for the creation of
space. It seems obvious for them to use a tool that is adept at
providing three-dimensional representation of ideas and which also
facilitates the production of construction documentation. The Virtual
Building is a way for the architect, owner, consultant, contractor and
municipality to understand the project more thoroughly and
accurately. This all translates into better-managed projects with fewer
modifications, fewer misinterpretations and fewer conflicts.
For all practical purposes, the Virtual Building is a carefully described
digital representation of an architectural work modeled in three
dimensions. It provides the architect/designer with the opportunity
to study, inhabit, and evaluate the work prior to construction. The key
advantages to the Virtual Building, as opposed to the traditional
drafting approach, are as follows:
Coordination errors between drawings are reduced by working on
one model rather than on many drawings.
Presentation/visualization materials and construction documents
are part of the same virtual model.
A more comprehensive understanding of complex projects is
obtained by always being three-dimensional.
Custom attributes
Pen sets
Libraries
Information about a system, component, and/or material should be
entered into the project the very first time a decision is made. This
helps make the production of a project drawing set more efficient.
For instance, instead of drawing two lines to represent a wall, the
information about that wall is entered at the time it is placed into the
drawing file.
USING THE VIRTUAL BUILDING

Making It Effective
The Virtual Building approach is an aid for producing
well-coordinated project documents; however, standards and
procedures need to be in place to make it truly effective. For example,
though ArchiCAD and PlotMaker enable multiple drawings to be
updated with changes made in the model, the resulting drawings may
not be correct if carefully considered standards are not followed.
These standards include:
Directory structures
Views and View Sets
Layers and Layer combinations
Display Options Combinations
Introduction
Composite materials, thickness, height, layer, pens, etc., should all be

assigned within each drawing component. With care and precision at
the moment of placement/construction, future editing becomes
significantly easier as the design evolves.
Exploiting the Virtual Building Database

With more information included in the project at an earlier phase, it
becomes easier to evaluate the design decisions that are being made
throughout the course of the project. Sections and elevations can be
generated and studied earlier in the process, without having to
construct them as separate drawings. This instant feedback allows
conflicts and coordination issues to be resolved before they become
major problems that result in costly revision work. For example,
architectural details can be refined sooner allowing their impact to
occur earlier in the project. Important areas of complex spatial
organization or material joinery can be studied and resolved earlier in
the project. The simplicity of having a computer model as the
generator of all the final documentation allows the modeler to make
revisions in a single location. Therefore, instead of having to change
many drawings (while tracking all the subsequent drawings that are
effected by the changes) only the model file is changed. Changing the
model file means that all related drawings affected by the
modifications are automatically updated.
Contrary to traditional two-dimensional drafted documentation, the
Virtual Building offers more information available in the model,
allowing for a better comprehension of components and their
relationships.
When used in conjunction with ArchiCADs calculation functions,

the Virtual Building allows for a complete and accurate cost analysis
and project cost estimate. Another advantage of the Virtual Building
is the possibility of having all of the projects building information
residing in a single file. This, naturally, makes file management easier
and more efficient. In theory, all of the drawings produced for the
final set will be generated from this one file. This leaves the project
manager a single project file to manage, thereby dramatically reducing
the number of coordination errors among the production staff.
A New Way of Thinking about Architecture

The Virtual Building approach is not only a concept, it is a
methodology as well. It changes the how of producing work and the
sequencing of when that work is completed. As mentioned earlier, the
Virtual Building requires that more information be entered into the
project at an earlier phase. This early data entry does several things
for both the architect and client.
It provides a more complete project through all phases of design.
It enables easier visualization for the project team.
It shifts the distribution of workload in the project.
Since the work is being performed in a three-dimensional model,
there are always sections and elevations in addition to the plans ready
to be studied and evaluated. Documentation of a project is
continually ongoing as the model is developed and refined. It is no
longer necessary to invest extra time in generating support drawings
to provide an understanding of the project. Rendered images and
animations can also be provided with minimal effort. In contrast to
traditional two-dimensional drafting, where a more intensive effort
was invested in the construction documentation phase, ArchiCAD
now places more emphasis and effort in the schematic design and
Introduction
design development phases of a project. This may result in potential

fee restructuring, based upon individual office management style.
In conclusion, beyond providing a way to minimize coordination

errors and streamline the production process, the Virtual Building is a
design methodology. It provides ways to study each individual project
in perspective, parallel projection, section, and elevation. It allows for
the designer to use these three-dimensional environments as a vehicle
for making changes to the model and thus affecting final drawing
output.
Switching to ArchiCAD
SWITCHING TO ARCHICAD
In the following section, we will discuss the ways in which architects
can most effectively and efficiently implement ArchiCAD into the
office environment. In particular, we will outline ways to use existing
standards and methods and we will address the means to deal with
the positive changes in practice and how to maintain a system with
ever changing technology.
EVALUATING EXISTING
INFRASTRUCTURE
Hardware and Software
The first step in converting to ArchiCAD consists of a thorough
evaluation of the existing office infrastructure. Items such as office
hardware, software, and network solutions, as well as the evaluation
of existing standard drawing files and/or templates should all be
considered.
CAD Managers/IT staff must ensure that workstations meet the
minimum specifications to run ArchiCAD, as described in the
Getting Started booklet and the Read Me First files provided with the
ArchiCAD package. CAD Managers/IT staff should also evaluate all
office software for compatibility with ArchiCAD.
Office Standards
Over time, most offices develop standards for their drawings,
whether they consist of standard drawing sheets, sets of standardized
details, customized drawing symbols, template files, etc. There are
several options for these existing resources to continue to be used:
detail drawings can be converted into library parts;
CAD drawing files can be converted into .PLN files;
DWGs can be X-referenced and merged into ArchiCAD projects;
supported file types can be used directly by PlotMaker.
Each of these solutions has benefits and limitations that are
important to understand before implementation.
10
See also Sharing the Content of the Virtual Building on page 79 and the
ArchiCAD 9 Reference Guide for more information on how to open, import
and merge files of various types.
MANAGING CAD RESOURCES

For an established architectural practice, transitioning from a
two-dimensional drafting program to a three-dimensional object
based application will undoubtedly have an effect, in particular on
office support staff, project staffing, and administrative processes.
Technology Staff Resources

Using CAD effectively requires standards and proper dedicated
management. As IT has become an essential resource in offices, and
we move to a completely digital workflow, CAD and IT are key
functions. Optimally, these roles report directly to senior executives
of the firm: in a larger firm to the Office Manager, in a smaller firm to
a partner with management responsibility.
Two roles are paramount: that of the CAD Manager and that of the
IT Staff. The role the CAD Manager needs to be defined, if it has not
been already,. In a larger office it will be important to make this a
single full time appointment, serving and advising all project teams.
In a smaller office the role may be shared with a direct project role.
However this job description is fulfilled, it is imperative that its task
be accomplished consistently and rigorously.
The CAD Manager takes responsibility for the setup and support of
project technology and of CAD systems within the office. He/She
provides technical advice and support to project teams, ensuring that
systems are properly implemented and used to their optimum and
that office standards are adopted and maintained.
The CAD Managers responsibilities are to:
assist project teams identify appropriate technology solutions to
support project deliverables;
set up, configure and customize systems for specific projects;
assist project CAD establishment and adherence to office
protocols;
identify project specific needs and coordinate with IT in their

delivery;
participate in review of project performance at milestones and
project completion and report to IT on project technology
effectiveness, development priorities etc.;
manage the development, implementation and maintenance of
project technology standards and procedures;
maintain project template files;
maintain libraries;
update software.
Complementing the CAD Manager, the second role of an IT or
Information Technology person needs to be filled. The IT Manager
takes responsibility for the management of the digital hardware and
software systems within the office and provides technical advice and
support. He ensures that the system is properly maintained and used
to its optimum.
IT responsibilities include:
hardware support and maintenance;
operating system and application installation and maintenance;
network installation and support;
office computer system documentation and hardware/software
inventory;
daily, weekly and monthly digital information archiving;
coordination of activities with Office Manager;
reporting to Office and IT Managers on system performance;
contribution to development, implementation and maintenance of
standards and procedures for digital systems;
testing software for compatibility and conflicts.
The CAD Manager and IT staff should work in conjunction to create
network solutions, backup options, and standardized office
procedures and security options. Using the systems put in place by
the IT staff and the CAD Manager, the architectural staff can be
focused on the design, presentation, production and output of the
office projects.
11
Project Staffing
When using ArchiCAD, the architect/designer/drafts person is
producing the drawings through modeling the project. As each
element is created, decisions about height, construction, material,
manufacturer, etc. are being made and incorporated directly into the
model. This methodology does several things:
It intensifies the effort in earlier phases of the project;
It begins to narrow the gap between architectural staff and
draftspersons.
To take full advantage of ArchiCAD in an office may require a shift in
the training of production staff and/or specialized management so as
to effectively manage an ArchiCAD produced project.
Note: How an office chooses to staff projects depends on its size,
the types of work and the working knowledge of the users. It is
not uncommon on smaller jobs for the designer/architect to do
most of the production work, while receiving assistance in
periphery tasks such as creating details and refining presentation.
On larger jobs it may be necessary to have several people
dedicated to specific tasks with one team member responsible for
overall coordination.
See also Practical Use of TeamWork on page 71 for more information on
setting up and managing team projects.
When to Use ArchiCAD within the Project

Lifecycle
ArchiCAD redefines how and when a project is brought into the
CAD environment and how it is developed. While we certainly
encourage hand sketches and conceptual drawings, we suggest using
ArchiCAD as early as possible in the design process to increase the
accuracy and viability of design solutions. Accurate does not mean
final. The exact point of transition from hand-drawn to
computer-drawn depends upon the users level of comfort and design
preferences.
Tip: It is our recommendation that once the extents of a project
are known, the basic forms should be roughed out in ArchiCAD
in order to begin setting up the project layouts.
Preliminary design can continue by hand and be brought into
ArchiCAD as a scanned image in order to transfer the design into a
Virtual Building. The accurate computer generated plans can then be
printed and sketched over to continue developing the design. This
back and forth procedure increases the designs accuracy early on,
while allowing for a more fluid or traditional design approach.
PROJECT DELIVERY
Administrative Processes
ArchiCAD is CAD software that extensively exploits the modeling
database upon which it is built. What this means is that the earlier
information can be added to the system, the more effective and
efficient ArchiCAD becomes as a tool for producing a projects
documentation. Since using ArchiCAD effectively involves
considering as many aspects of an element or component as possible
at the time it is created, the earlier phases of a project take more time
to complete. From an administrative point of view this means that
billing percentages can be more evenly distributed through the life of
a project since more work is being performed earlier than with the
traditional design-document approach.
12
See also The Project Cartoon Set and the Layout Book Template on page 89.
Design Communication
In the early phases of project design, many architects rely on
hand-drawn sketches to generate ideas and concepts. The perception
of many is that a sketch or hand drawing is a more flexible design tool
than a computer-generated drawing. Consequently, many designers
are opposed to hard-lined accurate computer representation early in
the project life cycle.
Tip: With ArchiCAD, there is the ability to soften the look of a
given solution while retaining the accuracy necessary for the
documentation phase by creating a sketch line type. To achieve
the look of a hand-drawn schematic elevation, perspective, or
floor plan, simply change the normal line type settings to this
newly created sketch line type.
Another method for creating the appearance of less final drawings is

to use other ArchiCAD rendering engines such as GraphiSketch
Renderer, Piranesi, etc. (Image > PhotoRendering Settings >
Effects). These rendering engines create a rough pencil sketch of a
three-dimensional project view.
Note: These engines can significantly increase the amount of time
necessary to create rendered views.
A further effective design communication tool afforded by
ArchiCAD is its ability to involve the client in interactive design
sessions. Clients can participate in their project, having their ideas
quickly incorporated, and then see the results in three-dimensions.
TRAINING
A New Technology in the Office
The introduction of ArchiCAD can be an overwhelming and
occasionally unsuccessful experience. This applies not only to CAD
staff but to project leaders, senior management and the owners of the
firm. Typically the selection of ArchiCAD has been delegated to a
small team; once their recommendations have been agreed to, a plan
for training at all levels in the organization is needed. Why?
Addressing the Needs of Executives

Having invested in the ArchiCAD solution, owners want to exploit
the advantages of their new technology. They need to be trained to
understand how ArchiCAD changes old processes and creates new
opportunities. How will these changes benefit clients? What
additional services can now be offered? What new collaboration with
existing firms, industry colleagues can be achieved? Can better fees be
charged or can resources be used more productively? Can the firm
claim, move towards or want industry leadership?
All of these potentials and impacts need to be discussed and
articulated. This level of the organization will not need, or expect to
use ArchiCAD generally, but some principals will. This gives a strong
signal to the rest of the organization and industry that the firm and its
leaders have committed to this technology, enhancing the
commitment of staff and the image in the industry.
Above all, the executives of the firm need to understand, endorse and
support the new acquisition. They must be articulate about its
benefits and be prepared to support the process of implementation in
good and bad times.
Addressing the Needs of Project Leaders and

Senior Architects
Graphisofts virtual building technology has significant impacts on
the design and documentation processes as outlined above. What
different team skills does the project require? How does the firm
work with clients, consultants and contractors? What technology
support is needed? How is the project team structured?
13
Experienced users of ArchiCAD on larger projects have identified

new roles for Model and Document management.
The Model Manager is a designated CAD team member, whose
main responsibility is to manage the CAD database. Supported by
the Office CAD Manager, the Model Manager instructs the CAD
team on the project setup, the application of office protocols and
the development of special resources. The Model Manager works
with consultants and ensures that their CAD data is consistently
structured and integrated in the model. The Model Manager works
with the Project Leader to allocate tasks and establishes the
Teamwork or other relevant arrangement to ensure the database
and that the team deliver on time, on quality, on budget.
The Document Manager controls the output of drawings in
collaboration with the Project Leader, and in an increasingly
internet-enabled project environment, manages the uploading and
related tasks for web-based projects. The Document Manager
focuses on the definition of project documents, their generation
and their distribution to the entire project team. In a larger project
this is a significant switch in resources and vital to the success of a
project.
At the project level, all systems must work. Unless the Project Leader
understands the new processes, the virtual model concept and new
team roles, projects will not perform well and the expectations of the
ArchiCAD solution will not be met.
Addressing the Needs of CAD Staff

Naturally, CAD staff need full competence in all aspects of
ArchiCAD; what is often overlooked is the many different responses
individuals have to a change as significant as the Virtual Building
model. While recent graduates have only known a digital workplace,
longer-term employees, especially the most experienced, have only
learned this new technology in practice. CAD skills are highly
technical and usually require significant learning of the tool.
ArchiCAD changes the concepts - 2D paper to integrated 3D model
- and changes processes. While some people will enthusiastically
adopt it, some wont. Expect that many people will find it difficult
and provide training and general awareness programs that address
these differences.
14
It is important to note that instantaneous productivity is not a reality.

Upon the initial implementation of ArchiCAD, we recommend that
office staff establish a firm time line and/or pilot project for a
thorough evaluation of the software and established standards and
procedures. It has been our experience that effective use of
ArchiCAD is dependent upon the firms existing organization,
standards and methodologies and the firms commitment to change.
Once familiar with an established system, most users can become
productive in a matter of weeks.
Initial Training and Continuing Education

Once the office has adopted ArchiCAD, the training of new
employees and/or new users becomes a critical factor in the longevity
of the solution. We have found the implementation of an in-house
training program to be highly beneficial to acclimatizing new users,
while being an excellent resource for retraining casual users and
management.
An office-developed training program should introduce new users
and new employees to the changes in concepts and processes; it
should also provide an overview of the firms intended usage and
goals. It should expose a user to all of the required and expected tasks
involved in delivering a typical project. It should be geared towards
familiarity with both the software and the office infrastructure,
systems and standards.
Tip: Continuing education is paramount to the long-term success
of any CAD solution. User groups for ArchiCAD and GDL, either
in-house or community-based, can be organized to share
information, ideas and techniques. Consult local resellers for more
information on user forums.
Tailoring ArchiCAD
TAILORING ARCHICAD
THE INTENT OF CUSTOM SETUP
In this chapter, we will outline some of the components of custom
setup, and explain the process by which customization can be
achieved. ArchiCAD has the necessary tools to effectively set up and
manage the modeling and drawing information contained within a
project file. However, given the diversity in architectural practice,
including the varying size and scope of projects, it is necessary for
each firm to evaluate their project types, workflow, standards and
goals for standardizing and implementing procedures. To that, it
would be unrealistic to think that a single template file or standard set
of installation options could suit the needs of all ArchiCAD users.
Tailoring ArchiCAD is important for several reasons:
It shapes the software from a more generally usable tool to one
that performs as an integral part of the design process in a specific
arena, i.e. firm or project;
It provides a way to streamline the processes of design and
production to achieve consistent product quality;
It encodes the specific practices of an organization and ensures
consistency across projects and amongst users;
It provides a mechanism for the firm to change, grow and
consistently evaluate methods of practice.
It is important to remember that customizing is not meant to imply
the altering of the software application itself. It is about finding ways
to take advantage of the existing features, and creating methods for
using them effectively. Tailoring or customization happens at four
levels within the firm:
Software Installation: provisions for a uniform set of application
attributes and interface options.
Project Information: the location and structure of project
information stored in directories/folders.
Project Document Standards: the application of the company
design and document standards.
Project Resources: the provision of ArchiCAD specific templates,

libraries and tools to establish projects consistently and efficiently.
It is also important to remember that when designing custom setups
within an office, the systems need to be both organized and flexible
and at the same time easily maintainable; and, achieving this balance is
where the challenge lies. Some solutions that are extremely flexible
tend not to be as easily maintainable as less flexible ones due to
complexity. Likewise, highly organized systems may be lacking in
flexibility. The goal is to devise solutions that address each
consideration to the highest level possible to meet firm goals.
ESTABLISHMENT OF STANDARDS
Normally, as their practice evolves, most architectural firms develop
some semblance of office standards; whether formally set down or
strictly implicit. They exist in many fashions and may relate to
drawing graphics, such as the size of drawing notation text, or to the
scale of a particular drawing types, or to organizational methods such
as sheet numbering and content.
Tip: Begin the process of customization with what currently
exists, then edit, refine and add information as deemed necessary.
Starting with existing ideas will not only speed up the process but it
will provide some familiar territory on which to build a Virtual
Building methodology.
In addition to using existing company standards as a starting point, it
may be wise to incorporate standards developed by a national,
international or local governing body as well. For example, in the U.S.,
the Uniform Drawing System (UDS) is a set of guidelines and
standards developed for the AEC industry. These standards consist
of everything from the naming of individual layers to sheet naming
and numbering conventions.
15
Tailoring ArchiCAD
One of the benefits of this system is that it keeps like elements

grouped in lists, minimizing that amount of scrolling and searching
for the correct layer, and that it is also very flexible.
Once again, keep in mind that guidelines cannot address every
particularity, though some may attempt to cover every component
related to even the most sophisticated architectural projects. These
sets may be thorough, but not necessarily adaptable as-is for use
with ArchiCAD.
FOLDER HIERARCHY
The Digital Filing System
Tip: It is important to note that, as with any guideline, there will
always be instances that demand deviation (including those
developed internally). When it becomes necessary to make
modifications, we suggest that the inherent logic of the guideline
be followed.
Note: Using published standards as a guideline is strongly
recommended. They will make the drawings and/or template file
structure more familiar to new employees, contractors and
consultants making it easier to use, faster to learn and help to
mitigate missed information.
When people use standards and deal with others who use them,
the number of variations from file to file is reduced, making it
easier, more efficient, and more effective to share information. For
example, again in the US, the American Institute of Architects has
published the CAD Layer Guidelines, as part of the UDS, which
names layers by Discipline, Major Group, Minor Group, and
Status Code.
16
It is important that all the project information has a place to be

stored. If everything has a place, i.e. there are no Miscellaneous or
Misc. folders, less time is spent looking for files and there are fewer
problems with drawing links, and with archiving. ArchiCAD is
helping to make the management of the Virtual Building information
significantly easier by eliminating intermediate steps and allowing
PlotMaker to read the ArchiCAD .PLN directly. There is still a great
deal of information produced for a drawing set however, and careful
consideration should be given to typical jobs and where information
will be stored.
Tailoring ArchiCAD
Having separate folders for the different drawing and file types makes
their locations predictable; others asked to work on a project can do
so, and be immediately productive without having to learn an
individuals organizational system.
As project requirements and needs change, and more information is
generated, care must be taken in order to not become disorganized.
Short lists of files are much more user-friendly and manageable,
especially from within dialog boxes.
When setting up a directory, it is important to account for all of the
information contained within the context of CAD information. Due
to this information changing from country to country, firm to firm,
and project to project, the optimum folder set varies.
Tip: It is recommended that the CAD Manager(s), with the
assistance of project managers create a more inclusive
folder/directory structure to support all project types, allowing
project managers to cull as necessary to avoid overly complicated
structures when unwarranted.
Like practice itself, this 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 files)
Project detail files (.PLNs or .DWGs, DWFs, etc.)
3D Image Files
PlotMaker Layout Book(s) (.LBK files)
Externally created text or data files
The level to which the structure is broken down from that point is a
function of the firm and their projects.
17
Tailoring ArchiCAD
CUSTOM INSTALLATION
To facilitate the creation and maintenance of necessary standards and
procedures, ArchiCAD provides the means to encode specific
settings at the installation process.
It is possible and recommended that, when installing ArchiCAD, a
network location be defined from which the application will read and
load settings each time it is launched, to ensure that standard features
will be available and up to date across all workstations; as well as to
simplify the maintenance and evolution of said features by
centralizing their location. These attributes include Work
Environment Profiles and Schemes for both ArchiCAD and
PlotMaker, Default Libraries, and Translators.
See also the documentation that accompanies the ArchiCAD Folder, as well as
the Application Preferences & Profiles on page 18, Library Management
on page 41, and The Project Cartoon Set and the Layout Book Template on
page 89 for more information on creating and using Custom Installation features.
APPLICATION PREFERENCES &

PROFILES
There are many settings that should remain consistent from machine
to machine allowing everyone to work from a common starting point.
This can be invaluable especially if two or more people share
machines. Many of these settings are established within the project
file and will be in place when a new project is started from a project
template file (the following section deals extensively with project
template files). However, some settings are inherently stored within
the application preferences. These settings include everything from
custom menu shortcut keys and Info Box content, to floating palette
shapes and locations and menu contents. It is important for the CAD
Manager to determine the level of application flexibility based on that
particular offices methods of operation.
In ArchiCAD 9, it is possible to group and save many of these
settings through the creation of User Profiles also to transfer these
settings to other work stations. The Work Environment on the
Options menu allows the CAD Manager or user to make different
profiles available to different users.
18
Tailoring ArchiCAD
Note: It is crucial that the CAD Manager(s) establish a baseline of

standard application settings, not to constrain users, but to
implement a workspace that is consistently familiar and functional.
The Work Environment interface provides access to most of the
customizable interface settings from within one dialog (file specific
settings such as Background Color and Grids are still accessed on the
Options menu through Preferences, and discussed in more detail
below). The five customizable sets are bundled into Work
Environment Profiles consisting of User Preference Schemes,
Shortcut Schemes, Tool Schemes, Palette Schemes and Command
Layout Schemes.
Shortcut Schemes replaces the previous Keyboard Shortcuts interface

located on the Options menu under Customize. Though the interface
design has changed slightly, it functions in the same way with the
added benefit of simply using the intended shortcut to store, rather
than having to check boxes to activate modifier keys. It is also
possible to assign any command a single key shortcut; i.e. modifiers
are no longer necessary for menu commands.
The User Preference Scheme contains many of the settings previous

available from within the Preference dialog.
19
Tailoring ArchiCAD
Palette Schemes stores the position, shape, size and visibility of the
docked and floating palettes in the ArchiCAD main window, allowing
the interface to be reconfigured according to the user profile selected.
The Tool Schemes portion of Work Environment combines all of the

customizable features of the tools, including personalized Toolboxes,
Tool Settings dialog boxes, as well as the Info Box.
The Command Layout Schemes section allows users to customize the
Menu layout order and content as well as providing the ability to build
and edit toolbars. (Toolbars were previously unavailable on the
Macintosh, now they are available and customizable, providing single
click access to often used functions.)
20
Tailoring ArchiCAD
Project Cartoon Set and the Layout Book Template on page 89, and
referenced in the appropriate section of this manual as applicable.
Like other aspects of customization, if a guideline is used to create the
office standard, learning curves are reduced and productivity and
effectiveness are increased. Let us take a case in point where there
may be menu commands in ArchiCAD that are used quite frequently
but that do not have shortcut keys assigned to them by default
(depending upon which of the ArchiCAD provided schemes you start
with). If a menu shortcut key is added during a project, this new
setting or scheme will only be available from within that particular
copy of the application that created it. In order for a custom scheme
to be available on another machine, the custom Shortcut Scheme, or
in a larger office, a User Profile, needs to be created within Work
Environment and then exported as an .XML stored in a network
location to be accessed by all users.
Added versatility is attained through the Work Environment by each

section being able to be altered separately and saved out as either a
stand alone set of options; e.g. an office standard set of Shortcuts; or,
as and entire group of options customized to user groups, such as
Production Personnel, Project Manager/Reviewers, or Visualization
Staff.
The net effect of these new features is first, the ability to provide
users flexibility and power while not burdening them with the initial
set up; and second, simplifying the interface from several settings
locations to one settings location, making it easier to perform updates
as the firm grows, changes and improves.
This additional power and flexibility of the Work Environment is
further enhanced by the available Custom Installation options,
making maintenance updates less intensive for CAD managers and IT
staff.
Note: Custom Installation options extend from making available
custom profiles and firm template files to ensuring default libraries
load with each project and are discussed in more detail at The
Profiles and/or Schemes can be imported directly from a network

location, or download to a machine and then imported, from within
the Work Environment dialog to be used as imported or further
customized by the user as any other available Profile or Scheme could
be.
21
Tailoring ArchiCAD
Note: Profiles or Schemes that are imported by a user will reside as

part of that particular work stations preferences, thereby making
manual updating necessary to reflect external changes made to
those Profiles and Schemes I.e. changes are not automatically
reflected in a workstations settings when Profiles or Schemes are
imported.
The alternative to importing Profiles and Schemes, and the solution
for keeping firm standards up to date and consistent, is to point the
application Registry to a network location containing Profiles and
Schemes per the firms standards.
Note: When the Registry is direct to point to a particular location,
only the Profiles and Schemes located there will be available to the
user.
This method keeps all copies of the application consistent because
ArchiCAD will load the settings directly from this folder each time it
is launched. Changes therefore can be made to Profiles or Schemes at
any time while maintaining consistency and eliminating the need to
copy information to each work station.
22
The level to which standardized customization takes place is a matter

of firm type, size, organizational structure, user skill levels and
infrastructure. Each component should be evaluated as to the net
effectiveness weighed against personal work methods.
For instance, the need or desire to customize Palette Schemes may
arise due to varying display sizes in the office. Users fortunate to have
large displays can afford to have all of their palettes open and in
extended mode and grouped in one area to speed access to
commands and functions. With smaller displays, it may be necessary
to have some palettes hidden and/or have them in compact mode
and positioned to maximize the visible workspace. Having palettes
visible and extended does provide more information feedback and
makes information more accessible, but varying display sizes in an
office may force the standard set up scheme to show palettes in their
compact form so that the user is ensured a functional set up on
limited display area.
Standard Profiles can also provide benefit for offices where Principals
or Lead Designers often look at much of the work being produced,
and need to make changes to that work. For instance, a profile can be
set up on the network folder so that the Lead Designer has access to
his/her profile at every machine, making it comfortable and efficient
to make changes within a familiar interface. The Profile can be set
while the file is in use, and changed back following the revisions to
restore the original users settings.
Note: When installing ArchiCAD it is recommended that it be
done from a network folder to produce clean install
performance of the software on each machine while taking
advantage of the features available through the Custom
Installation such as Standard Profiles or Default Libraries. Using
Customized Installation allows the CAD Manager to perform
exactly the same installation on all of the computers in the office.
See details in the Read Me First file on your ArchiCAD CD.
See also The Project Cartoon Set and the Layout Book Template on page 89
for more information on creating a Custom Installation package.
Tailoring ArchiCAD
THE PROJECT TEMPLATE FILE

Customizing ArchiCAD involves the creation, modification and/or
deletion of certain components contained within and used by the
software to create a template file. These include the following:
Views and View Sets;
Layers and layer combination setup;
Display Option Combinations;
Pen Weights and Colors;
Line types;
Fill types;
Materials;
Composites;
User library setup.
Note: In ArchiCAD 9, the New from Template command in the
File menu allows you to choose among template files for starting a
new project. Any ArchiCAD project or archive file can be changed
into a template file by changing the .PLN or .PLA extension to
.TPL or by performing a Save As ArchiCAD Project Template.
Firm template files can also be made available in the New from
Template dialog by customizing folder locations in the Special
Folders tab in Options > Work Environment. The Work
Environment and Custom Installation are discussed in more detail
throughout the manual.
Where Do I Begin?
A project template file is a read-only file that is the starting point for
ALL new projects within the firm and should be used when
performing new/additional work on older project files. The most
compelling reasons to use a template file rather than opening a new
file are that:
all new projects open with the exact same attributes allowing
everyone in the office to understand the file organization
immediately
all new projects open free of errors and non-standard attributes
such as nonstandard layers, layer combinations, line types, fill
types, composites, etc.
It is important for the CAD Manager and the firms management to

understand the needs and time constraints of the firm before
embarking upon template creation. Every firm has its unique criteria
for their file, and what works for one firm may not work for another.
It is neither practical nor necessary to create the perfect file before
using it, as it will need to be altered as projects are completed while
using it and new ideas, methods and attributes are incorporated.
Note: The creation of a template file is an evolutionary process; its
capabilities and benefits will increase as it is used and refined over
a period of time.
One way to begin the creation of your template file is to purchase a
ready-made template file or use one provided as part of the
ArchiCAD installation. There are several resources for purchasing
ready-made template files; and, while these templates may shorten
your process of customization, they more than likely will not serve
each firms needs completely, and will require modification to be truly
effective and fit within established firm culture and methodology. An
alternate method of template file development is to hire an outside
consultant to produce the custom file. Though both are excellent
ways to get a head start on the process, neither may be appropriate
for your firm and it may be necessary to simply start with a file from
the firms previous software solution, or to build the template from
the ground up.
Some key questions to ask before purchasing a ready-made template
file, hiring a consultant, or beginning the process in-house are:
How much time will be allocated for file development?
Which drawings will be produced using the Virtual Building file?
Will the project ever be used as a TeamWork file?
Will drawings be generated at multiple scales?
Will consultants share this file directly or indirectly?
Will all of the project details be contained within the Building.PLN
file?
Note: Whichever path is chosen in order to develop the template
file, it is critical that all components of the file are well
documented. Documentation facilitates training, allows for
evaluation of the file and serves as a form of back-up.
23
Tailoring ArchiCAD
Contents of a Template File

Several components make up an effective template file:
proper views and view sets to ensure consistency and simple
navigation
adequate layers to ensure proper placement for all of the projects
elements without becoming overly complex or cluttered;
layer combinations to manage the project information while
working on the model;
display option combinations
commonly used custom line types, fill types, composites to
simplify and speed drawing;
well considered pen weights and pen colors that produce highly
readable output and reduce on screen eye strain;
custom material palette for better, faster visualization;
VIEWS AND VIEW SETS

One of the more powerful and useful feature sets developed in
ArchiCAD, which has become an integral part of a well functioning,
well-equipped template file, is the Project Navigator > View Editor
> Publisher. Serving several primary functions, this feature set
provides the means for: moving through and working on complex
Virtual Building models; assigning attributes for the proper output of
information with regard to both content and graphic quality;
streamlining procedures for sharing information amongst consultants
and/or in-house departments.
The first step in utilizing these functions is to identify the Views that
will be used for all typical projects. Views are definitions that contain
Layer Combinations, Display Option Combinations, Scale and Zoom.
These definitions are what PlotMaker reads in order to get the model
information onto the layouts.
24
Note: It is extremely important to specifically and descriptively

name each view created both standard views in the template, and
added views in the project.
Naming Views is important for two reasons: first, by default,
ArchiCAD will name the view with the story designation and story
name; and though the view may be moved to a specific folder within
a specific view set, when importing it into PlotMaker, it may be
difficult to import the proper view if many have the same name;
second, if the name is specific, it can be used by Title Types in
PlotMaker making it easier to label drawings on the layouts and easier
to maintain those labels.
Tailoring ArchiCAD
An implementation of these functions would be to create discrete

View Sets for
1 daily work on a project by the in-house design team that would
take into account the necessity for view customization and view
creation;
2 linking information to the .LBK for plotting and printing ensuring
that most if not all, typical views for all typical projects are created
with proper attributes and settings for dependable output;
3 producing various file types to share as required amongst either
consultants (taking into account file type, destination, translator
settings) or in-house departments (addressing file type, size and
save location).
Since the Navigator plays such an important role in the project work
flow, it should be considered carefully while the template is being
created. It is not difficult to over complicate the feature set with many
different View Sets containing many different options. The advice
here is to start simply, and build upon the needs of the users as
familiarity with the features increases and the desire to use more of
the applications functionality grows. There is always a trade off
between simplicity, and versatility/flexibility. The balance that needs
to be struck can only come about as the application and the
associated standards are used and tested.
Some questions to consider when developing view sets:
Is it necessary to have different view sets for the different project
phases, i.e. is the building information content and display
different enough between, say Design Development and
Construction Documentation, that it justifies the creation of
separate view sets?
25
Tailoring ArchiCAD
As a general rule, it is always best to use and reuse information in the

simplest form possible. With that said, it is recommended that unless
there are extenuating circumstances warranting multiple sets for
project phases on a typical basis, one well defined set be created and
maintained, using PlotMaker to create the differentiation between
phases.
Is there a need to share project information with various in-house
departments such as Engineering, Visualization or Business
Development?
Various in-house departments that are typically involved with all
projects tend to warrant having Views and View Sets created to serve
them specifically. By creating views specific to their needs and
including them in the template file, those departments are ensured
consistent information for each project regardless of the user
producing the project.
Are many outside consultants used with whom information needs
to be shared?
For similar reasons to the inclusion of views for in-house
departments, the same is true for outside consultants. By including
views specifically designed to serve outside groups, such as structural
or mechanical engineers, those consultants are assured consistent
information from the firm, rather than from individual members of
the firm.
How tightly will the ArchiCAD template be integrated with the
PlotMaker layout book template?
The more tightly woven the two pieces of the ArchiCAD solution are,
the more thorough and complete the Views and View Sets need to
be. For instance, if the .LBK is pre-linked and populated with
information from the ArchiCAD template, it is better to have all of
the typically used views for all typical projects set up and linked;
because, as a rule it is easier for the majority of individual users to
remove superfluous views from their projects than it is for them to
create necessary views, replete with all of the standard and necessary
attributes, and link them to their .LBKs.
Should provisions be made to allow users to customize all or some
View Sets on a project specific basis?
The advantage and disadvantage to having all of the views necessary
for a project predetermined is that, though the output will be
26
consistent and much easier to attain and maintain, working on the

project in ArchiCAD can become cumbersome or complicated by
not being able to manipulate different views to work effectively. The
recommendation here is that there be specific sets that control the
output and other sets that are used for moving through and working
on the project. It may be less intimidating and more flexible to users
if there is a primary working set constructed to allow the user to add,
edit and delete views to facilitate modeling and developing a project
while keeping the linked .LBK views unaltered and in tact.
Note: It is best if the template View Sets are produced after all
Layer Combinations and Display Option Combinations have been
established. Layer combinations can be modified to include or
exclude layers, etc., with established views not being affected as
long as the combination name doesnt change. Changing
combination names after Views have been established will cause
the Views to have a Missing Combination, forcing its
redefinition.
for additional information.
Tailoring ArchiCAD
LAYER MANAGEMENT AND SETUP

As noted above, it is important that due diligence be performed with
regard to layer management and setup. Changes can of course always
be made to Layers, Combinations, Views and View Sets; it is simply a
matter of the time that it takes to ensure coordination and cohesion
in the template as more and more pieces are completed. Therefore it
should be stated again that one of the larger and more critical parts of
customization is the creation of Layers and Layer Combinations.
Most firms using ArchiCAD or switching to ArchiCAD have existing
layers in place to manage their information, allowing these layers to
be edited and/or modified to serve in the use of the Virtual Building
system.
Note: Switching from a two-dimensional drawing environment to
a three-dimensional environment is not as simple as adding or
deleting layers. It requires a rethinking or reorganization of
thought processes. The model as a whole has to be considered as
well as all of the individual resultant drawings and layouts and
layers have to be carefully considered as to what information they
should contain, when they are visible or hidden locked or
unlocked.
adding extensions to the name of the layer. An extension is a text

entry typically consisting of a few letters and has its own column in
the layer dialog. By structuring layers using extensions, one can get a
quick overview of 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.
Evaluation of Firm Project Types

Different project types may demand different setups, depending
upon the intended use of the Virtual Building file. One particular
template file may not be suitable for varying project types. For
example, a residential project may require layers for more detailed
framing plans, while a hospital may need layers for extensive
equipment planning.
Note: It is important for the CAD Manager(s) to work with the
project managers on the best approach for the firms template(s),
thus choosing between one template to be used for all project
types in the firm, or multiple templates to be created according to
project type.
The Use of Layer Extensions

In addition to using layer names as a means of managing data,
another useful technique of organizing layers can be achieved by
An example of layer extensions for use in offices doing a lot of

refurbishment works can be the following:
.n for new works;
.e for existing;
.d for demolished.
Tip: For proposed new construction plans show layer extensions
.n and .e; for demolition construction plans show .e and .d.
Another system for offices working on large developments is to
structure the layers according to the way the building has been
divided into different teams working on the project:
27
Tailoring ArchiCAD
.clad for those working on the building skin;

.sub for those working on the building;
.core for those working on the building core; .int for those
working on the interior design;
The Use of Layer Combinations

Layer combinations are an important part in the production of
accurate, well-documented Virtual Building models and are for all
intents and purposes, mandatory in the ArchiCAD workflow. Layer
combinations provide several advantages for the efficiency of a
Virtual Building project, including:
a way to easily manage information while working on the project
without excessively accessing the Layer Settings dialogs box;
a way to effectively and confidently produce the two-dimensional
drawing output;
providing assistance in putting elements on the appropriate layers;
a way to control the amount of layers that appear in the scrolling
list within the tools dialog box.
Tip: It is recommended that a policy be established, under which
all work would be done within the project file with a Layer
Combination selected, ensured by using the Project Navigator to
enable specific views.
The main purposes for creating layer combinations are to:
to work with, and display on the screen, the information as it will
appear on the drawings, i.e. within the project Layout Book;
create temporary combinations that enable the user to effectively
and efficiently model the project.
A custom or temporary combination allows for all of the necessary
information to be accessed quickly and repeatedly without manually
toggling many different layers in the dialog box. As an example, when
modeling the elements of a ceiling, it is often necessary to see
additional information that might only be visible in a floor plan layer
combination.
Note: Layer combinations work extremely well to define the
visible information that will appear on the plotted layouts. By
setting up all of the necessary layer combinations and views in the
templates, output with accurate information can be assured.
28
When to Lock, Hide, or Show

Visibility of a layers information within a Layer Combination is
dependent upon the desired output. Obviously, if a layer contains
information that needs to be visible for a particular drawing,
rendering or animation, it is necessary for that layer to be visible.
Carefully constructed template files should take into account layer
combinations that not only toggle visibility, but also toggle availability
(whether or not they are locked). Layers availability is a more
subjective choice than their visibility. Availability does not affect the
display of the model, drawings, animations, or renderings. It is simply
a device for assisting the user in information management.
The purpose of layer combinations that have visible, non-visible and
locked layers is to aid the user in placing elements on the appropriate
layers.
For instance, while working on a foundation plan, it is often necessary
to know where all of the plumbing fixtures are located. Though the
fixtures are visible, it may not always be appropriate to have the ability
to edit those fixtures in that particular layer combination. Therefore,
having the plumbing fixture layer locked but visible allows the user to
see the appropriate information without being able to edit and
potentially create conflicts with elements cause other problems in the
floor plan, reflected ceiling plan or sections. Having the plumbing
fixture layer locked also helps in avoiding inadvertently placing other
object types on that layer, e.g. placing a steel joist on the plumbing
layer.
Tailoring ArchiCAD
Tip: Although not critical, it is highly recommended that the

firms master template file(s) take advantage of layer availability.
Another benefit to having some layers locked in various Layer
Combinations is to limit the list of available layers in a tools dialog
box. This does two things: it helps to ensure the placement of
elements on the appropriate layers and limits excessive scrolling in
both the tools dialog box and the Info Box.
Note: Whether a layer is visible or not, the user retains the ability
to select that layer for the creation of an element. This is not the
case when a layer is locked. Locked layers do not appear in either
the tools dialog box or the Information palette, provided that
youve checked the appropriate box in the Preferences >
Miscellaneous dialog box.
29
Tailoring ArchiCAD
DISPLAY COMBINATIONS
The ability to control the display of information has always been part
of ArchiCAD. In the past, changing the display was done on an
as-needed basis, and done step by step in the Display Options
dialog.
The process was a bit cumbersome and time consuming, and it often
caused problems due to the amount of options that potentially
needed to be changed in order to achieve the desired results.
To facilitate changing the settings, Display Options Combinations
were introduced to toggle information as a set, like Layer
Combinations, that could be used effectively, efficiently and with
30
confidence, and then grouped with other information within View

Sets to streamline the workflow. Like all other parts of the template
file, consideration needs to be given to how the firm operates and to
what level flexibility is consistent with simplicity.
By default, there are five (5) Display Options Combinations that can
be used out of the box or that can be customized. It is also possible
to add firm specific combinations. More than likely, some
combination of these three options will be used to make the most of
the features. For instance, it may be helpful to set up combinations to
configure the architectural backgrounds for engineering consultants.
The differences between combinations could be that it is necessary to
hide the individual skins of a composite wall for the Mechanical
Tailoring ArchiCAD
Engineer; yet show the skins for the Structural Engineer. Display
Options Combinations could be established for both needs making
the configuration simple and automatic if setup in the template file.
Tip: It is possible to edit a combination by select a combination,
making changes and selecting Save as. The Save Combination
window will appear with the previously selected name, appended
with copy. Simply delete the word copy (along with the added)
space and click Save. A prompt will ask if you want to replace the
combination; click Replace. You have now edited the
combination.
THE IMPORTANCE OF CUSTOM

ATTRIBUTES
ArchiCAD works well for producing excellent three-dimensional
Virtual Building models. The key to using it effectively is to tailor it so
that the firm is able to consistently produce the necessary product
accurately and efficiently. Custom pen colors and weights, line types,
fills, composite structures, materials and textures allow for more
information to be included in simple elements.
Note: It is highly recommended to keep the Virtual Building
model intact and to only add 2D data where necessary, for
instance graphics. Most instances where 2D information is being
considered, can be accomplished with a carefully considered 3D
element.
Pens Weights and Colors

Having standard pens for use within a firm helps to increase the
consistency of output and provides flexibility in the display of
different drawing types; and it is recommended that firms establish
standard pens and design groupings of pens/pen sets, to suit specific
needs.
Note: Tests should be conducted to ensure that selected weights
are distinguishable when plotted and that they reproduce well, and,
as always, the simpler the system is, the more reliable it will be.
31
Tailoring ArchiCAD
There are certain pens that should be considered carefully, and tested
when altering their default weights as there is the potential that they
will produce unexpected and/or undesired results when output due
to their use by many standard ArchiCAD objects. These pens are:
Pens 2 & 3: used by many of the standard windows and doors 2D
and 3D options;
Pens 7 & 8: used as contour pens for many objects;
Pen 91: the default white pen used as a fill pen for many objects
background fills.
Note: Because the project work is a digital model, displayed on a

low-resolution screen, pen colors are mainly for distinguishing or
visualizing pen weights; i.e. it is simply a working aid. If color
output is desired, the results will vary significantly from station to
station, printer to printer and application to application, even
when using identical pen sets or industry standard color palettes.
By creating pen sets in ArchiCAD and modeling elements using the
pens in different sets, it is possible to create and control different
output results from within PlotMaker with a couple of clicks.
32
Tip: By having one set of pens as the primary modeling pens and
another set as emphasis pens, it is extremely easy to achieve a
particular drawing affect of highlighting certain information while
screening other context information.
For instance, drawings that could benefit from this method are
structural framing and reflected ceiling plans. These drawings would
have their context floor plan information (walls, etc.) screened back
while the emphasizing their particular subject, i.e. framing members,
lights, mechanical diffusers, soffits, etc. Using pen sets effectively can
raise the level of information in a drawing and add graphic
complexity without altering element attributes in ArchiCAD.
Though pen sets add power and can help achieve better looking and
more informative drawings, they add complexity to a template file
that requires greater attention from the users. Users need to
determine when creating an element, how it is to appear in different
instances and render it with the appropriate pens, or have the
attributes set as part of a Favorites file. This level of complexity may
or may not be appropriate for all users in all firms.
Tailoring ArchiCAD
Pen Setup
In this example, the first ten pens are the primary pens and are used
for the creation of most elements and have the flexibility of being
printed black or gray. The second set (pens 11-20) is used for
elements that will always be printed in black. The third set (pens
21-30) is used for elements that will always be gray, possibly existing
information, owner furnished equipment, or elements not yet
determined or designed.
See also Utilizing Pen Sets in PlotMaker on page 69 for more information on
using Pen Weights and Colors.
Line Types
In the case of a Structural Framing Plan, the way it works is as
follows: when modeling the walls, doors, windows, i.e. information
common to other drawings, and that which will be desirable to plot in
black (Floor Plan) or gray (specialty plans such as the Structural
Framing Plan), the first set is used. When creating the framing
elements, text, dimensions, notes, i.e. information particular to a
drawing, and which will be desirable to have in black only, the second
set is used. With the model/drawing elements rendered with the
appropriate pens within particular groupings, their final output
display can be controlled/tailored in PlotMaker,
Custom line types allow the user to produce scalable lines that are
particular to the firms 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 be made to contain numbers
to indicate a fire rating, or to indicate a color of paint on a curb, or
can be used to draw in elements such as batt insulation.
33
Tailoring ArchiCAD
Tip: 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.
For instance, at an early stage in a project, the owner is interested in
seeing the building section. It has not however been engineered for
structural requirements, therefore, framing members have not yet
been modeled. Without the framing members the section does not
appear very informative. By creating a line type that resembles a
cross-section through framing members, the section can be
embellished quickly.
Fill Types
Similar to lines, ArchiCAD fills can be created to convey more
accurate information with less effort. The use of custom fills
simplifies the task of drawing accurate floor covering and/or wall
texturing information. Custom fills also assist in creating custom
composite structures that are often used in architectural practice.
Note: By utilizing and editing the standard fills and creating
custom fills, it is easy and more effective to have specific fills that
provide more information rather than generic fills that merely
attempt to resemble a component or that appear graphically
similar.
For instance, instead of simply using the general fill called Facing
Tile to represent a specific tile, the fill could be duplicated, edited and
then saved as Quarry Tile Q-1234. This specific name aids in
selection, listing and editing.
In order to create this line type, one section was first drawn. The
elements were then copied to the Clipboard. The scale of the drawing
was changed to 1:100. In the Line Types dialog box, a new symbol
line is created. Click Paste line components. The dash is now set at
whatever distance required, in generic units. For instance: if a truss is
to be repeated at 16 on-center, the dash is set to 16 and should be
set to Scale with Plan. When the model is returned to its original
scale, the line type is available and appropriately sized.
Tip: By starting the name with special character e.g., a space
(Mac), or + (Windows) the new fill is moved to the beginning of
the alphanumeric list. This helps to find and track fills used in the
project.
34
Tailoring ArchiCAD
Note: When creating custom fills, it is best to use and edit existing
fills. The reason is that, when line components are pasted to create
a custom hatch, it is generated as a Symbol Fill. Symbol fills take
significantly longer to render than the optimized vectorial fills
supplied with ArchiCAD.
Though this may seem like a minor detail, it can be quite effective
when applied to many users. Now that there are standard composites
in place, it is important to use them as they were designed. That
means checking the boxes in the tools dialog boxes to render the wall
with the defined line types, pens and background.
Composites
It is recommended that commonly used composite structures be
created and included into the template file. This allows all users to
access wall types, floor systems and roof systems that are
dimensionally and graphically consistent, without having to create
them again for each project. These standard composites can be edited
as necessary to meet the needs of particular conditions on each
project.
Tip: When a standard element is edited, it is best to edit a copy
and retain the original for future use. It is also recommended that
all walls, floors and roofs modeled in a project be constructed
using composites.
This not only ensures dimensional stability throughout the model but
also makes for easier editing should criteria change. As with many
features in ArchiCAD, there are standard composites that are part of
a new file. These ArchiCAD composites may need to be deleted
and/or edited to satisfy an individual firms requirements. Another
tactic in creating composites is to be certain to select its availability as
a wall, slab or roof, or combination thereof. This will limit the
number of options in the respective tools dialog box.
35
Tailoring ArchiCAD
In ArchiCAD 9, it is possible to customize the pen weights between

each of the composite skins, but also the line types. Aside from the
obvious benefit of controlling the legibility of the composite, this
feature can be effectively used to provide status wall types; i.e. a single
well defined composite can be triplicated to designate demolition,
existing and new condition by altering the line types separating the
various skins.
project. Custom materials attributes can make it easy to select more

generic descriptions that allow for easy editing at a later stage of the
project. One method for making these materials effective is to create
options that are rendered in values of gray and that are categorized by
element or system. For instance, instead of assigning to a wall an
outer material of Red Brick, and an inner material of Rough Plaster,
it is more beneficial to use materials such as Masonry-Brick-Dark-1
and Wall-Interior-Rough-Light-2, until refinements are made
substituting actual product names and colors for the generic ones.
Tip: Using the same principles as the layer naming conventions,
materials have a core material, a type material, a value, and
numeration, making the system easily recognizable and usable.
Warning: Be extremely cautious when editing materials.
Removing ArchiCAD materials from a project file will cause all
library parts that reference those deleted attributes to revert to
some other default material. Loaded third party libraries often
bring with them custom, and/or redundant materials, that could
result in conflicts and errors.
Refer to Using Attribute Manager on page 39.
Textures
Textures, like materials, deal mainly with visualization. Having a
library with many textures allows for more accurate renderings.
Textures are libraries that can be included within a third party
solution, or loaded as an additional folder.
Note: As composite groupings are made and named it is
important to maintain standard conventions for listing purposes. It
is also a good idea to leave unassigned spaces that already contain
some base information available at the end of a grouping for the
creation of job-specific composites.
Materials
Where customized lines, fills and composites deal more with the
accuracy of the model and the two-dimensional output, materials
assist in producing more accurate photorenderings and animations.
Materials play an important role in the design and visualization of a
36
Tailoring ArchiCAD
Libraries can be purchased and created in-house. Depending on how

the firm is organized and what type of work it does, the strategy for
loading and storing texture libraries can vary.
See also Library Management on page 41 for more information on building
and maintaining libraries.
Tip: Texture libraries can be compartmentalized and loaded to
serve particular projects; e.g. a masonry library could be divided
into concrete, brick and stone, helping to reduce the number of
unneeded textures.
General Note: For editing line types, fill types, composites,
materials, and textures, it is recommended that an additive
approach be taken. Editing and adding to the default settings
within ArchiCAD helps to maintain database integrity. Deleting
attributes can cause unexpected results and create maintenance
issues in the future.
THE STORIES APPROACH

Corresponding to ArchiCADs three-dimensional nature, stories
enable the user to further organize information rather than rely
exclusively on layers. Stories allow the Virtual Building to be
constructed much like an actual building and reinforce thinking about
section and elevation.
The Stories feature allows layers to be used in multiple workspaces.
This means that all layers are available on each story. Stories can have
any height, even zero! Taking advantage of stories helps to minimize
the number of layers needed to organize a project and increases
flexibility. Typically, it is helpful to set story height as the
floor-to-floor height of a building. Modeled on a story would be the
finished floor, its structure, and all elements on that floor, including
the ceiling information.
Note: A number of stories, their heights and names, should be set
up in the office template file as a general guide, then edited by the
project manager upon the requirements of each individual project.
Strategic Ways to Use Stories

Stories do not have to be exclusively associated with the stories of a
project. Stories can be created to serve as additional project
workspaces, places to hold:
custom library objects; a workshop;
modeling helper modules, or kits of parts;
scanned background images;
multiple design options;
imported DWG or DXF files.
Tip: Commonly used information can be accessed easily from all
stories by option/alt-clicking items made visible using the Ghost
Story functionality.
Tip: You can use existing DWG or DXF files to quickly set up
your ArchiCAD virtual building. First, merge the DWG or DXF
using the proper layering filters and/or procedures. Secondly,
place the contents of the merged file onto a dedicated layer. For
example, you could create a layer called guidelines onto which
you would place the merged DWG or DXF information. Once
placed, this guidelines story can become the active ghost story,
allowing you to use the underlying information as an overlay base
to create an ArchiCAD model.
See also Using Favorites on page 40 for an alternative method of accessing
resources.
SETTING UP THE WORKING

ENVIRONMENT
Standards are set up primarily to help a firm achieve quality and
consistent output. Several of these key settings include:
Background and Grid Options;
Working, Dimension and Calculation Units;
Work Environment.
37
Tailoring ArchiCAD
Building the Template File

There are a number of techniques to build a template file:
Copy a good project example.
Create a new file and add resources.
Use the Attribute Manager to copy the correct components from a
variety of sources.
Use the Favorites palette to transfer your most commonly used
ArchiCAD elements between project files.
Tip: The New from Template command enables you to use any
of your existing projects as a template file. You only need to
change project files to templates by changing the .PLN or .PLA
extension to .TPL or by performing a Save As ArchiCAD Project
Template. Opening the template will bring up the project file
with its full content while automatically renaming it to Untitled
by default. You can then save the project under the required
project name.
Background
The project background is a file specific setting defined by a user
within the project file. The template will contain background
information when opened. While different users have their
preference of background color, it is important that one color be set
as a standard.
Note: Background color will affect the choice of drawing pen
color and how information is processed when sent to an output
device.
For example, with the use of a black background there will more than
likely be a white pen. This means that when going to plot, there will
need to be a conversion of the white pen to some other pen with a
value greater than zero. This can be set in PlotMaker using pen sets or
through scripting, but is to be avoided if a near-white background is
used. Locating selection dots can also be problematic with a dark
(black) background.
One advantage to using a white background is that it is easier to
envision since most output is typically on white media.
Tip: Always use a near-white background with contrasting pen
colors to help simplify the output process and help reduce
38
eyestrain. Near-white, as opposed to pure white allows for the

identification of elements rendered in white pens such as object
background fills and lines from externally obtained files.
As a means of mitigating the problems associated with having
invisible information, ArchiCAD utilizes a feature to automatically
change pens to avoid invisibility.
Pen Weights and Colors

Pen colors typically equate to line weights and do not/should not
refer to a specific layer; their settings reside in the project file.
Elements are routinely made up of multiple line weights; therefore, it
is important to set up pens with colors that are easily differentiated so
as to manage the use of line weight. It is recommended that tests be
done to determine which pen weights print/plot and reproduce most
effectively. All 255 pens can have discrete colors and line weight.
Note: The inclusion of 255 pens/colors is mainly for
compatibility between CAD softwares.
Tip: It is recommended to minimize the number of line weights
and colors used, while retaining flexibility and precision. Just
because you can have 255 different colors and line weights, does
not mean you should use them all.
Decide on pens whose line weights are distinguishable. For example
.05 mm, .15mm, .30mm, .45mm, .70mm, .90mm, etc. This will give
better readability to the drawings while not overloading the user with
too many pens.
See also Utilizing Pen Sets in PlotMaker on page 69 for more information on
Using Pen Sets.
Working Units, Dimensions and Calculation

Units
One of the most important reasons for starting all new projects from
a standardized template file has to do with unit settings. All users
working within the firm or office should have confidence in the fact
that when they sit down to work on a project, all the tolerances will be
in compliance with the established standards. There are many
opinions on what is the most effective use of tolerances. Taking into
account a computers drawing precision, should modeling be done to
Tailoring ArchiCAD
the nearest 1/128th of an inch or 1/10th of a millimeter? Or should it

be kept simpler and rounded to the nearest 1/8-inch or
one-millimeter? Regardless of the decision made by the CAD
Manager(s) and the project managers, it is best that the working units
and the dimensional units remain consistent. These units should not
be changed through the course of a project so as to avoid
dimensional inconsistencies.
The calculation units can be set to whatever tolerance necessary for a

particular measurement. It is possible to change these values during
the course of a project. Calculation unit tolerances do not have the
same effect on the outcome of a project in terms of its
constructability as the working units and dimension tolerances
mentioned above.
Work Environment
As mentioned earlier, setting up standards in terms of the graphic
user interface, and the consistency and availability of commands and
features is a major component to streamlining workflow processes
and producing quality consistent work. It should be carefully
considered how the firm will treat the use of Profiles and Schemes to
allow users the flexibility to tailor their own environment while
maintaining a rigid enough framework for the firm to function as an

efficient unit.
Refer back to Application Preferences & Profiles on page 18 for more
information.
Font Types and Sizes

In order to establish a standard look to the production drawings for
the entire office, it is important to set up separate template files for
drawings of each different scale. These template files will most
certainly have examples of all the standard texts (font types, styles and
heights) for different types of building elements (window/door
dimensions, labels) and other drawing conventions within the office
(dimensions, section symbols etc.). The following example shows a
possible way of sorting scale specific information by layer extensions:
-text.2, -.5, -.10, -.20, -.50, -.100 layer extensions for text
information that is to be shown in the respective scale only.
USING ATTRIBUTE MANAGER

The development of an elegant template is evolutionary. Just as
practices change, so do the tools necessary to be effective and
efficient in practice. As the template is refined, it is often necessary to
update ongoing projects with new attributes. The Attribute
Manager is an effective way to keep all files current. Rather than
trying to manually add layers, combinations, materials, lines, etc., it is
possible to save an .AAT file the can be opened from within Attribute
Manager to update that projects information as necessary.
Tip: Depending upon the level of refinement of the template file,
it may be effective to save individual .AATs to manage the changes
to layers, combinations, pens, materials, etc. separately.
Transferring Custom Attributes

Once a template is set up and published for use within the firm, a
system should be put in place to evaluate suggestions, review
comments, and make the necessary modifications.
As a general rule, one person (the CAD Manager) or a committee
should be responsible for keeping the template files up to date. Ideas
39
Tailoring ArchiCAD
can be collected from the users, and, once agreed upon by a

committee as being relevant and necessary to the template(s), changes
can be made. AATs can be saved for individual project managers to
then merge into current jobs.
Tip: Attribute Manager can be used to custom build a template
for use with particular projects by merging in only relevant
attributes, reducing clutter and superfluous information.
See also Attribute Manager in the ArchiCAD 9 Reference Guide for more
information.
USING FAVORITES
The Favorites palette enables you to quickly access frequently used
ArchiCAD tools and custom settings. You can save a favorite group
of construction/documentation elements with their settings to a file
(name.prf), which allows you to transfer them between projects. You
can also save frequently used groups of elements to be selected. For
example, if you need to edit all the fire doors, you can save this
selection and return to it from the palette at any time.
There is no need for the project template files to include actual
architectural elements on the Floor Plan, as template files only need
to have the appropriate attribute settings. The specific element
selections and settings should be defined in the Favorites palette. The
favorite settings for the actual project file can be loaded in at any
stage.
CAD Managers can set up individual sets of Favorites for different
project types. The content of the specific Favorite sets can contain
the most commonly used architectural element types (wall, slab,
column, roof, door, window and other object types) as well as the
typical 2D documentation tools (font, line, dimension types) for the
respective project type (residential, industrial, commercial, etc.).
Moreover, Favorites can now have certain parameters excluded when
saved out, through Favorite Preferences > Favorite Parameters
Exclusions. A particular use for this feature could be the addition of
wall types without the inclusion of height definition, or any object
without an ID.
40
Note: The Favorites Palette does not carry the actual attributes
of the tools over from file to file.
Library Management
LIBRARY MANAGEMENT
Project libraries are a major part of using ArchiCAD effectively. Many
decisions need to be made with respect to the use and maintenance of
office libraries and several key factors must be considered when
implementing a particular office library solution.
These key factors include:
types of libraries;
location of the libraries;
loading time;
adding, updating;
FTP Libraries;
on-line acquisition.
TYPES OF LIBRARIES
In their simplest form, library parts can be divided into two
categories:
parts that assist in creation of construction documentation;
parts that aid in the enhancement of presentation quality material.
Library types are a key factor in successful library management in
terms of when parts from these libraries are to be used. For example,
the project team involved in the production of construction
documents may only need parts fundamental to those documents;
items such as north arrow, graphic scale, toilets, windows and doors,
mechanical and electrical symbols, etc.
Conversely, those tasked with marketing, visualization and/or

presentation would need parts that are more decorative in nature;
items necessary to enhance the basic material, such as people, trees,
vehicles, specialized furniture, etc., yet not necessarily integral to the
building design or its documentation.
41
Library Management
members should add additional TPLs if the model needs to be

enhanced or furnished for visualization.
Note: By defining a DefaultLibrary.XML ArchiCAD will always
load the libraries defined in this file, such as the AOL and OSL
thereby mitigating the occurrences of files opening with missing
parts. The definition of the DefaultLibrary.XML and its reference
from ArchiCAD is done through the Registry as part of a Custom
Installation.
See The Project Cartoon Set and the Layout Book Template on page 89 for
more information.
A DefaultLibrary.XML can also be especially helpful with PlotMaker
launching BGArchiCAD in order to read a TeamWork file that may
have had libraries remapped by users. The DefaultLibrary.XML
placed next to the .PLP, will have the paths contained therein which
will be run if BGArchiCAD finds that a particular library is
unavailable.
In an effort to speed the loading time of libraries, ArchiCAD has the
ability read libraries directly from an archived project, .PLA; the
default format for the AOL. ArchiCAD can still of course read a
hierarchical folder structure (HFS) library, but it is recommended that
a .PLA library be used whenever possible for both speed and
standards integrity, since it is much easier and faster to read one larger
file than hundreds of smaller ones. Moving and copying libraries is
also made more efficient for the same reason.
In whatever way, and by whom the library objects are to be used, they
should be organized into separate libraries:
the most current releases ArchiCAD Object Library (AOL);
an office standard library (OSL), which could be further
sub-divided into visualization and documentation, or others;
project specific libraries (PSL);
third party libraries (TPL);
Tip: It is recommended that the firms standard template file(s)
load by default, the AOL and the OSL from the network server or
local hard drive as outlined herein. Each project once established,
should also load the PSL from the project directory. Specific team
42
Library Management
ArchiCAD Object Library
Office Standard Library
The AOL should always be loaded by default with the firms template
file(s) and by extension, each project, as it contains all of the required
macros and necessary components to make all objects function
properly.
The Office Standard Library is defined as the library that, in addition

to the AOL, will be loaded with each and every project within an
office. The OSL will contain all of the objects created, edited or
adapted by the firm as a standard to suit specific needs. Like the
AOL, it is best if the OSL is accessed as a .PLA rather than in an
HFS; this decreases loading time, and maintains the librarys integrity.
The CAD Manager along with assigned office staff, should determine
a workable OSL based upon staff skills, project types and firm
provided services; as well as be responsible for its maintenance.
Project Specific Library
By always loading this library as it is shipped with ArchiCAD, the

transition process from one release version to the next is simplified. It
also reduces the amount of maintenance required by a firms library
structure; i.e. most of the objects used on a daily basis will come from
the AOL, with the majority of the rest residing in the Office Standard
Library. If these libraries were combined into a single master library,
the task of adding all of the firms objects to each new releases AOL
would be significant and the potential for objects to be missed in the
update greatened.
The Project Specific Library is defined as the individual library folder

that is created specifically for each project within an office. The PSL
is included within every projects directory/folder at the time it is
created and is maintained as an HFS.
The PSL 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 OSL. Once created, custom
parts can be evaluated as to their relevance for inclusion into the OSL
at any time.
Tip: Standardized List Templates can be included in the OSL and
saved into the PSL once modified. In order to be able to save List
Templates into a PSL, it is necessary that it be the first library
loaded by a project. ArchiCAD cannot write to a .PLA library, so if
the AOL or the OSL loads first, changes to a List Template cannot
be saved. It is recommended that PSLs carry a job number as the
first characters to ensure it loading first.
43
Library Management
One of the drawbacks to loading multiple libraries is not being able to

locate objects quickly because there are several similar locations
where it could reside (as recommended above, the OSL should be
organized as is the AOL). Having to search separate locations for a
particular object can be eliminated by sorting the libraries directory
by Subtype, rather than by the default Folder View. This alternate
viewing groups like objects together regardless of their resident path.
44
Tip: Within the Object dialog it is possible to display objects in

Folder View, Subtype View or Find Library Parts enabling the
search for objects by Keyword making it easier than ever to locate
specific objects.
See also Creating and Maintaining an Office Library on page 49.
Library Management
LOCATION OF LIBRARIES
In the following section, we will outline concepts and possible
solutions as they pertain to the location and usage of office libraries.
In particular, we will discuss:
network libraries;
local libraries;
FTP libraries.
It is recommended that the AOL remain in its default location
within the ArchiCAD folder created by the Installer. Because the
library does not get edited and its location is consistent from
machine to machine, the template files Library Manager can use
the same path regardless of file or user to access the library.
Network Libraries
Network libraries are loaded from shared directories/folders on a
server, and are highly effective and easily maintained as an office
solution. It is an excellent way to provide access to the OSL, while
making it easily maintainable.
To learn more about loading libraries refer to the Library Management in the
ArchiCAD 9 Reference Guide.
In order for the network solution to work effectively, the CAD
Manager(s) must ensure that:
only one copy of a particular library exists on a specified server;
the OSLs location is write protected, or, read only;
naming and organizational conventions remain standardized.
Note: Using a network library can significantly decrease operating

speed as it is accessed by multiple users. In order to maximize
library speed, it is recommended that, before any major library
change in the network library, the CAD Manager Update Library
Parts. If you are using a mixed network, this operation should be
repeated for both platforms.
Having a single copy of a library ensures that the entire office is using
the same kit of parts on each project. Also, if more than one copy of a
library, or part of a library resides on a network, there is the risk of
duplicate parts being used from these various locations. This
duplication increases the chances of parts to be reported as missing,
or for incorrect information to be included in a project, as well as
creating a reduction in overall efficiency.
Project quality is greatly enhanced when the system is predictable,
and users are able to locate and implement the necessary objects
quickly. If users are required to navigate a complicated or
ill-considered library structure, time is spent finding items rather than
exercising their parameters and making more precise project
documents.
45
Library Management
Moreover, if duplicate libraries are loaded it is possible that not all

parts will be available from within a specified folder: some parts will
be available in one copy of the folder, and the remaining items
available in another copy of the library. Though there is still access to
all of the parts, time is wasted moving between folders, making the
system unpredictable and unnecessarily complicated. Though sorting
the libraries by Subtype helps eliminate some navigation as discussed
above, loading duplicate objects will also compromise the integrity of
the system, lowering efficiency and effectiveness.
Making the OSL read-only is critical if the information placed in the
model is to be reliable. If users are able to edit a standard library,
modifications can be made to the library, which will then affect all
projects loading the modified objects resulting in incorrect
information in multiple project documents. Using .PLA libraries
eliminates the users abilities to edit the objects default parameters
though the location may still not be secure.
Tip: To make a library location read-only in Windows, right-click
on the root folder housing the OSL and select Properties from
the pop-up menu. In the Properties dialog box select the
Read-only checkbox.
The Localized Solution
On the Macintosh, control-click the librarys folder, and select Get

Info > Ownership & Permissions, and set the Group option to
read-only.
46
The local solution is also effective; however, it lends itself to smaller

office applications and to those with the ability to either script
automatic installations and updates procedures, or to access all
machines remotely. A localized library means that the projects
libraries are located on the hard drive of each individual office
computer. In order for the local solution to work effectively, the CAD
Manager(s) must ensure that:
each copy of the standard libraries is current;
the modification of a library is documented and communicated;
naming and organizational conventions remain standardized.
One of the principal advantages to localized libraries is the loading
time. Libraries housed on the network are accessed by all users
creating random periods of peak activity, potentially affecting
Library Management
performance dramatically. By having project libraries on the hard

drive the speed of the network is not a factor.
It is very important that each user is working from identical office
libraries for the following reasons:
if local libraries do not contain the same objects, and multiple
users are working on the file, users are faced with having to find
missing parts on other machines and update their library;
outdated parts become harder to phase out as they are continually
cross-pollinated amongst multiple library copies.
One way to ensure that each users copies of the libraries are current
is to use the Library Cache. The Library Cache is in essence a
combination of the pure network and local library solutions. The
Library Cache creates a copy of the loaded libraries on the local disk,
thereby ensuring the most up to date standard libraries are being
used. The primary disadvantage is the time it takes to copy large
library files to the hard drive (especially over slower networks). Once
the library is copied however, network speed is not a factor. Again,
with the advent of .PLA library access, speeds are increased simply
because the library is one large file rather than many hundreds of files
in a folder structure, comprising the same aggregate size as the .PLA.
.PLAs have made localized libraries much more viable as a solution

than in previous versions since the .PLAs cannot be edited without
extraction, and re-archiving; thereby making standards control more
attainable.
If .PLAs are not used, great care should be taken when editing and
updating objects, both from a user and CAD Manager perspective.
Documentation of library modifications on the part of the CAD
Manager becomes imperative. If the CAD Manager is a user, as is the
case in many smaller firms, we recommend to always use a copy of the

original library, backed up in a safe location, since parts may be
edited, permanently overwriting the original parts parameters.
Since each machine has a copy of each library part, any modification
to the standard library will affect all projects launched on that
machine. For example, if one user customizes a standard library part,
W Awning.WIN, for use on a particular project, and inadvertently
saves it into his localized library; the information in other projects
which use W Awning.WIN will be affected when launched on that
machine. Likewise, when the standard OSL is updated for download
by all users, changes made to that part will be gone, overwritten by
the new standard object, affecting the accuracy of the project for
which the object was modified. Depending on the types of changes
made to the object, this could have serious repercussions. To repeat,
this is not an issue with the use of .PLA libraries.
Note: It is highly recommended to always use custom names for
customized copies of standard library parts.
See also Creating and Maintaining an Office Library on page 49 for more
information on modifying libraries and objects.
ADVANTAGES AND DISADVANTAGES

Both the network library and local library approaches are valid and
useful, and can be used exclusively or in conjunction with one
another through careful management.
It is strongly suggested that when determining what solution to
implement, that all firms evaluate their network, ability to maintain
standard libraries, anticipated frequency of updates, and technical
resources, keeping in mind these main points:
Maintenance: Any changes in the library should happen in one
location on the server, modifying all instances of that particular
part in all projects.
Standardization: All users will be operating with an identical library,
allowing any user in the office to work on any project within the
office without being faced with the issue of conflicting or missing
library parts.
Security: The ability to lock the library prevents the deletion or
modification of any library parts on the network.
47
Library Management
Access & Navigation: Multiple users can easily access the standard
library, which is consistent and predictable.
Note: It is important to remember that if libraries are accessed
across the network, any network failures will prevent users from
accessing additional parts until the network services are restored.
Any objects already placed will not be affected.
While there are advantages to storing and accessing libraries over the
network, local libraries provide certain advantages, regardless of
whether the libraries are .PLAs or objects stored in an HFS, such as:
allowing the user to continue adding objects to projects during
network errors or crashes;
allowing the user to take full advantage of the calculate menu,
including customized listing;
significantly reducing library loading time.
Note: List templates are stored within the ArchiCAD Library
folder. If this library is locked, it is not possible for individual users
to customize lists.
Speed is dependent upon the number of users - the more users

attempting to access the same data, the slower the response. So, by
definition, network libraries will undoubtedly load more slowly than
local libraries being accessed by one user. Moreover, the larger the
library, the longer the loading time; and, by extension, loading
multiple libraries increases the required time.
Tip: It is our recommendation to develop a solution that
minimizes library loading time while maximizing the number of
relevant objects available to the users. One way to accomplish this
is to place the main library on the network while making other
objects available either locally or through FTP sites.
In general, the fewer number of libraries and the simpler the navigation,
the better. Production teams assembling a project should not have to sit
through many long library loads, or be forced to navigate through
multiple folders to find appropriate objects.
Tip: Another way to minimize the loading times of libraries is to
use a network/local hybrid where the Office Standard Library is
maintained on each machine, and project specific libraries are
loaded from the server. Caution must be exercised whenever
libraries are being maintained locally.
In instances where users are in and out of many files through the
course of a day, each loading different libraries, loading time should
be minimized. For those users requiring access to many parts (e.g.,
members of a visualization team) having many libraries loading is not
as much of a concern. Here speed is sacrificed for access to a wide
variety of parts. Once again, this is where the ability to sort by
Subtype has significance in determining how to organize and
maintain a library solution with an office.
See also Using FTP Libraries on page 54 for more information.
Loading Time
The CAD Manager(s) must consider the time needed to load project
libraries when designing a solution, and hardware specifications play a
key role in determining the speed at which the library will load.
Exactly what hardware should be used to maximize performance
depends on the following factors:
location of the libraries;
number of libraries and their sizes.
48
Library Management
CREATING AND MAINTAINING AN

OFFICE LIBRARY
Creating and maintaining an office library solution requires standards
and procedures, and an organizational methodology to make it
flexible and understandable.
Additive Libraries
Creating a new Office Standard Library can be a time consuming
task. It involves creating an entire folder structure that conforms to
users needs and then adding to that, objects from various sources.
Objects that are included in this library could come from third party
sources, i.e. purchased online a la carte, or as part of a package; or
could be standard ArchiCAD objects edited to suit firm specific
needs; or could be written/modeled by users in the firm.
As an organizational methodology, the OSL should maintain the
same or similar directory structure as the localized ArchiCAD Object
Library; the familiar structure makes it easier for users to locate
specific objects. For instance, the library localized for the U.S. is
structured around the Construction Specifications Institutes
framework and the OSL should follow suit. Though it may not be
necessary to have as many subdirectories as the main library, knowing
that, for instance, steel shapes are located in Division 5, Metals, makes
them easy to locate for all users.
The OSL should also contain all of the macros from previous
versions of ArchiCAD that used the version number as an identifier
(i.e. Versions 6.0, 6.5, and 7.0) as well as all of the third party libraries
macros used. Keeping the macros in the OSL prevents users from
having to deal with locating them when individual parts are pulled
from various locations (like previous projects) or from having to load
entire libraries when only a single part is needed, which will be added
to the Project Specific Library.
49
Library Management
Creating the firms library within a familiar framework also allows for
some reorganization. For instance, not all objects in the ArchiCAD
library are going to be organized in an intuitive location for use by the
firm, so commonly used parts can be adapted from the AOL and
included in the OSL in a more appropriate location. For instance, it
may be desired to modify and move Bathroom Accessories from
Division 11, Equipment to Division 10, Specialties. The additive OSL
allows a library that is structured in the way that the users think and
comprised of the objects necessary to the work of the firm. These
libraries require a bit of maintenance, but their level of familiarity and
usability is increased.
Updating Libraries
All of the textures collected or developed by the firm should also be

kept in the OSL; again, preventing users from having to locate them
when a particular object calls them.
50
In the past, each time Graphisoft would upgrade the software, a new
library would be included, whose parts would be named differently
than the previous versions library. This was done to help keep track
of which parts from which libraries were being used in a project. The
side effect to changing names was that the new librarys parts would
not replace those of the previous library already used in a project
making upgrading to the new version difficult for these projects;
leaving the alternatives as either performing a tedious library
transition or maintaining multiple software and library versions for
these projects.
With ArchiCAD 8, Graphisoft introduced a library object Global
Unique Identifier (GUID) to enable ArchiCAD to search for the
appropriate parts identified by their name and 72-character number.
This system eliminates the need to append object names with the
suffix that identifies them as being part of a particular version. It is
theoretically possible therefore, that by using the minimum three
library concept outlined herein, projects either started under this
system or converted to this system, can move forward through
version upgrades while loading the same three libraries, without
having to actually transition the libraries.
Library Management
Creating the Office Standard Library

When creating the Office Standard Library as an archived project
(.PLA Library), there are several components that need to be
maintained by the CAD Manager in order to simplify the updating
process.
First, the HFS needs to be created as discussed above, and populated
with the required content. The root folder should be given a
descriptive name that identifies it clearly, such as OSL Source.
Now that there is a project file that opens reading only the firms
standard object source library structure, it can be saved as a .PLA,
using the name by which it will be recognized by the firm, e.g., ADC
Master Library.PLA.
Next, a .PLN needs to be created that will load only OSL Source,
and ideally, the .PLN that is used would be generated by the firms
template file. Though it is not necessary (a standard ArchiCAD
template file would suffice), using the firms file provides continuity
and consistency throughout the firms standards. Like the library that
this project loads, it should be saved with a descriptive name, e.g.,
OSL Source.PLN.
51
Library Management
Note: It is important that the Include All Parts of Loaded

Libraries option not be selected.
Note: When saving the .PLA, it is necessary to save all parts in the
loaded library. This feature is accessed through Options in the
Save As dialog.
From this point on, changes to the library are made by 1) adding
objects to, or editing objects in, the OSL source folder; 2) opening the
OSL source .PLN; and, 3) saving as a .PLA, overwriting the existing
file.
Once the .PLA is saved (locally, to help speed the process), it should
be opened and a new library created (the user will be prompted to
either read them directly from the .PLA or to extract elements to a
folder; the latter should be selected).
Transitioning Libraries
In the following section, we will outline the process by which a library
transition can be successfully accomplished and in a timely manner
for projects that were begun under a previous library solution.
All projects to be transitioned will need to be saved as archive files
(.PLA) to extract all of the objects being used in a project. Typically
this is done by the project manager.
52
Library Management
The result will be an HFS that maintains the original library structure,
containing all of the parts used within that project. This library folder,
named descriptively, can then be added to the project specific library.
Though saving library parts from the previous library into each of the
active jobs libraries will consume some server space, it will ensure
that all of the projects objects will be loaded and information will be
maintained.
File/Folder Naming Conventions

When altering the OSL with either user created custom parts, or parts
from third party sources, naming and organizational conventions
must be standardized and followed within an office.
As parts are developed through the needs of a particular project, they
should be collected and evaluated as to whether they need to be
included in the OSL. Those parts that are suited for office use should
be reviewed by a committee or qualified staff member, possibly
edited, and then given a name that designates it as a standard part.
Tip: It is suggested that when custom parts are created for a

specific job, they be named beginning with the project number or
other office convention to clearly identify their origin and content.
If accepted into the office library, object names should be edited
to follow the conventions of the library while carrying an identifier
suffix to identify its origin.
Tip: Folder and GDL Object names should be 27 characters or

less allowing for the three-character extension and the dot
separator. Sharing files cross-platform and within each OS will be
unpredictable otherwise.
53
Library Management
USING FTP LIBRARIES
ON-LINE ACQUISITION
In addition to loading libraries locally or across networks, they can be

loaded from remote sites. FTP (File Transfer Protocol) sites can be
used to access individual parts or entire libraries remotely. Having
libraries located on FTP enables firms in multiple locations to access
the same libraries or to provide access to standard libraries for
telecommuters. FTPs are also extremely helpful for adding specialized
parts without having to load entire libraries. As parts are needed, they
can be accessed on an FTP site or on-line services from within the
library dialog and added directly to the project. Once the libraries
load, it is not necessary to maintain the Internet connection because
the library is cached. The loaded parts can be accessed at any time,
just as if they were on a local drive.
Third party libraries can greatly enhance the selection and quality of
office library collections. Having more parts at the disposal of the
user means that Virtual Building models can be more realistic and
require less drawing and clean up when producing the project
documents. Third party objects are available from sites such as
www.objectsonline.com, www.ddgi.com, http://cadobject.dataoffice.se/ and
www.gdltechnology.com.
Manufacturers are also beginning to produce their product lines in
GDL. Manufacturers such as Novoferm, Falco, Offecct, Plastmo,
Velux, Villeroy & Boch, Wilkhahn, Wiesner-Hager, have all or part of
their product lines available as ArchiCAD objects.
See also Sharing GDL Objects on page 88 for more information.
54
Data Safety
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 those 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,
autosaving and project archiving will be discussed.
SAVING
Manual Saving
Autosaving
Autosaving is NOT a replacement for saving; however, it can be help
in such cases as:
system crashes;
program crashes;
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 > User Preference Schemes).
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. Use the Save command as
much as possible when working on a project file. It is important to
note, however, that saving takes some time; anywhere from a few
seconds to perhaps more than a minute depending upon the size of
the project file and hardware. Saving may not be appropriate after
every modification, but is highly recommended after:
major modifications are made to the project;
tedious modeling operations are performed;
the creation of custom parts;
revisions are made to layers and combinations;
additions or alterations of stories;
the creation of custom line types, fills, composites, materials.
Manually saving updates the project file typically located within a
project folder on the network server.
See also Tailoring ArchiCAD on page 15 for details on project
directories/folders.
Note: After a manual Save, you can no longer cancel recent
changes with Edit > Undo.
ArchiCAD allows the user to autosave either by the interval-based
method (time in seconds) or by the action-based method (steps).
55
Data Safety
Tip: It is our recommendation that autosave always be turned on

and that it functions on the action-based method set to the last 20
- 30 steps in any particular project file. Timed autosaves can often
be distracting and disruptive, as the file will be saved at the
specified time interval regardless of progress.
ArchiCAD places the autosaved document into the ArchiCAD
Temporary Folder. The volume of this temporary folder can be
determined within the Data Safety dialog box. Be sure to have
enough free space in the selected volume.
Tip: 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.
File Backups
File backups can be created via the Options > Work Environment
> User Preference Schemes > Data Safety dialog box within
ArchiCAD, and in the Options > Work Environment > User
Profile Scheme > Temporary Folder and Backup Options dialog
in PlotMaker. If the Make Backup Copy option is checked,
ArchiCAD will make a file with a .BPN extension; PlotMaker a .BBK.
These files will be updated upon each manual save and will contain
the previously saved version of the project.
It is also important to understand the limitations of the autosave

feature as compared to the manual save. You should be aware that the
autosaved document might be older then the last saved plan file.
56
Data Safety
ARCHIVING
Archiving Data in the Office
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:
the close of project phases;
Authority, Cost Plan, Permit, Bid or Tender Sets, i.e. where it is
necessary to have digital backup of legal documents;
significant design changes;
predetermined calendar intervals;
Archived files can be stored on specific server partitions, CD or other
removable disk media, tapes, or even FTP sites.
About the ArchiCAD Archive File (.PLA)

Tip: 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 days work and thereby allowing
the previous days 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
needed 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 projects changes and offer a means to retrace steps.
The Teamwork function of ArchiCAD contains yet another set of
backup options.
For more information, see Practical Use of TeamWork on page 71.
See also Teamwork Guide in ArchiCAD Help.
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 .PLAs 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:
long-term phased projects;
project additions and renovations;
uncompleted or halted projects;
general archiving.
57
Data Safety
In the Archive Options dialog box, there are several check boxes
that define the contents of the .PLA, which is to be created.
58
The four check boxes generally do two things they provide

flexibility should an archive need to be revisited for future work; and
they increase file size. Obviously, the more pieces that are included
within a .PLA, the larger that file will become. In order to maximize
flexibility while minimizing file size, determinations need to be made
as to the intended future use of the archive. When these are made, the
files parameters can be defined.
Tip: If files are being archived for general backup purposes and
for record copies, it is recommended to save the archive with the
boxes checked as in the following figure:
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 firms 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.
Data Safety
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.
Tip: 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.
See also Library Management on page 41 for additional information on using
archived libraries.
Archiving PlotMaker Layout Books

Typically, all of the views/drawings within a Layout Book linked and
will continue to be updated when the book is opened, and Update
Drawings is performed. Archiving PlotMaker Layout Books
provides a way to freeze information in its current state, as either
.LBKs or .PDFs; ideal for record copies through the course of a
project. In order to create effective .LBK archives within PlotMaker,
several steps need to be taken:
Save As should be performed to not overwrite the current Layout
Book;
All drawing links need to be broken;
Layout Books should be saved to include the drawings.
Note: Saving layout books to include the drawings will increase

the storage space needed. It is recommended that once a Layout
Book has been saved for archiving, it be removed from the job
servers and stored on CD or on a read-only server partition for
future use.
If it becomes necessary to return to the archive as the active set, all of
the links can be reestablished Through Drawing Usage. It is
important that the Layout Book again be Saved-as to not include the
drawings.
59
Data Safety
Tip: Another possible solution for archiving project drawings is to

save the .LBK in .PLT format. Since PlotMaker uses HPGL/2
language, .PLTs occupy the smallest amount of disk space and can
be produced on all plotters.
Warning: Plotting renders differing output than does printing;
though small and versatile, .PLTs may not yield the desired results.
Tests should be conducted to ensure that both the displayed
information and the resultant hardcopy are correct.
See also Project Output on page 62 for additional information on printing and
plotting.
Staying Organized
If using .PDF to archive project Layout Books, it is best to create

publishing sets in the .LBK template to accommodate the typical
layout sizes and that have all of the necessary printer settings and file
attributes established to save the files properly.
60
When archiving project files, (whether they are .PLAs, .LBKs, .PDFs
or .PLNs) naming conventions need to be established and followed.
Though it is impossible to prescribe an absolute method for all
situations, the following are tips and examples of file naming during
project archiving:
Always save the ArchiCAD file to include the job number first.
At stages of major modifications, Save-as a new version of the
project with an additive suffix and file the previous version in an
archive folder within the job folder. For example, 04-123-5.PLN
means the year 2004, the 123rd job, fifth version. .PLAs would
follow similar conventions. It is recommended that the current
project file never change names; i.e. if a new version needs to be
created either for archiving purposes or other, the file to be
archived should have its name altered to identify it and the file to
remain active and linked, should maintain its designation. The
purpose for this is two-fold; first, the links to the .LBK will not be
disturbed, and second, there is never any question as to which file
has the most current information. Any one joining the project
team should know that the conventionally named file, without
modifiers, is the most current file.
Name .LBKs to carry the job number. Where 04-123.LBK means
the year 2004, the 123rd job. .PDFs would follow similar
conventions. If desired, the .LBK could carry a project name
description.
All of the required drawings that will be produced from the
ArchiCAD project file should have a view set up in ArchiCAD.
Data Safety
Though it is still possible to manipulate the scale and layers of

views from within PlotMaker, it is still not a recommended
practice.
See also Project Output on page 62 for additional information on archiving.
61
Project Output
PROJECT OUTPUT
QUALITY AND CONSISTENCY
In general, the application used to produce project documentation, is
only as good as the ease and dependability of generating printed
output. As with many computer applications printing, and in the case
of CAD, plotting, can be extremely frustrating when achieving the
desired hardcopy results involves wasted time and resources. With
standards and testing, it is possible to achieve quality and consistent
output using ArchiCAD and PlotMaker. There are several key factors
to achieving the desired output:
Output application;
Creating and using project templates in PlotMaker;
Establishing and maintaining links;
Project attributes;
Output devices and software.
OUTPUT APPLICATION
Printing from ArchiCAD
It is possible to print and/or plot directly from ArchiCAD, but due to
its limitations, this is best suited for review purposes only. This ability
to produce output quickly form ArchiCAD is extremely useful:
to share information with team members, including consultants;
to produce rough three-dimensional views to share with clients;
to view the intended quality of a particular drawing; checking items
such as pen weights, fill rendering, etc.;
to review a specific portion of a design, printing only those areas
to be studied.
Note: It is possible to produce the drawing sheets from within
ArchiCAD, but it is not recommended for constructing and
outputting an entire project set.
reason, that we strongly recommend PlotMaker to produce project
62
The reason for this recommendation is quite simple: this method is

rather limited and possibly very complex, because only drawings
created at the same scale can reside in a particular workspace created
in ArchiCAD without clumsy and inefficient work-around. Even
though the project is constructed in real world dimensions, the
displayed workspace in ArchiCAD (plan, section, or story) is always
displayed at a particular scale, and while it is possible to reuse the plan
view at multiple scales, it is not possible to show different areas
within that same plan at different scales simultaneously. It is for this
output.
Project Output
Publishing View Sets
Output from PlotMaker

For the layout and output of drawing information generated within
ArchiCAD, the best results come through the use of PlotMaker.
PlotMaker is essentially a desktop publishing application (DTP), and
a sister application to ArchiCAD. Though somewhat limited in its
simulation of ArchiCAD tools and text handling capabilities,
PlotMaker is very adept at integrating ArchiCAD information. With
the last two releases, PlotMaker has become much more refined and
powerful, and in contrast to other DTPs that can establish links to
many different file formats, PlotMaker can combine multilingual
graphic file formats, with a pre-linked multi-sheet layout book
template that reads the ArchiCAD project file directly). This unique
interface capability makes PlotMaker the preferred choice for project
output.
One of the primary features in PlotMaker, designed to aid production

and consistency, is the Project Publisher. By creating specific
publishing View Sets in PlotMaker, that are either manually created
and maintained or clones of the Layout Book, it is possible with a few
clicks to publish the book in multiple formats without having to set
them up each time.
Note: Cloning a Layout Book, or subset folder contained therein
as a means of producing a publishing set, causes that newly created
set to be automatically updated each time a change is made to the
cloned source. That is, the publishing set is a proxy, if you will, of
whatever folder was cloned, that has publishing properties
assigned to it; and will immediately reflect any changes made to the
parent set or sub-set.
It is recommended to use a clone whenever possible, as updating
and maintaining independent publishing sets can be labor
intensive and require a great deal of coordination.
For instance, by creating a Print View Set, a Plot View Set, a .PDF
View Set and one or more consultant View Sets, etc., a user can print
a reduced size set to a laser jet or full color set to the inkjet plotter,
plot a full sized set to a laser plotter, generate a single .PDF
containing all sheets of a book, and generate all necessary
backgrounds for all consultants without having to change any device
settings, or manually update the contents of the View Set, once the
View Sets are configured. This process is not only simple and
versatile, it promotes faster more dependable output through the
control being placed on the project manager or CAD Manager at the
time of initial set up.
63
Project Output
finally, detail sheets would contain standard sized detail drawings,

(those drawings that can be formally organized to maximize sheet
usage).
Hint: Detail drawings could come from either a database of
individual .PLN or .DWG files, from the ArchiCAD project file,
or from a .PLN, or limited number of .PLNs, that consolidate all
standard details, organized through the use of the Independent
Detail tool.
The number of view sets and their desired function is a matter of

project type, project requirements, firm infrastructure, and desired
workflow. It is recommended that as much set up take place in the
.LBK template as possible, with only minor modifications being
made at the user level.
Project .LBK Templates
PlotMaker project templates create a common standardized starting
point from which to begin the placement of all drawings; in fact, all
drawings for typical sets can be linked to their sheets within the .LBK
template. Layout Book templates can be designed to contain all of the
sheet types that a practice uses to accommodate an architectural
project. Fundamentally, drawing sheets consist of:
title/cover or general information sheets;
standard drawing sheets;
detail sheets. A title/cover sheet might contain information such
as the project name, date, architects name, consultants
information, project rendering, code information, and a sheet
index, etc.; a standard sheet would contain architectural drawings
such as plans, elevations, and sections, (those drawings whose sizes
are not standard or whose placement is not formally defined); and
64
Project Output
In addition to the different sheet types

being part of the template, each sheet type
can also have varying designs and sizes to
accommodate any project or phase. Like the
sheet types, varying sizes and designs are all
accomplished by producing multiple master
layouts in the .LBK. As described in the
PlotMaker reference guide, any layout in a
book which needs to be changed, can be
reformatted simply by dragging a different
master layout onto the sheet, subset or set.
Tip: Using an industry standard or
guideline helps in determining which
sheets will contain what information,
where that information might be located
on the sheet, how the sheets will be
numbered as well as organized in the set.
In the U.S., for instance, the Unified
Drawing System (UDS) is an excellent
source for such information; it assists in
providing consistency and flexibility,
creating a basis for uniform logical decision making when
developing standards and procedures.
same two standard sheet sizes; and potentially a Supplemental

Drawing sketch layout on standard printer sized sheets (A4/Letter,
A3/Tabloid). Detail sheets and set Cover sheet could potentially also
have their own Masters, depending upon philosophy and graphic
intent.
Multiple Masters create versatility through
the course of a project helping to reduce the
number of files created and the number of
links established, thereby reducing the
chances for errors.
Master layouts will contain all of the
formatting, and general project and sheet
information. They can be applied to any
individual layout, subset, set, or the Book at
anytime, instantly changing the sheets to
which the master was applied.
Note: When re-applying Masters to
layouts originally set up with a different
sheet size, it will be necessary to
reposition placed information
accordingly.
Tip: It is recommended that only
information necessary to the layout itself
be added using PlotMaker and that all
textual information used on a sheet be
inserted as AutoText when and wherever
possible; and that PlotMaker be used
mainly as a paste up board where most information is created by
another application (ArchiCAD, or other as needed).
Master Layouts
In order to make the .LBK template as effective as possible, it is
necessary to create multiple Masters to manage output on various
sheet sizes, and/or with different graphics/title blocks. Examples of
different Masters might include a Design Development layout on two
standard sheet sizes and a Construction Document layout on the
65
Project Output
View Links and Subsets
As a starting point, one could create multiple templates for sheet sizes
and designs, but by having a file that can be manipulated throughout
the process, the number of templates to create and maintain is
minimized, inherently simplifying processes. If separate templates
need to be maintained, there are more opportunities for there being
discrepancies from template to template, increasing the chance for
errors in the project data and project consistency.
Note: It is always beneficial to limit the number of files that are
needed to produce the majority of the firms projects.
Sometimes breaking items into smaller parts cannot be avoided.
Project types within a firm may demand simplicity over maintenance,
or different company divisions may have diverse needs and
expectations. The basic goal, however is to design elegant templates
systems to achieve:
a balance in the degree of organization;
maximum flexibility;
limit the amount of maintenance.
See also View Links and Subsets on page 66 and the Data Safety on
page 55 for additional information.
66
The goal in setting up a PlotMaker Layout Book template should be

to pre-link every typical view/drawing used in the majority of firm
projects to its proper sheet(s); or to put it another way, the fewer
views/drawings that need to be added to projects on a regular basis,
the more successful the template is.
Note: Using a subtractive methodology at the user level for
removing superfluous views is much easier and more reliable then
an additive one which does not require the setup or the attention
to detail otherwise needed; so it is therefore recommended that the
Layout Book be as complete as possible for all project types.
In order to have an .LBK pre-linked with all of the necessary views,
those views must first be created and named in the ArchiCAD .PLN
and imported into the .LBK and placed appropriately. Before they
can be placed however, they need a place to go, i.e. a sheets to be
placed on.
See the Views and View Sets on page 24 for more information.
As learned from the discussion on Masters above and elsewhere in
this manual, the simpler and more flexible a system is, the better. The
same is true here in terms of the number and types of Subsets
created.
Tip: Creating one project set (the Layout Book itself) for use
throughout the process will minimize file maintenance and help to
ensure reliability of the output information.
The simplest and most effective approach to setting up the Layout
Book template is to have one set that will track through the process
(whether or not it gets made-over to appear differently), broken down
into Subsets, taking advantage of auto-sheet numbering and making
the maintenance and ordering of layouts easier and more reliable.
Project Output
The creation of Layouts within the template should again take into
account all typical firm projects, and be as complete as necessary,
broken down as required.
Note: While creating views in ArchiCAD can be complex and
requires a rather high attention to detail; adding Layouts in
PlotMaker is a bit simpler and can be accomplished rather easily at
the user level, especially with Subset numbering and when a copy
of an existing layout is used as a source.
With the subsets in place, layouts can be added and named, while
numbering happens automatically (See the PlotMaker Guide for more
information regarding Subset numbering).
67
Project Output
still creates .PMKs in the background, storing them in an application

preference folder on the work station hard drive. Because these files
are stored locally, the .LBK will not have access to them if opened on
another work station, forcing each user to re-link the .LBK to all files
included therein, so that PlotMaker can create the. PMKs on that
particular work station. It is therefore necessary to change the default
settings of the .LBK if multiple users will be accessing the .LBK.
On the Options menu, under Preferences > Cache Folder, there is
the option to include the Cache in the Layout Book or into a folder.
Selecting the option to include it in the book, ensures all users will
able to open the book with all views/drawings in tact.
With the layouts created, it is almost time to import the views. Before
this is done, however, there are a few last things to be checked to
ensure optimal performance.
Even though PlotMaker reads the .PLN views directly (there are no
interim steps to creating the drawing for inclusion on the layouts), it
68
Note: As with all other options, there is an effect for selecting it:
saving the Cache in the book increases file size significantly. This
fact should be considered where storage space is an issue.
Another Preference, under Miscellaneous which should be
considered before completing the template, is whether or not newly
placed drawings should automatically be appended with a particular
Title Type, and whether or not a drawing should have its frame
cropped to display the zoomed area as in ArchiCAD.
Tip: Since these are global settings in the Book, it maybe difficult
to determine their advantages at the time of the template creation;
so, it may be necessary to evaluate their usefulness in a project
setting and revisit their inclusion in the template.
Project Output
another .PLN that has the first set of pens rendered in gray:
PROJECT ATTRIBUTES
Utilizing Pen Sets in PlotMaker
Pens and colors are used and treated differently in PlotMaker than in
ArchiCAD. ArchiCAD uses pens colors to distinguish their weight to
the user. Obviously if all pens in ArchiCAD were black (as is the
intended output the majority of the time), it would be extremely
difficult to model and draw effectively. Similarly, if the weighted
(colored) pens could only be plotted with their corresponding
grayscale value, many drawings would not be as clear as desired nor
have the flexibility in conveying different types of information. At a
very basic level, ArchiCAD requires the color to be effective; and
PlotMaker the weight. With that being the case, it is necessary to be
able to assign pens in PlotMaker easily and without disturbing any
other settings or attributes.
In order to toggle the first sets pens from color to black or gray, as
described earlier in Tailoring ArchiCAD on page 15, two dummy.
PLN files need to be created, containing the black and gray pen
options, in lieu of color. Essentially what we have, is a template(s) file
where the model is made, that has the first set of pens in color;
and another .PLN that has the first set of pens rendered in black:
Note: In the model file, it may be difficult to distinguish line

weights of pens 11-20 (those that will always plot black), so their
colors are set in ArchiCAD at a very dark value of their original
color, making it possible to visualize line weight while
understanding them as black. These pens will later be converted to
true black in PlotMaker.
69
Project Output
For ease of conversion and the retention of information, the second

set of pens is accomplished by adjusting pens 1-10 from their normal
color to a value of gray that plots and reproduces well, and pens
11-20 are adjusted from their normal color to black. The third set has
pens 1-10 adjusted from their normal color to black and pens 11-20
are again adjusted from their normal color to black. Views are created
in each of these .PLNs, which will be pre-linked to the .LBK and the
.PLNs included in the projects directory.
Note: These views should remain linked for the life of the project.
If, by way of the system setup, these views do not link, they should
be re-linked to the .PLNs in the projects directory, and saved
immediately.
Ideally, all of the views necessary for a typical project will be
pre-linked, and will have their pens pre-set. If, for example, a new
view is created in ArchiCAD and imported into the .LBK, it will be
necessary to define its pens per the standards.
Pens are assigned to individual views or drawings by
Alt/Option-Clicking a node of the source file and
Control-Alt/Command-Option-Clicking on a node of the target
view/drawing.
Note: PlotMaker limits access to this ability (along with the ability
to manipulate scale and layers) at the .LBK level through the
70
Options > Preferences > Drawing Attributes dialog, and at the

individual drawing level through Edit > Drawing Settings.
Unchecking the Pens and Colors box allows the user to control
the settings.
for more information on producing sheet content.
OUTPUT DEVICES AND SOFTWARE

Up to this point, our discussion has primarily been about setting up
templates and manipulating settings within the software. However,
that still doesnt get the product out the door; for the most part now,
we are dependent upon hard copy.
As simple practical advice on how to get your output devices to
produce exactly what it is you created, the only thing we can say
without this becoming a book about printing, is test and TEST! Test
as many different scenarios as possible, always being sure to
document all settings and specific instances when things do not come
out as planned. Once the optimum settings are discovered, most of
what you desire can be accomplished, though there will always be
exceptions. There are simply too many issues surrounding printer
models, drivers, file extension conflicts, file sizes, and spooling
software, to say definitively say how to do it. What can be said
regarding output is this:
ArchiCAD and PlotMaker should control pen settings;
Graphic file formats are best printed.
Note: Ink jet plotters are in fact large format printers, and typically
are set up to take pen descriptions from the application.
The terms printing and plotting here refer to the drivers that
process drawing data.
Generally speaking, printing is far more flexible and versatile within
the architectural office environment. It will also provide more
consistent results and flexibility regarding various paper sizes. The
down side is the increased time that it takes to print versus plot. The
difference can be significant especially when dealing with complex
vectorial hatching and bitmap patterns. If all systems are not in line
and functioning properly, much time can be lost during the project
output portion of the design services.
Practical Use of TeamWork
PRACTICAL USE OF TEAMWORK

The ability for multiple users to work simultaneously on a single
project file is a powerful feature of ArchiCAD. To establish a
successful TeamWork project, the initial sharing setup and the
ongoing management of a TeamWork project are critical. In this
section we will discuss strategies for practical application and
management of TeamWork files.
SETTING UP TEAMWORK PROJECTS

By definition, teamwork suggests that a group of people are working
together to complete a particular task; though this is a main use of
TeamWork in ArchiCAD, a single user can also effectively take
advantage of its features. Below, we have outlined some specific uses
and methods for the both single user and team.
Regardless of how they are to be used, TeamWork projects should be
set up according to office established standards to allow flexibility
and consistency. Certain steps should be taken and criteria met to
avoid user confusion, data loss, and breaks in productivity.
Sharing the Project

After selecting Teamwork > Share This Project, the first step is to
set key passwords for the Administrator and Team Leader.
For the definition and privileges of the Administrator and Team Leader, please
refer to the Teamwork Guide in ArchiCAD Help.
Set the Administrator Name to administrator; and set both the
Administrator and Team Leader passwords to be the office project
number or precise project name or other agreeable office convention,
(for example, 01-123, where 01 is the year=2001, and 123 is the 123rd
project of the year).
Tip: When setting user names and passwords to be accessed by

many, always use lowercase characters. Though user names are
typically not case sensitive, passwords are; using lowercase
characters, always, minimizes the risk of incorrect entry or
forgotten specifics.
Though the generic setup may appear to be a disadvantage, extensive
use of TeamWork has shown us that unless project information is
highly sensitive or requires strict security, the simplification of access
privileges substantially increases the efficiency of the TeamWork
processes. In particular, ease of access aids the project when it is
necessary for team members to assume various roles to complete
particular tasks.
Backup Options
Due to the complexity of TeamWork projects - multiple users,
sending and receiving changes, signing in and out project backups
are very important to ensure data safety. File backups are stored and
updated according to the specifications in the Make New Backups
dialog box. Upon setup, the Administrator can define the number of
backups and the frequency at which they are updated.
Tip: It is recommended that the frequency at which backups are
made be set to After (1) Modification. This will create a new
backup each time changes are sent to the .PLP.
71
It is also recommended that the Keep Old Backups option be set

to Keep the last (1) Backups.
Though more or fewer backups can be saved according to project
size, complexity and number of users, keeping the last three is a
reasonable compromise between protecting project data and
minimizing file storage requirements. Each backup is in itself a copy
of the entire project and having many copies can consume server
space, especially with large projects. However many backups are
determined to be necessary, it is a good idea to always set it the same
for consistency.
STRATEGIES FOR USING TEAMWORK

Team Application
In the following section, we will provide a framework of basic
teamwork issues and application processes. It is in the true team
environment that we have been exposed to the challenges and
benefits of TeamWork. TeamWork can be broken down into several
main areas. They are:
Team Selection/Management Issues
Project Workspace
TeamWork Project Information
File Sizes/Types
TeamWork Web Sharing
72
Team Selection/Management Issues

When performing the setup for a project to be shared, one of the
options is to allow Open Access or Registered Members Only.
Though allowing only registered members provides some control

over those working within the project, it requires additional
administrative work. If, for instance, a firm associate is asked to
become involved in a project temporarily, it is necessary for the
administrator to sign into the project and add the new team member.
With open access, the new team member could sign in and be added
automatically.
To establish a specified list of users select Registered Members
Only and then click the Add New Member button to add the first
team member to the list. Repeat as necessary until the entire project
team, including the administrator, have been added to the list.
Should a person who is not a part of the project team attempt to sign
into the project, they will be asked to contact the project
administrator, at which time the administrator can either add the new
member or not.
Project Workspace
When signing into a TeamWork project, it is necessary for a team
member to define a project workspace. Keep in mind when selecting
a workspace, that there are many different ways in which the project
could be shared. User preference, building type, managerial direction,
and/or any combination help to determine the most appropriate way
to share any particular project at any given time. Virtual Building
model workspaces can be defined using three basic methods:
Stories Method
Sectional Method
Systems Method
The Stories Method (selection by floor) allows the user complete
access to all components on the entire story of a Virtual Building
model.
This method can useful for a multistory project where each signed in
member works on a particular floor, or for a project where the site is
on a discrete story from the building, allowing the site to be
developed by one member while the building is developed by others.
The second manner by which project workspace can be defined is the
Sectional Method (selection by marqueed area). The Sectional
Method allows the user to isolate a particular section of a building
either on a particular story or across all stories as defined by the
marquee settings.
73
This method is extremely useful in complex building types and

campus projects. Take for example a complex building such a
hospital. Due to the diversity of functions within a hospital, it may be
necessary for team members with specific knowledge be assigned to
work on specialized areas of the hospital. Using the Sectional
Method, a team member could develop a specific portion of the
building, for instance, a cancer research wing, while another team
member is working on the outpatient surgery portion of the building.
In a school campus situation where there are several building types
such as a cafeteria, gymnasium, and classroom buildings, the Sectional
Method could allow each project team member to be responsible for
a particular building in its entirety.
Note: Having an entire campus contained within a single
TeamWork file requires proper hardware, memory allocation and
project management, and is only one possible solution for such a
project.
The third method of workspace definition is the Systems Method
(selection by layers). The Systems Method allows the user to isolate
certain building systems. In this case, the user would be able to edit
ONLY those elements placed on the selected drawing layers.
This method is particularly useful for firms that divide work into
production tasks such as ceiling or roof development, or mechanical
systems coordination, as well as in large firms where in-house
engineers may work within the .PLP. If a team member were
responsible for the mechanical systems coordination of a building for
example, only layers corresponding to those systems such as
M-DIFF-SUPP, E-LITE-INTR, P-FIXT, etc. would be selected.
Tip: These systems sign-ins could in fact be the team members
names, allowing anyone to sign in quickly to perform a particular
task without having to redefine the layer selections based on their
actual team member name.
For more information on project sharing methods please refer to the Teamwork
Guide in ArchiCAD Help.
Note: When sharing a sophisticated or complicated Virtual
Building model, it may be necessary for the project manager to be
solely responsible for setting up project work spaces before any
team member signs in. This management role helps to ensure
proper team coordination and efficient production time.
Single User Application

The single user application requires the same setup procedures as
outlined above, but unlike a team application, the single user will
typically sign in as the Team Leader with exclusive access, and will be
74
the only person sending changes to the .PLP. Though the single user
can benefit from TeamWork functions such as multiple project
backups and project notes taken within the file, the primary
advantage is that multiple design options can be explored easily
within the project.
To accomplish this the user should save a .PLC to the desktop or to
the project folder/directory on the network. The .PLC can then be
repeatedly duplicated and renamed to express content or intent.
The two major advantages to having multiple .PLCs are that the
designer can work on several design schemes concurrently, and that
any changes to the associated .PLCs can be sent to overwrite any
subsequent changes to the .PLP. Simply opening the appropriate
.PLC, and sending its changes allows users to revert to previous
iterations of a design. All PLCs are linked to, and tracked by, the .PLP.
Any .PLCs changes can be sent to overwrite the present information,
at any time.
Sign In/Out; Send & Receive Changes

Signing in, and signing out as well as sending and receiving changes
can be a challenging aspect in using TeamWork. To successfully
establish a system for these, it is important to understand the
variables involved, including the speed and reliability of the network,
size of the TeamWork project, and the number of team members
accessing the project.
Communication among team members is absolutely critical to the
success of a TeamWork file. Through careful project management,
scheduled signing in and signing out as well as intervals for sending
and receiving changes should be set up. Project managers should also
plan ahead and find creative ways to share the Virtual Building .PLP
that keeps the entire team productive for the majority of the workday
in an effort to minimize changes in the workspace, which can be
extremely time consuming and often effect other team members.
See also Project Workspace on page 73 for additional information.
Team members should sign into the project in a systematic manner
with only one member at a time attempting to access the .PLP.
Note: Though users trying to access the .PLP are queued by
ArchiCAD, it is safer and more reliable if team members
communicate and perform their operations one at a time helping
to avoid file corruption or network crashes.
Sending and receiving changes can significantly tax a network, it is
helpful to minimize the number of times that this is performed, while
still saving all modifications made to the model. The most effective
way to save work and minimize network traffic is to sign into a
TeamWork project, and immediately save a draft copy of the file
(.PLC) into a temporary folder on your local hard drive or into a user
folder within the project folder/directory.
Note: Saving the .PLC to a network folder increases storage
requirements, as every signed in team member will have their own
.PLC; it also increases the file save time since it is not being written
locally.
Selecting File > Save from within a TeamWork project will, by
default, reveal the Save-As dialog box, offering to save a draft copy,
automatically assigning a .PLC extension to the file. Once you have
completed this step it is important to remember that:
75
you are now working within the draft, and all saves will update the
draft;
you are still signed into the teamwork project file;
you will lose all changes if you sign out without sending changes;
you can send and receive changes at any time and continue
working on the same .PLC.
Tip: We highly recommend that work should be done with PLCs,
instead of directly on the PLP.
Depending on the size of the project and the number of team
members involved in sending and receiving changes, schedules or
time intervals vary and should be determined on a project by project
basis. An affective method for completing the process is for one team
member to initiate the sending and receiving process and, upon
completion, notify the next team member on the schedule and so on
throughout the entire project team.
Tip: It is recommended that team members perform Send
&Receive Changes upon completion of their tasks as well as at
the end of the day. Signing Out at the end of a day should be at the
discretion of the project or teamwork manager, though it should
be minimized!
See also Teamwork Guide in ArchiCAD Help for additional information on
sending and receiving changes, signing in and signing out and changing
workspaces.
Once changes are sent and the team member signed out, the .PLC
should be deleted from its temporary location.
TeamWork Project Information

TeamWork maintains a database of all project activity and any signed
in team member has access to this information from within
Teamwork > Project Sharing Info. Information within this
database can identify team members currently signed into the project,
their defined workspace, their sending and receiving activity and
when they signed in and out.
76
In addition, we strongly recommend the use of Add Comments in

the Teamwork menu.
This feature allows users to make notes about the project or create
accurate and concise documentation of session tasks that can be
shared amongst team members through Teamwork > Teamwork
Notes. Written notes can also be incorporated in the Send &
Receive Changes dialog box.
In addition to the written staff notes, the corresponding .txt file
provides information such as: who has signed in or out of the .PLP;
who has saved hotlinks; the dates and times for these. Because this
information is written as a .txt file, it can be opened from outside the
ArchiCAD environment. This may be particularly useful for job
progress information, client billings, overall project tracking, and for
addressing staffing requirements.
Extending ArchiCAD
EXTENDING ARCHICAD
Add-Ons are independent chunks of software that increase the
functionality of ArchiCAD. There are several advantages to using an
Add-on approach:
Users may develop a custom application of their own or through a
third party software developer, though it should be noted that
custom development by the end users should not be a first choice
as it requires knowledge of C programming;
Product manufacturers and specialist organizations can distribute
tailored applications;
Updates are easily implemented and distributed.
There are several Add-ons, currently being used by ArchiCAD, to
accomplish tasks from making stairs and roof framing, to making
ductwork and crown molding. The role of the CAD Manager with
respect to Add-ons is to determine which are appropriate for the
office, i.e. what role they will play and how they will be accessed in
ArchiCAD and incorporated into the interface. For example, a
commercial office may not have a need for RoofMaker, in this case
the CAD Manager may opt to remove it from the interface using a
custom Command Layout Scheme; while it may be desired or
necessary to have Profiler available and as part of the extras menu
rather than on the Tools menu.
77
Extending ArchiCAD
ADDING FUNCTIONALITY
All Add-Ons placed in the folder, ArchiCAD 9.0/Add-Ons, will
automatically be loaded and available upon launching the program.
Those items not placed in the add-on folder can be added while the
program is running via Tools > Add-On Manager.
78
Note: It is important to keep in mind that any Add-ons loaded

while working within ArchiCAD will be available upon the next
session on that particular workstation only, i.e. it is a locally
referenced setting, not project based. This is an important point
when working in TeamWork. If it is desired to have certain
functionality available throughout the office, it is advised that the
CAD Manager make the necessary changes to his configuration
copy, and make the settings or attributes available globally using
the network location of a Profile or Scheme.
Sharing the Content of the Virtual Building
SHARING THE CONTENT OF THE VIRTUAL BUILDING

In the following section we will discuss what information contained
within the Virtual Building can be effectively shared, and how to
accomplish information sharing efficiently amongst project team
members.
ArchiCAD has a number of sharing options, each providing a highly
effective environment for a number of internal and external project
collaboration tasks such as:
Sharing of the working database (for design and editing) using
TeamWork;
Managing the production of output (drawings, animations etc. for
the project team (managed through Publisher);
Sharing the model with building service disciplines;
Sharing the object model, using IFC exchange protocol.
What to Share
With View Editor and Publisher, View Sets can be designed,
created, and edited to keep all project team members informed and
contributing. All information that can be set up in a view, generated
from the Project Map, can be published; including:
stories;
sections;
3D pictures and movies;
element, component and zone lists.
SHARING INFORMATION
How to Share
This section focuses on an umbrella of features, which encompasses
three core information exchange processes: Publisher, Project
Reviewer, and Project Mark-Up. Also discussed in this section will
be IFC, an international object based model exchange format
developed by the International Alliance for Interoperability.
Whatever the purpose for exporting information, the types of files
generated and their destinations can be managed through the
Publisher.
Publisher takes advantage of the Navigator (setting Layers, Scale,
Display Options, and Cropping), and applies it to an automated Save
As function allowing the defined Navigator view settings to be saved
to a variety of locations and in a variety of formats.
When sets are published, they can be saved locally, uploaded to FTP
sites or sent to local output devices. All this can be done from the
Publisher dialog box and predefined within the template file.
79
Using Shared Information within ArchiCAD

The two tools alongside Publisher that make up the project
exchange functions in ArchiCAD are:
Project Reviewer
Project Mark-Up
Project Reviewer is a simple application, that along with a .DWF
(ArchiCADs default file exchange format) generated through
Publisher, allows basic red-lining features through e-mail interface.
A large advantage to Project Reviewer is that it is not necessary to
have ArchiCAD installed on a machine in order to use it. This is ideal
for getting feed back from clients, management, or from remote team
members. The option to include the web environment necessary to
use Reviewer is selected in the view sets Publishing Properties
dialog.
80
The .DWF can be marked, sent back, and incorporated into the
project as required.
With ArchiCAD installed on the machine, Project Mark-Up can be
used to collaborate more effectively, whether within an office
environment or across the Web. Mark-Up is an API that loads with
ArchiCAD and it enables three-dimensional modifications to the
Virtual Building. Elements are modeled in a red pen by default,
allowing clear identification of changes.
Hotlinked Modules
Hotlinked Modules are a powerful way to share information within
the context of a project. Some specific uses for hotlinked modules
include:
creating repeated elements within a building;
linking entire buildings to a site;
creating toolkits or modeling helpers for use in projects;
linking consultant drawings information.
Note: Modules can also be produced by Publisher as a specified
file type making it much easier and efficient to update all other
files referencing the same information.
Using Shared Information Outside of ArchiCAD

Though there are many drawing formats used, and capable of being
produced by ArchiCAD, the conversions to .DXF and .DWG are the
most common; the former is a drawing exchange format that retains
three-dimensional characteristics and can be opened by many
packages; the latter, is native AutoCAD format. Almost unavoidably,
there are issues that occur whenever a conversion is made from one
applications language to another; however, there are actions that can
be taken to make the exchange easier.
81
Setting Up
Many of the settings and attributes that are adjusted for saving a
.DWG file to a specified person or firm, such as layers, display
options, destination, etc., are tracked by either including the attributes
in the view definition, or through Publishing options used by
Publisher. The ability to map the configuration on a view by view
basis eliminates the need to reconfigure each update.
Making It Look Right

When exchanging information between applications, some drawing
information that ArchiCAD handles naturally, like composite walls,
decomposes, thus making the new file unmanageable, difficult to edit
and unnecessarily large when exported. There are two very simple
things that will aid and speed the sharing of files. Both have to do
with Display Options:
Line weight display should be set to hairlines;
Composite walls should be set to not display fills.
82
Note: Depending upon the drawing recipient, it may be necessary,

or desired, to turn off the fills, yet leave the composites skins
visible (Empty vs. No Fills). E.g. Mechanical, Electrical and
Plumbing Engineers often need only see the walls as reference;
while Structural Engineers require knowing where the structural
component of the wall is in relation to the finish system or
cladding.
Setting line weight display to hairlines will eliminate the need for
consultants to edit down the poly lines created to give the line
thickness, and it will reduce file size. Turning the composite walls
display to Empty or No Fills will give your consultants lines
without the composites broken fills representing materials. Broken
fills not only increase file size, they are extremely difficult to edit due
to their quantity, physical location and base element size.
Note: The quantity of fills created in the conversion from a
three-dimensional composite to two-dimensional elements,
depends upon the quantity of materials represented in the
composite and the way in which walls are broken at the
intersection with other elements. If columns are embedded in
walls of a complex composite, they will add a significant number
of fills needed around the column when the walls are converted to
lines and fills.
As with the fills of a composite, actual two-dimensional drawing fills
must also be addressed in a conversion. Though there is no All Fills
to Empty display option, it is possible to edit fill handling in exported
files through the .DXF-.DWG Translator Setup. Exporting fills as
Solid makes them much easier to manage and edit. Though one
could choose not to export fills at all by simply turning off specific
layers; fills often represent critical information, and their extents need
to be known. Translator set up is covered in more detail below.
EXCHANGING FILES BETWEEN

AUTOCAD AND ARCHICAD
Since file sharing is a necessity, ArchiCAD makes it possible to create
configuration files, which filter attributes of file data during a
conversion. These translators can be associated with individual views
in a view set, assigned in Publisher.
Making effective configuration files requires knowledge of consultant

methodologies, requirements and potentially:
the names of consultants layers;
what line weight each layer carries;
the assignment of information to each converted layer.
With this information, a filter can be made through which a file can
pass, making global changes and reducing the stripping or
pairing-down of shared files.
Tip: It is wise to collaborate with oft-used consultants, and

strategies on how to meet their needs. By discussing goals and
understanding specific issues, a bit of trial and error in exporting
information can result in much time saved on both sides, and will
undoubtedly yield better product.
ArchiCAD also has the ability to merge a .DWG directly into a
Virtual Building file, without the interim step of opening the .DWG
and then saving it as a .PLN
Note: The translator file is also used here to merge in properly
formatted information.
See also DXF/DWG Conversion Guide in ArchiCAD Help for additional

information.
83
Sharing AutoCAD Information Directly

Sharing project files without merging them can also be achieved by
externally referencing them. .DWGs that are X-ref ed, become
Hotlinked Modules. As with linking .MOD or .PLN files themselves,
all instances that reference the drawings are updated as the original is
modified.
Note: X-refing .DWGs directly into an ArchiCAD project as the
same effect as Hot-Linking other files in that all attributes are
incorporated into the project file and, if not carefully managed,
could result in errors. I.e. all layers, line types and fills inherent in
the linked file will become part of the project; though as x-refs are
deleted, so to can the layers coming from that .DWG. Care should
be taken to ensure the proper display and coordination of
information brought in through X-Refs.
84
The IFC Integrated Object Model
THE IFC INTEGRATED OBJECT MODEL

WHAT IS AN IFC?
IFC, in practice meaning Information for Construction, is the set
of internationally standardized object definitions for use in the
Construction Industry developed by the International Alliance for
Interoperability (IAI).
The business objective of the IAI, through its chapters established in
some 11 countries around the world (refer
http://www.iai-international.org/) is to integrate the AEC/FM industry
by specifying Industry Foundation Classes (IFC) as a universal
language to improve the communication, productivity, delivery time,
cost, and quality throughout the design, construction, operation and
maintenance life cycle.
INTER-OPERABILITY DEFINITION
The IFC concept is based on the idea of objects (or elements in
ArchiCAD terms) brought together in an integrated model
(ArchiCADs virtual building). These objects are defined to support
the whole lifecycle of facility development from inception through
design, documentation and construction, then facility management
and finally demolition and/or disposal. IFC is to Project Model
exchange (wall, door, window) what DXF is to graphic entity
exchange (line, arc, circle). IFC is available to all participants in the
Construction Industry for use globally, including use by all
construction industry software vendors. IFC offers a higher-level
common language for the sharing of intelligent objects between
disciplines across the building lifecycle.
Evolution of 2D CAD into Integrated Object Models. The advantages of the

model are not only consistency of data but extend into visualization, simulation
and automation of production.
WHY USE IFC?

In each project, the CAD Manager, with the Project Leader and the
party with whom the exchange is to be made, should review why
information needs to be shared, what is to be exchanged and how.
85
Always remember that a combination of techniques may be more

useful than sticking to one solution only. Choose what suits the
project resources, skills available and the specific task at hand.
PLANNING AN IFC EXCHANGE

The first action is to determine that your partners and their software
applications have IFC compatibility. Having confirmed this, the next
important step is to select an appropriate version that both partners
can support, and to understand the functionality offered by that
version. ArchiCADs support of the IFC protocol offers the
following IFC compatibility:
IFC Version
Scope
1.51
2.0
2x
2x Edition 2
An ArchiCAD object is able to store extensive property data.

Why would you choose IFCs instead of traditional techniques such as
2D files in DWG/DXF or DGN format?
The principal benefit of IFCs is their object description not only
does the IFC protocol preserve the full geometric description in 3D,
but it also knows its location and relationships, as well as all the
properties (or parameters) of each object such as finish, serial
number, material description, thermal conductance and cost.
For ArchiCAD users this offers great potential to access the accurate
geometry of building service systems and structural elements, i.e. to
improve the information to be coordinated in the model, rather than
relying on the incomplete functions of current 2D CAD.
86
The first release of the IFC translator. This version

supported the concept of building carcass.
Substantial extension of functionality over 1.5.1. Increased
scope for cost estimating, thermal load calculations and
HVAC design, client briefing and space layout for
architectural design. Additional concepts are provided for
special transfers
The IFC2x platform release is stable until at least
2005/2006 to allow the industry to deliver mature interface
support. Additional capabilities extending the IFC2x
platform are planned to be introduced, but the solutions
remain downward compatible, so that previous IFC2x files
can be still read by the enhanced IFC2x interfaces.
The 2x Platform was extended by new functionality for
building strucutres (steel, concrete (including precast),
timber, building services HVAC, electrical, hydraaulic,
sanitary, extension of FM and some 2D entities.
DETERMINING THE SCOPE OF A

TRANSFER
This IFC exchange task is really no different to planning a .DWG or
.DGN transfer, except now the quality and richness of object
information can radically improve the information to be shared and
indeed lead to a re-think of the processes involved in design
collaboration and estimation, for example: Who are the parties to the
transfer and what information should be transferred? Is it one way or

two way? How are versions to be managed? While it would normally
be preferable to use the latest IFC release, it may be that the one
partner has a limited choice only.
Once these preliminary decisions have been made, consideration
needs to be given to specifying the detailed content of the exchange.
See IFC 2.0 Reference Guide > Appendix A: Supported IFC Entities in
ArchiCAD Help for a comparison of entities supported by all ArchiCAD IFC
add-ons.
VIEWS
IFC cover a diverse range of information within building
construction and the model does not distinguish who should be
exchanging that information or at what point in a project the
information is being exchanged.
Software applications are more usually concerned with specific
requirements and should not have to implement or use every class
that is contained within the IFC model. Therefore, subsets of the
model are defined that, when isolated from the complete IFC model,
still act as a coherent model. These subsets are called views.
Views are used to support the many different data needs of say
architect, structural engineer, HVAC engineer or cost estimator for
example. In the case of the ArchiCAD IFC Add-Ons the default
scope for export is to include everything.
Note: ArchiCAD does not support the IFC 2.0 BLIS view for
HVAC system design to Quantities/cost estimating
More selective functions are provided in the export settings of the
Add-Ons to filter the export of data from ArchiCAD.
See IFC 2.0 Reference Guide > Filter in ArchiCAD Help.
SET UP A PILOT OR TEST

Once the full scope has been agreed, test the process by doing a pilot.
This activity ensures that both parties get what they expected, so that
when crucial deadlines occur, the process can be confidently

undertaken.
IFC
View
ArchiCAD Functionality
Version
1.5.1
CAD The following entities are supported: Beam,
view
Building, Building Story, Column, Door, Floor,
Opening Element, Project, Proxy, Roof Slab,
Site, Space, Space Boundary, Wall, Window.
This entity set is comprehensive enough to
underpin a wide range of data sharing needs,
based on the structure of a building.
2.0
BLIS1 Four focused processes are supported:
view set Architectural design >> Quantities take
off/cost estimating
HVAC system design >> Quantities take off
/ cost estimating2
Architectural design >> Thermal load
calculations/HVAC system design
Client brief/space layout >> Architectural
design
See the BLIS reference below for detailed description of
the view definitions and objects included.
2xand 2x
Coordination View
Edition
Code Checking Singapore Building Plans.
2
1. BLIS is a worldwide consortium of AEC application
developers dedicated to developing IFC compliant products.
See their website http://www.blis-project.org/ for more information.
2. This view is not supported by ArchiCAD
The following guidelines may assist you and your team:
Start with very simple examples
Validate at both ends
Progressively expand data set to the full level
87
Document procedures at both ends

Report to Project leaders in all disciplines so that they understand
and agree to the process, resources and timetables
Note: Remember that sharing information is both a technical task
and a management process.
USEFUL LINKS FOR USING THE IFC

EXCHANGE PROTOCOL
To check current versions of Graphisoft translators refer to
http://www.graphisoft.com/ifc/
To understand more about the International Alliance for
Interoperability (IAI), the worldwide chapters and the IFC
development process see http://www.iai-international.org
To understand more about the BLIS project and definition of IFC
2.0 BLIS views see http://www.blis-project.org/
To find out the current availability of IFC compliant applications,
IFC development tools and forthcoming products see
http://www.bauwesen.fh-muenchen.de/iai/ImplementationOverview.htm
To get information about IFC software development and the IAIs
Implementation Support Group (ISG) see
http://www.bauwesen.fh-muenchen.de/iai/iai_isg/
88
SHARING GDL OBJECTS

Publishing Objects Online
A further option for an organization to publish object information
across offices, between project teams (inter/intra office) or between
business partners is to use Graphisofts Object tools - Object
Publisher and Web Plug-in. These tools permit you to easily
communicate technical data internally or externally.
Embedded GDL Objects

With the plug-in installed, it is possible to work with a GDL object
directly within a Web page or by using ArchiCADs Library
Manager tool. The objects can be product data, customized for a
particular project, a specific project set (in-house or outsourced) or
used to manage an organizations master or project libraries.
The objects can of course be any content permitted by GDL there
are no restrictions therefore on the content; consequently it is
possible to establish a details library, a contractors site products, a
fit-out companys project specific furniture catalogue, etc.
Download Compatibility on Other Platforms

From the plug-in it is possible to download the GDL Object to your
local object library for use in ArchiCAD, SalesCAD or any other
GDL compatible CAD solution (like AutoDesks AutoCAD with
GDL adapter installed). You may also turn to your ArchiCAD based
consultant for use of GDL Objects. It is also possible to save the
GDL object in other static formats like DXF, DWG, DGN, IFC or
3DS. These export functions are located in the Web Plug-ins folder
and can be exchanged, and new export functions can be added when
new versions arrive.
The possibilities this method offers are unlimited with interactive web
based product sheets, product catalogues, price lists, price offers,
door and window schedules. Additionally e-commerce and other
e-business systems are supported, including support for construction
phase processes.
The Project Cartoon Set and the Layout Book Template
THE PROJECT CARTOON SET AND THE LAYOUT BOOK

TEMPLATE
WHAT IS THE CARTOON SET?
HOW TO BEGIN
The Cartoon Set is the entire set of drawing created and linked to the
model, and all other supporting information, at a preliminary stage in
the project and used to provide continual feedback on project
progress, drawing set content and set format/organization. The point
at which the set is created varies slightly, from firm to firm and
project to project, but should be produced as early as possible for
maximum benefit.
Note: It is our recommendation that the set be produced once the
building or project extents are known (the footprint and overall
heights are well established) in order to have a better
understanding of how the sheets content will layout.
It is not necessary to be working exclusively in ArchiCAD at the time
of Cartoon Set creation; for general purposes, it is sufficient to rough
out project massing and extents, (though the sooner specifics can be
entered into ArchiCAD, the sooner the actual drawing set will take
shape).
See also Switching to ArchiCAD on page 10 on when to use ArchiCAD in a
project.
Before ArchiCAD 8, and the advent of the Layout Book, it was

typically necessary to take a best guess at what would be needed and
where it would go, and rough out each sheet accordingly. Now,
however, it is possible, and recommended, to setup a Layout Book
template with all typically required views, pre-linked to the ArchiCAD
.TPL (the starting point for all projects). Though the necessary
drawings and number of sheets could, and more than likely will
change as the project develops, with careful consideration, these
changes are liable to be relatively minor and easily accomplished. The
Layout Book template now supplants the cartoon set as it was
previously known
Note: Firm Layout Book templates should be produced to
accommodate the highest percentage of projects that fall into the
typical range, simply because it is much easier, and more efficient
for the user to subtract from a larger more complete template that
to have to add to a smaller, less thorough template.
89
The .LBK template should contain all sheets typical to the firms
projects, organized in subsets as required or necessary to address
firm, jurisdictional and client needs. Each Layout in the template
should be populated with the views set up in the ArchiCAD .TPL. All
other content, such as text files or standard graphics, should also be
placed.
By populating the .LBK template with the views created in the .TPL,
and using these as the basis for all project work; the copies made for a
job and placed in the job directory, essentially have placeholders for
the views. I.e. all content is emptied by changing the project paths.
These placeholders can then be remapped to read the appropriate
project file through the drawing usage dialog.
The pre-linked Layout Book takes full advantage of the

interconnectedness of ArchiCAD and PlotMaker. For the firm then,
to in turn get the most out the features, it is suggested to have
standards and/or conventions for sheet numbering and view naming.
90
selected. It is for this reason of simplified linking, which makes the

standardized naming of views critical.
PRODUCING SHEET CONTENT

With the building massing in place, the .LBK can be linked to the
.PLN, and views updated to begin formatting refinement. It is
important to remember that even though the Layout Book and
project templates were linked to construct the infrastructure; the
content will not be formatted on the project layouts due to unique
project parameters. The bulk of the work is done however, and in an
automated fashion; significantly reducing the time necessary to create
a project drawing set. Once the views are linked to the proper .PLN it
is only a matter of sizing windows and positioning them on the
layouts.
Note: Before linking the project .PLN to the project .LBK, it
should be customized in order to meet the projects specific
requirements.
Tip: When establishing the links between the Layout Book and its
content, all of the views produced within one .PLN can be linked
at the same time though Link To in Drawing Usage. If the Link
To button is not available, multiple content sources have been
Another significant advantage to the pre-linked Layout Book, is the

ability to assign custom attributes as the default. For instance, if
attributes are typically modified in PlotMaker to achieve desired
results, these settings can be included in the templates placeholders
and will automatically be enabled when the project files are linked.
E.g. if a view (or views) is imported into the .LBK template and the
pen attributes are modified or redefined for specialized output, the
settings become resident in that view instance, regardless of the view
that actually gets linked to that place holder, eliminating the need to
reassign the pens in every .LBK created using the template. Anyone
who has had to reassign pens to every drawing in a set knows the time
savings inherent in this solution, not to mention the consistency
achieved.
Of course, every project is different, and each will have its own special
requirements: some will need additional views created in ArchiCAD
and need to be imported into PlotMaker; some will need additional
sheets to accommodate the physical size of the project or the need
for specialized drawings; and still others may simply need to have
91
content shuffled to produce more attractive and informative sheets.

And though every project will need to have some individualization, it
is easily and efficiently accomplished when the .LBK template is
thoughtfully constructed and standards are in place.
Note: The use of subsets in PlotMaker and views in ArchiCAD
that are named and numbered according to established standards
or guidelines, makes adding deleting and editing content a smooth
process and it is advised to use features such as Autotext and Title
Types to eliminate steps in the production process.
when the same sheets and views are used throughout the design and
documentation process.
Note: Due to the quantity of views produced in the Virtual
Building that are linked to PlotMaker, it is recommended to avoid
creating separate view sets in ArchiCAD and separate layout sets
in PlotMaker for each project phase. Though it has some
advantages and is not uncommon, the transition from phase to
phase becomes much more laborious and increases the size of the
Layout Book significantly.
As previously discussed in Project Output on page 62, it is possible to

create multiple layout sizes and designs in a Layout Book, making it
simple to change the way a set looks to accomplish the creation of a
less formal Design Development package as compared to a
Construction Documents set, for instance. This flexibility works best
92
USING THE CARTOON SET

One major benefit to having the entire Layout Book linked early in
the project is that at anytime, it is possible to produce the set, or
portions thereof, for all types of progress work. To get the most out
of this inherent advantage, it is suggested that the .LBK template not
only contain the subsets, layouts and linked views to produce the
layouts efficiently, but also contain publishing options/sets to
produce all of the typical output used in an office so that users are not
required to alter settings each time different size, medium, or
destination is desired. For instance, typical publishing sets that may be
desired as standard options are:
full sizes plots;
full size color prints;
half size plots/prints;
full or reduced size .PDFs.
Since each option requires either a different output device or a
different scale setting, a separate Publishing Set needs to be created
for each, and should be named in order to provide information
without having to review settings.
See also ArchiCAD 9 Reference Guide for more information on importing

views and linking views to project .PLNs. and the Sharing Information on
page 79, as well as Output from PlotMaker on page 63 for related
information.
93
Tip: For Publishing Sets created in order to produce different

output results from the same set of drawings, it is recommended
that the sets be created using a clone of the Layout book. Using a
clone enables the user to edit the layout book without having to
maintain multiple publishing sets; a task that can be time
consuming and difficult to manage.
expectations and desires; and the time and skill necessary for each
user to have in order for them to produce the desired results.
Project Benefits
Using ArchiCAD, PlotMaker and the Cartoon Set methodology,
plans, sections, elevations, and any linked details, are all developed
simultaneously and can be evaluated in the context of the published
set at any time. A complete set of project documents illustrates both
the level to which the drawings are complete and the level to which the
design is complete. This completeness makes for more informed and
timely decisions by all members of a project team, leading to more
thorough drawings and more well coordinated buildings.
Since all projects have their own requirements, and each project
manager has his/her own methods for producing a project, it is
important that the Layout Book be accommodating. Freedom for the
user to create custom publishing sets, can be accomplished in one of
two ways: the user could either create the custom sets on the fly,
being responsible for all settings; or, empty custom sets can be
created, addressing the various conditions as listed above, letting the
user simply add the layouts to be included, while being assured the
desired output will be produced.
As with many other attributes contained within the ArchiCAD
Virtual Building template system, there is the trade off of the time
and resources necessary to create a template replete with all firm
94
INDEX
Symbols
.DWG 82
.LBK 17
.PLA 57
.PLN 17
.TPL 23
.XML 21
A
Add-On Manager 78
AEC/FM 85
Application Preferences & Profiles 18
ArchiCADs virtual building 85
Archiving 57
Attribute Manager 39
Transferring Custom Attributes 39
B
Background 38
BLIS project 88
business objective
IAI 85
C
CAD Layer Guidelines 16
CAD Manager 85
CAD Resources
Project Staffing 12
Staff Resources 11
Use ArchiCAD within the Project Lifecycle 12
CAD Resources 11
Cartoon Set 89, 93
Composites 35
Consistency 62
Contents of a Template File 24
converting to ArchiCAD 10
Custom Attributes 31
Custom Installation 18
D
Data Safety 55
.PLA 57
ArchiCAD Archive File 57

Archiving 57
Autosaving 55
File Backups 56
Include All Parts of Loaded Libraries 58
Manual Saving 55
PlotMaker Layout Books 59
Staying Organized 60
Determining the Scope of a Transfer 86
Display Combinations 30
Display Options 30
Document Manager 14
DWF 17
International Alliance for Interoperability 85

IFC
Embedded GDL Objects 88

Exchanging Files 83
Extending ArchiCAD 77
Adding Functionality 78
Add-On Manager 78
benefit 86
Versions 86
IFC Add-On
Information for Construction 85
IFC compatibility 86
IFC compliant applications 88
IFC concept 85
IFC Exchange Protocol 88
IFC exchange task 86
IFC Integrated Object Model 85
IFC2x
platform 86
Industry Foundation Classes 85
Information for Construction 85
Integrated Object Models 85
International Alliance for Interoperability 88
Inter-Operability 85
ISG 88
Favorites 40
Folder Hierarchy
3D Image Files 17
Digital Filing System 16
Externally created text or data files 17
PlotMaker Layout Book(s) (.LBK files) 17
Project detail files (.PLNs or .DWGs, DWFs 17
Virtual Building File(s) (.PLN files) 17
Folder Hierarchy 16
Font Types and Sizes 39
Layout Book 89
Library Management 41
Additive Libraries 49
Advantages and Disadvantages 47
ArchiCAD Object Library 43
Creating and Maintaining an Office Library 49
Creating the Office Standard Library 51
File/Folder Naming Conventions 53
FTP Libraries 54
Loading Time 48
Localized Solution 46
Location of Libraries 45
Network Libraries 45
Office Standard Library 43
On-Line Acquisition 54
Project Specific Library 43
Transitioning Libraries 52
Types of Libraries 41
Updating Libraries 50
Links for Using the IFC Exchange Protocol 88
Lock, Hide, or Show 28
G
Graphisoft translators 88
H
Hotlinked Modules 81
HVAC 86, 87
I
IAI 88
95
Index
M
Master Layouts 65
Materials 36
Model Manager 14
O
Office Standards 10
Output 62
~ Devices and Software 70
~ from PlotMaker 63
Master Layouts 65
Printing from ArchiCAD 62
Publishing View Sets 63
View Links and Subsets 66
Output from PlotMaker 63
P
Pen Weights and Colors 38
Pens Weights and Colors 31
Planning an IFC Exchange 86
Printing from ArchiCAD 62
Project Attributes 69
Project Benefits 94
Project Cartoon Set 89
Project Delivery 12
Design Communication 13
Project Leader 85
Project Template File 23
Publishing Objects Online 88
Publishing View Sets 63
S
Saving 55
Send & Receive Changes 75
Set Up a Pilot or Test 87
Shared Information 80, 81
Sharing 79
~ AutoCAD Information Directly 84
~ GDL Objects 88
Exchanging Files 83
Hotlinked Modules 81
Making It Look Right 82
Setting Up 82
Shared Information 80
Sheet Content 91
standards 7
96
Custom attributes 7
Directory structures 7
Display Options Combinations 7
Layers and Layer combinations 7
Libraries 7
Pen sets 7
Views and View Sets 7
Stories Approach 37
Stories 37
Switching to ArchiCAD 10
Views 87
Views and View Sets 24
Virtual Building 7, 8, 79
Exploiting the ~ Database 8
W
Work Environment 39
Working Environment 37
Working Units, Dimensions and Calculation Units 38
T
Tailoring ArchiCAD 15
Establishment of Standards 15
The Intent of Custom Setup 15
TeamWork 71
Backup Options 71
Project Information 76
Project Workspace 73
Setting Up ~ Projects 71
Sharing the Project 71
Sign In/Out 75
Single User Application 74
Team Application 72
Team Selection/Management Issues 72
Template File 38
Template 89
test the process 87
Textures 36
Training
Continuing Education 14
Needs of CAD Staff 14
Needs of Executives 13
Needs of Project Leaders and Senior Architects
Evaluation of Firm Project Types 27

Fill Types 34
Layer Management and Setup 27
Line Types 33
Pen Setup 33
13
Technology in the Office 13

Training 13
U
Uniform Drawing System (UDS) 15
use a template 23
Use of Layer Combinations 28
Use of Layer Extensions 27
V
Version 87
View Links and Subsets 66

Intro To Office Standards

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Intro To Office Standards

Uploaded by

Copyright:

Available Formats

Introduction to Office Standards

Introduction to Office Standards

Purpose of the Book

A special thanks to Graphisoft for providing the opportunity to share

The purpose of this manual is to assist architectural firms in taking

Introduction to Office Standards

Introduction to Office Standards

Quality and Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Introduction to Office Standards

USING THE VIRTUAL BUILDING

Composite materials, thickness, height, layer, pens, etc., should all be

Exploiting the Virtual Building Database

When used in conjunction with ArchiCADs calculation functions,

A New Way of Thinking about Architecture

design development phases of a project. This may result in potential

In conclusion, beyond providing a way to minimize coordination

Introduction to Office Standards

Introduction to Office Standards

MANAGING CAD RESOURCES

Technology Staff Resources

Introduction to Office Standards

identify project specific needs and coordinate with IT in their

When to Use ArchiCAD within the Project

Introduction to Office Standards

Another method for creating the appearance of less final drawings is

Introduction to Office Standards

Addressing the Needs of Executives

Addressing the Needs of Project Leaders and

Experienced users of ArchiCAD on larger projects have identified

Addressing the Needs of CAD Staff

It is important to note that instantaneous productivity is not a reality.

Initial Training and Continuing Education

Introduction to Office Standards

Introduction to Office Standards

Project Resources: the provision of ArchiCAD specific templates,

One of the benefits of this system is that it keeps like elements

It is important that all the project information has a place to be

Introduction to Office Standards

Introduction to Office Standards

APPLICATION PREFERENCES &

Introduction to Office Standards

Note: It is crucial that the CAD Manager(s) establish a baseline of

Shortcut Schemes replaces the previous Keyboard Shortcuts interface

The User Preference Scheme contains many of the settings previous

Introduction to Office Standards

The Tool Schemes portion of Work Environment combines all of the

Introduction to Office Standards

Added versatility is attained through the Work Environment by each

Profiles and/or Schemes can be imported directly from a network

Note: Profiles or Schemes that are imported by a user will reside as

The level to which standardized customization takes place is a matter

Introduction to Office Standards

THE PROJECT TEMPLATE FILE

It is important for the CAD Manager and the firms management to

Contents of a Template File

VIEWS AND VIEW SETS

Note: It is extremely important to specifically and descriptively

Introduction to Office Standards

An implementation of these functions would be to create discrete

Introduction to Office Standards

As a general rule, it is always best to use and reuse information in the

consistent and much easier to attain and maintain, working on the

Introduction to Office Standards