200 likes | 325 Views
ME4973 Intro. Outline. New team meeting times Syllabus [on web] Deliverables CDR, CAD, paragraph, graphic, design report Demo day ME4972 Feedback Shop needs / allocation Design report issues Oral 2 comments. Syllabus - Speakers. Energy Market: Chris D’Angelo, Zachry Ethics: Barber
E N D
Outline • New team meeting times • Syllabus [on web] • Deliverables • CDR, CAD, paragraph, graphic, design report • Demo day • ME4972 Feedback • Shop needs / allocation • Design report issues • Oral 2 comments
Syllabus - Speakers • Energy Market: Chris D’Angelo, Zachry • Ethics: Barber • Fatigue: T. Meyer • Testing Tolerance • Coef. of Variance, William Hally, Loctite • Tolerance in Testing: G. Quinn Hamilton • Lean Manufacturing: B. Montanari Habco • Patent law: Rafael Rosado P&W • Liability & Warrantee: Richard Bird, UConn • Group meetings
Syllabus - Deliverables • CDR • CAD=word format, name, team, object displayed, software used • Team photo=Igor or Barber by appointment • Paragraph and graphics by break • Orals 3, 4 ==== old guard • Demo day • No Friday classes • Setup Thurs. PM / Fri. AM • Judging starts at 10:30AM, public 1:00-4:00 • Special team needs: water, power, space, weight,…. • Format, posters, etc.
Syllabus - Deliverables • CAD Feb. 4 • CDR Feb. 11 • Team Photos Feb. 25 • Engineers week posters Feb. 22 ???? • Oral 3 Mar. 4 - Mar. 11 • Brochure input Mar. 13 • ASME speakers Mar. 13 • ASME Old Guard –U. Hart. Mar. 29 • ASME SPDC - W.P.I. Apr. 20
Syllabus - Deliverables Team 3 ASML: Prof. Baki Cetegen, Donald Karg, John Turner and Bryan Lightbody
Syllabus - Deliverables • Design report 1 Apr. 8 • Oral 4 Apr. 17-22 • Design report 2 Apr. 26 • Demo day May 3 • Final design report May 8 [Wed.] • Edited copy, 2 BxW copies, 1 color copy • Sponsor on-site visit T.B.D.
Design Report 1 • Missing deliverables • 1 color copy • 2 black and white copies • 1 edited copy
Design Report 1 Issues • Abstract… what WAS done • TOC… number sections here and in text, no TOC • Nomenclature: all symbols first used defined in text, alphabetical order • Figures / Tables – all have titles, cited in text, discussed • Figure titles on bottom • Table titles on top… tables are not figures • End of report requires summary, no conclusion now • References: personal communication, hardware sources, …
Design Report 1 Issues • No titles on cover page • Missing faculty /sponsor advisor names • Missing photos, graphics discussion • Reference citation • Figures cited and discussed, tables also
Design Report 1 Issues • Intro should include company background and array of products, including those not part of your project • …. • If continuation project… • Reference previous effort • Why did previous effort not work, explain and show data • Show how your ideas will work, not just personal confidence
Presentation Skills - 1 • Don’t use too many “ums “ [verbal pauses] when talking • Talk “to” the audience • Do read from notes • Hands out of pockets, speak out • Use pointer • Too much back and forth • Need to discuss axes on plots
Presentation Skills - 2 • Don’t chew gum!, Do not look at phone • Don’t prolong answering question , just get to the main point & be brief • Dress professionally • Ran over time; no time for questions • Bad flipping back to earlier charts, insert extra copy where needed.
Presentation Charts • Slide font a little too small • Gantt chart writing is too small, too detailed • Dark writings on dark background • Charts too busy • Do not number figures in oral presentation • Do not use small black font on dark picture • To small of a font for schedule / Gantt • Significant figures issue • Change numbers to percent error
Presentation Organization • Need title on title chart • Need outline • Need some sponsor background, not just on your product / problem • Need summary • Summary not conclusions
Design - 1 • How scaled? • Why choice of design? • Mention what software you are using or planning on using • Explain use of software [Fluent], why used? Validation? • Mesh sensitivity study is always needed • Explain terms [roping], is it a technical term used or yours? • No analysis, simple control volume type is needed ASAP
Design - 2 • Sloppy & free hand drawings • Use simple schematic or block diagram for concepts during orals • Need more figures & schematics… a picture is worth a thousand words • Try to include all your graphics in the presentation & avoid jumping around • Any analysis done to select hardware
Finally • For renewed projects need details why last project failed-incomplete, show data, etc, show photos • For entrepreneurial projects there has to be economics effort presented • Not all projects will finish on Demo Day