chapter 12 jan mohrbacher, connie dillard & anas alrawi

52
Quality Function Deployment Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Post on 19-Dec-2015

224 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Quality Function Deployment

Chapter 12

Jan Mohrbacher, Connie Dillard& Anas Alrawi

Page 2: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

At the conclusion of this class – You will have a thorough understanding of:

1. What is QFD?2. Why it is important?3. When it is used?4. How it is used?5. Understand the function of a QFD Team6. Realize the Benefits of QFD7. The Voice of The Customer8. Organization of information9. The House of Quality10. QFD Process

Quality Function Deployment - QFD

Page 3: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

History of QFD

Yoji Akao, a Japanese planning specialist, conceptualized QFD in the 1960’s

Dr. Shigeru Mizuno, Professor Emeritus of the Tokyo Institute of Technology is credited with initiated the quality function deployment system

Page 4: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Statistical Quality Control, SQC, was the central quality control activity after WWII.

SQC is an effective method of monitoring process using control charts.

SQC became Total Quality Control, TQC.

QFD was derived from TQC.

History of QFD

Page 5: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

First Application of QFD 1966, Bridgestone Tire Corp first used a process

assurance table.

1972, the process assurance table was retooled by Akao to include QFD process.

1972, Kobe Shipyards (of Mitsubishi Heavy Industry) began a QFD Oil Tanker project.

1978, Kobe Shipyards published their quality chart for the tanker.

Page 6: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD in North America

QFD spread rapidly in North America during the 1980’s

The Automobile industry and Manufacturing began heavy use of QFD at this time.

QFD symposiums (North American, Japanese, European, International) were set up to explore research relating to QFD techniques.

The QFD institute was formed in 1994.

Page 7: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Quality Function Deployment is a comprehensive quality design method that:

Seeks out spoken and unspoken customer needs from fuzzy Voice of the Customer verbatim;

Uncovers "positive" quality that wows the customer;

Translates these into designs characteristics and deliverable actions; and

Builds and delivers a quality product or service by focusing the various business functions toward achieving a common goal—customer satisfaction.

What is Quality Function Deployment?

Page 8: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

What is QFD?

Quality Function Deployment, QFD, is a quality technique which evaluates the ideas of key stakeholders to produce a product which better addresses the customers needs.

Customer requirements are gathered into a visual document which is evaluated and remodeled during construction so the important requirements stand out as the end result.

Page 9: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

The link between Customer Design Engineer Competitors Manufacturing

Provide Insight Into the whole design & manufacturing operation From concept to manufacture (cradle to the grave) Can improve efficiency

What is QFD?

Page 10: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Creative Definitions of QFD

Page 11: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Key Thought

Throughout

Quality Function Deployment is a Valuable Decision Support Tool, But

it is Not a Decision Maker

Page 12: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

WHAT DOES QFD DO?

Better Designs in Half the Time!

CUSTOMERCONCEPT

Benefits

“Traditional Timeline”

Plan Design Redesign Manufacture

Plan Design Redesign Manufacture

QFD is a Productivity Enhancer

Page 13: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

The QFD Paradigm

QFD provides the opportunity to make sure you have a good product before you try to design and implement it.

It is about planning and problem prevention, not problem solving .

QFD provides a systematic approach to identify which requirements are a priority for whom, when to implement them, and why.

Page 14: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD is very powerful because it incorporates the voice of customer in the design

Resulting in : A better product design A satisfied customer Insight into the design/manufacture

operation Improved problem solving and efficiency

in production

Why is it important?

Page 15: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Ask these important questions

◦Why do QFD?◦What is the goal?◦What should its make-up be?◦Is QFD the right tool ?◦Is this the right time?◦Is this the right place to implement?◦What is success?◦Who all should be involved?

When is it used?

Page 16: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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 putting out fires.

Page 17: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD Team

1. Its function in deployment2. Two Types of Teams

New product designImproving an existing design

3. Cross functional Marketing, design, quality, finance and

production

QFD Team

Page 18: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Comprehensive QFD involves

Four phases:

How to use it ?

Page 19: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Quality Function Deployment’sHouse of Quality

CustomerPerceptions

Relationshipsbetween

Customer Needsand

Design Attributes

Imp

ort

ance

Ran

kin

gs

CustomerNeeds

DesignAttributes

Costs/Feasibility

Engineering Measures

CorrelationMatrix

1The House

of Quality

Establishes the Flowdown Relates WHAT'S & HOW'S Ranks The Importance

2

3

6

54

7

8

Page 20: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Two Types of Elements in Each HouseTwo Types of Elements in Each House

