Hold Off Warning Rescinded

Kyle wrote in a more recent reply:

The Cloud Worksharing reliability issue associated with the Revit 2016 UR4 update has been resolved. The issue was resolved on the service itself, so no updates to the downloadable files were required.

Teams are encouraged to download and install the latest update, as it contains valuable enhancements to reliability and workflow.

Hold off on Revit 2016 Update Release 4

If you are using Revit 2016 and Collaboration for Revit (C4R) then you'll want to hold off installing the most recent update. Kyle shared the following in a post at RFO.

We have identified a compatibility issue with the latest Revit 2016 UR4 update, which is causing degraded Sync with Central (SWC) reliability for those that installed it. We have confirmed this issue internally, and are working to resolve the issue within our services.

Teams are advised to defer installing the latest Revit 2016 UR4 until we have resolved the matter on the Cloud Worksharing service. We apologize for the disruption this may be causing, and are urgently working to resolve the matter.

Upgrade Projects from 2015 C4R to 2016 C4R

The Revit Clinic offered a post describing the steps to move a project from 2015 to 2016 versions of Collaboration for Revit. It isn't as straight forward as we might think. It isn't as simple as opening a 2015 project via A360 with 2016 and waiting for it to be upgraded to 2016.

Take these steps:

• Open Revit 2015 (with C4R installed)
• Browse to the A360 project that you want to upgrade
• Open each Revit model and save it to your local workstation
• Create a new project to be used with A360 Collaboration for Revit 2016 in your A360 team hub
• Open Revit 2016 (need C4R installed for 2016 first of course)
• Open each Revit model that you saved to your local workstation save it after it upgrades to 2016
• Initiate Collaboration on each model and specify the 2016 project name that was created on A360 earlier
• The model is associated with the new A360 Collaboration for Revit 2016 project
• Re-link any Revit models as required
• Let everyone know that they should use the 2016 project now

There are now two separate and distinct projects (2015 format and 2016 format). Everyone must use the upgraded (2016) project and models now. Remember to rename the 2015 version of the project or deactivate it via A360.

Revit 2016 - Collaboration for Revit 2016 is Available

The 2016 version of C4R (Collaboration for Revit) is available now.

Click this to download or click the image for an overview

You'll need to visit your Subscription page to access the download to install it. Look at the Services page and it should be listed among whatever services you are entitled to. If you don't see it then you'll have to sort out your A360 account first.

This is the video they offer at the online help documentation site to explain how to initiate a project with C4R

Shared Coordinates and Collaboration for Revit

I've not written anything about Collaboration for Revit (aka C4R) yet. It's a recent development that puts a project in the cloud to give a project team access to the project data regardless where they are.

When it comes to Shared Coordinates, the Publish Coordinates tool is disabled. Acquire Coordinates does work.

As I understand the issue, Publish Coordinates is the only time that Revit has to be able to write changes to a linked file. The current A360 and C4R infrastructure doesn't support allowing that to happen...yet. They do understand it is something we want and need to do.

Regardless I'd still use Acquire Coordinates on a source survey file within a Master Site file, as usual. Then I'd link any building files and position them on the site, just like I'd normally do. To cope with the loss of Publish Coordinates I'd put location markers (a unique family for example) that allow me to figure out how to link and align Master Site in each building correctly afterward.

As I just mentioned, in each Building file I'd link the Master Site model and move, rotate and elevate it as required. Then I can use Acquire Coordinates and pick Master Site. This will pull the correct Shared Coordinates into the building model. I'd repeat that for each building.

I'd do the little building position dance in Master Site even though I could probably figure out how to do the reverse (position Master Site in each Building) somehow. I'd find it a little easier to work out each building's relationship to the Master Site model this way, seeing them all together at the same time in Master Site. I think it provides for better context.

When other trades get going they just need to link the Architecture model using Auto - Origin to Origin and then use Acquire Coordinates, picking the Architecture model. It's a cascading nested understanding of the survey coordinates, using Acquire Coordinates all the way down.

SMEP-Models - AC from - A-Model - AC from - Master Site - AC from - Site Survey

When they return their files to the architect they just need to be linked using Auto - Origin to Origin too. Technically if they do use Acquire Coordinates using By Shared Coordinates would work but if they didn't Auto - Origin to Origin is reliable...as long as they understand it is important that they start out using Auto - Origin to Origin themselves, when they link the architecture model.