Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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 1,675 records · Page 93

Requirements for an Integrated UAS CNS Architecture

Communications, Navigation and Surveillance (CNS) requirements must be developed in order to establish a CNS architecture supporting Unmanned Air Systems integration in the National Air Space (UAS in the NAS). These requirements must address cybersecurity, future communications, satellite-based navigation and APNT, and scalable surveillance and situational awareness. CNS integration, consolidation and miniaturization requirements are also important to support the explosive growth in small UAS deployment. Air Traffic Management (ATM) must also be accommodated to support critical Command and Control (C2) for Air Traffic Controllers (ATC). This document therefore presents UAS CNS requirements that will guide the architecture.

Templin, Fred L.↗

150 kW Class Solar Electric Propulsion Spacecraft Power Architecture Model

The National Aeronautics and Space Administration (NASA) Solar Electric Propulsion Technology Demonstration Mission (SEP TDM), in conjunction with PC Krause and Associates, has created a Simulink-based power architecture model for a 50 kilo-Watt (kW) solar electric propulsion system. NASA has extended this model to investigate 150 kW solar electric propulsion systems. Increasing the power capability to 150 kW is an intermediate step to the anticipated power requirements for Mars and other deep space applications. The high-power solar electric propulsion capability has been identified as a critical part of NASA’s future beyond-low-Earth-orbit for human-crewed exploration missions. This paper presents four versions of a 150 kW architecture, simulation results, and a discussion of their merits.

Power Control↗

150 kW Class Solar Electric Propulsion Spacecraft Power Architecture Model

The National Aeronautics and Space Administration (NASA) Solar Electric Propulsion Technology Demonstration Mission in conjunction with PC Krause and Associates has created a Simulink-based power architecture model for a 50 kilo-Watt (kW) solar electric propulsion system. NASA has extended this model to investigate 150 kW solar electric propulsion systems. Increasing the power system capability from 50 kW to 150 kW better aligns with the anticipated power requirements for Mars and other deep space explorations. The high-power solar electric propulsion capability has been identified as a critical part of NASAs future beyond-low-Earth-orbit for human-crewed exploration missions. This paper presents multiple 150 kW architectures, simulation results, and a discussion of their merits.

Power Control↗

Water Recovery System Architecture and Operational Concepts to Accommodate Dormancy

Future manned missions beyond low Earth orbit will include intermittent periods of extended dormancy. The mission requirement includes the capability for life support systems to support crew activity, followed by a dormant period of up to one year, and subsequently for the life support systems to come back online for additional crewed missions. NASA personnel are evaluating the architecture and operational concepts that will allow the Water Recovery System (WRS) to support such a mission. Dormancy could be a critical issue due to concerns with microbial growth or chemical degradation that might prevent water systems from operating properly when the crewed mission began. As such, it is critical that the water systems be designed to accommodate this dormant period. This paper identifies dormancy issues, concepts for updating the WRS architecture and operational concepts that will enable the WRS to support the dormancy requirement.

Carter, Layne↗

A New Architecture for Visualization: Open Mission Control Technologies

