Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Risk Management Space Projects”

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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Testing Strategies and Methodologies for the Max Launch Abort System

The National Aeronautics and Space Administration (NASA) Engineering and Safety Center (NESC) was tasked to develop an alternate, tower-less launch abort system (LAS) as risk mitigation for the Orion Project. The successful pad abort flight demonstration test in July 2009 of the "Max" launch abort system (MLAS) provided data critical to the design of future LASs, while demonstrating the Agency s ability to rapidly design, build and fly full-scale hardware at minimal cost in a "virtual" work environment. Limited funding and an aggressive schedule presented a challenge for testing of the complex MLAS system. The successful pad abort flight demonstration test was attributed to the project s systems engineering and integration process, which included: a concise definition of, and an adherence to, flight test objectives; a solid operational concept; well defined performance requirements, and a test program tailored to reducing the highest flight test risks. The testing ranged from wind tunnel validation of computational fluid dynamic simulations to component ground tests of the highest risk subsystems. This paper provides an overview of the testing/risk management approach and methodologies used to understand and reduce the areas of highest risk - resulting in a successful flight demonstration test.

Schaible, Dawn M.↗
NASA NTRSDate not supplied

Numerical Investigation of Heat Transfer and Fluid Flow within Electrochemical Hydrogen Peroxide Generation Unit

Long-term manned space missions require the onboard production of disinfectants essential for maintaining crew health and supporting life systems. Currently, disinfection aboard the International Space Station (ISS) relies on disposable wetted wipes, which are regularly resupplied from Earth. This approach imposes a significant burden on resupply logistics, storage, and waste management. To address these challenges and support future missions, efforts are underway to develop an in-situ solution that electrochemically generates hydrogen peroxide disinfectant using onboard resources. In collaboration with NASA, Faraday Technology, Inc. has advanced this concept through a series of Small Business Innovation Research (SBIR) projects, resulting in the development of a Peroxide Generation Unit (PGU). The PGU can produce up to 3 wt.% hydrogen peroxide on-demand at a rate of 1 liter per day, providing a sustainable alternative to Earth-dependent supplies. The resulting aqueous hydrogen peroxide (H₂O₂) is an effective disinfectant, safe for crew use, compatible with spacecraft systems, and free from volatiles, off-gassing, or residues. This innovation offers a reliable, efficient solution for onboard disinfection, reducing dependence on Earth-based resupply while ensuring the health and safety of space crews. Generating hydrogen peroxide at the required rate needs high voltages and currents, exceeding 20V and 2A respectively, which leads to significant heat generation from Joule heating. This temperature rise poses a risk to sensitive system components, especially critical and expensive membranes that can degrade under thermal stress. To mitigate this risk, the thermal, fluid, and electrical flows within the system are modeled computationally using the commercial software COMSOL. The numerical simulations are validated against experimental data from both sub-scale and alpha-scale systems. Once verified, the model is employed to identify thermal hotspots, investigate their underlying causes, and explore solutions to prevent them.

Life Support Systems (LSS)↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2014

MAVEN Information Security Governance, Risk Management, and Compliance (GRC): Lessons Learned

As the first interplanetary mission managed by the NASA Goddard Space Flight Center, the Mars Atmosphere and Volatile EvolutioN (MAVEN) had three IT security goals for its ground system: COMPLIANCE, (IT) RISK REDUCTION, and COST REDUCTION. In a multiorganizational environment in which government, industry and academia work together in support of the ground system and mission operations, information security governance, risk management, and compliance (GRC) becomes a challenge as each component of the ground system has and follows its own set of IT security requirements. These requirements are not necessarily the same or even similar to each other's, making the auditing of the ground system security a challenging feat. A combination of standards-based information security management based on the National Institute of Standards and Technology (NIST) Risk Management Framework (RMF), due diligence by the Mission's leadership, and effective collaboration among all elements of the ground system enabled MAVEN to successfully meet NASA's requirements for IT security, and therefore meet Federal Information Security Management Act (FISMA) mandate on the Agency. Throughout the implementation of GRC on MAVEN during the early stages of the mission development, the Project faced many challenges some of which have been identified in this paper. The purpose of this paper is to document these challenges, and provide a brief analysis of the lessons MAVEN learned. The historical information documented herein, derived from an internal pre-launch lessons learned analysis, can be used by current and future missions and organizations implementing and auditing GRC.

