Importing An Assembly Into Teamcenter – Part Family Member Options
The following article records how Part Family Templates and/or Part Family Members are treated when importing assemblies into Teamcenter based on the following two Teamcenter Integration for NX Import/Export Assembly Part Family Member Customer Defaults:
· Include Part Family Member Template part
If a part family member is encountered during an import or export operation, this option determines whether or not its template part should be included in the operation
· Ignore Part Family Member – Include Template Part
This option determines whether or not clone based import and export operations should ignore any part family member encountered during the operation. When this check box is turned on, the template part will be included in the operation instead.
The following steps were all completed with Generate Missing Part Family Members enabled in the Assembly Load Options. The assembly imported into Teamcenter contained two components, one of which was a Part Family Member.
1) Ignore Part Family Member – Include Template Part
· The Part Family Template was imported with the assembly
· On sending the assembly from Teamcenter to NX the following information is displayed:
Important information during successful load
ASSY/A The load was successful. However, there are some points you should note regarding potential problems encountered
during this process. Please read the following list carefully:
Auto regeneration of missing part family members
The following part family member could not be located in the database
PFM001/A;
This part family member has been regenerated automatically
The Part Family Member was generated on-the-fly when the assembly was sent to NX and will be saved in the Part Family Member’s folder of the Part Family Template in Teamcenter when saved in NX.
2a) Both Options Disabled – Treat Parts As Lost
· With both defaults unchecked the following dialog is raised asking the user how they want to treat the Part Family Member encountered during import. Both options are covered below:
· With Treat Parts As Lost selected, neither the Part Family Template nor the Part Family Member was imported. Therefore, having sent the assembly to NX the checkbox for the Part Family Member in the Assembly Navigator was empty. Clicking the checkbox to load the component raises the following dialog (as expected):
2b) Both Options Disabled – Turn Family Members into Normal Parts
· With Turn Family Members Into Normal Parts selected, the Part Family Member is imported.
Attempting to create a new Part Family Template from this member is successful, proving that the relationship to the original Part Family Template has been broken and the member was converted into a normal part.
3a) Include Part Family Member Template Part – Treat Parts As Lost
· Similar to the previous case the user is prompted how they want the import operation to treat the Part Family Member. Since the Part Family Template is not being imported the user has the same two options:
· With Treat Parts As Lost selected only the Part Family Member was imported
· When sending the assembly from Teamcenter to NX the following information is displayed:
Important information during successful load
ASSY/A The load was successful. However, there are some points you should note regarding potential problems encountered
during this process. Please read the following list carefully:
Auto regeneration of missing part family members
The following part family member could not be located in the database
PFM001/A;
This part family member has been regenerated automatically
· On making the PFM the work part the following dialog is raised, so the system recognizes that the component is still a Part Family Member:
3b) Include Part Family Member Template Part – Turn Family Members Into Normal Parts
· With Turn Family Members Info Normal Parts selected the Part Family Template and the Member are imported but the Part Family Member is severed from its original Part Family Template. Therefore attempting to make a new Part Family Member of the imported Part Family Member is allowed.
4) Both Options Enabled
· With both defaults checked the Part Family Template is imported.
· When sending the assembly from Teamcenter to NX the following information is displayed:
Important information during successful load
ASSY/A The load was successful. However, there are some points you should note regarding potential problems encountered
during this process. Please read the following list carefully:
Auto regeneration of missing part family members
The following part family member could not be located in the database
PFM001
This part family member has been regenerated automatically
As with case 1, the Part Family Member was generated on-the-fly when the assembly was sent to NX and will be saved in the Family Members folder of the Part Family Template in Teamcenter when saved in NX.
Benjamin Broad