Dwight wrote:
...
It takes commitment - firms that fail to employ 3D usually skimped on training, never brought in a consultant to help change their corporate culture - Aaron Bourgoin chime in here - and weren't that interested in producing superior construction documents...
Yes, I'll chime in.... Someone I know who, on seeing ArchiCAD for the first time, laughed and said, mockingly, "ArchiCAD sounds more like a way of life than a software application."
Somewhat defensively, I said, "You're absolutely right."
A month later, he placed an order. Client demand had given him a reason to buy a tool like ArchiCAD. The reason was convincing renderings of a project in a hurry. He seemed happy enough until he passed the software on to a pencil monkey who in his ernest desire to make a pretty picture modelled every brick in a large facade and brought a 3 city network to its knees.
Five years later he's no longer a user. He grew tired of trying to explain the rationale for a way of life to his partners and made the decision to get on with his life. The client demand for 3D stuff was still there and his firm was, for a time, situated on a testimonial page at the ADT web site despite his admission to me that after two years of using Desktop his firm still had no real idea of what to do with it.
The corporate culture is a strange thing. In my experience as a user and a reseller as well as someone responsible for its use in a large installation, the move to virtual building must be embraced by everyone in the firm and there absolutely has to be a deployment plan in place. A firm that doesn't function as a team, but rather a collection of individualists will not succeed in making ArchiCAD work.
An Illustration, albeit anecdotal:
One: The principal buys in:
Principals of firms very often champion ArchiCAD because they see the value of working in 3D.
For themselves.
Period.
The "way of life" is introduced and soon fails because as long as the principal can work the way they want, the rest of the team can do what they want as well. One sure sign that this is happening is the principal's reluctance to upgrade the software. The old version works fine - the new one is maybe a bit too complex. Another sign is that AutoCAD creeps back - in the dead of night.
Dwight wrote:
...
ArchiCAD destroys the archaic architectural labor pyramid - more senior people must have active involvement in forming the model, inevitably teaching the minions more - assistants learn more about building making models that quickly provide "reality information" to destroy the erratic fantasies of vague, gesticulating principals...
Two: The principal doesn't get it or at least not the whole thing
A recent post mortem on a project included the following statement:
"The transition from design development to working drawings necessitates the creation of a new model. The underlying assumptions in the design are not reflected in the construction of the design model and it should be restated. This can be done quickly because the principles are understood and its faster to remodel them than it is to massage the existing model."
I'm not sure if this is simply the statement of one who doesn't understand the virtual building process and is therefore totally wrong; or, if he has a point. Certainly if the model is constructed in such a way that it can't be revised to demonstrate these first principles of a design that there's something laking in the approach.
As someone involved in training and coaching, I think this is a sign that there still isn't a buy-in and that training needs to be taken back to something very basic.
This year I've been doing winter seminars taking one tool at a time and trying to reinforce the relationship between the tools. This was greeted with an initial sense of scorn - as if this was so basic that it was stupid. At the end of an hour, the attitude had changed. I heard comments like, "I didn't know you could do that", "I've been working too hard", "did you know that you can do it this way as well and its faster..."
These sessions have now transmuted into trying to make an even simpler point and that is if you don't work with other people in mind you really run the risk of cocking things up real fast. If a virtual building is not being constructed to a standard (where that the measure of it value is that anyone can pick up work on a project with a minimum of familiarization) the the information in the model can soon become very unworkable.
The true test of the transition to virtual building is in the understanding that while it might resemble 2D drafting (a comforting and seductive quality of the interface) but that it is surely something else entirely. For example, it is not enough to show someone how to label a wall a certain way (a triangular label of a set size, offset from the wall a certain distance. This is because the label is not really a label in ArchiCAD, its a portal to another source of information and that information (a wall type in this instance) is information that resides with the wall and NOT the label. This sounds very simple, but it is extremely hard to grasp for some people.
Again, a team approach, embedded in the corporate culture is essential.
Three: The principal still doesn't get it at all and probably won't.
Sometimes we look back to the days of the project file drawer and the sketches that document the progress of a project. They contain no re-usable information, simply an idea about the project at a point in time. In the old days when all we had were drawings, each drawing had a certain purpose. There was no such thing as a drawing that said everything.
A project is being developed by two firms in two different cities. Both use different tools. To make matters worse, one firm is drawing plans in AutoCAD, and developing two different models in Form*Z. The form is a compound curve and the temptation to extrude an unrationalized spline along a path has become too great. Every week there is an information exchange and the building information gets iterated into an ArchiCAD model. The spline is altered slightly and the recasting of the roof has to begin again. Base drawings are reissued from ArchiCAD, the AutoCAD plans are updated and the section (well, I really don't know what's happening to the section, I can't track the comings and goings of this one anymore).
The information or the "embodied knowledge" to paraphrase a current sustainable design term now exists in at least four drawing spaces and in the minds eye of at least two senior people who don't draw for themselves. Each version of this building - the 2D CAD plan, the two form*Z blobs and the ArchiCAD section each fulfill their respective role in the progress billing for the job.
Three instances of no teamwork, no direction, and no strategy. Where might this go? Less profit, more attrition and less competitive advantage.
Dwight wrote:
...
Working in ArchiCAD means that you have to think your work through - you can't "sort of" fake a thing up and hope they'll "work it out on the site." In Canada, this is a euphemism for "big [censored] change order."
Doing everything in 3D - to a point - provides work saving information and prevents ducts attempting to drill through beams. ...
I do not yet see the point where virtual buildings are ready to be embraced in even forward thinking practices. I used to think that firms who bought ArchiCAD to make pretty pictures - and only pretty pictures were the firms who soon ended up using the boxes as doorstops.
In the coming paradigm shift there will be other reasons for the breaking away from virtual buildings. While fewer firms are evaluating software simply for its ability to make pretty pictures, I've tried to illustrate the point that even those that see value in the model as "embodied information" and the "embodied knowledge" that is captured by and resides with a clearly articulated CAD standard can also miss the point. Big time!
Just as the argument for virtual building is still in its infancy, so too is the notion of sustainable design. Early adopters have embraced LEED as a way of hanging out a green shingle and its a pretty easy credential to obtain without necessarily knowing how to make sustainable design work. The early adopters are losing their competitive advantage as even the least "sustainable" firms can grab the credential with two days of studying and $350USD.
In order to reestablish a competitive advantage, the early adopters must refocus on teamwork and making the notion of "integrated design" work. Convincing engineers of this is a very frustrating task because it involves a similar reorganization of the labour and resource pyramid - that is the ways and means by which they have always been able to make more money than architects on projects - wait until the architect has stopped designing and go like hell at the very end. (ArchiCAD is way too front end intensive for current engineering practice. that is not to say that they'll never get it, but if architects are typically late adopters of technology, engineers don't like to disrupt their well-oiled money making machines.)
A convergence between this ongoing evolution of practice and the virtual building is coming and it may force the issue with the encouragement of the client. Building simulation is an important part of sustainable and integrated design. To do it effectively, it has to become a standard tool on the designer's desktop and not something to be hired out. (in Canada we don't really do simulation or life cycle cost analysis in real time we design something and execute a battery of tests on it to see if we passed - sort of like punch cards and computer runs).
Virtual building is the key to kicking the building while its being designed and another means of keeping more of the fees in house.
Here, too, the challenge is in making multi-platform collaboration work, a slow and steady encouragement of other consultants to embrace a virtual building platform (an argument for "integrated design" if there ever was one), and the education of clients to understand that there is a life for the virtual building that extends beyond the design and documentation of a project as well.
Think Like a Spec Writer
AC4.55 through 27 / USA AC27-6000 USA
Rhino 8 Mac
MacOS 14.6.1