FISMA↗
NASA NTRS2016

NASA Human System Risk Assessment Process

NASA utilizes an evidence based system to perform risk assessments for the human system for spaceflight missions. The center of this process is the multi-disciplinary Human System Risk Board (HSRB). The HSRB is chartered from the Chief Health and Medical Officer (OCHMO) at NASA Headquarters. The HSRB reviews all human system risks via an established comprehensive risk and configuration management plan based on a project management approach. The HSRB facilitates the integration of human research (terrestrial and spaceflight), medical operations, occupational surveillance, systems engineering and many other disciplines in a comprehensive review of human system risks. The HSRB considers all factors that influence human risk. These factors include pre-mission considerations such as screening criteria, training, age, sex, and physiological condition. In mission factors such as available countermeasures, mission duration and location and post mission factors such as time to return to baseline (reconditioning), post mission health screening, and available treatments. All of the factors influence the total risk assessment for each human risk. The HSRB performed a comprehensive review of all potential inflight medical conditions and events and over the course of several reviews consolidated the number of human system risks to 30, where the greatest emphasis is placed for investing program dollars for risk mitigation. The HSRB considers all available evidence from human research and, medical operations and occupational surveillance in assessing the risks for appropriate mitigation and future work. All applicable DRMs (low earth orbit for 6 and 12 months, deep space for 30 days and 1 year, a lunar mission for 1 year, and a planetary mission for 3 years) are considered as human system risks are modified by the hazards associated with space flight such as microgravity, exposure to radiation, distance from the earth, isolation and a closed environment. Each risk has a summary two-page assessment representing the state of knowledge/evidence of that risk, available risk mitigations, traceability to the Space Flight Human System Standards (SFHSS) and program requirements, and future work required. These data then can drive coordinated budgets across the Human Research Program, the International Space Station, Crew Health and Safety and Advanced Exploration System budgets to provide the most economical and timely mitigations. The risk assessments were completed for the 6 DRMs and serve as the baseline for which subsequent research and technology development and crew health care portfolios can be assessed. The HSRB reviews each risk at least annually or when new evidence/information is available that adds to the body of evidence. The current status of each risk can be reported to program management for operations, budget reviews and general oversight of the human system risk management program.

Francisco, D.↗
NASA NTRS2010

Planning and Estimation of Operations Support Requirements

Life Cycle Cost (LCC) estimates during the proposal and early design phases, as well as project replans during the development phase, are heavily focused on hardware development schedules and costs. Operations (phase E) costs are typically small compared to the spacecraft development and test costs. This, combined with the long lead time for realizing operations costs, can lead to de-emphasizing estimation of operations support requirements during proposal, early design, and replan cost exercises. The Discovery and New Frontiers (D&NF) programs comprise small, cost-capped missions supporting scientific exploration of the solar system. Any LCC growth can directly impact the programs' ability to fund new missions, and even moderate yearly underestimates of the operations costs can present significant LCC impacts for deep space missions with long operational durations. The National Aeronautics and Space Administration (NASA) 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 at or after launch due to underestimation of the complexity and supporting requirements for operations activities; the fifth mission had not launched at the time of the mission. The drivers behind these overruns include overly optimistic assumptions regarding the savings resulting from the use of heritage technology, late development of operations requirements, inadequate planning for sustaining engineering and the special requirements of long duration missions (e.g., knowledge retention and hardware/software refresh), and delayed completion of ground system development work. This paper updates the D&NF LCC study, looking at the operations (phase E) cost drivers in more detail and extending the study to include 2 additional missions and identifies areas for increased emphasis by project management in order to improve the fidelity of operations estimates.

Newhouse, Marilyn E.↗
NASA NTRS2011

Full-Scaled Advanced Systems Testbed: Ensuring Success of Adaptive Control Research Through Project Lifecycle Risk Mitigation

