Search NASA⌕ Search

SEARCH · Search NASA

Results for “programmatic”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,243 records · Page 69

Environmental Effects on ISS Materials Aging (1998 to 2008)

The performance of ISS spacecraft materials and systems on prolonged exposure to the low- Earth orbit (LEO) space flight are reported in this paper. In-flight data, flight crew observations, and the results of ground-based test and analysis directly supporting programmatic and operational decision-making are described. The space flight environments definitions (both natural and induced) used for ISS design, material selection, and verification testing are shown, in most cases, to be more severe than the actual flight environment accounting, in part, for the outstanding performance of ISS as a long mission duration spacecraft. No significant ISS material or system failures have been attributed to spacecraft-environments interactions. Nonetheless, ISS materials and systems performance data is contributing to our understanding of spacecraft material interactions with the spaceflight environment so as to reduce cost and risk for future spaceflight projects and programs. Orbital inclination (51.6 deg) and altitude (nominally near 360 km) determine the set of natural environment factors affecting the functional life of materials and systems on ISS. ISS operates in an electrically conducting environment (the F2 region of Earth s ionosphere) with well-defined fluxes of atomic oxygen, other charged and neutral ionospheric plasma species, solar UV, VUV, and x-ray radiation as well as galactic cosmic rays, trapped radiation, and solar cosmic rays. The LEO micrometeoroid and orbital debris environment is an especially important determinant of spacecraft design and operations. The magnitude of several environmental factors varies dramatically with latitude and longitude as ISS orbits the Earth. The high latitude orbital environment also exposes ISS to higher fluences of trapped energetic electrons, auroral electrons, solar cosmic rays, and galactic cosmic rays than would be the case in lower inclination orbits, largely as a result of the overall shape and magnitude of the geomagnetic field. As a result, ISS exposure to many environmental factors can vary dramatically along a particular orbital ground track, and from one ground track to the next, during any 24-hour period. The induced environment results from ISS interactions with the natural environment as well as environmental factors produced by ISS itself and visiting vehicles fleet. Examples include ram-wake effects, hypergolic thruster plume impingement, materials out-gassing, venting and dumping of fluids, and specific photovoltaic (PV) power system interactions with the ionospheric plasma (7-11). Vehicle size (L) and velocity (V), combined with the magnitude and direction of the geomagnetic field (B) produce operationally significant magnetic induction voltages (VxB.L) in ISS conducting structure during flight through high latitudes (> +45deg) during each orbit. Finally, an induced ionizing radiation environment is produced by cosmic ray interaction with the relatively thick ISS structure and shielding materials. The intent of this review article is, therefore, to provide a summary of selected aspects and elements of the ISS vehicle with regard to LEO space environment effects, associated with the much larger and more complicated vehicle that ISS has become since 1998, but also with an eye towards performance life extension to the year 2016 and beyond.

Alred, John↗

PrimeSupplier Cross-Program Impact Analysis and Supplier Stability Indicator Simulation Model

PrimeSupplier, a supplier cross-program and element-impact simulation model, with supplier solvency indicator (SSI), has been developed so that the shuttle program can see early indicators of supplier and product line stability, while identifying the various elements and/or programs that have a particular supplier or product designed into the system. The model calculates two categories of benchmarks to determine the SSI, with one category focusing on agency programmatic data and the other focusing on a supplier's financial liquidity. PrimeSupplier was developed to help NASA smoothly transition design, manufacturing, and repair operations from the Shuttle program to the Constellation program, without disruption in the industrial supply base.

Calluzzi, Michael↗

From LEO, to the Moon and then Mars: Developing a Global Strategy for Exploration Risk Reduction

