Prior to the new Revit Server, all worksharing in Revit was file-based. When worksharing was enabled for a project to allow multiple team members to work with it, a central file of the project was automatically created on the LAN (local area network) of the office, and it worked as the master copy, storing the current ownership information for all the elements in the project and acting as the distribution point for all changes published to the file. All users worked on a local copy of the central file, made edits to their local copy, and then synchronized with the central file to publish their changes to it. Revit’s transparent element borrowing feature made collaboration easier by automatically assigning ownership of an edited element to a user, which was then automatically relinquished when the user saved their local copy back to the central file.

Worksharing in Revit, worked well when all the team members were in the same office and only needed to work with the model on the LAN; it was when teams from other offices needed to work on the same model that collaboration became problematic, as they were now required to access the central model across a WAN (wide area network), which was noticeably slower. Contrary to the popular assumption that this latency was caused by Revit’s large file sizes, it turns out that this was actually due to the communication protocol between the central model and local copies, which, according to Autodesk, was not optimized and too “chatty.” After the local copy is first created from the central model—which will, of course, take a longer time for larger files—subsequent saves and reloads to and from the central model transmit only the changed model elements back and forth and not the entire file. At this point, therefore, the file size is not a factor—the latency problem caused by the non-optimized communication protocol would be of the same magnitude, irrespective of the size of the file.

The newly introduced Revit Server technology addresses the WAN latency problem through some key new features and changes. To start with, it is introducing the concept of a Central Server located in any part of the world, where the central Revit models of projects would be stored, and Local Servers at each of the office locations, which maintain copies of the models that users in that office are working with. Users will now need to access the Revit model only across a LAN as it is stored on the Local Server, avoiding the latency problems that existed earlier when accessing models across a WAN. At the same time, in the new scenario, the Central Server and the multiple Local Servers are being constantly synchronized to ensure that changes made to the local models are updated in the central model, which are then, in turn, updated in all the Local servers in different locations. Also, even though the synchronization between the Central and Local servers is happening over a WAN, it is using new communication protocols that are much faster than the earlier non-optimized protocols, ensuring that the central and local models stay constantly synchronized. (Of course, if two users save their changes at exactly the same time, there will be a temporary asynchronization.)