Search NASA⌕ Search

SEARCH · Search NASA

Results for “system-level effects”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

A Real-Time Rover Executive based On Model-Based Reactive Planning

This paper reports on the experimental verification of the ability of IDEA (Intelligent Distributed Execution Architecture) effectively operate at multiple levels of abstraction in an autonomous control system. The basic hypothesis of IDEA is that a large control system can be structured as a collection of interacting control agents, each organized around the same fundamental structure. Two IDEA agents, a system-level agent and a mission-level agent, are designed and implemented to autonomously control the K9 rover in real-time. The system is evaluated in the scenario where the rover must acquire images from a specified set of locations. The IDEA agents are responsible for enabling the rover to achieve its goals while monitoring the execution and safety of the rover and recovering from dangerous states when necessary. Experiments carried out both in simulation and on the physical rover, produced highly promising results.

Bias, M. Bernardine↗
NASA NTRS2003

Design and Analysis of the ST7 Disturbance Reduction System (DRS) Spacecraft Controller

The Space Technology 7 experiment will perform an on-orbit system-level validation of two specific Disturbance Reduction System technologies: a gravitational reference sensor employing a free-floating test mass and a set of micronewton colloidal thrusters. The Disturbance Reduction System is designed to maintain a spacecraft's position with respect to the free-floating test mass to less than 10 nm/square root of Hz, over the frequency range 10(exp -3) Hz to 10(exp -2) Hz. This paper presents the design and analysis of the coupled drag-free and attitude control system that closes the loop between the gravitational reference sensor and the micronewton thrusters while incorporating star tracker data at low frequencies. The effects of actuation and measurement noise and disturbances on the spacecraft and test masses are evaluated in a seven-degree-of-freedom planar model incorporating two translational and one rotational degrees of freedom for the spacecraft and two translational degrees of freedom for each test mass.

Maghami, P. G.↗
NASA NTRS2003

18-Degree-of-Freedom Controller Design for the ST7 Disturbance Reduction System

The Space Technology 7 experiment will perform an on-orbit system-level validation of a Disturbance Reduction System employing gravitational reference sensors and micronewton colloidal thrusters to maintain a spacecraft s position with respect to free-floating test masses in the gravitational reference sensors to less than 10 nm/dHz over the frequency range 1 to 30 mHz. This paper presents the design and analysis of the control system that closes the loop between the gravitational reference sensors and the micronewton thrusters while incorporating star tracker data at low frequencies. The effects of disturbances and actuation and measurement noise are evaluated in a eighteen-degree-of-freedom model.

Markley, F. L.↗
NASA NTRS2003

A Power Conversion Concept for the Jupiter Icy Moons Orbiter

The Jupiter Icy Moons Orbiter (JIMO) mission is currently under study by the Office of Space Science under the Project Prometheus Program. JIMO is examining the use of Nuclear Electric Propulsion (NEP) to carry scientific payloads to three Jovian moons. A potential power system concept includes dual 100 kWe Brayton converters, a deployable pumped loop heat rejection subsystem, and a 400 Vac Power Management and Distribution (PMAD) bus. Many trades were performed in aniving at this candidate power system concept. System-level studies examined design and off-design operating modes, determined startup requirements, evaluated subsystem redundancy options, and quantified the mass and radiator area of reactor power systems from 20 to 200 kWe. In the Brayton converter subsystem, studies were performed to investigate converter packaging options, and assess the induced torque effects on spacecraft dynamics due to rotating machinery. In the heat rejection subsystem, design trades were conducted on heat transport approaches, material and fluid options, and deployed radiator geometries. In the PMAD subsystem, the overall electrical architecture was defined and trade studies examined distribution approaches, voltage levels, and cabling options.

Mason, Lee S.↗
NASA NTRS2003

Requirements Development for the NASA Advanced Engineering Environment (AEE)

