B2 - Advantages and Challenges for Interoperability in BIM

Chapter 3 of the BIM Handbook was centered on the topic of interoperability. Eastman began the chapter by defining this idea broadly as “the ability to pass data between applications.” Essentially, it encompasses the ability of different programs and processes to translates data across the defined levels of tools, platforms, and environments within BIM. When this version was published, these ideas were still largely in development. Eastman claims that “extracting the stick and node model for a structural analysis and determining the relevant loads is not yet a common automated translation”, but during my co-op experience I have seen that REVIT’s family properties have become robust enough to take not only standard members but also custom trusses or girders and convert them into usable STAAD models, greatly improving efficiency in design. Platform to platform (REVIT to Structureworks for example) provide the most amount of hurdles because of the amount of data and properties used to describe objects, as well as the economic consequences to each of these companies for creating pathways to communicate with each other. These programs are each looking for different properties with unique syntax to describe the same objects that populate models. The National BIM Standard is working to standardize these processes in order to allow data to be exchanged easier between programs.

Eastman makes a point of identifying the streamlining of workflow as the next great leap for the construction industry. He proposes the idea of BIM repositories that function as a storage area for the actual objects that define a building (not the file types that are unique to applications). This automates exchanges and allow different stakeholders to pull down relevant information into their respective analysis software. In the near future, this is expected to be industry standard in project management. In the design stage, interoperability can lead to streamlining as well. Auto-fixing of systems in response to clash detection and auto-communicating between model, takeoff, and estimating services can free engineers from these tedious tasks.

However, the ushering in of interoperability has presented some issues as well that will need to be resolved before full implementation can occur. In a BIM repository scenario, the master model must be entirely complete, containing all of the data relevant to the different disciplines (down to structural connections, with complexity and precision adequate enough to be useful to Finite Element Models and other such processes). The ability to auto-update all models with a change made in one automatically to prevent confusion. Even in a situation where auto-updates occur, these can often have ripple effects that could go unnoticed and provide significant issues to a particular disciplines design (the movement of mechanical equipment changing the loading on a particular bay for example, leading to a scenario where perhaps members are not sized appropriately). It will also be necessary for designers to be involved in the process of developing interoperability tools – expertise is necessary for identifying and defining the parameters relevant for one program relative to another, as well as when these definitions can change (an exterior wall contains structural properties, as well as an assembly with a specified R value that impacts building energy performance).

Eastman, Charles M. BIM Handbook : A Guide to Building Information Modeling for Owners, Managers,Designers, Engineers and Contractors. Vol. 2nd ed, Wiley, 2011. EBSCOhost,        ezproxy2.library.drexel.edu/login?url=http://search.ebscohost.com/login.aspx?direct=true&db= nlebk&AN=364239&site=ehost-live.

Comments:

Alec,
I enjoyed your qualification of BIM as  "bridge" that connects contractors to the design team. I think in addition to the practical cost-saving benefits of including contractors (to a degree) in the design process, there is also value in establishing trust between the project stakeholders as well. If everyone is included in the room from the outset, there will be a much deeper understanding of each party's interests and priorities, reducing the amount of frustration that can occur when the building actually goes under construction.

Harvin,
I think your chapter is really vital to understanding a lot of the benefits (and challenges) that exist with BIM software. Having an idea of the mechanics of BIM software (inputs, outputs, properties, etc.) can help to envision the various ways that BIM can be applied for different members of the project team. Your post was helpful to read in conjunction with the chapter that I was assigned to read on interoperability because many of the roadblocks that exist in that sphere revolve around differences in BIM programming structure. Focusing on streamlining the syntax and properties of objects in the BIM environments is a necessary step to improving project efficiency as a whole.

Christian,
I think that your reactions to Chapter 3 of Eastman were very similar to mine. It is interesting that you noted that many of the manual inputs to BIM will ultimately be automated with the advent of more robust interoperability capabilities. One of the recurring themes that I have thought about since the lecture that was given in class week is the impact that this will happen for traditional job roles in the industry. It appears that many of the responsibilities given to entry level engineers at firms prior to them gaining necessary experience to undertake their own projects will soon be automated. I think that this will make the transition from college to the workforce a much more intimidating one, and that a separate infrastructure (perhaps a stronger, defined mentorship program) will need to be developed to take its place.