Hello!

Did you know that logged in users can see a lot more content?

Best practices in Tekla Model Sharing

Last updated November 23, 2018 by Tekla User Assistance tekla.documentation@trimble.com

Software version: 
2017

Best practices in Tekla Model Sharing

Best practices in Tekla Model Sharing

To keep you shared models in good shape and to share your changes successfully, follow the Tekla Model Sharingcloud service for collaboration and for storing and sharing a model

Tekla Model Sharing is one of the Tekla online services.

best practices.

Note that in some situations, pour management has caused conflicts when reading in, even if the pour units have not been modified. These conflicts may result in objects being removed from pour units.

For general Tekla Model Sharing troubleshooting instructions, see Troubleshooting Tekla Model Sharing.

How different object types work in shared models

When several users modify the model at the same time in Tekla Model Sharing , conflicts may occur.

In general, all object types work similarly in Tekla Model Sharing. When you read in, the changes in the incoming packet override your local changes to the same object. In other words, if several users modify the same object, the user who first writes out the changes to the sharing service wins in conflicts.

Before you start to share models, agree on common ways of working.

For example,
  • have users work on different areas of the model.

  • check catalogs so that they include all the needed definitions.

  • check family numbering settings.

    Family numberingprocess of assigning family-based numbers to cast units or assemblies

    settings are shared but cannot be incrementally updated. We recommend that one user first reads in all the packets, makes the updates and then shares the settings by writing them out. If the user needs to read in before writing out, it is important to check that the settings are as they were before starting to share them.

    Give start numbers in wide ranges so that you do not run out of numbers within a numbering seriesset of identifiers defined by the user, based on which Tekla Structures compares parts, assemblies, cast units, or reinforcement with each other during the numbering and gives position numbers

    Numbering series is defined by a prefix and a start number.

    The user can, for example, allocate separate numbering series to different phases or part types.

    , and that any numbering series does not overlap with another.

    We recommend you to use the Numbering series of selected objects command on the Drawings & reports tab when numberingprocess of assigning position numbers to parts, cast units, assemblies, or reinforcement

    In Tekla Structures, the position numbers assigned in the numbering are shown in marks and templates, for example.

    .

  • agree whether pours will be used in the model and set XS_ENABLE_POUR_MANAGEMENT accordingly.

If users modify different properties of the same object, the end result is a combination of modifications.

  • Model objects

    A shared modification to an object propertysingle characteristic associated with an object type

    For example, profile and material are object properties.

    overrides any other object property modification.

    For example, one user modifies a beam profile and writes out. Another user has modified the material of the same beam and reads in. The user who modified the beam material loses the changes, because the shared changes override the local changes to the same object.

  • Grids

    If there is a conflict in sharing grids, grids are recreated using the original values that have been set in the gridmodeling aid that represents a three-dimensional complex of horizontal and vertical planes

    In Tekla Structures, grids are used as an aid in locating objects in a model. The grid is shown on the view plane by dash-and-dot lines. It is also possible to show grids and grid line labels in drawings, and to modify grid properties in the drawings.

    It is possible to have more than one grid in a model. For example, a large-scale grid for the entire structure, and smaller grids for some detailed sections.

    properties. Any manually added grid lines are lost.

    For example, when two users modify a grid by adding extra grid lines and write out, the added grid lines disappear from the model when they read in.

  • User-defined attributes (UDAs)

    A shared change to a user-defined attributeobject property created by the user in order to widen the range of predefined object properties

    User-defined attributes are used when the predefined object properties are not sufficient but more properties are needed. For example, comment, locked, and erection status are user-defined attributes.

    (UDAobject property created by the user in order to widen the range of predefined object properties

    User-defined attributes are used when the predefined object properties are not sufficient but more properties are needed. For example, comment, locked, and erection status are user-defined attributes.

    ) overrides changes to the same UDA only.

    For example, a change in the Comment UDA overrides a change to the Comment UDA but not to the Shorten UDA.

    A shared change to a part does not override UDA changes and vice versa.

  • Part and the related component

    A shared change to a part does not override component changes and vice versa.

  • Drawings

    There can be duplicate drawings from the same part.

    For example, two users create drawings from the same part when they are working on their local versions of the shared modelmodel used for collaboration over the Tekla Model Sharing service

    With a shared model, each user works with their own model and the changes are shared through Tekla Model Sharing. A shared model requires the use of a single-user model. The same model cannot be a shared model and a multi-user model.

    . When both users write out their changes, two drawings appear on the drawing listlist of drawings that provides information about the drawings in a particular model and that is used for searching, managing, and printing the drawings

    In the drawing list, the user can, for example, search, open, update, freeze, lock, and delete drawings. The drawing list can also be used to display the associations between the drawings and the parts in the model.

    Drawing list is used in Tekla Structures until version 2018. See document manager.

    . Tekla Structures does not delete either of the drawings, and it does not merge the changes from the drawings. You need to visually check the drawings and decide which drawing to delete, or to use drawing locks to prevent other users modifying the drawings.

  • Pours

    If the pours are enabled in the model, do not disable the pours using XS_ENABLE_POUR_MANAGEMENT , especially in the middle of the project. The pours and pour breaks in the model and in the drawings may get invalid, and you may lose all pour-related modeling work.

    In some situations, pour management has caused conflicts when reading in, even if the pour units have not been modified. These conflicts may result in objects being removed from pour units.

  • Standard files for numbering setup

    Standard files for numbering setup are not loaded automatically when you read in. If you want to take them in to use, you need to reload them after reading in.

