Hello!

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

PDMS/E3D and Tekla Structures Interoperability: Q&A, collected 29th August 2018

Last updated August 29, 2018 by Tekla Extensions - General Design tekla.extensions-generaldesign@trimble.com

Software version: 
Not version-specific
Environment: 
Not environment-specific

PDMS/E3D and Tekla Structures Interoperability: Q&A, collected 29th August 2018

Question:
Having issues with the mapping to native sections

Answer:
Tekla sections shown as panels in PDMS but not as native PDMS sections.
=> TS-PDMS link has a principle that if mapping for profile/part is not found panels/plates (PANE) used in PDMS
If mapping is found then a profile section is used (SCTN). Mapping file ProfileMapping.txt is included in installation and it needs
to be in PDMS project folderfolder that is used for storing Tekla Structures-related files customized for a particular project

under TS-PDMS/Mapping. Example of mapping row is W8X35;AISC-SPEC/W8x35


Question:
Revision handling does not work in PDMS side or error in importing file to PDMS

Answer:
Note: Do not change file name of TS export because it is used in revision handling when updates exported.
Also important that the TEKLA 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.

's (TEKLA_GUID, TEKLA_IFCGUID, TEKLA_VERSION) must be created for PDMS project (see instructions).
Also important not to use spaces in file name when exported from TS
 


Question:
Problems to install PDMS application

Answer:
Edited file named in PDMS is related to module you are running. So
PDMS Design --> DesignAddins.xml
Marine,Outfitting --> OutfittingAddins.xml
The company setup might read files from different locations (e.g. can be read from a server based on company setup).
If so contact your PDMS support to get the modifications done correctly.
Problem can be that edited DesignAddins.xml file is not read at all.


Question:
Mapping dialog in PDMS shows red color lines

Answer:
There might be some cases where mapping file is not correctly read, e.g. when deleting a row in dialog.
Usually closing Interoperability dialog in PDMS and reopening solves the problem


Question:
Export to PDMS does not work and red color appear in row in Export to PDMS -dialog when new installation taken into use

Answer:
Uninstall old installation before installing new. Check that ..\bin\applications\Tekla\Model\ExportToPDMS has been removed in
uninstallation and if not remove manually.


Question:
Import to PDMS does not work and an error message like "Error reading package ...ifcZip - aborting" appears

Answer:
TS20.0 version exports .ifczip extension format and TS21.0 .tcZip - in TS-PDMS folder under PDMS project can be old information which causes the problem.
Probably in this case Links folder has not updated information.
Exported files from TS must/should be imported to PDMS from TS-PDMS folder under PDMS project. In TS-PDMS folder should include Mapping folder,
Links folder and export/import files (.tcZip, ifcZip). With newest versions only Links folder needs to be inside TS-PDMS folder. Also Mapping folder can be changed with settings.
The Links folder is a restricted folder that is created and maintained by application.
So user should not go in here. And important is that only one Links folder exists – otherwise problems may occur.
The user can delete the folder if problems. He will then lose all entries in dialog and lose possibilities to do updates.
So a delete is just in case of e.g. starting from beginning.


Question:
Export pipes, equipment from PDMS does not work

Answer:
At the moment only link version for PDMS12.1 can export other than structural objects.
In PDMS if you want to export a PIPE, make the PIPE current element and add it do export dialog. Then mark it and press export.
Please note that PIPE is lowest level for piping export. BRAN is not a possible selection.


Question:
It takes a long time to import to PDMS

Answer:
TS exports parts mainly in extrusion format which can be imported to PDMS as native PDMS objects. Complicated parts as multiplane polybeams
will be exported at the moment as Brep (surface) format and those will be imported to PDMS as polyhedron objects. But Brep objects are slow to import
and handle in PDMS. So best is to avoid Brep format if possible. TS21.0 can export e.g. polybeams and cones as extrusion format - TS20.0 as Brep


Question:
Export from PDMS does not work, profiles/sections related errors in log file

Answer:
Reason probably is restricted (no permission to read) catalogues in PDMS. So open the catalogues for reading.


Question:
Export/import to PDMS does not work and red color appear in row

Answer:
Some special characters in file/model name may cause problems like u with 2 dots (ü).
Change of name needs to be done in Tekla side export. Name cannot be changed after export.
Time stamp will be automatically added to file name. So own time stamps in file/model name with # character not allowed and not needed


Question:
Revision handling does not work in PDMS side and duplicate members created

Answer:
Important to use same row (model) in Tekla Interoperability dialog and not to add a new row


