Understanding Customer Requirements

Slides:



Advertisements
Similar presentations
Quality Function Deployment (QFD)
Advertisements

QUALITY FUNCTION DEPLOYMENT
Designing Products & Engineering. Customers Requirements l Normal Requirements are typically what we get by just asking customers what they want. l Expected.
Introduction to Marketing
Using QFD to Establish Design Specifications
Affinity Diagrams.
Ken YoussefiMechanical Engr. Dept., UC Berkeley 1 Product Specifications.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
Project Clarification: Objectives Tree BE 20–Engineering Design with Computer Applications Week 4: 15-September-2004.
8 September Announcements  GIT Class: Friday 3-5 SN 115 (Peter Parente)  Information for Project Links PageProject Links Page  Hot Topics Teams.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Quality Function Deployment
Greg Baker © Part One The Foundations – A Model for TQM Chapter # 3 Design for quality.
QUALITY FUNCTION DEPLOYMENT
IE673Session 4 - Customer Relationships1 Customer Relationships (The Voice of the Customer)
Wrapping Up PBL Problems Hal White Dept. of Chemistry and Biochemistry Workshop Wednesday June 28, 2006 about Developed by with who uses Presented on emphasizing.
QUALITY FUNCTION DEPLOYMENT CHAPTER 12
Analysis Concepts and Principles
Quality Function Deployment
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Product Design.
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
Quality Function Deployment Quality Function Deployment QFD Vivian Cherie KJ.
Designing Products and Processes with a Future. What does it take? Involve the customer Meet with the customer Listen to customer Educate the customer.
Creating a Customer Focus
Principles of Food, Beverage, and Labor Cost Controls, Ninth Edition.
Quality Function Deployment
IET 619:Quality Function Deployment
New Products Management Part IV: Development Chapter 13 Design.
Leaders Facilitate the Planning Process
Mantova 18/10/2002 "A Roadmap to New Product Development" Supporting Innovation Through The NPD Process and the Creation of Spin-off Companies.
Quality Function Deployment
P RODUCT D ESIGN AND D EVELOPMENT Chapter 3, 4 & 5 – Product Planning, Customer Needs & Product Specifications.
Principles of User Centred Design Howell Istance.
ENGM 620: Quality Management Session Five – Sept. 25, 2012 Organizing for Quality, Part I –Voice of the Customer –Voice of the Market –Process and Procedures.
Architecture Business Cycle
Quality Function Deployment. What is QFD? A method of transferring customer needs and requirements into technical specifications for new product and service.
TQM TECHNIQUES BENCHMARKING Target key areas for improvement within operations – Increase productivity, competitiveness, and quality – Quality results.
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.
Introduction to Marketing
8 Identifying Market Segments and Targets
Customer Benefits, Product Features, Product Specifications IPD February 15, 2005.
Design Specifications and QFD. Establishing the Need Sources: –The market: what do customers want? –New technology: Creates a market Risky and expensive.
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.
Advertising and Sales Promotion ©2013 Cengage Learning. All Rights Reserved. Chapter 3.
Experience the QFD : An Automobile Bumper Client Request: There is too much damage to bumpers in low-speed collisions. Customer wants a better bumper.
Chapter 27 The Engineering Design Process. Learning Objectives Describe the various factors that are changing the design process Discuss the steps in.
Quality Function Deployment. Example Needs Hierarchy.
11 ES1050 – Introductory Engineering Design and Innovation Studio Introduction to Design Process Customers’ Needs Product Design Specifications Sept. 23,
Chapter 12 Translating Expectations to Specifications CEM 515: Project Quality Management Prof. Abdulaziz A. Bubshait King Fahd University of Petroleum.
Developing a Marketing Plan
Market Analysis Glencoe Entrepreneurship: Building a Business Doing Market Research Industry and Market Analysis 6.1 Section 6.2 Section 6 6.
House of Quality Tutorial for Medical Device Design CAPT Kimberly Lewandowski-Walker National Expert, Medical Devices U.S. Food and Drug Administration.
Quality Function Deployment (QFD) Getting from the voice of the customer to technical design specifications.
SQU College of Education Instructional & Learning Technologies Department TECH4211.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
ME/MECA 238A1 ME/MECA 238A - Mechanical/Mechatronic Design Project I Course notes prepared by G.A. Kallio, based on The Mechanical Design Process, by D.G.
1 © 2006 The McGraw-Hill Companies, Inc., All Rights Reserved Chapter 4 Product Design.
Manufacturing Management Prayash Neupane. Manufacturing Management MM refers to all aspects of the product manufacturing process. From assembly design.
Marketing Plan.
Chapter 4 Product Design. Chapter 4 Product Design.
Section 4-Part 2 Self Study
Why QFD….? Product should be designed to reflect customers’ desires and tastes. House of Quality is a kind of a conceptual map that provides the means.
Business Essentials, 7th Edition Ebert/Griffin
Quality Function Deployment
3.1 Introduction. Chapter 3 Understand the problem and the development of Engineering specification.
Chapter 7 Process Management.
Chapter 11 Quality Function Deployment (QFD)
Quality Function Deployment (QFD)
Presentation transcript:

