1 An Overview of MSFC Quantitative Risk Assessment (QRA) Practices Fayssal Safie/MSFC October 25, 2000.

Slides:



Advertisements
Similar presentations
Mission Success Starts with Safety The Similarities and Differences of Reliability Engineering and Probabilistic Risk Assessment RAMS VII Workshop November.
Advertisements

1 Component Design Basis Inspection (CDBI) Graydon Strong 6/17/14.
Work Breakdown Structures. Purpose The WBS shows different levels within the product hierarchy. For Government program managers levels 1-3 are of prime.
Display of Information for Time-Critical Decision Making Eric Horvitz Decision Theory Group Microsoft Research Redmond, Washington 98025
Training Manual Aug Probabilistic Design: Bringing FEA closer to REALITY! 2.5 Probabilistic Design Exploring randomness and scatter.
5 december 2011 Living Probabilistic Asset Management Dr.ir. J.A. van den Bogaard.
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
Managing Reuse Presented by: Aisha Al-Hammadi. Outline Introduction History. The technical and managerial advantages of Reusing Solutions. The main challenges.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Sustainment Management Systems
Page - 1 Rocketdyne Propulsion & Power Role of EASY5 in Integrated Product Development Frank Gombos Boeing Canoga Park, CA.
Uncertainties in Thermal Barrier Coating Life Prediction by Karl A. Mentz A Thesis Submitted to the Graduate Faculty of Rensselaer Polytechnic Institute.
RAM Modelling in the Project Design Phase Friday 30 th April, 2010 Paul Websdane Reliability Modelling for Business Decisions Asset Management Council.
«Enhance of ship safety based on maintenance strategies by applying of Analytic Hierarchy Process» DAGKINIS IOANNIS, Dr. NIKITAKOS NIKITAS University of.
Copyright © 2005, SAS Institute Inc. All rights reserved. Quantifying and Controlling Operational Risk with SAS OpRisk VaR Donald Erdman April 11, 2005.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.
Chapter 11: Project Risk Management
N By: Md Rezaul Huda Reza n
OSMA2003 Center for Reliability Engineering 1 Integrating Software into PRA Presented by C. Smidts Center for Reliability Engineering University of Maryland.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
CRESCENDO Full virtuality in design and product development within the extended enterprise Naples, 28 Nov
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Introduction to Software Engineering ECSE-321 Unit 4 – Project Management 10/19/2015Introduction to Software Engineering – ECSE321Unit 4 – Project Management/1.
National Aeronautics and Space Administration From Determinism to “Probabilism” Changing our mindsets, or why PTC isn’t an easy sell - yet.
West Virginia University Towards Practical Software Reliability Assessment for IV&V Projects B. Cukic, E. Gunel, H. Singh, V. Cortellessa Department of.
AMERICA’S ARMY: THE STRENGTH OF THE NATION Mort Anvari 1 Cost Risk and Uncertainty Analysis MORS Special Meeting | September.
J1879 Robustness Validation Hand Book A Joint SAE, ZVEI, JSAE, AEC Automotive Electronics Robustness Validation Plan The current qualification and verification.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
1 DISTRIBUTION A. Approved for Public Release; Distribution Unlimited. 88ABW , 23 May Integrity  Service  Excellence ADT 101: Introduction.
Managing Rotorcraft Safety During Frequently Performed Unique Missions September 28, 2005 AHS International Helicopter Safety Symposium 2005 Philip G.
Chap. 5 Building Valid, Credible, and Appropriately Detailed Simulation Models.
1 Mission Discussion & Project Reviews 祝飛鴻 10/14/93.
5-1 ANSYS, Inc. Proprietary © 2009 ANSYS, Inc. All rights reserved. May 28, 2009 Inventory # Chapter 5 Six Sigma.
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
SOFTWARE PROJECT MANAGEMENT
NASA/Air Force Cost Model presented by Keith Smith Science Applications International Corporation 2002 SCEA National Conference June
Futron Corporation 400 Virginia Avenue,SW Suite 340 Washington, DC Phone Fax NASA PRA Practices.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin 8-1 Chapter Eight Audit Sampling: An Overview and Application.
Learning Simio Chapter 10 Analyzing Input Data
Center for Reliability Engineering Integrating Software into PRA B. Li, M. Li, A. Sinha, Y. Wei, C. Smidts Presented by Bin Li Center for Reliability Engineering.
Pavan Rajagopal, GeoControl Systems James B. Dabney, UHCL Gary Barber, GeoControl Systems 1Spacecraft FSW Workshop 2015.
Lecture 2 System Development Lifecycles. Building a house Definition phase Analysis phase Design phase Programming phase System Test phase Acceptance.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Robust Design: The Future of Engineering Analysis in Design
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Probabilistic Risk Assessment and Conceptual Design Bryan C Fuqua – SAIC Diana DeMott – SAIC
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Equipment Life Optimization Program (ELOP) Doug Hilleman February 10, 2011.
William Prosser April 15, Introduction to Probability of Detection (POD) for Nondestructive Evaluation (NDE) This briefing is for status only and.
Building Valid, Credible & Appropriately Detailed Simulation Models
Review on Test-Based Approach of Software Reliability November 22 nd, 2010 Nuclear I&C and Information Engineering LabKAIST Bo Gyung Kim.
Failure Modes, Effects and Criticality Analysis
Software Design and Development Development Methodoligies Computing Science.
1 ME Spring 2015 Systems Engineering, Part II Session 8 5 February 2015 Mr. Larry Hopp, CPL © Copyright 2013.
19-1 Lesson 19: Reliability of Nondestructive Evaluation (NDE)
DATA ANALYSIS: THEORY AND PRACTICE by Vicki M. Bier.
Wind Composite Services Group/WindCom
PRA: Validation versus Participation in Risk Analysis PRA as a Risk Informed Decision Making Tool Richard T. Banke– SAIC
Enabling Team Supervisory Control for Teams of Unmanned Vehicles
Project COMP10: Designing for Blade Aeromechanical Integrity
of Heritage and New Hardware For Launch Vehicle Reliability Models
ACCURACY IN PERCENTILES
Chapter 10 Verification and Validation of Simulation Models
Reliability Engineering Applications and Case Studies
Knowing When to Stop: An Examination of Methods to Minimize the False Negative Risk of Automated Abort Triggers RAM XI Training Summit October 2018 Patrick.
Jeff Dutton/NASA COR August 26, 2019
Presentation transcript:

