Help clarifying proper use of production run quantity produced and rejected.

[Christian Carlow]

Production run declarations allow produced and rejected quantities to be 
declared but because of the various by-product scenarios that may exist, 
ambiguity is preventing me from determining how to properly use the 
fields.  For example, for Pierre's yeast-residue brewery example, the 
product is being produced but it isn't the product the production run 
was created to produce.  Therefore I'm not sure if the resulting 
yeast-residue should constitute quantity produced.  The same ambiguity 
applies to Jacopo's defective tortilla scenario.  Technically the 
tortilla isn't the same as the pizza the production run is meant to 
produce so declaring it as quantity rejected seems possibly correct.  
Are these fields supposed to be used only for tracking the goods 
quantities or are they meant to indicate quantities for non-production 
run goods as well?  This ambiguity is preventing me from implementing 
additional functionality required by the customer.

Re: Help clarifying proper use of production run quantity produced and rejected.

[Pierre Smits]

Christian,

It seems to me that you are confusing yourself with your own reasoning

Look at it from this simple and absolute perspective: when executing a
production run that results in the end product beer the outcome of that
intention is either beer (success) or no beer (failure). The rest is a
by-product. Defective end products don't exist. Just end products
(success), wanted by-products (e.g. waste - as in the bags the barley came
in -  or in the beer scenario yeast-residue) and unwanted by-products (the
stuff that you get when failed)

It also seem to me that you are the only one in your organisation carrying
the burden of implementing business case/solution/process and technical
adjustments. Beware of falling on the knife of your own promises.

Regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

Re: Help clarifying proper use of production run quantity produced and rejected.

[Christian Carlow]

Thanks Pierre,

You are correct, I'm the only one carrying the burden.

So what you are saying is for a production run to create 10 of some 
amount of brews, the yeast would not constitute quantity produced 
specified in the left hand form?  So there is yeast-residue left over 
after each of the 10 brews, you wouldn't declare a quantity produced of 
2 (1 for beer 1 for yeast residue) but 1 for just the beer meant to be 
produced correct?


On 03/10/2014 12:19 PM, Pierre Smits wrote:

Christian,

It seems to me that you are confusing yourself with your own reasoning

Look at it from this simple and absolute perspective: when executing a
production run that results in the end product beer the outcome of that
intention is either beer (success) or no beer (failure). The rest is a
by-product. Defective end products don't exist. Just end products
(success), wanted by-products (e.g. waste - as in the bags the barley came
in -  or in the beer scenario yeast-residue) and unwanted by-products (the
stuff that you get when failed)

It also seem to me that you are the only one in your organisation carrying
the burden of implementing business case/solution/process and technical
adjustments. Beware of falling on the knife of your own promises.

Regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com