Revit Server or Collaboration for Revit (C4R)? Revit Server or Collaboration for Revit 14-11-17 | Page 5

Financially, the ROI from C4R projects saves an average of 30 minutes per individual team
member every week. Over the course of an entire year, this could mean that C4R can
virtually pay for itself.
Technical Issues and How Autodesk Supports C4R:
Bottlenecks in the code, capacity scaling under varying load, intermittent connectivity -
Product teams across the cloud ensure that services have the right approaches and
architecture to carry out their operations consistently and with high levels of reliability.
Degradations or outages - Services are designed so that dependencies are ‘soft’ and don't
bring down core products.
Deviation of operational behaviour - Services are constantly logging operation results for
‘health checks’. Notifications of deviation of behaviour occur within minutes and can be
rectified quickly. In addition, data trends are studied for usage patterns to improve capacity.
Overall, both Revit Server and C4R work-sharing methods have advantages and downsides,
but depending on the organisation concerned and its specific needs, one may be more
useful over the other. However, with the increased shift to subscription-based software
licensing, C4R may be seen as the logical way forward for many firms that have not already
invested in costly Revit server hardware and require easy to use and easy to operate cloud-
based solutions for collaborating on their projects.