PRODUCT SPECIFICATIONS

1
PRODUCT SPECIFICATIONS

• Sources
• Cooper, Product Leadership - Creating and
  Launching Superior New Products, Perseus, 2000.
• Ulrich and Eppinger, Product Design and
  Development, 2nd ed., Irwin McGraw-Hill, 2000.
• Pugh, Total Design - Integrated Methods for
  Successful Product Engineering, Addison Wesley,
  1990.
• Pugh (with Clausing and Andrade), Creating
  Innovative Products Using Total Design, Addison
  Wesley, 1996

2
Product Specifications

• Cooper
• Part of the product definition
• Product features, attributes, requirements
• Ulrich and Eppinger
• What the product has to do, not how
• Consists of a metric and a value

3
Coopers Stage 2 Business Case

• What is the product and who will it be sold to?
  (the product definition)
• Target market
• Product concept and benefits delivered
• Positioning strategy
• Products features, attributes, requirements

4
Ulrich and EppingersProduct Development Process
Product Development Process
After Ulrich and Eppinger, Exhibit 2-2
5
Concept Development Phase (U E)
After Ulrich and Eppinger, Exhibit 2-3
6
The Product Specs Process (UE)

• Set Target Specifications
• Based on customer needs and benchmarks
• Develop metrics for each need
• Set ideal and acceptable values
• Refine Specifications
• Based on selected concept and feasibility testing
• Technical modeling
• Trade-offs are critical
• Reflect on the Results and the Process
• Critical for ongoing improvement

7
Product Specification Steps
Gather and filter problem information
Convert requirements into specifications
Establish the customers requirements
8
Requirements vs. Specifications

• Requirements
• Define what the customer wants
• May be subjective, qualitative, difficult to
  measure
• Specifications
• Define what will actually be delivered
• Respond to customers needs, organizational
  capabilities, technology and resource
  availability
• Always Measurable

9
Specifications.....

• Precisely define the end product or result
• Quantify the customers needs and specify the
  degree to which the needs will be met
• Should not limit how the customers needs are to
  be addressed
• Consist of
• Metric - Characteristic being measured
• Value or range of values
• Unit of measurement

10
Specifications are the yardstick for determining
project success
11
Rules for Creating Specifications

• 1. Focus on the end RESULTS.
• 2. Do not build your ideas of how to achieve the
  results into the specifications.
• 3. Make sure that each requirement is covered.
• 4. Make sure that the customers interests are
  protected.
• 5. Make sure that your interests are protected.

12
Product Design Specifications

• Guidelines for developing the Product Design
  Specification (PDS)
• (see Pughs Product Design Specifications)

13
P a u s e

14
Using Customer Input

• Quality function deployment (QFD)
• Customer input and the House of Quality

15
Quality Function Deployment(QFD)House of
Quality

16
Quality Function Deployment

• A technique for identifying customer requirements
  and matching them with engineering design and
  performance parameters
• From the Japanese phrase meaning the strategic
  deployment throughout all aspects of a product of
  appropriate characteristics according to customer
  demands

17
The general arrangement of a QFD table consists
of the following 5 regions
1. Customer requirements 2. Engineering
requirements 3. Matrix of requirements
relations 4. Competitive benchmarks 5.
Engineering targets
Engineering Metrics (Region 2)
Matrix of Requirements Relations (Region 3)
Customer Requirements (Region 1)
Competitive Benchmarks (Region 4)
Engineering Targets (Region 5)
18
Contents of the Regions

• Customer Requirements (1)
• features or characteristics that the customer
  indicates as relevant
• must be in customers own words, not filtered by
  marketing or engineering
• Engineering Metrics (2)
• generated by engineering staff
• quantifiable aspects of system that can
  contribute to satisfying customer requirements
• mixture of performance parameters and design
  parameters

19
Contents of the Regions

• Matrix of Requirements Relations (3)
• matrixwith rows of customer requirements and
  columns of engineering metrics
• each relationship marked with an x
• Benchmarking (4)
• opportunity to explicitly compare your design to
  that of a competitors
• mark the customer requirements that are met with
  an o.

20
Contents of the Regions

• Engineering Targets (5)
• list numerical values established for each
  engineering metric (2), along with units
• target may be the value that the requirement must
  achieve in order to compete with the benchmarked
  products

21
Variations to QFD Tables

• A region can be inserted next to (1) for
  weighting the relative importance the customer
  places on his/her requirements
• A roof can be put over (2) and used to show
  relationships between metrics ( or -)
• Numerical values indicating relative weights may
  replace the xs and os in the matrix

22
QFD House of Quality
23
Example

• Goal
• Design an improved automobile bumper
• Objectives
• Design an inexpensive front bumper to withstand a
  5 mph head-on collision (concrete wall)
• Bumper must be easily recyclable
• Constraints
• must be installed 18 up from ground
• weight lt 50 lb
• must attach to mounting brackets on targeted
  automobile frames

24
House of Quality for Automobile Bumper
25
Product Specifications ExampleMountain Bike
Suspension Fork
26
Start with the Customer Needs
27
Establish Metrics and Units
28
Link Metrics to Needs
29
Benchmark on Customer Needs
30
Benchmark on Metrics
31
Assign Marginal and Ideal Values
32
Set Final Specifications
33
ENHANCED QUALITY FUNCTION DEPLOYMENT

• (EQFD)

34
Notes HOQ House of Quality TSA Total System
Architecture SS Subsystem PP Piece-part
35
(No Transcript)
36
Notes HOQ House of Quality TSA Total System
Architecture SS Subsystem PP Piece-part
37
(No Transcript)
38
(No Transcript)
39
Subsystem Design Decisions Piece-Part
Expectations
Retard friction coefficient
Jam clearance strategy
Enhanced stack force
Retard brake torque
TAR surface speed
Normal stack force
UMC breackdown
TAR action time
Retard radius
Trigger time
Subsystem Expectations
A
B
C
D
E
F
G
H
I
J
6
1
Misfeed rate
lt50/10
O
O
O
6
2
Multifeed rate
lt50/10
O
O
O
O
O

O
6
3
Jam rate
lt30/10
O
4
Copy rate
702/-0CPM
O
5
Jam clearance time
lt20 sec
O
6
6
Paper damage rate
lt40/10
O
7
UMC
lt250
O
8
Paper speed
11.7

3 ips
O
9
Delivery time
141

10 msec
O
0.005 in
0.3 ips
0.25
4 in-oz


100 msec
120 msec

Ref. Y

Ref. Z
0.880
0.3 lb
0.7 lb
1.50
11.7
40
Subsystem Design Matrix
Source Pugh,
Creating Innovative Products Using Total Design
, Addison-Wesley, 1996
40
(No Transcript)
41
(No Transcript)
42
The Product Specs Process Summary

• Set Target Specifications
• Based on customer needs and benchmarks
• Develop metrics for each need
• Set ideal and acceptable values
• Refine Specifications
• Based on selected concept and feasibility testing
• Technical modeling
• Trade-offs are critical
• Reflect on the Results and the Process
• Critical for ongoing improvement

43
The End