Key Elements Informational

Elements

The

Hou

se o

f Qua

lity

Page 21: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD Flowdown

Customer Wants

Technical Requirements

Part Characteristics

Manufacturing Process

Production Requirements

ManufacturingEnvironment

ManufacturingEnvironment

Customer Wants

Product Functionality

System Characteristics

Design Alternatives

SoftwareEnvironment

SoftwareEnvironment

Customer Wants

Service Requirements

Service Processes

Process Controls

ServiceEnvironment

ServiceEnvironment

Flowdown Relates The Houses To Each OtherFlowdown Relates The Houses To Each Other

Le

vels

Of

Gra

nula

rity

Le

vels

Of

Gra

nula

rity

Page 22: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Building the House of Quality

1. Identify Customer Attributes

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.

Page 23: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 24: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Types of Customer Information and How to Collect it

Lagging Leading

Solicited

Quantitative

Structured

Unsolicited

Qualitative

Random

Trade visitsCustomer visitsConsultants

Sales forceTraining programsConventionsTrade journalsTrade showsVendorSupplierAcademicEmployees

Focus groups

Complaint reportsOrganization standardsGovernment regulationsLawsuits

Hot linesSurveysCustomer testsTrade trialsPrefered costumersOM testingProduct purchase surveyCustomer audits

Page 25: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Key

Ele

men

ts -

“W

hat’s

Voice of the CustomerVoice of the Customer

What Does The Customer Want Customer Needs CTQs Ys

What’sWhat’s

Page 26: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Key

Ele

men

ts:

C

usto

mer

Req

uire

men

ts

Voice of the CustomerVoice of the Customer

How Important the What’s are TO THE CUSTOMER

Customer Ranking of their Needs

Customer

Importa

nce

Customer

Importa

nce

Page 27: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 28: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Key

Ele

men

ts -

“How

’s”

Satisfing Customer NeedsSatisfing Customer Needs

How Do You Satisfy the Customer What’s Product Requirements Translation For Action X’s

How’sHow’s

WHAT'S HOW'SWhat’sWhat’s

Page 29: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Information – C

orrelation Matrix

Conflict ResolutionConflict Resolution

Impact Of The How’s On Each Other

Strong PositivePositiveNegativeStrong Negative

Correlation MatrixCorrelation Matrix

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

5534241

H

H

H

H

L

M

M

M

MM

M L

L L

L

LH

OW

1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

57 41 48 13 50 6 21

3 lb

s

12

in.

3 m

ils

40

psi

3 8 a

tm

1 m

m

65

45

21

36

8

52

4

Page 30: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 31: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Key

Ele

men

ts: R

elat

ions

hip

Untangling The WebUntangling The Web

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)

Relationships

Relationships

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

5534241

H

H

H

H

L

M

M

M

MM

M L

L L

L

L

Page 32: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 33: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 34: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Info

rmat

ion:

How

Muc

h

Consistent ComparisonConsistent Comparison

Target Values for the How’s

Note the Units

How MuchHow Much3

lbs

12

in.

3 m

ils

40

psi

3 8 a

tm

1 m

m

H

H

H

H

L

M

M

M

MM

M L

L L

L

L

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

57 41 48 13 50 6 21

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

5534241

65

45

21

36

8

52

4

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

Page 35: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Info

rmat

ion:

Tar

get D

irect

ion

The Best DirectionThe Best Direction

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

Target Direction

Target Direction

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

5534241

H

H

H

H

L

M

M

M

MM

M L

L L

L

L

57 41 48 13 50 6 21

65

45

21

36

8

52

4

Information On The HOW'S More Is Better Less Is Better Specific Amount

Page 36: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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.

Page 37: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

36

45

36

45

1

6

15

M

99

12 4

5 5

3

2

57 41 48 13 50 6 21

Key

Ele

men

ts: T

echn

ical

Impo

rtan

ce

Ranking The HOW'SRanking The HOW'S

Which How’s are Key Where Should The Focus Lie “CI” = “Customer Importance” “Strength” is measured on a 9, 3, 1,

0 Scale

Technical Importa

nce

Technical Importa

nce

TI = Scolumn(CI *Strength)

CINeed 1Need 2Need 3Need 4Need 5Need 6Need 7

534241

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

Page 38: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

H

H

H

H

L

M

M

M

MM

M L

L L

L

L

Key

Ele

men

ts: C

ompl

eten

ess

Have We Captured the HOW'SHave We Captured the HOW'S

Are All The How’s Captured Is A What Really A How

