Lecture 5 Product specifications.

1. Lecture 5 Product specifications. ECEn 490 –Winter 2014

2. How did you do on the Homework Assignment • Go through the process describe in the lecture (and text) with your team. Email me with the following, • Description of the customer for your project, • The questions you would like to ask this customer, • The customer responses that you think the customer would give, and, • The interpreted customer needs that you determined. • The method of prioritizing the needs that you used. ECEn 490 –Winter 2014

3. Identifying customer needs. • Homework assignment • What were some of the challenges in coming up with customer needs? How did some of you arrive at a definition of your customer? • What were some of the 5 top needs as identified by your process? • How will you use these needs in developing your product? ECEn 490 –Winter 2014

4. Plan • Downstream • Development • Test • Product • Concept • Set • Final • Specs • Perform Economic Analysis • Benchmark Competitive Products • Build and Test Models and Prototypes • Concept Development Phase • Phase 1 • Phase 2 • Phase 3 • Phase 4 • Phase 5 • Concept • Development • System-Level • Design • Detail • Design • Testing and • Refinement • Production • Ramp-up • Mission • Statement • Development • Plan • Establish • Target • Specs • Generate • Product • Concepts • Identify • Customer • Needs • Select a • Product • Concept • Concept Development • Exhibit 3 Chapter 5 Ulrich & Eppinger ECEn 490 –Winter 2014

5. What • yes • Successful • Product • Metrics/ • Values • IF • no • Needs and Specifications • Customer Needs describe What the end product or service does for the user. They are expressed in the “language of the customer”. The “product__________” • Product Specifications allow quantification of the customer needs. Specifications are expressed in the language of engineering; metricsand values. • The Product Metrics describe the measures used to determine IF the product meets the required needs. • The Value is the actual numeric specification that the designers use to determine when the product meets the customer requirements. ECEn 490 –Winter 2014 • 5

6. Example: Specialized mountain bike design. • Customer need: The Suspension enables high-speed descents on bumpy roads. • Product Metrics: • Attenuation from dropout to handlebar at 10 Hz. • Maximum value from the Monster (suspension test by Mountain Bike Magazine.) • Minimum descent time on test track. • Note: the metric does not yet have an actual value assigned at this point. Why not? • Product Specifications usually require a preliminary product definition. ECEn 490 –Winter 2014

7. Importance of Clear Specifications • Product Specifications are the “blue prints” of a project. They will guide the project throughout the development. • Developing product specifications is a two step process. • Step 1 establish target specs to help channel the thinking during the product concept generation process. (Usually requires making assumptions as to what the final product configuration will be.) • Step 2 is the refinement of the specifications once the team has picked a product concept and is ready to go into system level design. Completed after concept selection. ECEn 490 –Winter 2014

8. Process for Establishing Target Specifications Prepare the list of Metrics based on your customer needs or expected outcomes. Establish what “best in class” products would require. Collect competitive benchmarks if available. Decide where your solution will be “best in Class”. How are you going to win? Set the target values for each metric Reflect on the results ECEn 490 –Winter 2014

9. The process of developing product specifications begins with your completed matrix of interpreted customer needs. Again note that there are no values. ECEn 490 –Winter 2014

10. Product Specs are based on Customer Needs • The Customer expresses the need in terms of What the product must do. • The robot can quickly change alignment without forward motion. • The Product Specification sets metrics and values that allow quantification of the user need. • The Robot can rotate 360 degrees in 2 secs without forward motion . ECEn 490 –Winter 2014

11. A Product Spec for each Need Prioritize the Needs. It is important to identify the critical factors for success and make sure you have a way of quantifying these factors. Develop a measure and value for each need Some needs may have more than one specification. ECEn 490 –Winter 2014

12. Example of a customer needs table ECEn 490 –Winter 2014

13. Example of a Product Specification table ECEn 490 –Winter 2014

14. Types of Metrics Some metrics are dependent, some are independent variables Independent metrics can be set by the designer, “number of motors”, “amount of battery time required” Dependent metrics are the result of other design decisions, “mass of robot”, “size of the battery” - It is important to identify the dependent variables to insure the other design choices don’t compromise the customer needs. • Examples for your project? ECEn 490 –Winter 2014

15. Values of Metrics At least X-- set a minimum amount, At most X -- set a maximum, Between X and Y -- set a range, 4. Exactly X -- set a fixed value, 5. Discrete values – parts are only available in discrete increments, Are all needs quantifiable? ECEn 490 –Winter 2014

16. What department in most companies is most concerned with Product Specifications? • The QA department. • What does QA stand for? • Quality Assurance • What does a QA department do? • Works with design engineers to develop comprehensive specifications for all critical customer requirements. • Develops test procedures to allow designers to test their designs against the specifications. • Test products and processes to ensure the end product complies with those design specifications. ECEn 490 –Winter 2014

17. Tools for transforming Needs into Specifications Needs-Metrics Tables Quality Function Deployment- QFD Competitive Benchmarking • Analyze Data • vs. Requirements • measure • requirements • Correlate Requirements • with Measures ECEn 490 –Winter 2014

18. Needs-Metrics Tables ECEn 490 –Winter 2014

19. Quality Function Deployment- QFD, • or a Needs-Metrics Matrix • Metrics • Needs ECEn 490 –Winter 2014

20. Competitive Benchmarking • Evaluate the competition ECEn 490 –Winter 2014

21. Homework assignment Complete the Preliminary Functional Specifications Document (PFSD) for your senior project. You can use the template illustrated in Example FSD on the website, or a similar format to capture the relationship between your customer needs and the product specs you will need meet in your design. Have the document available on your management site and emailed to Prof. Clifford by next Tuesday, Jan 28th. Read Chapter 6 Concept Generation or the class notes on the website. ECEn 490 –Winter 2014

22. The Four sections of the FSD • Project Description and background: What is the project, and what is expected to be accomplished. • Project Requirements: Who is the customer, and what are the interpreted needs and requirements including their relative importance. (customer needs table) • Product Specifications: The measurable engineering characteristics (metrics) and target values for the product. • Linking of the Project Requirements and Product Specifications: The analysis of the specifications to insure that critical program and customer requirements are being met. (table showing needs, specs, and values) ECEn 490 –Winter 2014

23. In-Class Exercise Get into your teams take the Interpreted Customer Needs from your homework assignment develop 3-5 target product specifications for the product (both the metric and value) Remember, you haven’t picked a final product concept yet– try keep the specifications in terms of “what” not “how” be prepared to present your ideas to the class. ECEn 490 –Winter 2014