1 An Overview of MSFC Quantitative Risk Assessment (QRA) Practices Fayssal Safie/MSFC October 25, 2000

2 Agenda Quantitative Risk Assessment System (QRAS) Other PRA-Related Practices Reliability Prediction Probabilistic Structural Analysis Similarity Analysis Reliability Demonstration

3 MSFC Propulsion Elements QRAS

4 QRAS Background Space Shuttle probabilistic risk assessment (PRA) studies Space Shuttle PRA for Galileo mission (PRC) Galileo PRA update (SAIC) Space Shuttle PRA (SAIC) 1997/ Space Shuttle PRA (NASA/Code Q)

5 QRAS Background (cont’d) 1997/2000 NASA QRA study In July 1996, the NASA Administrator directed NASA Headquarters to develop a software system to quantitatively assess the overall shuttle risk and serve as a tool to estimate risk changes due to proposed shuttle upgrades. At the request of NASA Headquarters, MSFC and JSC, supported by their prime contractors, are modeling their respective elements. The software system, called QRAS (Quantitative Risk Assessment System), is designed and developed by NASA Headquarters Code Q.

6 Develop a quantitative risk model to: Assess the reliability/risk of the overall shuttle vehicle, its major elements, and their components Evaluate risk reduction due to proposed shuttle upgrades Rank shuttle failure modes Perform trade studies/sensitivity analyses QRAS Objectives

7 QRAS Model Requirements Model builds on work done by SAIC Shuttle PRA model. Model is modular, reflecting shuttle modularity with its discrete elements, subsystems, and components (flexible to accommodate upgraded components and additional details). Model must be most detailed in high risk areas to allow sensitivity analysis and trade studies to be performed. Model/tool must be user-friendly and easily updateable. Model must be capable of identifying, quantifying, and prioritizing the major risk contributors. Model must support NASA decision-making process (evaluating shuttle upgrades and supporting flight issues).

8 QRAS Modeling Approach Space Shuttle ORBITER MCC HEX HPFTPLPFTP Products 1. Space Shuttle Risk 2. Element Risk 3. Subsystem Risk 4. Risk Ranking 5. Sensitivity Analysis etc.. Turbine Blade Porosity Turn- Around Duct Fail. Housing Retaining Lug Fail. FLIGHT/TEST DATA PROBABILISTIC STRUCTURAL MODELS SIMILARITY ANALYSIS ENGINEERING JUDGMENT System Hierarchy Turbine Blade Porosity Mission Success Inspection Not Effective Porosity Present in Critical Location ET SSME ISRB UNCERTAINTY DISTRIBUTION FOR LOV DUE TO TURBINE BLADE POROSITY Event Tree RISK AGGREGATION OF BASIC EVENTS Functional Event Sequence Diagram (FESD) End State or Transfer Porosity Present in Critical Location Leads to Crack in <4300 sec Scenario Number 1LOV 3 MS 4 2 Turbine Blade Porosity Inspection Not Effective Porosity Present in Critical Location QUANTIFICATION OF FESD INITIATING & PIVOTAL EVENTS UNCERTAINTY DISTRIBUTION FOR EVENT PROBABILITY EVENT PROBABILITY DISTRIBUTION BASIC/INITIATING EVENTS Porosity in Critical Location Leads to Crack in <4300 sec Mission Success Mission Success Loss of Vehicle (LOV) Blade Failure Mission Success Blade Failure 5MS

