Rust.randy

16
Sensitive But Unclassified– For NASA Internal Use Only "Requirements Driven versus Risk Informed Design" "Requirements Driven versus Risk Informed Design" Randy Rust SR&QA Lead, Altair Project Johnson Space Center Randy Rust SR&QA Lead, Altair Project Johnson Space Center Requirements Driven versus Risk Informed Design

Transcript of Rust.randy

Page 1: Rust.randy

Sensitive But Unclassified– For NASA Internal Use Only

"Requirements Driven versus Risk Informed Design""Requirements Driven versus Risk Informed Design"

Randy RustSR&QA Lead,Altair ProjectJohnson Space Center

Randy RustSR&QA Lead,Altair ProjectJohnson Space Center

Requirements Driven versus Risk Informed Design

Page 2: Rust.randy

2

Heavy LiftLaunch Vehicle

Crew Launch Vehicle

Earth DepartureStage

Crew Exploration Vehicle

LunarLander

Transportation Components of Program Constellation

Page 3: Rust.randy

3

Typical Lunar Reference Mission

Ascent Stage Expended

ED

S, L

ande

r

CE

V

Earth Departure Stage Expended

Lander Performs LOI100 km Low Lunar Orbit

Vehicles are not to scale.

Low Earth Orbit

Service Module Expended

MOONMOON

EARTHEARTH

Direct EntryLand Landing

Page 4: Rust.randy

4

Altair Lunar Lander

♦ 4 crew to and from the surface • Seven days on the surface• Lunar outpost crew rotation

♦ Global access capability♦ Anytime return to Earth♦ Capability to land 14 to 17

metric tons of dedicated cargo ♦ Airlock for surface activities♦ Descent stage:

• Liquid oxygen / liquid hydrogen propulsion

♦ Ascent stage:• Hypergolic Propellants or Liquid

oxygen/methane

Page 5: Rust.randy

5

Design Approach

♦ Project examined the multitude of concepts developed in the post-ESAS era, took lessons learned and began to develop a real design.

♦ Altair took a true risk informed design approach, starting with a minimum functionality design and adding from there to reduce risk.

♦ Lunar Design Analysis Cycle (LDAC) 1 developed a “minimum functional”vehicle.• “Minimum Functionality” is a design philosophy that begins with a vehicle that will perform the

mission, and no more than that• Does not consider contingencies• Does not have added redundancy (“single string” approach)• Provides early, critical insight into the overall viability of the end-to-end architecture• Provides a starting point to make informed cost/risk trades and consciously buy down risk• A “Minimum Functionality” vehicle is NOT a design that would ever be contemplated as a

“flyable” design!

♦ LDAC-2 determined the most significant contributors to loss of crew (LOC) and the optimum cost/risk trades to reduce those risks.

♦ LDAC-3 (current LDAC) is assessing biggest contributors to loss of mission (LOM) and optimum cost/risk trades to reduce those risks.

♦ Goal of the design process is to do enough real design work to understand and develop the requirements for SRR.

Page 6: Rust.randy

6

Upgraded Flyable VehicleClose the gap with the CARD

Safety / Reliability Upgrades (LOC)

Jun 07 Dec 07 Mar 08 Jun 08 Sept 08 Dec 08 Mar 09Sept 07

Lander Design Analysis Cycle 1

Minimum Functional Vehicle

LDAC-2

Upgraded Flyable VehicleAdditional safety, reliability and functionality (LOM); Global access

LDAC-1

LDAC-3

CxP LCCR

LDAC-4In-H

ouse

Des

ign

Effo

rt

Jun 09 Sept 09

♦ Lander design process kicked off with Design Analysis Cycle 1♦ Took a “minimal functionality” approach for LDAC-1♦ LDAC-1 completed November 2007

Requirements Development

LDAC-X

Page 7: Rust.randy

7

New Philosophy Needed

♦ For previous programs and projects, the general thought was to apply a failure tolerance philosophy • One failure tolerant for loss of mission failures, and two failure tolerant to prevent loss of

