260 likes | 340 Views
Project Presentation. 2013 Annual Streamer Dogfight Competition Model Airplane Prepared for: Dr. Stracener Prepared by: Levi Duncan Date: 4/26/2012. Systems Engineering EMIS. Dr. Jerrell Stracener-Associate Professor. Background. Scope/Motivation:
E N D
Project Presentation 2013 Annual Streamer Dogfight Competition Model Airplane Prepared for: Dr. Stracener Prepared by: Levi Duncan Date: 4/26/2012 Systems Engineering EMIS Dr. Jerrell Stracener-Associate Professor
Background • Scope/Motivation: I am an Aeronautical Engineer who is hired for a side job to fabricate and deliver a model airplane to Team Lightning (father & son) in order for the team to compete in the 2013 Annual Streamer Dogfight Competition. This is their fifth year to enter in the competition, and they have decided to go with a different approach to develop their model. • Goal: My goal is to design, perform reliability analysis, build, integrate, and test the model airplane, ensuring it meets Team Lightning’s required, operational needs for their competition. 2
Team Lightning Requirements Customer: Team Lightning Operational Need: Remote control model airplane that is required to be effectively maneuverable and evasive to compete with other registered aircraft in the 2013 Annual Streamer Dogfight Competition. 3
Team Lightning Requirements(Cont.) Description: The model airplane must operate in the air for a minimum of 6 minutes and have high speed and quick turning capability. The aircraft’s system shall consist of the following major components: • Balsa/hardwood airframe • 2-cycle gas engine • Transmitter/receiver/5-servo electric control system • Landing Gear • Monokote finish 4
Team Lightning Requirements(Cont.) • Schedule: • Flight Test: Model airplane shall be ready for flight test and verification 9 months from job start date. • Delivery: Fully functional and verified model airplane shall be delivered to Team Lightning for training 11 months from job start date. • Team Lightning Priorities: • 1. Flight time • 2. Weight • 3. Maneuverability • 4. Delivery for training • 5. Total cost not to exceed $4,750 5
Program Performance Measures 0.5 450 1 100 7 3.5 10 55 Goal 50 600 8 0.65 150 4.5 8 1.5 200 2 9 900 0.8 6 6 40 Threshold C1 C2 S1 T1 T2 T3 T4 S2 Design/Build Cost (man hrs) Test/Verify Cost (man hrs) Design/Build Time (months) Weight (lbs) Flight Time (min) Top speed (mph) Barrel roll Time (s) Test/Verify Time (months) 9
Key Performance Parameter Line Graph A/C Weight (lbs) Tolerance Band 10 Planned Profile 8 6 Threshold Actual Value 4 Planned Value Goal 2 Time 10
Integrated Master Plan Team Lightning TRR LOA PDR CDR SRR TRR Air System • A/C ready for flight • test • Detailed • procedures • developed to • perform flight test • Risk assessment • (emphasis on • flight test) • System req. defined • Performance req. • defined • Initial risk • assessment • established • Design and interfaces defined (airframe, engine, electronic controls, gear, finish) • Draft test plans developed • Risk assessment (emphasis on detailed design) • A/C design and integration frozen with drawings ready for release • Final test plans written • A/C ready for production • Risk Assessment (emphasis on final design & producibility) • A/C ready for • integration testing • Detailed • procedures • developed to • conduct testing • Risk Assessment • (emphasis on • integration • testing) Key Accomplishments 11
Integrated Master Schedule 230 hrs 230 hrs 230 hrs 230 hrs 12
Achievements • Objectives: - Design a reliable and affordable product - Manufacture a quality product - Execute successful testing of product - Deliver product to customer on time - Product meets customer’s needs as advertised - Keep good reputation of my side business
Risk Management • Risks: - Repair cost uncertainties - Engineer’s technical experience - Violating TPM thresholds - Engineer’s flying experience for flight test - Customer’s learning capabilities during flight training 14
Benefit • Opportunity to promote growth in my side business • A chance to strengthen reliability analysis skills with real world product • Discover new ideas for future business products 15
Approach • Strategy/SOW: - Design architecture of model airplane - Perform reliability analysis on key components to determine optimal performance to customer’s priorities - Start build of the model airplane’s optimized design - Perform integration testing - Perform flight testing - Deliver model airplane to customer - Train customer to operate aircraft 16
Ground Rules and Assumptions • Scope: Assessment will apply to the design, reliability analysis, build, and flight test for model airplane, which is due 11 months after job go-ahead for Team Lightning training • Customer: Assume the customer’s requirements will not change after job go-ahead • Dependency: Assume all design programs, build tools, and pre-flight equipment will be accessible and have licenses granted for use; all procured parts delivered will meet system and cost requirements • Schedule: Assume all procured parts will be delivered on time for both model airplanes to support the design, reliability analysis, build, and flight test • Cost: Assume cost of design programs, build tools, and pre-flight equipment will not be included in the assessment
Ground Rules and Assumptions • Failure rate is constant • Exponential model is utilized for reliability analysis for key air system components • All items come on and function continuously at time = 0; all items turn off and stop functioning at time = t • Reliability analysis is performed based on past experience data • Cost is low priority to customer, so cost analysis will not be part of this assessment • Qualification test results for procured parts were not available from the supplier; reliability spec parameters are assumed from past experience • Flight time is customer’s top priority, so this TPM will be the only parameter assessed in the reliability analysis
Analysis Overview • Tasks: To evaluate the reliability of the flight time performance measure of the model airplane. • Method: • - Use exponential model to evaluate reliability; failure • rate and test time will be attained from past • experience testing • - Qualification testing done in same environment as • the customer • - Conduct analysis of reliability of TPM using • series configuration • End State: Calculate R(t) for each key component, then calculate overall system R(t) for evaluation of • airplane 20
Reliability Analysis • Test collection environment: • - Same exact model airplane has been flown for my personal • pleasure • - 210 cumulative flight minutes (3.5 hrs) recorded in log • book • - Over total flight time, the following failures have • occurred: 2 transmitter/receiver faults, 1 servo fault, 6 engine • faults • Test Results: • t (hours) = 3.5 • Tx/Rx failure rate (, failures/hour) = 2/3.5 = 0.57 • Servo failure rate (, failures/hour) = 1/3.5 = 0.28 • Engine failure rate (, failures/hour) = 6/3.5 = 1.7
Reliability Analysis • Required flight time TPM (KPP): 6 minutes (0.1 hrs) • Reliability Equation: R(t)=e -t • RTx/Rx = e –(0.57*0.1) = 0.945 • RServo = e –(0.28*0.1) = 0.972 • REngine = e –(1.7*0.1) = 0.844 23
Reliability Analysis • The model airplane’s key components are in a series configuration for the air system to successfully operate. • RS = (RTx/Rx)*(Rservo 1)*(Rservo 2)*(Rservo 3)* (Rservo 4)* (Rservo 5)*(Rengine) • RS = (0.945)*(0.972^5)*(0.844) • RS = 0.692 = 69.2% Tx/Rx Engine Servo (5x) (elevator) (RH aileron) (throttle) (LH aileron) (rudder) 24
Reliability Analysis System failure rate = = 0.57 + 0.28 + 1.7 = 2.55 System MTTF = = 1/2.55 = 0.392 hrs = 23.52 min 25
Results/Conclusions • Results: • - Overall reliability of model airplane is 69.2% • - Overall MTTF of model airplane is 23.52 minutes • Conclusions: • - Reliability of model airplane is acceptable to the customer, • Team Lightning, with the following things considered: • Required flight time is only 6 minutes • Regarding nature of competition, risk of losing • model airplane is on customer anyway • Engine is least reliable key component; emergency • landing procedures will be provided to customer in case • of engine failure 26