Teamcenter - HyperMesh Integration

The Part browser, which replaces the Assembly browser in the Teamcenter-HyperMesh integration, displays all of the BOM-related information, including part/assembly hierarchy, part attributes, and representation information.

browser_part

Representation (HyperMesh session) attributes are now displayed independent of the PDM attributes. Attribute columns can be turned on/off in the Column Visibility dialog, which can be accessed by right-clicking in the Part browser and selecting Column Visibility from the context menu.

In the image above, the session attributes (PID, MID, Material, Thickness) are blank because representations have yet to be created or loaded. The corresponding PDM attributes, from the imported PLMXML BOM file, show their values from Teamcenter.

Option

Description

Create

Creates HyperMesh representation(s) via BatchMesher.

Save

Saves representations for selected part(s) based on the chosen alias and file type.

Add

Adds representations for selected part(s) based on the chosen alias and file type or from the Part Library.

When adding representations for multiple parts or part assemblies from external sources, the Add Representations dialog enables you to map and associate representation files to multiple parts simultaneously.

part_assembly_team_center_add_reps

If appropriate metadata is available in the BOM, then the alias values will be preselected. After choosing a Representation Folder, representation files will be mapped according to the Teamcenter naming convention. You can then manually select or update any of the alias and representation file values.

Indicators are displayed for each part to indicate the status of that row.

•	Skip. Any Part which does not have a mapped or selected representation.

•	OK. Alias and representation are chosen for the part.

•	Overwrite. Part already has a representation which will be overwritten by the selected mapping.

•	Duplicated. The same representation file is chosen for more than one part, or the chosen representation file is already used by another part in the same BOM.

You cannot click OK to add the representations when representations are duplicated.

Load

Load part representations from your current Teamcenter-HyperMesh session or from the Part Library.

If any of the selected parts currently have a representation loaded in the session, you will be prompted whether or not to unload them before loading new representations.

If representations are not unloaded first, incoming representations will be imported on top of the existing representations, and Load Settings will be used.

Unload

Unloads representations for selected part(s).

Delete

Deletes representations for selected part(s) from your current Teamcenter-HyperMesh session or from the Part Library.

Reload

Restores part representations to their original state.

Settings

Displays the current load settings, which are used when representations are imported.

The Teamcenter integration environment requires an additional layer, on top of the out-of-the-box Part browser behavior. When launching HyperMesh via Teamcenter, the environment will be set automatically. However, all of the integration features may be accessed by manually setting the environment.

To manually set the Teamcenter-HyperMesh environment:

1.	Locate the Teamcenter-HyperMesh custom layer in your installation. By default, the custom layer is located in <ALTAIR_HOME>\hm\scripts\br\views\modules\custom\TC, where <ALTAIR_HOME> refers to the base installation folder where HyperWorks is installed, for example C:\Program Files\Altair\HW14.0.

2.	Set the environment variable HW_CONFIG_PATH=<ALTAIR_HOME>\hm\scripts\br\views\modules\custom\TC\properties.

3.	Set the environment variable HM_CAT_CUSTOM=<ALTAIR_HOME>\hm\scripts\br\views\modules\custom\initTC.tcl.

Note:

For customer-specific customization that are above and beyond the standard Teamcenter-HyperMesh integration, set HM_CAT_CUSTOM to the init<XYZ>.tcl file, where XYZ refers to customer “XYZ’s” individual custom layer.

If HyperMesh was launched via the Teamcenter - HyperMesh Integration, you will be prompted to import updated data back to Teamcenter.

browser_part_teamcenter4

If the BOM was loaded manually, for example HyperMesh was not launched via the Teamcenter-HyperMesh Integration, then the updated PLMXML package can be manually imported into Teamcenter.

1.	Copy the exported BOM PLMXML, along with the folder(s) containing the monolithic file (if saved) and any saved/updated representations to a convenient folder accessible by Teamcenter.

2.	Select the Import PLMXML option to import the updates.

browser_part_teamcenter5

BOM selection within Teamcenter remains the same in HyperMesh 14.0 as it was in previous versions.

As in previous versions, you can directly launch HyperMesh and import the selected BOM.

browser_part_teamcenter1

The selected BOM and associated files will be exported from Teamcenter and automatically loaded in the HyperMesh Part browser, which replaces the Assembly browser used in previous versions.

Using the Pre-Processor Integration option (shown above) exports the PLMXML package to the last run folder, which Teamcenter continues to interact with until the HyperMesh session is closed. Once closed, Teamcenter prompts you to accept or reject updates. The last run folder is then automatically cleaned up.

Export the PLMXML package so that you can work on it over time by selecting the Export PLMXML for Pre-Processor option.

browser_part_teamcenter2

The resulting PLMXML BOM file, along with its associated data files, will be exported to the last data folder and can be imported directly into HyperMesh via the Import - BOM tab.

