Search NASA⌕ Search

SEARCH · Search NASA

Results for “Component 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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS1992

Space micro-guidance and control - Applications and architectures

The features and the components of a new microscale guidance, navigation, and control (GN&C) system for future space systems are discussed. An approach is described for the utilization of new microengineering technologies for achieving major reductions in the GN&C system's mass, size, power, and costs. The micro-GN&C system and the component concepts include microactuated adaptive optics, micromachined inertial sensors, fiberoptic data nets with light-power transmission, and VLSI microcomputers. The GN&C system will be applied in microspacecraft, microlanders, microrovers, remote sensing platforms, interferometers, and deployable reflectors.

Mettler, Edward↗
NASA NTRS1990

Habitability: CAMELOT 4

During 1988 to 1989 the NASA/USRA Advanced Design Program sponsored research and design efforts aimed at developing habitability criteria and at defining a habitability concept as a useful tool in understanding and evaluating dwellings for prolonged stays in extraterrestrial space. The Circulating Auto sufficient Mars-Earth Luxurious Orbital Transport (CAMELOT) was studied as a case in which the students would try to enhance the quality of life of the inhabitants by applying architectural design methodology. The study proposed 14 habitability criteria considered necessary to fulfill the defined habitability concept, which is that state of equilibrium that results from the interaction between components of the Individual Architecture Mission Complex, which allows a person to sustain physiological homeostatis, adequate performance, and acceptable social relationships. Architecture, design development, refinements and revisions to improve the quality of life, new insights on artificial gravity, form and constitution problems, and the final design concept are covered.

Alequin, W.↗
NASA NTRS1991

Architecture for Survivable System Processing (ASSP)

The Architecture for Survivable System Processing (ASSP) Program is a multi-phase effort to implement Department of Defense (DOD) and commercially developed high-tech hardware, software, and architectures for reliable space avionics and ground based systems. System configuration options provide processing capabilities to address Time Dependent Processing (TDP), Object Dependent Processing (ODP), and Mission Dependent Processing (MDP) requirements through Open System Architecture (OSA) alternatives that allow for the enhancement, incorporation, and capitalization of a broad range of development assets. High technology developments in hardware, software, and networking models, address technology challenges of long processor life times, fault tolerance, reliability, throughput, memories, radiation hardening, size, weight, power (SWAP) and security. Hardware and software design, development, and implementation focus on the interconnectivity/interoperability of an open system architecture and is being developed to apply new technology into practical OSA components. To insure for widely acceptable architecture capable of interfacing with various commercial and military components, this program provides for regular interactions with standardization working groups (e.g.) the International Standards Organization (ISO), American National Standards Institute (ANSI), Society of Automotive Engineers (SAE), and Institute of Electrical and Electronic Engineers (IEEE). Selection of a viable open architecture is based on the widely accepted standards that implement the ISO/OSI Reference Model.

Wood, Richard J.↗
NASA NTRS1992

Formalization and visualization of domain-specific software architectures

This paper describes a domain-specific software design system based on the concepts of software architectures engineering and domain-specific models and languages. In this system, software architectures are used as high level abstractions to formulate a domain-specific software design. The software architecture serves as a framework for composing architectural fragments (e.g., domain objects, system components, and hardware interfaces) that make up the knowledge (or model) base for solving a problem in a particular application area. A corresponding software design is generated by analyzing and describing a system in the context of the software architecture. While the software architecture serves as the framework for the design, this concept is insufficient by itself for supplying the additional details required for a specific design. Additional domain knowledge is still needed to instantiate components of the architecture and develop optimized algorithms for the problem domain. One possible way to obtain the additional details is through the use of domain-specific languages. Thus, the general concept of a software architecture and the specific design details provided by domain-specific languages are combined to create what can be termed a domain-specific software architecture (DSSA).

Bailor, Paul D.↗
NASA NTRS2021

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗
NASA NTRS2006

Airport Surface Network Architecture Definition