The requirements development process for the Advanced Engineering Environment (AEE) is presented. This environment has been developed to allow NASA to perform independent analysis and design of space transportation architectures and technologies. Given the highly collaborative and distributed nature of AEE, a variety of organizations are involved in the development, operations and management of the system. Furthermore, there are additional organizations involved representing external customers and stakeholders. Thorough coordination and effective communication is essential to translate desired expectations of the system into requirements. Functional, verifiable requirements for this (and indeed any) system are necessary to fulfill several roles. Requirements serve as a contractual tool, configuration management tool, and as an engineering tool, sometimes simultaneously. The role of requirements as an engineering tool is particularly important because a stable set of requirements for a system provides a common framework of system scope and characterization among team members. Furthermore, the requirements provide the basis for checking completion of system elements and form the basis for system verification. Requirements are at the core of systems engineering. The AEE Project has undertaken a thorough process to translate the desires and expectations of external customers and stakeholders into functional system-level requirements that are captured with sufficient rigor to allow development planning, resource allocation and system-level design, development, implementation and verification. These requirements are maintained in an integrated, relational database that provides traceability to governing Program requirements and also to verification methods and subsystem-level requirements.

Rogers, Eric↗
NASA NTRS2003

Disturbance Reduction Control Design for the ST7 Flight Validation Experiment

The Space Technology 7 experiment will perform an on-orbit system-level validation of two specific Disturbance Reduction System technologies: a gravitational reference sensor employing a free-floating test mass, and a set of micro-Newton colloidal thrusters. The ST7 Disturbance Reduction System is designed to maintain the spacecraft's position with respect to a free-floating test mass to less than 10 nm/Hz, over the frequency range of 1 to 30 mHz. This paper presents the design and analysis of the coupled, drag-free and attitude control systems that close the loop between the gravitational reference sensor and the micro-Newton thrusters, while incorporating star tracker data at low frequencies. A full 18 degree-of-freedom model, which incorporates rigid-body models of the spacecraft and two test masses, is used to evaluate the effects of actuation and measurement noise and disturbances on the performance of the drag-free system.

Maghami, P. G.↗
NASA NTRS2005

Addressing the Real-World Challenges in the Development of Propulsion IVHM Technology Experiment (PITEX)

The Propulsion IVHM Technology Experiment (PITEX) has been an on-going research effort conducted over several years. PITEX has developed and applied a model-based diagnostic system for the main propulsion system of the X-34 reusable launch vehicle, a space-launch technology demonstrator. The application was simulation-based using detailed models of the propulsion subsystem to generate nominal and failure scenarios during captive carry, which is the most safety-critical portion of the X-34 flight. Since no system-level testing of the X-34 Main Propulsion System (MPS) was performed, these simulated data were used to verify and validate the software system. Advanced diagnostic and signal processing algorithms were developed and tested in real-time on flight-like hardware. In an attempt to expose potential performance problems, these PITEX algorithms were subject to numerous real-world effects in the simulated data including noise, sensor resolution, command/valve talkback information, and nominal build variations. The current research has demonstrated the potential benefits of model-based diagnostics, defined the performance metrics required to evaluate the diagnostic system, and studied the impact of real-world challenges encountered when monitoring propulsion subsystems.

Maul, William A.↗
NASA NTRS2005

Optimal Design of Integrated Systems Health Management (ISHM) Systems for improving safety in NASA's Exploration Vehicles: A Two-Level Multidisciplinary Design Approach

In this paper, a two-level multidisciplinary design approach is described to optimize the effectiveness of ISHM s. At the top level, the overall safety of the mission consists of system-level variables, parameters, objectives, and constraints that are shared throughout the system and by all subsystems. Each subsystem level will then comprise of these shared values in addition to subsystem-specific variables, parameters, objectives and constraints. A hierarchical structure will be established to pass up or down shared values between the two levels with system-level and subsystem-level optimization routines.

Tumer, Irem↗
NASA NTRS2004

Using explanatory crop models to develop simple tools for Advanced Life Support system studies

System-level analyses for Advanced Life Support require mathematical models for various processes, such as for biomass production and waste management, which would ideally be integrated into overall system models. Explanatory models (also referred to as mechanistic or process models) would provide the basis for a more robust system model, as these would be based on an understanding of specific processes. However, implementing such models at the system level may not always be practicable because of their complexity. For the area of biomass production, explanatory models were used to generate parameters and multivariable polynomial equations for basic models that are suitable for estimating the direction and magnitude of daily changes in canopy gas-exchange, harvest index, and production scheduling for both nominal and off-nominal growing conditions. c2004 COSPAR. Published by Elsevier Ltd. All rights reserved.