Open Mission Control Technologies (MCT) is a new architecture for visualisation of mission data. Driven by requirements for new mission capabilities, including distributed mission operations, access to data anywhere, customization by users, synthesis of multiple data sources, and flexibility for multi-mission adaptation, Open MCT provides users with an integrated customizable environment. Developed at NASAs Ames Research Center (ARC), in collaboration with NASAs Advanced Multimission Operations System (AMMOS) and NASAs Jet Propulsion Laboratory (JPL), Open MCT is getting its first mission use on the Jason 3 Mission, and is also available in the testbed for the Mars 2020 Rover and for development use for NASAs Resource Prospector Lunar Rover. The open source nature of the project provides for use outside of space missions, including open source contributions from a community of users. The defining features of Open MCT for mission users are data integration, end user composition and multiple views. Data integration provides access to mission data across domains in one place, making data such as activities, timelines, telemetry, imagery, event timers and procedures available in one place, without application switching. End user composition provides users with layouts, which act as a canvas to assemble visualisations. Multiple views provide the capability to view the same data in different ways, with live switching of data views in place. Open MCT is browser based, and works on the desktop as well as tablets and phones, providing access to data anywhere. An early use case for mobile data access took place on the Resource Prospector (RP) Mission Distributed Operations Test, in which rover engineers in the field were able to view telemetry on their phones. We envision this capability providing decision support to on console operators from off duty personnel. The plug-in architecture also allows for adaptation for different mission capabilities. Different data types and capabilities may be added or removed using plugins. An API provides a means to write new capabilities and to create data adaptors. Data plugins exist for mission data sources for NASA missions. Adaptors have been written by international and commercial users. Open MCT is open source. Open source enables collaborative development across organizations and also makes the product available outside of the space community, providing a potential source of usage and ideas to drive product design and development. The combination of open source with an Apache 2 license, and distribution on GitHub, has enabled an active community of users and contributors. The spectrum of users for Open MCT is, to our knowledge, unprecedented for mission software. In addition to our NASA users, we have, through open source, had users and inquires on projects ranging from Internet of Things, to radio hobbyists, to farming projects. We have an active community of contributors, enabling a flow of ideas inside and outside of the space community.

Trimble, Jay↗

Evaluation of a Candidate Trace Contaminant Control Subsystem Architecture: The High Velocity, Low Aspect Ratio (HVLA) Adsorption Process

Traditional gas-phase trace contaminant control adsorption process flow is constrained as required to maintain high contaminant single-pass adsorption efficiency. Specifically, the bed superficial velocity is controlled to limit the adsorption mass-transfer zone length relative to the physical adsorption bed; this is aided by traditional high-aspect ratio bed design. Through operation in this manner, most contaminants, including those with relatively high potential energy are readily adsorbed. A consequence of this operational approach, however, is a limited available operational flow margin. By considering a paradigm shift in adsorption architecture design and operations, in which flows of high superficial velocity are treated by low-aspect ratio sorbent beds, the range of well-adsorbed contaminants becomes limited, but the process flow is increased such that contaminant leaks or emerging contaminants of interest may be effectively controlled. To this end, the high velocity, low aspect ratio (HVLA) adsorption process architecture was demonstrated against a trace contaminant load representative of the International Space Station atmosphere. Two HVLA concept packaging designs (linear flow and radial flow) were tested. The performance of each design was evaluated and compared against computer simulation. Utilizing the HVLA process, long and sustained control of heavy organic contaminants was demonstrated.

Kayatin, Matthew J.↗

Comparative Study of 3-Dimensional Woven Joint Architectures for Composite Spacecraft Structures

The National Aeronautics and Space Administration (NASA) Exploration Systems Mission Directorate initiated an Advanced Composite Technology (ACT) Project through the Exploration Technology Development Program in order to support the polymer composite needs for future heavy lift launch architectures. As an example, the large composite structural applications on Ares V inspired the evaluation of advanced joining technologies, specifically 3D woven composite joints, which could be applied to traditionally manufactured barrel segments. Implementation of these 3D woven joint technologies may offer enhancements in damage tolerance without sacrificing weight. However, baseline mechanical performance data is needed to properly analyze the joint stresses and subsequently design/down-select a preform architecture. Six different configurations were designed and prepared for this study; each consisting of a different combination of warp/fill fiber volume ratio and preform interlocking method (z-fiber, fully interlocked, or hybrid). Tensile testing was performed for this study with the enhancement of a dual camera Digital Image Correlation (DIC) system which provides the capability to measure full-field strains and three dimensional displacements of objects under load. As expected, the ratio of warp/fill fiber has a direct influence on strength and modulus, with higher values measured in the direction of higher fiber volume bias. When comparing the z-fiber weave to a fully interlocked weave with comparable fiber bias, the z-fiber weave demonstrated the best performance in two different comparisons. We report the measured tensile strengths and moduli for test coupons from the 6 different weave configurations under study.

Jones, Justin S.↗

