© 2011 Autodesk Top 50 BIM Bugs and Things to Avoid Nicholas M Kramer – HMC Architects

© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid

Nicholas M Kramer – HMC Architects

© 2011 Autodesk

Class Summary

Whether you are new to building information modeling (BIM) or you are a seasoned BIM pro, this class is for you. BIM is an intricate process, and you need to know where you are going before you can plan the path to get you there. Come and learn the top 50 pitfalls that can cause broken BIM models. We will cover all BIM bases from Autodesk® Revit® to Autodesk Navisworks® to Autodesk Quantity Takeoff.

© 2011 Autodesk

Learning Objectives

At the end of this class, you will be able to: Know what you should ask before starting every BIM project. Understand cross-discipline coordination issues. Understand cross-platform coordination issues. Know how your BIM process affects others downstream. Understand the main objectives of BIM and how to achieve them.

© 2011 Autodesk

Coordination: Getting Everything to Work Together

Know what you should ask before starting every BIM project: The needs of each project are different and change from project to project, team to team and over time. Address these ten points at the beginning of each project and keep them up to date. Going over standards and expectations at the beginning of a project and then ignoring them will lead to lost time, money and at best BiM, if even that.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: Coordination

Software Who and What

Hardware: Adequate vs. Appropriate

Content BIM revolves around content

© 2011 Autodesk


Naming Conventions: Drive BIM Obvious vs. Criptic

Project Set Up Define setup, critical path and leadership

Layout: Define and Track

© 2011 Autodesk


Information Exchange Consistency: stick to the schedule In Person vs. Digital

Non-Native Collaboration Use the model in all forms of communication.

© 2011 Autodesk


Viewers Get everyone involved.

Suites Look at what others use. Understand potential and limitations.

© 2011 Autodesk

Coordination: Getting Everything to Work Together

- Have a plan.- Keep everything up to date.- Know what it takes to keep the team working

together.

Nicholas M Kramer – HMC Architects [email protected]

- BIM is in the content, not the software.- Make BIM user friendly.- Keep track of the model.


© 2011 Autodesk

© 2011 Autodesk

Autodesk Revit ® – All Flavors:Trade Specific and getting them to work together.

Understand cross-discipline coordination issues: There is a lot you can do inside of Revit to make other platforms and even other flavors of Revit work together and work better. BIM is an ecosystem that relies on all parties working together. In order to achieve this each party needs to know how the others work and what they need. These fifteen points can help to better coordinate within your office as well as with the rest of the project team.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: Autodesk Revit ®

Initial Project Setup: Plan

Project Standards Consistent within the platform

Templates Office Project

© 2011 Autodesk


Views

Worksets Assigning Cross discipline

Copy/ Monitor Uses and Limitations

© 2011 Autodesk


Floor vs. Roof What are they used for?

Structural vs. Non-Structural Performance and ownership

Links Link everyone, but not everything

© 2011 Autodesk


Maintain Coordination Avoiding is easier than solving

Model as intended to be built Expect to change the way you work

Fixtures Ownership and Accuracy

© 2011 Autodesk


Systems (for MEP) Define and Filter

Sub Categories Break up specialties Consistency

Materials Uses and limitations

© 2011 Autodesk

- Plan each project.- Spend time on company standards.- Enforce standards.

- Know your limits.- Coordinate while you work.- Model for the project, not necessarily

everything.

Autodesk Revit ® – All Flavors:Trade Specific and getting them to work together.



© 2011 Autodesk

© 2011 Autodesk

QTO, E-Specs and Other AEC Software:In the program and what you do in other programs to make them work/ work better.

Understand cross-platform coordination issues. BIM is an ecosystem not a single platform. This ecosystem revolves around data. In the case of quantity take off and specification there are five key points that allow interoperability between platforms.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: QTO, E-Specs and Other AEC Software

Project Setup

Workflow

Data Management

Assembly Codes

Naming Conventions

© 2011 Autodesk

- Know your limits.- Model or data first?

- Ownership- Standardize communication:

software and people

