Fall Homework Read Chapter 4, “Identifying Customer Needs” and/or read the lecture 4 notes. Team assignment; Develop the “Body of Facts” (all the information that you currently know about your project). What are the key assumptions that you are making at the beginning of the project?

Fall 2015 ECEn 490 Lecture #4 2 Team discussion Assignment Discuss within your team the following: 1.Who is the customer or a potential user?, 2.What are the key features that would make your product successful? 3.Describe the competition for your product. 4.What are the areas where you can differentiate your product from the competition. 5.How would you set a priority on the needs that are identified? Reading Assignment, Class notes for Lecture 5

ECEn 490 -Fall 2015 Product Specs 3 Lecture 5 Product specifications.

ECEn 490 -Fall 2015 Product Specs 4 Identifying customer needs. Homework assignment What were some of the challenges in coming up with customer/user needs? How did some of you arrive at a definition of your customer? Where are you going to differentiate your product? How will you use these needs in developing your product?

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

ECEn 490 -Fall 2015 Product Specs 6 Specify: To name or mention exactly and clearly. How do you make statements Exact and Clear??

ECEn 490 -Fall 2015 Product Specs 77 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 does (something)” Product Specifications allow quantification of the customer needs. Specifications are expressed in the language of engineering; metrics and 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. What Metrics/ Values IF yes no Successful Product

ECEn 490 -Fall 2015 Product Specs 8 Example: Specialized mountain bike design. Customer need: The Suspension enables high-speed descents on bumpy roads. Product Metrics: 1.Attenuation from dropout to handlebar at 10 Hz. 2.Maximum value from the Monster (suspension test by Mountain Bike Magazine.) 3.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 -Fall 2015 Product Specs 9 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 -Fall 2015 Product Specs 10 Process for Establishing Target Specifications 1.Prepare the list of Metrics based on your customer needs or expected outcomes. 2.Establish what “best in class” products would require. Collect competitive benchmarks if available. 3.Decide where your solution will be “best in Class”. How are you going to win? 4.Set the target values for each metric 5.Reflect on the results

ECEn 490 -Fall 2015 Product Specs 11 # Customer Need StatementsInterpretation of NeedsImp. 1Can win Robot can score more goals than opponent 4 2Can control the ball while moving Robot can maintain possession of the ball while moving 4 3Want a simple design Robot has simple design so as to facilitate functionality void of problems 4 4Can block shots Robot positions itself between its goal and the ball to prevent a goal 4 5 Robot is able to score from anywhere on the field Robot is able to shoot the ball at different angles so as to score 4 6 Able to determine position of ball and opponent Robot is able to determine the position of the ball and its opponent 4 The process of developing product specifications begins with your completed matrix of interpreted customer needs. Again note that there are no values.

ECEn 490 -Fall 2015 Product Specs 12 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 -Fall 2015 Product Specs 13 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 -Fall 2015 Product Specs 14 # Customer Need StatementsInterpretation of NeedsImp. 1Can win Robot can score more goals than opponent 4 2Can control the ball while moving Robot can maintain possession of the ball while moving 4 3Want a simple design Robot has simple design so as to facilitate functionality void of problems 4 4Can block shots Robot positions itself between its goal and the ball to prevent a goal 4 5 Robot is able to score from anywhere on the field Robot is able to shoot the ball at different angles so as to score 4 6 Able to determine position of ball and opponent Robot is able to determine the position of the ball and its opponent 4 Example of a customer needs table

ECEn 490 -Fall 2015 Product Specs 15 Metric # Need # MetricUnitsMarginal Value Ideal Value 11 Goals scored minus conceded goalsGoals> 0> 2 22 Distance from ball to robotcm<10<2 32 Time from possession of balls>10>=30 42 Radius of circle made while in possession of ball at top speedcm>=50>=10 53 Number of motors, circuits, batteries, moving partsparts<=12<=6 63 Number of lines of codelines Percentage of blocked shots given random speed and location of ball and robot %>=50>=90 85 Percentage of goals given random location of shot and opponent %>=70>=95 96 Maximum difference between calculated ball position and actual ball position cm<=5<1 106 Maximum difference between calculated opponent position and actual opponent position cm<=5<1 Example of a Product Specification table