Currently, airport surface communications are fragmented across multiple types of systems. These communication systems for airport operations at most airports today are based dedicated and separate architectures that cannot support system-wide interoperability and information sharing. The requirements placed upon the Communications, Navigation, and Surveillance (CNS) systems in airports are rapidly growing and integration is urgently needed if the future vision of the National Airspace System (NAS) and the Next Generation Air Transportation System (NGATS) 2025 concept are to be realized. To address this and other problems such as airport surface congestion, the Space Based Technologies Project s Surface ICNS Network Architecture team at NASA Glenn Research Center has assessed airport surface communications requirements, analyzed existing and future surface applications, and defined a set of architecture functions that will help design a scalable, reliable and flexible surface network architecture to meet the current and future needs of airport operations. This paper describes the systems approach or methodology to networking that was employed to assess airport surface communications requirements, analyze applications, and to define the surface network architecture functions as the building blocks or components of the network. The systems approach used for defining these functions is relatively new to networking. It is viewing the surface network, along with its environment (everything that the surface network interacts with or impacts), as a system. Associated with this system are sets of services that are offered by the network to the rest of the system. Therefore, the surface network is considered as part of the larger system (such as the NAS), with interactions and dependencies between the surface network and its users, applications, and devices. The surface network architecture includes components such as addressing/routing, network management, network performance and security.

Nguyen, Thanh C.↗
NASA NTRS2007

In-Plane Cracking Behavior and Ultimate Strength for 2D Woven and Braided Melt-Infiltrated SiC/SiC Composites Tensile Loaded in Off-Axis Fiber Directions

The tensile mechanical properties of ceramic matrix composites (CMC) in directions off the primary axes of the reinforcing fibers are important for architectural design of CMC components that are subjected to multi-axial stress states. In this study, 2D-woven melt-infiltrated (MI) SiC/SiC composite panels with balanced fiber content in the 0 degree and 90 degree directions were tensile loaded in-plane in the 0 degree direction and at 45 degree to this direction. In addition, a 2D triaxially-braided MI composite panel with balanced fiber content in the plus or minus 67 degree bias directions and reduced fiber content in the axial direction was tensile loaded perpendicular to the axial direction tows (i.e., 23 degrees from the bias fibers). Stress-strain behavior, acoustic emission, and optical microscopy were used to quantify stress-dependent matrix cracking and ultimate strength in the panels. It was observed that both off-axis loaded panels displayed higher composite onset stresses for through-thickness matrix cracking than the 2D-woven 0/90 panels loaded in the primary 0 degree direction. These improvements for off-axis cracking strength can in part be attributed to higher effective fiber fractions in the loading direction, which in turn reduces internal stresses on critical matrix flaws for a given composite stress. Also for the 0/90 panel loaded in the 45 degree direction, an improved distribution of matrix flaws existed due to the absence of fiber tows perpendicular to the loading direction. In addition, for the +67/0/-67 braided panel, the axial tows perpendicular to the loading direction were not only low in volume fraction, but were also were well separated from one another. Both off-axis oriented panels also showed relatively good ultimate tensile strength when compared to other off-axis oriented composites in the literature, both on an absolute strength basis as well as when normalized by the average fiber strength within the composites. Initial implications are discussed for constituent and architecture design to improve the directional cracking of SiC/SiC CMC components with MI matrices.

Morscher, Gregory N.↗
NASA NTRS2007

Development of Network-based Communications Architectures for Future NASA Missions

Since the Vision for Space Exploration (VSE) announcement, NASA has been developing a communications infrastructure that combines existing terrestrial techniques with newer concepts and capabilities. The overall goal is to develop a flexible, modular, and extensible architecture that leverages and enhances terrestrial networking technologies that can either be directly applied or modified for the space regime. In addition, where existing technologies leaves gaps, new technologies must be developed. An example includes dynamic routing that accounts for constrained power and bandwidth environments. Using these enhanced technologies, NASA can develop nodes that provide characteristics, such as routing, store and forward, and access-on-demand capabilities. But with the development of the new infrastructure, challenges and obstacles will arise. The current communications infrastructure has been developed on a mission-by-mission basis rather than an end-to-end approach; this has led to a greater ground infrastructure, but has not encouraged communications between space-based assets. This alone provides one of the key challenges that NASA must encounter. With the development of the new Crew Exploration Vehicle (CEV), NASA has the opportunity to provide an integration path for the new vehicles and provide standards for their development. Some of the newer capabilities these vehicles could include are routing, security, and Software Defined Radios (SDRs). To meet these needs, the NASA/Glenn Research Center s (GRC) Network Emulation Laboratory (NEL) has been using both simulation and emulation to study and evaluate these architectures. These techniques provide options to NASA that directly impact architecture development. This paper identifies components of the infrastructure that play a pivotal role in the new NASA architecture, develops a scheme using simulation and emulation for testing these architectures and demonstrates how NASA can strengthen the new infrastructure by implementing these concepts.