Warning:

If an object deletion has been written out to the sharing service, the object will be deleted in your model when you read in. This happens regardless of whether you have modified the object before reading in. Deleted objects remain deleted if the deletion has been shared.

Deleted objects are not visualized when you read in.

How object IDs work in shared models

Tekla Structures objects have an identifier that is shown as an object GUID, Globally Unique Identifier, that is also used in Tekla Model Sharing.

This means that features that do not use GUIDs need to be changed to use GUIDs:

  • Interoperability import/export actions:

    • FabTrol XML

    • ASCII

  • All other applications, macros and report processes that rely on static IDs.

How to share catalog updates without creating new objects

Sometimes you may need to update catalogs with new definitions, such as new profiles, and share the changes without creating any objects with the new definitions.

To share cataloguser interface for displaying or modifying information in categorized lists

For example, profile catalog and shape catalog are catalogs.

updates:

  1. Ensure that all users on the shared model write out their changes.
  2. Read in all the model changes.
  3. Update the needed catalogs.
  4. Create a new baseline.
  5. Ensure that all users join the created baseline.

    After users have joined the baseline:

    1. Ensure that users check that their settings for excluded files and folders are up-to-date in File menu > Sharing > Sharing settings > Exclude , or that they copy the FileSharing.ini file from the previous local version of the model in ..\TeklaStructuresModels\<model>\ModelSharing\Settings.
    2. Ensure that users remove their previous local versions of the model.

How to share Organizer data

By default, Organizer data is not shared. However, you can use the Organizer import and export with Tekla Model Sharing to share the Organizer changes.

To share Organizertool that is used for categorizing and managing model information, object properties and object property queries, and model object classification

Organizer consists of two tools, object browser and categories.

data:

  1. Select a user who is responsible for the Organizer data. This is User A.
  2. User A creates the Organizer data and exports the data to a model subfolder.

    Note that the selected folder cannot be the default ProjectOrganizer folder.

  3. User A writes out.
  4. User B reads in and notices that there is new data available.
  5. User B opens Organizer and imports the data that User A has exported.

    The data appears as new in Organizer.

  6. User B removes the old Organizer data and saves the model.
  7. User A updates the Organizer data, exports the update and writes out.
  8. User B reads in and imports the updated data to Organizer.

    The data appears as new in Organizer. User B removes the old data.

Backing up shared models

We recommend you to back up the models used in Tekla Model Sharing. In case there are problems with a shared model, it is possible to select any user's local version of the model, or a model that has been backed up, and continue working using that model. Make sure that you have the complete backed up model in use and that the model folderfolder that is used for storing files associated with a model

Tekla Structures stores all files associated with a model in a folder it creates with the same name as the model database (.db1).

In multi-user mode all users access the same model folder.

includes, for example, drawings and different databases. This ensures that the model functions properly and you do not lose any data. If the backed up version of the model is old, reading in all the changes may take some time.

Back up your models according to your company conventions, for example, by using Windows Backup. You can also use the Save as > Save and create backup copy command to create a backup copy of the model. The backup copy will have the same GUIDs as the original model.

Note that the Save As command cannot be used for backing up the model. If you use Save As , the model gets new IDs and it has no relation to the original model.

If you use the Save as command, the model history is not copied with the saved model.

Restoring shared models

If you have problems with the shared model, you can restore a previous version of the model, and start using that model in Tekla Model Sharing.

To take a previous version of the model into use:

  1. Join the model again.
  2. Read in the packets until you have reached the preferred level in the model history.
  3. Exclude the model from sharing.
  4. Start sharing and invite other users again to the model.

    Ensure that all the users within the model start to use the restored version of the model.

Quick feedback

The feedback you give here is not visible to other users. We use your comments to improve our content.
We use this to prevent automated spam submissions.
Content rating: 
Average page rating: 1 (1 vote)
Refresh page after voting to show updated result.

Comments

by John Swallow

No information on users expecting to use different version of Tekla Structures when sharing the same model?

by Tekla User Assistance

The users of the same shared model need to have the same Tekla Structures version and preferably the same latest service pack. We'll add this information to the help.