Collaborate on Bill Layout for Engineering with Ease Using airSlate SignNow

Bill layout for Engineering

so there are different formats of bill of materials we will discuss four here the first one is product tree so it could be single level uh tree or multi-level we have indented bill of material we have summarized mill of material and finally we have modular bill of material so first we will discuss product tree the most basic representation of the product structure is the product tree it's a graphical or tree representation of the bill of material the productry clearly illustrates the structural relationship of the parent item and all the components needed to build it so it shows the structural relationship of the parent that is actually the assembly so assembly or sub assembly is also sometimes called parent and all the components that are needed to build it the simple pictorial nature of the product tree makes it an ideal way to examine the product structure for evaluation teaching and testing so practically it is not very commonly used especially for very complex products but at least in books or for simple products that have maybe four or five levels then it is very useful so i will explain what is meant by the levels but if there are too many levels or there are too many component then this is not a preferred method and practically for complex products in the industries it is generally not used but for simple products or for training or instruction purposes it can be very useful so the product tree can be viewed as either a single level bill or multi-level bill of material single level or multi-level so first we will discuss what is a single level product tree in a single level bill only the items that are directly used in the production of the parent are shown so here is a very simple example of a personal computer so it has a screen two casings a keyboard a cover and a hardware kit so they are required to make the final personal computer now it is called a single level because after the final product only one level is shown one level of the sub assemblies or components so in other words the materials that are used to make the final computer are shown so the personal computer is the parent and the screen casing keyboard cover and hardware kit constitute the components needed in the assembly the numerical value these values 1 [Music] and 2 and so on these values in the paranthesis represent the quantity of each of the component items required to make one unit of the parent so simply in this case to make a personal computer we need one screen two casings one keyboard one cover and a hardware kit and there is only one level this level after the parent or the final assembly or the sub assembly that directly make the personal computer are shown their sub components are not shown so this is a single level wheel of material so of course this keyboard may have further some sub components but they are not shown here or hardware it may have further hardware items so they are not shown so we have stopped at the first level so this is called a single level bill then we have a multi-level bill of material where all parents and sub-assemblies are displayed so we have gone two steps ahead as compared to the previous bill of material that was shown on the previous slide so apart from this first level we are having their sub components as well so screen needs one blank and one casing to be built keyboard further has a keys kit and a blank board and a blank board further needs three side boards and one front board so in this case we are having three levels so how there are three actually the top one is called level zero the final assembly then we are having level one components or materials or sub-assemblies then we have level two and then we have level three so in the bill of materials shown one keyboard is required to build one personal computer so this one is showing that we need one keyboard to make one person computer however the keyboard itself is a sub assembly that is composed of keys kit and blank bolt so this keyboard further has two components so they are the keys kit and blank board so therefore the keyboard this keyboard is also parent that must be produced invented and issued when a personal computer is built so in simple words we need a keyboard in order to have a personal computer but in order to have a keyboard we need these two things the keys kit and blank board in order for the keyboard to be built and similarly for this blank board we need three side boards and one front board in order to make this blank gold so this is multi-level bill of material and from here you can get an idea of the sequence of steps to make this personal computer so first we need the lowest level item so this was level three so this was the lowest level in this case so if we start from scratch of course we are assuming that we are starting from scratch so first we need to build the side boards and the front board so that we can have this blank board and we need to have these four things the blank the casing the keys kit and of course this uh a blank border let me simplify it actually we need these two things the blank and the casing in order for the screen to be made and we need keys and blank board in order for the keyboard to be made but in order to start the final assembly that is joining these five components together we need these four components to be available because if any one of them is missing we cannot build the final computer for example if the casing is missing we cannot build the screen and if we don't have the screen we cannot make the personal computer so we need these two plus these two in order to make screen and keyboard respectively and once we have these one two three four and five sub assemblies or the components then we can make the personal computer so in a way you can say that uh from the bill of material shown in the form of a product tree multi-level bill of material we not only know the list of the components and the material that are required so they are obvious secondly we know the quantities of each of them required and thirdly in this case we also know the sequence of production we don't know of course many details about the production but we can have a fair idea of the sequence of production steps that are required and first we need the lowest level component then upper level level one and finally we can have the finished product so that is a big benefit of multi-level bill of materials so it is a good tool to visualize actually not only the quantities and the components and the quantities but also the relationship of the different components so just to re-emphasize that we know that these two components are required to make this thing and these two are required to make this so there is a good structural relationship that a multi-level bill of material shows now there is an important question that whether it is better to store product structure as a single level or multi-level bills of material in your erp or some other software now what does this question mean this product structure could be saved as multi multiple single level bills of material so for example first bill of material could be this that we have already seen [Music] right so this is one bill of material that could define the personal computer the final product we could have a second separate single level bill of material for screen [Music] right another single level bill of material for keyboard and yet another single bill of material for blank board so we could have four single level bill of materials instead of having this one multi-level bill of material that is shown on the screen we could have four separate single level bill of materials one for personal computer one for screen one for keyboard and another for blank so is it better to have a single bill of material like the one shown or it would have been better to have four single level bill of materials so generally speaking which of these two options is better so it is better to store information describing the product structure as a single level being if you are defining your product structure for the erp software so it is recommended to store information as a single level bill a series of single level bills is needed to completely define a product so a product structure begins as single level bills it is recommended it is the responsibility of manufacturing engineering to link these bill of materials in order to establish the structure for each assembly now we can then of course build the multi-level bill of material by grouping single levels bill of materials so first we define the single level wheel of materials for each of the component that has some sub components and then we can group single level bits of material to make the multi-level build of material as required so why why it is better single level product structures can be used as components in multiple assemblies so for example if you are let's continue with the same example so for example the keyboard assembly can be used on all companies personal computers so for example you have defined the keyboard assembly as a single level bill of material separately now you have saved different personal computers that you are building and say there are 20 types of personal computer that you are building now if you are defining each of the products as multi-level bill of material then you will be having a separate bill of material for each of the personal computers and for each of the personal computers you will have to define the keyboard assembly separately same assembly will have will have to be defined again and again assuming that this is the same keyboard sm but if you have defined keyboard assembly as a separate single level bill of material you have to simply retrieve that keyboard assembly definition for each of the personal computers even if you if we have a look at it in in a different perspective that this keyboard assembly was being used in all these 20 personal computers and we changed the design of the keyboard assembly now you have to change the definition of keyword assembly in each of the 20 models but if you had a separate definition of the keyboard assembly and you are retrieving it you have to make changes in that what we call master file or master definition and the same change could apply in all of the 20 personal computers so this is one benefit of using single level of material secondly once you are defining the keyboard assembly for example in this case or each of the 20 personal computers you are actually duplicating the records you are defining the same product 20 times so it is requiring redundant effort as well the number of records and the file size will also reduce if you are having single level definitions so you will have small relatively more number of files but small sized files and updating as i mentioned that if you are changing the design of one of the component that is used in many subsets you will have to update it at one place instead of doing it multiple times so that is the re these are the reasons why single level bills are recommended now if you have any argument you can you can have it and we can discuss