Slywczak, Richard A.↗
NASA NTRS2003

Advantages of Brahms for Specifying and Implementing a Multiagent Human-Robotic Exploration System

We have developed a model-based, distributed architecture that integrates diverse components in a system designed for lunar and planetary surface operations: an astronaut's space suit, cameras, all-terrain vehicles, robotic assistant, crew in a local habitat, and mission support team. Software processes ('agents') implemented in the Brahms language, run on multiple, mobile platforms. These mobile agents interpret and transform available data to help people and robotic systems coordinate their actions to make operations more safe and efficient. The Brahms-based mobile agent architecture (MAA) uses a novel combination of agent types so the software agents may understand and facilitate communications between people and between system components. A state-of-the-art spoken dialogue interface is integrated with Brahms models, supporting a speech-driven field observation record and rover command system. An important aspect of the methodology involves first simulating the entire system in Brahms, then configuring the agents into a runtime system Thus, Brahms provides a language, engine, and system builder's toolkit for specifying and implementing multiagent systems.

Clancey, William J.↗
NASA NTRS2002

Brahms Mobile Agents: Architecture and Field Tests

We have developed a model-based, distributed architecture that integrates diverse components in a system designed for lunar and planetary surface operations: an astronaut's space suit, cameras, rover/All-Terrain Vehicle (ATV), robotic assistant, other personnel in a local habitat, and a remote mission support team (with time delay). Software processes, called agents, implemented in the Brahms language, run on multiple, mobile platforms. These mobile agents interpret and transform available data to help people and robotic systems coordinate their actions to make operations more safe and efficient. The Brahms-based mobile agent architecture (MAA) uses a novel combination of agent types so the software agents may understand and facilitate communications between people and between system components. A state-of-the-art spoken dialogue interface is integrated with Brahms models, supporting a speech-driven field observation record and rover command system (e.g., return here later and bring this back to the habitat ). This combination of agents, rover, and model-based spoken dialogue interface constitutes a personal assistant. An important aspect of the methodology involves first simulating the entire system in Brahms, then configuring the agents into a run-time system.

Clancey, William J.↗
NASA NTRS2007

Preliminary Performance Analyses of the Constellation Program ARES 1 Crew Launch Vehicle

By the time NASA's Exploration Systems Architecture Study (ESAS) report had been released to the public in December 2005, engineers at NASA's Marshall Space Flight Center had already initiated the first of a series of detailed design analysis cycles (DACs) for the Constellation Program Crew Launch Vehicle (CLV), which has been given the name Ares I. As a major component of the Constellation Architecture, the CLV's initial role will be to deliver crew and cargo aboard the newly conceived Crew Exploration Vehicle (CEV) to a staging orbit for eventual rendezvous with the International Space Station (ISS). However, the long-term goal and design focus of the CLV will be to provide launch services for a crewed CEV in support of lunar exploration missions. Key to the success of the CLV design effort and an integral part of each DAC is a detailed performance analysis tailored to assess nominal and dispersed performance of the vehicle, to determine performance sensitivities, and to generate design-driving dispersed trajectories. Results of these analyses provide valuable design information to the program for the current design as well as provide feedback to engineers on how to adjust the current design in order to maintain program goals. This paper presents a condensed subset of the CLV performance analyses performed during the CLV DAC-1 cycle. Deterministic studies include development of the CLV DAC-1 reference trajectories, identification of vehicle stage impact footprints, an assessment of launch window impacts to payload performance, and the computation of select CLV payload partials. Dispersion studies include definition of input uncertainties, Monte Carlo analysis of trajectory performance parameters based on input dispersions, assessment of CLV flight performance reserve (FPR), assessment of orbital insertion accuracy, and an assessment of bending load indicators due to dispersions in vehicle angle of attack and side slip angle. A short discussion of the various customers for the dispersion results, along with results and ramifications of each study, are also provided.

