Transcript

Welcome to the next lecture on Design and Specification Requirements. If you look at the design tool whatever we have, design thinking process we have used, in this process there are five stages Empathy, then we have Definition of the Problem, then we will have Ideation then we will have Prototype Development and the last one will be the Validation and Testing.

So this week what we have seen is Empathy study tools and today we will see more about the definition of the problem. We were discussing till now about voice of the customer, customer Needs, and here we are going to convert the customer need into an engineering Specification. Till now it was all I need a lighter tool, I need a heavier tool, it has to collect more leaves. It was all qualitative now this qualitative has to be converted into a quantitative one such that the design team can work on solving the problem.

So, now today we will focus on Design and Specification Requirements. Engineering Design – so once the customer wants and the needs have been identified the design team converts hem to engineering requirements for the product. The engineering requirement becomes part of the design requirements for the product. So engineering requirement is now converted into design requirement. Successfully converting the customer wants and needs to meaningful engineering requirement needs good communication between the design and engineering group will happen and this will try to help us in developing good products. An engineering technique that is used for helping design team convert customer wants and need to the engineering requirements is done by a tool called as quality function deployment tool (QFB).

So what are the benefits of QFB. So it is basically customer driven so, creates focus on customer requirements, uses 02mpetitive information effectively prioritizes resources, identifies item that can be acting on. Reduced Implementation Time, Decreases midstream Design Changes, avoid future development redundancy, identifies future Application Opportunity, Surfaces Missing Assumptions and Promotes Teamwork and Provides Proper Documentation. These are all the benefits of quality function deployment (QFD). So it is otherwise called as House of Quality.

In a house of quality first thing is you will have customer requirement. This is nothing but the voice of the customer which is done. So now this customer requirement, how are you going to technically describe this voice of the customer? Now between the customer requirement and the technical descriptions you try to have a relationship matrix between the requirements and the descriptors, you will have a relationship matrix and if you see the top triangle we will try to have a relationship amongst these technical descriptors amongst the technical descriptors we will try to have a relationship that is done in this Triangle. Then we try to take the customer voice and then we try to ask them to get the prioritizing their requirements. And then we try to prioritize technical description, so here what we do is we try to take this detail and amongst them what are the important technical descriptors to be solved that’s what we do here ranking them one, Two, three, four, five. So customer requirements to technical description there is a relationship matrix and then you try to prioritize the customer requirement and prioritize the technical descriptors. So here also you can have ten descriptors you try to prioritize and then try to attack them first so that you can try to solve the Problem. So building a House of Quality is nothing but WHY. So list of customer Requirements -you try to ask, what are your wants?

Next, list of technical descriptors – how are you going to achieve the customer requirements? This relationship is what and how is the relationship between the requirements and the descriptors. Then development interrelationship is in the top. Then you try to do competitive assessment which is not here but if one product is already existing we try to take that product and then we try to strip that product right on all the significant requirements and then we try to assess our product whatever is there or whatever is there in your mind with respect to competitors so, that is called as Competitive Assessment.

Then we try to prioritize the customer requirement, then we try to prioritize the technical descriptors. So, now what I have done is I have split the QFD matrix into small Small, small modules so that you can better understand. So customer requirements as we studied earlier Primary, Secondary, Tertiary so we try to write down what is primary? For that primary you will have I said 3 or 10 thought process will be there. So then we try to write down primary. Secondary thought process and then here we will try to write down the technical descriptors Right, and then after writing this technical descriptors we try to write down a relationship between the customer requirement and the technical Descriptors. So, here in the relationship we try to give weightages we try to give dark and dot where it is all nine points which is highly important, then which is medium, and which is very weak. The differences between the three has to be when you give a magnitude you try to give a larger magnitude difference. So that when you try to multiply you try to see a heavier impact on the ultimate Solutions. So this is only a mathematical representation you can have one, two, three or ten, 20, 30 or 10, 30, 90 whatever it is okay. So the relationship so here we try to draw between the customer requirement and the technical descriptors.

