Quality Function Deployment

Slides:



Advertisements
Similar presentations
Quality Function Deployment (QFD)
Advertisements

Designing Products & Engineering. Customers Requirements l Normal Requirements are typically what we get by just asking customers what they want. l Expected.
House of Quality. Quality Function Deployment Walls (Customer requirements) Right side Prioritized customer requirement Planning matrix Left side Voice.
IBM Corporate Environmental Affairs and Product Safety
Stage-Gate Process & Qualify Function Deployment
System Development Life Cycle (SDLC)
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
W5HH Principle As applied to Software Projects
1 Thinking Visually. 2 Diagramming for change Change produces opportunities for organisations, but it can also provides numerous problems. When evaluating.
Quality Function Deployment
Planning and Strategic Management
CISB444 - Strategic Information Systems Planning
Quality Function Deployment
VM SAVE International providing value ….. to the world VM Briefing SAVE International introduces “ Value Methodology ” Presentation version 1.
Chapter 2Copyright ©2008 by South-Western, a division of Thomson Learning. All rights reserved 1 Learning Outcomes – Chapter 2 1. Understand the importance.
Greg Baker © Part One The Foundations – A Model for TQM Chapter # 3 Design for quality.
IE673Session 4 - Customer Relationships1 Customer Relationships (The Voice of the Customer)
QUALITY FUNCTION DEPLOYMENT CHAPTER 12
Quality Function Deployment
Quality Function Deployment(QFD) Joseph Appianing Dan Sheehan Matt Casey October 29,2008.
Quality Function Deployment Quality Function Deployment QFD Vivian Cherie KJ.
TSM: Safety Management in a Quality Management Setting
Total Quality Management By: Zaipul Anwar Manager, R & D Dept. Business & Advanced Technology Centre UTM.
Organizational Project Management Maturity: Roadmap to Success
Designing Products and Processes with a Future. What does it take? Involve the customer Meet with the customer Listen to customer Educate the customer.
Quality Function Deployment
1 IMC Planning Knowing the Score In IMC, a plan is similar to a musical score. The IMC plan details which marketing communications and media should be.
Introduction to Computer Technology
The New Product and Services Development Process By SK Winning Innovations for Tomorrow (WIT)
Introduction to Quality Function Deployment
Quality Function Deployment
IET 619:Quality Function Deployment
Foundations of Planning
Quality Function Deployment
COMPANYWIDE ASSESSMENT OF QUALITY
Scoring 1. Scoring Categories 1 – 6 (Process Categories) Examiners select a score (0-100) to summarize their observed strengths and opportunities for.
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 8 Performance Measurement and Strategic Information Management.
Quality Function Deployment. What is QFD? A method of transferring customer needs and requirements into technical specifications for new product and service.
New Product Development Management NPDM 4 Mohsen SADEGHI Department of Graduate School of Management and Economics Sharif University of Technology.
SYSE 802 John D. McGregor Module 6 Session 1 Systems Engineering Analyses II.
Outcome Based Evaluation for Digital Library Projects and Services
T OPICS: House of Quality (QFD) IENG 464 / 465 F ALL / S PRING 2013 – 2014.
Kenneth J. Andrews EMP Manufacturing Systems: EMP-5179 Module #9: Quality Function Deployment (QFD) Dr. Ken Andrews High Impact Facilitation Fall.
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
QUALITY FUNCTION DEPLOYMENT LISTEN VOICE OF THE CUSTOMER First application of QFD was at Mitsubishi, Japan, in 1972 by Dr. Mizuno. In production of mini-vans.
Chapter 14: Using the Scalable Decision Process on Large Projects The process outlined is meant to be scaleable. Individual steps can be removed, changed,
Lecture-3.
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 7 Process Management.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
Chapter Fourteen Communicating the Research Results and Managing Marketing Research Chapter Fourteen.
PRESENTED BY GROUP 1 QUALITY FUNCTION DEPLOYMENT.
© G. A. Motter, 2006, 2008 & 2009 Illustrated by Examples Quality Function Deployment and Selection Matrices Customer Driven Product Development.
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Information, Analysis, and Knowledge Management in the Baldrige Criteria Examines how an organization selects, gathers, analyzes, manages, and improves.
Chapter 12 Translating Expectations to Specifications CEM 515: Project Quality Management Prof. Abdulaziz A. Bubshait King Fahd University of Petroleum.
© Wiley Total Quality Management by Adnan khan.
Requirement Engineering
New Product Development Page 1 Teddy Concurrent Engineering by Teddy Sjafrizal.
House of Quality Tutorial for Medical Device Design CAPT Kimberly Lewandowski-Walker National Expert, Medical Devices U.S. Food and Drug Administration.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
Manufacturing Management Prayash Neupane. Manufacturing Management MM refers to all aspects of the product manufacturing process. From assembly design.
Quality Function Deployment
Total quality management
Principles of Information Systems Eighth Edition
Chapter Outline Innovation, Technological Change, and Competition
The Systems Engineering Context
Quality Function Deployment
Chapter 7 Process Management.
Chapter 11 Quality Function Deployment (QFD)
Presentation transcript:

Quality Function Deployment By Zaipul Anwar Business & Advanced Technology Centre, Universiti Teknologi Malaysia

Quality Function Deployment Hin Shitsu Ki No Ten Kai "A group of courageous people working in harmony pursuing the finest detail to unlock the organization and roll out products that the multitudes in the marketplace will value." Glenn Mazur

Quality Function Deployment 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.

Creative Definitions of QFD A systematic way of documenting and breaking down customer needs into manageable and actionable detail. A planning methodology that organizes relevant information to facilitate better decision making. A way of reducing the uncertainty involved in product and process design. A technique that promotes cross-functional teamwork. A methodology that gets the right people together, early, to work efficiently and effectively to meet customers’ needs.

Key Thought Throughout Quality Function Deployment is a Valuable Decision Support Tool, But it is Not a Decision Maker

Better Designs in Half the Time! QFD Is a Productivity Enhancer What Does QFD Do? Better Designs in Half the Time! CONCEPT CUSTOMER Plan Design Redesign Manufacture “Traditional Timeline” Plan Design Redesign Manufacture Benefits QFD Is a Productivity Enhancer

Why Does QFD Work? The Quality Lever PRODUCT DESIGN Why Does QFD Work? PROCESS DESIGN 100:1 PRODUCTION IMPROVE PRODUCT 10:1 1:1 LOW VISIBILITY LOW REWARD TIME HIGH VISIBILITY HIGH REWARD The Quality Lever

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.

Return on Investment from Using QFD Companies using QFD to reflect "The Voice of the Customer" in defining quality have a competitive advantage because there is/are: 1. Fewer and Earlier Design Changes 2. Fewer Start-up Problems 3. Shorter Development Time 4. Lower Start-up Costs 5. Warranty Cost Reductions 6. Knowledge Transfer to the Next Product 7. Customer Satisfaction

Origin - Mitsubishi Kobe Shipyard 1972 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

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

Two Types of Elements in Each House Key Elements Informational Elements The House of Quality Two Types of Elements in Each House

QFD Flowdown Levels Of Granularity Customer Wants Technical Requirements Part Characteristics Manufacturing Process Production Requirements Manufacturing Environment Customer Wants Product Functionality System Characteristics Design Alternatives Software Environment Customer Wants Service Requirements Service Processes Process Controls Service Environment QFD Flowdown Levels Of Granularity Flowdown Relates The Houses To Each Other

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

1. Identify Customer Attributes These are product or service requirements IN THE CUSTOMER’S TERMS. Market Research; Surveys; 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.

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

Key Elements: Customer Requirements How Important Are The What’s TO THE CUSTOMER Customer Ranking of their Needs Key Elements: Customer Requirements Need 1 Need 2 Need 3 Need 4 Need 5 Need 6 Need 7 5 3 4 2 1 Customer Importance Voice of the Customer

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.

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

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

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 it 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.

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

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 links QFD to a company’s strategic vision and allows priorities to be set in the design process.

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.

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

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

6. Select Design Attributes to be Deployed in the Remainder of the 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.

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

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

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.

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

The Cascading Voice of the Customer HOWS NOTES: “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. WHATS Y Critical to Quality Characteristics (CTQs) The Four Houses of Quality Key Manufacturing Processes X Key Process Variables

Common QFD Pitfalls 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

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

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