Question:
Export from PDMS12.0 SP6: Alignment/justification problems for profiles, e.g. beams moved up (or down) half of height when imported to Tekla BIMsight or Tekla Structures

Answer:
Problem has been found, depends on rules used in profile catalogues. If a fixed 12.0 version before official installation is needed it can be downloaded from address below using e.g. Internet Explorer
PDMS 12.1 version is ok.
https://dl.dropboxusercontent.com/u/16517004/TS-PDMS_Library_120SP6_2015...


Question:
Import to PDMS does not work and warning message "Parent object not selected in dialog" appears

Answer:
PDMS hierarchy needs to be selected in PDMS (Site, Zone, Stru) for select correct position in import


Question:
Tekla UDAs cannot be imported to PDMS even attribute mapping file AttributeMapping.txt used

Answer:
Attribute may not be correctly written in mapping file. Example can be seen by e.g. importing reference filefile that contains information that can be used in a model or a drawing

A reference file can contain a reference model or a reference drawing, for example.

to Tekla and inquiring reference object in Tekla.
For example when PROFILE and NAME attributes added in Settings tab page of PDMS export dialog the mapping syntax in file is
Project.PROFILE;String;:TEKLAPROFILE;String
Project.NAME;String;:TEKLANAME;String
when :TEKLAPROFILE is the UDA name in PDMS. In PDMS export application "Project" is the fixed prefix in front of UDA name
Also important to create UDA name in PDMS separately


Question:
 Ifc change management application does not work properly in Tekla side when trying to compare two revised reference models

Answer:
In PDMS side revision check will use two files exported from Tekla. And also in Tekla side revision check will use two files exported from PDMS.
So if wanted e.g. to check modifications done in PDMS side workflow is that export file1 in PDMS side (e.g. immediately after importing from Tekla)
and then after modifications export file2 and use those file1 and file2 in 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.

change management application in Tekla side.
Recommended workflow practice anyway is that (after first export from PDMS to Tekla) do structural modifications in Tekla side or even start in Tekla


Question:
Integer type of UDA attributes can not be transferred to PDMS

Answer:
In version _13_ if attribute is set to be a string in mapping, only the string attribute in IFC is considered.
Integer types could not be mapped at all. This is fixed in new _14_ version


Question:
Problem to install application to other path than c:\TS_PDMS

Answer:
Installation copies folder (files) to c:\TS_PDMS. If needed other path place copy folder TS_PDMS to desired place. And edit DesignAddins.xml to use correct path.


Question:
Modeling started in PDMS/E3D side but  modified members from Tekla not correctly updated in PDMS/E3D (e.g. new members created instead of modification)

Answer:
Exported model name from Tekla needs to be same as FRMW name in PDMS/E3D. Import needs to be done in FRMW level (and not e.g. in STRU level)
NOTE: Could be that by accident same initial_GUID attribute value modified to other Tekla member. See release notes 28.12.2015 and how this can be prevented
Also e.g. a check report can be created and used for verifying above situation


Question:
Polybeams (e.g. railings) from Tekla  not imported correctly to PDMS

Answer:
Newest Tekla side export applications can export polybeams also as an extrusion format. This means polybeampart of a certain shape that is created as a continuous chain of beams passing through points that the user picks

The segments of the polybeam are straight, but segment intersections can be curved. For example, a beam that follows a zigzag line is a polybeam.

profile needs to be mapped in PDMS/E3D, otherwise it is not imported. This can be seen in log file when importing to PDMS/E3D.
For non polybeams members PANE type is used in PDMS/E3D if mapping does not exists. But for polybeams mapping needs to exist. For TS21.1 versions a new PDMS/E3D side link version (28.12.2015) needed


Question:
Rule based mapping does not work for IPE profiles in PDMS side. Library profiles not found

Answer:
For IPE profiles extra colon needs to be used in case of rule based mapping to library profiles. So e.g.
IPE:H;DIN-SPEC/IPE:H -> parametric profilepredefined profile whose cross section dimensions the user can change by using parametric variables


IPE:H;:DIN-SPEC/IPE:H -> library profile


Question:
Bended objects (curved elbows of e.g. PDMS/E3D pipes) are missing when importing to Tekla

Answer:
Check PDMS catalogue. Obstruction levels of bends and elbows need to be same in PDMS catalogue, otherwise elbows may not be transferred correctly from PDMS/E3D to Tekla


Question:
Error happens when trying to import file to PDMS/E3D

Answer:
Also write permission (not only read) is needed because new hierarchies (e.g. FRMW) may be created


Question:
How to use company specific hierarchies ?