On the Development and Application of High Data Rate Architecture (HiDRA) in Future Space Networks

Historically, space missions have been severely constrained by their ability to downlink the data they have collected. These constraints are a result of relatively low link rates on the spacecraft as well as limitations on the time during which data can be sent. As part of a coherent strategy to address existing limitations and get more data to the ground more quickly, the Space Communications and Navigation (SCaN) program has been developing an architecture for a future solar system Internet. The High Data Rate Architecture (HiDRA) project is designed to fit into such a future SCaN network. HiDRA's goal is to describe a general packet-based networking capability which can be used to provide assets with efficient networking capabilities while simultaneously reducing the capital costs and operational costs of developing and flying future space systems.Along these lines, this paper begins by reviewing various characteristics of modern satellite design as well as relevant characteristics of emerging technologies (such as free-space optical links capable of working at 100+ Gbps). Next, the paper describes HiDRA's design, and how the system is able to both integrate and support the operation of not only today's high-rate systems, but also the high-rate systems likely to be found in the future. This section also explores both existing and future networking technologies, such as Delay Tolerant Networking (DTN) protocol (RFC4838 citeRFC:1, RFC5050citeRFC:2), and explains how HiDRA supports them. Additionally, this section explores how HiDRA is used for scheduling data movement through both proactive and reactive link management. After this, the paper moves on to explore a reference implementation of HiDRA. This implementation is currently being realized based on a Field Programmable Gate Array (FPGA) memory and interface controller that is itself controlled by a local computer running DTN software. Next, this paper explores HiDRA's natural evolution, which includes an integration path for software-defined networking (SDN) switches. This section also describes considerations for both near-Earth and deep-space instantiations of HiDRA, describing how differences in latencies between the environments will necessarily influence how the system is configured and the networks operate. Finally, this paper describes future work. This section includes a description of a potential ISS implementation which will allow rapid advancement through the technology readiness levels (TRL). This section also explores work being done to support HiDRA's successful implementation and operation in a heterogeneous network: such a network could include communications equipment spanning many vintages and capabilities, and one significant aspect of HiDRA's future development involves balancing compatibility with capability.

DTN↗

A Discussion of Integrated Life Support and In Situ Resource Utilization Architectures for Mars Surface Missions

Life support on the International Space Station is made possible by a combination of technologies to ensure the availability of clean water and air for the crew. Resources, including water and oxygen, are partially recovered and recycled; the balance is lost as waste either to space or incinerated during reentry into Earth's atmosphere. Frequent resupply cargo is provided to ISS to replace these lost resources. For missions beyond Low Earth Orbit, resupply becomes increasingly challenging both economically and logistically. To limit the need for these resupply missions, three options are available: increase the recovery and recycling of necessary materials, leverage in situ resources available for a given mission, or a combination of both. Here we discuss several basic life support and in situ resource utilization (ISRU) architectures, identify common technologies, propose possible integrated architectures, identify benefits of and challenges to varying levels of life support and ISRU integration, and discuss several considerations for technology commonality, dis-similar redundancy, and developmental overlap.

Abney, Morgan B.↗

The Core Flight System (cFS) Experiences in Opening an Architecture

This presentation presents a software architecture model that contains three perspectives: User, Business, and System. This model is used to evaluate the evolution of the cFS from a NASA/Goddard in-house product line to an open source open architecture used by a world wide community.

Mccomas, David↗

Interoperable End-To-End Space Communications Architecture Using CCSDS Building Blocks

End-to-end space communication architectures must connect system elements that may be in space, on the ground in mission operations centers, or are shared assets such as ground communications stations. End-to-end connectivity involves space communications over RF links, but also cross support services, terrestrial network circuits, and a variety of application layer protocols for commanding, telemetry, and mission operations. CCSDS has developed a large suite of interoperable, and cross-supportable, protocols for these purposes. Each of these defines a specific “layer” of functionality, such as: RF modulation, space link error coding, cross support frame delivery, or network layer routing. CCSDS has recently published a Space Communication Cross Support Architecture Requirements Document (SCCS-ARD) that describes how many of these standards fit together and how they are intended to be used. This paper provides an overview of this document, presented so as to explain the concepts so that others may use them. These concepts will be described from several key viewpoints.

