Ok, this is a similar situation to us at present.
We are an electronics manufacturer moving from a home grown system to
Vantage. In the "good old days", we structured our BOMs around the
production operator sat at the bench, with component locations such
as R1, R2 etc. driving the line order on the BOM. This also resulted
in the same part appearing on many lines, however we then spent far
too much time compressing this all back down again in order to keep
purchasing happy. After all they only want to see one line per part
and dont care about where is actually fits in the product.
Vantage is an inventory control tool and not an engineering control
tool ( that was a fundamental change in thinking for us ), and whilst
you could use fields such as "Bubble" to store component locations,
or even store them in one of the description fields, out of the box
its really designed to control inventory and not provide production
operators with workable information straight from the bom.
Moving forwards we are now looking at structuring the BOM around the
procurement and inventory control process, and use external
information to provide the production operator with actual build
documentation ( we still might control this via associations with the
part and MES, or indeed PLM if we choose to go ahead and buy this ).
We will be looking to tie materials to production operations as this
will help the scheduling process and stop goods receiving getting
flooded with everything arriving all on the same day.
I think you will have to strike a balance between the procurement and
manufacturing activities as both have differing needs, however I
think you will find yourself leaning towards the Vantage BOM being
inventory-centric, and finding another medium for producing shop
floor information.
Not sure if that will help you in your thoughts...
Thanks,
Nick
We are an electronics manufacturer moving from a home grown system to
Vantage. In the "good old days", we structured our BOMs around the
production operator sat at the bench, with component locations such
as R1, R2 etc. driving the line order on the BOM. This also resulted
in the same part appearing on many lines, however we then spent far
too much time compressing this all back down again in order to keep
purchasing happy. After all they only want to see one line per part
and dont care about where is actually fits in the product.
Vantage is an inventory control tool and not an engineering control
tool ( that was a fundamental change in thinking for us ), and whilst
you could use fields such as "Bubble" to store component locations,
or even store them in one of the description fields, out of the box
its really designed to control inventory and not provide production
operators with workable information straight from the bom.
Moving forwards we are now looking at structuring the BOM around the
procurement and inventory control process, and use external
information to provide the production operator with actual build
documentation ( we still might control this via associations with the
part and MES, or indeed PLM if we choose to go ahead and buy this ).
We will be looking to tie materials to production operations as this
will help the scheduling process and stop goods receiving getting
flooded with everything arriving all on the same day.
I think you will have to strike a balance between the procurement and
manufacturing activities as both have differing needs, however I
think you will find yourself leaning towards the Vantage BOM being
inventory-centric, and finding another medium for producing shop
floor information.
Not sure if that will help you in your thoughts...
Thanks,
Nick
--- In vantage@yahoogroups.com, "j.schwerer" <jschwerer@...> wrote:
>
> I'm new to vantage, but came from a company that used SAP. In SAP
we
> would place a parts BOM into the system from engineering. This BOM
> was in a logical order for the stockroom to pick the parts.
> Manufacturing would take the BOM and create a sequence of events,
or
> the order in which the parts were assembled.
>
> The company I'm with now is using the same BOM for both, either a
> pick list or job traveler, with the line/sequence set-up more for
> the manufacturing process. This in turn drives the stock room crazy
> with the parts on their pick list being all over the map. I've been
> experimenting with operations, thinking it may be the same as my
old
> sequence of events. Assigning operation numbers, it seems I can
flip
> the BOM either way to be best for both, but I'm not sure if
> manufacturing will be able to use this to get a pick list, and a
> build list so to speak. Their just starting to use `operations'
> here to track labor costs, but I feel it's not being used to it's
> full potential. Right now only a few BOM's were adapted, with only
3
> or 4 operations for the entire assembly – 1st stage, 2nd, final –
so
> on. Where as, I created and assigned a different operation number
to
> each part on my test BOM.
>
> I hope someone can tell me if I'm chasing the wrong tail here. I've
> been poring over the "Help" files, but can't seem to find a good
> explanation of how to create a BOM and then manipulate it for
> different departmental functions, or what operations is really all
> about.
>
> Hope I wasn't to confusing.
> Thanks everyone in advance.
>