Why Tekla Model Sharing vs Multi-user mode?

The product guide Working collaboratively within a Tekla Structures model gives an overview of Tekla Model Sharing and Multi-user mode. We frequently receive inquiries from users seeking advice on the optimal solution for their specific scenarios. It is our strong recommendation to adopt Tekla Model Sharing for virtually all situations.

Some of our reasons for the recommendation of Tekla Model Sharing are:

• Tekla Model Sharing enables local and globally distributed teams and to collaborate effectively on a single model, irrespective of geographical locations and time differences.
• An internet connection is required solely for the purpose of sharing modifications to the model.
• Users maintain a local copy of the model on their individual computers, significantly reducing latency issues associated with network server connections. This local storage approach offers several advantages:
  • The ability to work in an offline mode or when disconnected from the (cloud or local network) server.
  • Enhanced performance for many operations compared to network drive storage.

  • Every computer maintains an individual backup of the model.

• Model data is shared and synchronized via the internet, stored on the cloud-based Tekla Model Sharing service, providing the added benefit of cloud model back-ups.
• The setup and management of Tekla Model Sharing is more streamlined
  • There is no special set up in the company (no server hardware). Users can immediately Share a model in Tekla Model Sharing.
  • Centralized administration of all models through the Management Console for Tekla Model Sharing.
    • View model information in the Management Console: model name, creation date, Tekla Structures version, model ID, environment, number of users, and number of versions.
    • Manage users in shared models in the Management Console
    • Lock models and delete model versions in the Management Console
    • Archive and delete shared models in the Management Console
• Tekla Model Sharing significantly reduces the likelihood of user errors, conflicts, and data corruption.
  • By Managing users in Tekla Model Sharing, it is possible to prevent viewers from accidentally sharing (Writing Out) unintended modifications.
  • It is possible to Detect sharing changes and view the sharing history in Tekla Model Sharing. This aids in recovering from "oops" moments, even after saving your local version.

  • Ability to recover lost drawings by: restoring shared model back-ups and cloning the drawing from the restored back-up.

  • Separation of local saves and Writing Out to the shared model facilitates easier recovery from unintended modifications, even after the local version has been saved.

  • Tekla Model Sharing decouples the numbering operation from the read-in/write-out cycle, enhancing project integrity and operational efficiency.