IFC improvements

Tekla Structures
Tekla Structures

IFC improvements

In Tekla Structures version 2022, you have better control over IFC entities, and you can filter the objects that you want to include in the IFC4 export. Defining the property sets for the IFC export is now easier and more reliable due to the improvements in the property set definition dialog box and functionality. There are also some improvements in the IFC object conversion and IFC4 reference model insert. Bridges are now supported in the IFC4 export.

Better control over IFC entities

More exact definition of IFC entities in IFC4 export

You now have more control over the object types to support the workflow when you export information to the IFC4 format, and you can define the needed IFC entities more precisely by using the new predefined and user-defined subtypes.

For example, if you have a native assembly in your Tekla Structures model, you can define that its entity type is IfcBridgePart, like earlier, but now you can also be more specific and select a Subtype (IFC4) among the predefined subtypes available, or select USERDEFINED and then type the desired type in User-defined type (IFC4) in free text, for example, bridge part.

IFC entity moved to property pane

The IFC entity setting was earlier located in the user-defined attributes dialog box for model objects, now it is located in the IFC export section in the property pane for model objects, and accessed more easily.

For more information about the IFC entities and IFC export, see Export a Tekla Structures model or selected model objects to an IFC file.

Bridge support in IFC4 export

  • Bridge view export has been added to the IFC4 export. The main purpose of the Bridge view export is to extend Tekla Structures to bridge constructions. The bridge IFC files are based on the IFC4.3 schema.

  • The Bridge view option has been added to the Export type list in the IFC4 Export dialog box.

  • A new user-defined attribute, IFC_BRIDGE, was added in project properties.

  • There is also a new IFC entity type, IfcBridgePart, available for mapping of bridge assemblies.

Improvements in IFC property sets

The Property Set Definitions dialog box has been improved. Defining new property sets, and editing and deleting property sets has changed, and you can now select the desired IFC entity type from a new drop-down list to display the entities of the selected type only.

Improvements in the Property Set Definitions dialog box

  • Property set configuration file name is the new name for the file name field. It shows the name of the configuration file that you are currently working on.

  • There are new buttons available for working with property sets:

    • opens another dialog box where you can edit the name and description of the selected property set.

    • deletes the selected property set from the configuration file. You need to confirm the deletion.

    • opens another dialog box where you can create a new property set in the selected configuration file.

  • The new Entities drop-down list allows you to select the IFC entity type category. When you select a category, the related IFC entities are displayed in the Select entity types list.





    Structural: This is the default entity type category.


If you have created additional property sets in a previous Tekla Structures version, only the property sets corresponding to the IFC objects types found in the new Structural entity type category will be available in Tekla Structures 2022. Property sets corresponding to object types located in other entity type categories (such as IfcCovering in Common) will need to be recreated.

For more information about property set definitions, see Define additional property sets for IFC export.

Other property set improvements

  • The property set comparison tolerance attribute (.rmct) and comparison set attribute (.rmcs) can now be read from the XS_FIRM and XS_PROJECT folders.

  • User-defined attributes that are defined for parts in objects.inp are now visible and selectable in the Property Set Definitions dialog box.

  • The IfcRoof, IfcRamp and IfcStair property set definitions could not be included in the IFC export without including the IfcElementAssembly as well. This has now been fixed.

    This improvement was already introduced in Tekla Structures 2021 SP1.

  • The IFC2X3 export does not export steel secondary objects as IfcDiscreteAccessory from now on. You can force previous categorization by setting the new advanced option XS_IFC2X3_EXPORT_SECONDARY_AS_DISCRETEACCESSORY to TRUE in an .ini file, for example, teklastructures.ini.

    This improvement was already introduced in Tekla Structures 2021 SP1.

  • Before, when an additional property set definition contained rules, no property sets were written to the IFC4 export. Now rules can be used in the additional property set definitions also in the IFC4 export.

Other IFC export improvements

  • The IFC export is now using translation strings from all folders mentioned for the XS_MESSAGES_PATH advanced option.

  • IFC2x3 export: The Output file folder path may now contain up to 247 characters instead of the previously supported 72 characters.

IFC object conversion

UDA mapping

  • You can now have dots (.) in the property set names in Copy properties to UDAs Property box in the IFC object conversion settings dialog box. You can copy properties from the IFC object property sets to be used as user-defined attributes of converted Tekla Structures objects.

  • The mapping of the IFC property Profile name now supports using either "EXTERNAL.profile name" or "EXTERNAL.profilename". Now you can also use translated strings in mapping product and profile attributes for Profile name, Description, Ifc type (type), Object type, Phase, Material, Finish, Profile, and Name. For example, you can use the German string "EXTERNAL.Profilname" and it works.

For more information about IFC object conversion, see Convert IFC objects to native Tekla Structures objects.

Material mapping

Now the material mapping is also enabled for existing materials. Previously, the mapping was working only for not found materials.

IFC4 reference model insert now supports base points

Support for using base points has been added to the IFC4 reference model insert through IFC4 schema specific IfcMapConversion.

Was this helpful?