Understanding Customer Requirements Principles of Design Zahed Siddique Assistant Professor School of Aerospace and Mechanical Engineering University Of Oklahoma zsiddique@ou.edu

Need to focus Moving in the wrong direction at a fast pace is still moving in the wrong direction. Right Wrong

Information on QFD…. Developed in Japan in the mid 1970s Introduced in USA in the late 1980s Toyota was able to reduce 60% of cost to bring a new car model to market Toyota decreased 1/3 of its development time Used in cross functional teams Companies feel it increased customer satisfaction

Why….? Product should be designed to reflect customers’ desires and tastes. House of Quality is a kind of a conceptual map that provides the means for interfunctional planning and communications To understand what customers mean by quality and how to achieve it from an engineering perspective. HQ is a tool to focus the product development process

QFD Target

Important points Should be employed at the beginning of every project (original or redesign) Customer requirements should be translated into measurable design targets It can be applied to the entire problem or any subproblem First worry about what needs to be designed then how It takes time to complete

Components of House of Quality Hows vs Hows Components of House of Quality Customer Evaluation Who Hows Now This Product Who vs. Whats Whats Whats vs Hows Now vs What Units Hows vs How Muches How Muches This Product Targets Targets

Extensions to House of Quality Customer Evaluation Ratio of Improvement Useful Data Target This Product Weighted Importance Importance % Units This Product Targets Technical Difficulty

Step 1: Who are the customers? To “Listen to the voice of the customer” first need to identify the customer In most cases there are more than one customer consumer regulatory agencies manufacturing marketing/Sales Customers drive the development of the product, not the designer

Step 2: Determine the customers’ requirements Need to determine what is to be designed Consumer product works as it should lasts a long time is easy to maintain looks attractive incorporated latest technology has many features List all the demanded qualities at the same level of abstraction

Step 2: cont... Manufacturing Marketing/Sales easy to produce uses available resources uses standard components and methods minimum waste Marketing/Sales Meets customer requirements Easy to package, store, and transport is suitable for display

Kano Model Basic Quality: These requirements are not usually mentioned by customers. These are mentioned only when they are absent from the product. Performance Quality: provides an increase in satisfaction as performance improves Excitement Quality or “wow requirements”: are often unspoken, possibly because we are seldom asked to express our dreams. Creation of some excitement features in a design differentiates the product from competition.

Types of customer requirements Functional requirements describe the product’s desired behavior Human factors Physical requirements Reliability Life-cycle concerns Resource concerns Manufacturing requirements

How to determine the Whats? Customer survey (have to formulate the questions very carefully) If redesign, observe customers using existing products Combine both or one of the approaches with designer knowledge/experience to determine “the customers’ voice”

Affinity Diagram Provides structure for verbal data by creating natural clusters or groups Ensures that the list of demanded qualities are complete and expressed at the same level of detail

Constructing Affinity Diagram Set a brainstorming session to list all possible requirements Record each element of the list on small cards Place all cards on a table randomly Silent mode Spend time reading all demanded qualities Start at the same time, once everyone is ready - everyone quickly and without thought find two demanded qualities that have something in common If you find a demanded quality is not where you think it belongs, move it. If it is moved again, make a duplicate and talk about it later. The process continues until all demanded qualities are in a group.