Most nations currently involved in human spaceflight, or with such ambitions, believe that space exploration will capture the imagination of our youth resulting in future engineers and scientists, advance technologies which will improve life on earth, increase the knowledge of our solar system, and strengthen bonds and relationships across the globe. The Global Exploration Strategy, published in 2007 by 14 space agencies, eloquently makes this case and presents a vision for space exploration. It argues that in order for space exploration to be sustainable, nations must work together to address the challenges and share the burden of costs. This paper will examine Mars mission scenarios developed by NASA, ESA and other agencies and show resulting conclusions regarding key challenges, needed technologies and associated mission risks. It will discuss the importance of using the International Space Station as a platform for exploration risk reduction and how the global exploration community will develop lunar exploration elements and architectures that enable the long term goal of human missions to Mars. The International Space Station (ISS) is a critical first step both from a technology and capability demonstration point of view, but also from a partnership point of view. There is much work that can be done in low earth orbit for exploration risk reduction. As the current "outpost at the edge of the frontier", the ISS is a place where we can demonstrate certain technologies and capabilities that will substantially reduce the risk of deploying an outpost on the lunar surface and Mars mission scenarios. The ISS partnership is strong and has fulfilled mission needs. Likewise, the partnerships we build on the moon will provide a strong foundation for establishing partnerships for the human Mars missions. On the moon, we build a permanently manned outpost and deploy technologies and capabilities to allow humans to stay for long periods of time. The moon is interesting from a scientific point of view, but it is extremely important for development and demonstration the technologies and capabilities needed for human missions to Mars. This paper will show the logic and strategy for addressing technological, operational and programmatic challenges by using low earth orbit and lunar missions to enable the long term goal of exploration of our solar system.

Laurini, Kathleen C.↗

Problems Encountered During the Recertification of the GLORY Solar Array Dual Axis Gimbal Drive Actuators

The Glory observatory is the current incarnation of the Vegetation Canopy Lidar (VCL) mission spacecraft bus. The VCL spacecraft bus, having been cancelled for programmatic reasons in 2000, was nearly integrated when it was put into storage for possible future use. The Glory mission was a suitable candidate for using this spacecraft and in 2006 an effort to recertify the two axis solar array gimbal drive after its extended storage was begun. What was expected to be a simple performance validation of the two dual axis gimbal stepper motors became a serious test, diagnosis and repair task once questions arose on the flight worthiness of the hardware. A significant test program logic flow was developed which identified decisions that could be made based on the results of individual recertification tests. Without disassembling the bi-axial gimbals, beginning with stepper motor threshold voltage measurements and relating these to powered drive torque measurements, both performed at the spacecraft integrator s facility, a confusing picture of the health of the actuators came to light. Tests at the gimbal assembly level and tests of the disassembled actuators were performed by the manufacturer to validate our results and torque discrepancies were noted. Further disassembly to the component level of the actuator revealed the source of the torque loss.

Saltzman, Marc↗

Integrated Risk and Knowledge Management Program -- IRKM-P

The NASA Exploration Systems Mission Directorate (ESMD) IRKM-P tightly couples risk management and knowledge management processes and tools to produce an effective "modern" work environment. IRKM-P objectives include: (1) to learn lessons from past and current programs (Apollo, Space Shuttle, and the International Space Station); (2) to generate and share new engineering design, operations, and management best practices through preexisting Continuous Risk Management (CRM) procedures and knowledge-management practices; and (3) to infuse those lessons and best practices into current activities. The conceptual framework of the IRKM-P is based on the assumption that risks highlight potential knowledge gaps that might be mitigated through one or more knowledge management practices or artifacts. These same risks also serve as cues for collection of knowledge particularly, knowledge of technical or programmatic challenges that might recur.

Lengyel, David M.↗

Approach for Mitigating Pressure Garment Design Risks in a Mobile Lunar Surface Systems Architecture

The stated goals of the 2004 Vision for Space Exploration focus on establishing a human presence throughout the solar system beginning with the establishment of a permanent human presence on the Moon. However, the precise objectives to be accomplished on the lunar surface and the optimal system architecture to achieve those objectives have been a topic of much debate since the inception of the Constellation Program. There are two basic styles of system architectures being traded at the Programmatic level: a traditional large outpost that would focus on techniques for survival off our home planet and a greater depth of exploration within one area, or a mobile approach- akin to a series of nomadic camps- that would allow greater breadth of exploration opportunities. The traditional outpost philosophy is well within the understood pressure garment design space with respect to developing interfaces and operational life cycle models. The mobile outpost, however, combines many unknowns with respect to pressure garment performance and reliability that could dramatically affect the cost and schedule risks associated with the Constellation space suit system. This paper provides an overview of the concepts being traded for a mobile architecture from the operations and hardware implementation perspective, describes the primary risks to the Constellation pressure garment associated with each of the concepts, and summarizes the approach necessary to quantify the pressure garment design risks to enable the Constellation Program to make informed decisions when deciding on an overall lunar surface systems architecture.

