This blog is about using BIM on a day to day basis. I cover ArchiCAD tips and tricks, BIM and management thoughts, and occasionally how this all relates to the Minnesota ArchiCAD Usergroup (which I started in 2009). The specifics are about ArchiCAD—that’s the software I use and sell—but the overall themes are relevant regardless of your software. Programs are just tools. BIM is a mentality.
Posted: January 22nd, 2012 | Author: Vaneshrie Sullivan | Filed under: Guest Bloggers | Tags: Templates, Tutorials | 4 Comments »
The Interactive ArchiCAD Practice Manual came from the realization that, although there are numerous books on teaching ArchiCAD users how to use the tools and navigate around projects, there is not much guidance on how to apply this software in the most efficient manner in an everyday office environment. ArchiCAD is both user friendly and customizable, giving users the freedom to work in the software in countless ways. The price to be paid for this flexibility is that, in an office with many staff and no basic guidelines, the wheel is constantly re-invented. Over 10 years of training ArchiCAD users, I have also noticed that new features are not being applied in a structured format. Many users work with the latest software, but neglect the newer tools and workflows.
The standards in the Interactive ArchiCAD Practice Manual aim to provide solutions to setting up Projects that are easily adaptable through phases of Planning, Tender, Construction, Interiors and As-Built drawings, and have been developed over the years. This book refers to ArchiCAD version 14, however, it is possible to adapt the standards to suit older versions as well. I am hoping that the Interactive ArchiCAD Practice Manual together with standard templates and example files available for download will be a starting point to assist offices in creating the foundations for a structured Practice. It is my hope that every ArchiCAD user will find this book beneficial to their practice.
It is my intention to continue working with newer versions of ArchiCAD and to keep updating these standards. I also offer consultancy services to ArchiCAD users, such as Tailoring Custom Office Templates, Creating Translator Files, Training, Technical Support, Creating Library Parts, etc.
For a preview of the book please visit the website.
Posted: January 11th, 2012 | Author: Kristian Bursell | Filed under: Guest Bloggers, Long Posts | Tags: BIM philosophy, GDL, Modeling, Objects | No Comments »
I officially entered the building design realm through the Architecture and Environmental Design course at the University of Canberra. After constantly being told that my ideals were that of a dreamer I became unsure of myself and decided the safe option was to follow the notions of friends, family and university Lecturer’s on “what life is”. However I felt nothing when I reached the milestones they said would bring fulfilment; and in the space of two weeks all I was told to aim for crumbled, and I found myself in a deep dark hole. So I threw their notions to the wind, clawed my way out of the hole and began beating my own path. Lesson 1; follow your heart not your head, because others will fill it with rubbish that does not apply to you.
Within my first year in the industry I had taught myself ArchiCAD and was already much faster than the experienced ArchiCAD users around me. My deeper understanding of the program meant that I was relied upon for maintaining and developing ArchiCAD systems within every company I worked for.
While delving into the capabilities of ArchiCAD I began to explore the wonderful world of parametric objects. I then began teaching myself all the nuances of ArchiCAD’s GDL scripting language. GDL, at its peak, is a very well organized series of geometric equations with a maze of variables. I discovered that creating parametric GDL objects gave me a great deal of satisfaction.
There is something very fulfilling about seeing parametric 3D objects come to life through mathematical equations. Perhaps it’s that overwhelming urge to create and understand form that many of us from the non-child-bearing gender experience. Whatever it is, I knew I had found my calling.
When I moved to Brisbane the head and the heart battled again; I was running out of money and my head was telling me to take one of the many jobs I was offered, but my heart, for no apparent reason, was set on working for Cottee Parker Architects. A couple days before my funds ran dry the call from CPA finally came and I was hired before the job interview was over.
My heart new best; the 3 years I worked for CPA was the best opportunity I could have to develop my skills. I spent the first year in CPA’s Brisbane office assisting with the development of their impeccable ArchiCAD template. Working on large scale projects taught me more about exploiting ArchiCAD’s full potential. I was also relied on to develop a series of intelligent parametric GDL library parts.
Being a small town boy at heart, one year in the big smoke was all I could bear. Also, my ArchiCAD development work for CPA was still only, at best, 50% of my workload; my speed made me far too useful as a documenter. These two factors prompted me to move from Brisbane back to a small coastal town. However, when I discussed this with Robert Cottee he asked me to continue doing ArchiCAD development work for CPA from wherever I planned to move to. I jump at the opportunity and for the next two years I worked as a remote ArchiCAD manager, developer and trainer for CPA.
Two solid years of GDL scripting was a great opportunity to learn what is possible with ArchiCAD library parts. It helped me to isolate the best scripting methods to ensure the parts I create are of the highest standard. When my role with CPA was terminated in October 2008 due to the Global Financial Crisis, I began working on my advanced set of GDL Library Parts.
 Swift Joinery |
 Swift Gutter Plus |
