Capstone Design Mechanical, Industrial, and Manufacturing Engineering

1. Capstone Design Mechanical, Industrial, and Manufacturing Engineering

2. MIME Capstone DesignToday's Class • Graduate School (Batten) • The Petition Process (Parmigiani) • Fall Term Deliverables *(Parmigiani) • Communication Inventory • Team Charter and Peer Performance Evaluation • Background Research • Product Projects: Existing Devices, Designs, and Methods (Parmigiani) • System Level • Component Level • Process Projects: Current State Analysis and Benchmarking (Funk)

3. Petition ProcessOverview • An approved petition can change any course requirement • Common petitions: • Changes to HoQ • Changes to Due Dates • Outcome of a petition is • Approve • Approve w/ penalty* • Refuse • Petition process is powerful, but students must be proactive! • A petition form is provided … * Penalty is at the discretion of the instructor. A common guideline is 10% per week of delay (e.g. change TP in week 3 of winter term = 30% deduction)

4. Petition ProcessPetition Form

5. Petition ProcessProcedure • Fall Term • Petition form not required for HoQ changes (just get approval signatures, including instructor) • For other changes, submit form to instructor • Winter Term • Petition required for all changes • Submit form to instructor (If petition involves HoQ, must have approvals)

6. Petition ProcessCriteria for Decision • Approve and waive penalty • No significant fault / negligence due to student team • Scope of project remains appropriate for Capstone Design • Original intent of project remains intact

7. Petition ProcessCriteria for Decision • Approve and impose penalty • Some fault / negligence due to student team • Scope of project remains appropriate for Capstone Design (HoQ) • Sufficient time remains to complete other deliverables (due date) • Original intent of project remains intact

8. Petition ProcessCriteria for Decision • Refuse • Scope of project would become inappropriate • Original intent of project fundamentally changed • Inappropriate effect (e.g. attempt to circumvent testing failure)

9. Petition ProcessExamples Project is to construct a wheeled, human-propelled, vehiclefor close study of plants in remote areas. Project requirementis that the vehicle can be disassembled and transported by oneperson over long distances and rough terrain. In week 5 of winter term, team asks that this requirement be droppedbecause it is "unrealistic". • Approve & waive penalty? • Approve & impose penalty? • Refuse?

10. Petition ProcessExamples Project requires data to be sampled at 100,000 Hz. Project Sponsor assures team that a device (well beyond project budget)is available to do this. Students list 100,000 Hz sampling rate as ER. In mid-winter term sponsor says he made an error and deviceonly samples at 25,000 Hz. Students request change in ER. • Approve & waive penalty? • Approve & impose penalty? • Refuse?

11. Petition ProcessExamples • Project requires specialized machining done at a machine shop recommended by sponsor. Students contact machine shop inearly December and schedule machining for 1 week before E1. All is well until 2 weeks before E1, when machine shop delays machining until after scheduled E1. Students request 1 week extension to E1 due date. • Approve & waive penalty? • Approve & impose penalty? • Refuse?

12. Petition ProcessExamples • Students require approval of the sponsor board to test their design. In week 4 of winter term, they request an extension to the E1 due date. They are unable to obtain board approval in time. They claim this is because communication with the board is impossible since the board will not meet again until after the current due date. They only meet once a month. • Approve & waive penalty? • Approve & impose penalty? • Refuse?

13. Petition ProcessExamples Students construct a drive mechanism for their projectusing V belts. During testing it becomes evident that a chain and sprockets are needed. Students have no funding remaining to buy sprockets, ask sponsor for more funding (change in ER: budget). Sponsor agrees to increase in budget. • Approve & waive penalty? • Approve & impose penalty? • Refuse?

14. Fall Term DeliverablesCommunication Inventory • Available on course Blackboard siteINDSTR ENGR ANALYSIS & DESIGN (IE_497_X001_F2010) • Purpose • A self assessment and goal-setting exercise • Help students focus on their engr. communication skills • Email • Written reports • Oral reports • Information for capstone design instructors & MIME to use in designing a communication curriculum for the school. • Due Thursday, October 7 in 102 DB drop box • 35 course-point penalty if not submitted on time. • Students will review the CI at the end of winter term as part of completing the Capstone Assessment Memo.

15. Fall Term DeliverablesTeam Charter and Peer Evaluation • Team Charter • A written agreement of the roles of each team member • Use template on course web site • Due by 4:00 PM Thursday (Oct. 7) in 102DB Drop box • Revise & Resubmit as necessary as roles change • GTA will keep current version on file • No changes after week 8 • Peer Performance Evaluation • A student evaluation of each team member • Use template on course web site • 100 course points • Must be based on roles defined in Team Charter • Due by 4:00 PM Monday (Dec. 6) in 102DB Drop box

16. Background ResearchSystem Level • Part of the “Existing Designs, Devices, and Methods” • Section 2.1 of report template • Required for Background Report • Consider your project at the system, or entire entity, level • For example, if your project was to design a pressure vessel for a particular application, you would describe existing pressure vessels meeting “similar” requirements • You must describe at least three other system-level designs, devices, or methods related to your project • For some projects relationships will be direct, for others less so… • It is expected, and desired, that you may need to stretch the idea of related existing designs devices and methods

17. Background ResearchComponent Level • Part of the “Existing Designs, Devices, and Methods” • Section 2.2 of report template • Required for Background Report • Consider your project at the component, or part, level • Perform a “functional decomposition” • Consider each individual task or function to be performed • In section 2.2, describe your functional decomposition • Your functional decomposition must include at least three components • For each component consider at least three existing designs, devices, and method (sections 2.2.x)

18. Background ResearchComponent Level • Again using the pressure vessel example … • Functional Decomposition • Generating pressure (pump) • Containing pressure (physical container) • Measuring pressure (gauges) • Safety / control (valves) • Component-level Existing Designs, Devices, and Methods • Pumps • Gear • Piston • Centrifugal … • You must describe at least three other system-level designs, devices, or methods related to your project • It is expected, and desired, that you may need to stretch the idea of related existing designs devices and methods