Aitchison, Lindsay↗

Evaluating Failures and Near Misses in Human Spaceflight History for Lessons for Future Human Spaceflight

There have been a number of studies done in the past drawn on lessons learned with regard to human loss-of-life events. Generally, the systemic causes and proximate causes for fatal events have both been examined in considerable detail. However, an examination of near-fatal accidents and failures that narrowly missed being fatal could be equally useful, not only in detecting causes, both proximate and systemic, but also for determining what factors averted disaster, what design decisions and/or operator actions prevented catastrophe. Additionally, review of risk factors for upcoming or future programs will often look at trending statistics, generally focusing on failure/success statistics. Unfortunately, doing so can give a skewed or misleading view of past reliability or a reliability that cannot be presumed to apply to a new program. One reason for this might be that failure/success criteria aren't the same across programs, but also that apparent success can hide systemic faults that, under other circumstances, can be fatal to a program with different parameters. A program with a number of near misses can look more reliable than a consistently healthy program with a single out-of-family failure and provide very misleading data if it is not examined in detail. This is particularly true for a manned space program where failure/success includes more than making a particular orbit. Augmenting reliability evaluations with this near miss data can provide insight and expand on the limitations of a strictly pass/fail evaluation. Even more importantly, a thorough understanding of these near miss events can identify conditions that prevented fatalities. Those conditions may be key to a programs reliability, but, without insight to the repercussions if such conditions were not in place, their importance may not be readily clear. As programs mature and political and fiscal responsibilities come to the fore, often there is considerable incentive to eliminate unnecessary conservatism, design margin, redundancy, operational support, testing, training, or safety oversight. An evaluation that demonstrates how these features and capabilities averted disaster can ensure processes that saved lives or missions are not discarded without appropriate review and understanding. Close examination of accidents that almost were can also highlight differences in design from one program to another, either justifying reliability comparisons or negating them. It can also provide considerable insight into how those saving factors were developed and implemented so that similar methods can be used to ensure appropriate life-saving and mission saving factors can be developed, even for a dissimilar space program. The lessons are appropriate for seasoned manned space programs and agencies, but crucial for untried agencies and organizations that are interested in sending man into space. The large body of publicly available near miss and accident data available provide invaluable insight into programmatic, technical, and even political issues that can be addressed before they impact safety. In this paper, we examine a number of these near misses and accidents and steps a program, agency, or potential spacefaring company might take to improve their chances of success and avoid mission or safety disasters using this data.

Barr, Stephanie↗

ARPS Enabled Titan Rover Concept with Inflatable Wheels

The Decadal Survey identified Titan as one of the top priority science destinations in the large moons category, while NASA's proposed Design Reference Mission Set ranked a Titan in-situ explorer second, after a recommended Europa Geophysical Observer mission. This paper discusses a Titan rover concept, enabled by a single advanced Radioisotope Power System that could provide about 110We (BOL). The concept targets the smaller Flagship or potentially the New Frontiers mission class. This MSL class rover would traverse on four 1.5 m diameter inflatable wheels during its 3 years mission duration and would use as much design and flight heritage as possible to reduce mission cost. Direct to Earth communication would remove the need for a relay orbiter. Details on the strawman instrument payload, and rover subsystems are given for this science driven mission concept. In addition, power system trades between Advanced RTG, TPV, and Advanced Stirling and Brayton Radioisotope Power Systems (RPS) are outlined. While many possible approaches exist for Titan in-situ exploration, the Titan rover concept presented here could provide a scientifically interesting and programmatically affordable solution.

Radioisotope Power System (RPS)↗

Generative Representations for Automated Design of Robots

