Cancel
Showing results for 
Search instead for 
Did you mean: 

Hide assembly from BOM but not from lifecycle viewer

Valued Contributor
Valued Contributor

Is that possible in NX managed?

There is some assemblies that in some products we purchased assembled so we dont not purchase its components. In some other products the same assemblie is purchased disassembled so we purchase its components.

 

I would like to set an assembly as if it were one part so we only see it in structure and we only purchase it and other times set it as a normal assembly. I can do that by setting the assembly as "reference component" but then it doesnt apppear in the lifecycle viewer. 

 

Thanks in advance

5 REPLIES

Re: Hide assembly from BOM but not from lifecycle viewer

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
These are two different use-cases and need to addressed using two different methods.

The first use-case is a wholly purchased assy. That should get a single Item number in Teamcenter and imported as a single part (monolithic).

The second use-case is for purchasing pieces of the assy as a kit. A kit should be created in Teamcenter and the components imported as individual parts (polylithic) to create the BOM for the kit.

Hope that helps clear up your usage question.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Hide assembly from BOM but not from lifecycle viewer

Valued Contributor
Valued Contributor

In the case of the wholly purchased assembly we design it as a normal assembly, we add or remove components that are on our reuse libraries... so we manage the CAD data as a normal assembly. I would like that TC see it as just one component but keeping the assembly in NX so we can modify it, reuse in future products...

Re: Hide assembly from BOM but not from lifecycle viewer

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
Sounds like you need to change your business practices. You probably don't design the purchased assembly and a dumb solid is all you need to design around it. Only break it up where it makes sense like the kitting example. Your use-cases will be more clear and you'll be happier in the end (less work/rework).

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Hide assembly from BOM but not from lifecycle viewer

Valued Contributor
Valued Contributor

We design the purchased assembly. For example a extruded aluminum profiles framework. We design it, profiles lenght, fixtures, doors, wheels... but they are mostly of the self components for our supplier and they deliver the framework assembled but with the components we chose. We need to assemble them in 3D to use as base to assemble other components manufactured by ourselves and in the desing process we make changes to the framework. Sometimes we want to reuse this design for other products or we want to know what components composed that just in case we need to modify the machine or to supply a spare part. I think a dumb solid is not good for us. But at the same time we dont want these components to appear in TC structure as we dont want to purchase them.

Re: Hide assembly from BOM but not from lifecycle viewer

Siemens Phenom Siemens Phenom
Siemens Phenom

Hi @Javiduc,

 

Along the lines of what @RandyEllsworth suggests, and since you're using TC, perhaps you could take advantage of MultiCAD and represent the reference assembly as a single monolithic JT.

Selecting "File > Export > JT" from NX allows you to export the assembly as a single JT, which when added to NX (and SM) would appear as a single dataset, but in Lifecycle Viewer the structure is revealed:

 

Screenshot - 9_6_2017 , 9_30_17 AM.png

 

Screenshot - 9_6_2017 , 9_30_44 AM.png

 

Screenshot - 9_6_2017 , 9_31_26 AM.png

 

Regards, Ben