Community
@Anonymous thanks for your feedback. Perhaps I can provide some context on the Autodesk side historically that will add to the discussion.
First, just to be sure I understand what I think you are saying, you would prefer to see the live model version in the Document Management module. So, if you had 100 Sync with Central (SWC) on the model that you saw in the version history within Manage Cloud Models, you would see 100 versions on the web site in the Document Management module under your team folder. Since that team is always working with the latest in Revit, the thought would be to always see the latest in your team folder.
There are a couple concepts from our side that are loosely tied together. First, there are people on the project who are not necessarily going to be in Revit. So, the web portal is a way for non-Revit users to see/review models that are being worked on. Second, not every SWC is significant from a review standpoint. A team may have 5 people working on a model and they all perform multiple SWC throughout the day versioning the model 25-30 times throughout the day. Are all of those versions going to be reviewed or perhaps just some of them? Finally, from the translation standpoint, there is an expense for each version being published. From the customer side, that expense is time and creating 25-30 viewables for each model in the project could become time consuming, when it's really just one specific version that a team may be interested in reviewing.
So, with that context we landed on seeing the live SWC versions in the manage cloud models dialog within Revit. When you open a model you are always getting the latest and greatest. If you want people on your team, but who are not using Revit to see a specific update, you publish the model where they can see that version on the web site. If you want people outside of your team to be able to view and/or link to a specific version of the model the new Design Collaboration module gives you the chance to create a package with that model/sheets/views included. In this way, the significant versions are shared out and viewed without the overhead of every SWC getting a view-able on the web site.
I hope this help clarify how we got to where we are. I think your idea of a flowchart is really good and I'll try to put something together that visually represents all the options. Also, while you didn't mention it, we've gotten a lot of feedback on scheduling the publishes which could save some time on your end. Do you have some thoughts on that as well?
Thanks again!
Adam Peter
Customer Program Manager
Autodesk
@Anonymous thanks for your feedback. Perhaps I can provide some context on the Autodesk side historically that will add to the discussion.
First, just to be sure I understand what I think you are saying, you would prefer to see the live model version in the Document Management module. So, if you had 100 Sync with Central (SWC) on the model that you saw in the version history within Manage Cloud Models, you would see 100 versions on the web site in the Document Management module under your team folder. Since that team is always working with the latest in Revit, the thought would be to always see the latest in your team folder.
There are a couple concepts from our side that are loosely tied together. First, there are people on the project who are not necessarily going to be in Revit. So, the web portal is a way for non-Revit users to see/review models that are being worked on. Second, not every SWC is significant from a review standpoint. A team may have 5 people working on a model and they all perform multiple SWC throughout the day versioning the model 25-30 times throughout the day. Are all of those versions going to be reviewed or perhaps just some of them? Finally, from the translation standpoint, there is an expense for each version being published. From the customer side, that expense is time and creating 25-30 viewables for each model in the project could become time consuming, when it's really just one specific version that a team may be interested in reviewing.
So, with that context we landed on seeing the live SWC versions in the manage cloud models dialog within Revit. When you open a model you are always getting the latest and greatest. If you want people on your team, but who are not using Revit to see a specific update, you publish the model where they can see that version on the web site. If you want people outside of your team to be able to view and/or link to a specific version of the model the new Design Collaboration module gives you the chance to create a package with that model/sheets/views included. In this way, the significant versions are shared out and viewed without the overhead of every SWC getting a view-able on the web site.
I hope this help clarify how we got to where we are. I think your idea of a flowchart is really good and I'll try to put something together that visually represents all the options. Also, while you didn't mention it, we've gotten a lot of feedback on scheduling the publishes which could save some time on your end. Do you have some thoughts on that as well?
Thanks again!
Adam Peter
Customer Program Manager
Autodesk
Accepted solution
@Anonymous wrote:
Hi Peter. I agree with that work flow. It does make it easier to manage non revit users having a visual aid at a set period.
Just a question with regards to consumed models. At the moment reloading links takes a decent amount of time (I live in New Zealand so our Incoming line isn't the greatest) Currently the compare tool is able to see changes from one version to another. So in the background there must be data being compared. Is there no way that after hitting consume, when a user presses sync in revit that just the actual changes could come through? Instead of it reloading the whole model. Again I might be wrong in this. I've just noticed it still takes a considerable time
Cheers
Robin,
What you ask for is actually what is happening, at least in terms of the data transfer. Let me explain a bit further.
When the "Consume" button is pressed in the Design Collaboration UI, this updates the version of the cloud workshared model in the Consumed folder. The next time that a member of the team chooses to load that link - either via "Reload Link" in the Manage Links dialog, or loading the host model - then only the updated data is actually downloaded on the team member's workstation. The entire RVT is not downloaded.
In the case that the link is already loaded, and the team member hits the "Reload Link" button, then Revit merges the downloaded "delta binaries", and then regenerates the implications of those data changes. In the event that the host model is being opened, then the full linked model is loaded, and regeneration is carried out for any implications on the host model, on account of the new changes in the linked model.
-Kyle
Kyle Bernhardt
Director
Building Design Strategy
Autodesk, Inc.
@Anonymous wrote:
Hi Peter. I agree with that work flow. It does make it easier to manage non revit users having a visual aid at a set period.
Just a question with regards to consumed models. At the moment reloading links takes a decent amount of time (I live in New Zealand so our Incoming line isn't the greatest) Currently the compare tool is able to see changes from one version to another. So in the background there must be data being compared. Is there no way that after hitting consume, when a user presses sync in revit that just the actual changes could come through? Instead of it reloading the whole model. Again I might be wrong in this. I've just noticed it still takes a considerable time
Cheers
Robin,
What you ask for is actually what is happening, at least in terms of the data transfer. Let me explain a bit further.
When the "Consume" button is pressed in the Design Collaboration UI, this updates the version of the cloud workshared model in the Consumed folder. The next time that a member of the team chooses to load that link - either via "Reload Link" in the Manage Links dialog, or loading the host model - then only the updated data is actually downloaded on the team member's workstation. The entire RVT is not downloaded.
In the case that the link is already loaded, and the team member hits the "Reload Link" button, then Revit merges the downloaded "delta binaries", and then regenerates the implications of those data changes. In the event that the host model is being opened, then the full linked model is loaded, and regeneration is carried out for any implications on the host model, on account of the new changes in the linked model.
-Kyle
Kyle Bernhardt
Director
Building Design Strategy
Autodesk, Inc.
Hi @Anonymous,
If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.
Thank you and have a great day!
Anil Mistry
Technical Support Specialist
Hi @Anonymous,
If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.
Thank you and have a great day!
Anil Mistry
Technical Support Specialist
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