browser_part_teamcenter3

The BOM is displayed in the Part browser, which replaces the Assembly browser used in previous versions.

Export PLMXML BOMs by right-clicking on the Model part assembly in the Part browser and selecting Export PLMXML from the context menu.

You will automatically be directed to the Export - BOM tab, where the correct name and path will be set, using the lst_output.xml file name expected by the Teamcenter-HyperMesh integration.

The following fields are available in the Export - BOM tab:

Field	Description
File Type	Export BOM files as either PLMXML or UDMXML. For the Teamcenter-HyperMesh process, PLMXML will be used.
File	Path to the exported BOM file. For the Teamcenter-HyperMesh process, the file should be named lst_output.xml, and the file should be saved to the same location as the original BOM file, lst_input.xml.
Prompt before overwrite	Warns you when saving a BOM file over an existing file.
Save Monolithic file	Saves the assembly monolithic file, according to the PLMXML Master Format attribute value, while exporting the BOM.
Update Attributes to PDM	Updates PDM attributes based on part attributes prior to writing exported BOM file. Using this option assures that attribute updates made in the session will be sent back to Teamcenter.

In Teamcenter-HyperMesh, Part Libraries are disconnected by default. You must connect to a Part Library in order to access Part Library options.

The Part Library is an integral part of data management and revision control within the Part browser. By default, a Part Library is generated when the Part browser is enabled. There are two modes, unmanaged, which is local file management, and managed using the Part Library. The default Part Library is located at <user home>\AltairLibraries\2017.

Use the Part Library to manage, control, and update Major, Study, and Library Part revisions. The Part Library serves as a centralized library of HyperMesh parts, which in turn facilitates the collaboration between simulation teams both locally and abroad.

If you are not connected to a Part Library, all Part Library related options will be removed from the user interface.

In the Part browser, the Revision column displays the Major revision, Study revision, and Library Part revision. All of the appropriate workflows have entry or access points to the part library, enabling quick and easy access to previous revisions or simply generating new revisions.

•	Major Revision. Depicts a change or set of changes that have been finalized and released for further review. In most cases the Major Revision is mapped to the PDM Revision, but it can be modified by users.

•	Study Revision. Created locally to track experimental changes or prototyping changes that may or may not be published. The purpose of the Study Revision is to manage design and prototype exploratory concepts. The Study Revision can be modified by users.

•	Library Part Revision. Locally, published revision within the Part Library. The Library Part Revision cannot be modified by the user.

part_browser_revision_column

You can review and edit a part's Major Revision, Study Revision, and Library Part Revision in Entity Editor.

In the image above, the LeftOuter_A_000435_Safety.c01 part displays A,1,1 in the Revision column of the Part browser, which indicates:

•	Major Revision = A (mapped to the PDM revision, user editable)

•	Study Revision = 1 (can be any letter or numerical value, user editable)

•	Library Part Revision = 1 (library version, not editable)

A default Part Library is generated when the Part browser is enabled, and is located at <user home>\AltairLibraries\2017. You can register and connect to new libraries of your choice.

1.	In the Part browser, right-click and select Library > Libraries from the context menu.

2.	In the Libraries dialog, manage libraries.

•	Register a new library.

Click +.

b.	Enter a Library Name and Library path.

c.	Click Add.

•	Delete a registered library.

a.	Select a library to unregister.

Click -.

•	Connect/disconnect a library.

a.	Select the currently connected library, and click Disconnect.

b.	Select a disconnected library and click Connect.

part_library

In the Part browser, right-click on a part/part assembly and select Library > Sync from the context menu.

The in-session version is synced with the latest, available version in the Part Library. If the version available in the current session is out of sync with the Library reversion, use Sync to update the session version with the Part Library version.

Note: You can only sync library revisions when there is a connected library.

Study Revisions are a way to explore design space, and can be promoted to a Major Revision as required. You can assign and edit Study Revisions in the Entity Editor.

1.	In the Part browser, select a part/part assembly.

2.	In the Entity Editor, edit the Study Revisions field.

part_revision_study_edit

Part representations can be loaded from your current Teamcenter-HyperMesh or from the Part Library.

When CAD representations are loaded, components are created for the loaded CAD representations. Materials and properties, if available in the CAD file would also be created, and their values would be displayed in the Part browser columns. However, unlike the Assembly browser, the component naming conventions are not yet imposed, nor are the materials and properties created automatically at this time. This enables you to review information within the CAD files themselves prior to mesh representation creation. According to the Teamcenter-HyperMesh naming conventions, component naming and material and property handling will occur during the meshing process.

1.	In the Part browser, right-click on part assemblies or parts and select Representations > Load > from Session from the context menu.

1.	In the Change Representation dialog, Load tab, select a type of representation to load.

