Interoperability, Data Exchange and BIM

            The assigned reading is about interoperability, which is a key to any engineering firm’s success. Projects must be shared among many different areas of expertise through different computer applications. Or must they? It seems that the goal of BIM is to bring all of these applications into one large file where all parties can access and edit the model. This is the way of the future, but we’re not exactly there yet. This article explains that it’s been almost 40 years since our country realized that interoperability is needed to keep project cost and time under control. 40 years seems like way too long to still be dealing with this issue as a country and even on the global scale. In terms of file exchange, the public level exchange formats are what need to be implemented in all engineering firms. They can handle all the excess data that goes into BIM in addition to the standard geometric data. The only reason I think the idea of interoperability has not been implemented in the field is because of business. Each company struggles to outdo the others by using different formatting and programming that will not be accepted by other companies’ applications. We’re never going to fully see the potential of interoperability until these companies figure out a way to work together, and that seems unlikely to ever happen. The ISO-STEP committee seems like it was attempting to solve this issue, but clearly has not succeeded. Similarly, the IAI has made considerable steps toward interoperability. This international program seems to be the best chance we have to making interoperability happen. Based on the information in this article, the IFC model structure is the only model format that brings all building systems together in one place, and links elements of all systems in the same model. This is what I understand BIM was invented to do. The model is incredibly in depth and contains geometric models for building elements of all shapes and sizes, of all ranges of importance. IFC’s are not great for complex shapes, and also can have trouble transferring connection and property data. Although IFC’s have limitations, there is potential to fix these problems in future versions. It’s good to see that as of 2007, just about all leading technological countries are attempting to integrate BIM and IFC’s into their engineering industry. What is emphasized is that these tools will be implemented in future design, but must be used extremely carefully and precisely in order to produce accurate and confident results.

            XML is another data transfer model that has more to do with applications to GIS, energy simulation, construction documents, quantities, etc. It works on web applications through html. Problems with XML are that the different XML data transfers don’t exchange with each other, and that they require more space than IFC’s.

            The article then discusses DWF  and PDF’s, which are simple files that are meant to show designs to respective parties. These files are only meant to be looked at, and not to be edited by the new viewers.

            The optional article I selected is called BIM Interoperability. This article is written by StructureMag, so it has a interesting expert opinion on the future of this issue. The article is far less technical than the BIM handbook chapter on data exchange, and it brings the idea into perspective for what can actually be done, and what is probably out of reach in terms of interoperability at this time. The article summarizes BIM briefly, explaining its most relevant use for structural engineers and surveyors. It mentions how BIM models can be paired with GIS software to skip a surveying job and go directly to marking column grids on site. It then explains that structural engineers are already converting, or have converted to BIM because of its incredible application in the industry. After all this praise, the downside of BIM is delved into: Data Exchange. BIM creates massive amounts of data that must be exchanged between many users and many building systems, but BIM is still in its “early stages” on this front. It describes 3 main ways of exchanging data in our field. 1. Through use of software by the same company. 2. Through software with an API, or an interface that can translate data from different companies. 3. Through use of IFC’s and CIS/2. In my opinion, #1 is never going to work because of competition in business. #2 is not going to work because of competition in business as well. So #3 is the only solution left for us to use to use for interoperability in BIM. This is the exact same conclusion made in the assigned article. Next, the article stresses that analysis programs must be integrated into BIM to help keep all design processes in the BIM model. This idea is still in the early stages of development as well. Similarly to the assigned article, this article next stresses how the intricate details of the model are extremely important, and they must be carefully designed and checked. Version compatibility issues are touched on, and then finally the future of BIM Interoperability. The article says that although the process is in early stages, it is still an improvement in technology, and should be implemented. I tend to agree with this article because I have seen how much can be learned from BIM compared to more dated software. It states that interoperability is not going to stop BIM from taking over the industry, but it is going to make it take a lot longer to happen.