Assembly Browser

The Assembly Browser is an object oriented modeling environment where the fundamental entity is the module entity.

A module is a HyperMesh entity used to represent subsystems of an assembly. It can have multiple representations and related metadata such as ID ranges, tagpoints and states. Modules can be created from the Assembly Browser by right-clicking and selecting Create Module. The Edit Module is used to manage the various aspects of the module definition, which can be accessed from the Assembly Browser by right-clicking and selecting Edit Representations. A module based assembly definition can be saved in an .xml file.

To open a previously created assembly, you need to import an .xml file. This should be an assembly database file that you exported from the NVH Director.

The Assembly Browser includes the following views:

Base View

This view displays every entity within the hierarchy, the display status and the Analysis status.


Figure 1.

File View

The File View display shows the Export status and the associated .xml file path for each module.


Figure 2.
This view also includes the Preserve/Merge option.
Preserve
Saves an assembly .xml file along with a set of nested subassembly files (similar to include files).
Merge
Saves the assembly file with all subassembly files merged into it.
Subassembly files can be specified by clicking the ‘-‘ icon in the XML file path column. Navigate to the desired folder and specify a file name. Export of subassembly files can be controlled by checking/unchecking of the checkbox in the Export column.
Note: The Save XML option is enabled only in the File View to ensure that you are aware that the subassembly files are over-written.

ID View

The ID View shows the summary of ID ranges assigned to modules with representation in the assembly hierarchy. It also shows the assignment and conflict status in terms of Intra-Module and Inter-Module flags. Intra-Module = Yes means IDs of all entities in the module are within assigned range, or else Intra-Module = No. Inter-Module = Yes means there are no ID conflicts across modules, or else Inter-Module = No.


Figure 3.

Property View

The Property View shows the mass and damping of modules with representation in the assembly hierarchy. Mass is also shown for the root module and parent modules.


Figure 4.