NASA Discipline Life Support Systems↗
NASA NTRS2005

Design Methods and Practices for Fault Prevention and Management in Spacecraft

Integrated Systems Health Management (ISHM) is intended to become a critical capability for all space, lunar and planetary exploration vehicles and systems at NASA. Monitoring and managing the health state of diverse components, subsystems, and systems is a difficult task that will become more challenging when implemented for long-term, evolving deployments. A key technical challenge will be to ensure that the ISHM technologies are reliable, effective, and low cost, resulting in turn in safe, reliable, and affordable missions. To ensure safety and reliability, ISHM functionality, decisions and knowledge have to be incorporated into the product lifecycle as early as possible, and ISHM must be considered as an essential element of models developed and used in various stages during system design. During early stage design, many decisions and tasks are still open, including sensor and measurement point selection, modeling and model-checking, diagnosis, signature and data fusion schemes, presenting the best opportunity to catch and prevent potential failures and anomalies in a cost-effective way. Using appropriate formal methods during early design, the design teams can systematically explore risks without committing to design decisions too early. However, the nature of ISHM knowledge and data is detailed, relying on high-fidelity, detailed models, whereas the earlier stages of the product lifecycle utilize low-fidelity, high-level models of systems and their functionality. We currently lack the tools and processes necessary for integrating ISHM into the vehicle system/subsystem design. As a result, most existing ISHM-like technologies are retrofits that were done after the system design was completed. It is very expensive, and sometimes futile, to retrofit a system health management capability into existing systems. Last-minute retrofits result in unreliable systems, ineffective solutions, and excessive costs (e.g., Space Shuttle TPS monitoring which was considered only after 110 flights and the Columbia disaster). High false alarm or false negative rates due to substandard implementations hurt the credibility of the ISHM discipline. This paper presents an overview of the current state of ISHM design,and a review of formal design methods to make recommendations about possible approaches to enable the ISHM capabilities to be designed-in at the system-level, from the very beginning of the vehicle design process.

Tumer, Irem Y.↗
NASA NTRS2006

Propulsion IVHM Technology Experiment

The Propulsion IVHM Technology Experiment (PITEX) successfully demonstrated real-time fault detection and isolation of a virtual reusable launch vehicle (RLV) main propulsion system (MPS). Specifically, the PITEX research project developed and applied a model-based diagnostic system for the MPS of the X-34 RLV, a space-launch technology demonstrator. The demonstration was simulation-based using detailed models of the propulsion subsystem to generate nominal and failure scenarios during captive carry, which is the most safety-critical portion of the X-34 flight. Since no system-level testing of the X-34 Main Propulsion System (MPS) was performed, these simulated data were used to verify and validate the software system. Advanced diagnostic and signal processing algorithms were developed and tested in real time on flight-like hardware. In an attempt to expose potential performance problems, the PITEX diagnostic system was subjected to numerous realistic effects in the simulated data including noise, sensor resolution, command/valve talkback information, and nominal build variations. In all cases, the PITEX system performed as required. The research demonstrated potential benefits of model-based diagnostics, defined performance metrics required to evaluate the diagnostic system, and studied the impact of real-world challenges encountered when monitoring propulsion subsystems.

Chicatelli, Amy K.↗
NASA NTRS2006

An Efficient Approach for the Reliability Analysis of Phased-Mission Systems with Dependent Failures

