Issuing Materials in vendor Standard Packing sizes?

I think we're saying the same thing. Essentually you would be stocking it in the Vendor's UM (and issuing at such - as in a box).

Where is where it gets crazy (people issue). An engineer (or a stockroom person) can't blindly assume the BOM qty (or Issue) UM is EAch. If there are 1000 ea/bx and the BOM needs one (ea), the engineer needs to enter 0.001 as the qy per. He/she is likely to enter 1 per on occasion (meaning you are issuing or backflushing 1000.

For Bar stock (bought in vendor's UM of lb's and stocked/issued in FT), people are used to it.

Doing it for things traditionally stocked/issued in EA causes confusion, more mistakes and stress when mistakes occur.

(People stuff.)

Rob

--- On Wed, 9/24/08, eltaria.foong <eltaria.foong@...> wrote:

From: eltaria.foong <eltaria.foong@...>
Subject: [Vantage] Re: Issuing Materials in vendor Standard Packing sizes?
To: vantage@yahoogroups.com
Date: Wednesday, September 24, 2008, 2:59 AM






Hi Rob, thanks for the feedback,
I appreciate your thoughts, although I was hoping for a 'quick fix'
solution :)

If that's the only way of getting it to work, then I can foresee the
starry eyes from the warehouse guys when I tell them about this.
Maintaining two sets of part numbers will be definitely resisted too
by everyone.

People will definitely be an issue here too.

Actually, I'd expect such a functionality to be built into vantage
itself, as I believe it's pretty common for manufacturing companies to
issue in vendor standard unit of measurement, is it not?

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...> wrote:
>
> Any MRP system from the '70s on can be 'tricked' into doing what you
want.
>
> In your case, you would buy screws (I suggest under a different P/N
then your current screw PN) - perhaps with a vendor qty of each but a
stocking IUM of "bags" where 1 "bag" - 500 "each" of the screw.
>
> You COULD then also set up a non-stock/phantom method to convert
"BAG"s of screws back to "EACH" screw (for use in you normal methods).
Setting the BAG OF SCREWS Part record to only use integer values would
then force requirement generation and issue of complete bags.
>
> This is also a fairly well tried and true technique (although a
cludge) for making older MRP system act like quite effective KanBan
processors.
>
> An additional upside is that your cycle counting/inventory
control/accuracy WILL go up as you will be counting full bags on small
parts that typically require weigh counting that gives different
results on even thr best maintained/calibrat ed scales (and alsmost
always vary with vendor weigh counts versus your receiving weigh
counts)... It simply eliminates the need entirely as (like kanban)
partials don't matter... A Kanban is considered full until it is
completely empty.
>
> The negatives are:
>
> People acceptance:
>
> There are some real smart people out there that, because they grew
up in the digital age, don't understand that "knowing" a value to the
nth decimal point can give a less accurate answer than knowing all
variable values to the same significance. (Slide rules put Men on the
Moon - not computers.)
>
> There are not so smart people - no... absolutely the wrong words -
There are people that don't accept change well. (An attribute that
often makes the VERY well suited for and good at the MANY repetitive
jobs in the physical manufacturing process.) A change such as this (if
wide spread) would take some signficant touchy-feely change management
commitment and plan to make it work (Sustain: One of the Lean 5 S's).
>
> System set up changes to reflect the new IUM paradigms:
>
> This impacts nearly all areas (BOMS, Inventory control, purchasing,
vendor price lists, costing, etc.,)... Lot's of data to update to make
it work (and then it has to be understood well enough to be maintained
- getting back to those people issues above).
>
> If anyone has a better Vantage specific (particularly v8 405a)
solution, I'd love to here it as we have similar issues and I don't
relish the challenge of getting buy-in to do what is proposed above
(on ANY scale).
>
> Rob Brown
Hi Group,

I've tried searching through the list for this, but I can't find
anything. There're a lot of valuable information in this list, but I
noticed it's a bit hard to search for it sometimes, wish Yahoo could
implement a tagging system in...

We're using Vantage 6.1, and would like to ask how did everyone else
deals with the following scenario?

Scenario :
We have a production run of 1000 units of Finished Goods, which
created a demand of 1050 Zinc Coated Screws. 5% scrap rate.

We buy the Screws in packets of 500 each.
And as such, warehouse will issue 1,500 unit to production. As it's
not viable for them to unpack and count 50 pieces out to production.

Right now, we're using Mass Issue, and entering 1000 units of
production quantity for the Job.

By default, Mass Issue will populate all raw materials with (Finished
Goods Qty + Scrap % ) is it possible for Vantage to take into
consideration the standard packing sizes as well, and issue 1500 (3
packets) instead of saying 1050 by default?
Any MRP system from the '70s on can be 'tricked' into doing what you want.

In your case, you would buy screws (I suggest under a different P/N then your current screw PN) - perhaps with a vendor qty of each but a stocking IUM of "bags" where 1 "bag" - 500 "each" of the screw.

You COULD then also set up a non-stock/phantom method to convert "BAG"s of screws back to "EACH" screw (for use in you normal methods). Setting the BAG OF SCREWS Part record to only use integer values would then force requirement generation and issue of complete bags.

This is also a fairly well tried and true technique (although a cludge) for making older MRP system act like quite effective KanBan processors.

An additional upside is that your cycle counting/inventory control/accuracy WILL go up as you will be counting full bags on small parts that typically require weigh counting that gives different results on even thr best maintained/calibrated scales (and alsmost always vary with vendor weigh counts versus your receiving weigh counts)... It simply eliminates the need entirely as (like kanban) partials don't matter... A Kanban is considered full until it is completely empty.

The negatives are:

People acceptance:

There are some real smart people out there that, because they grew up in the digital age, don't understand that "knowing" a value to the nth decimal point can give a less accurate answer than knowing all variable values to the same significance. (Slide rules put Men on the Moon - not computers.)

There are not so smart people - no... absolutely the wrong words - There are people that don't accept change well. (An attribute that often makes the VERY well suited for and good at the MANY repetitive jobs in the physical manufacturing process.) A change such as this (if wide spread) would take some signficant touchy-feely change management commitment and plan to make it work (Sustain: One of the Lean 5 S's).

