R5 - Data Interchange

I thought the assigned reading was a very good overview of the technological data exchanges that occur between various programs associated with creating a BIM model. Although some of the detailed technical terms were over my head, it seemed that the most beneficial exchange format was having direct, proprietary links between the BIM tools. I think it’s extremely important to have all of the systems linked and interdependent on one another in order to accurately model a building. Slight changes in one area can drastically affect the needs of another. For example, adding 10 more windows to the south face of a building could change the demand and sizing of the HVAC equipment, and any program that does not allow direct data interaction might miss these relationships. I was especially interested in the CORENET program in Singapore, because they seem to be taking the BIM model a step further and integrating the construction and project management into the modeling process. Some models are merely used in the design phase to predict the way a building will perform and to design it efficiently, but I think carrying the BIM model further and monitoring input data during the construction process is going to be a major component of building modeling in the near future. Similarly, the Norwegian approach to integrating automatic code checking will be important, though this might be difficult since codes change all the time. The language monitoring the codes in the program would have to be edited or rewritten quite often. I definitely think this would be most beneficial in a rapidly growing area, where code violations might be overlooked due to the fast pace demand for buildings, such as Beijing.

Intrigued by code checking technologies in BIM as the required article discussed, the second article I read was the Impact of code checking usage on IFC model, CAD, and end users: the challenge of imperfect data by Naveed Shaikh. This article outlined the primary obstacle with code checking - imperfect data due to a variety of causes can make code checking difficult. Among these include human error, varying building designs, and most importantly, the inability of CAD or another drafting program to export a model to create an accurate IFC model. These are programs that check the consistency of an IFC model, but require customization for each model being checked, so they are limited in this respect. One program, FORNAX, is being used as a buffer zone between the imperfect inputs from various disciplines and the generation of an IFC model to minimize the amount of imperfect data being used. Because different buildings have different designs, it’s difficult to code check objectively without identifying what all of the spaces and components of the building model are. As the data comes in, FORNAX reads it all simultaneously and recognizes objects and spaces (ie kitchen, corridor, toilet). This allows the program to compartmentalize the areas of the building for easier code checking. FORNAX also uses some name recognition, so if something is labeled kitchen, it can reference codes for kitchens, and check the adherence to the code before converting it into an IFC model. Overall, I thought this was quite interesting, and could have large impacts on design time and accuracy.