Revit Model Workflows - Updating and Publishing

[HGC-Jchandler]

We are a GC, regularly receive design Revit models for coordination. 

We have 2 options, neither are great. Wondering if anyone has found other ways to skin the cat. 

Option 1 - Save design Revit models as cloud models. 

The good - can publish views from federated model for model coordination, estimating, etc. 

The bad - if/when we get revised models from the design team, we have to change the name or remove the original model and replace it with the new model which is time consuming and removes version control. 

Option 2 - Use the Drag & Drop method to upload design Revit files to BIM 360 & link through desktop connector.

The good - revised design models are easily updated and versions tracked by dragging & dropping them into B360

The bad - published views for coordination/estimating do not show models linked through desktop connector. 

Are there other methods available or is this it? Thanks!

[gareth.spencer1]

Hi @HGC-Jchandler ,

The problem you have here is if you need to see specific views or elements in consultants model each time, they share a copy you are likely to receive it in the same way. ie. wrong views, families turned on or off, etc. 

Have you asked them when sharing they need to publish specific views and make sure the correct families are visible at the time of sharing? 

You mention you are coordinating models. Are you using BIM Collaborate for this?  

[PatrickDavis20]

Those are the basic options. If I was in your shoes, I would define what I am trying to get out of the models, the time it takes you to condition/setup new or updated models, and then determine the value.

My approach is a twist on Option 2. I prefer to set up a container file and link in all my other models. When I get updated, then I replace the file. I keep the same file naming. Version control/management is handled by simple text editing on the Home screen in the container file to track when a file was updated.

Cloud models are great, except if you are not part of the original cloud model team. If someone is sending you updated models, then you have to swap them out and as you said, it takes time. And version control is a lower priority is you are working smart.

I also like to use Autodesk Assemble. If someone is opening Revit just to look at a schedule, I would rather then open up Assemble and get that information there. They can also condition the data as they see fit and in many cases, those changes will be retained with model updates. 

Hope this was helpful.

[HGC-Jchandler]

@gareth.spencer1 I think you are suggesting that the consultants models should be dragged and dropped, either into estimating or coordination spaces and we should work with the consultants to get the appropriate views setup. And in a perfect world I would certainly agree.  Unfortunately the time it would take to get the information needed, assuming the consultants were willing, is prohibitive. Even more so I prefer they be focused on RFIs & submittals, or furthering the design more so than perfecting views for downstream use. 

[HGC-Jchandler]

@PatrickDavis20 Appreciate your insight. I lean towards option 2 as well however there are cases where the number of updates becomes an issue.

And yes, agree we manually version the cloud models by name and move them to an archive folder. Each time I do it though, I look at the little v2 next to the file name box that should automatically update and shake my head. 

One rather significant drawback to option 2 is the inability to use the compare versions tool. We'll often drag and drop into a separate folder just for that functionality. 

[gareth.spencer1]

Hi @HGC-Jchandler ,

No sorry I was not suggesting any of the two options. Just merely trying to understand what you trying to do here and then give you a few ideas how best to do things.

Does your consultant have access to Docs? or are they just sharing the files with you by other means? ie project CDE, WeTransfer, etc. Which means you then need to upload them to your Docs project.

If they don’t have access to Docs, why don’t you see if they have a license then they can simply upload directly saves a little bit of time in the process. If they are using, then it should be straightforward in my option, but I am not working on the project.

When receiving files sent to you is there no protocol on the file naming outlined. That everyone must follow? I would always keep a record copy of any incoming files (drawings or models). Then have clean copy which I keen up and link in which has the same file name. It does sound like you are receiving updates often. How often are you receiving updates?

If files are dragged and dropped into Docs, it will save the next version unless the file name is different. The only reason you cannot compare would be if the version of Revit the file was created in is different.

You are always going to get the same problem with the published views not being correct and updating linked files when receiving new models for a third party. It does not matter if you are using ACC/BIM or saving locally on your server.

I was going to suggest the same as what @PatrickDavis20 mentioned in his post about having a container file to link all models into.

Good luck in what you do anyway.

[HGC-Jchandler]

@gareth.spencer1 Thank you for the response. I think we are all saying very similar things with slightly different lingo. 

One point of clarification - the majority of the time, we (the GC) receive a transmittal from the design team in which the architect compiles their model and their consultants models at a predetermined milestone, often CDs. There are some less common cases where we operate in more of a design-build capacity, but for the sake of my original post this is referring to those Design-Bid-Build environment data transfers. We (the GC) have no involvement in file naming/setup/views/softare/versions/etc. during the design phase and often have to beg and plead just to get the models period. 

"When receiving files sent to you is there no protocol on the file naming outlined. That everyone must follow? I would always keep a record copy of any incoming files (drawings or models). Then have clean copy which I keen up and link in which has the same file name."

We have a file naming convention for files that are originated by us or files that are originated by others but then modified by us. Yes - We keep a record copy of all files sent or received and then a copy of the original is used for it's intended purpose so that, as you mention, there is always an original. 

"It does sound like you are receiving updates often. How often are you receiving updates? " 

It varies from project to project from zero updates to double digit updates. 

"I was going to suggest the same as what  @PatrickDavis20 mentioned in his post about having a container file to link all models into."

I didn't explain this well enough in my original post. On our end, federated model = container model. We are using "container models" in both scenarios. The main problem we are running into is when we drag and drop the design teams Revit models into ACC/BIM 360, and link them into a container model, is the linked models do not show up in views published from the container model. This matters because there are other processes that utilize the published views like estimating/QTO tools and model coordination. The alternative is to setup the design team's models as cloud hosted models which when linked into a container model will show up in published views from the container model however this workflow removes the versioning and model compare capabilities.