Eliminate the need to Publish Revit Models to my own Team

[rick_notari]

What is the purpose of publishing a model to my own team? Why not allow members of my own team to view the live models in the Docs viewer.

The publishing process could be reserved for milestone records, while still maintaining a publish set so Revit users can choose which views and sheets are visible in the viewer. The ability to share models with broader teams/disciplines, for coordination workflows in BIM Collaborate Pro or asset workflows in Autodesk Build can still remain, to ensure appropriate levels of control and accountability. 

Publishing large models can take an excessive amount of time and sometimes fail altogether, which isn’t practical when working to tight deadlines. Eliminating or revising this workflow would save the end user a lot of frustration.

[Chad-Smith]

I understand and appreciate what it is that you are requesting. Having to publish frequently, and the time it can take to finish can be time consuming.

I think this is just a symptom of needing to translate a data dense authored Revit model file into a lightweight format that can be viewed in the browser. And given the potentially excessive time it can take, then ACC can't be publishing the model every time a Revit user synchronises their changes.

I suspect the best we could hope for under the current process is for our internal models to be published on a daily basis - overnight. This way the internal team has refreshed model data at the start of every day.

But I also hold out hope that the recent announcements from Autodesk about the evolution of design via Forma may open opportunities to alleviate the heavy server load of data translation by instead working as native data regardless of whether you are in Revit or ACC. I'm hoping this will completely remove this need to publish. We'll have to wait and see.

[rick_notari]

@Chad-SmithThanks for the comment! I understand what you’re saying, and that thought did cross my mind.

Perhaps it makes sense for the first publish, but is it really necessary every time? Surely only updates from the previous version could be published. I'm not sure what happens at the backend (that's above my paygrade), but from my experience working in the reseller space, this isn’t just my frustration, it’s something many of our clients share as well.

Hopefully this is in Autodesk's strategy moving forward with the evolution of working in Forma.

Have a good night!

[Susana_Duarte_LMSI]

The publish to ACC workflow is needed to be able to do compares. We would not want a version up for every move a user does.

Those publishes can already be automatic in the time frame you need (daily or weekly). What we need is the publish to stop be with links or without links. It should be both, so that revit/ACC could use the apropriate one when needed (bridge models need without links, ACC with links, downloads may need both as per need). Please make this improvement ASAP. Thank you.