In the last few years I have consulted to a large number of small, medium and large architectural firms, optimizing their ArchiCAD systems. I have discovered that the majority of people, and companies, do not use ArchiCAD very well.
My goal with ArchiCAD is the same as it was in the beginning; to automate as many processes as possible simply by modelling building elements. The only way to do this effectively is through GDL Library Parts. You are not working efficiently if you use a tool to model an element and then have to add in lines and text and other manual 2D information to complete the representation of that element in all views and schedules. Modelling will be tedious if you have to use a boring parameter list to configure each aspect of the modeled element. With moveable hotspots in 2D and 3D and polished user interfaces, my library parts bring joy and speed back into modelling.
The idea of BIM is information in a model, the idea of Swift library parts is enjoying modelling every building element and having ALL required information in the modeled element. I will continue to develop intelligent design tools through GDL and help everyone enjoy the BIM process as much as possible. Visit CADSwift to learn more.
 Swift Car Ramp |
 Swift Vehicle Paths |
Posted: August 28th, 2011 | Author: Jeroen de Bruin | Filed under: Guest Bloggers, Long Posts | Tags: ArchiCAD-Talk Forum, BIM philosophy, GDL, Modeling, Objects | 3 Comments »
My adventure started after finishing a bachelor in architecture and working in several architects’ offices. I found that drafting in 2D really annoyed me: First draw the floor plan, then the elevations, manually add in shadows… and then the architect changes the design and you start over again. Those painstaking hours of checking if the elevation matched the floor plan… If only there had been an ArchiCAD feature like Trace and Reference! I was always looking for ways to prevent errors and optimize the program.
In 2006, I started working for the Dutch reseller of ArchiCAD. At the first sight of ArchiCAD I knew that I would never go back to old 2D methods. Pretty quickly I mastered ArchiCAD and was enjoying all the automatic stuff. From there I took my first steps into GDL. By opening the open source objects from Graphisoft ArchiCAD’s Library I studied the code. My first objects were really simple, but it was fulfilling to create something and see it work. And once the first steps were taken, I became an enthusiast. I wrote more objects and overcame many GDL challenges. But the reseller needed more from me besides library-development; I had a lot of other activities like support and training. This meant little time to focus on my many ideas. Since in my spare time I was starting all sorts of GDL projects, I started my own company just for the fun of GDL.
 |
I started a topic in the ArchiCAD-talk to offer free custom GDL objects. I created a number of objects and posted them on the Object Depository, like the Sea Container. I really liked the contact with ArchiCAD users from all over the world and got many great responses. Besides the user requests I had some ideas of my own, which I started to sell on my website. Slowly the amount of objects grew and now I have 28 objects and counting.
 |
Good GDL objects are versatile, and they are never more versatile than when you create them yourself. Though GDL is not easy, anybody can create custom objects with the built-in object creators from the File / Libraries and Objects – menu, which is why I made some objects that convert self-made objects by the user into something parametric. For instance, the Object Slicer can create a Floor Plan Cut Plane-sensitive and story-sensitive display of any self-made object. Or the Silhouette, with which you can easily create people or tree silhouettes that automatically turn to the camera, all without any knowledge of GDL.
Lately I have been writing articles for ArchiMAG on a freelance basis. In these articles I describe how to make a parametric object with very little GDL knowledge. GDL can be very overwhelming, but with a few inside tricks you can unlock a great deal of power.
The core objects of Master Script are the BIM objects. ArchiCAD is a BIM program and I love to write objects that retrieve the “I” in BIM: the Information. While creating Label Everything, I discovered the true amount of data that can be extracted from an ArchiCAD element. Besides displaying the data, it can also be processed and show any data in any form you like. To improve the BIM factor of an object, it is essential that it lasts through the whole project. You can put in a lot of information, which can grow during the project. But it is important to be able to show this information in many sorts of ways. To do this I use the Model View Options. This underlying Library Global-technology allows you to store the behavior of an object per view. The object on the floor plan simply retrieves the active settings stored in the MVO and displays it accordingly. This gives the object many possible representations but can also be effectively controlled. I have incorporated this in the Total Zone and Total Marker.
 |
