Building Information Models (BIM) support designers and builders in creating and coordinating system designs and planning work. In practice—out of necessity—this includes checking that systems do not clash, but what constitutes a clash? How do clashes come about? Do clashes relate to design-, buildability-, or building- performance qualities? How does a clash detection process fit (or not) in lean project delivery? In this paper we describe our findings from research into clashes. Our sample is biased in that a number of the people we spoke with have been working in Integrated Project Delivery (IPD) teams, with commercial terms spelled out in an Integrated Form Of Agreement (IFOA). Many are co-located on their project site—at least some part of each week—so that they can work together closely as their thoughts on design and construction unfold. It is common practice for these teams to share their BIMs, each discipline-specific model having been developed by a specialist design- or contracting firm, and integrate them in a big-room setting. Nevertheless, this integration process invariably appears to include the identification and resolution of clashes. When viewing these BIM development practices from a ‘lean’ perspective, we found that many are far from lean. Accordingly, we present opportunities for process improvement when using of BIM in pursuit of lean ideals.
Building Information Model (BIM), BIM pathology, clash detection, root-cause analysis, design management, tolerances, constructability, contingency, waste