Quality Function Deployment in Product Development

quality function deployment n.w
1 / 29
Embed
Share

Quality Function Deployment (QFD) is a structured method that helps translate customer requirements throughout product development. Learn about its history, key elements, and importance in improving communication and streamlining product realization processes.

  • Quality
  • Product Development
  • Customer Needs
  • QFD
  • Manufacturing

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. QUALITY FUNCTION DEPLOYMENT Dr. Raghu Nandan Sengupta Professor Department of Industrial and Management Engineering All figures are taken from(unless otherwise mentioned): Introduction to Statistical process Control Douglas. C Montgomery 6thEdition

  2. QUALITY FUNCTION DEPLOYMENT (QFD) QFD Is a structured method that is intended to transmit and translate customer requirements, that is, the Voice of the Customer through each stage of the product development and production process, that is, through the product realization cycle. These requirements are the collection of customer needs, including all satisfiers, exciters/delighters, and dissatisfiers.

  3. When is QFD Appropriate ? Poor communications and expectations get lost in the complexity of product development. Lack of structure or logic to the allocation of product development resources. Lack of efficient and / or effective product / process development teamwork. Extended development time caused by excessive redesign, problem solving, or fire fighting.

  4. Brief History of QFD Origin - Mitsubishi Kobe Shipyard 1972 Developed by Toyota and its Suppliers Expanded to other Japanese Manufacturers Consumer Electronics, Home Appliances, Clothing, Integrated Circuits, Apartment Layout Planning Adopted by Ford and GM in 1980s Digital Equipment, Hewlett-Packard, AT&T, ITT Foundation Belief that products should be designed to reflect customer desires and tastes

  5. Quality Function Deployments House of Quality Correlation Matrix 6 The House The House of Quality of Quality 3 Design Attributes 2 5 1 Customer Needs 4 Customer Perceptions Importance Rankings Relationships between Customer Needs and Design Attributes 7 Establishes the Flow down Relates WHAT'S & HOW'S Ranks The Importance Costs/Feasibility 8 Engineering Measures

  6. The House of Quality Key Elements Informational Elements Two types of elements in each House

  7. Manufacturing Environment Software Environment Service Environment QFD Flowdown Levels Of Granularity Customer Wants Customer Wants Customer Wants Technical Requirements Product Functionality Service Requirements Part Characteristics Service Processes System Characteristics Manufacturing Process Process Controls Design Alternatives Production Requirements Flow down Relates the Houses to each other

  8. Building the House of Quality 1. 2. Identify Design Attributes / Requirements 3. Relate the customer attributes to the design attributes. 4. Conduct an Evaluation of Competing Products. 5. Evaluate Design Attributes and Develop Targets. 6. Determine which Design Attributes to Deploy in the Remainder of the Process. Identify Customer Attributes

  9. 1. Identify Customer Attributes These are product or service requirements IN THE CUSTOMER S TERMS. Collected and analyzed through Market Research; Surveys; and Focus Groups. What does the customer expect from the product? Why does the customer buy the product? Salespeople and Technicians can be important sources of information both in terms of these two questions and in terms of product failure and repair. OFTEN THESE ARE EXPANDED INTO Secondary and Tertiary Needs / Requirements.

  10. What Does The Customer Want Customer Needs CTQs Ys Key Elements - Whats Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 Voice of the Customer Voice of the Customer

  11. How Important are the What s TO THE CUSTOMERS ? Customer Ranking of their Needs Customer Requirements Key Elements: 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 Voice of the Customer

  12. 2. Identify Design Attributes Design attributes are expressed in the language of the Designer / Engineer and represent the TECHNICAL Characteristics (Attributes) that must be deployed throughout the DESIGN, MANUFACTURING, and SERVICE PROCESSES. These must be MEASURABLE since the Output will be controlled and compared to Objective Targets. The ROOF of the HOUSE OF QUALITY shows, symbolically, the Interrelationships between Design Attributes.

  13. How Do You Satisfy the Customer What s Product Requirements Translation For Action X s Key Elements - Hows HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 Hows 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 WHAT'S HOW'S Satisfy the Customer Needs

  14. Correlation Matrix Impact Of The How s On Each Other Correlation Matrix Strong Positive Positive Negative Strong Negative Information HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 H L L M 65 45 21 36 8 52 4 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H M M L H L M M L H L 3 mils M 8 atm 40 psi 1 mm 12 in. 3 lbs 3 57 41 48 13 50 6 21 Conflict Resolution Conflict Resolution

  15. 3.Relating Customer & Design Attributes Symbolically we determine whether there is NO relationship, a WEAK one, MODERATE one, or STRONG relationship between each Customer Attribute and each Design Attribute. The PURPOSE is to determine whether the final Design Attributes adequately cover Customer Attributes. LACK of a strong relationship between a customer attribute and any design attribute shows that the attribute is not adequately addressed or that the final product will have difficulty in meeting the expressed customer need. Similarly, if a design attribute DOES NOT affect any customer attribute, then it may be redundant or the designers may have missed some important customer attribute.

  16. Strength of the Interrelation Between the What s and the How s H Strong 9 M Medium 3 L Weak Transfer Function Y = f(X) Key Elements: Relationship 1 HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 H L L M 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H M M L H L M M L H L M Untangling The Untangling The WebC WebC

  17. 4. Add Market Evaluation & Key Selling Points This step includes identifying importance ratings for each customer attribute AND evaluating existing products / services for each of the attributes. Customer importance ratings represent the areas of greatest interest and highest expectations AS EXPRESSED BY THE CUSTOMER. Competitive evaluation helps to highlight the absolute strengths and weaknesses in competing products. This step enables designers to seek opportunities for improvement and link QFD to a company s strategic vision and allows priorities to be set in the design process.

  18. 5. Evaluate Design Attributes of Competitive Products & Set Targets This is USUALLY accomplished through in-house testing and then translated into MEASURABLE TERMS. The evaluations are compared with the competitive evaluation of customer attributes to determine inconsistency between customer evaluations and technical evaluations. For example, if a competing product is found to best satisfy a customer attribute, but the evaluation of the related design attribute indicates otherwise, then EITHER the measures used are faulty, OR else the product has an image difference that is affecting customer perceptions. On the basis of customer importance ratings and existing product strengths and weaknesses, TARGETS and DIRECTIONS for each design attribute are set.

  19. Target Values for the How s Note the Units Information: How Much HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 H M L L 65 45 21 36 8 52 4 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H M M L H L M M L H L M 3 lbs How Much mils mm atm 12 40 psi in. 3 8 1 3 57 41 48 13 50 6 21 Consistent Comparison

  20. Information On The HOW'S More Is Better Less Is Better Specific Amount Target Direction HOW 6 HOW 1 H HOW 2 L HOW 3 HOW 4 HOW 5 L HOW 7 M Information : 65 45 21 36 8 52 4 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H M M L H L M M L H L M 57 41 48 13 50 6 21 The Best Direction The Best Direction

  21. 6. Select Design Attributes tobe Deployed inthe Remainder ofthe Process This means identifying the design attributes that: have a strong relationship to customer needs, have poor competitive performance, or are strong selling points. These attributes will need to be DEPLOYED or TRANSLATED into the language of each function in the design and production process so that proper actions and controls are taken to ensure that the voice of the customer is maintained. Those attributes not identified as critical do not need such rigorous attention.

  22. Technical Importance Which How s are Key Where Should The Focus Lie CI = Customer Importance Strength is measured on a 9, 3, 1, 0 Scale HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 Key Elements: 45 5 5 15 CI 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 45 9 9 3 36 2 6 12 4 36 1 M (CI *Strength) TI = column 57 41 48 13 50 6 21 Ranking The HOW'S Ranking The HOW'S

  23. Completeness Key Elements : Are All The How s Captured Is A What Really A How HOW 6 HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 7 C I 3 4 2 4 1 65 45 21 36 8 52 4 H L L M Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H 5 M M L H L M M L H L M CC = row (CI *Strength) 57 41 48 13 50 6 21 Have We Captured the HOW'S Have We Captured the HOW'S

  24. Using the House of Quality The voice of the customer MUST be carried THROUGHOUT the production process. Three other houses of quality are used to do this and, together with the first, these carry the customer s voice from its initial expression, through design attributes, on to component attributes, to process operations, and eventually to a quality control and improvement plans. In Japan, all four are used. The tendency in the West is to use only the first one or two.

  25. 1 Design Attributes Attributes Customer 2 Component Attributes Attributes Design 3 Process Operations Component Attributes 4 Quality Control Plan The How s at One Level Become the What s at the Next Level

  26. The Cascading Voice of the Customer Design Attributes are also called Functional Requirements Component Attributes are also called Part Characteristics Process Operations are also called Manufacturing Processes and the Quality Control Plan refers to Key Process Variables. HOWS NOTES: Y Critical to Quality Characteristics (CTQs) Key Manufacturing Processes X Key Process Variables

  27. QFD On Everything Set the Right Granularity Don t Apply To Every Last Project Inadequate Priorities Lack of Teamwork Wrong Participants Lack of Team Skills Lack of Support or Commitment Too Much Chart Focus Hurry up and Get Done Failure to Integrate and Implement QFD Common QFD Pitfalls

  28. Review Current Status At Least Quarterly Monthly on 1 Yr Project Weekly on Small Projects HOW 1 HOW 2 HOW 3 HOW 4 HOW 5 HOW 6 HOW 7 65 45 21 36 8 52 4 H L L M 5 5 3 4 2 4 1 Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 H M M L H The Static QFD L M H M L L 3 mils M 8 atm 40 psi 12 in. 1 mm 3 lbs 3 57 41 48 13 50 6 21

  29. Points to Remember The process may look simple, but requires effort. Many entries look obvious after they re written down. If there are NO tough spots the first time: It Probably Isn t Being Done Right!!!! Focus on the end-user customer. Charts are not the objective. Charts are the means for achieving the objective. Find reasons to succeed, not excuses for failure. Remember to follow-up afterward

Related


More Related Content