Autodesk Construction Cloud bridges establish data links between different projects (possibly on different hubs) but on the same geographical Amazon Web Server.
There are different bridges that can be created within the Autodesk Construction Cloud. It depends on whether you’re using the Docs, or the Collaborate Pro subscription and their purposes differ.
For instance, a Docs bridge might be appropriate for Autodesk Takeoff to leverage a specific catalog standard (Takeoff allows for a primary and secondary standard and cannot accommodate multiple standards for multiple companies). Each company that needs to do a takeoff according to their own classification standard must therefore create a bridge.
The Bridging of Teams using Collaborate Pro is different. The purpose of creating the bridge might ultimately just come down to the trust that is invested in the Project’s Administrator (who can see and access EVERYTHING). To protect a hub’s intellectual property, only the relevant information can be shared out in Team packages and Docs bridges. This would make probity agreements irrelevant and take some risk out of the system.
To set up bridge team automations, you must have a bridge between your projects first. The invite goes out from the project into which a team will be shared. The member who does the inviting must have Administrator rights to grant access. The invited member gets an email. They get to choose which project must be bridged from the projects they are administrators of.
Once the projects are bridged, the team may be bridged. The sharing of a package now shares from one project to another.
If you need help adopting the AEC Collection or the Autodesk Construction Cloud in your practice or you are looking to invest in hardware, please contact Micrographics so that we may be of assistance.
Still looking for answers? Start a discussion with other professionals in your industry!