Phillips, Mark↗
NASA NTRS2009

Ares V: Shifting the Payload Design Paradigm

NASA's Ares V heavy-lift cargo launch vehicle is being designed send more crew and cargo to more places on the lunar surface than the 1960s-era Apollo program and provide ongoing support to a permanent lunar outpost. In addition to that role, however, its unmatched mass and volume capability represent a global asset for exploration, science, and commerce. The Ares V also is an enabler of a large class of space missions not thought possible by scientists and engineers since the Saturn V program ended over 30 years ago. Compared to current systems, it will offer approximately 5 times the mass and volume to most orbits and locations. This should allow prospective mission planners to build robust payloads with margins that are 3 to 5 times the industry norm. The space inside the planned payload shroud has enough usable volume to launch the volumetric equivalent of approximately 10 Apollo Lunar Excursion Modules or approximately 5 equivalent Hubble Space Telescopes. This mass and volume capability to Low Earth Orbit enables a host of new scientific and observation platforms, such as telescopes, satellites, planetary and solar missions, as well as being able to provide the lift for future large in-space infrastructure missions, such as space based power and mining, Earth asteroid defense, propellant depots, etc. The Ares V team is engaging the potential payload community now, 2-3 years before System Requirements Review, in order to better understand the potential limitations and or additional requirements that could be added to the Ares V from the mission planning community. If a viable mission is determined and added to the Ares V as a design case, tradeoffs will be conducted to determine if other mission design requirements can be included in the system. Multiple shroud options for the Ares V have been analyzed to identify their impact on performance. Ares V is in a conceptual design stage prior to a formal design phase. The initial concept for the cargo launch vehicle (CaLV) that would later be dubbed "Ares V" was produced by the Exploration Systems Architecture Study in 2005. Since then, it has evolved through hundreds of concepts. The current point-of-departure (POD) concept was approved during the Lunar Capabilities Concept Review/Ares V Mission Concept Review in June 2008. This reference concept serves as a starting point for a renewed set of design trades and detailed analysis into its interaction with the other components of the Constellation architecture and existing launch infrastructure. This paper will discuss the Ares V design evolution, the most recent point-of-departure concept, and its capabilities to support future science missions.

Summrall, Phil↗
NASA NTRS1991

Demonstration of automated proximity and docking technologies

An autodock was demonstrated using straightforward techniques and real sensor hardware. A simulation testbed was established and validated. The sensor design was refined with improved optical performance and image processing noise mitigation techniques, and the sensor is ready for production from off-the-shelf components. The autonomous spacecraft architecture is defined. The areas of sensors, docking hardware, propulsion, and avionics are included in the design. The Guidance Navigation and Control architecture and requirements are developed. Modular structures suitable for automated control are used. The spacecraft system manager functions including configuration, resource, and redundancy management are defined. The requirements for autonomous spacecraft executive are defined. High level decisionmaking, mission planning, and mission contingency recovery are a part of this. The next step is to do flight demonstrations. After the presentation the following question was asked. How do you define validation? There are two components to validation definition: software simulation with formal and vigorous validation, and hardware and facility performance validated with respect to software already validated against analytical profile.

Anderson, Robert L.↗
NASA NTRS2019

Reliability Requirements and Research Strategies for Urban Air Mobility Propulsion

