Product Specifications.pptx

1. Product Specifications

2. Product Development Process

4. Concept Development Process
Perform Economic Analysis
Benchmark Competitive Products
Build and Test Models and Prototypes
Identify
Customer
Needs
Establish
Target
Specifications
Generate
Product
Concepts
Select
Product
Concept(s)
Set
Final
Specifications
Plan
Downstream
Development
Mission
Statement Test
Product
Concept(s)
Development
Plan
Target Specs
Based on customer needs
and benchmarking
Final Specs
Based on selected concept,
feasibility, models, testing,
and trade-offs

8. Product Specifications Example:
Mountain Bike Suspension Fork

9. Start with the Customer Needs

10. Start with the Customer Needs

11. Establish Metrics and Units
1.Prepare the List of Metrics

12. Link Metrics to Needs

13. Benchmark on Metrics
2.Collect Competitive Benchmarking Information

14. Benchmark on Customer Needs
2.Collect Competitive Benchmarking Information

15. 3. Set ideal and Marginally Accepted Target Values
Assign Marginal and Ideal Values

16. Set Final Specifications
3. Reflect on the results and the process

17. The Product Specs Process
1. Set Target Specifications
– Based on customer needs and benchmarks
– Develop metrics for each need
– Set ideal and acceptable values
2. Refine Specifications
– Based on selected concept and feasibility testing
– Technical and economic modeling
– Trade-offs are critical
3. Reflect on the Results and the Process
– Critical for ongoing improvement

18. 06/18/18 9
Procedure for establishing
target specifications
1. Identify a list of metrics and measurement
units that sufficiently address the needs
2. Collect the competitive benchmarking
information
3. Set ideal and marginally acceptable target
values for each metric (using at least, at
most, between, exactly, etc.)
4. Reflect on the results and the process

19. 1. Develop technical models to assess technical feasibility. The
input is design variable and the output is a measurement using
a metric.
2. Develop a cost model of the product.
3. Refine the specifications, making tradeoffs, where necessary to
form a competitive map.
4. “Flow down” the final overall specs to specs for each
subsystem (component and part).
5. Reflect on the results to see
❖ Whether the product is a winner, and/or
❖ How much uncertainty there is in the technical and cost model, or
❖ Whether there is a need to develop a better technical model.
06/18/18 10
Process for setting the final
specifications

21. Thank You

22. What is product development ?
➢Product Development is the set of activities ,beginning with the
perception of a market opportunity and ending in the production , sales
and delivery of a product.
➢The goal of the subject is to present a clear and detailed way a set of
product development methods while focusing together the marketing,
Design and manufacturing functions of the organization.

26. Benchmark on Customer Needs

27. Product Specifications
As of now faced several challenges:
 How could the relatively subjective customer needs be translated into precise targets
for the remaining development effort?
 How could the team and its senior management agree on what would constitute
success or failure of the resulting product design?
 How could the team develop confidence that its intended product would garner a
substantial share of the suspension fork market?
 How could the team resolve the inevitable trade-offs among product characteristics like
cost and weight?
Definition : A specification (singular) consists of a metric and a value.
 The development teams usually establish a set of specifications, which spell out in
precise, measurable detail what the product has to do.
 Product specifications do not tell the team how to address the customer needs, but they
do represent an unambiguous agreement on what the team will attempt to achieve in
order to satisfy the customer needs.
 We intend the term product specifications to mean the precise description of what
the product has to do.
 Some firms use the terms “product requirements” or “engineering characteristics” in this
way.
 Other firms use “specifications” or “technical specifications” to refer to key design
variables of the product such as the oil viscosity or spring constant of the suspension
system.

28. When Are Specifications Established?
 Immediately after identifying the customer needs, the team sets target
specifications.
 These specifications represent the hopes and aspirations of the team, but they are
established before the team knows what constraints the product technology will
place on what can be achieved.
 The team’s efforts may fail to meet some of these specifications and may exceed
others, depending on the product concept the team eventually selects.
 To set the final specifications, the team must frequently make hard trade-offs
among different desirable characteristics of the product.
 This chapter presents two methods: the first is for establishing the target
specifications and the second is for setting the final specifications after the product
concept has been selected.

29. Establishing Target Specifications
 The target specifications are established after the customer needs have been
identified but before product concepts have been generated and the most
promising one(s) selected.
 An arbitrary setting of the specifications may not be technically feasible.
 They are the goals of the development team, describing a product that the team
believes would succeed in the marketplace.
Later these specifications will be refined based on the limitations of the product
concept actually selected.
The process of establishing the target specifications contains four steps:
1. Prepare the list of metrics.
2. Collect competitive benchmarking information.
3. Set ideal and marginally acceptable target values.
4. Reflect on the results and the process.

30. Setting the Final Specifications
 As the team finalizes the choice of a concept and prepares for subsequent
design and development, the specifications are revisited.
 Specifications that originally were only targets expressed as broad ranges of
values are now refined and made more precise.
 Finalizing the specifications is difficult because of trade-offs—inverse
relationships between two specifications that are inherent in the selected
product concept.
 Trade-offs frequently occur between different technical performance metrics
and almost always occur between technical performance metrics and cost.
Here, we propose a five-step process:
1. Develop technical models of the product.
2. Develop a cost model of the product.
3. Refine the specifications, making trade-offs where necessary.
4. Flow down the specifications as appropriate.
5. Reflect on the results and the process.