In environments where cloud connectivity or BIM 360 is not preferred, a non-BIM 360 approach to central Revit models can be highly efficient. This traditional method relies upon a manual synchronization process and a setup of a local wireless network.
How to Set Up a Traditional Central Model
1. Create the Central Model
- Organize your master file:
Start by creating a Revit project with an organized and clean file. This file must include all templates, standards and project settings. - Save in a Shared Network:
Place a master file on an accessible shared network drive. This drive becomes the central repository of the project.
2. Establish Worksets
- Split the Project:
Use Revit Worksets for a more manageable model. It allows the team to work independently and on different aspects of the project. - Assign Ownership:
Define clearly which team members are responsible for the worksets to avoid duplication of changes. Set up a procedure for checking out and in worksets.
3. Create local copies to work off-line
- Download Local Files:
Each user should save a local version of the central model on their own workstation. In order to maintain the connection to the central model, it is important to not remove the file from the computer during the initial opening. - Work Independently:
The team members should save the work they do frequently. Local work offers flexibility, particularly for environments with limited access to the network.
Synchronization and Daily Workflow
Regular Updating
- Synchronize Often:
Users must frequently synchronize the changes they make to the central version. This practice helps to reduce the chances of conflicts and keeps the master file current. - Resolve Conflicts:
Review the changes immediately and merge any conflicts if necessary.
Backup and Maintenance
- Routine Back-ups:
Regularly backup the central model in order to prevent data loss from file corruption and network issues. Highly recommend automating your backup process. - Communication protocol:
To coordinate synchronization, use communication tools and regular team meetings.
Challenges and Advantages of Offline Approach
Advantages
- Control, Security and Privacy:
Data can remain within a localized network which is beneficial to organizations with strict security standards. - Simplicity:
The non–BIM 360 method avoids the complexity of cloud-based management and may be easier for teams accustomed to traditional workflows.
Challenges
- Limited Remote Access:
Working offline restricts the access to the central model when the team is not on the same networking. - Manual Coordinating:
In order to avoid conflicts and ensure data accuracy, it is necessary to have a disciplined synchronization process and clear communication.
The traditional method of managing central Revit models is a solid framework for teams that operate in local networks. The traditional approach to managing central models in Revit offers a reliable framework for teams operating in secure, local network environments. Although this method does require disciplined coordination and regular backups, its ease of use and enhanced control makes it a viable option for projects with strict network security requirements.
This article will serve as the basis of our three part series on using central models in Revit. We will examine the BIM 360 collaboration approach in the next installment. This is a modern cloud-based tool that uses real time updates, robust versions control and global accessibility. Watch for tips on how to fully benefit from and transition to a BIM workflow that is cloud-enabled.
