Product Specifications

Slides:



Advertisements
Similar presentations
Ken YoussefiMechanical Engr. Dept., UC Berkeley 1 Product Specifications.
Advertisements

Chapter 4 Product and Service Design 1Saba Bahouth – UCO.
Product Design L5- Ch4: Product Specifications Dr. Husam Arman 1.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Writing Target and Final Specifications translating customer words… into … realizable engineering specifications.
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
Product Development. Major Topics The product portfolio of a company concretizes its mission A description of the product selection and development process.
Developing Products and Services
Chapter 5 Product Specifications. Learning Objectives How to translate subjective customer needs into precise target specs? How could the team resolve.
SUBJECT  Industrial facility design. GROUP MEMBERS H.Hammad Ali 11-IE-32 S.Hammad shah 11-IE-21 Hammad Hassan 11-IE-41.
Product Specifications
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.
Ways for Improvement of Validity of Qualifications PHARE TVET RO2006/ Training and Advice for Further Development of the TVET.
Engineering Design Introduction to Mechanical Engineering
Engineering Design George E. Dieter Mc Graw Hill.
1 CERTIFIED SOLIDWORKS ASSOCIATE (CSWA) EXAM Nov 26, 20119:00-12:00 Dec 3, :00-12:00 SEB1015 NOTES We’ll take registrations in November but you’ll.
An overview of multi-criteria analysis techniques The main role of the techniques is to deal with the difficulties that human decision-makers have been.
1 Lecture #1: PD - Ch 1. Introduction Ref: Product Design and Development by Karl T. Ulrich and Steven D. Eppinger, McGRAW-Hill
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Chapter 2 continued Quality Function Deployment. What is Quality Function Deployment (QFD)? QFD is a tool that translates customer requirements into the.
© G. A. Motter, 2006, 2008 & 2009 Illustrated by Examples Quality Function Deployment and Selection Matrices Customer Driven Product Development.
Quality Function Deployment. Example Needs Hierarchy.
Chapter 12 Translating Expectations to Specifications CEM 515: Project Quality Management Prof. Abdulaziz A. Bubshait King Fahd University of Petroleum.
Product Design Specification Lecture 5. 2 PDS in Design Process Recognition of Need Becoming Informed Problem Definition  Market analysis  Background.
Tata McGraw CHAPTER 4 Product and Service Design.
Lecture 2. An Overview of Engineering Design JANUARY 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
Design Process Design process is a collection of procedures and habits that help teams design better products.
Chapter 4 Assessment.
Classroom Assessments Checklists, Rating Scales, and Rubrics
An Overview of Engineering Design
Design and modeling 10 step design process
Ten-Stage Design Process
ECE362 Principles of Design
For Products and Services
Fundamentals of Information Systems, Sixth Edition
Writing Product Requirements
Ten-Stage Design Process
Classroom Assessments Checklists, Rating Scales, and Rubrics
2 Selecting a Healthcare Information System.
Software Requirements analysis & specifications
“The best design is the simplest one that works.” Albert Einstein
OVERVIEW Debate in engineering design community: Should design be taught as: Establishing a foundation of theory? or Engaging students in loosely supervised.
Chapter 2 The Process of Design.
Product Specifications
Applicable Areas Business Logic Case Presentation Cost Design
An Overview of Engineering Design
Engineering Design George E. Dieter Mc Graw Hill.
DEFINING REQUIREMENTS (REV. 05/22/2008)
MINGGU KE 9: PROSES DESAIN PRODUK BARU
PRODUCT SPECIFICATIONS chapter FOUR
Objectives 1. A definition of planning and an understanding of the purposes of planning 2. Insights into how the major steps of the planning process are.
Design Analysis Higher Product Design.
Project Management Process Groups
Performance Management
Writing Product Requirements
Chapter 11 Selecting the Best Alternative Design Strategy
Goal-Driven Continuous Risk Management
F o u n d a t i o n s o f pl a n n i n g
Chapter 9: Setting the list or quoted price
Writing Target and Final Specifications
CHAPTER 14 SETTING A DIRECTION FOR INFORMATION RESOURCES
MGT601 SME MANAGEMENT.
CHAPTER 14 SETTING A DIRECTION FOR INFORMATION RESOURCES
Goal-Driven Software Measurement
An Overview of Engineering Design
Time Scheduling and Project management
Chapter 11 Selecting the Best Alternative Design Strategy
Modern Systems Analysis and Design Third Edition
Chapter 2: Development process and organizations
Presentation transcript:

Product Specifications Chapter 5 Product Specifications

What Are Specifications? Product specs spell out in precise, measurable detail what the product has to do. Product specifications tell the team how to address the customer needs. For example: customer need: “the suspension is easy to install” corresponding specification might be: “ the average time to assemble the fork to the frame is less than 75 seconds.”

Similar terms: Specifications Product requirements Engineering characteristics Technical specifications: to refer to key design variables of the product such as the oil viscosity or spring constant of the suspension system. A specification (singular) consists of a metric and a value.

What Are Specifications? For example, “average time to assemble” is a metric, while “less than 75 seconds” is the value of this metric. The product specifications (plural) are simply the set of the individual specifications.

When Are Specifications Established? Immediately after identifying the customer needs, the team sets target specifications. Target 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.

When Are Specifications Established? The team’s efforts may fail to meet some of these specifications and may exceed others, depending on the product concept the team eventually select. For this reason, the target specifications must be refined after a product concept has been selected.

When Are Specifications Established? Team revisits specs. while assessing actual technological constraints & expected production costs. To set the final specifications, the team makes trade-offs among different desirable characteristics of the product.

The Concept Development Process

Product Design Specifications PDS in Design Process Recognition of Need Becoming Informed Problem Definition Market analysis Background study Product Design Specifications 9

PDS It is a control document of what designers try to achieve It acts like a design checklist and applicable to all design applications It is dynamic rather than static – can be improved, changed to suit design requirements It defines the constraints/boundary of the design. 10

Elements of PDS 11

PDS Performance – target, attainable values Environment – effects on product during manufacture  use, effects on environment Life in service – 7 days/week, 24hrs/day, @ X years Maintenance – maintenance philosophy, need for special tools, ease of maintenance Targeted production cost Competition – data from benchmarking, IP, info search Shipping – delivery method, lifting capability Packing – cost & method of packing Quantity – will affect other costs such as tooling, processes Manufacturing facility – in-house or vendor, support system, machinery 12

PDS (cont’d) Size – affects user, cost, shipping & handling Weight - affects user, cost, shipping & handling Aesthetics – user perception or acceptence Materials Product Life Span – life in production line Standard and Regulations – government, BS/ISO/MS/DIN Ergonomics Customer – target customer Quality & Reliability – subjected to standards (BS, ISO, etc) Shelf Life – storage risks and problems Processes – processes involved, in-house facility/vendor Time-scales – period to complete the design 13

PDS (cont’d) Time-scales – time needed to complete the development Testing – methods, facility, requirements/standards Safety – safety requirements Company Constraints – house, facility, cost Market Constraints – local conditions, full market knowledge Patents, literature & Product data – clash & IP laws Political & Social Implications – social unrest, rejection Legal – product liability legislation (product defects, defects of manufacture, defects of design, etc) Installation – assembly consideration (stand alone, subsystem) Documentation – manual, user instructions, etc Disposal – environment. 14

Writing PDS Document It is a control document Should be clearly written Use sharp and definitive statements, NOT in essay form Try to quantify parameters or estimate a figure Vary your starting point Date and put your issue number Clearly document amendments 15

Four Steps of the Process of Establishing The Target Specifications 1. Prepare the list of metrics, using the needs-metrics matrix, if necessary. 2. Collect the competitive benchmarking information. 3. Set ideal and marginally acceptable target values for each metric. 4. Reflect on the results and the process.

Step 1. Prepare the List of Metrics Most useful metrics are those that reflect as directly as possible the degree to which the product satisfies the customer needs Ideally, there is one and only one metric for each need. In practice, this is frequently not possible.

Step 1. Prepare the List of Metrics A simple needs-metrics matrix represents the relationship between needs and metrics. The rows of the matrix correspond to the customer needs, and the columns of the matrix correspond to the metrics. This matrix is a key element of the House of Quality, a graphical technique used in Quality Function Deployment, or QFD

Guidelines of Metrics Metrics should be complete. Ideally each customer need would correspond to a single metric,and the value of that metric would correlate perfectly with satisfaction of that need. Metrics should include the popular criteria for comparisons in the marketplace. For example, popular science, customer reports

