Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems Architecture”

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 91 records · Page 5

Critical early mission design considerations for lunar data systems architecture

This paper outlines recent early mission design activites for a lunar data systems architecture. Each major functional element is shown to be strikingly similar when viewed in a common reference system. While this similarity probably deviates with lower levels of decomposition, the sub-functions can always be arranged into similar and dissimilar categories. Similar functions can be implemented as objects - implemented once and reused several times like today's advanced integrated circuits. This approach to mission data systems, applied to other NASA programs, may result in substantial agency implementation and maintenance savings. In today's zero-sum-game budgetary environment, this approach could help to enable a lunar exploration program in the next decade. Several early mission studies leading to such an object-oriented data systems design are recommended.

Hei, Donald J., Jr.↗

A temporal analysis and response to nitrate availability of 3D root system architecture in diverse pennycress (Thlaspi arvense L.) accessions

Introduction Roots have a central role in plant resource capture and are the interface between the plant and the soil that affect multiple ecosystem processes. Field pennycress ( Thlaspi arvense L.) is a diploid annual cover crop species that has potential utility for reducing soil erosion and nutrient losses; and has rich seeds (30-35% oil) amenable to biofuel production and as a protein animal feed. The objective of this research was to (1) precisely characterize root system architecture and development, (2) understand plastic responses of pennycress roots to nitrate nutrition, (3) and determine genotypic variance available in root development and nitrate plasticity. Methods Using a root imaging and analysis pipeline, the 4D architecture of the pennycress root system was characterized under four nitrate regimes, ranging from zero to high nitrate concentrations. These measurements were taken at four time points (days 5, 9, 13, and 17 after sowing). Results Significant nitrate condition response and genotype interactions were identified for many root traits, with the greatest impact observed on lateral root traits. In trace nitrate conditions, a greater lateral root count, length, density, and a steeper lateral root angle was observed compared to high nitrate conditions. Additionally, genotype-by-nitrate condition interaction was observed for root width, width:depth ratio, mean lateral root length, and lateral root density. Discussion These findings illustrate root trait variance among pennycress accessions. These traits could serve as targets for breeding programs aimed at developing improved cover crops that are responsive to nitrate, leading to enhanced productivity, resilience, and ecosystem service.

59 BASIC BIOLOGICAL SCIENCES↗

Advanced satellite system architecture for VSATs with ISDN compatibility

This paper describes a future communications satellite system architecture concept which allows the use of Very Small Aperature Terminals (VSATs) of 1.2 m to 1.8 m diameter and which provides access according to the international Integrated Services Digital Network (ISDN) standard. This satellite system design could make dial-up integrated voice and data service available nationwide and perhaps worldwide. The paper gives a conceptual system design based on the year 1995 technology for the communications satellite, the earth terminal, and the ground-based master control station and interface to the terrestrial ISDN network.

Jorasch, Ronald E.↗

Phenome‐to‐genome insights for evaluating root system architecture in field studies of maize

Abstract Understanding the genetic basis of root system architecture (RSA) in crops requires innovative approaches that enable both high‐throughput and precise phenotyping in field conditions. In this study, we evaluated multiple phenotyping and analytical frameworks for quantifying RSA in mature, field‐grown maize in three field experiments. We used forward and reverse genetic approaches to evaluate >1700 maize root crowns, including a diversity panel, a biparental mapping population, and maize mutant and wild‐type alleles at two known RSA genes,DEEPER ROOTING 1(DRO1) andRootless1(Rt1). We show the utility of increasing the dimensionality of traditional two‐dimensional (2D) techniques, referred to as the “2D multi‐view” method, to improve the capture of whole root system information for mapping genetic variation influencing RSA. Comparison of univariate and multivariate genome‐wide association study (GWAS) approaches revealed that multivariate traits were effective at dissecting complex RSA phenotypes and identifying pleiotropic quantitative trait loci (QTLs). Overall, three‐dimensional (3D) root models generated from X‐ray computed tomography and digital phenotyping captured a larger proportion of RSA trait variations compared to other methods of root phenotyping, as evidenced by both genome‐wide and single‐gene analyses. Among the individual root traits, root pulling force emerged as a highly heritable estimate of RSA that identified the largest number of shared QTLs with 3D phenotypes. Our study shows that integrating complementary phenotyping technologies helps to provide a more comprehensive understanding of the genetic architecture of RSA in field‐grown maize.