The National Aeronautics and Space Administration's Dryden Flight Research Center completed flight testing of adaptive controls research on the Full-Scale Advance Systems Testbed (FAST) in January of 2011. The research addressed technical challenges involved with reducing risk in an increasingly complex and dynamic national airspace. Specific challenges lie with the development of validated, multidisciplinary, integrated aircraft control design tools and techniques to enable safe flight in the presence of adverse conditions such as structural damage, control surface failures, or aerodynamic upsets. The testbed is an F-18 aircraft serving as a full-scale vehicle to test and validate adaptive flight control research and lends a significant confidence to the development, maturation, and acceptance process of incorporating adaptive control laws into follow-on research and the operational environment. The experimental systems integrated into FAST were designed to allow for flexible yet safe flight test evaluation and validation of modern adaptive control technologies and revolve around two major hardware upgrades: the modification of Production Support Flight Control Computers (PSFCC) and integration of two, fourth-generation Airborne Research Test Systems (ARTS). Post-hardware integration verification and validation provided the foundation for safe flight test of Nonlinear Dynamic Inversion and Model Reference Aircraft Control adaptive control law experiments. To ensure success of flight in terms of cost, schedule, and test results, emphasis on risk management was incorporated into early stages of design and flight test planning and continued through the execution of each flight test mission. Specific consideration was made to incorporate safety features within the hardware and software to alleviate user demands as well as into test processes and training to reduce human factor impacts to safe and successful flight test. This paper describes the research configuration, experiment functionality, overall risk mitigation, flight test approach and results, and lessons learned of adaptive controls research of the Full-Scale Advanced Systems Testbed.

Pavlock, Kate M.↗
NASA NTRS2011

Medical Updates Number 5 to the International Space Station Probability Risk Assessment (PRA) Model Using the Integrated Medical Model

The Integrated Medical Model (IMM) Project has been developing a probabilistic risk assessment tool, the IMM, to help evaluate in-flight crew health needs and impacts to the mission due to medical events. This package is a follow-up to a data package provided in June 2009. The IMM currently represents 83 medical conditions and associated ISS resources required to mitigate medical events. IMM end state forecasts relevant to the ISS PRA model include evacuation (EVAC) and loss of crew life (LOCL). The current version of the IMM provides the basis for the operational version of IMM expected in the January 2011 timeframe. The objectives of this data package are: 1. To provide a preliminary understanding of medical risk data used to update the ISS PRA Model. The IMM has had limited validation and an initial characterization of maturity has been completed using NASA STD 7009 Standard for Models and Simulation. The IMM has been internally validated by IMM personnel but has not been validated by an independent body external to the IMM Project. 2. To support a continued dialogue between the ISS PRA and IMM teams. To ensure accurate data interpretation, and that IMM output format and content meets the needs of the ISS Risk Management Office and ISS PRA Model, periodic discussions are anticipated between the risk teams. 3. To help assess the differences between the current ISS PRA and IMM medical risk forecasts of EVAC and LOCL. Follow-on activities are anticipated based on the differences between the current ISS PRA medical risk data and the latest medical risk data produced by IMM.

Butler, Doug↗
NASA NTRS2006

Crew Launch Vehicle (CLV) Upper Stage Configuration Selection Process