9 QRAS MSFC Team Participants MSFC Safety & Mission Assurance (S&MA) Chief engineer & project offices Engineering Prime contractors Reliability engineering Design & manufacturing engineering Hernandez Engineering Inc. (HEI) Reliability engineering and simulation

10 QRAS Databases Problem Reporting and Corrective Action (PRACA) Automated Configuration data Tracking System (ACTS) Logbooks Engineering data/analyses Generic data Lessons learned SAIC study

11 QRAS Propulsion Element Models Significant Observations Strength: QRAS modeling effort has contributed towards drawing management attention in using statistical and probabilistic information in the decision making process. Event Sequence Diagram (ESD) provides a better understanding of the failure mode risk and an excellent way to address risk mitigation. Data contained in the individual ESD packages are an excellent source of reference material and lessons learned. QRAS models constitute: The best source of failure rate data for the shuttle program to evaluate upgrades. The best source of information to understand the risk mitigation in place. The best source to understand the physics of failure for critical failure modes/events.

12 Considerations: QRAS is a large scale QRA study which is very complex and require extensive knowledge of the system, a large amount of data, and extensive modeling. Use of engineering judgment introduces significant amount of uncertainty. Quantification methods, in most cases, are not robust. Overlooking one piece of data may dramatically change the probability of loss of vehicle. QRAS Propulsion Element Models Significant Observations (cont’d)

13 Considerations (cont’d): Modeling of human error/process error is a big challenge. Human error/process error has been incorporated implicitly where flight and test data exist. For structural failures which are modeled using design information, the human error/process error has been incorporated explicitly using placeholders based on historical data. The QRAS modeling effort has shown that developing explicit models for the human error/process error is extremely difficult because of lack of adequate data. QRAS Propulsion Element Models Significant Observations (cont’d)

14 Considerations (cont’d): QRAS/PRA failure probabilities are imbalanced Some failure probabilities are derived using mainly design information ( P&W Turbopumps), while others are derived using mainly test and flight data (RKDN SSME hardware). Generic data are also used in other cases. Some failure probabilities are derived using limited data (solid propulsion elements), while others are derived based on a lot of data (liquid propulsion elements). Difficult to model common cause failures Incomplete interface models QRAS Propulsion Element Models Significant Observations (cont’d)

15 QRAS Conclusions Following a well defined and documented systematic procedure, involving the appropriate disciplines (reliability, design, and manufacturing engineering), and using the appropriate data are the key elements for a successful QRA study. Information derived from QRA studies are most accurate and useful at lower levels (within components and failure modes). QRAS tool is the best QRA tool available to support the shuttle program management decisions.

16 Other PRA-Related Practices Reliability Prediction

17 Reliability Prediction Reliability prediction techniques are dependent on the degree of the design definition and the availability of historical data. Two commonly used techniques are: Probabilistic design techniques: Reliability is predicted using engineering failure models. Similarity analysis techniques: Reliability of a new design is predicted using reliability of similar parts.

18 Reliability Prediction Probabilistic Structural Analysis It is a tool to probabilistically characterize the design and analyze its reliability using engineering failure models. It is a tool to evaluate the expected reliability of a part given the structural capability and the expected operating environment. It is used when failure data is not available and the design is characterized by complex geometry or is sensitive to loads, material properties, and environments.

19 FRACTURE LOCATION During rig testing the AT/HPFTP Bearing experienced several cracked races. Summary of 440C race fractures / tests: 3 of 4 Fractured Reliability Prediction Probabilistic Structural Analysis (cont’d) Turbo-Pump Bearing Example

20 OBJECTIVE: Predict probability of inner race over-stress, under the conditions experienced in the test rig, and estimate the effect of manufacturing stresses on the fracture probability. Stress Allowable Load Failure Region Reliability Prediction Probabilistic Structural Analysis (cont’d) Turbo-Pump Bearing Example

21 Conditions Using rig fits and clearances Crack size data from actual cut-ups Stresses associated with manufacturing (ideal) Materials properties and their variations Failure mode being analyzed is over-stress Reliability Prediction Probabilistic Structural Analysis (cont’d) Turbo-Pump Bearing Example