We consider the reliability analysis of phased-mission systems with common-cause failures in this paper. Phased-mission systems (PMS) are systems supporting missions characterized by multiple, consecutive, and nonoverlapping phases of operation. System components may be subject to different stresses as well as different reliability requirements throughout the course of the mission. As a result, component behavior and relationships may need to be modeled differently from phase to phase when performing a system-level reliability analysis. This consideration poses unique challenges to existing analysis methods. The challenges increase when common-cause failures (CCF) are incorporated in the model. CCF are multiple dependent component failures within a system that are a direct result of a shared root cause, such as sabotage, flood, earthquake, power outage, or human errors. It has been shown by many reliability studies that CCF tend to increase a system's joint failure probabilities and thus contribute significantly to the overall unreliability of systems subject to CCF.We propose a separable phase-modular approach to the reliability analysis of phased-mission systems with dependent common-cause failures as one way to meet the above challenges in an efficient and elegant manner. Our methodology is twofold: first, we separate the effects of CCF from the PMS analysis using the total probability theorem and the common-cause event space developed based on the elementary common-causes; next, we apply an efficient phase-modular approach to analyze the reliability of the PMS. The phase-modular approach employs both combinatorial binary decision diagram and Markov-chain solution methods as appropriate. We provide an example of a reliability analysis of a PMS with both static and dynamic phases as well as CCF as an illustration of our proposed approach. The example is based on information extracted from a Mars orbiter project. The reliability model for this orbiter considers the various phases of Launch, Cruise, Mars Orbit Insertion, and Orbit. Some of the CCF for the orbiter in this mission include environmental effects, such as micrometeoroids, human operator errors, and software errors.

reliability analysis↗
NASA NTRS2010

Evaluation of a Guideline by Formal Modelling of Cruise Control System in Event-B

Recently a set of guidelines, or cookbook, has been developed for modelling and refinement of control problems in Event-B. The Event-B formal method is used for system-level modelling by defining states of a system and events which act on these states. It also supports refinement of models. This cookbook is intended to systematize the process of modelling and refining a control problem system by distinguishing environment, controller and command phenomena. Our main objective in this paper is to investigate and evaluate the usefulness and effectiveness of this cookbook by following it throughout the formal modelling of cruise control system found in cars. The outcomes are identifying the benefits of the cookbook and also giving guidance to its future users.

Yeganefard, Sanaz↗
NASA NTRS2010

The ICARE Method

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

Henke, Luke↗
NASA NTRS2013

Vehicle Integrated Prognostic Reasoner (VIPR) Metric Report

This document outlines a set of metrics for evaluating the diagnostic and prognostic schemes developed for the Vehicle Integrated Prognostic Reasoner (VIPR), a system-level reasoner that encompasses the multiple levels of large, complex systems such as those for aircraft and spacecraft. VIPR health managers are organized hierarchically and operate together to derive diagnostic and prognostic inferences from symptoms and conditions reported by a set of diagnostic and prognostic monitors. For layered reasoners such as VIPR, the overall performance cannot be evaluated by metrics solely directed toward timely detection and accuracy of estimation of the faults in individual components. Among other factors, overall vehicle reasoner performance is governed by the effectiveness of the communication schemes between monitors and reasoners in the architecture, and the ability to propagate and fuse relevant information to make accurate, consistent, and timely predictions at different levels of the reasoner hierarchy. We outline an extended set of diagnostic and prognostics metrics that can be broadly categorized as evaluation measures for diagnostic coverage, prognostic coverage, accuracy of inferences, latency in making inferences, computational cost, and sensitivity to different fault and degradation conditions. We report metrics from Monte Carlo experiments using two variations of an aircraft reference model that supported both flat and hierarchical reasoning.

Cornhill, Dennis↗
NASA NTRS2013

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM). This methodology and corresponding model, known as a Goal-Function Tree (GFT), provides a means to represent, decompose, and elaborate system goals and functions in a rigorous manner that connects directly to design through use of state variables that translate natural language requirements and goals into logical-physical state language. The state variable-based approach also provides the means to directly connect FM to the design, by specifying the range in which state variables must be controlled to achieve goals, and conversely, the failures that exist if system behavior go out-of-range. This in turn allows for the systems engineers and SHM/FM engineers to determine which state variables to monitor, and what action(s) to take should the system fail to achieve that goal. In sum, the GFT representation provides a unified approach to early-phase SE and FM development. This representation and methodology has been successfully developed and implemented using Systems Modeling Language (SysML) on the NASA Space Launch System (SLS) Program. It enabled early design trade studies of failure detection coverage to ensure complete detection coverage of all crew-threatening failures. The representation maps directly both to FM algorithm designs, and to failure scenario definitions needed for design analysis and testing. The GFT representation provided the basis for mapping of abort triggers into scenarios, both needed for initial, and successful quantitative analyses of abort effectiveness (detection and response to crew-threatening events).