The Crew Launch Vehicle (CLV), a key component of NASA's blueprint for the next generation of spacecraft to take humans back to the moon, is being designed and built by engineers at NASA s Marshall Space Flight Center (MSFC). The vehicle s design is based on the results of NASA's 2005 Exploration Systems Architecture Study (ESAS), which called for development of a crew-launch system to reduce the gap between Shuttle retirement and Crew Exploration Vehicle (CEV) Initial Operating Capability, identification of key technologies required to enable and significantly enhance these reference exploration systems, and a reprioritization of near- and far-term technology investments. The Upper Stage Element (USE) of the CLV is a clean-sheet approach that is being designed and developed in-house, with element management at MSFC. The USE concept is a self-supporting cylindrical structure, approximately 115' long and 216" in diameter, consisting of the following subsystems: Primary Structures (LOX Tank, LH2 Tank, Intertank, Thrust Structure, Spacecraft Payload Adaptor, Interstage, Forward and Aft Skirts), Secondary Structures (Systems Tunnel), Avionics and Software, Main Propulsion System, Reaction Control System, Thrust Vector Control, Auxiliary Power Unit, and Hydraulic Systems. The ESAS originally recommended a CEV to be launched atop a four-segment Space Shuttle Main Engine (SSME) CLV, utilizing an RS-25 engine-powered upper stage. However, Agency decisions to utilize fewer CLV development steps to lunar missions, reduce the overall risk for the lunar program, and provide a more balanced engine production rate requirement prompted engineers to switch to a five-segment design with a single Saturn-derived J-2X engine. This approach provides for single upper stage engine development for the CLV and an Earth Departure Stage, single Reusable Solid Rocket Booster (RSRB) development for the CLV and a Cargo Launch Vehicle, and single core SSME development. While the RSRB design has changed since the CLV Project's inception, the USE design has remained essentially a clean-sheet approach. Although a clean-sheet upper stage design inherently carries more risk than a modified design, it does offer many advantages: a design for increased reliability; built-in extensibility to allow for commonality/growth without major redesign; and incorporation of state-of-the-art materials, hardware, and design, fabrication, and test techniques and processes to facilitate a potentially better, more reliable system. Because consideration was given in the ESAS to both clean-sheet and modified USE designs, this paper will highlight the advantages and disadvantages of both approaches and provide a detailed discussion of trades/selections made that led to the final upper stage configuration.

Davis, Daniel J.↗
NASA NTRS1992

Intelligent fault management for the Space Station active thermal control system

The Thermal Advanced Automation Project (TAAP) approach and architecture is described for automating the Space Station Freedom (SSF) Active Thermal Control System (ATCS). The baseline functionally and advanced automation techniques for Fault Detection, Isolation, and Recovery (FDIR) will be compared and contrasted. Advanced automation techniques such as rule-based systems and model-based reasoning should be utilized to efficiently control, monitor, and diagnose this extremely complex physical system. TAAP is developing advanced FDIR software for use on the SSF thermal control system. The goal of TAAP is to join Knowledge-Based System (KBS) technology, using a combination of rules and model-based reasoning, with conventional monitoring and control software in order to maximize autonomy of the ATCS. TAAP's predecessor was NASA's Thermal Expert System (TEXSYS) project which was the first large real-time expert system to use both extensive rules and model-based reasoning to control and perform FDIR on a large, complex physical system. TEXSYS showed that a method is needed for safely and inexpensively testing all possible faults of the ATCS, particularly those potentially damaging to the hardware, in order to develop a fully capable FDIR system. TAAP therefore includes the development of a high-fidelity simulation of the thermal control system. The simulation provides realistic, dynamic ATCS behavior and fault insertion capability for software testing without hardware related risks or expense. In addition, thermal engineers will gain greater confidence in the KBS FDIR software than was possible prior to this kind of simulation testing. The TAAP KBS will initially be a ground-based extension of the baseline ATCS monitoring and control software and could be migrated on-board as additional computation resources are made available.

Hill, Tim↗
NASA NTRS2016

Large Payload Ground Transportation and Test Considerations