Answer:
Hierarchies ZONE,STRU,FRMW,SBFR are fixed but company specific between SITE and ZONE  can be handled manually and below ZONE in a normal way with new link version


Question:
GENSEC (e.g. polybeam handrails) members do not disappear in PDMS when deleted in Tekla

Answer: 
TEKLA-UDAs (:TEKLA_GUID, :TEKLA_IFCGUID, :TEKLA_VERSION) need to be added also to GENSEC element types (not only SCTN, PANEL).
This is automatically fixed in 17.1 version installation, file TS_INTEROPERABILITY_UDA.DATAL. In previous installations need to modify manually or use 17.1 version file


Question:
In some cases if only rotation (part moved by rotation) changed in TS modification of part not noticed and not done in PDMS side

Answer:
PDMS side import will check TS side exported attributes (and also profile, material) when checking if part modified. Center of gravity attributes are included but if only rotation changed so that cog is similar then need to add also bounding boxrectangular border with the smallest measure within which all the selected points that position the model objects lie

In Tekla Structures two-dimensional bounding boxes are used in drawings and three-dimensional bounding boxes in models.

extreme values in TS side export. So add to Export to Aveva / Settings tab page next attributes: BOUNDING_BOX_MAX_X, BOUNDING_BOX_MAX_Y, BOUNDING_BOX_MAX_Z, BOUNDING_BOX_MIN_X, BOUNDING_BOX_MIN_Y, BOUNDING_BOX_MIN_Z. Then modification will be found because some of extreme values will be different. We still need to verify that this really is a solution


Question:
Import to E3D does not succeed. Error message appears

Answer:
We have problems with different library dll version files and not yet been able to solve it. When solved it will be informed
 


Question:
UDA (template) values like WEIGHT (or e.g. hierarchy definitions) cannot be exported for IfcDescreteAccessories types of members.
NOTE: This is fixed in 2016i.3.1 and 2016.5.1 versions

Answer:
In Aveva_Psets.xml file which Export To Aveva applications creates when started and uses is an error that IfcDescreteAccessories tick box is off . This can be fixed by opening export to IFC command dialog and then open Additional Property Sets "Aveva_Psets" and modify and save after adding tick boxes ON also for IfcDescreteAccessories similar like in e.g.IfcBeam. Note that this needs to be done for property sets Tekla,Hierarchy,Project. Export to Aveva application uses Aveva_Psets.xml file from 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.

and under subfolder AdditionalPsets
NOTE: This is fixed in 2016i.3.1 and 2016.5.1 versions
NOTE: In old projects (models) an old/existing Aveva_Psets.xml file can be used and there tick box can be wrong and so need to be changed.
 


Question:
Sloped slabplate that represents a concrete structure

In Tekla Structures, a slab is created by picking three or more points.

Slab may be part of a floor, for example.

not imported correctly to PDMS

Answer:
Given dz1,dz2 (chamfer) or (horizontal line) cut values not correctly used when importing to PDMS. In sloped slab cases attribute Brep needs to be given/defined as Ifc export type in the slab object (User-defined attributes and IFC export tab page)
Also using polygon cutcut that is defined by a polygon

for horizontal cut (not line cutcut that is defined by a cutting line

) to handle slope works ok - then also Auto option for Ifc export type can be used 
 


Question:
Import to E3D does not work, error message appears

Answer:
There is a problem in current E3D installation. Problem seems to be solved now.
Our plan is to create next 18.1 link version soon (hopefully in about 2 weeks time) and then also release the E3D2.1 version.
If you need/want the link for testing, below is a (unofficial) link. Password for zip file is tekla
https://dl.dropboxusercontent.com/u/16517004/TeklaStructures-E3D_Interop...
 


Question:
Beam end cuts and holes not properly exported from PDMS using new 18.1 link version

Answer:
There is a change in new 18.1 link version which does not work properly. It will be fixed in coming (soon) 19.1 link version.
 


Question:
Error message "Duplicate IFC guids in model, see log file" appear when trying to import to PDMS/E3D

Answer:
There are members in PDMS/E3D which have same Tekla IFC Guid numbers. This check done on purpose and only unique number for each member allowed, otherwise revision import may not work properly. Duplicate number can appear when PDMS user manually copies member imported from Tekla. Then also IFC guid number copied. User needs to check log file and delete Tekla (Guid) UDAs from manually copied members. PDMS macrosaved series of actions that includes instructions for a program

Macros are located in the applications and components catalog. They are recorded or created manually and stored as .cs file in a folder defined with the advanced option XS_MACRO_DIRECTORY.

