Revit Server Workflow 2015

[Anonymous]

Hi sgoodmansen,

Thanks for the confirmation that my work place is using a File-Based topology which is also what I had thought with a 90% confidence. After my company had failed to meet a project deadline through worksharing collaboration of using Revit 2015. I start to wonder if the established Revit Server workflow is really effective for wide geograhic distances. After I read this article attached below, I generally understood the benefits of using the Revit Server accompanied by Riverbed accelerators for two fundamentally different workflow topologies : Server-based and File-based. The tests performed in the article clearly indicates that Server-based topology delivers the greatest overall performance which minimizes the WAN traffic with the least amount of time required to perform Sync w/ Central, Reload Latest, Element Borrowing and Element Relinquish than File-based topology, despite the fact that network compression with Riverbed accelerator is more effective for File-based workflow.

I just like to know what are the drawbacks of using a Server-based workflow which is not the current workflow topology being used by my company. If considered, would this be more appropriate than File-based workflow for documentation worksharing across three geographically long distance locations ?

Also, I just want to get some clarification about the "Local Revit Server". I know for sure that all the central files are stored on the web-based file server (see attached screenshot with the server circled in red). All the locally saved Revit files are backed up in the Documents folder under the C: Drive, and the cache contents are all defaulted to C:\Users\username\AppData\Local\Temp. But there is no Central Revit Server in this case, because it is a file-based workflow which means that no Local Revit Server should be used or connected to the Riverbed accelerator across the WAN, correct ? The only time when Local Revit Server/Servers can be used is in the scenario of a Server-based workflow, such that the Local Revit Server (a physical piece of hardware/ machine) must run in parallel with an accelerator per geographic location and using only the Local Revit Server instead of the accelerator to cache data within local area network (LAN). There would also be a Central Revit Server( a physical piece of hardware/machine) residing at one of the geographic locations, but the central models/files are stored across the WAN, not on the central server, correct ? Sorry for asking many the questions at once, I hope my questions are clear and easy to understand. Thank you.

[Anonymous]

Autodesk Revit Server is used to connect offices in a WAN for Revit models. The central office or primary project office should host the Revit Central Server, and each collaborating office should have a Revit Local Server (aka accelerator). Model data is stored on both the Central and the Accelerator servers. This makes it possible for each office to work as though the model data is local (LAN). The basic technology is a cache file server using IIS (Windows Web services).

This is a viable technology if the offices are within the same region 1000+ mile radius, and if the network connection has high bandwidth and stability. This technology, however, does not scale well if you have more than three offices, or you are connecting offices between continents. The network latency between offices needs to be under 100 ms, and optimum performance should be under 30 ms.

[Anonymous]

Thanks for the clarification between a "local revit server " and an "accelerator". I previously thought that a local revit server is completely independent from an accelerator that these are two completely different things. But then you pointed out that a Riverbed accelerator is indeed considered a local revit server and vice versa when in the case of a "Server-based" workflow topology, correct ? I'm just really trying to understand the major difference between a "Server-Based" workflow topology vs. a "File-Based" workflow topology.  Since all three offices (more than 3000 mile radius) of my company are all using the up-to-date 2015 Revit servers with the central models stored/hosted on the central Revit server in the primary office, and using only the Riverbed accelerators caching the data with one per location, does this confirm that it is a "Server-Based" workflow ?

[Anonymous · Accepted solution]

Sorry, I did not mean to confuse you.

The Revit Local server is also known as the Revit Accelerator. This is completely separate from the Riverbed accelerator. The Revit Accelerator copies (caching) model data between offices. The Riverbed accelerator optimizes data throughput from the Revit Server Network through port 808.

My interpretation is that it is a server based workflow is one with a server application (e.g. Revit Server). I think of the Riverbed accelerator as an appliance which can enhance a file based workflow (e.g. network drive) or a server based workflow.

Because your offices are pretty far apart, both Revit Server and the Riverbed accelerators will improve the performance.

[Anonymous]

Anyone who reads this will be benefited from your explanation on Revit servers and workflow. I've waited a long time for someone to answer and clarify these questions and I'm very thankful to have my questions answered finally.

Thanks so much !