Aaron Nash (Mechanical Engineering) Erik Bellandi (Mechanical Engineering)

1. Project Status UpdateP09121 – MAV AirframeP09122 – MAV Control SystemP09123 – MAV Platform Structure Aaron Nash (Mechanical Engineering) Erik Bellandi (Mechanical Engineering) Joe Hozdic (Mechanical Engineering)

2. Project Status Update Project Number and Name P09121 Micro Aerial Vehicle (MAV) Airframe and Propulsion P09122 Micro Aerial Vehicle (MAV) Control System P09123 Micro Aerial Vehicle (MAV) Platform Structure and Layout Project Family Micro Aerial Vehicle Track Aerospace Systems and Technology Start Term 2009-1 End Term 2009-3 Faculty Guide Dr. Jeffery Kozak (Mechanical Engineering) – Confirmed Faculty Consultant Dr. Agamemnon Crassidis (Mechanical Engineering) – Confirmed Primary Customer Dr. Jeffery Kozak, RIT MAV Team - Confirmed Secondary Customer MAV09 Flight Competition

3. Phase 0: PlanningOverall Mission Statement Product Description /Project Overview MAV Family Objectives: • To build a semi-autonomous, tending towards full autonomy, air vehicle that will be used in the future for Multidisciplinary Senior Design and for graduate studies in the college of engineering and the college of imaging science. • To have a hands on aeronautical project for undergraduate students that is of low cost and simplicity as to be able to be made by hand. • To provide an incentive for students as well as exposure of engineering at RIT by competing in the more aggressive US/European MAV competition. Primary Market /Project Opportunities The primary market for this project is the RIT MAV team, and their future vehicle development. Secondary Market /Project Opportunities • DARPA • CIA • Military • Coast Guard • HAZMAT Teams • National Weather Service • 2009 MAV Competition Stakeholders • Dr. Jeffery Kozak • RIT MAV Team • 2009 MAV Competition – Rules and Regulations • Other 2009 MAV projects • Impact Technologies • Other companies funding projects

4. Project P09121:MAV Platform Airframe

5. Phase 0: PlanningProjectMission Statement Product Description /Project Overview The MAV family of projects: To build a semi-autonomous, tending towards full autonomy, air vehicle that will be used in the future for Multidisciplinary Senior Design and for graduate studies in the college of engineering and the college of imaging science. To have a hands on aeronautical project for undergraduate students that is of low cost and simplicity as to be able to be made by hand. To provide an incentive for students as well as exposure of engineering at RIT by competing in the more aggressive United States/Europe MAV competition This specific project (P09121) will design the airframe and propulsion system for a robust, stable, and reusable flying platform of contemporary MAV size onto which various sensors can be mounted by the end of Senior Design II. Key Business Goals/Project Deliverables The primary business goals of this product are to MAV specific airfoil and propulsion research Airfoil analysis, design, fabrication and testing Propulsion system design, procurement, mounting and integration Lifting and control surface research, design, and fabrication Flight Testing and tweeking

6. Phase 1: Concept DevelopmentIdentify Customer Needs - Interviews Primary Customer(s) The primary customer for this project is Dr. Kozak and the MAV program. Interview transcripts can be found on the EDGE website Interview 1 - Overall project scope defined for 2009 MSD year Interview 2 - Customer needs defined and preliminary questions answered Interview 3 - Mission statement defined Other Stakeholder(s) Other stakeholders who can possibly be interviewed are: Impact Technologies representative RIT representative (KGCOE dean, department heads etc) These interviews have not yet been conducted but are listed as possible sources for future inquiry Past Senior Design Team(s) Full list of past MAV MSD teams are available on the EDGE website dating from 2004 to present Interview with Michael Reeder (P08121 team leader) scheduled for this week

7. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Needs Statements: The MAV should: Be able to fly Be remotely controllable Be a stable flight platform Be robust Be able to interchange sensors, cameras, IR devices, and other sensing type payloads Be easy to fly Be a contemporary size and weight Have a wing span of no more than 80 cm Have a weight of no more that 1 kg Be highly adaptable Be semi-autonomous Be safe Be able to perform basic flight maneuvers Be able to run its motor and sustain flight for XX minutes

8. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret • Organize the Needs into a Hierarchy • Need 1: Size Characteristics • Need 1.1: Should adhere to MAV08 competition constraints • Need 1.1a: The lateral dimension of the MAV should be equal to or less than 0.8m • Need 1.1b: The weight of the MAV should not exceed 1kg • Need 2: Flight Characteristics • Need 2.1: Easy to fly • Need 2.2: Airfoil to achieve a greater than 1 lift to weight ratio • Need 2.3: Flight must be stable • Need 2.4: Able to perform basic flight maneuvers • Need 2.5: Able to fly in some adverse weather conditions • Need 3: Plane Characteristics • Need 3.1: Robust and durable • Need 3.2: Adaptable for different payloads • Need 3.3: Aerodynamic surfaces • Need 3.3a: Wings, horizontal and vertical stabilizers • Need 3.3b: Control surfaces

9. Work Breakdown Structure MAV Airframe & Propulsion Design Testing Fabrication Procurement Wing/ Airfoil Horiz/Vert Stabilizers Propulsion Hand Fab Pre-Fab Lifting Surface Materials Power Used Rudder Static Dynamic Thrust Propulsion System Elevator Weight Training Material Airfoil Shape Material Mounting Dimensions Propeller Geometry Dimensions

10. Preliminary Schedule

11. Future PlanWhere do you go from here? More interviews Dr. Kozak - Deliverables, WBS, Schedule, Staffing overviews Michael Reeder - Insights from the last MAV Pursue more funding Local companies Boeing Moog Set tentative staffing requirements Setting tentative resources More research on past MAV projects

12. Project P09123:MAV Platform Structure

13. Phase 0: PlanningProjectMission Statement Product Description /Project Overview The overall objective is to develop an expandable and re-useable Micro Aerial Vehicle (MAV) Platform. This platform is intended to be the base model for current and future MAV design. This project will develop the Platform Structure, in co-operation with two other projects addressing Aerodynamics and Control Systems. Key Business Goals/Project Deliverables Materials Research, Testing, and Manufacturability Evaluate Structural Integrity of Airframe and Components Determine Crash Worthiness and Failure Modes Equipment Protection, Packaging, and Mounting Primary Market /Project Opportunities The primary market for this project is the RIT MAV team, and their future vehicle development. Secondary Market /Project Opportunities The secondary market is the 2008 MAV flight competition. (military, outside sources?) Stakeholders Stakeholders in the design of our product include the following: - RIT MAV Team - Dr. Jeffery Kozak - 2008 MAV Competition – Rules and Regulations - Erik Bellandi – P09122- Micro Air Vehicle (MAV) Control System - Aaron Nash – P09121 - Micro Air Vehicle (MAV) Airframe and Propulsion System

14. Phase 1: Concept DevelopmentIdentify Customer Needs - Interviews Primary Customer(s) RIT MAV Team – Dr. Jeffery Kozak Interviews: 3/20/08 – Defined Project Scope 3/24/08 – Structural Needs and Goals 4/4/08 – Overall MAV Future Goals Other Stakeholder(s) MAV09 Competition Rules, Regulations, and Competition Scope Incorporate into Design Goals Past Senior Design Team(s) Mike Reeder – current MAV design Team lead Plan to Interview for Current Development Progress Past Project Archives Provide Insight Into Past MAV Development Problems Encountered/Lessons Learned

15. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Needs Statements: Provide undergraduate students with a hands on aero project Allow for addition of various sensors and other equipment Integrate various control devices and inputs into the structure Provide a stable platform from which to base future MAV projects and designs Provide opportunities for graduate level research projects Stay within guidelines of MAV09 Competition rules with goal of entering the competition within the next few years The Micro Air Vehicle needs to be: Cost effective Easy to manufacture Made from readily available materials Less than 1 kg in weight, and 80 cm in any dimension Made from lightweight materials Able to survive a crash with minimal damage to critical components Capable of withstanding sustained flight loads Self-sustainable

16. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Objective Tree:

17. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Needs Hierarchy: • Provide a stable platform for future MAV projects • Hands on aero project for undergraduate students • Base model for future senior design projects • Support for graduate level research projects • Allow for future development and easy integration • Allow for addition of various sensors and other equipment • Integrate various control devices and inputs into the structure • Design within guide lines of MAV09 Competition rules • Less than 1 kg in weight, and 80 cm in any dimension • Made from lightweight materials • Capable of withstanding sustained flight loads • MAV projects must be self-sustainable • Cost effective • Easy to manufacture • Made from readily available materials • Able to survive a crash with minimal damage to critical components

18. Preliminary Work Breakdown Structure Overview

19. Preliminary Work Breakdown Structure Details

20. Preliminary Work Breakdown Structure Details

21. Future PlanWhere do you go from here? Coordinate with aero design project and controls projects Conduct further interviews with customer Look into progress of current senior design project Develop more detailed schedule Refine WBS and Objective Tree Determine necessary resources

22. Project P09122:MAV Control System

23. Phase 0: PlanningProjectMission Statement Product Description /Project Overview To design a versatile flight control system for the Micro Aerial Vehicle, capable of adjusting for various platforms and conditions and upgradeable for future projects. Key Business Goals/Project Deliverables Primary Business Goals: Make the MAV as autonomous as possible. A control system able to stabilize and control the flight of the MAV based on inputs. A control system that can be adapted for flight conditions, payloads and platform characteristics. A fully tested control system capable of integrating to the MAV platform. Secondary Business Goal: Compete in the 2009 MAV Competition.

24. Phase 1: Concept DevelopmentIdentify Customer Needs - Interviews Primary Customers Dr. Jeffrey Kozak – Interviewed Project Scope Goals and Needs Project Objectives All Interview Information on EDGE Other Stakeholders MAV Team Other 2009 MAV projects Vendors Funding Projects Impact Technologies (MAV 08 Funding) RIT Current Senior Design Team MAV 08 – Mike Reeder (Team Head) – Interviewed Previous Analysis Equations on EDGE Industry “Rules of Thumb” Microcontroller (O-Navi) Possible Upgrade for Next Year Funding Interview Information on EDGE

25. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Needs Statements: The control system needs to: Be as autonomous as possible. Be independent of the platform. Work simultaneously with remote input. Measure the current conditions. Command the control surfaces appropriately. Be calibrated for the platform characteristics. Compensate for environmental conditions. Compensate for various payloads. Be light weight. Have GPS capability. Create a stable flight. Have a video relay system. Process data from all inputs. Have interchangeable sensors.

26. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Needs Hierarchy Control Capability Be as autonomous as possible. Create a stable flight. Command the control surfaces appropriately. Have a video relay system. Process data from all inputs.. Adaptability Calibrated for the platform characteristics. Compensate for environmental conditions. Compensate for various payloads. Have interchangeable sensors. Receive Inputs Work simultaneously with remote input. Measure the current conditions. Have GPS capability. Weight Be light weight Independence Be independent of the platform.

27. Phase 1: Concept DevelopmentIdentify Customer Needs - Interpret Objective Tree Establish Relative Importance of Needs The relative importance of the needs will be determined following further meetings with Dr. Kozak and Dr. Crassidis. Reflect on the Results and the Process Reflections will be made following the development of the relative importance.

28. Work Breakdown Structure

29. Preliminary Schedule

30. Future PlanWhere do you go from here? Refine Needs Establish Relative Importance of Needs Expand Work Breakdown Tasks and Items Integrate SD I & II Tasks into Schedule Refine Schedule