Is BIM the future?
BIM (Building Information Modelling) has long been the way I think the industry ought to work. It just seems so logical to me. The premise is simple – build an intelligent 3D model of a building which can be exported and manipulated by various designers, including architects, structural engineers and building services engineers. This model is in effect a virtual prototype of the proposed building. Various proposals can be tested in the virtual model, resulting in an actual building whose vagaries are well understood before a brick is laid.
Sounds great on paper, but the reality is that this is still a long way off. What does the industry need to change in order to further this technology, which exists today but is grossly underexploited?
One problem is that the information in CAD is not suitable for direct export into BIM (this article explains well). IES are hoping to have moved one step closer. They have teamed up with AutoCAD Revit to enable BIM more easily.
What worries me slightly is the claim:
This direct link means the user can run a variety of analyses, without needing specialised skills, separate analysis packages or separate models for each analysis. Greatly increasing the quality and speed of the technical feedback this development enables building designers to examine the implications of alternative design strategies at the touch of a button and use the tools for sustainable design rather than just plant sizing.
A nice philosophy, but beware of putting software in the hands of those without specialised skills. You still need to know how to interpret results, even if you no longer need to be a master at 3D building modelling, something which Kathy Sierra* touched on here.
But does BIM actually reflect reality? I don’t think so. Do you know anyone who uses Hevacomp or IES to it’s full potential? Or are you more likely to come across engineers who use a mish-mash of pencil and paper, excel spreadsheets with a little bit of hevacomp and perhaps a little IES thrown in? This dissonance between what the software is capable of doing and what the user actually wants it to do is probably part of the problem. Users see the software as too complex for what they want to do and so don’t want to overcome the hurdle of learning a new way of doing things. There’s some great writing out there on this topic including this (old) article from Jeffrey Phillips :
So the conundrum is, we’ve got to design for lowest common denominator in a user interface, while providing as much functionality as is necessary for the customer to be interested and excited in the application. Unfortunately, the users of applications are rarely the buyers of applications, so we need a better method to get the proposed user interface in front of the actual users as often as possible.
So is the problem with the software or with the users? It’s probably a bit of both. Another Kathy Sierra’s post tries to explain some of the reasons from the users’ perspective.
A final word from Jeffrey Phillips again:
The real rationale is that requesting a new feature is costless. A customer or prospect can ask for features all day long. However, the user interface and its complexity has tremendous cost, since most people are lazy and don’t want to think – and good design should not require them to think overly much. In fact good design should lead a user to the right conclusions and actions without a lot of training or support help, regardless of the number of features. What people are really saying is: give me the features I want, but simplify the interface to make it even easier to use, so I don’t have to receive training, or support this application once we start using it.
This is a topic I’ll be returning to. I hope BIM is the future, for lots of reasons, but for the minute there are hurdles to overcome…
*Sadly, Kathy hung up her blogging boots back in April 2007 after a nasty cyber incident involving death threats. Yikes. I still miss her blog…
Recent Comments