James, I am in complete agreement with you. Everyone should decide for themselves which BIM application works best for their firm.
At the AIA Convention in 2005, I visited the booths of (in my opinion) the top four BIM application developers. After spending hours at their booths watching demos and having discussions, I narrowed the list to two: ArchiCAD and Revit. Following additional research confirming these two seemed best suited for us, our firm set up a team of four architects who then spent four months immersed in Revit, and then another four months immersed in ArchiCAD. We brought in developer-authorized trainers for both programs, developed a test project through all phases of a project, kept comparison spreadsheets of "soft" aspects such as ease-of-use as well as factual aspects like file import/export capabilities.
After 9 months, we chose ArchiCAD. It was a surprise decision to many, as most architects in our region were being told that "BIM=Revit" followed by: "and here is the cost to upgrade from your AutoCAD licenses..." We rocked with ArchiCAD for several years. "BIM-plementation" of ArchiCAD was successful.
But then our firm's practice began to change and we found ourselves partnering and sharing design roles with other architecture firms around the country as our expertise in our market grew beyond just our local region. As the majority of these partner firms were using Revit (often by default as mentioned above) our use of a different successful BIM platform not only surprised them, but presented challenges during some model exchanges, and further, precluded any possibility of both firms working "live" in the model. (ArchiCAD has had single-server-based live participation for several years, and we even offered other Revit firms ArchiCAD licenses but there were no takers.)
We eventually came to the conclusion that we needed to move (back) to Revit. (Like previous posters in this thread, we used, er, more accurately TRIED to use, Revit 1.x for over a year.) It was difficult to explain this move to staff as they struggled learning Revit, having full capability of producing excellent work in ArchiCAD. While we considered running both platforms for a little while, in the end it became the
right business decision for us to switch all projects over to Revit, even though most staff still preferred ArchiCAD after learning Revit.
You can squabble over comparisons of "pet pallets" and ribbons, and talk about which company has more market share in different parts of the planet, but in my opinion, in the end it really comes down to which tool best facilitates success for your individual practice. Try them out. Don't trust the chainsaw salesman.
Tom Peterson
-------------------------------------------
Thomas H. Peterson AIA, LEED AP
Principal
Mackey Mitchell Architects
Saint Louis MO
www.mackeymitchell.com -------------------------------------------
Original Message:
Sent: 03-14-2013 10:11
From: James Vandezande
Subject: ArchiCAD vs Revit
Good posts here, but there's one problem that no one has yet to address - you shouldn't be making a major design/production tool decision based on what other people say. If you're a cabinet maker using hand saws and you query your friends about which power tool you should buy and they say a chainsaw would work best - would you go out and buy one?
Each software application for BIM has its pros and cons - it's up to you to install a trial, spend some time learning the application properly, and doing a sample project. In an ideal scenario, try the same process on the other application under consideration and compare your results. Archicad might have some neat feature that makes your work much more productive than Revit would. Revit might be a bit easier to learn...what's important to your needs?
I started with Revit back in 2001 and my former firm evaluated it against Archicad and Bentley. We went with Revit - not because it was the best all-around application, but because it met MOST of our needs and was easy enough to learn that we could have just about everyone on a project team learning it and producing models. That same firm thought that Digital Project (Gehry's version of CATIA) was the best all-around modeling tool; however, when they tried to implement it across the board, only a few people out of the entire NY office figured out how to use it.
Recently, I have been frustrated by an apparent lack of innovation from the Revit development team at Autodesk, but it is still the core tool we can use to design and document about 90% of our project systems. What happens to the other 10%? Sometimes we'll need to use an application like Rhino with Grasshopper to develop a custom facade solution and then import it into Revit.
-------------------------------------------
James Vandezande AIA
HOK, Inc.
New York NY
-------------------------------------------