Popular in Course
Popular in Aerospace Engineering
This 46 page Class Notes was uploaded by Abe Torp on Saturday October 3, 2015. The Class Notes belongs to ARO103L at California State Polytechnic University taught by StevenDobbs in Fall. Since its upload, it has received 28 views. For similar materials see /class/218402/aro103l-california-state-polytechnic-university in Aerospace Engineering at California State Polytechnic University.
Reviews for IntroductiontoAerospacePropulsionLaboratory
Report this Material
What is Karma?
Karma is the currency of StudySoup.
Date Created: 10/03/15
Fundamentals of Systems Engineering Preliminary Design ARO 201 L Week 7 Lecture 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 1 System LifeCycle Engineering ACQUISITION PHASE gtquot UTILIZATION PHASE gt N C once tual DetaII DeSI n ProduotIon E 9 Product Use Support PreIImInary and andor E Phaseout and DIsposaI D DeSIgn Development ConstruotIon 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 2 0 090607 Continuing Tasks ln Preliminary System Design Requirements Developing design requirements from systemlevel requirements for subsystems and major system elements Specifications Preparing development product process and material specifications that are applicable to subsystems Functions Accomplishing functional analysis and allocation at and below the subsystem level Detail Design Pre aration Establishing detailed design requirements and developing plans for their allocation to engineering specifications Methods Identifying and utilizing appropriate engineering design tools a Iu technologies Trade Studies Conducting tradeoff studies for both design and operational effectiveness ReVIews erospace EngineeringFundamentals of Systems En Ineeerln Week 5 3 Conducting design revnews at predetermlne points in time Preliminary Design Review Team Presentation 2 All presentations will be submitted on a thumb drive and color hard copy Each team will have 25 minutes for their presentation and 5 minutes for questions Each team member shall deliver part ofthe presentation All questions will be held until the presentation is complete The presentation shall contain Title page with your Company Name and Logo Date ARO 201 Section Team quot Team Organization Chart Update with any new assignments add members Pictures with names Statement of Problem amp Program Objectives Update from Conceptual Design Program Life Cycle Schedule show from Needs to disposal life cycles Design Concept Graphics 4a Show one or more illustrations of your chosen total system design and 4b at least two key subsystems trade studies with callouts of key attributes and design features that caused you to select a speci c candidate and will illustrate that your system is superior to a competitor and will meet or exceed customer system level requirements 5 WBS Develop a more detailed Work Breakdown Structure for your project lower levels System to sub systems to components than you showed in your proposal with at least one page ofa WBS Dictionary for one important subsystem and components PWN 6 Requirements allocation to at least three ofthe subsystems showing traceability back to System Speci cation can show by adding boxes to the WBS diagram to the right ofthe the subsystem box 7 B Level Subsystem Spec A lower level subsystem speci cation forthe one important subsystem ou Y chose for the WBS dictionary showing traceability back to System Speci cation see chart 16 for a B Level spec outline 8 A requirements veri cation matrix observation analysis similarity simulation test etc 9 Application Of Models Diagram Model Based Systems Engineering example Landing gear design and analysis 10 10a Prioritize TPMs from proposal that relate to the subsystem you chose for the B Level Subsystem Spec or new ones if you change or re ne your TPMs and 10b Plot TPM vs time make guesses 11 Test strategy showing test objectives success criteria assets required and types of test facilities 12 Rislt analysis 12a Risk Cube 12b Technical Risk Mitigation Waterfall 12C Program Risk Mitigation Wa erfall 13 Summary Chart with a few bullets telling why your system preliminary design is worthy of being selected to go on to Detail design 39 You will be graded on technical content and quality of your oral presentation and Power Point Graphics by the instructor amp the class Team Logo X Title of Chart Point1 Point 2 Point 3 Sub point 1 Sub point 2 Sub point 3 Point 4 Pictures plots tables Title of Request for Proposal 10 Team Organization Chart Preliminary Design U date with an new assivnments add members Pictures with names 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 6 20 Program Objectives U date from Conce tual Desivn 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 7 Definition of Need E System LifeCycle Process Preliminary Design Conceptual Design Feasibility study a Needs analysis b Syste operational requirements 0 System maintenance concept d Functional requirements Advance product planning plans and specifications gt System functional analysis Preliminary synthesis and allocation of design criteria System optimization System synthesis and definition Functional analysis System operational identification of alternative functions and sub functions Allocation of Allocation of system support requirements System analysis System and performance factors subsystem tradeoffs functions design factors and and evaluation of System analysis effectiveness alternatives System and subsystem analysis Preliminary design performance configuration and arrangement of chosen system analyses data prototyping physical models testing etc Detail specifications i t J Feedback J Detail Design and Development v System product design Production andor Construction System prototype development Detail design of functional system prime equipment and software Detail design of system maintenance and logistic support elements Design support functions Design data and documentation System analysis and evaluation Design review System prototype test and evaluation System assessment analysis and evaluation Development of system prototype model Development of system maintenance and logistic support requirements lr Test preparation Testing of prototype system and equi ment Test data analysis and evaluation Test reporting System analysis and evaluation Modifications for corrective action Modification for corrective action andor for product improvement lr Utilization and Support gt System assessment analysis and evaluation Modification for corrective action or for product improvement t J Feedback Phaseout and Disposal I 30 Life Cycle Schedule Crewed Space System Objective Emergency Crew Retum amp Deliver Crew and Cargo to Orbiting Space Station 39 i 0 Milestones 05gt Crew Emergency gtme amp Cargo quotrm 5 mime R lUn Transfer NeedslMissions WWW Capability Capability Space Station Tech Develop Concept Design Veri cation 050le Prelim Design Detail Design Production UtilizationSupport Flt Test Vehicle Disposal S stem Disr owl l 000007 A r quot 39a Week59 Weekl 18b UU I IIU V UIU VUI IUUUIU I Illvl Program Objective Update chart as needed from Conceptual Design chart 16 emphasize the Prelim Design bar in your presentation Months or Years Milestones Tasks 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 10 40a Chosen System design concept graphics Orbit Transe I 39 es 2 Earthto Orbit Subsystem n 39 39 f 7 ed rgo g lt lsron ellvery M r j K 39 m ISS and P 0L 39 fer nf39guratlon conf Cargo Deli ry Ve cle TDRSS 3 pace Support a quot lnfrt cte bsystem 7 1 Ground Support r 7 Grou Tracking f 39 lfrastructure Subsysf r amp Co trol l39f NW 39 ehicle and Payload tegration Building g f H 5 7 Maintenance 39 39 g MISSlon Ops Hanger Support 0 Launch Pad Room OffLine Payload Processing quot upport hop and Offices aining 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 11 40b1 Design Concept Graphics 1st Stage LoXILH2 VTOIHL 5 Engines Autonomous fly back Integrated structure Composite Cryo tanks Propellant Cross feed Advanced TPS tiles CC leading edges TPS 2 week turn around Wet Wt 25MLbs Hydrazine RCS 2st Stage Bimese of 1st Stage Key Subsystems 090607 Cargo Pod Stays attached 2ncl stage for reentry GrlEpoxy 60 ft bay 19 ft Dia Compatable with OTV robotic extraction A rospace Engineeringrundamentals of Systems Engineeering Crew Vehicle VTOIHL olnterchanges with Cargo Pod GrlEpoxy with advanced TPS One main engine LoxILH2 6 Crew Dual escape system 2 week onorbit provisions GLOW 150K lbs Week 5 12 40b2 Engine Trade Study 1st Stage Engine 1st Stage Engine Candidate 1 Candidate 2 Pratt amp Whitey Rocketdyne LoXIRP LoXILH2 Thrust 12M lbs Thrust 09M lbs sp 245 sec sp 450 sec Cost 32M Cost 27M Reiabiity 1I125 Reiabiity 1I250 LOM LOM 0 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 13 40b3 etc other key component Trade Study Other Component Other Component Other Component etc etc etc etc etc etc etc etc etc etc etc etc etc etc etc etc etc etc Such as Control Surface Actuators hydraulics vs electric and Main Landing Gear single wheel vs dual wheel and Fuselage Material Aluminum vs Composites and etc You choose the key components for trades that are most important for meeting system level requirements 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 14 5a WBS for Preliminary design FXX Aircraft System 0001 1 I I I I I Air System System Installation Program Vehicle Integrated Test and Management Logistics Support Tests 1000 5000 2000 4000 X000 I z I I Airframe Avionics Integration Flight PIOPU39SIOW F IOJ39eCt SYStem And Control System Management Engineering Assembly System Management 1100 1300 500 1400 1200 X100 X200 i I x I I Navigatlon Eczema i j nmunications Preliminary Desrgn Aids Identi cation Develop More Detail at lower levels 1310 1320 1 in WBS I I I I I Head Radar Fire 39 Up Control 1 Display Software 132001 132002 132003 erospace ngineering un amen o ys ems ngineeering Week 8 15 be 607 A E 39 39 F d taLQ fS t E 39 39 5b WBS Dictionary Format PROJECTPROGRAM WORK BREAKDOWN STRUCTURE DATE FXX DICTIONARY CONTRACT NO SHEET OF 1 1 WBS LEVEL ELEMENT TITLE 1 2 3 4 5 6 x 1000 AIR VEHICLE ELEMENT DESCRIPTION AIR VEHICLE The complete flyaway FXX for delivery to the U S Government The flyaway FXX constitutes the structum a ac aled engines and subsystems including mission pecuiw equwment as defined by the Detail Specification for Model FXX Aircraft Weapon system including all attendant addendums and the Avionic Specification WBS LEVEL ASSOCIATED LOWER LEVEL ELEMENTS 1 2 3 4 5 6 TITLE X 1100 AIRFRAME 1200 PROPULSlON This is available as Example WBSppt on Aerospace 1300 AVIONICS SYSTEM Engineering Department website 14UU FLIGHT CONTROL SYSTEM 1500 INTEGRATION AND ASSEMBLY 0906 7 I I Aerospace ngIneerIng un amenaso ys ems ngIneeerIng Week816 6 Requirements allocation on WBS Requirements box E Sys Regmt s I i FXX TR00011 Range 1200 miles mg l Aircraft PR00012 Costaircraft system lt 40M I System TR00013 Detect enemy at 40 miles I gt10001 1200 mi 0001 TR00014 etc I range I I PR00012 gt Req ersk Air System System Installation Program 26M Vehicle Integrated Test and Management TR00013 Logistics Support Tests gt10003 piiot 1000 5000 2000 4000 X000 detect enemy at I 40m I I i r Airframe AID S Stem owed to com onent Flight Propulsion Project System w i Control System Management Engineering 10001 gt Req 10001 Cd crUIselt02 System Management 1100 10002 gt Req11002 Airframe costlt 1400 1200 x100 X20 18M i I I I I I I I System flowed to I N Fire Communications i Subcomponent System flowed to Subcomponent aVIgation i i Aids Control And I I L4 Regmts l e mts 1310 Identification Etc i 10001 gt Req 12001 Sp Fuel 1320 1330 39 Consumption lt 10000 Ibhr 3910002 gt Req 12002 Cost I System flowed to Sub 2Mengme Head Radar Fire p q C m onent Re mts Up Control 10003 gt Req 132002 1 Radar i Display Software power 2 mw for 40 mi range 132001 132002 132003 Aerospace EngineeringFundamentals of Systems Engineering Week 8 17 Types of Specifications System Specification Type A Includes the technical performance operational and support characteristics for the system Development Specification Type B Includes the technical requirements qualitative and quantitative for any new item below the system level where research design and develo ment are accomr lished Product Specification Type C Includes the technical requirements qualitative and quantitative for any item below the system level that is currently in inventory and can be procured Process Specification Type D Includes the technical requirements qualitative and quantitative associated with a process andor a service performed on any element of a system or in accomplishment of some functional requirement Material specification Type E Includes the technical requirements that pertain to raw materials or semifabricated materials 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 18 703 B Level SubSystem Specification Prelim Design insert a phrase to describe each line item add ref to related chart nos 3 charts max 10 Scope EX Covers Preliminary design requmts and design features for Earth to Orbit Subsystem 20 Applicable Documents 30 Requirements 31 System Definition 311 General Description 2 stage Reusable Launch Vehicle boosters cargo pod crew vehicle 312 Operational Requirements 313 Maintenance Concept what is it etc 314 Functional Analysis of what functions 315 Allocation of Requirements ex WBS allocation tree chart 5b shows allocation 316 Functional Interfaces 32 System Characteristics 321 Performance Characteristics 322 Physical Characteristics 323 Effectiveness Requirements 324 Reliability 325 Maintainability Choose a LilliSystem for our 326 Usability Human Factors SP6 Such as 1000 Aquot Vehf 0 327 Supportability Maintenance or 5000 Logistics 328 TransportabilityMobility 9 a mp quotequotts h as quot00 329 Flexibility Airframe or 1200 AVIonics etc 3210 Other 70b BLevel System Specification Prelim Design 33 Design and Construction 331 CADCAM Requirements EX CATIA CADCAM 3D solid models Product Data Manager 332 Materials Processes and Parts 333 Mounting and Labeling 334 Electromagnetic Radiation 335 Safety 336 Interchangeability 337 Workmanship 338 Testability 339 Economic Feasibility 34 DocumentationData 35 Logistics 351 Maintenance Requirements 352 Supply Support 353 Test and Support Equipment 354 Personnel and Training 355 Facilities and Equipment 356 Packaging Handling Storage and Transportation 357 Computer Resources Software 358 Technical DataInformation 359 Customer Senice 36 Producibility 37 Disposability 38 Affordability 40 50 an Test and Evaluation Quality Assurance Provisions Dietrth IHnn and r leiAmer Coninn u um NC 4 v 7O Retirement and Material RecvclinoDisoosal Example System Specifications Transponder Landing System Tactical Transponder Landing System Advanced Navigation amp Positioning Corporation SYSTEM SPECIFICATION December 16 997 DOZUMENT 0 000iI07R EV B Apprmetl Dale 12mm Name LlowlSmillI Tillc Prn39eciDireclurCluicl llng39nccr Also see this doc on CoE server MyEGR Class Folders 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 21 System Test and Evaluation The specific requirements for system test and evaluation are initiall determined during the conce tual design phase System level requirements are identified through the de nition or System operational requirements Maintenance and support concept Identification and prioritization of the technical performance measures 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 8 22 Test and Evaluation Directives Test and evaluation shall identify the preferred technical approach the technical risk and feasible solutions Test and evaluation will begin as early as I ossible in the ac Iuisition I hase and will be conducted throughout the system ac Iuisition I rocess as necessar to assess acquisition risks 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 8 23 Requirements Verification Methods Observation Requirement Example R10001 The aircraft shall accommodate no more personnel than a single pilot Satisfied b observing the ro osed design itself Analysis Ex Rx1003 The acquisition cost shall not exceed 40M for each aircraft in 2008 dollars Satisfied by a cost analysis Similarity Ex R50002 The logistics delivery time for an engine replacement shall not exceed the delivery time for the predecessor l18EF logistics trainquot Satisfied by using the same F18EF logistics train system for the new design Simulation Ex R10002 The aircraft shall be able to penetrate radar and hostile ghter defenses as such as posed by the North Korean and Iranian Air Forces as projected to exist in 2012 with a survival rate of 9991 000 sorties Satisfied by a computer simulation of the aircraft radar cross section and pilot in the loop mission simulations in a 6 dof motion based dome simulator Ground Test Ex R11001 The airframe shall have a fatigue life of 1 5 times the operational life time of 10000 hours using the cyclic loads based on combat mission pro le in Figure XXXY Satisfied by an actual airframe in a test stand having simulated air loads applied in cycles vs time over 15000 hours 2 year test Flight Test Ex R10003 The aircraft shall have an unrefueled range of 1000 nmiles carrying a 5000 pound weapons load with no external fuel tanks Satisfied by a flight test 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 8 24 Examples of Flight Tests Using Flight Demonstrators These are developmental usually are not for the final requirement veri ication Northrop Grumman39s BAC 111 This aircralt is being used to test the radar and DAS that will be employed byt e F35 Northrop Grumman photo Aerospace Engineerinngundamemals mi Systems Engineeermg Week we 725 Fe m WWW delensemedianelwurk cumslurieslrunlrendrulrlherkillrcham 80 S S S ec Aircraft Test Eval amp Re uirements Verification Matrix REQUIRE WBS VERIFICATION METHOD 39MENT EEK OBSERVA ANALYSIS SIMILIARITY SIMULA Ground Flight Tested TON TION TEST TEST R10001 1000 x R1000 2 1000 x R10003 1000 x RX1003 x100 x R11001 1100 x R50002 5000 X 3222 Requirements trace back to System Speci cation Identify the specific test and test objective that is designed to verify requirement compliance Week826 090607 Aerospace EngineeringFundamentals of Systems Engineeering Example RS 68 Engine Test Program to validate Thrust and Reliability requirements 7 i 7 ii Lab AFRL cziiromia Stennis Space Center 55C Mississippi Figure 15 RS 68 Engine Test Program REF EVOLVED EXPENDABLE LAUNCH VEHICLE SYS39l RSGS MAIN ENGINE DEVELOPMENT David Conley Capt USAF SMCIMVB Norman Y Lee Aerospace Corporation Peter L Portanova Aerospace Corporation Byron K Wood Vice President and General Manager Rock mgropulsion amp Power The oeing ompany No of Tests 2000 1800 1600 1400 1200 1000 i 800 600 400 200 US Apouo 1730 NumberofEngmes F1 Aerospace EngineeringFundamentals of Systems Engineeering us Shuttle Japan Eunope Hll Ariane D thaw 280 e a if 258 183 13 16 15 m SSME LE7 VULCAIN RSGB Figure 17 EnginesTests First Flight Certification Week 8 27 9 Application Of Models Model Based Systems Engineering example Landing gear design and analysis See separate briefing Chart 90 MBSE we will do demo in class to fill out your chart 9 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 28 What is Model Based Systems Engineering I Simulation of the complete system I Description of physical phenomena based on w macroscopic parame ers I Multidomain I Multilevel approach I The simulation model is an assembly of components I Components are described with analytical or tabulated models I We are looking for staticdynamic responses time 8 frequency domains 3 sure r c Used by permission 39om LMS Cal Poly student use only not to be distributed beyond Cal Poly m copyngm LMS Imemallonal 72ml Hydraulics Flight Control All types of controlled systems coupling mechanical electromechanical hydraulic thermal Hydraulic cylinder with moving body I Mechanism Animation r l 21 copyrigm LMs lnlemmrunabml l H mm Imva39rinn Used by permission from LMS Cal Poly student use only not to be distributed beyond Cal Poly 090607 Model Based Systems Engineering Example Landing Gear Shock Absorber Design to Prevent C Lll II I I II I I AIR TRANSPORT SAFE LORI RANSON WASHINGTON DC Boun check out our collection of online dynamic 1 aircraft profiles for the latest news Inior matlcn and images on civil and military programmes at igtrtgohalxomnro tes I ced MD115 spark training alert After series of heavy landings and rollover accidents US safety authority urges changes to make pilots aware of sink rate S safety regulators are urging new regulations to halt a raft of Boeing MBA11 hard landings which in some cases have result ed in the aircraft being destroyed Fourteen such landings since the MD11 entered service in 1990 have led to substantial damage Four events were hull losses while seven have Doomed in the past two 39ears 39 The National Transportation Safety Board in a recommen 8 tion letter to the Federal Aviation Administration sai The number and severity of these events raise concerns that the MID11 ight crews are not effec tively trained 39 J an i rest high sink rates during landing or to properly control pitch atti l tude following chord landing quot It requests that Boeing revises MID11 operating manuals to re emphasise high sinkrate aware ness stress the importance ofmo montarily maintaining landing pitch attitude alter touchdown and using proper pitch attitude to L l r L a A to perform a goeeround after a bouncedlandin The NTSB also wants all MD 11 operators to incorporate Boeingrecommended bounce recognition and recovery proce dures in operating manuals and naming I It focuses on the accident in volving a Lufthansa Cargo MD IIF that caught re alter a hard landing at Riyadh Saudi Arabia on 27 July 2010 The captain ml Three of the trlje 3 re ed Inverted as the jolt snapped wing spars monitoring the approach did not call out the high sink rate or call for a goaround it said Following initial touchdown the aircraft bounced 39lAm 47h off the runway and touched down a second time at 3g After the sec ond touchdown the aircraft reached a pitch attitude of 13 and the force on the main lan luggear during the third touch down exceeded 4g Flight data indicated two large forward and all column inputs were made be tween rst and nal touchdown Although 6 rst of cer had cover training holding 75 pitch and applying gowaround st thecoman39sMD 1 chief flight instructor stated that the simulator was limited in its ability to capture the true sensa tion of a bounced landingquot the NTSB said Week 5 31 90 Model Based Systems Engineering Determinethe Minimum Shock Absorber Damping Coef cient for a landing Gear that will keep the Body Mass Port1 below mSquot2 for a 2msec sink rate hard landing LandeGearMudel Body Mass Acceleration Response 39om a 2 msec hard landing msquot2 4 WWWm gn siwmdm J m39 r M will N l l 39 D x v 2 Shock Absorber Damping Coef cient Newtonmetersec nanem AerospaceEngmeermgFundamentals UlSvstemsEnumeeermg Weekt r 32 10a Prioritized TPMs Update from conceptual design chart 7 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 33 1OB TPM Report for Max thrust range etc plot one example from your TPM chart 10a guess at the plot ups and downs Maximum Actual Goal Pammemr a DE Si m E Q 3 F a b 3 V V V V V VVV V Design Tests Evaluations Operational Expenence Event 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 34 11 Test Strategy Test objectives What are you trying to validate SUCCESS criteria What measurements do you make to know if the objectives are met Test articles VIind tunnel models Subsystems bench test articles Tech demonstrator Prototype Production vehicle etc Types of test facilities needed Windtunnels structures lab iron bird simulator for ight controls vacuum chamber flight test center etc 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 35 Risk Management Risk The I otential that something will go wrong as a result of one or a series of events Technical risks ie the possibility that a technical requirement WIII HOE oe acnleveo He OGSlgn or technology will not work Programmatic risks ie The possibility that the program cost schedule or humanequipment resource requirements will not be met Risk Mitigation A series of actions in a schedule performed to retire the risk to an acceptable level Team Activity Identify at least 2 technical and 2 Programmatic risks for 1 our I roect 1 Identify the key Programmatic and key Technical Requirements that if not met would cause the most damage to your program success 2 Format of a risk statement related to a requirement Requirement Risk amp statement f this occurs due to then the adverse consequence to the system will be that Write on the poster amp present 20 Risk Statements Senior Project Examples Chart 20 Programmatic Risk Requirement 812 Complete fabrication of the inflatable test article by April 9 P Risk 812 E the fabrication of the test article is not completed by April 9 due to late delivery from the supplier threatened by bankruptcy then the testing could be delayed past the team s graduation date and graduation would be delayed Message box at bottom Chart 30 Technical Risk example Requirement 821 the inflation pressure must be maintained constant during the loaddeflection test T Risk 821 the inflation I ressure is not constant durinw the load deflection test due to a leak or other unforeseen event then the sensor strain measurements would be invalid Message box at bottom Likelihood Goal reduce risk from red to 12a Risk Cube Cal Poly Senior Project Objective Structural Sensors Performance for Mars Inflatable 2 3 Consequence l V Technical Risks Risk Related Risk Related Reqm t Risk Description Reqmat Risk Description order hardware by Late Start OfNASA 1396ng Constant test Pressure leakage during test 811 NOV20 contra delaymg fundmg 821 pressure invalidating strain measurements Complete fabrication Supplier late hardware delivery Excessive learning curve for new 812 by Aprll 9 delaymg fabrlcanon Predict strains structural analysis software producing Late Start on modeling due to 822 under load inaccuracies in predictions 813 D6518 due NOV 18 trammg delaymg deSIgn Relate model Cannot obtain scaling factors preventing Lack of Lab availability results to full accurate scaling to full scale 814 Begin Test April 10 delaying test 823 scale deSIgn Vehlde Identifying Risk Severity in Risk Cube Likelihood is the likelihood the risk will happen processes or Near Ge na39nty39 are available a LOW Likelihood usually av0ided this type of risk With minimal oversight in on iven the risk is realized what would be the manitude of its im actc NSEQUENCE 1 2 3 4 performance and Technical a or no im ifsame ch etained alternatives eXIst though schedule slip rogramcritical path not achieve key ram milestone Schedule al or no im to meet key miss need date c a cor measco measco production cost it production cost it production cost gt mews o a or no im production cost 12b1 Mitigation Waterfall Programmatic Risk 812 Supplier late hardware delivery delaying fabrication Program Cal Poly Mars Re entry Balute Senior Project Risk Level Use standard strain gages while waiting for fiber L39kequoth d X optics sensors amp conduct correlaton rests on Consequence dummy 4 Extend project duration fr 3m 2 to 3 quarters raduation 1 2 Complete SP 3 Quarter fab of Report lest due hardware A The risk must be in the 39 green before this milestone I 39 I 39 I 39r l 12b2 Risk Mitigation Waterfa Technical Risk 821 Pressure leakae durin test invalidatin strain measurements Program Cal Poly Mars Reentry Balute Senior Project 3 Design alternate tube end clamping seals Likelihood x Consequence Add pressure regulator and ctive compressor to test setup d sign to 4 ll IIVquot 39 quot 39v quottiretests A A A I x raduation 1 2 Complete SP 3 Quarter Test of Report hardware due The risk must be in the green before this milestone n 12a Risk Cube Project 14 5 4 Likelihood 3 2 1 Tech n ieaI Risl Key message goes here 12b Mitigation Waterfa Risk Project 25 High 15 I55 Yellow Likelihood X Medium Consequence 4 Low 1 Legend Time months years etc A Key Milestone before which the risk must be in the green I Mitigation activity Key message goes here 13 Summary with a few bullets telling why your system preliminary design is worthy of being selected to go on to Detail design Our Preliminary Design of the will etc at an acceptable risk level 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 45 Summary Preliminary system design is an extension of the conceptual system design activities Preliminary design moves from technical approaches to the design approaches VWe are ready to start the Preparing Preliminary Uesrgn Hevrew Presentation 2 Assignment Due Week 10 Team chooses a new leader for Prelim Design Read Chapters 4 and 5 Virgpare all Charts and do Presentation on Week 090607 Aerospace EngineeringFundamentals of Systems Engineeering Week 5 46