Egnyte provides a unique value proposition for customers in the Architecture Engineering and Construction (AEC) industry. Customers in the construction industry use Egnyte for sharing project files between headquarters and remote job-sites. While hybrid cloud adoption and large files is a common trend, we also see a growing usage of Autodesk’s Revit application. In many cases, Revit collaboration and sharing are critical for the business that customers pilot-test Revit on Storage Sync in a production-like environment during their trial period with Egnyte.
Is Storage Sync similar to Windows Server for Revit Collaboration?
From an operational perspective, AEC customers expect Storage Sync to be a Windows Server replacement. Once Storage Sync is deployed on-premise, IT admins require all of their users to continue to use the same drive letter (for e.g. P:) as they did before migrating to Egnyte. During the migration phase, IT administrators move certain project folders to Storage Sync while the remaining data is still served from the Windows Server. They leverage Microsoft Distributed File System (DFS) to consolidate the project folder namespace across the Windows Server and Storage Sync.
After the Revit files are migrated to Storage Sync, the workflow for Revit collaboration is no different than Windows-based Revit collaboration. If a user wants to collaborate on a Revit project file, he will need to elevate the Revit Local file to a Central file using the File-based Worksharing mode and save the file. This enables other on-premise users to open the same file and work on different components of the project.
Best Practices for Configuring Storage Sync for Revit collaboration
Given the unique nature of Revit collaboration, you should consider the following best practices that will help maximize efficiency and end-user satisfaction while collaborating on Revit files.
- Configure Storage Sync with large memory and CPU: Revit is a resource-intensive application. If you have many users connected to a Storage Sync device, this can easily stress the system. Allocate at least 8 GB RAM and quad-core CPU on the Storage Sync virtual machine. If you plan to purchase a NETGEAR ReadyNAS device for Revit collaboration, look for ReadyNAS devices with higher memory and CPU specifications.
- Optimize your folder structure for Revit collaboration: If you have project-based teams and Revit users collaborate within active projects, create a folder structure that reflects project-based workflow. For instance, if you have remote teams in Phoenix and San Diego, you can create a top-level Projects folder and structure all active projects underneath this based on geographic location. This will enable you to choose only relevant folders for each Storage Sync instance in a given location.
- Central Files co-located in a Storage Sync instance: If you want to leverage Revit’s File-based Worksharing mode, all the collaborators require access to the same Storage Sync instance. In other words, Revit users must open the file through their network drive letter, and not through Egnyte Connect Desktop App.
- Windows Terminal Servers for Remote Collaboration: Remote workers who wish to work on a Revit central file will require access to the Storage Sync device over VPN. Additionally, you can set up Windows Terminal Servers within the company firewall in order for your remote users to access and collaborate on Revit files. By deploying Windows Terminal Servers in the same network as your Storage Sync, your on-premise users and remote workers can efficiently collaborate on Revit projects with minimum network delays.