Macros can, for example, be used for creating drawings or reports.

Macros are sometimes used to run an application.

could be created to do this. After that import works ok.
 


Question:
Using new 19.1 link version in PDMS side in Tekla interoperability dialog link rows colored as yellow even no updated file exist

Answer:
This is an error which hopefully can be fixed soon. This happens after PDMS session saved. So at the moment manual checking needed for investigation of existing of updated files. Anyway it does not matter if same file imported twice.
 


Question:
Import to PDMS/E3D does not succeed and error message appear in dialog: "Aborted due to duplicate IFCGUIDs in model, see log file"

Answer:
Member(s) imported from Tekla have manually copied in PDMS/E3D. Then also Tekla GUID number UDAs copied. These numbers are used for checking purposes in revision cases and so need to be unique for every member. So no duplicates allowed. There is no way in PDMS/E3D in copying to prevent UDAs copying. So user needs to manually delete Tekla UDAs from copied members. In log file all duplicate members are listed and so can be easily selected. Smallest id number is most probably the original member imported from Tekla. Others are manually copied. Best to create a "macro" which deletes Tekla UDAs if members imported from Tekla used also for manual copying in PDMS/E3D.
 


Question:
Member(s) exported as Brep format not imported to PDMS/E3D (as POHE members)

Answer:
Error found in 19.1 version and a new version 20.1 is needed. Target is soon. Brep members exported also to one separate dgn file inside tczip file (e.g. 7-Zip program can be used for extracting) and at the moment dgn file can be imported to PDMS/E3D.
 


Question:
Import time to PDMS is long. Does some extra things ? Also batch import is slow and seems to do something extra ?

Answer:
Checking for duplicate TEKLA_GUIDs done for all SITEs in PDMS and this took extra time. This is fixed in new link 21.1 version (also batch import) with new option TeklaDuplicateGUIDsCheckForImportSpecificAvevaSITEsOnly (default=True). See release notes for more info.
 


Question:
Import to PDMS/E3D does not succeed and error message "Selected hierarchy is not STRU/FRMW" appear

Answer:
There are two ways to export from Tekla: using hierarchies or not using hierarchies. If hierarchies not used then in PDMS/E3D side in Design Explorer/Model Explorer a STRU or a FRMW need to be selected before importing. See more info from instructions
 


Question:
Import to PDMS/E3D does not succeed

Answer:
Simple reason for this can be that exported file name from Tekla (.tczip extension) is modified. It is not allowed. If new/other name needed then a new export in Tekla side needed to be done using Export To Aveva application
 


Question: 
Decimals not taken into account in tube profile mapping file, e.g. tube diameter 101.6 mm in Tekla and 1016 mm in PDMS

Answer:
Windows setting for decimal symbol (dot or comma) might effect to this. In case of problem a comma instead of dot could be used in PDMS side like
RO101.6*6.3;DESPAR-SPEC/Tube_with_design_parameters:101,6:6,3:0


Question:
Update (import) to PDMS/E3D does not work and message "nothing to import, aborting ..." happens

Answer:
If sorting used (e.g. by version in Tekla Interoperability dialog) before pressing Import-Update the error happens in 21.1 (2.1) link version.
Rearranging the dialog gave mismatch between dialog rows and models and this caused the error. It will be fixed in next official version but now do not use sorting
 


Question:
Tekla UDAs cannot be imported to PDMS even attribute mapping file AttributeMapping.txt used

Answer:
UDAs need to be defined as a string type even UDA is defined in Tekla side as integer or double format. So e.g. Tekla Common.Phase UDA defined in Tekla side as integer and need to write to AttributeMapping.txt following
Tekla Common.Phase;String;:TEKLA_STR_1;String
where :TEKLA_STR_1 is the UDA name in PDMS/E3D side
 


Question:
Profiles rotated after importing to PDMS when 22.1 link version used

Answer:
This kind of rotation error noticed and it happens if  profile mapping file used and not e.g. European DIN-SPEC mapping. We are working to fix this but at the moment one workaround is not to use mapping file. Then members are correctly positioned  but PANE members before final fix available.
 


Question:
Imported members to PDMS/E3D will be rotated (bangle 180).
           

Answer:
If SITE or ZONE or STRU position level set in PDMS/E3D side as non zero. E.g. SITE pos set to E0 U0 U100000. 
This error happens in 23.1 (PDMS) and 9.1 (E3D) versions and will be fixed to 24.1 (PDMS) and 9.1 (E3D) versions. Fixed preliminary versions (library files) available and can be sent if needed


Quick feedback

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