An emerging new mission for aeronautics is Urban Air Mobility (UAM), a concept for air transportation around metropolitan areas with passenger-carrying operations. UAM vehicles must be capable of vertical take-off and landing, and this requirement presents unique technical challenges for electric and hybrid-based vertical take-off and landing (eVTOL). A critical challenge for UAM market growth is to gain public acceptance for being as safe as - or safer than - commercial air travel and automotive transportation. There is a lack of data for propulsion systems, components, and the associated thermal management systems for UAM eVTOL propulsion systems. The new mission, new propulsion system concepts, safety criticality of propulsion component performance during vertical take-off and lift operations, and lack of data presents many research challenges and opportunities. NASA has developed and published UAM vehicle concept studies. For a subset of the said concept vehicles, NASA has contracted for a study to identify failure modes and hazards associated with the propulsion systems of the concept vehicles and to perform functional hazard analyses (FHA) and failure modes and effects criticality analyses (FMECA) for each. From the completed study results, it was recommended for NASA to support research toward developing electric/hybrid-electric propulsion components with improved reliability and to explore powertrain architectures that can take advantage of higher reliability components to achieve inherent air-vehicle safety. NASA has started a research effort for UAM propulsion with a focus toward improving safety and reliability. Recent results and research strategy will be discussed toward the goals by means of: 1) improving individual component reliability through advanced materials and design methods, 2) improving the thermal management system, and 3) designing propulsion system architectures to provide inherent UAM vehicle safety.

Krantz, Timothy↗
NASA NTRS2020

NASA SpaceCube Intelligent Multi-Purpose System for Enabling Remote Sensing, Communication, and Navigation in Mission Architectures

New, innovative CubeSat mission concepts demand modern capabilities such as artificial intelligence and autonomy, constellation coordination, fault mitigation, and robotic servicing –all of which require vastly more processing resources than legacy systems are capable of providing. Enabling these domains within a scalable, configurable processing architecture is advantageous because it also allows for the flexibility to address varying mission roles, such as a command and data-handling system, a high-performance application processor extension, a guidance and navigation solution, or an instrument/sensor interface. This paper describes the NASA SpaceCube Intelligent Multi-Purpose System (IMPS), which allows mission developers to mix-and-match 1U (10 cm × 10 cm) CubeSat payloads configured for mission-specific needs. The central enabling component of the system architecture to address these concerns is the SpaceCube v3.0 Mini Processor. This single-board computer features the 20nm Xilinx Kintex UltraScale FPGA combined with a radiation-hardened FPGA monitor, and extensive IO to integrate and interconnect varying cards within the system. To unify the re-usable designs within this architecture, the CubeSat Card Standard was developed to guide design of 1U cards. This standard define spinout configurations, mechanical, and electrical specifications for 1U CubeSat cards, allowing the backplane and mechanical enclosure to be easily extended. NASA has developed several cards adhering to the standard (System-on-Chip, power card, etc.), which allows the flexibility to configure a payload from a common catalog of cards.

Advanced Avionics, Hybrid Processing, Data Process↗
NASA NTRS1988

An architecture for integrating distributed and cooperating knowledge-based Air Force decision aids

MITRE has been developing a Knowledge-Based Battle Management Testbed for evaluating the viability of integrating independently-developed knowledge-based decision aids in the Air Force tactical domain. The primary goal for the testbed architecture is to permit a new system to be added to a testbed with little change to the system's software. Each system that connects to the testbed network declares that it can provide a number of services to other systems. When a system wants to use another system's service, it does not address the server system by name, but instead transmits a request to the testbed network asking for a particular service to be performed. A key component of the testbed architecture is a common database which uses a relational database management system (RDBMS). The RDBMS provides a database update notification service to requesting systems. Normally, each system is expected to monitor data relations of interest to it. Alternatively, a system may broadcast an announcement message to inform other systems that an event of potential interest has occurred. Current research is aimed at dealing with issues resulting from integration efforts, such as dealing with potential mismatches of each system's assumptions about the common database, decentralizing network control, and coordinating multiple agents.

Nugent, Richard O.↗
NASA NTRS2009

ARTEMIS: Ares Real Time Environments for Modeling, Integration, and Simulation

This slide presentation reviews the use of ARTEMIS in the development and testing of the ARES launch vehicles. Ares Real Time Environment for Modeling, Simulation and Integration (ARTEMIS) is the real time simulation supporting Ares I hardware-in-the-loop (HWIL) testing. ARTEMIS accurately models all Ares/Orion/Ground subsystems which interact with Ares avionics components from pre-launch through orbit insertion The ARTEMIS System integration Lab, and the STIF architecture is reviewed. The functional components of ARTEMIS are outlined. An overview of the models and a block diagram is presented.

Hughes, Ryan↗