My next adventure is trying to attract manufacturers of building products. Generally manufacturers offer 2D CAD files as a way of marketing their products. Obviously they should start offering ArchiCAD objects, but the building industry evolves slowly. So I want to take the opportunity to ask of all of you to start asking for it! Write an e-mail to the manufacturer of your choice (or more than one) and ask for GDL objects. You can redirect them to any qualified GDL developer like me or anyone on the developers list of gotogdl.net.
Posted: July 24th, 2011 | Author: David Jefferis | Filed under: Guest Bloggers, Long Posts | Tags: Production, Templates | 5 Comments »
This guest post is by David Jefferis.
 Hybrid Notation |
My preferred style of notation breeds the Full Text Note with the Full Keynote to produce the Hybrid Note. The primary problem with both styles of notation presented last week is the lack of hierarchy: special details or materials are not given special treatment and can get lost amid the notes for standard assemblies. Using the Hybrid Note system, these standard assemblies such as wallboard, base trim, and insulation are keyed. Complex or custom assemblies and materials are called out on the drawings directly as text, calling special attention to these conditions. Combining text and keys in this way also reduces the weaknesses inherent in their pure states. Since unique conditions will show up only a few times in the set (else they would be typical and become a keynote), it reduces the amount of text to review. The lack of hierarchy within the keyed notes also becomes less of an issue since there are fewer of them, and their repetition aids memory and reduces the need to constantly reference the key. I use this style for almost all new construction, where unique conditions always arise, and renovations and additions, where typical assemblies meet unique existing conditions.
Serial Notes versus Specification Sections
I’ve written and illustrated the last two posts assuming that keynotes use serial numbering (1, 2, 3, etc.). It is possible to improve the effectiveness of both the Full Keynote and the Hybrid Note styles by keying the notes to specification sections. For example, one could use the key (9.25) for gypsum wallboard. Since I rarely work on large commercial or institutional projects where complete and detailed specifications are prepared simultaneously with the construction drawings, I usually use a simple prefix and suffix method to denote the section. For example, using the prefix 9 for finishes and serial suffix 01, 02, 03, etc. for any finish notes results in the numbering series 9.01, 9.02, 9.03.
Constructing the Keynote
Unique Symbols: It’s good to be different.
Establishing a unique graphic symbol for keynotes is fundamentally important for easy legibility, especially on plan and elevation sheets where there may be many different types of symbols. Basic geometric shapes (Circles, Squares, Triangles and Hexagons) are usually already claimed by doors, windows, equipment, revisions, or other standard components. My preference is for hybrid shapes, such as the rounded rectangle used throughout these examples. Elongated hexagons or ovals are other good options.
 Leader Lines: Orthogonal, Angled, Curved |
I have used all of these leader lines types at various points in my career and I believe that they all have their strong points. The orthogonal style can be made most compact and is simplest style to use if it is important that all leader lines are aligned. The angled style is the fastest to use, as long as one is not too picky about perfect alignment of the leader lines; on the drawings I’ve seen this style is also the most common. Finally, the arced style is most easily legible: since details for even curved forms tend to be drawn with many orthogonal lines, the leader lines stand out from the drawing they annotate. Also, alignment of leaders is not as much of an issue since a variety of curves is not as visually distracting as many different angles.
 Leaders: The ubiquitous arrow |
If you’ve ever worked in an office, you are familiar with the arrow as the more or less ubiquitous way of pointing at detail conditions. I was introduced to the leader line with no arrow through European drawings and construction manuals. I believe that it actually aids clarity since there is no arrow tip to obscure portions of the drawing. It also simplifies the graphic presentation. However, this is one point where I have often given in to convention, since the arrow is a nearly universal standard. The example image is shown with Full Text Notation and orthogonal leader lines since this is how I’ve usually seen it deployed in drawings.
About the author:
David Jefferis is a licensed Architect working in Houston, Texas. Though ArchiCAD is his preferred program, he have extensive experience on multiple modeling and rendering platforms. His primary interest is in general techniques and theories of standardized architectural representation, with a specific focus on the ways in which BIM software alters the way these drawings are made by expanding the amount, availability, and types of graphic and textual information.
Posted: July 17th, 2011 | Author: David Jefferis | Filed under: Guest Bloggers, Long Posts | Tags: Production, Templates | 9 Comments »
This guest post is by David Jefferis.
In these posts, I will focus on general techniques of standardized representation and strategies for producing construction documents so that our conventional drawings can be exceptional.
An important but rarely discussed part of starting an office is establishing a set of effective graphic standards for communicating design intent through construction documents. Most design websites and blogs show multiple rendered perspectives, plans and sections of their featured projects, and it takes only minutes to download a huge catalogue of images as reference material. However, conventional architecture working drawings are much more difficult to find and, when shown, are often stripped of their dimensions, notes, keys, and labels.
This imbalance is understandable. After all, a primary purpose of renderings is to be beautiful, to seduce and convince. In the construction document hierarchy, on the other hand, beauty often takes a distant third place behind accuracy and completeness. The argument I will make through these posts is that beauty, the coherent graphic expression of a design, is not a subordinate category but is instead an important part of what makes a drawing accurate and complete. Given the flexible and efficient organization tools and object editing available in modern modeling software I believe that beautiful construction drawings can be, if not effortless, than at least easy.
 Like videogames, cartoons have lots to teach us |