crew.

♦ For the Lander, where mass is extremely critical, this philosophy alone will not yield an optimal design solution.• There are ways other than redundancy to improve reliability and still reduce the risk of loss

of crew.

♦ We needed a new philosophy where we could develop a spacecraft that provides a required level of safety for the crew and is reliable enough to perform the mission.• Defined the minimum set of functions necessary to accomplish the mission objectives.

• Made it work. Created the simplest & lowest mass conceptual design of the contemplated system.

• Consistent with NESC RP-06-108, Design, Development, Test, and Evaluation (DDT&E) Considerations for Safe and Reliable Human Rated Spacecraft Systems)

Page 8: Rust.randy

8

LDAC-1 Starting Point

♦ ‘Hard’ Requirements• 4 Crew• 7 Day Sortie• 210 Day Outpost• Airlock (implemented on sortie mission only)• CxP transportation architecture

− 8.4 meter shroud, TLI Loads, Lander performs LOI burn, CEV IRD, etc• Control Mass

− Total Lander mass at TLI for crewed missions: 45,000 kg− Total Lander mass at TLI for cargo missions: 53,600 kg

♦ 3 DRMs with Mission Timelines and Functional Allocations• Sortie Mission to South Pole

− 4 Crew / 7 Days on Surface / No support from surface assets− No restrictions on ‘when’ (accommodating eclipse periods)

• Outpost Mission to South Pole− 4 Crew with Cargo Element (LAT Campaign option 2)− Outpost provides habitation on surface (down and out)− 210 Days with surface support (power)

• Cargo Mission to South Pole− Short duration, large payload

♦ One Lander design, with variants (kits) if required for the different DRMs

Page 9: Rust.randy

9

Structures and Mechanisms

Propulsion

Thermal Control

Life Support

Other

Propellant

Non-Propellant Fluids

Manager's Reserve

Mass Available for PayloadAvionics Power

Results of LDAC1

Outpost Variant45,000 kg

Descent ModuleAscent Module

Sortie Variant45,000 kg

Descent ModuleAscent Module

Airlock

Cargo Variant53,600 kg

Descent ModuleCargo on Upper Deck

Sortie Mission Lander Mass distribution

Page 10: Rust.randy

10

Upgraded Flyable VehicleClose the gap with the CARD

Safety / Reliability Upgrades (LOC)

Jun 07 Dec 07 Mar 08 Jun 08 Sept 08 Dec 08 Mar 09Sept 07

Lander Design Analysis Cycle 2

Minimum Functional Vehicle

LDAC-2

Upgraded Flyable VehicleAdditional safety, reliability and functionality (LOM); Global access

LDAC-1

LDAC-3

CxP LCCR

LDAC-4In-H

ouse

Des

ign

Effo

rt

Jun 09 Sept 09

Requirements Development

LDAC-X

♦ LDAC2's focus was to buy down the Loss of Crew (LOC) safety risks in the point of departure design.

♦ LDAC2 completion date was May 2008.

Page 11: Rust.randy

11

Overview of LDAC-2 risk buy back process

Vehicle Top Risks Divided into 33 Tasks

System Teams Develop Options &

Safety estimates LOC For Each Option

DAC1Baseline LOC

Task Options ChosenBy Mass ∆ and LOC ∆

Task’s Option LOC Rolled Up to System Level

System Level Rolled Upto Vehicle Level

DAC2Baseline LOC

Page 12: Rust.randy

12

Example Risk Buyback Task: #33, Improve Comm System Reliability

♦ Purpose: Improve Comm System Reliability to be able to update the state vector

♦ Brief description of problem addressed by your task• There are currently 6 single point failures that could cause loss of the state vector

input to the bus to the flight computer. This study identifies several options increase communications reliability.

• Inability to obtain state vector results in LOC for ascent. Proposed Solutions:

• (A) Redundancy with 2 SDRs (instead of XPDR’s), cross-strapped to single diplexer/antenna pair (common EVA comm)