Genetics & Heredity↗

Multi-Mission System Architecture Platform: Design and Verification of the Remote Engineering Unit

The Multi-Mission System Architecture Platform (MSAP) represents an effort to bolster efficiency in the spacecraft design process. By incorporating essential spacecraft functionality into a modular, expandable system, the MSAP provides a foundation on which future spacecraft missions can be developed. Once completed, the MSAP will provide support for missions with varying objectives, while maintaining a level of standardization that will minimize redesign of general system components. One subsystem of the MSAP, the Remote Engineering Unit (REU), functions by gathering engineering telemetry from strategic points on the spacecraft and providing these measurements to the spacecraft's Command and Data Handling (C&DH) subsystem. Before the MSAP Project reaches completion, all hardware, including the REU, must be verified. However, the speed and complexity of the REU circuitry rules out the possibility of physical prototyping. Instead, the MSAP hardware is designed and verified using the Verilog Hardware Definition Language (HDL). An increasingly popular means of digital design, HDL programming provides a level of abstraction, which allows the designer to focus on functionality while logic synthesis tools take care of gate-level design and optimization. As verification of the REU proceeds, errors are quickly remedied, preventing costly changes during hardware validation. After undergoing the careful, iterative processes of verification and validation, the REU and MSAP will prove their readiness for use in a multitude of spacecraft missions.

Sartori, John↗

System architectures for telerobotic research

Several activities are performed related to the definition and creation of telerobotic systems. The effort and investment required to create architectures for these complex systems can be enormous; however, the magnitude of process can be reduced if structured design techniques are applied. A number of informal methodologies supporting certain aspects of the design process are available. More recently, prototypes of integrated tools supporting all phases of system design from requirements analysis to code generation and hardware layout have begun to appear. Activities related to system architecture of telerobots are described, including current activities which are designed to provide a methodology for the comparison and quantitative analysis of alternative system architectures.

Harrison, F. Wallace↗

TROPIX Power System Architecture

This document contains results obtained in the process of performing a power system definition study of the TROPIX power management and distribution system (PMAD). Requirements derived from the PMADs interaction with other spacecraft systems are discussed first. Since the design is dependent on the performance of the photovoltaics, there is a comprehensive discussion of the appropriate models for cells and arrays. A trade study of the array operating voltage and its effect on array bus mass is also presented. A system architecture is developed which makes use of a combination of high efficiency switching power convertors and analog regulators. Mass and volume estimates are presented for all subsystems.

Manner, David B.↗

Space Assembly of Large Structural System Architectures (SALSSA)

Developing a robust capability for Space Assembly of Large Spacecraft Structural System Architectures (SALSSA) has the potential to drastically increase the capabilities and performance of future space missions and spacecraft while significantly reducing their cost. Currently, NASA architecture studies and space science decadal surveys identify new missions that would benefit from SALSSA capabilities, and the technologies that support SALSSA are interspersed throughout the fourteen NASA Technology Roadmaps. However, a major impediment to the strategic development of cross-cutting SALSSA technologies is the lack of an integrated and comprehensive compilation of the necessary information. This paper summarizes the results of a small study that used an integrated approach to formulate a SALSSA roadmap and associated plan for developing key SALSSA technologies.

Dorsey, John T.↗

NASA Laboratory telerobotic manipulator control system architecture

In support of the National Aeronautics and Space Administration (NASA) goals to increase the utilization of dexterous robotic systems in space, the Oak Ridge National Laboratory (ORNL) has developed the Laboratory Telerobotic Manipulator (LTM) system. It is a dexterous, dual-arm, force reflecting teleoperator system with robotic features for NASA ground-based research. This paper describes the overall control system architecture, including both the hardware and software. The control system is a distributed, modular, and hierarchical design with flexible expansion capabilities for future enhancements of both the hardware and software.

