Presentation is loading. Please wait.

Presentation is loading. Please wait.

SENIOR DESIGN Conceptual Design Presentation TOPICS:

Similar presentations


Presentation on theme: "SENIOR DESIGN Conceptual Design Presentation TOPICS:"— Presentation transcript:

1 SENIOR DESIGN Conceptual Design Presentation TOPICS:
IENG 464 / 465 FALL / SPRING 2013 – 2014 TOPICS: Conceptual Design Presentation Conceptual Design Report Conceptual Design Outcomes SENIOR DESIGN Conceptual Design Presentation

2 Conceptual Design Presentation
Preparation & Requirements

3 First Term: Conceptual Design Presentation
Presentation: Final Exam Period 20 min. presentation, 10 min. questions Due via ½ hour before presentation, before end Friday 13 Dec. Bring on a jump-drive Introduction (~ 2 min) Team Members & Responsibilities Problem Statement & Constraints Design Approach & Results (~ 9 min) Recommended Concept(s) (~ 8 min) Implementation/Testing Plan Implementation/Testing Budget Conclusion (~ 1 min) Questions (remaining time) Every member does a portion of presentation, answers questions 1/16/2019 IENG 471 Facilities Planning

4 Hints for a Successful Conceptual Design Presentation
Respect Your Audience Schedule at least a week ahead (and then send a reminder!) Be dressed appropriately Start and end on-time Avoid unnecessary jargon in your presentation Present appropriately for your audience Choose and use graphics and tables wisely Avoid any text below 16 point Mock-ups are an excellent way to communicate Practice Your Presentation Check the slides on the exact equipment ahead of time Make sure that the color scheme and font are readable Practice as a team After you have made your last change to the presentation, run through it twice more 1/16/2019 IENG 471 Facilities Planning

5 Hints for a Successful Conceptual Design Presentation
Be Professional Answer questions directly, honestly Check the slides for tpyos! Anticipate the questions your audience will ask Have hidden slides or “beyond the ending” slides to help with questions Don’t get flustered or defensive OK to say “I don’t know”, especially if you follow up with “I’ll find out” Expect Tough Questions Make sure you have your slides numbered Bring copies of your slides as handouts Every member does a portion of presentation, answers questions 1/16/2019 IENG 471 Facilities Planning

6 Conceptual Design Report
Preparation & Requirements

7 Conceptual Design Report
First Term Report: (Due Wednesday of Finals Week, 12:00 Noon) Cover Page Executive Summary Table of Contents Introduction Problem Statement & Constraints Methodology & Preliminary Analysis Recommended Concept(s) Concept Implementation Planning Implementation Timing Estimated Implementation Cost Conclusion & Acknowledgements References Appendices Include copies of relevant engineering notebook pages from each member; communications; trial designs … 1/16/2019 IENG 471 Facilities Planning

8 Conceptual Design Report Format
Turn in a paper and electronic copy – single document Paper copy will go to your client/sponsor – so be professional! Cover Page - With project title, and team members. Table of Contents - With page numbers. Executive Summary - One page or less. Brief description of problem(s), approach, main findings and recommendations. Introduction - Include an overview of the problem and operations. Briefly discuss the project thrust. Problem Statement - Concise description of problems that are addressed by this project. What is wrong? Who is being affected? Etc. Methodology and Preliminary Analysis - This can have sub-sections. Justify your approach. What other approaches were available to you? This section should contain a research review, with pertinent references cited from your reference section. Describe how you approached the problem - methods and procedures, assumptions, analysis techniques used, data sources. Why did you choose your approach? Teams are expected to make and justify their own assumptions in areas where information provided is unclear or insufficient. 1/16/2019 IENG 471 Facilities Planning

9 Conceptual Design Report Format
Recommended Concept - Provide a brief summary of your analysis results and then present your design concept. Discuss the results and their sensitivity to changes in assumptions. Some graphs and charts would be good in this section. Detailed printouts or calculations should be put in an appendix. Note, all pertinent information must appear within the body of the report. The reader should only need to refer to the appendices to get more detailed information. Concept Implementation Planning - Describe a clear list and discussion of your next-term recommended tasks. Follow this with an implementation plan (Gantt chart). Discuss the estimated costs and benefits for implementing your recommendations, as well as any limitations. Follow this with a next term budget and timing of expenditures Conclusions and Acknowledgments. References - (Including oral conversations, listed as “Personal Communication”.) Note, citations should be made throughout your report where appropriate. Appendices - Drawings and Equipment Listing if required. Also summarize and document data collection (OPCs, BOMs, Value-Added, …) 1/16/2019 IENG 471 Facilities Planning

10 CDR Outcomes Grading & Budgets

11 PROJECT MANAGEMENT PROCESS
IEEM Senior Design Projects address REAL problems: IEEM developed expertise is demonstrated DURING the project IEEM Project Rubric considers: Context, Analysis, Recommendations, and Communication ALL projects require management of the “triple constraint”: Time, Budget, and Function Result of each term is an earned LETTER GRADE Senior Design Project Process: Draft Team Formation Individual Resumes Client-Team Meetings Engineering Project Proposal & Documentation Conceptual Design Development Progress Reporting Conceptual Design Presentation Design Development & Testing Results Presentation Final Project Documentation Final Project Documentation is due at NOON on Friday of Finals Week