Representations that exist in the repository are shown in the Representations column, and their availability is indicated in the Available column.

representations_loading_1

2.	To send unavailable representations to the BatchMesher directly from the Change Representation dialog, select Batch Mesh Unavailable.

Note:

Available representations will also be loaded when you click OK if Batch Mesh Unavailable is selected.

3.	Optional. To save the representations to the Part Library select the Save to Library checkbox.

Click OK.

5.	In the Confirm Load Representation dialog, click:

•	Load All. Loads all available representations into the current session for selected parts.

•	Skip Loaded. Ignores representations that are already loaded for selected parts.

As representations are created and saved to the repository they are displayed in the Available Representations pane.

After importing a BOM that has representations saved in the Part library, you can load the saved representations.

1.	In the Part browser, right-click on a part/part assembly and select Representations > Load > from Library from the context menu.

2.	In the Change Representation dialog, Library tab, select representations and click OK.

representation_loading_from_library

The selected representations are loaded to the Representation folder on the file system. Similarly, every time a BOM is imported, files are loaded to the Representations folder, if you retrieve them from the Part Library.

1.	Create mesh representations by right-clicking in the Part browser and select Representation > Create from the context menu.

2.	In the Change Representation dialog, Create tab, select the NVH_Standard_8 representation.

Each representation is uniquely identified by its alias and file type. For example, “NVH_Standard_8/HyperMesh” and “NVH_Standard_8/Nastran” representations.

The appropriate representation will automatically be selected, based on the available PLMXML metadata: discipline, mesh representation, and mesh density. If the appropriate metadata is unavailable, then you can select the desired representation type to create. In the Change Representation dialog, Create tab, only HyperMesh representations can be created.

Per the current Teamcenter-HyperMesh integration rules, only one representation per file type is allowed per part. This means that you can only have a single HyperMesh file type representation, Nastran file type representation, CAD representation, and so on for each part. For example, if you create a NVH_Standard_8/HyperMesh representation and then subsequently create a NVH_Coarse_15/HyperMesh representation, the NVH_Coarse_15/HyperMesh representation will become the only HyperMesh representation for the given part.

browser_part_teamcenter15

3.	Optional. To save the newly created representations to the Part Library select the Save to Library checkbox.

4.	Click OK. BatchMesher is invoked, and meshes are created using the appropriate batch meshing parameter and criteria files.

The parameter and criteria file mappings are configurable based on the batchmesher_config.cfg file available in the installation.

As part of the post-batchmeshing process, each part’s components are created, using the Teamcenter-HyperMesh naming convention. In addition, the loaded representation (NVH_Standard_8 in this case) is displayed, and the component ID (CID), property ID (PID), Material, and Thickness are created, per the values available in the PLMXML BOM.

browser_part_teamcenter13

Select a part or parts to update, then right-click and select Representations > Update from the context menu to:

•	Rename the selected parts or part's component (or create if it does not already exist).

•	Create a material based on PDM Material and PDM MID.

If a material of the given ID already exists, then it will not be overwritten or recreated in order to avoid overwriting any existing material properties.

Only linear attributes are updated. Default steel attributes are used with the following unit system: millimeter, second, tonne, and Newton.

•	Create a property based on PDM PID and PDM Thickness*.

If a property of the given PID already exists, its thickness will be updated based on PDM Thickness; however, the existing property will not be recreated. Only relevant metadata will be updated in order to avoid overwriting any existing property card values.

*If the PDM MeshFlag attribute is set to SMT (Solid Mesh Tetra) or SMH (Solid Mesh Hexa), than a solid card image will be assigned to the property.

Sync PDM metadata (PDM PID, PDM Thickness, PDM Material, and PDM MID) based on a selected part or part's metadata (PID, Thickness, Material, MID) by right-clicking on a selected part or parts and selecting Representations > Sync Metadata from the context menu.

*When a part has multiple properties, only the first property will display in the PID PDM field when you select Sync Metadata.

You can save the HyperMesh file at any time. The HyperMesh session stores all of the BOM-related information, including hierarchy, metadata, and representations. The original PLMXML BOM file is no longer required to load, view, or modify any of this information.

1.	From the menu bar, click File > Save > Model.

2.	In the Save Model As dialog, save the model to your working directory.

1.	From the menu bar, click File > Open > Model.

2.	In the Open Model dialog, open the recently saved HyperMesh model.

All of the BOM-related information is retained with the most recently loaded representations loaded in the session.

browser_part_teamcenter14

Teamcenter - HyperMesh Integration

Teamcenter - HyperMesh Integration

Teamcenter - HyperMesh Integration

Create

Save

Add

Load

Unload

Delete

Reload

Settings

File Type

File

Prompt before overwrite

Save Monolithic file

Update Attributes to PDM