systems
Member
We are manfacturer and exporters.At presentwe are in the process of implemetation stage and we are now faced with this particular issue relating to Bill of materials .
Case Study
For e.g I have an item -ABC (item no) -Fruit & Nut Chocolate (Item description)
Standard BOM for this item would be as follows
1 Fruit- x qty
2 Nuts-x qty
3 Sugar-xqty
4 Chocolate-x qty
5 Cocoa butter- x qty
6 Emulsifying agents- x qty
7 Stabilising agents-x qty
8 Aluminium foil(Packaging item)-x qty
9 Blue Packaging Wrapper/ Outer Cover(Packaging item)-x qty
10 Product Label- x qty
11 Shipping Carton - x qty
12 Shipping Label - x qty
In the above items highlighted in green (Sno.1 - S.no-7) are raw materials and item highlighted in blue (S.no-8- S.no-12) are Packaging items.
In most of our cases the packaging specifications(items Sno.8- Sno.-12) are given by customer and they differ from one customer to another. i.e instead of having the standard Blue wrapper (Sno.9)
Customer (A)- wants Greenstripped wrapper
Customer (B)- wants yellow polka dot Wrapper
Customer (C)- wants Red psycadelic tri-color combination wrapper.
All customers could request a special product label, shipping carton or shipping label also.
Notes
In all the above cases only my packaging requirement is changing and my raw materials are the same. In this case I do not generate a new item number for each specification.
I generate a new item number only when any of my raw material content(s) is changed i.e in case of cocoa butter i want to use milk.
We have tried to use the Configurator to take care of this problem, but it appears that everytime we would add a new customer, whose packaging requirements are a little different, I would have to modify the configurator, which I don't think is a task we can entrust to an ordinary user. Modifing the configurator also envolves modifying assembling inclusion rules and adding new values for the new requirements and it is by no means a simple operation.
On an average our company would add about 10-15 new specific customer products in the system every day.
This would be a typical requirement for any OEM equipments manufacturer. He would make products and label and packgae them according to specific requirements of the customer. So we feel that you would have a solution for this.
Requirement:
We would like to know how would the setup take care of situations like this.
I would not like to create a new items code every time I sell the same product with a different packaging specification to a new customer.
Is it possibile for us to store the specific packaging requirement for every customer which I could associate to a product for that customer.
Issue No. 2 - Configurator setting
Case Study
Suppose we manufactured Pizza
We offered 2 basic broad category of Pizza - Vegetarian & Non Vegetarian
Options available under both kind are - Thin crust, Pan crust
Options available under both kind for size are - small, large, regular
Other Options are different combinations of toppings names as - Supreme, Classic, Veggie Lover
Optional extra toppings - 10 different toppings
Now lets say the option of topping combination of "Supreme" was not available under thin crust and veggie lover was not available as a small size pizza. And also under the toppings we have all toppings - both vegetarian & non vegetarian.
Supreme is non - vegetarian & Classic & Veggie Lovers are vegetarian pizza.
Now if we were to use the configurator for this and as per our consulting team any time I made the following selection, this is what I would have to do-
If I wanted a vegetarian pizza, thin crust, small size, veggie lovers with 2 extra toppings which I left the user to make a selection on. We also assume that the user does not know the above validations and does not also know that peporni is non-vegetarian.
The user could select
Vegetarian
Thin crust
Small
Veggie lover
Peperoni
Green Pepper
This is an incorrect combination because Veggie lovers is not available in small size & Peperoni would make the pizza non-vegetarian.
On saving this configutaion,the software would then validate and throw an error that the selection is incorrect. There is no way the user can know where he made the mistake in his selection. As per our consulting team, the user will have to try a different combination everytime to find out the correct combination or he would be supposed to know what he needs to select in the configurator. Theorectically it would mean that the probability of the user coming up with the correct configutaion would be 360:1 (2x2x3x3x10 = 360). This would be quite absurd.
Requirements
How can we setup up validations during the entry screen so that user does not make wrong selection.
If the user had chosen the first selection as vegetarian, then he should not be able to select -
Combination of Topping - Supreme
Non-vegetarian extra toppings - e.g. peporoni
If the user had chosen the small size, then he should not be able to select -
combination of topping - Veggie lovers
Non-vegetarian extra toppings - e.g. peporoni
Pls advise how would the configutaor setup have to be done for this.
"
Case Study
For e.g I have an item -ABC (item no) -Fruit & Nut Chocolate (Item description)
Standard BOM for this item would be as follows
1 Fruit- x qty
2 Nuts-x qty
3 Sugar-xqty
4 Chocolate-x qty
5 Cocoa butter- x qty
6 Emulsifying agents- x qty
7 Stabilising agents-x qty
8 Aluminium foil(Packaging item)-x qty
9 Blue Packaging Wrapper/ Outer Cover(Packaging item)-x qty
10 Product Label- x qty
11 Shipping Carton - x qty
12 Shipping Label - x qty
In the above items highlighted in green (Sno.1 - S.no-7) are raw materials and item highlighted in blue (S.no-8- S.no-12) are Packaging items.
In most of our cases the packaging specifications(items Sno.8- Sno.-12) are given by customer and they differ from one customer to another. i.e instead of having the standard Blue wrapper (Sno.9)
Customer (A)- wants Greenstripped wrapper
Customer (B)- wants yellow polka dot Wrapper
Customer (C)- wants Red psycadelic tri-color combination wrapper.
All customers could request a special product label, shipping carton or shipping label also.
Notes
In all the above cases only my packaging requirement is changing and my raw materials are the same. In this case I do not generate a new item number for each specification.
I generate a new item number only when any of my raw material content(s) is changed i.e in case of cocoa butter i want to use milk.
We have tried to use the Configurator to take care of this problem, but it appears that everytime we would add a new customer, whose packaging requirements are a little different, I would have to modify the configurator, which I don't think is a task we can entrust to an ordinary user. Modifing the configurator also envolves modifying assembling inclusion rules and adding new values for the new requirements and it is by no means a simple operation.
On an average our company would add about 10-15 new specific customer products in the system every day.
This would be a typical requirement for any OEM equipments manufacturer. He would make products and label and packgae them according to specific requirements of the customer. So we feel that you would have a solution for this.
Requirement:
We would like to know how would the setup take care of situations like this.
I would not like to create a new items code every time I sell the same product with a different packaging specification to a new customer.
Is it possibile for us to store the specific packaging requirement for every customer which I could associate to a product for that customer.
Issue No. 2 - Configurator setting
Case Study
Suppose we manufactured Pizza
We offered 2 basic broad category of Pizza - Vegetarian & Non Vegetarian
Options available under both kind are - Thin crust, Pan crust
Options available under both kind for size are - small, large, regular
Other Options are different combinations of toppings names as - Supreme, Classic, Veggie Lover
Optional extra toppings - 10 different toppings
Now lets say the option of topping combination of "Supreme" was not available under thin crust and veggie lover was not available as a small size pizza. And also under the toppings we have all toppings - both vegetarian & non vegetarian.
Supreme is non - vegetarian & Classic & Veggie Lovers are vegetarian pizza.
Now if we were to use the configurator for this and as per our consulting team any time I made the following selection, this is what I would have to do-
If I wanted a vegetarian pizza, thin crust, small size, veggie lovers with 2 extra toppings which I left the user to make a selection on. We also assume that the user does not know the above validations and does not also know that peporni is non-vegetarian.
The user could select
Vegetarian
Thin crust
Small
Veggie lover
Peperoni
Green Pepper
This is an incorrect combination because Veggie lovers is not available in small size & Peperoni would make the pizza non-vegetarian.
On saving this configutaion,the software would then validate and throw an error that the selection is incorrect. There is no way the user can know where he made the mistake in his selection. As per our consulting team, the user will have to try a different combination everytime to find out the correct combination or he would be supposed to know what he needs to select in the configurator. Theorectically it would mean that the probability of the user coming up with the correct configutaion would be 360:1 (2x2x3x3x10 = 360). This would be quite absurd.
Requirements
How can we setup up validations during the entry screen so that user does not make wrong selection.
If the user had chosen the first selection as vegetarian, then he should not be able to select -
Combination of Topping - Supreme
Non-vegetarian extra toppings - e.g. peporoni
If the user had chosen the small size, then he should not be able to select -
combination of topping - Veggie lovers
Non-vegetarian extra toppings - e.g. peporoni
Pls advise how would the configutaor setup have to be done for this.
"