Many spacecraft concepts under consideration by the National Aeronautics and Space Administration’s (NASA’s) Evolvable Mars Campaign take advantage of a Space Launch System payload shroud that may be 8 to 10 meters in diameter. Large payloads can theoretically save cost by reducing the number of launches needed--but only if it is possible to build, test, and transport a large payload to the launch site in the first place. Analysis performed previously for the Altair project identified several transportation and test issues with an 8.973 meters diameter payload. Although the entire Constellation Program—including Altair—has since been canceled, these issues serve as important lessons learned for spacecraft designers and program managers considering large payloads for future programs. A transportation feasibility study found that, even broken up into an Ascent and Descent Module, the Altair spacecraft would not fit inside available aircraft. Ground transportation of such large payloads over extended distances is not generally permitted, so overland transportation alone would not be an option. Limited ground transportation to the nearest waterway may be possible, but water transportation could take as long as 67 days per production unit, depending on point of origin and acceptance test facility; transportation from the western United States would require transit through the Panama Canal to access the Kennedy Space Center launch site. Large payloads also pose acceptance test and ground processing challenges. Although propulsion, mechanical vibration, and reverberant acoustic test facilities at NASA’s Plum Brook Station have been designed to accommodate large spacecraft, special handling and test work-arounds may be necessary, which could increase cost, schedule, and technical risk. Once at the launch site, there are no facilities currently capable of accommodating the combination of large payload size and hazardous processing such as hypergolic fuels, pyrotechnic devices, and high pressure gasses. Ironically, the limiting factor to a national heavy lift strategy may not be the rocket technology needed to throw a heavy payload, but rather the terrestrial infrastructure—roads, bridges, airframes, and buildings—necessary to transport, acceptance test, and process large spacecraft. Failure to carefully consider where and how large spacecraft are manufactured, tested, and launched could result in unforeseen cost to modify existing (or develop new) infrastructure, or incur additional risk due to increased handling operations or eliminating key verifications. Although this paper focuses on the canceled Altair spacecraft as a case study, the issues identified here have wide applicability to other large payloads, including concepts under consideration for NASA’s Evolvable Mars Campaign.

Rucker, Michelle A.↗
NASA NTRS1990

Transition flight control room automation

The Workstation Prototype Laboratory is currently working on a number of projects which can have a direct impact on ground operations automation. These projects include: (1) The fuel cell monitoring system (FCMS), which will monitor and detect problems with the fuel cells on the shuttle. FCMS will use a combination of rules (forward/backward) and multithreaded procedures, which run concurrently with the rules, to implement the malfunction algorithms of the EGIL flight controllers. The combination of rule-based reasoning and procedural reasoning allows us to more easily map the malfunction algorithms into a real-time system implementation. (2) A graphical computation language (AGCOMPL) is an experimental prototype to determine the benefits and drawbacks of using a graphical language to design computations (algorithms) to work on shuttle or space station telemetry and trajectory data. (3) The design of a system will allow a model of an electrical system, including telemetry sensors, to be configured on the screen graphically using previously defined electrical icons. This electrical model would then be used to generate rules and procedures for detecting malfunctions in the electrical components of the model. (4) A generic message management (GMM) system is being designed for real-time applications as a message management system which sends advisory messages to a user. The primary purpose of GMM is to reduce the risk of overloading a user with information when multiple failures occur and to assist the developer in the devising an explanation facility. The emphasis of our work is to develop practical tools and techniques, including identification of appropriate software tools to support research, application, and tool building activities, while determining the feasibility of a given approach.

Welborn, Curtis Ray↗
NASA NTRS1990

Transition Flight Control Room Automation

The Workstation Prototype Laboratory is currently working on a number of projects which we feel can have a direct impact on ground operations automation. These projects include: The Fuel Cell Monitoring System (FCMS), which will monitor and detect problems with the fuel cells on the Shuttle. FCMS will use a combination of rules (forward/backward) and multi-threaded procedures which run concurrently with the rules, to implement the malfunction algorithms of the EGIL flight controllers. The combination of rule based reasoning and procedural reasoning allows us to more easily map the malfunction algorithms into a real-time system implementation. A graphical computation language (AGCOMPL). AGCOMPL is an experimental prototype to determine the benefits and drawbacks of using a graphical language to design computations (algorithms) to work on Shuttle or Space Station telemetry and trajectory data. The design of a system which will allow a model of an electrical system, including telemetry sensors, to be configured on the screen graphically using previously defined electrical icons. This electrical model would then be used to generate rules and procedures for detecting malfunctions in the electrical components of the model. A generic message management (GMM) system. GMM is being designed as a message management system for real-time applications which send advisory messages to a user. The primary purpose of GMM is to reduce the risk of overloading a user with information when multiple failures occurs and in assisting the developer in devising an explanation facility. The emphasis of our work is to develop practical tools and techniques, while determining the feasibility of a given approach, including identification of appropriate software tools to support research, application and tool building activities.

Welborn, Curtis Ray↗
NASA NTRS2010

Atrial Arrhythmias in Astronauts - Summary of a NASA Summit

