Hello!

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

What is shared in Tekla Model Sharing

Last updated November 6, 2017 by Tekla User Assistance tekla.documentation@trimble.com

Software version: 
2017

What is shared in Tekla Model Sharing

What is shared in Tekla Model Sharing

By default, all the model data is shared when you share a model in Tekla Model Sharingcloud service for collaboration and for storing and sharing a model

Tekla Model Sharing is one of the Tekla online services.

.

How data is shared in Tekla Model Sharing depends on the type of the shared data.

  • Some data is shared incrementally.

    This means that only the new and changed data is shared. When you read in, the data that is fetched from the sharing service is merged to the data on your computer.

  • Some data is shared, but it cannot be updated incrementally.

    When you read in, the data that is fetched from the sharing service overwrites the data on your computer.

  • Some data is not shared.

    Empty folders under 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.

    are not shared.

    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.

Note:

Some of the cataloguser interface for displaying or modifying information in categorized lists

For example, profile catalog and shape catalog are catalogs.

files that are located in the environment folders ( rebar_database.inp , assdb.db , screwdb.db , matdb.bin , profdb.bin ) are copied to the model folder when the sharing is started.

Option Description

Model database

Model database .db1 is shared incrementally.

Numbering database

Numbering database .db2 is shared, but it cannot be updated incrementally.

If you have modified the family numbering settings and you read in, you lose the changes if another user has changed the family numbering settings and has written out.

We recommend that one user updates and shares the numbering settings with other users by writing them out. In case the user needs to read in before writing out the numbering updates, it is important to check that the settings are as they were before starting to share them.

We recommend you to use the Numbering series of selected objects command on the Drawings & reports tab when numbering.

Create your model output, such as drawings, reports, NC files and IFC files, after a successful write out.

Model history database

Model history database history.db is shared incrementally.

Plan database

Plan databases .db3 are shared, but they cannot be updated incrementally.

If you have imported a CIS/2 or a SDNF model and you read in, you lose the plan database changes if another user has imported the same CIS/2 or SDNF model and has written out.

Analysis model database

Analysis model database .db6 and analysis results model database .db5 are shared, but they cannot be updated incrementally.

If you have modified an analysis model and you read in, you lose the analysis model changes if another user has changed the same analysis model and has written out.

Custom components and sketched profiles

Custom components and sketched profiles database xslib.db1 is shared incrementally.

Profile catalog

Shared model contains the profile catalog file profdb.bin.

When you add and use a new profile definition in the shared model, the definition is shared the next time you write out. When another user reads in this new definition, the profdb.bin file in the user's model folder is updated to include the added definition.

You can also update the profile catalog with new profile definitions without creating any new objects.

Reinforcing bar catalog

Shared model contains the reinforcing bar database rebar_database.inp.

When you add and use a new reinforcing bar definition in the shared model, the definition is shared next time you write out. When another user reads in this new definition, the rebar_database.inp file in the user's model folder is updated to include the added definition.

You can also update the reinforcing bar catalog with new reinforcing bar definitions without creating any new objects.

Bolt catalog

Bolt assembly catalog

Shared model contains the bolt catalog file screwdb.db and the bolt assembly catalog file assdb.db.

When you add and use a new bolt or bolt assembly definition in the shared model, the definition is shared the next time you write out. When another user reads in this new definition, the profdb.bin and assdb.db files in the user's model folder are updated to include the added definition.

You can also update the bolt catalog and bolt assembly catalog with new bolt or bolt assembly definitions without creating any new objects.

Material catalog

Shared model contains the material catalog file matdb.bin.

When you add and use a new material definition in the shared model, the definition is shared next time you write out. When another user reads in this new definition, the matdb.bin file in the user's model folder is updated to include the added definition.

You can also update the material catalog with new material definitions without creating any new objects.

User-defined attribute (UDA) definitions

When a model is created, the user-defined attribute definitions are read from the objects.inp files and the definitions are stored to the environment.db database. Modified and added new attribute definitions are shared incrementally.

New attribute definitions are added to the database automatically when the model is opened. If the current objects.inp file has a different definition than the environment.db , it is possible to take changes to use by clicking File menu > Diagnose & repair > Diagnose and change attribute definitions .

If the objects.inp file is in the model folder, it is shared as a file and it overrides the local objects.inp file when you read in.

Options

When a model is created, the options are read from the options.ini files and the model-specific options are stored to options_model.db and options_drawings.db databases.

Model-specific options can be modified using the Options and Advanced Options dialog boxes. Model-specific option modifications are shared incrementally.

  • Some of the options are of the type SYSTEM(ROLE). These options are read from the .ini files and are not shared. It is possible to change SYSTEM(ROLE) model option to MODEL(ROLE) option and the drawing option to DRAWINGS(ROLE) option. The options are then stored to the options_model.db or options_drawings.db databases in the model folder, and the value is shared incrementally.

  • Some of the options are of the type USER. These options are user-specific and they are not shared.

  • Some of the options are of the type SYSTEM. These options are user-specific and they are not shared. It is possible to change a SYSTEM option to a MODEL(SYSTEM) option. If you change a SYSTEM option to MODEL(SYSTEM) , the changed value only works for the current model. These options are not shared.

Other important files in the model folder

The database ID range mapper file db.idrm and the library database ID range mapper file xslib.idrm are related to the handling of IDs. These files are needed, for example, to open drawings that have been created in single-user or multi-user modes.

View sharing

By default, views are not shared. Views are shared if they have a name, and the Share option in the View Properties dialog box is set to Shared.

Note that when you join a model, you get all the model views but changes to the views are not shared if the Share option is set to Not Shared.

If you want to check the files that have been overwritten when you read in, click File menu > Sharing > Open file backup folder. You can then, for example, copy the files back to your model or check the files for change detection.

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: 
No votes yet