cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Provide capability to compare the CAD assembly model structures to identify changes from previous revisions. This is required for user adoption and efficiency.

Provide capability to compare the CAD assembly model structures to identify changes from previous revisions. This is required for user adoption and efficiency.

Problem Statement(s):

Cannot compare different versions of a CAD assembly structure within Windchill.

·         System does not allow the engineer to see the difference in the CAD Structure from one version to the next. 

·         Desire is to see parts and sub-assemblies that have been added, removed, restructured, or different versions of components that are used in the CAD structure.

Cannot compare the structure of a CAD assembly to another non-identical CAD assembly within Windchill.

·         Engineer is unable to investigate the differences in 2 different CAD assembly structures. Desire is to see parts and sub-assemblies that have been added, removed, restructured, or different revisions that may exist in the structure.

Cannot compare different configurations of a CAD assembly structure within Windchill

  • Engineer is not able to do      comparisons of the various configuration filters (i.e. as-stored vs.      latest)

Background

When the Owner Link is not used to drive structure into WTParts, comparisons using part structure driven from CAD is not available. Within Bose, there is currently no plan to drive structure from EPMDocument assemblies to WTParts.

When engineering assemblies are changed in CAD, the functionality to see how the changes have occurred and what is different between versions doesn’t exist.  Currently there are methods to compare Parts from one version to the next but not a CAD structure that is at different versions.

If structure isn’t being driven into the WTPart objects, there is no visibility into the changes of the CAD structure over the assembly history.


Use Case Scenarios and Requirements:

Version to Version Assembly Structure comparison

Configuration Analyst is unable to check/verify the quality of the data used in a CAD assembly (i.e. we do not want down rev CAD data used in an assembly, nor do we want unreleased latest CAD data in an assembly being released unless it’s being released at the same time).

·         See how the structure is different between versions

·         Determine what parts and sub-assemblies have been:

o    Added

o    Removed

o    Revised

o    Restructured

o    Qty Differences

·         Be able to select standard filtering criteria such as Latest and As-Stored to compare between.

·         Functionality for browsing structure differences would be similar to the part comparison tool that exists

Different CAD Document Number Assembly Comparison

·         Be able to select the CAD Documents and specific versions of each assembly to compare .

·         Look at assemblies that aren’t from the same parent CAD Document number against each other.

·         Determine what CAD Document and sub-assemblies have been:

o    Added

o    Removed

o    Revised

o    Restructured

o    Qty Differences

·         Be able to select standard filtering criteria such as Latest and As Stored to compare between.

·         Functionality for browsing structure differences would be similar to the Part comparison tool that exists

CAD Data on a change needs to be validated against released data

  • Validation of CAD configurations      being released on a change must be performed to ensure CAD data does not      include working copies of components that are not being changed in the      final as stored configuration of the assembly or of a prior released      version. 
  • This will help to ensure the      quality of the CAD data being released.  Specifically that the assembly only has non-released components for      CAD documents that are actually being changed.
  • Comparison of the As-Stored      configuration to the latest Released version shall be selectable.
  • Highlighting of components      that are not the same shall be shown.

·         Determine what CAD Document and sub-assemblies have been:

o    Added

o    Removed

o    Revised

o    Restructured

o    Qty Differences

  • Flagging of components that are released and have a pending action.
    • On another change
    • In Work
    • etc.
3 Comments
GregoryPERASSO
Aquamarine

Hello,

duplicate with this Idea. 

Ability to compare two CAD Documents structure

Please vote and add your detail requirements.

Thanks,  regards

Gregory

RahulHRaut
Visitor

Thanks Gregory. I voted for it.

PTCModerator
Emeritus
Status changed to: Archived