Moving The Use of Building Information Modelling in the Construction Industry Forward

Writer Jeffrey Pinheirol’s has an interesting post up about what contractors are looking for in the BIM models they receive. I’m actually already sold on the benefits of looking forward in the building process for how best to structure the building data but his post contains some good practical advice about how to best approach this goal. The first take away for myself was that we should all be using REVIT’s build-in assembly code parameters in our models. Having each model element associated with its matching UNICODE format data greatly facilitates the estimating process (and by extension the tendering process). For myself, I think tagging model elements with assembly code data represents easy low hanging fruit which any firm can take implement of with very little investment.

Secondly, the writer touches on an issue central to the development of BIM. The coordination of the required level of detail in any given project has been a difficult goal to achieve for the BIM community. While the consequences of either over-modelling or under-modelling a structure are clear. Less well understood is agreed upon definitions of differing levels of development and detail within a project. Fundamentally this is a communications issue which manifests itself with inconsistences in the deliverables. This issue is an obstacle especially for distributed teams and integrated building design workflows which require a shared language to continually move the design forward. AIA’s Level of Development package is a good starting point for establishing agreed upon levels of development but certainly project partners have also stepped in to define the model’s level of completeness on a case-by-case basis.