Symphony-CSCC / ivs_rcs

Inventory and Recipe Costing
0 stars 0 forks source link

Production using Recipes #49

Open bltbersonda opened 7 years ago

bltbersonda commented 7 years ago

OBSERVATION: We created a new Production for Gulaman, Green, Cooked. Based on definition of fields, Quantity = Batch Quantity. In this case, we were preparing 2 batches of the recipe Gulaman, Green, Cooked. See figure below. (I edited this in photoshop because we weren't able to get screenshots on the first run) 2017-07-07 16_19_35-symphony cms 2 1 - city sports club cebu

Then we checked the inventory for Gulaman, Green, Cooked. We found out that only two cups were produced, however, 2kgs of raw material Gulaman, Green was deducted from the inventory. We opened again the Production Form. See below. 2017-07-07 16_19_36-symphony cms 2 1 - city sports club cebu

Everything seemed the same. But, we noticed that we could edit the Quantity field. We changed the 2 to 40 and clicked save. See image below. 2017-07-07 16_19_37-symphony cms 2 1 - city sports club cebu

We again checked the inventory and found that 40C of Gulaman, Green, Cooked was added to the inventory. Also, 2kg of raw material Gulaman Green was deducted from inventory.

We again opened the same Production Form and changed the Quantity back to 2. We noticed that the ingredients to be used was now only 0.10pack. Check image below. 2017-07-07 16_19_40-symphony cms 2 1 - city sports club cebu

FIX:

  1. Please fix quantity whether it is Batch Quantity or Total Yield.
  2. As we finish debugging, please disallow editing of the Quantity field as soon as Production is 'Saved' the first time.

ENHANCEMENT: *problem Scaling of recipes is not a direct proportion. Thus, sometimes, when cooking large batches (x10 of the original recipes), the Yield changes. E.g. recipe says 1kg of Gulaman, Green can produce 20C of Gulaman, Green, Cooked. However, when we scale the recipes 10x, 10kg of Gulaman, Green will produce 210C of Gulaman, Green, Cooked instead of 200C. If we just base it on the current method, yield would only be 200C as specified by the recipe.

*possible solution Would it be possible to make the Actual Yield a variable?

  1. Quantity will be used as a multiplier to the original recipe. Here we get our Total Recipe Cost.
  2. Variable Yield will be the Actual Yield.
  3. Cost per Recipe Unit = Total Recipe Cost / Actual Yield.
rodjular commented 7 years ago

Hi Chef, comments in bold. Thanks!

FIX:

Please fix quantity whether it is Batch Quantity or Total Yield. >Quantity is in yield. (gulaman sample should be in cups). Recipe Production Yield is for reference only which serves as basis in computation of issuance(deduction) quantity.

As we finish debugging, please disallow editing of the Quantity field as soon as Production is 'Saved' the first time. >Ok. just let me know when to activate. Also, I would like to suggest that there should also be an allowed user(eg Dept Head) that can edit, in case there would be a typo error.

ENHANCEMENT: *problem Scaling of recipes is not a direct proportion. Thus, sometimes, when cooking large batches (x10 of the original recipes), the Yield changes. E.g. recipe says 1kg of Gulaman, Green can produce 20C of Gulaman, Green, Cooked. However, when we scale the recipes 10x, 10kg of Gulaman, Green will produce 210C of Gulaman, Green, Cooked instead of 200C. If we just base it on the current method, yield would only be 200C as specified by the recipe.

*possible solution Would it be possible to make the Actual Yield a variable?

Quantity will be used as a multiplier to the original recipe. Here we get our Total Recipe Cost. Variable Yield will be the Actual Yield. Cost per Recipe Unit = Total Recipe Cost / Actual Yield. >How about we give user to edit recipe unit?

bltbersonda commented 7 years ago

Thanks for your reply.

Actually, sa sequence of inputting lang kami nagkamali. Better pala to add the items first (assigning specific items to generic) before putting in the Quantity. There ma compute nya ang actual issuance quantity. This is OK.

ENHANCEMENT: We can currently edit the recipe. The previous posted pics the fields were disabled for editing kase posted na ung production. This is doable, pero very tedious because we need to change each value of each ingredient. See picture below: 2017-07-10 13_50_02-symphony cms 2 1 - city sports club cebu In this case, we manually computed the qty of gulaman to be 0.91kg just so we get to use 2 packs sa issued qty (actual na nagamit). Note that the yield is 44 Cups after we doubled the recipe. This is an easy example kase 1 ingredient lang. If marami ang ingredients, we will need to compute 1 by 1.

Incase, multiple ingredients, this is our suggestion: 2017-07-10 14_01_56-symphony cms 2 1 - city sports club cebu

We add a field Batch Quantity. This is the multiplier how many batches of the recipes were made. Formula will now be:

Issue Qty = ([Recipe Quantity] / [Conversion]) X [Batch Quantity]

instead of

Issue Qty = ([Recipe Quantity] / [Conversion]) X ([Production Quantity] / [Yield Quantity])

Tapos the Total Yield will be used to compute the Cost per Unit sa Recipe. I edited the form pala and placed the Total Yield field at the bottom right.

Total Recipe Cost / Total Yield = Price per Unit

What do you think?