"Labels are text blocks or symbols optionally linked to construction elements and 2D fills. Labels allow you to identify or comment elements or parts of your design." That's from the ArchiCAD 9 Ref Guide page 343, and it's pretty succinct so I'll keep it. Here's more:

"You can use labels in two ways:

Independent labels manually placed using the Label tool.

Associative labels can be assigned automatically before the creation of an element or added to them later."

So there's two kinds. Independent labels are like regular objects, in that they do their own thing. There is a simple text label that's basically a text block with a leader, and it works OK as long as you don't go longer than one line. I (used to!) use these to call out structure in the sections and other simple things like that. They are a marginal improvement over plain text with an arc.

Associative labels are attached to elements, and can say intelligent things about them. They remain accurate as the data they represent changes. They can move when the element is moved. They are very cool.

(Why don't we use them yet? Because the underlying design of the label functionality is very poor, making it hard to figure out how they work, especially the differences between the two kinds. Now that I/we have them figured out, the actual making isn't hard.)

Frequently (Probably) Asked Questions follow. I'm focusing on associated labels, since independent labels are simple.

More»

Zones are calculation instruments. They represent rooms and other definable areas/volumes in the project.

More»

In the future, buildings will be engineered and documented exclusively using virtual modeling techniques. The near future.

The term 'model' is being used in two ways: To pretend to build, as with clay or Legos. To simulate using math, logic, and rules, as with climate modeling.

Carry this further, and we see that the virtual building model contains two types of information: Polygons, the stuff the building pretends to be made of, and descriptions, the words and numbers about the stuff the the building is made of in reality.

This is instantly recognizable as the ancient duality of architectural documentation: pictures and specifications. Show what it should look like, add descriptions for clarity and emphasis.

We model geometry, which ends up as drawings. We model information, which ends up as specifications.

The geometric, polygon model allows/forces us to check the consistency of the geometry. Things have to fit. It discourages pretending. You can move the polygons now, or the concrete later.

Working out the geometry is hard work. But it is the exact same work builders have always done, now orders of magnitude less expensive. The responsibility of designers to understand the geometry has not changed. The tools have made this understanding a hundred times more attainable.

With the geometry in place, the simulation model gives us for free the ability to maintain the integrity of the information.

Ideally, we would draw/describe every single thing in the project, and point to the drawings/descriptions from every conceivable point of view. In reality, the maintenance of describing every single thing in every conceivable context becomes prohibitive. Changes are incompletely deployed, and you have inconsistency as well as errors of commission, i.e., mistakes. This is worse than what you were trying to avoid: errors of omission, where things aren't called out enough.

The virtual building enforces consistency. It enforces it by moving one window and affecting multiple views. It enforces it by letting you draw a detail once and call it out indefinitely.

As you zoom in in scale, less information is modeled, and more is drawn and described. Details will be drawn for the foreseeable future. This does not mean they're 'not modeled' and therefore substandard. They are drawn within the system of the virtual building, drawn once and called out repeatedly. Drawn accurately, so their geometry is checked, even in 2D. In this way, they are part of the model as simulation.

The important thing is for the professional, you, as you 'draw', to maintain the integrity of the model, in the software and in your mind. It is permissible and necessary to draw, but you must know exactly how that drawing relates to the model, and be able connect the drawing to the model, and maintain the connection. It is the maintenance, again, that is expensive. When you 'just draw it', you are sacrificing integrity, risking error, and making your job harder.

Buildings are incredibly complicated. The paradigm of our time is to say of complicated things, "They contain a lot of information." Without a computer, managing a lot information requires a lot of energy, which means people and money. With a computer, managing a lot of information is only slightly more costly than managing a little.

Cars and airplanes, which are much more complicated than buildings, have been designed digitally for some time. This shows clearly that the slowness of adoption in the building industry is due to culture, not technology. People are coming to realize that a complete building simulation is an extremely valuable document. It helps everyone: Architects, clients, engineers, tradespeople, facilities managers.

The virtual building idea is nearing a tipping point, where suddenly the next day it will be everywhere, like the web, or cars, or airplanes. We are lucky to be in the forefront of this movement; the late-adopters will be looking for work. Technological revolutions have a way of putting the leaders in the middle of the pack. We must continue to push forward, because things are about to start moving very fast.

Nothing new really, but here's some links to the stuff we looked at.

Solid Element Operations
Existing to Addition Transition
Cache Library

Update: I have expanded on this topic here". I have strikethrough'd the really wrong bits here.

(I am planning a tech meeting for this topic the week of the fifth.)

Q What is a detail window.
A new kind of window in AC8. A hybrid of a section window and a patch.
Like a patch, they can be generated from existing geometry. Like a section, they can be renewed. Unlike a section, they cannot be model views, only drawings.

Q What are they for.

More»

Tech Meeting Notes, PlotMaker 3, July 29, 2003.

More»

Tech Meeting Notes, ArchiCAD 8 Navigator, July 29, 2003.

More»