Reuse Library - manage similar (non parametric) nx-parts 1

[wogo62]

We've several Step-components imported to NX (native).
These parts are none-parametric (only stupid 3D-bodies) and each part has it's own size.
Is it possible to manage these parts via reuse library and spreadsheet-handling like other standard part nuts, bolts, etc. ?

Regards
Wolfgang

 

[PSI-CAD]

Hi Wolfgang,
What do you expect in spreadsheet in case of non parametric parts ?

Regards
Didier Psaltopoulos

http://www.psi-cad.fr

 

[petulf]

We have created part families for some series of similar parts that were supplied as dumb solids, by having all the solids in the same part file and using loads of suppress by expression. The down side is that all part family members carry around all the others geometry which is far from optimal.

 

[NutAce]

You can mimic partfamily behavior using the KRX file.
You need to create an master item which can act as a container for this KRX file.

Basically what you do is create a spreadsheet which holds all the attributes you want to be able to select on.

I have added a pdf explaining how to do this. It is based on a Teamcenter Environment but you should be able to figure out how to adapt it to your needs...



Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX11 / TC11

 

[Rob_N]

Thanks Ronald, I too have been wondering how to do this. I have a lot of imported re-use geometry.

 

[3dr]

If you want to place all the same dumb bodies in 1 part file and have access to them all via a re-use part.

1. Use a logical base or "Insertion point" (WCS Zero) for the bodies.
2. Suppress / un-suppress with the associated spreadsheet.

The Expression with the 0 / 1 that controls suppression needs to be listed in the spreadsheet.

Super easy, I've never thought of this one before.
It's a quick way to get a part family put together with no complicating issues.

Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX9, Win 7 Pro SP1

 

[wogo62]

Hello,

collecting all dumb bodies in one part file and afterwards suppress unneeded bodies is one solution especially when working with only few bodies (e.g less 10).
Handling with numerous bodies is far from optimal as petulf mentioned.

Ronald, handling with a mimic part family and krx-file works pretty good - just a minor drawback: all children parts should be in the same folder, otherwise they couldn't be found. Think in TC that isn't a real problem, but in native mode it's unbeautiful to see lot's of files in the reuse folder and furthermore it's difficult to find the master file.

Best regards
Wolfgang

 

[TaylorAnderson]

Wolfgang --

[pre]>> it's unbeautiful to see lot's of files in the reuse folder
>> and furthermore it's difficult to find the master file[/pre]

That's what the "KE Parts" (Knowledge-Enabled Parts) filter is for.

This will make only the parts with an accompanying KRX file visible, and hide all of the other unbeautiful ones.

Taylor Anderson
NX Product Manager, Knowledge Reuse and NX Design
Product Engineering Software
Siemens Product Lifecycle Management Software Inc.
(Phoenix, Arizona)

 

[wogo62]

Hello Taylor,

wow - this option was completely unknown for me.
Perfect !

Best regards
Wolfgang

 

[petulf]

Hi Taylor

I have a tangential question about reuse library (Teamcenter 10 environment). Which parameter decides the sorting order when thumbnails are displayed? it seems to be random and changes every time the reuse library folder is refreshed.

Table view is able to sort according to the object name in alphabetic order.