Guidelines of Metrics Metrics should be dependent, not independent, variables. Variant of the what-not-how principle Specifications indicate what the product must do, but not how the specifications will be achieved. Designers use many types of variables in product development; some are dependent, such as the mass of the fork, and some are independent, such as the material used for the fork.

Use Dependent Metrics Example: Designers cannot control mass directly because it arises from other independent decisions the designers will make, such as, dimensions and materials choices. Metrics specify the overall performance of a product and should therefore be the dependent variables ( i.e., the performance measures or output variables)

Guideline of Metrics Metrics should be practical. Metrics will be directly observable or analyzable properties of the product that can be easily evaluated by the team. Some needs cannot easily be translated into quantifiable metrics. Team notes that the metric is subjective and would be evaluated by a panel of customers. ( “Subj.” )

List of Metrics for the Suspension

The Needs-Metrics Matrix

Competitive Benchmarking Chart Based on Metrics

Competitive Benchmarking Chart Based on Metrics

Step2: Collect the Competitive Benchmarking Information Information on competing products must be gathered to support product positioning decisions. Warning: Sometimes the data contained in competitors’ catalogs and supporting literature are not accurate. If possible, verify by independent testing or observation.

Step3: Set Ideal and Marginally Acceptable Target Values for Each Metric Two types of target values are useful: an ideal value and a marginally acceptable value. The ideal value is the best result the team could hope for. The marginally acceptable value is the value of the metric that would just barely make the product commercially viable.

Five ways to express the values of the metrics At least X At most X Between X and Y Exactly X A set of discrete values

At least X Establish targets for the lower bound on a metric, but higher is still better.

At most X Establish targets for the upper bound on a metric, with smaller values being better.

Between X and Y Establish both upper and lower bounds for the value of a metric.

Exactly X Establish a target of a particular value of a metric, with any deviation degrading performance.

A set of discrete values Some metrics will have values corresponding to several discrete choices. For example, the headset diameters are 1.000, 1.125, or 1.250 inches.

Competitive Benchmarking Chart

Step 4: Reflect on the Results and the Process The team may require some iteration to agree on the targets. Are members of the team “gaming”? For example, is the key marketing representative insisting that an aggressive value is required for a particular metric in the hopes that by setting a high goal.

Step 4: reflect on the Results and the Process Should the team consider offering multiple products or at least multiple options for the product in order to best match the particular needs of more than one market segment, or will one “ average” product suffice? Are any specifications missing? Do the specifications reflect the characteristics that will dictate commercial success?

The target Specifications

Setting the Final Specifications As the team finalizes the choice of a concept and prepares for subsequent design and development, the specifications are revisited. Finalizing the specifications is difficult - How to resolve trade-offs

Setting Final Specs: 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

Step 1: Develop Technical Models of the Product A technical model of the product is a tool for predicting the values of the metrics for a particular set of design decisions. Models  both analytical and physical approximations of the product. When physical models must be constructed, it is often useful to use DOE techniques to minimize the number of experiments required to explore the design space

Step 2: Develop a Cost Model of the Product Goal: to make sure that the product can be produced at the target cost. For most products, the first estimates of manufacturing costs are completed by drafting a bill of materials (BOM) and estimating a purchase price or fabrication cost for each part.

A Bill of Materials with Cost Estimates

A Competitive Map

Step 3: Refine the Specifications, making Trade-Offs where necessary One important tool for supporting this decision-making process is the competitive map. This map is a scatter plot of the competitive products along two dimensions selected from the set of metrics. Generally the team will prepare three or four such maps corresponding to a handful of critical metrics.

The Final Specifications

Step 4: Flow Down the Specifications as Appropriate For highly complex product consisting of multiple subsystems: to ensure that the subsystem specifications in fact reflect the overall product specifications. to ensure that certain specifications for different subsystems are equally difficult to meet (e.g. mass of engine & engine body)

Step 5: Reflect on the Results and the Process Is the product a winner? How much uncertainty is there in the technical and cost models? Is the concept chosen by the team best suited to the target market, or could it be best applied in another market? Should the firm initiate a formal effort to develop better technical models of some aspect of the product’s performance for future use?