Quality Function Deployment (QFD) : BITS Pilani
Quality Function Deployment (QFD) : BITS Pilani
(Qfd)
BITS Pilani
Pilani Campus
Agenda
Introduction
QFD Benefits
House of Quality (HOQ)
QFD Steps to build HOQ
Conclusion
Introduction
Quality Function Deployment (QFD) is an approach to
design introduced in Japan in 1966 by Yoji Akao.
Definition: QFD is a very systematic and organized
approach of taking customer needs and demands in the
consideration when designing a new products and
services or when improving existing products and
services.
QFD Benefits
Customer driven
Reduces implementation time
Promotes teamwork
Provides documentation
WHO
Who
Vs.
What
Wha
t
How
Now
What vs.
How
Now
Vs.
What
How much
BITS Pilani, Pilani Campus
QFD Steps
Step 1: Identify the customers: determine exactly WHO
they are.
Customers can be
internal or external to the
company.
For many products, the
most important
customers are the
consumers, the people
who will buy the product
and tell other consumers
about its quality (or lack
thereof).
How
Vs.
How
How
WHO
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
QFD Steps
Step 2: Determine the customers requirements: WHAT do the
customers want?
How
Vs.
How
How
WHO
Who
Vs.
Wha
t
Wh
at
What vs.
How
No
w
No
w
Vs.
Wh
at
How much
QFD Steps
Step 3: Determine relative importance of the requirements:
WHO versus WHAT
Relative importance can be
evaluated by generating a
weighting factor for each
requirement.
Traditionally, the customers are
asked to rate each requirement on
a scale from 1 to 10.
A better method, the fixed sum
method, is to tell each customer
that they have 100 points to
distribute among the requirements.
How
Vs.
How
How
WHO
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
QFD Steps
Step 5: Generate engineering specifications: HOW will the
customers requirements be met?
Engineering specifications
are the restatement of the
design problem in terms
of parameters that can be
measured and have
target values.
Parameters are
developed in this step and
the target values for these
parameters are
developed in step 8.
How
Vs.
How
How
WHO
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
QFD Steps
Step 6: Relate customers requirements to engineering
specifications: HOW to measure WHAT?
This is the central part of HOQ.
How
Vs.
How
How
WHO
Strong relationship
Medium relationship
Weak relationship
Blank = no relationship
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
QFD Steps
Step 7: Set engineering targets: HOW MUCH is good enough?
Target values are used to
evaluate the products ability
to satisfy customers
requirements.
Two actions:
1. To ascertain how the
competitors (step 4)
meets the engineering
specifications, and
2. To establish the targets
for the new product.
How
Vs.
How
How
WHO
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
QFD Steps
Step 8: Identify relationships between engineering requirements:
How are the HOWs dependent on each other?
Engineering specifications may
be dependent on each other. It
is best to realize these
dependences early in the design
process.
Negative
(-1)
Strong negative (-3)
Strong positive
(9)
Positive
(3)
How
Vs.
How
How
WHO
Who
Vs.
What
Wh
at
What vs.
How
Now
Now
Vs.
Wha
t
How much
Customer
Requiremen
ts
Competitive
assessment
Relations
hip matrix
Importance
rating
Engineering
Characteristics
Target values
Conclusion
The QFD technique ensures that the problem is well
understood.
The HOQ automatically documents and records the
evolution of the product design.
The HOQ is an excellent communication tool for the
design team.
The QFD technique can be applied at any of the design
phases.