In this comparative blog we investigate the top ten differences between Autodesk Docs and Autodesk Collaborate. We specifically steer away from Collaborate Pro to show that there is value to consider in a subscription instead of Autodesk Docs.
In a later blog we shall compare the differences between Autodesk Collaborate Pro and Autodesk Collaborate and make the case for those that would like to unlock the co-authoring capabilities of Collaborate Pro on the cloud with reference to various Autodesk authoring platforms. Note: even when just one Autodesk Collaborate license is used to host the project there are still advantages for Autodesk Docs subscribers to gain benefit from.
Clash detection traditionally saves 1/5 of the construction project cost and is the easiest argument to make for adopting Autodesk Collaborate instead of Autodesk Docs.
Automatic clash detection in the Autodesk Construction Cloud is a capability that I’ve seen teams that are familiar with the alternative, Navisworks, adopt eagerly. We usually recommend that the shared folder is clash detected as a heads up assisting in the consumption of packages, and a formalized clash detection folder typically run by an expert in the Architectural team who then assigns clash issues do those responsible for remedial action.
Care must be taken at the beginning of the project to understand all the different file types that will be incorporated because there are limitations on the types of files that can be clash detected on the Autodesk construction cloud. Should the files fall outside of the capability of the Autodesk Construction Cloud, then Navisworks must be used.
The creation of Teams in Autodesk Collaborate is the equivalent of creating a work in progress silo within Autodesk Docks. The big difference between Autodesk Docs and Autodesk Collaborate in this regard is that Teams automate the creation of sharing protocols which we will shortly discuss.
3. Bridge teams across from other hubs (regardless of server location).
There are a few scenarios in which I can see the bridging of teams across from other hubs to be advantageous. These hubs may be hosted in the USA, the EU or Australia.
Quite often we work with collaborators from around the planet and managing the administration of their teams is onerous as a quick response relies on the working hours of the geographic region they are operating in (it is difficult enough to schedule design meetings, never mind ad-hoc admin requests). Bridging the team in from their hub gives them administrative responsibility and frees up our ability to collaborate across time zones.
Teams that perform model takeoffs would be interested in using their own catalog schedule. Unfortunately, each project only allows one set of classification systems. When you bridge teams in from other projects you can overcome this limitation. It should be considered that every team that performs takeoffs should run their own project from which they remote in. that could even be on your hub.
4. Share and Consume Packages.
Sharing and consuming packages helps aligning the project with UK BIM Level 2 Compliancy. In essence the principle is that the sharing party vets the data that they share. The consuming party then first engages in a multilateral vetting process before accepting the data. The big advantage of this is that the consuming team has an opportunity to object to the data in case they spend time and money operating on data that is not acceptable from the perspective of their own leadership.
This process is concluded on a time-liner which gives a visual que to the availability of newly published packages. A copy is made of the work in progress file. This copy then serves as the one version of the truth, and when consuming, this is once again copied into the consuming party’s silo. This siloed consumed file copy they have complete control of. Should a dispute arise around the nature of the consumed file, the original (shared) one source of truth serves as a reference which can be introduced in litigation. The one version of the truth maintains its history by virtue of being versioned.
The sharing and consumption of packages may be subscribed to, and the management of these notifications can be routed using rules within your e-mail application.
While you can compare files in Autodesk docs, Autodesk Collaborate allows you to compare models and sheets before consumption. Not only does this give you a heads up on what the other teams were working on before providing you with the new models and sheets, but it also makes it possible for you to make informed decisions on whether the data is reliable.
Later, we will see that clash detection is also available in Collaborate. Were the shared folder (unilateral) clash detected, this would even give you a heads up on if there were any clashes that might impact the project, and this change in clash status will also inform your decision to accept the incoming data.
6. View Federated Project Model.
Models that are uploaded to Collaborate are automatically federated and can be switched on or off to enable the viewer to do a constructability walkthrough. This allows us to create issues where necessary and assign them to the relevant parties for action.
Often the federated model consists of an enormous amount of data that could never be aggregated within one authoring platform (for instance Revit). An alternative would be to use Navisworks, but the automatic nature of the cloud is a huge advantage.
7. Hypermodel.
Hypermodel navigation is only available for newly published data and allows you to produce the 3D model with reference to a 2D sheet. You would need to publish the sheets with the model within the Revit authoring platform. In essence if you place your view tool in a 2D sheet view that is not split it will apply the crop to the 3D model and therefore navigate you to the geometry of interest.
8. Save Clash Views to Docs (mimicking the federated model).
If the project has Autodesk Collaborate enabled, 3D clash views can be saved onto the Autodesk Docs platform for users to navigate in a Federated format within which individual models can be switched on and off as required.
With Autodesk Collaborate comes the ability to track correspondence. The easiest way in which this can be done is to use the e-mail address generated for the project and to include that in e-mail correspondence and replies and to record that for future reference. Correspondence is recorded regardless of whether the originator is a subscriber to any Autodesk construction cloud license whatsoever. This is sometimes a deal breaker to subscribe to Collaborate instead of Docs.
10. Meetings.
Meetings can be hosted on the Autodesk construction cloud when you have Collaborate. You may even generate an online link for platforms like Microsoft Teams then record and transcribe the meeting and upload the recording and transcription for future reference. That is besides making notes within the meeting and assigning tasks and attaching documentation for follow up.
Investing in the Autodesk Construction Cloud is a good idea. Many have the Autodesk Docs license by virtue of having subscribed to the Autodesk AEC Collection. However, as much as the Docs subscription adds to value to the design process, the Autodesk Collaborate subscription benefits the project more, and might be important enough to invest in from a cost/benefit perspective.
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!
