subassembly problem

[Anonymous]

On a project we have an illuminated push button where the button has his own tag and also the light. Now if I want to make a BOM in this situation what should I do?
example:
If I link the 800FP-LF3 on the button it shows me all of the components on the BOM, but I can not give the light any Material because otherwise it shows up twice on the BOM.
Can I work with child - parent or link them?
Do I need to make new entries in the default_cat database and separate the materials?
Anyone any idea?

Thanks,
Peter

[Anonymous]

No one any idea?

[Anonymous]

Hi Peter,

Let me parrot back what I think you're saying and tell me if this is
correct... you insert the pushbutton symbol on the drawing and assign the
800FP-LF3 part number. It has the full complement of parts and pieces for
the whole assembly, including the pilot light part of the switch. Now you
insert the separate "light" part of the switch. It comes in as a "child"
type symbol but you force it to carry its own unique tag (different from the
pushbutton).

Now, in the BOM report, the switch as all of the necessary catalog
information for it but also for the light. But since the light, with its own
tag, doesn't show up in the BOM, it looks like the light was "missed".

Is this accurate? Please let me know.

Nate.


wrote in message news:5182840@discussion.autodesk.com...
On a project we have an illuminated push button where the button has his own
tag and also the light. Now if I want to make a BOM in this situation what
should I do?
example:
If I link the 800FP-LF3 on the button it shows me all of the components on
the BOM, but I can not give the light any Material because otherwise it
shows up twice on the BOM.
Can I work with child - parent or link them?
Do I need to make new entries in the default_cat database and separate the
materials?
Anyone any idea?

Thanks,
Peter

[Anonymous]

Hi Nate,

You are almost there. With this exception that it is not a parent and a child I insert but 2 parents. The "VPB11" and the "VLT1R" symbols (they can be on different pages).
They have a different TAG because the one is a light (ex. -11H61) and the other is a Push Button (ex. -11S31). On the PB I assign the 800FP-LF3 part which carries true his assycode the whole assembly (the button, the contact block, the mounting latch and the powerblock module with LED)
On my BOM I now see something like this:

11S31 exists out of 1 800FP-LF3, 1 800F-X10, 1 800F-ALP and 1 800F-N5G.

I would like a possibility to have it read like this:
11S31/11H61 exists out of 1 800FP-LF3, 1 800F-X10, 1 800F-ALP and 1 800F-N5G.

ADDED:
Ofcourse it has to be possible to use the PB without light also, so for this I need to adjust the mdb so I have a assycode in wich not all the parts are present Added comment on the bottom

[dougmcalexander]

I think I would not create an assembly code that pulls them all together. I would create an assembly list entry for each of the "sub-parts" and a separate entry in the catalog for the pushbutton by itself. When you need just the pushbutton, just catalog lookup and add the pushbutton MFG and CAT. When you need the additional sub-parts, enter their assembly list code(s) into the ASSEMBLY CODE field of the edit screen for the pushbutton, just below the MFG and CAT of the pushbutton itself. Use a semicolon to separate multiple assembly list codes. If you need more than one of any sub-part enter the quantity followed by a comma before its respective assembly list code.

This method allows you to keep the lamp as a separate TAG and let its MFG and CAT fields carry the appropriate BOM information and quantity. Even though the lap may be physically part of the pushbutton, if it is ordered with a separate part number from the vendor, and carries its own unique tag, it should appear as a separate entry in the BOM.

So the ASSEMBLY CODE field might look something like this: SUBPART1;2,SUBPART2,4,SUBPART3. SUBPART of course represents whatever text you typed into the assembly list field of the components that get added to the pushbutton.

[dougmcalexander]

Sorry for the typos. The assembly code field would read something like this instead: SUBPART1;2,SUBPART2;4,SUBPART3. I accidentally typed a comma instead of a semicolon between SUBPART2 and SUBPART3. The syntax above tells the BOM generator to get one SUBPART1 (no qty entry required for just one), but it calls for a quantity of 2 of SUBPART2, and 4 of SUBPART3.

[Anonymous]

Hi Peter,

I don't see a good, automated solution. You can get part way there, as you
describe below, by adjusting the catalog lookup so that you break out the
"light" part of the subassy into its own, stand-alone catalog part number.
But, as far as having the BOM report be able to group these two different
tagged parent entries together into a single BOM entry, that will have to be
done manually. I don't think we could even come up with a "user post" to do
this. The pushbutton part and the light part, with their different tags...
no way for the report post-processor code to know that they are supposed to
go together.

I'm sorry I don't have any other ideas how to work around this...

Nate.


wrote in message news:5188566@discussion.autodesk.com...
Hi Nate,

You are almost there. With this exception that it is not a parent and a
child I insert but 2 parents. The "VPB11" and the "VLT1R" symbols (they can
be on different pages).
They have a different TAG because the one is a light (ex. -11H61) and the
other is a Push Button (ex. -11S31). On the PB I assign the 800FP-LF3 part
which carries true his assycode the whole assembly (the button, the contact
block, the mounting latch and the powerblock module with LED)
On my BOM I now see something like this:

11S31 exists out of 1 800FP-LF3, 1 800F-X10, 1 800F-ALP and 1 800F-N5G.

I would like a possibility to have it read like this:
11S31/11H61 exists out of 1 800FP-LF3, 1 800F-X10, 1 800F-ALP and 1
800F-N5G.

ADDED:
Ofcourse it has to be possible to use the PB without light also, so for this
I need to adjust the mdb so I have a assycode in wich not all the parts are
present

Added comment on the bottom

[Anonymous]

Thanks for the reply's.

Gone for the short pain and created a child light and used the (text) cross refs to tell where each part is located. I put the catalog in the parent and that's it.

Actually you can look at it as 1 assembly so I wondered why tag it with different numbers? On a relay you also do not tag the auxiliary contacts any different from the main.
I changed the tag a little bit to read like this for example "-11SH21" instead of the 2 separate numbers for example "-11S21" and "-11H51".