12 IEEM PROJECT & PRESENTATION RUBRIC
3 2 1 Context Account for Environmental Variables Can identify both engineering and other environmental variables apropos to issue Can identify engineering related environmental variables apropos to the issue Can identify environmental variables, but unsure which are related to the issue Fails to identify environmental variables or see the need for these variables Define Problem Root cause(s) of problem determined Root cause(s) looked for, but process ended too soon Multiple symptoms aggregated as problem First symptom seen “defined” as the problem Gather Evidence Wide range of appropriate evidence sources used Some appropriate evidence sources used Evidence sources used, but not entirely appropriate to issue No or inappropriate evidence sources used Analysis Choose Appropriate Tools Both quantitative and qualitative tools used as appropriate Uses quantitative tools as appropriate Uses tools, but tools are not appropriate to issue No tools or frameworks used Develop a Chain of Evidence Clear links – uses data in its context and connects data using appropriate tools Links – uses data and connects using appropriate tools Almost links – based on inadequate data or tools No links – no chain of evidence Recommendations Make Choices Recommendation links to chain of evidence and shows consideration of additional alternatives Recommendation links to chain of evidence but comes from the “canned” set of alternatives Recommendation does not link to chain of evidence No recommendation made Reasonable Solutions Solution(s) considers implementation concerns, level of actual improvement, economic impact, social impact, and ethics Solution(s) considers implementation concerns and economic impact Solution(s) is technically feasible, but no additional concerns are considered Solution(s) is not feasible Communication Clarity of Argument Presentation of argument demonstrates problem definition, chain of evidence, analysis, and recommendation in easy to follow manner Presentation of argument demonstrates problem definition, chain of evidence, analysis, and recommendation but not easy to follow Presentation of argument demonstrates only parts of: problem definition, chain of evidence, analysis, and recommendation Presentation of argument cannot be followed by reasonable audience member Professional Presentation Well organized, uses professional language and grammar, appropriate use of tables, figures, etc, aimed at audience Somewhat organized, mostly uses professional language and grammar, appropriate use of tables, figures, etc, mostly aimed at audience Somewhat organized, poor grammar, uses texting language, needed figures, tables, etc present and appropriate, not aimed at audience No organization, poor grammar, uses texting language, needed figures, tables, etc not present, not aimed at audience

13 SIX SIGMA CERTIFICATE REQUIREMENTS
Six Sigma Project (IENG 463) requirements: DMAIC process is used DURING the project Stand alone project report is submitted for a LETTER GRADE Six Sigma Project Report: Report Structure: Cover Page Introduction & Problem Statement Headings for DMAIC Sections Recommendations, Conclusions and Acknowledgements References Appendices Report is due at NOON on Friday of Finals Week

14 Questions & Issues? Grading: Budgets: Finals Week:
Team grade is a base Individual grades may be better or worse Budgets: Allocated amount will be ed to the team by 23 DEC Finals Week: Term scores will post online Wednesday, Noon, grade book closes Wednesday, PM reports get graded Grades & Budgets posted on website by Saturday, PM Department will be keeping Concept Reports Can visit it, if you want – but keep a copy for yourself 1/16/2019 IENG 471 Facilities Planning

15 ENGINEERING NOTEBOOK Care and Maintenance Requirements

16 Engineering Notebooks
Individual Responsibility Must be legally constructed Pages can’t be re-sequenced Missing pages are easily identified as such Must be legally documented Entries must be accurate Entries must be chronological Entries of importance should be witnessed Examples to document: Meeting times, places, attendees, topics Relevant phone conversations Relevant expenditures, mileage Design principles, concepts, sketches Engineering results, decisions, rationale Copies are placed in Project Notebook regularly 1/16/2019

17 Engineering Notebooks
Engineering Notebooks are a permanent record for legal purposes Notebooks have a durable cover Pages are sewn or perfect bound (not loose-leaf or spiral bound) Entries are made with permanent methods Entries are made in sequential order & dated Errors are lined out, but not obliterated Loose material is attached within the notebook pages (if possible), or referenced within (if not) 1/16/2019

18 Using Your Engineering Notebook
Blow-by-blow Documentation Corner of page Date & time Location Personnel present Title of task Experimental conditions, equipment ID numbers Blow-by-blow record of process Sketches of experimental setup / design Summarize major decisions / results Single line ends an activity, Double line ends day 1/16/2019

19 Eng. Notebook Entry Example
10/1/99 Team Mtg George, Jane, Judy (Elroy absent) 4:15 pm Clodfelter’s Bar & Grill Agenda: Refreshments Brainstorming Material Purchase Discussed cost vs. refreshment performance George presented analysis showing non-linearity at high $ end Decision to invent more effective beverage Brainstormed concepts Reduced water content Increased hops in raw stock Decision to invest in further research Planned expenditure of $25.00 Actual expenditure of $26.75 due to heavy tipping Refresh. Level Cost ($) 1/16/2019


Download ppt "SENIOR DESIGN Conceptual Design Presentation TOPICS:"

Similar presentations


Ads by Google