Constructing Affinity Diagram Discussion Mode Begin discussion after group composition for the demanded qualities becomes stable First review the demanded qualities that seemed to have more than one home Select a descriptive name for the groups. Group names must also be demanded qualities, but at a higher level of abstraction Look at each group and judge if all elements are at the same level of abstraction Check each group by asking “If this is the name of the group, what elements should be included but are missing?” Next test for missing groups. Check with the types of customer requirements list

Step 3: Determine Relative Importance of the Requirements: Who vs. What Need to evaluate the importance of each of the customer’s requirements. Generate weighing factor for each requirement by rank ordering or other methods Hows vs Hows Customer Who Evaluation Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Rank Ordering Order the identified customer requirements Assign “1” to the requirement with the lowest priority and then increase as the requirements have higher priority. Sum all the numbers The normalized weight Rank/Sum The percent weight is: Rank*100/Sum

Step 4: Identify and Evaluate the Competition: How satisfied is the customer now? The goal is to determine how the customer perceives the competition’s ability to meet each of the requirements it creates an awareness of what already exists it reveals opportunities to improve on what already exists Hows vs The design: 1. does not meet the requirement at all 2. meets the requirement slightly 3. meets the requirement somewhat 4. meets the requirement mostly 5. fulfills the requirement completely Hows Customer Who Evaluation Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Step 5: Generate Engineering Specifications: How will the customers’ requirements be met? The goal is to develop a set of engineering specifications from the customers’ requirements. Restatement of the design problem and customer requirements in terms of parameters that can be measured. Hows vs Hows Customer Who Evaluation Each customer requirement should have at least one engineering parameter. Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Step 6: Relate Customers’ requirements to Engineering Specifications: Hows measure Whats? This is the center portion of the house. Each cell represents how an engineering parameter relates to a customers’ requirements. 9 = Strong Relationship 3 = Medium Relationship 1 = Weak Relationship Blank = No Relationship at all Hows vs Hows Customer Who Evaluation Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Engineering specifications maybe dependent on each other. Step 7: Identify Relationships Between Engineering Requirements: How are the Hows Dependent on each other? Engineering specifications maybe dependent on each other. 9 = Strong Relationship 3 = Medium Relationship 1 = Weak Relationship -1 = Weak Negative Relationship -3 = Medium Negative Relationship -9 = Strong Negative Relationship Blank = No Relationship at all Hows vs Hows Customer Who Evaluation Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Step 8: Set Engineering Targets: How much is good enough? Determine target value for each engineering requirement. Evaluate competition products to engineering requirements Look at set customer targets Use the above two information to set targets Hows vs Hows Customer Who Evaluation Hows Now This Product Whats Who vs. Whats Whats vs vs What Hows Now Units Hows vs How This Product Muches How Muches Targets Targets

Relationships Among Engineering Characteristics Identifying performance measure conflicts Customer Evaluation Customer Evaluation Record customer performance ratings for your Similar product and competitors’ products Engineering Characteristics Record Performance measures for each customer demanded quality Customer Evaluation Relative Importance Importance for each demanded quality needs to be determined Customer Attributes The first step is to list all the demanded qualities at the same level of abstraction Engineering Influence Customer Qualities Relationship between demanded customer qualities and Engineering Performance Objective Measures Units Technical benchmarking Determining Important Characteristics Technical Difficulty Importance Technical Difficulty associated with achieving Targets/improvements and importance of technical characteristics Units Targets Setting Technical Targets Targets Technical Difficulty Importance

Components of House of Quality Hows vs Hows Components of House of Quality Customer Evaluation Hows Who Now This Product vs Whats vs Whats Who vs. Whats What Hows Now Weighted Importance Importance % Addition to the House of Quality presented in text book Units Hows vs How This Product Muches How Muches Targets Targets Rank Technical Difficulty Selected

Creating the Requirement List Contents of Requirement List Specify if the individual items are demands or wishes in the clearest possible terms Tabulate Quantitative and Qualitative aspects Collect further information If possible rank wishes as being of major, medium or minor importance Living document Arrange the requirements in clear order Define the main objective and the main characteristics Split into identifiable groups Enter the Requirement list on standard forms and circulate Examine Objections

Requirement List

Requirement List Example Name 1 Name 2 Name 3 Requirement List Example Use information from House of Quality as an starting point for creating the requirement list. Need to identify requirements for the product that are basic and necessary but are not specified by the customers.

Example House of Quality Design a device to toast breads and other similar types of food