Completeness Criteria

Completeness Criteria

CC = Srow

(CI *Strength)

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

534241

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

57 41 48 13 50 6 21

Page 39: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Using the House of QualityThe 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.

Page 40: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Cu

sto

me

rA

ttrib

ute

sDesign Attributes1

2

3

4

De

sig

nA

ttrib

ute

sComponent Attributes

Co

mp

one

nt

Attr

ibut

es

Process Operations

Pro

cess

Op

era

tions

Quality Control Plan

The How’s at One Level Become the What’s at the Next Level

The How’s at One Level Become the What’s at the Next Level

Page 41: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Voice of the customer (VOC)

“The efforts to investigate and analyze the customer. With

QFD, VOC data is reduce into a set of critical customer needs

using techniques such as affinity, diagrams, function analysis,

etc, defined and documented in customer needs data

dictionary, and prioritized. This VOC effort is also the

opportunity to recognize unfulfilled needs that can be

provided at minimum, competitive advantage and potentially,

a break-through product or true value innovation”

The voice of the customer

Page 42: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

The Cascading Voice of the CustomerNOTES:

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

The Four Houses of Quality

WHA

TS

Critical to QualityCharacteristics

(CTQs)

Key ManufacturingProcesses

Key Process Variables

X

Y

Page 43: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

10 Minute Break

Page 44: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD Building a House of Quality

Class Activity:

Building a House of Quality

Page 45: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Improves customer satisfaction

Reduces implementation time

Promotes team work

Provides documentation

QFD – Benefits of it?

Page 46: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD - BenefitsImproves customer

satisfaction

Reduces implementati

on time

Promotes teamwork

Providesdocumentati

on

•Creates focus on customer requirements•Uses competitive information effectively•Prioritizes resources•Identifies items that can be acted upon•Structures resident experience/information

•Decreases midstream design changes•Limits post introduction problems•Avoids future development redundancies•Identifies future application opportunities•Surfaces missing assumptions

•Based on consensus•Creates communication at interfaces•Identifies actions at interfaces•Creates global view out of details

•Documents rational for design•Is easy to assimilate•Adds structure to the information•Adapts to changes (living document)•Provides framework for sensitivity analysis

Page 47: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

QFD On EverythingSet the “Right” GranularityDon’t Apply To Every Last Project

Inadequate Priorities Lack of Teamwork

Wrong ParticipantsLack of Team SkillsLack of Support or Commitment

Too Much “Chart Focus” “Hurry up and Get Done” Failure to Integrate and Implement QFDCom

mon

QF

D P

itfal

ls

Page 48: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

The “Static” QFD

Review Current Status At Least Quarterly Monthly on 1 Yr Project Weekly on Small Projects

Review Current Status At Least Quarterly Monthly on 1 Yr Project Weekly on Small Projects

Need 1Need 2Need 3Need 4Need 5Need 6Need 7

5534241 H

H

H

H

L

M

M

M

MM

M L

L L

L

L

HO

W 1

HO

W 2

HO

W 3

HO

W 4

HO

W 5

HO

W 6

HO

W 7

57 41 48 13 50 6 21

65

45

21

36

8

52

4

3 lb

s

12

in.

3 m

ils

40

psi

3 8 a

tm

1 m

m

654521368524

Page 49: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

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

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

Points to Remember

Page 50: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Questions?

Page 51: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

Thank You

Page 52: Chapter 12 Jan Mohrbacher, Connie Dillard & Anas Alrawi

References:

Besterfield, D. H., Besterfield-Michna, C., Besterfield, G. H., & Besterfield-Sacre, M. (2003). Total Quality Management. Upper Saddle River, NJ: Pearson Education.

Davis, G., Zannier, C., & Geras, A. (n.d.). QFD for Software Requirements Management. Retrieved March 15, 2009, from www.guydavis.ca/seng/seng613/group/qfd.ppt

Edgeman, R. (n.d.). Customer Needs: Kano, Garvin & Quality Function Deployment. Retrieved March 19, 2009, from uidaho: www.webpages.uidaho.edu/~redgeman/Generic%20Presentations/Customer-Needs___Kano-Garvin-&-QFD.ppt

Menks, D., Ahmed, A., & Fu, K. (2000, November 23). Quality Function Deployment. Retrieved March 18, 2009, from www.cs.ualberta.ca/~sorenson/cmput402/lectures/sqfd.ppt

Quality Function Deployment, QFD: Overview. (2008, June 7). Retrieved March 24, 2009, from thequalityportal: http://thequalityportal.com/q_know01.htm