Shames, Peter M.↗

Space Traffic Management with a NASA UAS Traffic Management (UTM) Inspired Architecture

Space is becoming increasingly congested as the number of on-orbit satellites and debris objects continues to grow. Space traffic management (STM) is critical for ensuring that the expanding orbital population operates safely and efficiently, avoiding collisions and radio-frequency interference while still facilitating widespread space operations. Recent events such as the FCC approval of SpaceX’s ~12,000 satellite constellation, the signing of Space Policy Directive 3 (which moves Space Situational Awareness responsibilities away from the Department of Defense and to a civil agency), and the growth in rideshare and small launch vehicles illustrate the rapidly changing nature of this domain. This paper will describe the concept of operations (ConOps) for a civilian STM research initiative, which has been developed from previous NASA work to enable safe operation of small unmanned aircraft systems. The STM ConOps proposes an architecture to enable efficient data sharing and coordination between participants to facilitate safe spaceflight operations. It is designed to utilize and promote the emerging field of commercial STM services, as a complement to existing government-provided STM services. The concept envisions a phased evolution that would gradually integrate additional capabilities, proposing a first phase architecture and tentative plans for a broader system. Work towards developing an STM research and prototyping platform is also discussed.

UTM↗

Interoperable End-To-End Space Communications Architectures Using CCSDS Building Blocks

End-to-end space communication architectures must connect system elements that may be in space, on the ground in mission operations centers, or are shared assets such as ground communications stations. End-to-end connectivity involves space communications over RF links, but also cross support services, terrestrial network circuits, and a variety of application layer protocols for commanding, telemetry, and mission operations. CCSDS has developed a large suite of interoperable, and cross-supportable, protocols for these purposes. Each of these defines a specific “layer” of functionality, such as: RF modulation, space link error coding, cross support frame delivery, or network layer routing. CCSDS has recently published a Space Communication Cross Support Architecture Requirements Document (SCCS-ARD) that describes how many of these standards fit together and how they are intended to be used. This paper provides an overview of this document, presented so as to explain the concepts so that others may use them. These concepts will be described from several key viewpoints.

Shames, Peter M.↗

Medical Data Architecture Prototype Development - Summary of Recent Work and Proposed Ideas for Upcoming Work

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions, and in ExMC Gap Med 10: We do not have the capability to provide computed medical decision support during exploration missions. These gaps recognize the need for a comprehensive medical data management system and the accompanying computational support to provide autonomous medical care during long duration exploration missions. As the MDA matures—including the capability to comprehensively process and discover medically-relevant information to support medical operations during exploration missions—project focus will shift to maturing and extending the MDA platform to enable clinical decision support and real-time guidance. To date, the MDA foundational architecture has recommended exploration medical system Level of Care IV requirements through a series of test bed prototype developments and analog demonstrations. The next stage in the development will focus on more autonomous clinical decision making necessary to address challenges in executing a self-contained medical system that enables health care both with and without assistance from ground support. A thorough understanding of current state of medical decision support systems, advanced machine learning algorithms and vast and varied data sources is required. The development of a clinical decision support for exploration missions (Level of Care V) roadmap is needed: one that assesses of current state of the art of clinical decision support systems (CDSS), interoperability issues, identification of challenges in health and performance monitoring, obtaining and processing information from biosensors, knowledge and data management, data integration and fusion, and advanced algorithm development. This roadmap must also include rapid prototype development in the areas of data processing, advanced analysis and prediction of medical events, and treatment based on medically relevant information processing and evidence-based best practices. In this presentation, an overview of the relevant issues and the beginning framework of a Level of Care V CDSS development roadmap will be provided.

Krihak, M.↗

Search Tree Pruning for Progressive Neural Architecture Search

