FeedbackPhase 0Feedback –Phase 0ProjectPhases- Conceptojectases- Affirmed Goals/Needs-Scope DefinitionDeliverablesp- Customer & Technology Basis- Project Plan- Concept Design- Engineering BasisPlan update- Proof of Concept PrototypePath Forward PlanScope Definition - Key Metrics- Technology Req’ts.Assess Customer Wants/Metrics/Specifications-Plan update-Path Forward PlanDesignConceptProveConceptDevelopment0Confirm Requirements1ProposeConcept23-Create/Design Concept; Analyze; Testppequ e e tspCreate/Design Concept; Analyze; Test- Benchmark TechnologyNote: UDesign and/or Engr Des by Dym and LittleWhat is a “Concept”?What is a “Concept”?A completely satisfactory solution to the problemHow many do you need?How many do you need?Abhh?Are some better than others?How can we propose validConcepts?Concepts?Only if we explain the requirements a “concept” must meetHow can we compare Concepts?Concepts?Only if we explain & validate the requirements a “concept” must meetRequirements = Target ValuesLater, how can we prove the design meets eq i ements?design meets requirements?Have measurable Target ValuesDo analysis/tests to prove itDo analysis/tests to prove itIf benchmarking and customer gdialog continue, does that ll th treally mean the wants, metrics, & target valuesmetrics, & target values change as we go?Of Course!Of Course! (e.g., Reuse jar and lid)(e.g., Reuse jar and lid)FeedbackContentFeedback -Content“h ld” “ ”Wants = “should” ; constraints = “must” Safety = Constraint Performance = WantCt WtCost = WantMetrics = ways to measure “wants/ constraints ”How does benchmarking lead to Metrics & Target Vl ?Values?Summarize why wants, metrics, target values chosen & how they drive the design!!!Show logic & assumptions/Explain “Decisions”See MS Project tutorial for making Gantt Chart for scheduling, explain task order (more later)FeedbackFo mFeedback -FormAlways deliver your best effortAlways deliver your best effortAlways spell-check, make user-friendlyAlways read out loud to catch errors!READ DIRECTIONS for formatContext – Background, Key Issues?“Sloppy”(or“Tarzan Talk”) means unreadable/Sloppy (or Tarzan Talk ) means unreadable /Embed important Figs & use Fig. #’s (Avoid Page-Flipping by Reader)Use photos/graphs whenever possibleCheck “Agendas” vs. “Minutes”Design Iss esDesign IssuesDo market research & strategyWhat’s wrong with current products? Is it really $?Whats wrong with current products? Is it really $? Can a new product be viable? More ergonomic?Use real people for customer reps Get sanity checks oftenDerive KEY Wants & explain (Open vacuum sealed jars)Derive KEY Wants, & explain (Open vacuum sealed jars)Benchmarking Derive Lessons Learned from benchmarking Analyze benchmarks for metrics & target valuesC t i WWW B k P l P d t tCategories: WWW, Books, People, Products, etc.Metrics & Target Values Derive KEY Metrics from KEY Wants, & explain Make metrics graphs for target values & tradeoffsWhi h i DRIVE h d i ? A h bl ?Which metrics DRIVE the design? Are they measurable? Which metrics DRIVE which subsystems? Concepts Select a best Benchmark Competitor Concept Derive Candidate Concepts from key Metrics, explain benefits/tradeoffsWitingIssesWriting IssuesMake it professional! Use 3rdperson for ReportsFive pages needs to be self contained, without requiring reader to refer to appendix.ldInclude: Title Page & Page #’sUse many Graphics and some TablesUse many Graphics and some Tables Figure #’s & Names & Callouts in text List of References (Author-Date) One Integrated PDF or Word Doc Don’t include process level documentsRtd’ttlld thi!D’tReports don’t actually do anything! Don’t say this report will demonstrate, show, … etc.Management Iss esManagement IssuesAssign 1 person as overall Editor Read the entire report out loudAssign 1 person for Quality Control Be sure all required elements are includedFind a Manufacturing Consultant Drives all concepts Start with Steve Beard See Books on reserveMCo sesIssesMyCourses IssuesUse correct levelsUse required doc names so I can findUse required doc names so I can find and download documents (especially Power Point Presentations)oe ot esetatos)Pee E alsPeer EvalsFollow Directions!Follow Directions!Well done is 85. You must Justify ratings over or under 85 See ratingratings over or under 85. See rating equivalents on input sheet. It would be very difficult too justify a 100!very difficult too justify a 100!On Time! No evaluation results in a 55 for you and 85 for team membersfor you and 85 for team members.ProjectPhases- Conceptojectases- Affirmed Goals/Needs-Scope DefinitionDeliverablesp- Customer & Technology Basis- Project Plan- Concept Design- Engineering BasisPlan update- Proof of Concept PrototypePath Forward PlanScope Definition - Key Metrics- Technology Req’ts.Assess Customer Wants/Metrics/Specifications-Plan update-Path Forward PlanDesignConceptProveConceptDevelopment0Confirm Requirements1ProposeConcept23-Create/Design Concept; Analyze; Testppequ e e tspCreate/Design Concept; Analyze; Test- Benchmark TechnologyNote: UDesign and /or Engr Des by Dym &
View Full Document
Unlocking...