Rowe, J. C.↗

NASA Laboratory Telerobotic Manipulator control system architecture

In support of the National Aeronautics and Space Administration (NASA) goals to increase the utilization of dexterous robotic systems in space, the Oak Ridge National Laboratory (ORNL) has developed the Laboratory Telerobotic Manipulator (LTM) system. It is a dexterous, dual-arm, force reflecting teleoperator system with robotic features for NASA ground-based research. This paper describes the overall control system architecture, including both the hardware and software. The control system is a distributed, modular, and hierarchical design with flexible expansion capabilities for future enhancements of both the hardware and software.

Rowe, J. C.↗

Control System Architectures, Technologies and Concepts for Near Term and Future Human Exploration of Space

Technologies that facilitate the design and control of complex, hybrid, and resource-constrained systems are examined. This paper focuses on design methodologies, and system architectures, not on specific control methods that may be applied to life support subsystems. Honeywell and Boeing have estimated that 60-80Y0 of the effort in developing complex control systems is software development, and only 20-40% is control system development. It has also been shown that large software projects have failure rates of as high as 50-65%. Concepts discussed include the Unified Modeling Language (UML) and design patterns with the goal of creating a self-improving, self-documenting system design process. Successful architectures for control must not only facilitate hardware to software integration, but must also reconcile continuously changing software with much less frequently changing hardware. These architectures rely on software modules or components to facilitate change. Architecting such systems for change leverages the interfaces between these modules or components.

Boulanger, Richard↗

A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost-effective set of multimission MOS products and services.

Estefan, Jeff A.↗

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

Ground System Architecture↗

PLEXUS: A Pattern-Oriented Runtime System Architecture for Resilient Extreme-Scale High-Performance Computing Systems

For high-performance computing (HPC) system designers and users, meeting the myriad challenges of next-generation exascale supercomputing systems requires rethinking their approach to application and system software design. Among these challenges, providing resiliency and stability to the scientific applications in the presence of high fault rates requires new approaches to software architecture and design. As HPC systems become increasingly complex, they require intricate solutions for detection and mitigation for various modes of faults and errors that occur in these large-scale systems, as well as solutions for failure recovery. These resiliency solutions often interact with and affect other system properties, including application scalability, power and energy efficiency. Therefore, resilience solutions for HPC systems must be thoughtfully engineered and deployed.In previous work, we developed the concept of resilience design patterns, which consist of templated solutions based on well-established techniques for detection, mitigation and recovery. In this paper, we use these patterns as the foundation to propose new approaches to designing runtime systems for HPC systems. The instantiation of these patterns within a runtime system enables flexible and adaptable end-to-end resiliency solutions for HPC environments. The paper describes the architecture of the runtime system, named Plexus, and the strategies for dynamically composing and adapting pattern instances under runtime control. This runtime-based approach enables actively balancing the cost-benefit trade-off between performance overhead and protection coverage of the resilience solutions. Based on a prototype implementation of PLEXUS, we demonstrate the resiliency and performance gains achieved by the pattern-based runtime system for a parallel linear solver application.

Hukerikar, Saurabh↗

Integrated airframe/propulsion control system architectures (IAPSA) study

Three integrated airframe/propulsion control system (ACS) architectures have been developed and are discussed. The baseline is a state of the art design which integrates autonomous propusion control and airframe flight control systems. Two alternate ACSs for the 1990s using emerging technologies were developed and are compared with each other and the baseline. One of these, designated D/D, uses parallel distributed processing, while the other, designated C/D, centralizes the processing into two centrally located redundant electronics complex. The C/D system locates all redundant computing elements and interfacing electronics in two boxes with optical sensor and actuation devices optically connected to the two boxes. Evaluation reveals the C/D architecture to be better than the other two in five of ten categories; D/D is superior in only two of the ten.

Stern,, A. d.↗