Autodesk Revit Templates and Resource Projects

July 26, 2018 Martha Hollowell

By Martha Hollowell

I’ve been thinking a lot about template files for Revit projects as I am updating the Autodesk Revit BIM Management: Family and Template Creation learning guide for Autodesk Revit 2019 due out in early autumn. In the guide we mention resource projects used in conjunction with template files for a more effective use of project planning and execution. These tools don’t get a lot of attention, but they are a critical component of good BIM Management and make the designers' life a lot easier if the office standards are already in place and ready to use.

What is the difference between Template Files and Resource Projects?

Template Files

A project template is a file that contains information that can be used over and over to create new projects. The goal is to save time by using company standards, enabling you to concentrate on the design. For example, if you do a lot of standard mid-rise buildings you can preset typical levels (as shown below) along with the related Floor Plans, Ceiling Plans, and/or Structural Plans. (If you are copy/monitoring levels through a linked file you do not need additional levels in your template file.)

1a-additional levels

Some items in a project template include:

  • Levels
  • Project-based settings (e.g., Project Units, Object Styles and discipline-specific settings, etc.)
  • System Families
  • Component Families
  • Annotation Types
  • Sheets with associated title blocks
  • Views, and View Templates and View Filters
  • Schedules and Legends

Resource Projects

A resource file is used to add views and elements to the current project after it has been started. You may have more than one resource project. For example, you may have a project that includes specific wall styles and wall details (as shown below) that you use for custom house design and a separate resource project for all your landscaping needs.

1-wall detail library

Some items in a typical resource file include:

  • Sheets
  • Schedules
  • System Families
  • Component Families
  • Drafting views (details)

How do you use Resource Projects?

There are several tools you can use to access information stored in resource projects. It depends on the type of element you need to add.

  • To copy drafting views (details), sheets, schedules, or reports into the current project, use Insert Views from File. You will select a project to open within the process and then you can select from a list of the available views and sheets as shown below.

1a-insert views

  • To copy system families (e.g., wall, floor, duct, pipe, wire types, etc) or annotations (e.g., text and dimension styles, materials, etc.), use Transfer Project Standards. A project has to be open to use this tool. Check None is an important button here as you rarely want all the settings imported.

1a-transfer text and dim

  • To copy component families from a resource project, use Copy to the Clipboard and either Paste Aligned to Selected Levels or Paste Aligned to Selected Views. For example, you might have a sheet full of schedules, as shown below, in the resource project that you can then select from to copy and paste into a sheet in the current project.

1a-temporary schedules

Questions?

What do you need in your template files and resource projects? Share your favorites in the comments below.

And look out for our upcoming version of the Autodesk Revit BIM Management: Family and Template Creation learning guide due out in early autumn.

Previous Article
Marking Up InfraWorks Models
Marking Up InfraWorks Models

Considering the fact that Autodesk InfraWorks does not have a print function, most people think that they c...

Next Article
5 Situations to Consider when Planning your PLM eLearning Projects
5 Situations to Consider when Planning your PLM eLearning Projects

When planning your next PLM eLearning project as part of a PLM software implementation, below is a list of ...

×

Sign up for email updates

First Name
Last Name
Country
Thank you!
Error - something went wrong!