Issue:

• The shared file is unavailable for linking.
• The shared file is not the current file.
• The ACC/BIM 360 dashboard displays errors stating that the folder is unavailable.
• The shared project file size does not match the file size on Document Management.
• Users are confused about the difference between consumed and shared folders.

Causes:

The issues listed above have various causes. However, most of the issues encountered in ACC/BIM 360 are due to a lack of understanding of how Design Collaboration works. This cheat sheet will explain the Design Collaboration workflow from setup to practical use, which will help users troubleshoot these issues.

Solution:

Design Collaboration has two model sharing methods, each with its own pros and cons. Before choosing which approach to use, we need to go over the requirements for Design Collaboration.

Requirements:

• Design Collaboration Pro: Enables collaboration on Revit in cloud environments with others. This subscription also includes a Docs subscription.
• Docs: Access to Autodesk Construction Cloud Docs dashboard requires a Docs subscription for all users who need access to the dashboard.

• All file sharing between team members happens inside Docs online. 
• The Revit file uploaded in Docs is not the same as the Revit file shown in the Revit Home Screen (CTRL+H). 
• Publishing a file from Revit is required to update the Revit file in Docs

File Sharing Workflows:

1. Package/Consume Method:
   • Pros:
     1. This is the best example of a controlled model file sharing process.
     2. Each team can control the schedule of updating the background file.
     3. Able to display federated model limited to only consumed model in the Design Collaboration module.
     4. Able to track which models have been consumed and not consumed by teams in chronological order.
   • Cons:
     1. The process of sharing and consuming packages can be convoluted.
     2. There is a chance that a team may not work with the latest updated reference due to human error.
   • Process:                                        
     1. Publish the Revit model either from Revit or using the Design Collaboration Auto Publish feature.                                                
     2. Create a package using the published model and share it in the Design Collaboration Module.                                                   
     3. Consume the package from other teams that were updated on the timeline in the Design Collaboration Module.                    
     4. Sync the Revit model, and all links that path to the team's consumed folder will be updated. 
2. Package Sharing Method:
   • Pros:
     1. It removes the need for teams to consume packages.
     2. The referenced Revit models update automatically as soon as the package is shared.
     3. All teams will look at the same reference models.
   • Cons:
     1. It is not possible to see the federated model in the Design Collaboration Module.
     2. Links update as soon as the package is shared, so there is limited control over the links.
   • Process:                              
     1. Publish the Revit model either from Revit or using the Design Collaboration Auto Publish feature.                                                
     2. Create a package using the published model and share it in the Design Collaboration Module.                                                                                        
     3. Sync the Revit model, and all links that path from the shared folder will be updated. 

About the Author

Sr Technical Support Specialist<br><br> Skilled in AutoCAD, Mixed-use, Renovation, Revit, and Sustainable Design. Strong arts and design professional with a BA in Urban design focused in Architecture from University of Washington.

Follow on Linkedin More Content by Gregory Lee