A method of automated design of complex, modular robots involves an evolutionary process in which generative representations of designs are used. The term generative representations as used here signifies, loosely, representations that consist of or include algorithms, computer programs, and the like, wherein encoded designs can reuse elements of their encoding and thereby evolve toward greater complexity. Automated design of robots through synthetic evolutionary processes has already been demonstrated, but it is not clear whether genetically inspired search algorithms can yield designs that are sufficiently complex for practical engineering. The ultimate success of such algorithms as tools for automation of design depends on the scaling properties of representations of designs. A nongenerative representation (one in which each element of the encoded design is used at most once in translating to the design) scales linearly with the number of elements. Search algorithms that use nongenerative representations quickly become intractable (search times vary approximately exponentially with numbers of design elements), and thus are not amenable to scaling to complex designs. Generative representations are compact representations and were devised as means to circumvent the above-mentioned fundamental restriction on scalability. In the present method, a robot is defined by a compact programmatic form (its generative representation) and the evolutionary variation takes place on this form. The evolutionary process is an iterative one, wherein each cycle consists of the following steps: 1. Generative representations are generated in an evolutionary subprocess. 2. Each generative representation is a program that, when compiled, produces an assembly procedure. 3. In a computational simulation, a constructor executes an assembly procedure to generate a robot. 4. A physical-simulation program tests the performance of a simulated constructed robot, evaluating the performance according to a fitness criterion to yield a figure of merit that is fed back into the evolutionary subprocess of the next iteration. In comparison with prior approaches to automated evolutionary design of robots, the use of generative representations offers two advantages: First, a generative representation enables the reuse of components in regular and hierarchical ways and thereby serves a systematic means of creating more complex modules out of simpler ones. Second, the evolved generative representation may capture intrinsic properties of the design problem, so that variations in the representations move through the design space more effectively than do equivalent variations in a nongenerative representation. This method has been demonstrated by using it to design some robots that move, variously, by walking, rolling, or sliding. Some of the robots were built (see figure). Although these robots are very simple, in comparison with robots designed by humans, their structures are more regular, modular, hierarchical, and complex than are those of evolved designs of comparable functionality synthesized by use of nongenerative representations.

Homby, Gregory S.↗

Langley Ground Facilities and Testing in the 21st Century

A strategic approach for retaining and more efficiently operating the essential Langley Ground Testing Facilities in the 21st Century is presented. This effort takes advantage of the previously completed and ongoing studies at the Agency and National levels. This integrated approach takes into consideration the overall decline in test business base within the nation and reduced utilization in each of the Langley facilities with capabilities to test in the subsonic, transonic, supersonic, and hypersonic speed regimes. The strategy accounts for capability needs to meet the Agency programmatic requirements and strategic goals and to execute test activities in the most efficient and flexible facility operating structure. The structure currently being implemented at Langley offers agility to right-size our capability and capacity from a national perspective, to accommodate the dynamic nature of the testing needs, and will address the influence of existing and emerging analytical tools for design. The paradigm for testing in the retained facilities is to efficiently and reliably provide more accurate and high-quality test results at an affordable cost to support design information needs for flight regimes where the computational capability is not adequate and to verify and validate the existing and emerging computational tools. Each of the above goals are planned to be achieved, keeping in mind the increasing small industry customer base engaged in developing unpiloted aerial vehicles and commercial space transportation systems.

Ambur, Damodar R.↗

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗

Computational Support for Technology- Investment Decisions

Strategic Assessment of Risk and Technology (START) is a user-friendly computer program that assists human managers in making decisions regarding research-and-development investment portfolios in the presence of uncertainties and of non-technological constraints that include budgetary and time limits, restrictions related to infrastructure, and programmatic and institutional priorities. START facilitates quantitative analysis of technologies, capabilities, missions, scenarios and programs, and thereby enables the selection and scheduling of value-optimal development efforts. START incorporates features that, variously, perform or support a unique combination of functions, most of which are not systematically performed or supported by prior decision- support software. These functions include the following: Optimal portfolio selection using an expected-utility-based assessment of capabilities and technologies; Temporal investment recommendations; Distinctions between enhancing and enabling capabilities; Analysis of partial funding for enhancing capabilities; and Sensitivity and uncertainty analysis. START can run on almost any computing hardware, within Linux and related operating systems that include Mac OS X versions 10.3 and later, and can run in Windows under the Cygwin environment. START can be distributed in binary code form. START calls, as external libraries, several open-source software packages. Output is in Excel (.xls) file format.

