Teamcenter and IPEM – Creo Integration

Teamcenter and IPEM – Creo Integration

Teamcenter, as a PLM (Product Lifecycle Management) system, can integrate into a variety of CAD systems. This gives the end user the ability to stay and use the tool that they are accustomed to while utilizing Teamcenter’s features. Each integration has its own server and client setup, sometimes it’s necessary to customize the install to match your business needs. This quick blog will cover some preference changes to the IPEM – Creo integration for Teamcenter.

The IPEM client installation wizard will install the necessary files needed to connect Cero to Teamcenter. The install directory that will have the two files needed to make the customization are:

  • Ipem.xml
  • ipem.properties

Note: It is alwasy a good idea to have a third party text editor, aside from Notepad. A good program to use is Notepad++.

JT translations of Cero 3D models are sometimes necessary because non-CAD users, or users who do not have a Cero license, have no way of interacting with the 3D model. JT files are “a 3D model format developed by Siemens PLM Software that was designed as an open, high-performance, compact, persistent storage format for product data. JT files are used for product visualization, collaboration and data sharing.”

The IPEM integration can automatically convert a Cero file into JT format when a model is saved to Teamcenter. Once the JT translator program is installed, some changes need to be made on the two files mentioned above.

Note: It is best practice to create backups of any files before making any modifications.

In the Ipem.xml file there is a section <auxiliary_file_map>. This is where installers would make one of the necessary edits. The example below shows an Ipem.xml file without any customizations.

This example shows where the JT customization was added to the file –

<auxiliary_file cad_type=”PRT” direction=”both”>

            <pdm_location named_ref=”AccelFile”/>

            <file_name pattern=”{cad_name,lower}.xpr”/>

        </auxiliary_file>

<jt_file action=”translate” cad_type=”PRT”/>

Note: Keep the edits in the syntax of the file, and ensure that the attributes are entered correctly.

Now, save and close the file.

Next, and edit needs to be made to the Ipem.properties file. Search the keyword “JT” and you will find this entry:

eai.jtenabled

The green text gives context to what and how the property is used in IPEM. In this case, changing the value to “true” will be automatically generated when a 3D Creo model is saved to Teamcenter. It will use the Ipem.xml file for the auxiliary file map.

Note: The value is case sensitive at times, and it is best to use the values that are presented in the file.

Now, when a model is saved in Creo, IPEM will automatically have the preference for “Save JT Files” already checked, and will generate the JT file.

Another area to customize are which properties are editable when performing a “Save-As” or “Save” operation in IPEM. In an OOTB (Out of the box) installation some attributes may no longer be updated (changed) while saving a new version of an existing revision. If you need to restore this capability, then a new set of attributes can be added to the Ipem.xml file.

Note: It is best practice to create backups of any file before making modifications.

The save_enabled_properties map attribute controls which properties are editable in context of a “Save-As” or “Save” operation.

For example, for an Item you would add:

<save_enabled_properties>

<item_type name=”Item”>

<properties>

<pdm_property name=”Item.object_desc”/>

<pdm_property name=”Dataset.object_desc”/>

</properties>

</item_type>

</save_enabled_properties>

This would allow users to change the Item and Dataset descriptions in the Save dialogue in IPEM.

And if there is a need for custom item types as well, then those can be added to the same attribute:

<save_enabled_properties>

<item_type name=”Item”>

<properties>

<pdm_property name=”Item.object_desc”/>

<pdm_property name=”Dataset.object_desc”/>

</properties>

</item_type>

<item_type name=”SWT_TestItem”> 

<properties> 

<pdm_property name=”Item.object_desc”/> 

<pdm_property name=”Dataset.object_desc”/> 

<pdm_property name=”Item:SWT_TestItem.swt_name”/> 

<pdm_property  name=”ItemRevision: SWT_TestItemRevision.Form: SWT_TestItemRevisionMaster.user_ data_1″/> 

</properties> 

</item_type> 

</save_enabled_properties>

 

These are just some of the customizations that can be done to the IPEM after the OOTB installation is complete. For more information on the server and client-side versions of IPEM, see the:

  • Teamcenter_Integration_for_Creo_12x(or11x) AdminGuide
  • Teamcenter_Integration_for_Creo_12x(or11x) InstallationGuide
  • Teamcenter_Integration_for_Creo_12x(or11x) UserGuide

These files can be found in Creo integration download from GTAC, or you can contact Swoosh Support for a copy of these guides.

 

Enjoy!

Post by Sam Estrada

Leave a Reply

Your email address will not be published. Required fields are marked *