BIM: Myth of Clash Detection

The myth

‘Clash detection’ is one of my favourite subjects, in a cranky, gets me annoyed kind of way. It has become the auto-response to justify the benefits of BIM by those who don’t understand the design process.

The myth is that clash detection is a BIM magic button that will guarantee a good design.

In fact, if not used properly, ‘clash detection’ will make the the design coordination process more difficult, more time consuming and will produce an inferior design result.

Clash detection is fantastic for final validation that the design is correct- but only useful within the right design process.

Technology over commonsense

I see projects where the various design consultants or subcontractors will independently put a significant effort into modelling their design without much planning, communication or coordination.

The models are then federated by the BIM Manager in a ‘clash detection’ process to see if it fits together (of course it won’t …)

The approach is generally ‘first-in, first served’, so arguments ensue over who needs to move their beam/pipe/duct/cable tray. The number of clashes can be gigantic (I’ve seen 40,000 in a single federated model) and individually resolving each clash is a slow, tedious or even painful process.

So- it can be a triumph of technology over commonsense.

It is much better to use BIM to plan and communicate, then model correctly the first time and use clash tools to check it all fits together.

Good design: Much more than clash free

Metrics such as 100% clash free design are sometimes used- this is quite meaningless and akin to counting the vacation as enjoyable just as long as the airplane and the mountain don’t collide. There is a lot more to a good design than merely a lack of clashes. A good design should be:

>Logical and efficient
>Repetitive where possible
>Readily constructable
>Readily maintained and serviced

and so on….

Therefore, a ‘clash free’ design is obviously necessary, but it is not the only criteria for a quality or complete design process.

Change in Behaviour

The strange thing is that the behaviour of design consultants, contractors & subcontractors (who really should know better & end up wasting their own time) has been influenced this capability of software, so that the design process is flipped on its head.

A Design Issue not a BIM issue

An interesting side effect of this phenomenon is that work that previously (and rightly) would have been a design coordination issue has now become a BIM issue. In other words, the task of identifying and resolving design issues seems to become the responsibility of the project ‘BIM Manager’ or similar, rather than the designer.

Start big, work down to the detail

BIM can play an important part in the design coordination process, which culminates in ‘clash detection’.

However, a common mistake is that too much model detail is added too early, with not enough attention in the planning stage. BIM can play an important part in this planning stage:

  • Agree typical design zones
    for structural, building services or fitout/finishes. This obviously has an effect on the construction sequence. If necessary this could be modelled as an extent.
  • Develop a ‘design zone’ model
    including horizontal and vertical zones allocated to each building service, structure & so on. This can be a fairly simple massing model that just shows the overall anticipated extent.
  • Commence discipline modelling
    by staying within respective zones. The zones for maintenance/replacement access should be modelled as a massing ‘exclusion’ zone.
  • ‘Anti-clash’ checks
    By visually comparing the zone model and each discipline/trade model, the design can be quickly & easily checked. I guess you could see this as an ‘anti-clash’ i.e everything from a particular discipline/trade should fall completely within the zone. It is only where the model goes outside of the zone that you need to worry.
  • Deal with exceptions
    There will obviously need to be exceptions where services have to pass through another zones and these can be dealt with individually. This could also apply to suspension or support systems.
  • Clash detection
    Once this has been completed, then a clash detection process can be completed as a final validation to make sure nothing has been missed.