Adumitroaie, Virgil↗

Space Communications and Navigation (SCaN) Integrated Network Architecture Definition Document (ADD): Executive Summary - Volume 1

The SCaN Program has defined an integrated network architecture that fully meets the Administrator s mandate to the Program, and will result in a NASA infrastructure capable of providing the needed and enabling communications services to future space missions. The integrated network architecture will increase SCaN operational efficiency and interoperability through standardization, commonality and technology infusion. It will enable NASA missions requiring advanced communication and tracking capabilities such as: a. Optical communication b. Antenna arraying c. Lunar and Mars Relays d. Integrated network management (service management and network control) and integrated service execution e. Enhanced tracking for navigation f. Space internetworking with DTN and IP g. End-to-end security h. Enhanced security services Moreover, the SCaN Program has created an Integrated Network Roadmap that depicts an orchestrated and coherent evolution path toward the target architecture, encompassing all aspects that concern network assets (i.e., operations and maintenance, sustaining engineering, upgrade efforts, and major development). This roadmap identifies major NASA ADPs, and shows dependencies and drivers among the various planned undertakings and timelines. The roadmap is scalable to accommodate timely adjustments in response to Agency needs, goals, objectives and funding. Future challenges to implementing this architecture include balancing user mission needs, technology development, and the availability of funding within NASA s priorities. Strategies for addressing these challenges are to: define a flexible architecture, update the architecture periodically, use ADPs to evaluate options and determine when to make decisions, and to engage the stakeholders in these evaluations. In addition, the SCaN Program will evaluate and respond to mission need dates for technical and operational capabilities to be provided by the SCaN integrated network. In that regard, the architecture defined in this ADD is scalable to accommodate programmatic and technical changes.

Younes, Badri A.↗

Assessing Requirements Volatility and Risk Using Bayesian Networks

There are many factors that affect the level of requirements volatility a system experiences over its lifecycle and the risk that volatility imparts. Improper requirements generation, undocumented user expectations, conflicting design decisions, and anticipated / unanticipated world states are representative of these volatility factors. Combined, these volatility factors can increase programmatic risk and adversely affect successful system development. This paper proposes that a Bayesian Network can be used to support reasonable judgments concerning the most likely sources and types of requirements volatility a developing system will experience prior to starting development and by doing so it is possible to predict the level of requirements volatility the system will experience over its lifecycle. This assessment offers valuable insight to the system's developers, particularly by providing a starting point for risk mitigation planning and execution.

Russell, Michael S.↗

Ares V: Enabling Unprecedented Payloads for Space in the 21st Century

Numerous technical and programmatic studies since the U.S. space program began in the 1960s has emphasized the need for a heavy lift capability for exploration beyond low Earth orbit (LEO). The Saturn V once embodied that capability until it was retired. Now the Ares V cargo launch vehicle (CaLV) promises to restore and improve on that capability, providing unprecedented opportunities for human and robotic exploration, science, national security and commercial uses. This paper provides an overview of the capabilities of Ares V, both as an opportunity for payloads of increased mass and/or volume, and as a means of reducing risk in the payload design process. The Ares V is part of NASA s Constellation Program, which also includes the Ares I crew launch vehicle (CLV), Orion crew exploration vehicle (CEV), and Altair lunar lander. This architecture is designed to carry out the national space policy goals of completing the International Space Station (ISS), retiring the Space Shuttle fleet, and expanding human exploration beyond LEO. The Ares V is designed to loft upper stages and/or cargo, such as the Altair lander, into LEO. The Ares I is designed to put Orion into LEO with a crew of up to four for rendezvous with the ISS or with the Ares V Earth departure stage for journeys to the Moon. While retaining the goals of heritage hardware and commonality, the Ares V configuration continues to be refined through a series of internal trades. The current reference configuration was recommended by the Ares Projects and approved by the Constellation Program during the Lunar Capabilities Concept Review (LCCR) June 2008. The reference configuration defines the Ares V as 381 feet (116m) tall with a gross lift-off mass (GLOM) of 8.1 million pounds (3,704.5 mT). Its first stage will generate 11 million pounds of sea-level liftoff thrust. It will be capable of launching 413,800 pounds (187.7 mT) to LEO, 138,500 pounds (63 mT) direct to the Moon or 156,700 pounds (71.1 mT) in its dual-launch architecture role with Ares I. It could also launch 123,100 pounds (55.8 mT) to Sun-Earth L2. Assessment of astronomy payload requirements since Spring 2008 has indicated that Ares V has the potential to support a range of payloads and missions. Some of these missions were impossible in the absence of Ares V s capabilities. Collaborative design/architecture inputs, exchanges, and analyses have already begun between scientists and payload developers. A 2008 study by a National Research Council (NRC) panel, as well as analyses presented by astronomers and planetary scientists at two weekend conferences in 2008, support the position that Ares V has benefit to a broad range of planetary and astronomy missions. This early dialogue with Ares V engineers is permitting the greatest opportunity for payload/transportation/mission synergy and with the least financial impact to Ares V development. In addition, independent analyses suggest that Ares V has the opportunity to enable more cost-effective mission design. 1

