Interoperability improvements

Last updated July 14, 2020 by Tekla User Assistance tekla.documentation@trimble.com

Software version: 
2019i

Interoperability improvements

Interoperability improvements

Tekla Structures 2019i contains improvements in reference models, IFCfile format commonly used in BIM that facilitates software interoperability

IFC is an open specification developed by the IAI (International Alliance for Interoperability).

Model can be exported into an IFC file.

object conversion, IFC export, and point cloudgroup of measured points that are imported to Tekla Structures as one unit

Point clouds can be placed by the model origin or by a defined base point.

functionality.

Reference models

Reference model object locking

  • Reference modelmodel which the designer can use as an aid when building another model

    A reference model is created in Tekla Structures or in other software and can be inserted to Tekla Structures. The reference model appears together with the model but it is not modified by Tekla Structures. The user can snap to reference model points.

    For example, an architectural model, a plant design model, or a heating, ventilating, and air-conditioning (HVAC) model can be a reference model.

    objects can no longer be locked. Locking prevented model update, caused confusion and increased the size of the database. Object lockuser-defined attribute that is used to protect model objects from being accidentally changed

    The model objects can be locked and unlocked in the object locks dialog box and in the phase manager.

    has been used for locking model location. We recommend that you use model lockto prevent unwanted action in a model or a drawing

    It is possible to lock model objects, reference models, and drawings, for example.

    instead and set XS_REFRESH_ALSO_LOCKED_REFERENCE_MODELS to TRUE.

    For more information about locking reference models, see Lock reference models.

.db1 as reference model format

  • The .db1 format has been removed from the supported reference model formats. You can still enable the .db1 format in the Add model dialog box by setting the advanced option XS_ENABLE_NATIVE_MODEL_AS_REFERENCE_MODEL to TRUE in an .ini file, for example in options.ini, user.ini, or company.ini. Originally, this format was added in the Add model dialog box for testing purposes.

Calculate new offsets when Location by is changed

  • Reference model Location by change logic has been improved. By default, the location by change does not keep the reference model location. A new check box was added to calculate new offsets and keep the current reference model location.

New reference model template attributes

  • Reference model properties Code , Title , Phase , Description and Group are now available as template attributes for reports.

Other reference model improvements

  • When you refresh reference models that have been created with previous versions of Tekla Structures , the reference model informationinformation stored to the model

    Model information covers, for example, model objects, and drawing and project information.

    is now updated to match the version of Tekla Structures that you are currently using.

  • The performance of the reference model insert has been improved when the Tekla Structures model already contains non-visible unloaded reference models. After the fix, non-visible reference models are not loaded anymore in the reference model insert.

  • Now it is possible to use 3D image files ( .obj ) as reference models.

IFC object conversion

  • IFC object conversion of steel contour plates now uses the prefix defined for plates in Components settings ( File > Settings > Options > Profile name > Plate ) as the prefix for Tekla Structures native plates. You can use prefixes that are supported by your environment.

  • Arbitrary profile mapping by name does not need to match the dimensions. Arbitrary profile mapping by name can be set to require dimensions to match by setting the new advanced option XS_CONVERSION_ARBITRARY_PROFILE_MAPPING_BY_NAME_MUST_MATCH_DIMENSIONS to TRUE. The default is FALSE.
  • Parametric profilepredefined profile whose cross section dimensions the user can change by using parametric variables

    conversion by profile name mapping does not need to match the dimensions. Parametric profile conversion tries to find a corresponding library profile and if a profile does not match the parameters, the default parametric profile will be used.

For more information, see Convert IFC objects into native Tekla Structures objects.

IFC export

IFC2x3 export

  • You can now also export radial grids in the IFC2x3 export.

  • Edge chamfers are omitted from the exported IFC model. This is to enable better interoperability with plant design systems. If the geometry with edge chamfers is needed, you can set the IFC export type to B-rep separately for those objects in the objects' user-defined attributes dialog box on the IFC export tab.

IFC4 export

  • The IFC4 Export now contains a new export type IFC4precast view. The IFC4precast view aims to support the fabrication data transfer workflow of precast elements. At the first phase it covers the fabrication of precast walls and slabs including all the needed reinforcement and embeds.

For more information, see Export a Tekla Structures model or selected model objects to an IFC file and IFC4precast.

Point clouds

  • You can now use point clouds through internet. There is a new URL option in the Attach point cloud dialog box where you can enter the URL address.

  • Point cloud web streaming cache has been added. The cache is a common cache with Trimble Connect(1) application for information sharing and collaboration for construction projects that is based on the Trimble Connect platform

    (1) Reference models are used in Trimble Connect application instead of using import and export.

    (1) Trimble Connect application includes web, desktop and mobile clients, and the Sync tool, for example.

    (2) Trimble’s platform for microservices in the cloud

    (2) Trimble Connect platform’s microservices include services for uploading, storing, processing, and managing or consuming data. These services are meant to provide common solutions required by multiple applications.

    for Desktop
    . You can define the cache folder using the advanced option XS_POINT_CLOUDS_WEB_CACHE in the File Locations category of the Advanced Options dialog box. The cache usage improves the performance of the web streamed point clouds.

For more information, see Point clouds.

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

Comments

by Eugene

"XS_ENABLE_NATIVE_MODEL_AS_REFERENCE_MODEL to TRUE in an .ini file."
It would be good to specify which files to use whenever using such statement. teklastructures.ini works in that case however it takes some time to check that.

by Dave Renninger

It's better to add your customized variables to a company.ini file (this can be defined in a custom shortcut) rather than modifying the teklastructures.ini file (this file can get overwritten when upgrading to a new SP).

by Päivi from Tekla User Assistance

Hi,
I will ask our experts what is recommended here.

Best regards,
Päivi from User Assistance Team

by Päivi from Tekla User Assistance

Hi again,
You are right. I will modify the instructions and recommend options.ini, user.ini, or company.ini.

Br
Päivi

by Päivi from Tekla User Assistance

Hi,
I will ask our experts what is recommended here.

Best regards,
Päivi from User Assistance Team

by Päivi from Tekla User Assistance

Hi again,
Options.ini, user.ini, and company.ini are recommended here. teklastructures.ini can be overwritten when Tekla Structures is updated. I will add the recommended ini files in the instructions.
BR
Päivi