System set up changes to reflect the new IUM paradigms:

This impacts nearly all areas (BOMS, Inventory control, purchasing, vendor price lists, costing, etc.,)... Lot's of data to update to make it work (and then it has to be understood well enough to be maintained - getting back to those people issues above).

If anyone has a better Vantage specific (particularly v8 405a) solution, I'd love to here it as we have similar issues and I don't relish the challenge of getting buy-in to do what is proposed above (on ANY scale).

Rob Brown



--- On Tue, 9/23/08, eltaria.foong <eltaria.foong@...> wrote:
From: eltaria.foong <eltaria.foong@...>
Subject: [Vantage] Issuing Materials in vendor Standard Packing sizes?
To: vantage@yahoogroups.com
Date: Tuesday, September 23, 2008, 9:36 PM











Hi Group,



I've tried searching through the list for this, but I can't find

anything. There're a lot of valuable information in this list, but I

noticed it's a bit hard to search for it sometimes, wish Yahoo could

implement a tagging system in...



We're using Vantage 6.1, and would like to ask how did everyone else

deals with the following scenario?



Scenario :

We have a production run of 1000 units of Finished Goods, which

created a demand of 1050 Zinc Coated Screws. 5% scrap rate.



We buy the Screws in packets of 500 each.

And as such, warehouse will issue 1,500 unit to production. As it's

not viable for them to unpack and count 50 pieces out to production.



Right now, we're using Mass Issue, and entering 1000 units of

production quantity for the Job.



By default, Mass Issue will populate all raw materials with (Finished

Goods Qty + Scrap % ) is it possible for Vantage to take into

consideration the standard packing sizes as well, and issue 1500 (3

packets) instead of saying 1050 by default?
Hi Rob, thanks for the feedback,
I appreciate your thoughts, although I was hoping for a 'quick fix'
solution :)

If that's the only way of getting it to work, then I can foresee the
starry eyes from the warehouse guys when I tell them about this.
Maintaining two sets of part numbers will be definitely resisted too
by everyone.

People will definitely be an issue here too.

Actually, I'd expect such a functionality to be built into vantage
itself, as I believe it's pretty common for manufacturing companies to
issue in vendor standard unit of measurement, is it not?



--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
> Any MRP system from the '70s on can be 'tricked' into doing what you
want.
>
> In your case, you would buy screws (I suggest under a different P/N
then your current screw PN) - perhaps with a vendor qty of each but a
stocking IUM of "bags" where 1 "bag" - 500 "each" of the screw.
>
> You COULD then also set up a non-stock/phantom method to convert
"BAG"s of screws back to "EACH" screw (for use in you normal methods).
Setting the BAG OF SCREWS Part record to only use integer values would
then force requirement generation and issue of complete bags.
>
> This is also a fairly well tried and true technique (although a
cludge) for making older MRP system act like quite effective KanBan
processors.
>
> An additional upside is that your cycle counting/inventory
control/accuracy WILL go up as you will be counting full bags on small
parts that typically require weigh counting that gives different
results on even thr best maintained/calibrated scales (and alsmost
always vary with vendor weigh counts versus your receiving weigh
counts)... It simply eliminates the need entirely as (like kanban)
partials don't matter... A Kanban is considered full until it is
completely empty.
>
> The negatives are:
>
> People acceptance:
>
> There are some real smart people out there that, because they grew
up in the digital age, don't understand that "knowing" a value to the
nth decimal point can give a less accurate answer than knowing all
variable values to the same significance. (Slide rules put Men on the
Moon - not computers.)
>
> There are not so smart people - no... absolutely the wrong words -
There are people that don't accept change well. (An attribute that
often makes the VERY well suited for and good at the MANY repetitive
jobs in the physical manufacturing process.) A change such as this (if
wide spread) would take some signficant touchy-feely change management
commitment and plan to make it work (Sustain: One of the Lean 5 S's).
>
> System set up changes to reflect the new IUM paradigms:
>
> This impacts nearly all areas (BOMS, Inventory control, purchasing,
vendor price lists, costing, etc.,)... Lot's of data to update to make
it work (and then it has to be understood well enough to be maintained
- getting back to those people issues above).
>
> If anyone has a better Vantage specific (particularly v8 405a)
solution, I'd love to here it as we have similar issues and I don't
relish the challenge of getting buy-in to do what is proposed above
(on ANY scale).
>
> Rob Brown