![revit project template upgrade revit project template upgrade](https://www.nationalbimlibrary.com/Content/images/ContentPages/revit-templates-head.png)
If majority of your company projects have long design and construction periods. Yours would vary depending on the local industry you are in and the type of projects you engage in. That's just our approach for your reference.
![revit project template upgrade revit project template upgrade](http://www.garethspencer.com/wp-content/uploads/2021/01/RVT-ApplicationMenu_001.png)
#REVIT PROJECT TEMPLATE UPGRADE UPGRADE#
The plug-in also handles the batch library upgrade every 3 years. The plug-in upgrades the specific family we need for the project as we drag and drop from its interface into the project. The families are kept separate from the project templates and managed via a third party content management plug-in. Any new content created for the legacy library will be upgraded afterwards to the current library. A backup database of superseded library is saved elsewhere for the rare use on legacy projects. We upgrade the library once every 3 years (upgrade to the oldest supported version in Autodesk's current project cycle). Else it starts to get too messy for us when we have multiple content creators across different Revit versions for different projects. We create and maintain one library for one Revit version at a time only. I only load about 60% of our content into our project templates to try to keep it a little leaner. In the old library location I put a Read Word Doc called, Where did all the content go? and it has the instructions to open the All Content template and take what you need. But I leave the main revit 2018 library folder there empty so staff dont get a path not found error when they open revit. I do a save as, and name the template "All content_2018.rte" and delete the old content from the 2018 library locations. I take our standard project_template.rte file and load everything from the 2018 directory in it. I dont get worried about a few not upgraded families floating around, every year I just re-upgrade everything and its good enough. The I basically save over the 2019, 2020, 2021 directories and create a new 2022 folder and paste in there as well. At that point, I will review my 2018 library for consistency, its just a quick check. Every August I end up building the new library for the next release. If i make a light fixture for a 2021 project, I make it in 2018, copy/paste to 2019, 2020, 2021 directories and load it into their project for them. In general for upgrading families throughout the year, I dont. Now they can find what ever they need and load it into their project, save it to desktop, etc. If someone needs content for an old 2016 project, they open revit 2016, browse tot he templates and select the "all content" template. I load absolutley everything into a new template and call it "All Content" as opposed to "x_project template" and delete the library from the network. The result is staff get a library that has content for all versions and the families are exactly the same for each version and each folder.Įvery year I "archive" the old content so it is still available.
![revit project template upgrade revit project template upgrade](https://i0.wp.com/revitiq.com/wp-content/uploads/2016/07/RT_screenshot_20160712_155446.png)
and knowing that Im going to save over everything every summer forces me to work in the lowest version or I will loose my own work. Going through the exercise of syncing the libraries before creating a new version helps maintain consistency between families. This summer I will review my 2018 library, copy it over my 19, 20, 21 folders and create a new 2022 folder. So each year I roll out a new release of revit, review my last previous version, i.e., 2017, make sure its in good shape (no duplicate files, typos, etc.) and copy paste to my new folder 2018. When im finished making/editing something in 2018, I will copy/paste it into my 2019, 2020, 2021 folders, upgrade the file and be done. I work in the lowest supported version, so that staff with older projects get newly created content.
![revit project template upgrade revit project template upgrade](https://www.caddmicrosystems.com/blog/wp-content/uploads/2019/10/cover-image.jpg)
I support current and three previous versions, as autodesk does.