Autodesk BAT Meetings

Tocci Stock

June 27, 2008 WOBURN, MA. Tocci, and our project partners KlingStubbins and Autodesk, recently held the kick-off meeting for Autodesk HQ, New England’s first IPD (Integrated Project Delivery) project and the first for all participants involved. The team began by reviewing the fundamental reasons IPD works:

Optimizing the whole: As individual team members can only benefit when the overall project is a success, participants are incentivized to merge talents & work together.

Collaboration unlocks creativity: Diverse viewpoints will produce more creative ideas, in both quantity and quality.

Self healing organization: Minor failures lead to major catastrophes. Since individuals are working as a unified team, small issues are brought to the table and resolved, rather than covered up.

Challenges spur creativity: People are known to “rise to the occasion”. However, when the challenges are too great, individuals become defensive, which negatively impacts collaboration, therefore intensity rather than hysteria will be cultivated.

Now that the project is in full swing Tocci is seeing examples of these principles everyday, especially in BAT meetings, when the full project team comes together. The BAT is the Building Advisory Team – a group of Autodesk employees that represent the various departments for design input. These are essentially design meetings but because the project is IPD everyone is involved during all project stages. So Tocci attends design meetings and KlingStubbins will visit the construction site and attend Tocci’s monthly meetings. The key to all this collaboration is the BIM (or The Model) which all parties are building and utilizing. An example of this model use occurred during last week’s BAT meeting. An amazing “BIM Moment” occurred; this is our Virtual Construction Manager’s account of the meeting:

BAT meeting in progress

“We were reviewing a potential feature in the building, with the hope that we could come to a decision. KlingStubbins had prepared a number of views, showing the feature. After going through the series of images, no one was sure if the feature was an effective enough design component to approve it. Offhand, one of the representatives from Autodesk offered to prepare a walk-through of the feature for the end of the meeting, but most people were convinced that the feature wasn’t going to happen. The feature was tabled until then.

Later that day, rather than a canned walk-through, we actually walked-through the feature live, using FreeWheel. As a feature, it was hard to control (or at least it appeared that way), but after that we really understood the feature and its impact. After walking through the space, observing the feature as a user in the building, everyone realized that the feature did have a significant design impact.

Decision made: BIM saved the design feature – it will be included in the project!”
Quote courtesy of bimx

  • 0
  • 0
  • 0

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>