Import from TEKLA
- Last UpdatedFeb 13, 2025
- 2 minute read
There are several methods available to import structural design data from TELKA. The main options are outlined as follows together with any particulars and considerations for each method.
TEKLA Interoperability
TEKLA also offers a bespoke interoperability feature that can be used to transfer data to AVEVA E3D Design. Refer to the Tekla support article PDMS/E3D for further information.
Note:
AVEVA is not able to provide more information about this option as it is developed
and owned by TEKLA, but it seems that many AVEVA customers get better results using
this capability than the other options of SDNF or IFC. But this may vary depending
on the model data and requirements.
SDNF
SDNF provides a way to import structural steel to E3D as intelligent elements, but has some limitations in what can be imported:
SDNF can import Linear elements such as UB, UC and PFC, as well as planar types (flat plates but not bent plates).
SDNF Cannot import Mechanical Items, and it can also not import Bolts or holes in linear elements. Holes in plates are possible but it depends if the source software can export them to the SDNF file.
During import Linear elements can be mapped to AVEVA Catalogue elements and can be edited in E3D.
IFC
Another option to import from TELKA is to use IFC which will be more complete, but the elements will not be native/editable and can only be used for referencing and coordination.
TELKA Structures offers a number of export type options refer to, for example, the Tekla support article Export a Tekla Structures model or selected model objects to an IFC file for further information.
AVEVA recommend the use of the Surface geometry (for IFC 2x3) or Reference view (for IFC4) options in TELKA to give the best results when the file is imported into E3D Design.
It is also important to do the IFC export from Tekla in a suitable scope per IFC file,(export in several smaller files than all in one big file). For example create one IFC export file for each framework in Tekla. Thus allowing the import of each file in E3D Design under different owners, which provides a more meaningful navigable hierarchy in E3D Design, and avoids getting too many members within a certain owner which could otherwise affect the performance in E3D Design, or even exceed the maximum number of members for an owner causing errors.
The Assembly level is stored as an AVEVA EQUI (Equipment) type and the single Part is stored as SUBE (Sub Equipment). All IFC imported elements are stored with the same Types in E3D regardless of their source application type. For example a Hole is also stored as a GENPRI under a SUBE under an EQUI.
There are also two DDSE (Data Sets) stored under each type, one dataset for the IFC attributes and the other for the attributes coming from the source application (Tekla). At Single part level (SUBE) again there are the two datasets and also the geometry which is stored as a GENPRI Element.
GENPRI Elements can be moved and rotated in E3D but their geometry cannot be modified. They cannot be changed or mapped to Catalogue items.