cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Design Collaboration should not require RCW to track changes

Design Collaboration should not require RCW to track changes

Sometimes the GC wants to utilize Design Collaboration to track design changes between disciplines however, in most contractual situations, the architect hosts the model and therefore is the owner of the hub with all RCW models. Since RCW can only happen on one hub, the GC can't use Design Collaboration to track changes. The GC receives weekly model updates through file share. They should be able to drop the models into "Teams" in Design Collaboration and track changes. However, this can't be done without RCW. Currently GC's need to use a combination of Assemble to track 3D changes and Document Management to track sheet/2D changes. Its cumbersome and inefficient. 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea