Teamcentre BoM vs. JT representation 1

[DaveJFT]

Hi folks,

In an electrical induction motor model in NX, rather than have to stack hundreds of stator or rotor laminates together in an NX assembly and suffer the graphics loading that generates, we model a single laminate separately and represent the stack as a single solid extrusion in the NX assembly.

However, when we come to create the BoM from Teamcentre this process means we have to set the stack body as a reference part (doesn't show up in the Tc BoM) and manually add the laminate part (x hundreds of instances) to the BoM in structure manager. Thus we get the correct BoM structure output.

What I'm now finding is that the JT model is reading the Tc BoM rather than showing the motor as seen in NX meaning it is showing a single laminate and a massive void where the stack body should be.

Is there a way we can handle this so that we get our cake and eat it?

Thanks!

Dave

 

[carlharr]

Hi Dave,

If a component is not in the BOMView, Vis won't know its there.

So, if you model the stack directly in parent assembly (i.e. in context), rather than in a separate component, an "assembly-level JT" will be created showing this single model.
You will also not need to make anything reference only.

Alternatively, if you really want it to be a separate component then:
1. WAVE link the solid body into your assembly
2. Make component ref only (to remove from parts list)
3. Suppress component in NX

Regards, Carl

http://www.jcb.com

NX 7.5 with TC 8.3

 

[DaveJFT]

Thanks Carl, most helpful.

Dave