So now this is what is customer requirement, technical descriptors, primary/secondary. Now, what we are doing is the second stage. This is the relationship amongst the technical descriptors. How strong is this relationship between the first technical descriptor and the ninth technical Descriptor. So we say strongly positive, Positive, negative, strongly negative. So again here you try to give the values. So this is mark and then this values are given. Why are you more serious about these values because finally we try to multiply these values as a weightage factor or we try to sum up and then try to get some quantifying values. Moment you have a quantifying values then it tries to easily give you the importance of that particular technical descriptor or the customer requirement. So here the relationship between the customer requirement and the technical descriptor is What Vs How. What the customer wants and how are you going to make it? Now we will see little more in detail so the first front half till this we, now we will see the bottom portion of the QFD. So in the bottom portion of the QFD, what we do is we try to write down what are the Customer Competitive Assessment. Customer Comment and Technical Competitive Assessment with two different competitors to this product what is our thing what is customer. The Product A what does it do? Product B what does it do in terms of technical Descriptions.

So here we will try to full this data and this data. From this what we do, is we try to write down the degree of technical difficulty in achieving the technical descriptor, then target values of absolute values then relate to weightages. So these are all again we try to get and this try to prioritize the technical description and as far as the customer importance we try to note down the customer importance, target values, scale up factors. Then you will have scale points then absolute weightages you multiply and then you get some values. Let us look at a simple example we have done for a Drone. Drone is a unmanned air vehicle which is flown above the ground surface for various applications like recording, surveillance taking, agricultural or image processing, So we use drone. So here we can see that we have put the customer requirement. We have put the technique acquirements are it has to be stylish, it has to be Lightweight, it has to be quiet, it has to have a hard a super HD camera, it has to have it has to have a high quality finish. so all these things now you see what we
have written as customer requirement or it is not written as per the priorities. We have written all and then we are trying to do the ranking. Then how do we achieve it is the technical descriptors we have done so now this technical descriptors we will try to see a relationship, amongst them we will try to do here in this top Triangle. Then what and how relationship is drawn here.

Then we have customer the competitor assessment is done and then we try to convert all these things into magnitude values such that we try to get more understanding towards defining the problem from the customer needs. Customer need was qualitative now you have converted into an engineering quantitative values. So a product development cycle if you see it starts from customer requirement, design Requirement, what you get is that design requirement. So you do the relationship between these two what finally you get is a design requirement.

Now, this design requirement you try to have a relationship with part quality characteristics. So then what you have you get the relationship between design requirement and part quality characteristics, what is the output you get is a part quality Statistics. This is the first HOQ, this is the second HOQ, the third HOQ and the fourth HOQ. So from the part quality characteristics we try to do Key Process Operations. So from this relationship we try to get the importance of key process operations.

Now with the key process operations you try to have a relation with production requirements and what you have is the production start which comes out. So this is how a typical product development cycle flows and we try to have relationship between customer Requirement, design requirement, design requirement to part quality, part quality to key process operations, key process to product requirements. So in conclusion in a house of quality HoQ we saw QFD gives orderly way of obtaining information, it shortens the product development cycle, it is considerably reduced startup cost, fewer engineering changes will happen if you follow QFD. Reduce the chance of oversights during the design process, environment of teamwork always behind HoQ together, then consensus decisions and preserves everything in writing. So all these things are advantage of HoQ. With this lecture we are completing four weeks of our course. Till now we saw Design Thinking, various stages of design Thinking, we in this design thinking stage we saw Empathy study as well as definition of the problem. We will now in the rest of the course see Ideation tools used for ideation, frugal innovation, then what are the different types of prototype, how do we make low fidelity prototype, high fidelity prototype, and then finally we will conclude the course with the case Study.

Till now whatever we have seen we have given lot of live examples. Please try to use these live examples to your own and then start customizing a problem, start solving it you will then appreciate the use of Design Thinking tool for developing agricultural implements or products.

Thank you