7 Tips for Updating Existing Project With New Standards
When I work with clients building efficient project templates for their firm, there is always surprised at the amount of items to consider when generating a template. Most firms cobble together a template over the years while working between projects, or it simply evolved into an amorphous mess with each subsequent project. After we nail down what the client actually needs, there inevitably is the question of “We have X number of ongoing projects, how to do we efficiently apply our new standards to existing projects?”
Optimistically, standards simply need to be copied over and simply manicure the existing project. Realistically, it is a long process that takes time to weed through and trim the fat. Some projects are hard to justify the time and money to update standards instead of working with the standards. Mostly it will have to be a management decision. If you can justify adjusting existing projects, here are my seven tips for applying new standards to existing projects efficiently.
1. Start over!
Can you start over with the new project template? How far along is the project? How much longer will the project continue? What are the BIM project deliverables? Will the standards update increase project efficiency? Is updating existing project standards critical for firm branding?
Depending on the answer to these questions, it might be best to start the project over with the new standards. If the office standards were in poor shape and workflows were not set up properly, it might save and/or generate more money in the long term to start over. Also, depending on what the project deliverables are, ensuring everything is standardized and clearly identifiable will benefit all parties involved in the project moving forward.
If this is not an option, consider the tips below for efficient updates
2. Use Transfer Project Standards
Revit has a built-in tool to assist in mass transfer of families to new files. This copies all family types and settings to a new file without having to do any work. Simply select this tool inside the project that needs the updated standards, click on the category check box required and hit OK.
Manage > Settings > Transfer Project Standards
The two downsides to using this method are, this only works for families, their parameter settings, and overlapping family names. Which means views and schedules are not transferrable using this tool. Another issue, if families in the new standards match the old standards there can be issues with duplicated items or no clear indication which family is the new standard aside from Revit adding an additional number to the end. My preferred method is to remove as much as possible or rename existing families to make spotting what needs to be removed or updated easier.
3. Insert from file
This tool specifically transfers views, sheets, and schedules from one project to the next. Particularly, firms use this to develop a Revit library file of pre-drawn details to selectively import into each project as needed, instead of including every possible detail in every project.
Insert > Load from Library > Insert from File > Insert Views from File
After navigating the file explorer to the correct file, select the correct view check boxes and hit OK.
4. Copy and paste
Ahhh nothing like the good ole’ CTRL+C to CTRL+V. This method is exactly what it sounds like. While crude, slow, and requires manually generating views, this can ensure accuracy selecting what should and should not transfer over. This method can be highly efficient by simply highlighting the desired families from a Template Standards view.
(BTW, all offices should have a Template Standards view as a Drafting or Legend view for quick reference. My preferred location is a Legend View to allow for legend components such as assembly families to be laid out, however this can cause issues when transferring to a new file. I will explain why later).
5. PyRevit: Copy Legends to Other Document
Revit, natively, does not have a feature that easily lets users transfers Legend views from one project to the next. However, along with the wide range of additional free tools available for BIM managers, PyRevit has a tool to answer the years of community cries. Go to:
PyRevit > Drawing Set > Legends > Copy Legends to Other Documents
This tool works similarly to Revit’s native Transfer Project Standards, so open both files in the same window to transfer Legend views. (Additionally, PyRevit also includes a tool to convert Detail Views to Legends and vice-versa.)
6. Categories to review
This tip does not cover every category to review and update but these are the major broad stroke categories to review when integrating into an existing project.
Line Styles
Located under:
Manage > Settings > Additional Settings > Line Styles
In every standard Revit file there are line styles wrapped with <>. These are Revit system styles that cannot be removed to renamed. Anyone can adjust the weight, color, and pattern but that is the extent they can change. All imported line styles will keep the existing weight, color, and custom pattern.
Dimensions & Text
Annotate > Dimension > Dimension Types
The dimension and text tools have a range of adjustable parameters to tailor branding. There are four different dimension string categories to be conscious of: linear, angular, radial, and diameter. Each dimension category type needs to be address and switched out with the new standard.
To edit text families, go to:
Annotate > Text > Text
Make sure to replace all existing dimensions and text families in the project with the new standards.
Symbols & Tags
Annotate > Tag drop down arrow > Loaded Tags and Symbols
Once all symbols and tags are loaded, select the default tags and symbols to be used. Setting these will ensure every time a user places a, window, tag the correct one will populate. This only sets tags that are not elevation, section, and callout tags.
Manage > Settings > Additional Settings > Annotations > Section/Elevation/Callout Tags
Separately, elevation, section, and callout tags have multiple families to make one type. Inside the view type dialog is where users set the combinations to create these tag types.
Fill Patterns/Regions
To learn more about fill patterns and regions read our previous post on the subject.
Filled Regions can be deleted by using the Purge tool, while Fill Patterns can only be deleted inside the Fill Patterns dialog.
Manage > Settings > Additional Settings > Fill Patterns
Assembly Families
This category is the hardest family type to deal with. Mostly due to switching out existing modeled assemblies with the new standards or converting the existing families.
Be sure imported families have unique names from the existing families to avoid any duplicates and confusion about which is the correct one.
Legends/Details
Legends and details simply need to be transferred using the methods outlined above and ensure all views are labeled correctly.
View Template
When transferring View Templates make sure any custom parameters associated transfer over. This is where a Shared Parameter files come in handy. Also ensure each View Type has a View Template associated so whenever a new View Type is generated the correct view graphics are applied.
Schedules
If there are any unique fonts for a schedule, ensure everything is still associated correctly to limit duplicate font types. When schedules transfer to new projects all unique schedule parameters will populate in the new project.
Title Blocks
Simply load title blocks from the file explorer or import from the new project template file. Ensure to add any shared parameters created for the project template that are not standard. Check out our other article outlining our must have items for title blocks.
7. Review and purge all unused standards
Once everything is imported its important to review what needs to be removed.
The Purge Unused tool cleans up a project file and removes all families that are not currently used. This helps by reducing the overall file size. (All BIM managers should perform this regularly.) Go to:
Manage > Settings > Purge Unused
Inside a user will check and uncheck Families and Family Types to purge from the file. This is the last point to ensure everything has been updated and replaced. If there are certain families that are not showing up in the Purge Unused dialog this means there are still instances of those families in the project.
Force Removal via Project Browser
Sometimes there are families that simply will not cooperate and remove themselves. So more drastic action is required. Inside the Project Browser, and under Families (near the bottom), there is a list of all lingering families. Right click and select Delete to finally remove the last bits. This will force Revit to delete those families by deleting all instances. Be careful when doing this to ensure there is no cascading effect.
Revit will not allow a user to delete every family in a project even if they are unused. There must be at least one family for every family category in a project. Who know why.
The last step is to save as and enjoy the new clean working environment. Savor the moment and remain optimistic someone will not f*** it up.