Creech, Steve↗

Metrology Requirements of Future X-Ray Telescopes

Fundamental needs for future x-ray telescopes: a) Sharp images => excellent angular resolution. b) High throughput => large aperture areas. Generation-X optics technical challenges: a) High resolution => precision mirrors & alignment. b) Large apertures => lots of lightweight mirrors. Innovation needed for technical readiness: a) 4 top-level error terms contribute to image size. b) There are approaches to controlling those errors. Innovation needed for manufacturing readiness: Programmatic issues are at least as severe

Gubarev, Mikhail↗

SIM-PlanetQuest: Progress Report

SIM-PlanetQuest is a NASA astrophysics mission that is implementing the National Research Counsel's recommended Astrometric Interferometry Mission (AIM) to develop the first, in-space, optical, long-baseline Michelson Stellar Interferometer for performing micro-arcsecond-level astrometry. This level of astrometric precision will enable characterization of planetary systems around nearby stars and enable a number of key investigations in astrophysics including calibration of the cosmological distance scale, stellar and galactic structure and evolution, and dark matter/energy distribution. This paper provides an update on the SIM-PlanetQuest Mission covering the results of the 2005 mission redesign and the recent completion of the last in a series of technology "gates." The SIM-PlanetQuest mission redesign was directed by NASA to recover eroded mass and power margins and to meet specific implementation cost targets. The resulting mission redesign met all redesign objectives with minimal impact to mission science performance. This paper provides the mission redesign objectives and describes the resulting mission and system design including changes in science capability. SIM-PlanetQuest also completed the last of eight major technology development gates that were established in 2001 by NASA, completing the enabling technology development. The technology development program, the last gate, and its significance to the project's flight verification and validation (V&V) approach are briefly described (covered in more detail in a separate paper at this conference). An update on project programmatic status and plans is also provided.

astrometry↗

NASA Spacecraft Fault Management Workshop Results

Fault Management is a critical aspect of deep-space missions. For the purposes of this paper, fault management is defined as the ability of a system to detect, isolate, and mitigate events that impact, or have the potential to impact, nominal mission operations. The fault management capabilities are commonly distributed across flight and ground subsystems, impacting hardware, software, and mission operations designs. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that 4 out of the 5 missions studied had significant overruns due to underestimating the complexity and support requirements for fault management. As a result of this and other recent experiences, the NASA Science Mission Directorate (SMD) Planetary Science Division (PSD) commissioned a workshop to bring together invited participants across government, industry, academia to assess the state of the art in fault management practice and research, identify current and potential issues, and make recommendations for addressing these issues. The workshop was held in New Orleans in April of 2008. The workshop concluded that fault management is not being limited by technology, but rather by a lack of emphasis and discipline in both the engineering and programmatic dimensions. Some of the areas cited in the findings include different, conflicting, and changing institutional goals and risk postures; unclear ownership of end-to-end fault management engineering; inadequate understanding of the impact of mission-level requirements on fault management complexity; and practices, processes, and tools that have not kept pace with the increasing complexity of mission requirements and spacecraft systems. This paper summarizes the findings and recommendations from that workshop, as well as opportunities identified for future investment in tools, processes, and products to facilitate the development of space flight fault management capabilities.

Newhouse, Marilyn↗