ECEn 490 -Fall 2015 Product Specs 16 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 -Fall 2015 Product Specs 17 Values of Metrics 1.At least X-- set a minimum amount, 2.At most X -- set a maximum, 3.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 -Fall 2015 Product Specs 18 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 -Fall 2015 Product Specs 19 Tools for transforming Needs into Specifications –Needs-Metrics Tables –Quality Function Deployment- QFD –Competitive Benchmarking Analyze Data vs. Requirements Correlate Requirements with Measures measure requirements

ECEn 490 -Fall 2015 Product Specs 20 Needs-Metrics Tables Metric #Need #MetricUnits 11 Goals scored minus conceded goalsGoals 22 Distance from ball to robotcm 32 Time from possession of balls 42 Radius of circle made while in possession of ball at top speedcm 53 Number of motors, circuits, batteries, moving partsparts 63 Number of lines of codelines 74 Percentage of blocked shots given random speed and location of ball and robot% 85 Percentage of goals given random location of shot and opponent% 96 Maximum difference between calculated ball position and actual ball positioncm 106 Maximum difference between calculated opponent position and actual opponent positioncm 117 Maximum percentage error between calculated ball position and actual ball position per second%/s 127 Average percentage error between calculated opponent position and actual opponent position per second %/s 13 8, 18Accelerationm/s^2 14 9, 18Mx speedm/s 15 10,25,27Time elapsed from a change in the environment to a change in the robot's actions 1611 Whether or not a victory dance is implemented at the right time (ie after robot scores)N/A

ECEn 490 -Fall 2015 Product Specs 21 Quality Function Deployment- QFD, or a Needs-Metrics Matrix Metrics Goals scored minus conceded goals Distance from ball to robot Time from possession of ball Radius of circle while in possession of ball Number of motors, batteries, moving parts Number of lines of code Percentage of blocked shots given random speed Percentage of goals w/random location of shots 1Robot can score more goals than opponent 2Maintain possession of the ball while moving 3simple design with functionality w/o problems 4positions itself between its goal and the ball 5able to score from anywhere on the field Needs

ECEn 490 -Fall 2015 Product Specs 22 Competitive Benchmarking Metric # Need # MetricUnitsMarginal Value Ideal Value 11 Goals scored minus conceded goalsGoals> 0> 2 22 Distance from ball to robotcm<10<2 32 Time from possession of balls>10>=30 42 Radius of circle made while in possession of ball at top speed cm>=50>=10 53 Number of motors, circuits, batteries, moving partsparts<=12<=6 63 Number of lines of codelines Percentage of blocked shots given random speed and location of ball and robot %>=50>=90 85 Percentage of goals given random location of shot and opponent %>=70>=95 96 Maximum difference between calculated ball position and actual ball position cm<=5<1 106 Maximum difference between calculated opponent position and actual opponent position cm<=5<1 Comp 1 Comp 2 Comp 3 Comp Evaluate the competition

ECEn 490 -Fall 2015 Product Specs 23 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 ed to Prof. Clifford by next Tuesday, Sept 22 nd. Read Chapter 6 Concept Generation or the class notes on the website.

ECEn 490 -Fall 2015 Product Specs 24 1.Project Description and background: What is the project, and what is expected to be accomplished. 2.Project Requirements: Who is the customer, and what are the interpreted needs and requirements including their relative importance. (customer needs table) 3.Product Specifications: The measurable engineering characteristics (metrics) and target values for the product. 4.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) The Four sections of the FSD

ECEn 490 -Fall 2015 Product Specs 25 Suggested team exercise –Meet as a team –take the critical 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.