BIM managers never want finding content to feel like playing 52-card pickup. They don’t want content scattered with everyone wondering if they are using what they are supposed to be using for a particular project. Instead, they want content to be organized and easy for team members to access.
One method for organizing content is by using container files. These container files allow firms to store system families that Revit doesn’t allow you to save as individual files (for example, fill patterns, drafting views, schedules, system types, etc.).
In this article, we will explore some of the benefits and drawbacks of using container files and will share our BIM experts’ recommendations for efficient content management.
A container file works as a centralized location for your team to store system families (you may have also heard of it referred to as a “warehouse file” or a “source file”).
These container files are different from a template file. You might utilize a template file for a new project, but you can think of a container file as a file that’s holding content that you would use for a specific type of project. For example, a container file for Schools could hold school-specific content such as walls, ceilings, stairs, etc.
Some items that work well in container files include:
• System types
By storing this content in a container file, you can ensure that users are always using the most updated content associated with that project type.
One Time-Consuming Drawback of Container Files…And A Solution
One of the drawbacks of using a container file is that you must constantly open each container file to see which system families are available.
But we recommend a more efficient method for using container files.
You can use UNIFI’s content management platform to export the items from your Revit container file and import them into UNIFI where it is easier for team members to find and insert into their projects. An easy-to-access button will appear in Revit (for UNIFI users) that lets them export content in minutes.
Exporting these container file contents to UNIFI also helps you to manage changes across types quickly and efficiently. You can easily track edits that are made in the Notes section, thus giving your team a clear history of what changes have been made.
Another drawback of using a container file is that content may not be as easy for team members to find.
But if you export your container file content to UNIFI, you could create saved searches that allow your team members to find what they are looking for in seconds.
To sum it all up, container files save time by allowing you to store system families in one centralized, searchable location. Exporting container files to UNIFI’s content management platform makes it easy for your team to access that content in seconds. Want to learn more about how to streamline your BIM management process using UNIFI? Click here to get started and book your live demo today.
Phone: 415 915 2123
Knowledge Center: help.unifilabs.com
Join us on social media.
Copyright © 2023 by UNIFI. All rights reserved.