About two years ago I reached a milestone in my career where drawings began to appear naked unless clothed with an array of keys and notes. I like to think of drawings as a comic strip: you can read the words, or you can look at the pictures, but you need both to get the point. The prevalence of many notes on even the smallest set of drawings means that an effective notation system must be in place so that notes are written and can be read consistently, accurately, and efficiently.
 Full Text Note |
The first style, Full Text Notes, is one familiar from historical working drawings and is the type I used as a residential designer. Individual callouts on the drawing are fully written out each time they appear on the drawings. This style of notation is easily legible, and does not require someone reading the drawing to look back and forth between graphics and text.
However, complex or unusual details can become very crowded with long, detailed notes. This in turn requires more time to write and organize drawings. A greater problem for someone reading the drawings is that this style of note has no hierarchy: since every note is treated in the same way, it can be difficult to call attention to unique conditions. In addition, this style of notation can become time-consuming and inefficient when redlining a large project as each note on each drawing must be checked for accuracy.
In my experience smaller firms primarily engaged in residential projects use this type of note. In my own work I typically use Full Text Notes for small residential or commercial projects with a minimum of unique conditions.
 Full Key Note |
Unlike the Full Text Note, the Full Keynote is highly efficient to create, check and correct. Since each note is written out once per page and linked to a number the note has to be checked only once for accuracy. Verifying that each reference number indicates the correct assembly is much faster than verifying the accuracy of many Full Text Notes. The small size of the reference numbers also gives you greater flexibility and speed in arranging notes on a drawing.
However, like the Full Text Note the Full Keynote has no hierarchy. This is exaggerated by the fact that the Keynote numbers have no clear relationship with the assembly they describe. In addition, like the Full Text Note unique details and conditions still tend to get lost in a sea of numbers.
I was introduced to this style of note when I worked for firms doing large commercial and institutional work. This style of note will become more prevalent in residential work as architects must increasingly rely on standardized proprietary products for roofing, framing, insulation, lighting controls, and other building systems. Recently I have been working on commercial projects with many standard details and have found this style of note to work very well.
In my next post I will describe my preferred style of notation, the Hybrid Note.
About the author:
David Jefferis is a licensed Architect working in Houston, Texas. Though ArchiCAD is his preferred program, he have extensive experience on multiple modeling and rendering platforms. His primary interest is in general techniques and theories of standardized architectural representation, with a specific focus on the ways in which BIM software alters the way these drawings are made by expanding the amount, availability, and types of graphic and textual information.
Posted: May 22nd, 2011 | Author: Jared Banks | Filed under: Guest Bloggers, Short Posts | Tags: Endless Path of Improvement | 10 Comments »
In the next few months I’m planning to revamp the blog and website. I’ve spent the last year focusing on writing and getting the word out. Now it’s time, among other things, to update the about page and the ArchiCAD page to better reflect who I am and what the blog has evolved into, add links to my favorite ArchiCAD sites, etc. As the first step in that process I’d like to both free up some of my time to fiddle with the parts of the blog I’ve been neglecting and also offer the opportunity for others to speak via the Shoegnome blog. My hope is that there are plenty of others with lots to share. So…
I’m looking for people who would be interested in being guest bloggers. Do you have a story that fits into one of the ten pieces of advice from this post? Let’s here it. Perhaps you’re a new user wanting to share your struggles, successes, and frustrations. Or maybe you are an experienced user with some great advice to give. Maybe you don’t use ArchiCAD but see how Shoegnome’s philosophy and blog is relevant to your work and want to share.
Version 15 comes out tomorrow. I am unfortunately working on a project in version 11 for the next month, so I won’t have any ‘in the trenches’ posts about version 15 until mid-summer. I know I’m not the only one interested in hearing about people’s first experiences with Version 15 before then.
E-mail me with your ideas.
Wisdom from the Crowd