NASA-LLIS-1087
Lessons Learned - Plan Timely Implementation of Backups In Case Breakthrough Technologies Fail to Meet Readiness Gates - 1998
Year: 2001
Abstract: Abstract:
Although the Deep Space 1 mission exceeded its overall technology demonstration objectives, certain important technologies under development never achieved flight readiness.
Develop a project implementation plan with preplanned alternatives that addresses technology readiness and risk mitigation. Cease development when technology readiness gates for critical technologies are not met and implement preplanned alternatives. Avoid a spacecraft architecture where one new technology relies on another in order to demonstrate them in-flight.
Although the Deep Space 1 mission exceeded its overall technology demonstration objectives, certain important technologies under development never achieved flight readiness.
Develop a project implementation plan with preplanned alternatives that addresses technology readiness and risk mitigation. Cease development when technology readiness gates for critical technologies are not met and implement preplanned alternatives. Avoid a spacecraft architecture where one new technology relies on another in order to demonstrate them in-flight.
Subject: Autonomous Navigation
Show full item record
contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
date accessioned | 2017-09-04T18:39:18Z | |
date available | 2017-09-04T18:39:18Z | |
date copyright | 37231 | |
date issued | 2001 | |
identifier other | JRUEQCAAAAAAAAAA.pdf | |
identifier uri | http://yse.yabesh.ir/std;query=authoCA5893FD081D49A96159DD6EFDEC014A/handle/yse/220980 | |
description abstract | Abstract: Although the Deep Space 1 mission exceeded its overall technology demonstration objectives, certain important technologies under development never achieved flight readiness. Develop a project implementation plan with preplanned alternatives that addresses technology readiness and risk mitigation. Cease development when technology readiness gates for critical technologies are not met and implement preplanned alternatives. Avoid a spacecraft architecture where one new technology relies on another in order to demonstrate them in-flight. | |
language | English | |
title | NASA-LLIS-1087 | num |
title | Lessons Learned - Plan Timely Implementation of Backups In Case Breakthrough Technologies Fail to Meet Readiness Gates - 1998 | en |
type | standard | |
page | 3 | |
status | Active | |
tree | NASA - National Aeronautics and Space Administration (NASA):;2001 | |
contenttype | fulltext | |
subject keywords | Autonomous Navigation | |
subject keywords | Flight Equipment | |
subject keywords | Flight Qualification | |
subject keywords | Hardware | |
subject keywords | Management and Planning | |
subject keywords | Policy & Planning | |
subject keywords | Risk Management/Assessment | |
subject keywords | Safety & Mission Assurance | |
subject keywords | Spacecraft | |
subject keywords | Technology Plan | |
subject keywords | Technology Readiness Level | |
subject keywords | Test & Verification |