Patterson, Jonathan D.↗
NASA NTRS2014

Control and Non-Payload Communications Generation 1 Prototype Radio Flight Test Report

Unmanned aircraft (UA) represent a new capability that will provide a variety of services in the Government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized because of the lack of a common understanding of what is required to safely operate Unmanned Aircraft Systems in the National Airspace System (UAS in the NAS). The desire and ability to fly UA is of increasing urgency. The application of UA to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UA to the NAS. Existing Federal Aviation Regulations, procedures, and technologies do not allow routine UA access to the NAS. Access to the NAS is hampered by challenges such as the lack of an onboard pilot to see and avoid other aircraft; the ability of a single pilot or operator to control multiple UA; the reliance on command and control (C2) links; the altitudes, speeds, and duration at which the aircraft fly; and the wide variation in UA size and performance. NASA is working with other Government agencies to provide solutions that reduce technical barriers and make access to the NAS routine. This goal will be accomplished through system-level integration of key concepts, technologies, or procedures and through demonstrations of these integrated capabilities in an operationally relevant environment. This project provides an opportunity to transition the acquired empirical data and knowledge to the Federal Aviation Administration and other stakeholders to help them define the requirements for routine UA access to the NAS.Radio communications channels for UA are currently managed through exceptions and use either Department of Defense frequencies for line-of-sight (LOS) and satellite-based communications links, low-power LOS links in amateur bands, or unlicensed Industrial/Scientific/Medical (ISM) frequencies. None of these frequency bands are designated for safety and regularity of flight. Only recently has radiofrequency (RF) spectrum been allocated by the International Telecommunications Union specifically for commercial UA C2, LOS communication (L-Band: 960 to 1164 MHz, and C-Band: 5030 to 5091 MHz). The safe and efficient integration of UA into the NAS requires the use of protected RF spectrum allocations and a new data communications system that is both secure and scalable to accommodate the potential growth of these new aircraft. Data communications for UA-referred to as control and non-payload communications (CNPC)-will be used to exchange information between a UA and a ground station (GS) to ensure safe, reliable, and effective UA flight operation. The focus of this effort is on validating and allocating new RF spectrum and data link communications to enable civil UA integration into the NAS. Through a cost-sharing cooperative agreement with Rockwell Collins, Inc., the NASA Glenn Research Center is exploring and performing the necessary development steps to realize a prototype UA CNPC system. These activities include investigating signal waveforms and access techniques, developing representative CNPC radio hardware, and executing relevant testing and validation activities. There is no intent to manufacture the CNPC end product, rather the goals are to study, demonstrate, and validate a typical CNPC system that will allow safe and efficient communications within the L-Band and C-Band spectrum allocations. The system is addressing initial "seed" requirements from RTCA, Inc., Special Committee 203 (SC-203) and is on a path to Federal Aviation Administration certification. This report provides results from the flight testing campaign of the Rockwell Collins Generation 1 prototype radio, referred hereafter as the "radio." The radio sets operate within the 960- to 977-MHz frequency band with both air and ground radios using identical hardware. Flight tests involved one aircraft and one GS. Results include discussion of aircraft flight paths and associated radio performance.

Shalkhauser, Kurt A.↗
NASA NTRS2015

Nano-ADEPT Aeroloads Wind Tunnel Test

Analysis completed since the test suggests that all test objectives were met– This claim will be verified in the coming weeks as the data is examined further– Final disposition of test objective success will be documented in a final reportsubmitted to NASA stakeholders (early August 2015)– Expect conference paper in early 2016• Data products and observations made during testing will be used to refinecomputational models of Nano-ADEPT• Carbon fabric relaxed from its pre-test state during the test– System-level tolerance for relaxation will be driven by destination-specific andmission-specific aerothermal and aerodynamic requirements• Bonus experiment of asymmetric shape demonstrates that an asymmetricdeployable blunt body can be used to generate measureable lift– With a strut actuation system and a robust GN&C algorithm, this effect could beused to steer a blunt body at hypersonic speeds to aid precision landing

atmospheric entry↗