BOM component exclusion 2

[cyril009]

We are using nx7.5.5.4 native, and are trying to become more efficient with the drafting portion of compound assemblies (assemblies of assemblies).

The assembly in question has multiple sub-assemblies, the BOM is set to look at all the sub-components and ignore the assembly level.
Several of the lowest level assemblies contain parts that need to be represented graphically, while being excluded from the BOM.
what is the most efficient method of excluding these components from a BOM?

We use the Master Model approach
I have adjusted my practices to avoid using reference sets where arrangements are more appropriate.
I have NOT YET figured out when to use arrangements or "component hide" to hide components, but that may prove irrelevant here.

in another thread:

(Mechanical)
24 Feb 12 5:08
Hi,
with RMB on a component or sub-assembly in ANT I can set some properties.
In Assembly Tab of Component Properties command there are two options :
1) Component is reference
2) Component is Non-geometric

I didn't find descriptions in the help.
The first option exclude the component or sub-assembly from the BOM, but visible in the drafting

The second option is blanked but visible in the BOM.

The first option (component is reference) sounds perfect, but is not available to us? please advise.

 

[jerry1423]

Maybe this thread can get you started in the right direction:

http://www.eng-tips.com/viewthread.cfm?qid=298393

 

[cyril009]

Fantastic Jerry, thanks for that link, plist_ignore_member is a huge help.

I still don't see the "reference only" option:

(Automotive)
9 May 11 8:06
Make it "reference only". Select it in the ANT, right click properties, and check the "ref only" box.
-Dave

NX 5.0.6.3mp7

I am left to assume that this was removed at or before 7.5?

 

[jerry1423]

Here is something from the NX7.5 documentation pertaining to reference components:

Reference-only component
You can add a reference-only component column to the Assembly Navigator to identify the components that are reference only. Right-click on a column, choose Columns, and select Reference-only.

An icon is displayed in the Reference-only column if the reference only attribute is present. If you are in native NX and not Teamcenter Integration, the column is always blank.

You can make a component reference-only by right-clicking on the component and choosing Properties to display the Component Properties dialog box. Then select the Component is Reference-Only checkbox. When you make a component reference-only in this manner, that component is removed from the parts list of the parent, thus maintaining the link between PSE and the Parts List.

Note:

You can only make a component reference-only if it is an immediate child of the current displayed part. If you select a component whose parent is not the displayed part, the Component is Reference-Only toggle is greyed out.

A warning message is displayed informing you of the change before the component is removed from the parts list. In the same way, when a reference-only component is turned back into a normal component, it is restored to the parts list and a message is displayed informing you of the change.

 

[jerry1423]

. . . But I don't get it.
I don't see any way to add a way to add a "refernce only" column to the ANT, it's not in the list

 

[SiW979]

Reference only will only apply to Teamcenter based NX as far as I can see. I have native open and there is no option, however in Teamcenter managed NX I have the option to turn on reference only.

Obviously this is no use to you, however in TC, you simply right click on a component in the ANT and under proerties you can toggle on Component Is reference Only. There is also another option to set UG geometry to NO.

Cheers

Si.

Best regards

Simon NX7.5.4.4 MP8 - TC 8

http://www.jcb.com

 

[Dave K]

Yes, the "reference only" check box only applies when using Teamcenter

-Dave

NX 7.5

 

[cyril009]

Once we get some ugs-nx-data-conversion logistics worked out, we'll be in teamcenter too, so looking forward, this information is still helpful and applicable.

many thanks to all who replied,
-Cyril