FW: Hi James, I have a Vantage need/want

You could use a phantom for X and for Y as a way to force any ECO to be
made at the phantom level and thus be used wherever the phantom is called
out.


A Phantom is not a separate assembly, but simply a short-hand way to refer
to a list of parts. But any modification to the BOM would be made to the
phantom and would, therefore, propagate through any bills in which the
phantom is used.

Carl Heeder
ST Inverter America
281-506-3146
Mobile: 281-221-3421
FAX 978-725-3057



"James Martin Jr." <jmartin@...>
Sent by: vantage@yahoogroups.com
08/08/2005 12:29 PM
Please respond to
vantage@yahoogroups.com


To
<vantage@yahoogroups.com>
cc

Subject
[Vantage] FW: Hi James, I have a Vantage need/want






This Vantage question was posed to me by one of our Manufacturing
Engineers. I was not aware that this is possible on Vantage 6.10.526,
but Engineering Workbench and related are not my forte. Anyone willing
to share opinion?



Thanks



James



________________________________

From: Duane Bartley
Sent: Monday, August 08, 2005 11:21 AM
To: James Martin Jr.
Subject: Hi James, I have a Vantage need/want



Here's the situation. I currently build part B1. Within part B1 is a
subassembly X and a cover plate Y. The cover plate Y covers one of two
holes in B1 that are for X. Now, a new part is to be built: B2. The
difference between them is that B1 has 1 X and 1 Y, part B2 has 2 X's
and 0 Y.



One option is obviously to create "B" as an assembly of its own and from
it, create B1 or B2. For the sake of this situation, let us assume that
is not practical.



My problem lies in ECO's. If an engineering change comes down the pipe
for B1, I want Vantage to either automatically prompt or force the ECO
on B2. The opportunity for failure exists in that persons not aware of
the 'new' assembly will also not know to include it (B2) in any changes
made to the legend part (B1). This could lead to the opportunity for a
new B2 to go out the door with an old engineering revision on the base
unit (B).



Any ideas would be greatly appreciated. Thanx for the assistance.



db



[Non-text portions of this message have been removed]



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links



SPONSORED LINKS
Technical support
Vantage
Database
Database management software
Membership database software
Church database software

YAHOO! GROUPS LINKS

Visit your group "vantage" on the web.

To unsubscribe from this group, send an email to:
vantage-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.




[Non-text portions of this message have been removed]
This Vantage question was posed to me by one of our Manufacturing
Engineers. I was not aware that this is possible on Vantage 6.10.526,
but Engineering Workbench and related are not my forte. Anyone willing
to share opinion?



Thanks



James



________________________________

From: Duane Bartley
Sent: Monday, August 08, 2005 11:21 AM
To: James Martin Jr.
Subject: Hi James, I have a Vantage need/want



Here's the situation. I currently build part B1. Within part B1 is a
subassembly X and a cover plate Y. The cover plate Y covers one of two
holes in B1 that are for X. Now, a new part is to be built: B2. The
difference between them is that B1 has 1 X and 1 Y, part B2 has 2 X's
and 0 Y.



One option is obviously to create "B" as an assembly of its own and from
it, create B1 or B2. For the sake of this situation, let us assume that
is not practical.



My problem lies in ECO's. If an engineering change comes down the pipe
for B1, I want Vantage to either automatically prompt or force the ECO
on B2. The opportunity for failure exists in that persons not aware of
the 'new' assembly will also not know to include it (B2) in any changes
made to the legend part (B1). This could lead to the opportunity for a
new B2 to go out the door with an old engineering revision on the base
unit (B).



Any ideas would be greatly appreciated. Thanx for the assistance.



db



[Non-text portions of this message have been removed]