• (B1) PA/LNA Bypass (with switches)• (B2) PA/LNA Bypass (with cables - IFM)• (C) Redundancy with 1 XPDR & 1 Dissimilar comm system• (D) Redundancy with 2 XPDRs, cross-strapped to single diplexer/antenna

pair• (E1) Full Redundancy with 2 SDRs strings (common EVA comm)• (E2) Full Redundancy with 2 XPDRs strings• (E3) Full Redundancy, 1 XPDR & 1 SDR strings (common EVA comm)

Page 13: Rust.randy

13

Example Risk Buyback Task: #33, Improve Comm System ReliabilityGraphical Summary of Options

Top Contenders:

(C)

(B2)(E3) (E2)

(D)(E1)

(Baseline)

Page 14: Rust.randy

14

Another Example: Active Thermal

L DAC 2  T hermal S ys tem  Options  (Delta  Mas s  Vs . L OC )

1.00E ‐03

1.00E ‐02

1.00E ‐01

0 100 200 300 400 500 600 700

De lta  Ma ss   (K g .)

Probab

ility

B as eline  LDAC 1_delta

Option A1 dual  internal  loop

Option A1f dual  internal  loop

Option B 1 dual c ritic alc omponents  

Option C 1 emergenc y   loop 

Option C 1f emergenc y   loop 

Option D1 s ublimator drivencoldplate  

Option E 1  fully  redundant  loops  

Option E 1fh  fully  redundant  loops  

Option E 1f  fully  redundant  loops  

Option F 1 s ingle   loops  withredundant c omponents

Option G 1 mix  and match 

Option G 1f mix  and match 

(Unallocated Differential vs. LOC)

Unallocated Differential (kg)

Page 15: Rust.randy

15

LDAC-2 Overview

♦ The initial Lander Design and Analysis Cycles (May-November 2007) created a “minimal functionality” lander design that serves as a baseline upon which to add safety, reliability and functionality back into the design with known changes to performance, cost and risk.

♦ LDAC-2 completed in May 2008. Goal was to “buy down” Loss of Crew (LOC) risks.

♦ “Spent” approximately 1.3 t to buy down loss of crew (LOC) risks.

♦ “Spent” an additional 680kg on design maturity.

P a y lo a d M a s s to S u rfa c e - C re w S o rtie(45 .0 m t c ontro l m as s ; perfo rm anc e re flec ts M G A and P M R )

500 500

3651

1671

500 500

0

500

1000

1500

2000

2500

3000

3500

4000

LD A C -111/07

LD A C -25/08

D A C /D a te

kg

CA RD s pecpay load mas s

Bottoms -upDA C pay loadmas s

Parametr ic f u llyf unc tiona lpay load mas s

L O C

0 .0 0 4 0 .0 0 4

0 .1 6 6

0 .0 0 5

-0 .0 3

0 .0 2

0 .0 7

0 .1 2

0 .1 7

L D AC -1 1 1 /0 7 L D AC 2 * 0 5 /0 8

LDAC

PLO

C C AR D S p e c

L D AC P L O C

* Note: Based on simplified models that address identified risks.

Page 16: Rust.randy

16

Lessons Learned During Risk Buy-down

♦ Full redundancy was usually heaviest, frequently NOT most effective for improving LOC• Conclusion may be different for LOM

♦ Quantitative risk tool was necessary to inform good design decisions• Always necessary to correlate engineering judgment with tool results• Tool forces team to reconsider• However, cannot rely solely on tool results. Must be able to technically explain

decision.♦ A risk tool the designers can interact with is a significant aid – improves

tool and design• e.g., when a result did not correlate with engineering experience, designers could

easily understand model in tool. Sometimes changed model and sometimes did not.♦ Designing for minimum risk

• results in lower weight design• is much harder and time consuming than simply adding redundancy• But, design team ends up much more intelligent on risk and design

drivers♦ Design for Minimum Risk is the way to go if you are trying to build a smart

design team