A thread on Brian Myer’s Revit Users Linkedin forum has been a good read and inspired a few of us here at Assemble to put our heads together on this topic. The Correct Modeling Practices thread has highlighted the state of building information model development from the perspective of BIM Managers at General Contracting firms and Architecture firms. As more teams leverage BIM information downstream, the question of quality always arises. We find that many design teams are interested in improving their models, and would like to know concrete ways to improve the data. They are also interested in gaining insight as to how other team members, such as estimators, are using their data downstream. At Assemble, our customers have published thousands of building information models, rich with data. Along the way we have had many discussions regarding the quality of the data, how it is organized and how to quickly get the most value out of the information. In an effort to further the development of models, to improve data management downstream, we have outlined 3 best practices we see repeatedly with our customers, for improving model development and therefore the quality of the data.
Some really important points such as the contractual use of a model, the BIM Execution Plan (BEP) commitments and other issues surrounding this topic are equally important and require just as much attention, but won’t be covered in this blog. Setting expectations for how the model will be used and at what stage in its Level of Development for downstream purposes should be explicitly stated in the BEP. Take the time to outline your BEP in detail, as it will improve communication of information greatly. Now, for tips on model development…
1. Names have a really powerful role in downstream use; take a moment to think them through.
If you have naming standards in your firm, bravo. Now use them! It is really easy to make a modification to a family, duplicate it and rename it and not think about the implications of that. The geometry seems to matter the most at the time. The problem is that the rest of the people that you work with downstream were not there when you made the change and don’t know what you were thinking at that time. Take the time to rename, or name appropriately to your office standards. It is a really simple way of improving communication. If you don’t have naming standards in your office, here are our suggestions for clarity. Often systems based information such as a wall type or door type is called out in the drawings but not clearly identified in the models. The exact method of naming can vary depending on the design team preferences and their current standards in place. Use the same practices you have for 2D drawings for describing the models and always have a reference to size. Notice the wall types in Image 1, the names are described differently, making it difficult to understand the intent.
System Name, Type Name as a reference to the drawings or specs. Example: Wall: Basic Wall: B6 – 3 5/8″ Partition
System Name, Descriptive Name with function or type and materials. Example: Wall: Basic Wall: Interior 5/8 GWB Metal Stud 5/8 GWB
Image 1: Wall Type descriptions; some with names and sizes, and some without.
2. Use the parameters you have access to.
Revit families have many parameters that are rarely populated. This is a missed opportunity. Comprehensive data extraction tools, like Assemble, will pull all information from the model for your team to easily use. If you don’t want a model component used for takeoff, add a note in the comments field. If you know the product but don’t have time to fill in all the fields about the model, manufacturer, etc., add a hyperlink. Even better, add a Project Parameter called Current LOD and label the level of development for the objects in your model. Revit parameters are really powerful and the team that uses the data downstream will get value out of the link you attach to the sink model component or the roofing system. Even though this data is buried in a dialogue box in Revit and not explicit to you in the geometric model, the team downstream will be able to easily retrieve it, use it to plan, schedule and estimate. A simple link to a product cut sheet will say a lot more than a note on a 2D page.
Image 2: Model information is populated with detail easily extracted and accessible in a platform such as Assemble
3. Follow Revit logic, don’t fight it.
This is a hard one we know, and there are many ways to approach it. Revit has a number of powerful scaffolds to organize geometry and therefore data; levels, worksets, phases, etc. When the data from your model is extracted for other purposes, these scaffolds are really great ways to section, organize and filter your design, largely in an effort to understand the design and the major systems. If you haven’t really thought about them, it’s usually clear downstream. Take for instance the image below. One of the approaches to model interrogation is grouping and viewing model components by level. In Image 3, the Level 1 objects are displayed to understand how the model was organized.
Image 3: Model objects grouped, filtered and viewed by Level 1.
Modeling is often the vehicle to represent the work that needs to be communicated in 2D drawing sets, however, as the industry moves forward with BIM, models are being leveraged for a number of purposes, including scheduling and quantity takeoff. For the benefit of the Owner and to build better partnerships with your consultants and GC’s, take some time to structure how your model can be organized to best communicate with the rest of the team. It will save you more time in the long run, maintain positive relationships with your customers and lead to a better project overall.
Nancy Brown is a Sales Manager for Assemble Systems when she isn’t traveling, skiing, or spending time on a boat with her family in the lovely Pacific Northwest.
Comments are closed.