The creation of a workset begins with the lead discipline defining the model architecture and assigning tasks for the entire project. This model structure and division of labor are then uploaded to a server and saved in a shared folder on the local area network via a “network path.” The central file is finalized by naming it according to the project and its start date.
Next, each discipline’s designer accesses the central file through the network path and updates their user permission from “no” to “yes.” After confirming this change, they save a local copy of the central file to their machine and carry out model development on this local version.
Designers across different disciplines synchronize their local files with the central file every three hours using the “instant synchronization” feature. They can also check the latest progress made by other team members by using the “reload latest workset” function, which updates their local model with recent changes from the central file.
Important Considerations for Workset Mode
In workset mode, both the central and local files are critical. If local files are not regularly synced back to the central file, there is a significant risk of data loss in case of a personal computer failure. Therefore, it is essential to develop a habit of frequently synchronizing with the central file to safeguard work.
Additionally, each designer has independent permissions for graphical elements within the workset. While this protects the integrity of each designer’s work by preventing unauthorized changes, it can also cause frequent requests to borrow graphic elements from others. When multiple design disciplines intersect, owners of these elements may spend considerable time managing borrowing requests, which can reduce overall modeling efficiency.
To improve collaboration, it is advisable to regularly release permissions on graphic elements and components, allowing smoother sharing and reducing bottlenecks during model construction.
Must log in before commenting!
Sign Up