Revit server 2012

[MikeJarosz]

We are new to the Revit Server (RS). We had a near death experience last night. We do not have the fastest communications link, and the synchronization is taking longer than we would like. This creates problems with save-to-central (STC). Everyone (6 users) started getting messages that the central file was locked. No one could save. We all saved to local and exited. Our IT manager overnight had to figure out how to unlock the central, which he did. In the morning, we were all able to STC our locals and nothing was lost.

I believe there should be some "warning light" that indicates the RS is in sync mode. Users would then know they should not STC. Is there some way to determine when the sync is completed? For now, we are announcing our STCs to the team by IM. We are located in NY and KY, soon to add MD and maybe MA. We have arbitrarily instituted a 15 minute wait after every STC. The number of IMs is distracting.

Is RS 2013 better? We are in a JV that requires 2012.

[cliff collins]

You can check the RS Admin website console to see when users have STC. Using IM in a large multi-office team is critical; esp. when lots of users are needing to Open and STC large files over the WAN. RS 2013 does improve this somewhat; but you must also convince management to invest in faster internet with better up/down speed and lower latency. Try having users at all offices do a speedtest.net (or sim.) and report their results. Latency (ping in ms) should be as low as possible; 15-20 ms is good. Anything more than 50 ms can cause problems.

[MikeJarosz]

I have the Admin console, and can see the STC history, but only after it's done, not during. If the sync is especially slow, there is a wide-open vulnerability.

I found another issue. The auto save for most of my users was set to 30 minutes. Most of them were saving when prompted. It's always something, right??????