22 HPFTP Roller Bearing Inner Race - Model Flow Randomly select values for inner race material properties  Randomly select values for shaft and sleeve material properties  Tolerance fits of rig test bearing Inner race hoop stress contribution at given conditions Shaft and sleeve hoop stress contribution at given conditions. Total hoop stress Stress due to Manufacturing Stress > Allowable Load Iterate and compute Failure Probability Variation in: o Fracture Toughness o Yield Strength o No. of Cracks o Crack Depth o Crack Length Compute Allowable Load for each crack Compute Allowable Load (worst crack) Reliability Prediction Probabilistic Structural Analysis (cont’d) Turbo-Pump Bearing Example

23 RESULTS - FAILURE RATES At Test 3 of 4 failed --- In 15+ tests never had a through ring fracture Race Configuration 440C w/ actual manufacturing stresses (ie ideal + abusive grinding) 440C w/no manf. stresses 440C w/ideal manf. stresses 9310 w/ ideal manf stresses Probabilistic Structural Analysis 68,000 fail/100k firings 1,500 fail/100k firings 27,000 fail/100k firings 10 fail/100k firings It is estimated that 50% of the through ring fractures would result in an engine shutdown. The shutdown 9310 HPFTP Roller Bearing Inner Race Failure Rate is then: 0.50 X 10/100k = 5 fail/100k firings Reliability Prediction Probabilistic Structural Analysis (cont’d) Turbo-Pump Bearing Example

24 Reliability Prediction Similarity Analysis Similarity Analysis is a technique for predicting the reliability of a new design based on historical data of similar designs (heritage hardware). Failure rates derived from historical data are modified to reflect the design and environment of the new hardware. Similarity Analysis is best performed at the lowest level possible, where more data is available and more appropriate judgment is made.

25 Reliability Prediction Similarity Analysis (cont’d) Fuel Turbo Pump Example Assume a Fuel Turbo Pump (FTP) has a historical failure rate of: 50 per 100k firings Assume also the failure mode break down is: Then the Cracked/Fractured Failure rate is:.35 X 50 = 17.5/100k firings Cracked/Fractured Blades Turbine bearing Failure Pump bearing Failure Impeller Failure Turbine Seal Failure 100% 35% 25% 20% 10%

26 If the failure causes for Cracked/Fractured are determined to be: Then the Thermal Stress Failure Rate is: 0.57 X 17.5 = 10/100k firings 100% Reliability Prediction Similarity Analysis (cont’d) Fuel Turbo Pump Example

27 Failure Rate Adjustments established through: Test Results Preliminary Analyses Integrated Product Team (IPT) Input Address "high hitters" - Using Thermal Stress failure rate of 10.0/100k firing Design changes to improve reliability Cum Percent Failure Rate Improvement Reduction Lower Operating Temperatures 20% 2.00 (Test) Hollow Blades 30% (additional) 4.40 (Analysis, Expert Opinion) Material Change 20% (additional) 5.52 (Analysis) Reliability Prediction Similarity Analysis (cont’d) Fuel Turbo Pump Example

28 If no other changes are made, the FTP predicted reliability is then: = / 100k firings Reliability Prediction Similarity Analysis (cont’d) Fuel Turbo Pump Example

29 Other PRA-Related Practices Reliability Demonstration

30 Reliability Demonstration Reliability Demonstration is a reliability estimation method that primarily uses test data (objective data) to calculate demonstrated reliability with some statistical confidence. Some commonly used models and techniques for reliability demonstration include Binomial, Exponential, and Weibull models. Reliability growth techniques, such as the U.S. Army Material Systems Analysis Activity (AMSAA) and Duane models can also be used to calculate demonstrated reliability.

31 SFR Criteria is an optimization tool based on the demonstrated reliability of SSME hardware. SFR is used by the SSME Program as a quantitative probabilistic risk management tool for SSME critical hardware. SFR Criteria: Extensive fleet hot-fire experience No failures or MR history No periodic inspection Use discrete optimization for life limit determination Extend life limit up to 50% fleet leader but not to exceed the minimum run time of the six leading samples New life limit should not be less than 25% of the fleet leader Advantages include: Maximize hardware usage Use of all operational history Reliability Demonstration Example SSME Single Flight Reliability (SFR) Criteria

32 Reliability Demonstration Example SSME Single Flight Reliability (SFR) Criteria – Powerhead Assembly Example Serial Number Seconds (Partial Listing) Beta = 2.08 Powerhead Assembly LRU Code A050 25% F/L – % F/L