Model Update

Compare and update a current HyperMesh session with an incoming model and generate comparison results.

Use the Model Update functionality to compare the session model with an incoming (updated) one. The session is updated based on the comparison results, and part sets and reports are created.

Open the Model Update Tool

From the Assembly ribbon, click the Model Update tool.

The Model Update dialog opens.

Import File: Provide the file path for the incoming .hm model.
Filters: Enter keywords to filter both sessions and incoming parts. Provide keywords from a table/list or by selecting a .csv file.
Removed Parts: Keep or delete parts that exist in the session and do not exist in the incoming file.
Revisions: Specifies the revision rule to be compared. There are three rules available: Major, Study and Library revision. The default option is Major revision.
Reports: Select the folder where the reports will be saved.

Update Process

Model Update is a process to compare and review changes between two models.

This functionality compares parts by Revision (Revised or Carryover) and detects differences and changes in the following categories: Topology, PDM data and Metadata. After the comparison, the session’s model is updated to match exactly the imported model. The report provides additional information on filtered, new and removed parts between the two models.

Model Update is based on four basic steps:

Compare revision for all of the parts.
Compare the revised parts for topology changes.
Compare the revised parts for metadata changes.
Compare the revised parts for PDM changes.

After the Model Update process, report file and part sets are created to review the changes.

Revision Comparison

The first step in the Model Update process is the revision comparison. Based on the selected comparison rule:

Every part that has a changed revision will be marked as Revised, and it will be compared.
Any part that has exactly the same revision will be marked as Carryover and will be skipped from comparison.

Every revised part will be compared with the incoming one for topology, metadata and PDM changes, and reports and part sets will be created based on the results.

Revision Comparison Rules

There are three rules for revision comparison. By selecting one of these rules, you define how comparison will be done and which parts will be marked as Revised or Carryover.

Major revision (default option): Only the Major revision will be compared. Parts that have different Major revision will be marked as Revised and will be compared.
Major and Study revision: Major and Study revision will be compared. Parts that have different Major or Study revision will be marked as Revised and will be compared.
Major, Study and Library revision: All three revisions will be checked (Major, Study and Library revision). Parts that have different Major, Study or Library revision will be marked as Revised and will be compared.

Note: Based on the selected rule, all of the parts that have the same revision will be marked as Carryover and will be skipped from comparison. Only parts with changed revision (Revised) will be compared.

Topology, Metadata and PDM Comparison

After the revision comparison finishes, all of the parts are organized in two major categories, Revised and Carryover. All of the revised parts will be compared for Topology, Metadata and PDM data changes.

Topology: Comparison to detect changes in the parts. Parts will be split into categories based on match percentages, allowing you to review parts by matching values.
Metadata: Comparison to detect changed or added Metadata values from the incoming model.
PDM data: Comparison to detect changed or added PDM data values from the incoming model.

Filtered, New and Removed Parts

In addition to comparison, the two models will be checked for parts that appear only on the session’s model or only on the incoming one. You also have the option to exclude some parts from comparison.

Filtered: This functionality provides the ability to filter some parts and exclude them from comparison.
New: Parts that exist in the incoming model but do not exist in the session model.
Removed: Parts that exist in the session but do not exist in the incoming model.

Update Session

After the completion of all of the above, the session will be updated to match the incoming model. Based on the results, part sets will be created for each category to review the changes.

Reports

When Model Update finishes, HTML reports will be created. These reports will help you to track and review all of the changes made in the model in an organized way. Reports present a comprehensive summary of comparison results on a structured page, where you can navigate through categories and find useful information about the model.