Our neural architecture search algorithm progressively searches a tree of neural network architectures. Child nodes are created by inserting new layers determined by a transition graph into a parent network up to a maximum depth and pruned when performance is worse than its parent. This increases efficiency but makes the algorithm greedy. Simpler networks are successfully found before more complex ones that can achieve benchmark performance similar to other top-performing networks.

Deanna Flynn↗

The Flexible Lunar Architecture for Exploration (FLARE): Designed for the Artemis-3 Moon 2024 Mission and Beyond

The Flexible Lunar Architecture for Exploration (FLARE) is a concept to deliver four crew to the lunar surface for 7 to 14 days and then return them safely to Earth by 2024. This meets NASA’s internal 2024 lunar landing deadline directed by President Trump (Trump, 2017) and the “5-year” goal set forth by Vice President Pence (Pence, 2019). FLARE is an alternative to NASA’s Human Landing System reference architecture from the Design Analysis Cycle (DAC) #2 (NASA, 2019b). The minimum FLARE concept uses one Space Launch System launch, one Orion, one European Service Module (ESM), and one human lander to deliver four crew to the Moon for a minimum surface duration of 7 days and return them to Earth. FLARE adds a new capability, called the SpaceTug, based upon the mature and successful United Launch Alliance “Common” Centaur Upper Stage vehicle, with modifications. In FLARE, the SpaceTug provides propulsion needed to return the Orion+ESM from the Moon to Earth. The SpaceTug also provides propulsion to deliver the human lander Descent Element (DE) and Ascent Element (AE) separately to lunar orbit. The Orion+ESM then completes a rendezvous with the mated DE+AE in lunar orbit. FLARE also offers optional phases to the Moon 2024 mission. The SpaceTug can also deliver components of the planned Gateway - including the Power and Propulsion Element and the Habitation and Logistics Outpost - to lunar orbit; however, the planned FLARE destination is a Low Lunar Frozen Polar Orbit unlike the NASA DAC2 plan for a Near Rectilinear Halo Orbit. FLARE also provides an option to deliver precursor equipment - including a habitation module, crew mobility devices and an In-Situ Resource Utilization demonstration - to the lunar surface for enhanced crew exploration and science with the extended 14-day surface mission.

Commercial Launch Vehicles (CLV)↗

Sense and Avoid Characterization of the Independent Configurable Architecture for Reliable Operations of Unmanned Systems

Abstract—Independent Configurable Architecture for Reliable Operations of Unmanned Systems (ICAROUS) is a distributed software architecture developed by NASA Langley Research Center to enable safe autonomous UAS operations. ICAROUS consists of a collection formally verified core algorithms for path planning, traffic avoidance, geofence handling, and decision making that interface with an autopilot system through a publisher-subscriber middleware. The ICAROUS Sense and Avoid Characterization (ISAAC) test was designed to evaluate the performance of the onboard Sense and Avoid (SAA) capability to detect potential conflicts with other aircraft and autonomously maneuver to avoid collisions, while remaining within the airspace boundaries of the mission. The ISAAC tests evaluated the impact of separation distances and alerting times on SAA performance. A preliminary analysis of the effects of each parameter on key measures of performance is conducted, informing the choice of appropriate parameter values for different small Unmanned Aircraft Systems (sUAS) applications. Furthermore, low-power Automatic Dependent Surveillance – Broadcast (ADS-B) is evaluated for potential use to enable autonomous sUAS to sUAS deconflictions as well as to provide usable warnings for manned aircraft without saturating the frequency spectrum.

Consiglio, Maria↗

End to End Optimization of a Mars Hybrid Transportation Architecture

NASA’s Mars Study Capability Team (MSCT) is developing a reusable Mars hybrid transportation architecture in which both chemical and solar electric propulsion systems are used in a single vehicle design to send crew and cargo to Mars. This paper presents a new integrated framework that combines Earth departure/arrival, heliocentric trajectory, Mars orbit reorientation, and vehicle sizing into a single environment and solves the entire mission from beginning to end in an effort to find a globally optimized solution for the hybrid architecture.

Qu, Min↗