Background and Problem Definition: To evaluate NASA s current standards and practices related to atrial arrhythmias in astronauts, Space Medicine s Advanced Projects Section at the Johnson Space Center was tasked with organizing a summit to discuss the approach to atrial arrhythmias in the astronaut cohort. Since 1959, 11 cases of atrial fibrillation, atrial flutter, or supraventricular tachycardia have been recorded among active corps crewmembers. Most of the cases were paroxysmal, although a few were sustained. While most of the affected crewmembers were asymptomatic, those slated for long-duration space flight underwent radiofrequency ablation treatment to prevent further episodes of the arrhythmia. The summit was convened to solicit expert opinion on screening, diagnosis, and treatment options, to identify gaps in knowledge, and to propose relevant research initiatives. Summit Meeting Objectives: The Atrial Arrhythmia Summit brought together a panel of six cardiologists, including nationally and internationally renowned leaders in cardiac electrophysiology, exercise physiology, and space flight cardiovascular physiology. The primary objectives of the summit discussions were to evaluate cases of atrial arrhythmia in the astronaut population, to understand the factors that may predispose an individual to this condition, to understand NASA s current capabilities for screening, diagnosis, and treatment, to discuss the risks associated with treatment of crewmembers assigned to long-duration missions or extravehicular activities, and to discuss recommendations for prevention or management of future cases. Summary of Recommendations: The summit panel s recommendations were grouped into seven categories: Epidemiology, Screening, Standards and Selection, Treatment of Atrial Fibrillation Manifesting Preflight, Atrial Fibrillation during Flight, Prevention of Atrial Fibrillation, and Future Research

Barr, Yael R.↗
NASA NTRS2005

Auxiliary Propulsion Activities in Support of NASA's Exploration Initiative

The Space Launch Initiative (SLI) procurement mechanism NRA8-30 initiated the Auxiliary Propulsion System/Main Propulsion System (APS/MPS) Project in 2001 to address technology gaps and development risks for non-toxic and cryogenic propellants for auxiliary propulsion applications. These applications include reaction control and orbital maneuvering engines, and storage, pressure control, and transfer technologies associated with on-orbit maintenance of cryogens. The project has successfully evolved over several years in response to changing requirements for re-usable launch vehicle technologies, general launch technology improvements, and, most recently, exploration technologies. Lessons learned based on actual hardware performance have also played a part in the project evolution to focus now on those technologies deemed specifically relevant to the Exploration Initiative. Formal relevance reviews held in the spring of 2004 resulted in authority for continuation of the Auxiliary Propulsion Project through Fiscal Year 2005 (FY05), and provided for a direct reporting path to the Exploration Systems Mission Directorate. The tasks determined to be relevant under the project were: continuation of the development, fabrication, and delivery of three 870 lbf thrust prototype LOX/ethanol reaction control engines; the fabrication, assembly, engine integration and testing of the Auxiliary Propulsion Test Bed at White Sands Test Facility; and the completion of FY04 cryogenic fluid management component and subsystem development tasks (mass gauging, pressure control, and liquid acquisition elements). This paper presents an overview of those tasks, their scope, expectations, and results to-date as carried forward into the Exploration Initiative.

Best, Philip J.↗
NASA NTRS2009

An Effective Health and Medical Technical Authority

The NASA Governance model directed the formation of three Technical Authorities, Engineering; Safety and Mission Assurance; and Health and Medical, to ensure that risks are identified and adjudicated efficiently and transparently in concert with the spaceflight programs and projects. The Health and Medical Technical Authority (HMTA) has been implemented at the Johnson Space Center (JSC) and consists of the Chief Medical Office (CMO), the Deputy CMO, and HMTA Delegates. The JSC HMTA achieves the goals of risk identification and adjudication through the discharge of the appropriate technical expertise to human space flight programs and projects and the escalation of issues within program and technical authority boards. The JSC HMTA relies on subject matter experts (SMEs) in the Space Life Sciences Directorate at JSC as well as experts from other Centers to work crew health and performance issues at the technical level, develop requirements, oversee implementation and validation of requirements, and identify risks and non-compliances. Once a risk or potential noncompliance has been identified and reported to the programs or projects, the JSC HMTA begins to track it and closely monitor the program's or project's response. As a risk is developed or a non-compliance negotiated, positions from various levels of decision makers are sought at the program and project control boards. The HMTA may support a program or project position if it is satisfied with the decision making and vetting processes (ex. the subject matter expert voiced his/her concerns and all dissenting opinions were documented) and finds that the position both acknowledges the risk and cost of the mitigation and resolves the issue without changing NASA risk posture. The HMTA may disagree with a program or project position if the NASA risk posture has been elevated or obfuscated. If the HMTA does disagree with the program or project position, it will appeal to successively higher levels of authority so that risk acceptance and risk trades will be acknowledged and sanctioned at the highest appropriate level; this includes Program Managers, Mission Directorate Associate Administrators and the Agency Administrator.