QTO, E-Specs and Other AEC Bridging Software:In the program and what you do in other programs to make them work/ work better.



© 2011 Autodesk

Autodesk Navisworks ® : In the program and what you do in other programs to make it work/ work better.

Understand cross-platform coordination issues. BIM is an ecosystem not a single platform. This ecosystem revolves around data. Navisworks primarily looks at the geometry of the model and how it was created. These five keys points allow easier interoperability between Navisworks and other platforms.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: Autodesk Navisworks ®

Native Model Creation

Same model, different information/ geometry

Model Once

Export Views

Templates

© 2011 Autodesk

- Import and interpretation of native models- Collision/ Coordination Model vs.

Documentation Model

- Ownership: model and data- BIM turnover

Autodesk Navisworks ® : In the program and what you do in other programs to make it work/ work better.



© 2011 Autodesk

Facilities Management and Post Construction:What to do during design and construction to facilitate continued use of the BIM after occupancy.

Know how your BIM process affects others downstream. BIM is an ecosystem not a single platform. This ecosystem revolves around data, data which continues to live on for the life of the project. Standardizing this data within BIM is the key to its continued use. These five points will create a starting point for the standardization of data as well as a basic facilities management solution.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: Facilities Management

Project Setup

Shared Coordinates

Data Type

Data Use

Shared Data

© 2011 Autodesk

- Start out right- Share

- Standardize data

Facilities Management and Post Construction:What to do during design and construction to facilitate continued use of the BIM after occupancy.



© 2011 Autodesk

© 2011 Autodesk

Top 10: Ten things that will make or break BIM.

Understand the main objectives of BIM and how to achieve them. Follow-through, better buildings and a cheaper and greener lifecycle.


© 2011 Autodesk

Top 50 BIM Bugs and Things to Avoid: Top 10

Consistency Content Standards

Planning Ownership Schedule

© 2011 Autodesk


Communication Hiding Follow Through

Management People Project Data

© 2011 Autodesk


Compatibility: Software Who What

Workflow: Stay in BIM Dead-end BIM What dimension (2, 3 or more)

© 2011 Autodesk


Workarounds Effects on others Lost information

Collaboration Instant/ Online Weekly upload death

© 2011 Autodesk


BIM for All Get the entire project team in BIM People = Information

End Goals BIM vs. BiM vs. BIM What information?

© 2011 Autodesk

- BIM = people: not just computers.- Automation ≠ Communication- Get past “weekly” uploads

- (Fake) Workarounds ≠ BIM- BIM for all- Plan your goals

Top 10: Ten things that will make or break BIM.


© 2011 Autodesk

About the SpeakerNicholas M. Kramer, LEED® AP, is a project leader and BIM project administrator at HMC Architects in Ontario, California. He has been using Autodesk Revit® since version 8.1 and has helped to implement BIM across an architectural company of over 400. He is currently the company-wide resource for BIM content creation and standardization on a wide variety of projects. His project experience varies from a 400,000 square foot library to higher educational laboratory buildings to medical tenant improvements to the renovation of the MLK Hospital in Los Angeles. Nicholas is currently serving as the president of the BIM User Group Inland Empire (BUGIE), and has guest lectured on BIM and sustainability in other forums. He is also a Committee Member and speaker with Revit Technology Conference – North America.

[email protected] [email protected]

Contributors: Brian Andresen – WLC Architects; Hiep Huynh – Saiful Bouquet Structural Engineers;

Michael Smith – CW Driver; Ed Tallmadge – Kelar Pacific; Jay Zallon – Perkowitz+ Ruth Architects


http://www.linkedin.com/profile/view?id=55629681&trk=tab_pro

http://www.linkedin.com/profile/view?id=55629681&trk=tab_pro

http://hmcarchitects.com/

http://www.meetup.com/BUG-IE/

http://www.revitconference.com.au/

mailto:[email protected]

mailto:[email protected]

© 2011 Autodesk

Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2011 Autodesk, Inc. All rights reserved.

Documents

© 2011 Autodesk Top 50 BIM Bugs and Things to Avoid Nicholas M Kramer – HMC Architects