One way to manage content more efficiently is by creating a Container File (or you may sometimes hear this referred to as a “Warehouse File” or a “Source File”). This file contains various templates for content that are used repeatedly. This helps to centralize your team’s ability to work on that content since Revit doesn’t allow you to save that content as an individual file.
These container files are different from template files. 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 of the content in the source/container file includes system types, drafting views, schedules, materials, fill patterns---basically, anything that you can Batch Export.
Here are a few examples of what you could have in your source/container file:
A file of system types that you use regularly, such as walls, roofs, ceiling, duct types, model groups, detail groups, railings, and stairs.
Drafting views where you have a detail that is already drafted up that you want to use again on different projects. You want something to start with so that you don’t have to draw it all from scratch. UNIFI allows you to pull that detail out and add it to UNFI so that it can be easily added. Keeping these detail items in a single file will make it easier for you to work with.
Once you make a change to something in this source/container file, you can use the Batch Export tool to save that to UNIFI, and then your team can easily find this content using UNIFI’s robust search features.
This helps you manage those changes across types quickly and efficiently.
The Notes option in UNIFI also allows you to create notes as edits are made, giving your team a clear history of what changes have been made.
You can also upload this Revit project to UNIFI and we can store it for you. You can make any changes and save that updated container file to UNIFI. One efficient way to store this is to create an Internal Library for this that allows just Admins to see this. They can use this simply as a working file to make changes.
To make it visible for End Users, we recommend that you create a Company Saved Search that is organized in a way that you’d organize your container file (for example, you might have Common Walls as a Saved Search).