Comments

by KEVIN TA

Have you been in this error problem before? I got this error message during Export to Tekla from E3D. Please help:

ERROR [ExportModelClick] - Could not load file or assembly 'Tekla.Technology.ManagedIfcLib, Version=1.16.0.0, Culture=neutral, PublicKeyToken=a70cba4ef557ee03' or one of its dependencies. The system cannot find the file specified.

by Petri Heinonen

Hi Kevin

We have had problems with E3D installation (library files incompatibility because PDMS and E3D use different libraries) but looks like we have solved the problem now.
Our plan is to create next 17.5 link version soon (hopefully in about 2 weeks time) and then also release the E3D2.1 version.

If you need/want the link for testing, below is a (unofficial) link. Password for zip file is tekla

regards Petri

https://dl.dropboxusercontent.com/u/16517004/TeklaStructures-E3D_Interop...

by Pietro Rocca

Hi, we noted some problems in the export process PDMS12.1 works correctly E3D2.1 seems no. PDMS during the first export process generates 2 different "tcifc" files, the 1st with the site name (as per our setting) and the 2nd with the site name followed by the export date and time. The "link" folder contains a folder with the site name and a file "settings" linking the the first file with the file with tha date and time in his name. In the subsequent export PDMS create another file with the site name followed by the date and time of export. Importing in Tekla the 1st file (not followed by the date and time of export) tekla can take trace of the change history because that file is updated with the information changes. Instead E3D during the first export process export only one file with the site name (as per our setting) followed by the date and time of export. In the subseguent export process E3d export always one file followed by the date and time of export, importing in Tekla the first file tekla could not take into account any change becasue the file is always different.

by Petri Heinonen

Hi, the purpose of export files with time stamp and without is that it would be easier to handle updates and revisions in Tekla side when same name of reference file can be used. Purpose is to have similar versions of PDMS and E3D but we have had some problems with E3D installation which is now solved. Earlier E3D test version probably had only one exported file with time stamp and so was different to new PDMS link versions. Today added a new 18.1 link version to Tekla Warehouse and target is to have E3D version next Friday 27th January.
Regards Petri

by Björn Kübler

Hi, does everyone have the same Problems that PDMS 12.1.SP4 Crash with a fatal error when using the Interoperability 18.1 and 19.1?
Today we use the Version 17.4, but some elements are not exported to the ifc file.

by Petri Heinonen

Hi
Crash probably related to changes which handle also situation when PDMS user did not save PDMS session after importing Tekla File. There were some errors related to this item in link versions 18.1 and 19.1. Now in current available 20.1 versions these should be fixed. And also Brep members correctly imported to PDMS. So if still issues exist I think best to send tczip file (Tekla model .db1 also needed if object really missing in ifc-file) directly to me (petri.heinonen@trimble.com) for testing purposes. But I think it is ok after installing new 20.1 link version.
regards Petri

by Le Viet Anh

Hi, our company is doing Tekla modelling for fabrication purpose, and sometimes we need to import PDMS model from design firm for reference. But I encountered these 2 issues below:

1. Reference model exported from PDMS is not match in right position with our Tekla model (I am very sure that both PDMS model and Tekla model were modelled in a correct location).
2. Structural tubular profiles are not correctly converted to native Tekla profiles as expected. E.g: /API_406.4x12.7_CZN in PDMS should be converted to Ø406.4*12.7 in Tekla, but somehow it becomes CF-CHS406.4*12.5 . I already updated the catalogue MappedProfiles to include this line "API_406.4X12.7_CZN;Ø406.4*12.7" but it didn't work.

Please help to figure out what could be a reason for that.
Thanks!

by Petri Heinonen

Hi, When PDMS (reference .tczip format) model imported to Tekla user defines where to locate the model. So pick origin for reference model. I suppose now origin point is not the same as in PDMS. In Tekla version 2017 and later also "base point" can be defined beforehand and used in import. Then no picking errors happen because predefined base point names can be used. Reference model can be also moved to correct location if by mistake put to wrong position.
Mapping question: Tekla will check if reference profile is similar to profile in Tekla catalog and if exactly similar then catalog profile mapped and used. But if not similar (like I suppose in this case) then another user defined profile created like I think in this case. So editing mapping file does not help. One reason for this kind of functionality is that otherwise situation in PDMS can be different to situation in Tekla because profiles can have different dimensions. Easy way to fix this manually is to select certain user defined profiles in Tekla and use modify command and change profiles to desired name/size.
Exported file .tczip file can also be sent to me (petri.heinonen@trimble.com)
regards Petri