ME 2110 Creative Decisions and Design Final Report

ME 2110: Creative Decisions and Design Final Report and Presentation Review Session The George W. Woodruff School of Mechanical Engineering Georgia Institute of Technology Atlanta, GA 30332 © GIT 2007

Agenda • The Next Two Weeks • Final Report Overview • Final Presentation Overview • Judging Overview © GIT 2007 2

This Week • • • Final Competition is Friday!!! Show up at 4: 45 pm in Ma. RC atrium Judging begins at 5 pm Competition begins at 6: 15 pm Hopefully, done by 9: 15 pm • Invite your friends and family!! © GIT 2007 3

Next Week • Final Report and Presentation due in studio • Peer Evaluation Forms © GIT 2007 4

Final Report Requirements • Maximum of 10 pages of text • Include Table of Contents • Include Bill of Materials • Follow style guidelines and formatting © GIT 2007 5

Final Report Outline Cover Page Abstract Table of Contents I. Introduction II. Design Overview III. Design Presentation IV. Methods and Results V. Closing Figures and Tables © GIT 2007 6

Abstract • Summary of what is presented in the report • Include relevant numerical results – Final Competition results – Judging Results • Include “takeaway” point © GIT 2007 7

Introduction • Problem Definition – What is the objective of this project? – What are the most important rules? • Engineering Challenges – NOT the same as the rules or constraints – NOT the same as the tasks • End with “roadmap” sentence/sentences © GIT 2007 8

Design Overview • Begin with the complete machine – What points are you going to score? – What are your subsystems? – What is the general operation? – Full system figures • Give main dimensions of the machine • Indicate what is the front of the machine • Show subsystems © GIT 2007 9

Design Presentation • Divide discussions by subsystem • Subsystem description – Give more detail of each subsystem – Use “zoomed” figures of each subsystem © GIT 2007 10

Discussing Designs • Cite the Figure • List the design components • Check for consistency of names • Use descriptive functional names © GIT 2007 11

Methods and Results • Need to include and discuss – Specification sheet – Function Tree – Morph Chart – House of Quality – Management and Planning Tools – Two alternative concepts – Concept Evaluation (using evaluation matrices) © GIT 2007 12

Discussing Design Tools 1) Cite the tool. 2) State how the tool has been used to address the assigned task. 3) Concisely describe the tool (one sentence maximum). 4) Present details by calling out and speaking to three cells / entries. 5) State how the information in the tool will be used in the next steps of this design process. © GIT 2007 13

Methods and Results (cont. ) • Present two alternative designs – Complete Designs. Not just the subsystems. – Less detail than chosen design – Each description should “stand on its own” • Concept Evaluation – Use evaluation matrices (1 st-3 rd level presented in class) – Do not use the numbers as sole reason for choice © GIT 2007 14

Results • Present Numerical Results – Judging – Competition • Analysis of Results – Discuss in terms of the design process – What assumptions were correct? … incorrect? – What items were weighted too heavily? … too lightly? • What would you change and/or improve on your design? © GIT 2007 15

Conclusion • Outlines what was just presented in the report • Include relevant numerical results – Final Competition – Judging • What is the “takeaway” point? © GIT 2007 16

Final Presentation Requirements • Less the 10 minutes • One speaker • Content is similar to final report • Follow guidelines in Lectures from Dr. Donnell © GIT 2007 17

Suggested Outline • • • Title Slide Agenda Problem Definition Chosen Design (complete system) Chosen Design subsystems 2 -3 main design tools (the most important to YOUR design process) • Two Alternative concepts • Highest order evaluation matrix you used • Results and Analysis © GIT 2007 18

Judging 1. State how many points you expect to obtain per round 2. State what your machine is going to do, and what objectives it will complete 3. Show which subsystems obtain which points 4. Demonstrate a subsystem 5. Be ready to explain A) What’s clever, B) What’s unreliable, C) Why you stuck with this design, D) How much did it cost © GIT 2007 19

Reminders • Clean, Sweep and Vacuum the lab thoroughly this week. • Find any missing parts of your kit • Have fun on Friday! • Any questions? © GIT 2007 20