Here are several different ideas or approaches you might consider.
Using same part # as OEM is also a big help when personnel of an OEM
communicate with us about their parts. We can share screen prints,
reports, that already have their part # on them.
The item # we use for what we make for OEMs is identical to THEIR part # &
we have a methodology to deal with the rare exception of two or more
customers with overlapping part# systems. Components of this have same
item# with characters after that correspond to the customer drawing.
We can have in BOM.
Part # A ... our internal unique id
Part # B ... our customer unique id
BOM has Part # A needing quantity one of Part # B with no routings
Both are master scheduled manufactured end items.
Enter any number of customer orders for Part # B ... BPCS works fine
Enter an order to get some of A, and BPCS tells us to make enough of B to
meet the A demand.
We can make/source 100% according to one BOM, then we do a pair of
inventory adjustments with reason code ID to replace a given quantity of
part-A with same quantity of part-B ... same physical part, just a
different item#.
Have you considered using METHOD coding?
One method for how the part is to be made in-house.
One method for how the part is to be when purchased.
Use default method (blank) for the method you expect to use most often.
That way you eliminate a lot of hassle with engineering updates.
Do not delete alternative engineering approach. Use effectivity dates.
More difficult is if you doing both at same time.
We have phantoms in our BOM to help with visibility of this and
Engineering Change history.
We also use commons ... like configurable concept ... the part # is for the
physical makeup of the component ... then this same "common" intermediate
part ends up being used on many different parts of many different customers.
There is a feature in BPCS that we have not been using, where you can setup
a reference # where here is the same item # as used by the customer.
The main problem is that METHOD CODES and BOM perspective does not
communicate effectively through all application users. It is like you need
notes that have good visibility various places to let people know about
exceptions. We end up having two item #s that are identical except for the
last character. The last character communicates to everyone in the company
what is going on with the part.
* If last character is letter S, this is a SAMPLE
* If last character is letter R, this is repair rework
* If last character is character !, this is phantom until pending hold
situation resolved
* After special last character has been stripped away, revert to normal
processing
We created a modification to parallel BOM information. Essentially it ties
together end items for what customers with component parts we order from
what vendors & what BOM math quantities needed. We use this for multiple
purposes:
* commonity pricing fluctuates on steroids ... what is the effect on the
bottom line of what goes to customers?
* another customer wants assurance of ROHS-compliance ... identify all the
vendors involved in their parts & rapidly answer that question
* we are able to obtain contract price discounts from some vendors thanks
to linking with future sales forecasts where used
* due to a reduction in one customer needs, we must rethink our stocks and
safety balance algorithm of the raw materials used for that customer ...
which of those raw materials are used where else on other customers parts?
Al Mac
an IT Manager who spends more time in Data Quality repairs than all else
combined
Greetings,
I am asking this from a Purchasing (consolidation) viewpoint.
We will design and manufacture some of our own products. More often, we
just manufacture to the design of our OEM's.
Thus, when we create a BOM for the OEM designed product, we want to use
all of their part numbers so that everything will match their drawings, etc.
But, when we create a BOM for one of our OWN designed products, we will
use our own internal part numbers.
The problem is that our Item Master ends up with TWO different part
numbers which POINT TO the very same physical component - which will be
entirely purchased from ONE supplier.
So, we want to be able to consolidate the Purchasing requirements for
those two (or more in cases) part numbers into just ONE NUMBER - which we
can then order from our supplier.
Anyone handle this through the vanilla BPCS? Anyone come up with their
own design?
Thanks,
Don C.
Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063
"Only one who devotes himself to a cause with his whole strength and soul
can be a true master. For this reason mastery demands all of a person."
Albert Einstein
midrange.com
