Blog 2: Chapter 2

I read chapter 2 of the BIM handbook which discusses BIM Tools and Parametric Modeling.  This chapter dives into the history of BIM, different BIM softwares and their utilizations including converting 2-D drawings to 3-D, and the various means used to identify similar components of a BIM software to compare different softwares.  Giving names to all of these components like tools, platforms, and environments, and the parts of history that went towards developing BIM softwares really helped me understand what goes into the software from an engineering perspective, and the players that contribute funds to the development and research of this type of software. 

My personal experience with AutoCAD has allowed me to begin learning AutoLISP, the coding language behind AutoCAD, which was mentioned in this chapter of the textbook.  This knowledge and experience was being put to use while reading through this chapter as I could identify specific exercises that I completed at work with the specific terms that the BIM handbook used.  In addition to this, section  2.3.6 raises some commonly asked questions, including one specifically that I, and many of my colleagues have asked in recent years: “Why Can’t Different Parametric Modelers Exchange Their Models?”.  In other words, or as I would actually ask the questions: “Why can I not export my model from one software to another?”.  Finally, I am able to understand, as explained in this section, that BIM softwares are able to define object behavior at the foundation of an object’s definition, and different softwares identify this behavior differently.  This behavior includes how 3-D objects interact with each other when, for example, a wall sits on-top of a concrete slab.  Although on the surface every software might represent this interaction the same way, the behind-the-scenes behavior of that interaction happens differently in different softwares.  This is why when converting models or files between softwares that are compatible, everyone is always wary of “glitches” or issues in the software during the conversion.  The model may get messed up, but only because the background behaviors of the objects differs for each BIM software.

This was just one of the topics that really resonated with my understanding of the softwares, and I am glad to finally have a better understanding of this phenomenon.  The background information that this chapter explains has provided me with a much better understanding of these softwares, and the interactions between them.

Works Cited:

[1] 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.

Response 1: Richard Kimball

Richard, I think that your conclusion at the end of your post to find a compromise between the systems or methods being chosen between is the best means to an end of creating the work product.  In the beginning of chapter 2, Eastman explains that when deciding between the two different modeling methods for defining objects, it was clear that they should be combined to create what is known as BIM modeling today.  Linking these ideas together, grabbing the best parts of each method is the best way for us to move forward in BIM modeling, and in the AEC industry.

Response 2: Kunlun Ren

Kunlun Ren, that was a great summary of the chapter that really highlighted each of the main points from the main sections.  Although many engineers and architects that use BIM stop learning about it once they know how to use the software itself, I believe that it is very important to understand how BIM came to exist, and also the parts and pieces that are running behind the scenes.  Understanding the difference between tools, platforms, and environments can give a drafter a much better understanding of what it is they are doing, and also how to optimize and improve their methods.

Response 3: Harvin Bhandal

Harvin, I like how you discuss the definition of an object’s behavior and how it interacts with other objects in a BIM software.  Like you said, each object in a BIM software interacts with other adjacent objects, and follows the pre-set rules of that particular software, although each software has its own set of rules to follow.  This is important to note as everyone who has used more than one software has noticed that everything works differently to get to the same work product.  Understanding why these differences in softwares exist, and realizing why and how some softwares are better than others for specific tasks can help to improve efficiency and help the engineer or architect understand the topic better.