Bruce if you would look in Vantage help there is a good example of a Phantom
BOM. It is pretty much the same thing as Eric just explained. I also had the
same question as you about the tracking/maintenance. If you look at the
routing of a BOM it looks like there is a subassembly and really there
isn't. As Eric suggested put "phantom" in the description or as someone
suggested to me, put a specific prefix in the part number to specify it's a
phantom.
Fredy Venczel
-----Original Message-----
From: Tyira Eric [SMTP:
eric.tyira@...]
Sent: Wednesday, May 05, 2004 7:58 AM
To:
vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Phantom BOM
I think the way I look at it is a phantom BOM does not have to be a
"real" BOM. It's just a way for engineering to group parts together and
release them with a few keystrokes. It can even have a B.S. part number and
name. I would also suggest using a Phantom BOM for rock solid designs that
have no chance of generating problems.
Example 1 (solid design): We need to release chain tensioners.
They consist of a base, shaft and sprocket each ordered and stocked
individually. There are #40 single, #50 single, double and triple, and
timing belt each with a fixed base, adjustable with teeth and adjustable
with teeth and a slotted base. We have setup a drawing that shows all the
combinations of tensioners. Each drawing number of the tensioners
(12345-001, 12345-002, 12345-003, etc.) is a phantom assembly in Vantage.
The tensioner assembly is called in the drive assembly as view as assembly,
pull as assembly. The drive assembly DOES NOT call the tensioner materials
directly as this would result in duplication. When we release the drive
assembly, the phantom collapses and leaves the tensioner materials behind in
the drive assembly. The drive assembly drawing shows which tensioner
assembly goes where. If production wants the tensioner assembly drawing,
they ca n get a copy using the drive assembly drawing as the reference to
the tensioner drawing number. In this example we are able to trace the
materials to the phantom BOM and cross reference the assembly drawing using
another assembly drawing. And yes, the BOM in job entry does not exactly
match the BOM on the drawing ... but it is acceptable for us.
Example 2 (bs part number): I need to release rigidizer and coating
cement for our insulation. For every gallon of coating cement, there is a
quarter gallon of rigidizer needed. We have setup a B.S. phantom BOM that
calls for 1 gallon of coating cement and .25 gallons of rigidizer per
parent. When we add this assembly to job entry, we call for a quantity of
100, then get details. The assembly is deleted and the coating cement and
rigidizer are left behind in the insulation assembly as materials with, you
got it, 100 gallons of coating cement and 25 gallons of rigidizer. In this
example, I don't care where it came from, only if the quantity (and ratio
for future releases) is correct.
I know at least here, as long as production gets the parts, they can
build it. Our production is not interested in highly complex, indented
assemblies with confusing travelers. In the end, it's just a list of parts
in job entry and the travelers are simplified.
Oh, and I would suggest that if you do use phantom boms, put the
word "phantom" in the description so you can find them all quickly in part
maintenance.
Eric L. Tyira
Software Engineer
Tamglass Tempering Systems, Inc.
P: (856) 786-1200
F: (856) 786-7606
eric.tyira@...
-----Original Message-----
From: Ordway, Bruce [mailto:
bruceo@...]
Sent: Tuesday, May 04, 2004 9:12 PM
To:
vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Phantom BOM
Eric,
>I don't care where it came from.<
> ...a "where used". This will them list all the boms the part is
called in, including the phantom.<
Please check this out & let me know if it's right.
Part A is on BOM 123 because Phantom ABC was added to the BOM.
A where used shows Part A used on BOM 123 and Phantom ABC.
Engineering says Part A has to change from Qty 1 to Qty 2.
I think you have to update BOM 123 and Phantom ABC as separate
entities
now.
It appears to me that if using phantoms you end up with double the
maintenance?
How do you handle ECO's when phantoms are involved?
I like the idea of phantoms but not having a reference on the parent
BOM
seems like it will cause problems in our environment. Let me know if
you
have this covered somehow.
I've used another system with a different style of phantom. It kept
the
reference to the phantom in the parent BOM. That way, update the
phantom, the parent BOM is updated at the same time.
The Vantage style phantom has me balking.
Thanks,
Bruce Ordway
Viking Engineering