Pdms Installation
Nayme Cutforth
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 folder 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 UDA'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:
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/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:
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 file 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 ifc 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:
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 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:
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:
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 box 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:
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 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 slab 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 cut for horizontal cut (not line cut) to handle slope works ok - then also Auto option for Ifc export type can be used
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 macro 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.