Fogarty, Jennifer A.↗
NASA NTRS2004

Methodolgy For Evaluation Of Technology Impacts In Space Electric Power Systems

The Analysis and Management branch of the Power and Propulsion Office at NASA Glenn Research Center is responsible for performing complex analyses of the space power and In-Space propulsion products developed by GRC. This work quantifies the benefits of the advanced technologies to support on-going advocacy efforts. The Power and Propulsion Office is committed to understanding how the advancement in space technologies could benefit future NASA missions. They support many diverse projects and missions throughout NASA as well as industry and academia. The area of work that we are concentrating on is space technology investment strategies. Our goal is to develop a Monte-Carlo based tool to investigate technology impacts in space electric power systems. The framework is being developed at this stage, which will be used to set up a computer simulation of a space electric power system (EPS). The outcome is expected to be a probabilistic assessment of critical technologies and potential development issues. We are developing methods for integrating existing spreadsheet-based tools into the simulation tool. Also, work is being done on defining interface protocols to enable rapid integration of future tools. Monte Carlo-based simulation programs for statistical modeling of the EPS Model. I decided to learn and evaluate Palisade's @Risk and Risk Optimizer software, and utilize it's capabilities for the Electric Power System (EPS) model. I also looked at similar software packages (JMP, SPSS, Crystal Ball, VenSim, Analytica) available from other suppliers and evaluated them. The second task was to develop the framework for the tool, in which we had to define technology characteristics using weighing factors and probability distributions. Also we had to define the simulation space and add hard and soft constraints to the model. The third task is to incorporate (preliminary) cost factors into the model. A final task is developing a cross-platform solution of this framework.

Holda, Julie↗
NASA NTRS2002

Enhancing Human Health Using Space Imagery: Summary of Research

The International Space University (ISU) 2002 Summer Session was conducted in Pomona, California, June 29-August 30, 2002. Ninety-nine professionals and students from thirty-one countries attended the Summer Session. More than half of these students participated in the Student Research Design Project entitled, "HI-STAR: Health Improvements through Space Technologies and Resources." ISU's interdisciplinary Student Research Design Projects are intended to have great educational value for the participants and, at the same time, to result in a product that will be useful to the field. The HI-STAR project was a success on both counts. The mission of the ISU students' effort on HI-STAR was to develop and promote a global strategy to help combat malaria using space technology. Like the tiny yet powerful mosquito, HI-STAR is a small program that aspires to make a difference. Timely detection of malaria danger zones is essential to help health authorities and policy makers make decisions about how to manage limited resources for combating malaria. In 2001, the technical support network for prevention and control of malaria epidemics published a study called "Malaria Early Warning Systems: Concepts, Indicators and Partners." This study, funded by Roll Back Malaria, a World Health Organization initiative, offered a framework for a monitoring and early warning system. HI-STAR seeks to build on this proposal and enhance the space elements of the suggested framework. Malaria disease dynamics and distributions are related to environmental variables. From space, environmental conditions that support the growth of mosquito populations can be monitored, Malaria-specific information can be gathered from satellite-borne remote sensing instruments and ground-based sensors. This information can be integrated via geographic information systems (GIS) into a Malaria Information System (MIS) that can provide assessment analyses and risk maps as output. HI-STAR defines and suggests the development of an active MIS as a low-cost tool to help organizations plan their efforts to fight malaria.

Finarelli, Margaret G.↗