project 14361. agenda intro problem background problem statement and deliverables stakeholders use...
DESCRIPTION
Team Members Corey Gillsepie – Electrical Engineer Thomas Gomes – Electrical Engineer Henry Almiron – Mechanical Engineer Dirk Thur – Mechanical Engineer Jennifer Leone – Industrial Engineer Lawrence Hoffman – Electrical Engineer Angel Herrera – Electrical Engineer Saleh Zeidan – Mechanical EngineerTRANSCRIPT
Project 14361
Agenda
• Intro
• Problem Background
• Problem Statement and Deliverables
• Stakeholders
• Use Scenarios
• Prioritized List of Needs
• Engineering Requirements
• Draft of Project Plan
Team MembersCorey Gillsepie – Electrical EngineerThomas Gomes – Electrical EngineerHenry Almiron – Mechanical EngineerDirk Thur – Mechanical EngineerJennifer Leone – Industrial EngineerLawrence Hoffman – Electrical EngineerAngel Herrera – Electrical EngineerSaleh Zeidan – Mechanical Engineer
Problem Background
• Students in the Mechanical Engineering department currently take a sequence of experimental courses, one of which is MECE – 301 Engineering Applications Lab.
• The goal is to have a common lecture period for all sections, and then a weekly, simpler experiments that students will also run independently.
Problem Statement and Deliverables
• The purpose of this project is to design and produce a number of laboratory modules that will eventually be used in the engineering course MECE – 301 Engineering Applications Lab
• Three to four modules used to provide a set of advanced investigative scenarios that will be simulated by theoretical and/or computational methods.
Stakeholders
• RIT ME students
• RIT ME professors
• MSD Team
Use Scenarios
• In the lab students will analyze a module which inspire an experiment which will include a theoretical, and experimental analysis of the module.
• After completing this experiment, the students should have a firmer grasp on basic engineering principles and processes.
Risk Management
ID Risk Item Cause Effect Likelihood
Severity
Importance
Action of Management
Owner
1 Complexity of Modules
To hard/ to simple
Students fail to learn
2 2 4 refer to customer
expertise to ensure proper
complexity
Team P14361
2 Injury to student
Human error Death, severe injury, emotional
trauma or dismemberment
1 3 3 In-depth Risk assessment/an
alysis once modules are
chosen
Project leader
3 Damage to dat property
Misuse of modules
Damage to dat property
1 2 2 In-depth Risk assessment/an
alysis once modules are
chosen
Mechanical Engineer
4 Late parts Failure to check lead
times
Missed deadlines 2 2 4 Establish order deadline
Team P14361
5 Budgeting Over/Under spending
Run out or lose funds
1 1 1 Budget accordingly
(pizza party)
Team P14361
Prioritized List of Needs
• Requests 3 modules at minimum; 4 or 5 are preferred
• Modules may be of different technical challenge and complexity
• All modules must emphasize practical engineering experiences.
• All modules should be interesting to the students
• All modules should bridge applications areas, such as electromechanical or electrochemical
• All modules should use commercially-off-the-shelf equipment to enable maintenance and sustainability of module use over many semesters of student enjoyment
• At least one module should have analysis challenges that are at or beyond student learning from core coursework
Prioritized List of Needs cont.
• All modules should be able to be fully configured, utilized, and returned by student engineers
• All modules should be able to stand alone; they should contain everything they need without borrowing from other sources
• All modules should have a high level of flexibility and expansion allowing for many engineering opportunities
• All modules must be robust and safe
Engineering Requirements
Draft of the Project Plan