Engineering PapersSearch

SEARCH · Engineering Papers

Results for “Architecture Development”

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 37 records · Page 2

Space station needs, attributes and architectural options. Volume 1, attachment 1: Executive summary NASA

User alignment plan, physical and life sciences and applications, commercial requirements national security, space operations, user needs, foreign contacts, mission scenario analysis and architectural concepts, alternative systems concepts, mission operations architectural development, architectural analysis trades, evolution, configuration, and technology development are discussed.

Source record

Characterization of in-Space Propulsion Trade Space to Support Initial Human Mars Segment

The National Aeronautics and Space Administration’s Exploration Systems Development Mission Directorate has been developing architecture concepts for human missions to Mars in alignment with the agency’s Moon to Mars blueprint objectives. The focus of the Architecture Development Office has been to decompose the blueprint objectives into the characteristics and needs for both lunar and Mars missions and develop functional needs to enable an integrated end-to-end mission architecture. One of the key components of a human Mars mission is the in-space transportation system that delivers crew and cargo to Mars vicinity and return crew safely back to Earth. The Mars Architecture Team has been evaluating four in-space transportation options to satisfy this functional need: 1) Hybrid Nuclear Electric/ Chemical Propulsion, 2) Nuclear Thermal Propulsion, 3) Hybrid Solar Electric/ Chemical Propulsion, and 4) All-Chemical propulsion. To answer the question “which transportation option is best?” decision makers will need to understand the performance characteristics—and limitations—for each architecture in the context of their preferred metric. Each option could be considered “better” than the others, depending on whether the primary selection criteria is fast, cheap, maximum cross-government applicability, maximizes commercial capabilities, and/or any other desired metrics. The Mars Architecture Team has completed considerable analysis on the Hybrid Nuclear Electric/Chemical Propulsion concept over the past three years. The Space Nuclear Propulsion program has also conducted significant work on the Nuclear Thermal Propulsion concept. The Hybrid Solar Electric/Chemical Propulsion concept, derived from technology planned for the Gateway program, was originally configurated for minimum vehicle stack mass (and, hence, minimum Earth-launched mass/cost), leveraging a highly efficient propulsion system on a minimum energy Conjunction Class trajectory. Historically, All-Chemical concepts were considered impractical due to the enormous propellant mass required, even for minimum energy Conjunction Class/long stay mission opportunities. However, considering the emerging commercial heavy-lift capabilities, the concept must be reevaluated across a range of concepts that leverage reusable launch vehicle capabilities to reduce the cost of launching large quantities of transportation elements needed for missions of various duration. This paper aims to provide an overview of the in-space transportation assessment work that is on-going within NASA.

Mars

Characterization of in-Space Propulsion Trade Space to Support Initial Human Mars Segment

The National Aeronautics and Space Administration’s Exploration Systems Development Mission Directorate has been developing architecture concepts for human missions to Mars in alignment with the agency’s Moon to Mars blueprint objectives. The focus of the Architecture Development Office has been to decompose the blueprint objectives into the characteristics and needs for both lunar and Mars missions and develop functional needs to enable an integrated end-to-end mission architecture. One of the key components of a human Mars mission is the in-space transportation system that delivers crew and cargo to Mars vicinity and return crew safely back to Earth. The Mars Architecture Team has been evaluating four in-space transportation options to satisfy this functional need: 1) Hybrid Nuclear Electric/ Chemical Propulsion, 2) Nuclear Thermal Propulsion, 3) Hybrid Solar Electric/ Chemical Propulsion, and 4) All-Chemical propulsion. To answer the question “which transportation option is best?” decision makers will need to understand the performance characteristics—and limitations—for each architecture in the context of their preferred metric. Each option could be considered “better” than the others, depending on whether the primary selection criteria is fast, cheap, maximum cross-government applicability, maximizes commercial capabilities, and/or any other desired metrics. The Mars Architecture Team has completed considerable analysis on the Hybrid Nuclear Electric/Chemical Propulsion concept over the past three years. The Space Nuclear Propulsion program has also conducted significant work on the Nuclear Thermal Propulsion concept. The Hybrid Solar Electric/Chemical Propulsion concept, derived from technology planned for the Gateway program, was originally configurated for minimum vehicle stack mass (and, hence, minimum Earth-launched mass/cost), leveraging a highly efficient propulsion system on a minimum energy Conjunction Class trajectory. Historically, All-Chemical concepts were considered impractical due to the enormous propellant mass required, even for minimum energy Conjunction Class/long stay mission opportunities. However, considering the emerging commercial heavy-lift capabilities, the concept must be reevaluated across a range of concepts that leverage reusable launch vehicle capabilities to reduce the cost of launching large quantities of transportation elements needed for missions of various duration. This paper aims to provide an overview of the in-space transportation assessment work that is on-going within NASA.

Mars

Integrity Constraint Monitoring in Software Development: Proposed Architectures

In the development of complex software systems, designers are required to obtain from many sources and manage vast amounts of knowledge of the system being built and communicate this information to personnel with a variety of backgrounds. Knowledge concerning the properties of the system, including the structure of, relationships between and limitations of the data objects in the system, becomes increasingly more vital as the complexity of the system and the number of knowledge sources increases. Ensuring that violations of these properties do not occur becomes steadily more challenging. One approach toward managing the enforcement or system properties, called context monitoring, uses a centralized repository of integrity constraints and a constraint satisfiability mechanism for dynamic verification of property enforcement during program execution. The focus of this paper is to describe possible software architectures that define a mechanism for dynamically checking the satisfiability of a set of constraints on a program. The next section describes the context monitoring approach in general. Section 3 gives an overview of the work currently being done toward the addition of an integrity constraint satisfiability mechanism to a high-level program language, SequenceL, and demonstrates how this model is being examined to develop a general software architecture. Section 4 describes possible architectures for a general constraint satisfiability mechanism, as well as an alternative approach that, uses embedded database queries in lieu of an external monitor. The paper concludes with a brief summary outlining the, current state of the research and future work.

Fernandez, Francisco G.

Development and Flight Testing of an Adaptable Vehicle Health-Monitoring Architecture

Development and testing of an adaptable wireless health-monitoring architecture for a vehicle fleet is presented. It has three operational levels: one or more remote data acquisition units located throughout the vehicle; a command and control unit located within the vehicle; and a terminal collection unit to collect analysis results from all vehicles. Each level is capable of performing autonomous analysis with a trained adaptable expert system. The remote data acquisition unit has an eight channel programmable digital interface that allows the user discretion for choosing type of sensors; number of sensors, sensor sampling rate, and sampling duration for each sensor. The architecture provides framework for a tributary analysis. All measurements at the lowest operational level are reduced to provide analysis results necessary to gauge changes from established baselines. These are then collected at the next level to identify any global trends or common features from the prior level. This process is repeated until the results are reduced at the highest operational level. In the framework, only analysis results are forwarded to the next level to reduce telemetry congestion. The system's remote data acquisition hardware and non-analysis software have been flight tested on the NASA Langley B757's main landing gear.

Woodard, Stanley E.

On-board B-ISDN fast packet switching architectures. Phase 2: Development. Proof-of-concept architecture definition report

For the next-generation packet switched communications satellite system with onboard processing and spot-beam operation, a reliable onboard fast packet switch is essential to route packets from different uplink beams to different downlink beams. The rapid emergence of point-to-point services such as video distribution, and the large demand for video conference, distributed data processing, and network management makes the multicast function essential to a fast packet switch (FPS). The satellite's inherent broadcast features gives the satellite network an advantage over the terrestrial network in providing multicast services. This report evaluates alternate multicast FPS architectures for onboard baseband switching applications and selects a candidate for subsequent breadboard development. Architecture evaluation and selection will be based on the study performed in phase 1, 'Onboard B-ISDN Fast Packet Switching Architectures', and other switch architectures which have become commercially available as large scale integration (LSI) devices.

Shyy, Dong-Jye

Considerations for the Next Revision of NASA's Space Telecommunications Radio System Architecture

Development of NASA's Software Defined Radio architecture, the Space Telecommunication Radio System (STRS), was initiated in 2004 with a goal of reducing the cost, risk and schedule when implementing Software Defined Radios (SDR) for National Aeronautics and Space Administration (NASA) space missions. Since STRS was first flown in 2012 on three Software Defined Radios on the Space Communication and Navigation (SCaN) Testbed, only minor changes have been made to the architecture. Multiple entities have since implemented the architecture and provided significant feedback for consideration for the next revision of the standard. The focus for the first set of updates to the architecture is items that enhance application portability. Items that require modifications to existing applications before migrating to the updated architecture will only be considered if there is compelling reasons to make the change. The significant suggestions that were further evaluated for consideration include expanding and clarifying the timing Application Programming Interfaces (APIs), improving handle name and identification (ID) definitions and use, and multiple items related to implementation of STRS Devices. In addition to ideas suggested while implementing STRS, SDR technology has evolved significantly and this impact to the architecture needs to be considered. These include incorporating cognitive concepts - learning from past decisions and making new decisions that the radio can act upon. SDRs are also being developed that do not contain a General Purpose Module - which is currently required for the platform to be STRS compliant. The purpose of this paper is to discuss the comments received, provide a summary of the evaluation considerations, and examine planned dispositions.

transmitters receivers

TAMU: Blueprint for A New Space Mission Operations System Paradigm

The Transferable, Adaptable, Modular and Upgradeable (TAMU) Flight Production Process (FPP) is a System of System (SOS) framework which cuts across multiple organizations and their associated facilities, that are, in the most general case, in geographically disperse locations, to develop the architecture and associated workflow processes of products for a broad range of flight projects. Further, TAMU FPP provides for the automatic execution and re-planning of the workflow processes as they become operational. This paper provides the blueprint for the TAMU FPP paradigm. This blueprint presents a complete, coherent technique, process and tool set that results in an infrastructure that can be used for full lifecycle design and decision making during the flight production process. Based on the many years of experience with the Space Shuttle Program (SSP) and the International Space Station (ISS), the currently cancelled Constellation Program which aimed on returning humans to the moon as a starting point, has been building a modern model-based Systems Engineering infrastructure to Re-engineer the FPP. This infrastructure uses a structured modeling and architecture development approach to optimize the system design thereby reducing the sustaining costs and increasing system efficiency, reliability, robustness and maintainability metrics. With the advent of the new vision for human space exploration, it is now necessary to further generalize this framework to take into consideration a broad range of missions and the participation of multiple organizations outside of the MOD; hence the Transferable, Adaptable, Modular and Upgradeable (TAMU) concept.

Ruszkowski, James T.

Modular Open Systems Approach (MOSA) for a Robust Commercial Lunar Ecosystem

Modular Open Systems Approaches (MOSAs) have been adopted worldwide to solve a myriad of challenges. Open systems by their nature maximize accessibility, reduce barriers to entry, and prevent vendor lock. Similarly, modularity speeds innovation, fosters design re-use, and enables incremental development & growth. Architectures developed using a MOSA synergize the benefits of modularity and open systems to produce better products at lower developmental cost and risk, saving the consumer money while allowing greater developer profit margins. Specific to the challenge of lunar exploration, a MOSA will ensure interoperability among diverse commercial, government, and international partners. Complex spaceflight systems can be assembled, upgraded, and serviced far more easily and with greater commercial involvement with the use of a MOSA. By allowing partners to self-limit their scope to key strengths, they can focus on producing premier components without carrying the high risk and associated cost of auxiliary tasks they don’t specialize in. We survey commercial and Department of Defense (DoD) lessons learned in past decades, discuss DoD robotics’ experience in Iraq and Afghanistan (first without then with MOSAs), and analyze the flourishing commercial ecosystem that has resulted from DoD MOSA adoption. We explore the future of lunar operations to demonstrate the criticality of MOSA adoption in key areas at the right time. Two specific lunar technical fields are studied as examples: Power and In-Situ Resource Utilization (ISRU). Finally, recognizing that the lunar ISRU campaign will be an eminently collaborative operation requiring seamless partnering among diverse commercial, government, and international partners, a comprehensive technology development ecosystem is explored aimed at enabling ISRU in a way that systems and components are affordable for commercial partners to design, build, and sustain.

Mathew DeMinico

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.

STI Architectural Framework Working Group

A general overview of the architecture developed for the NASA scientific and technical information (STI) modernization plan is presented. The value of standardization as a technique to reduce life cycle costs, to facilitate interoperability and scalability and to simplify the management process is explained. Definitions for both de facto and de jure standards follow with emphasis on government and industrial standards. The methodology applied in developing the STI architecture is described.

Kaye, Karen

T-infinity: The Dependency Inversion Principle for Rapid and Sustainable Multidisciplinary Software Development

The CFD Vision 2030 Study recommends that, “NASA should develop and maintain an integrated simulation and software development infrastructure to enable rapid CFD technology maturation.... [S]oftware standards and interfaces must be emphasized and supported whenever possible, and open source models for noncritical technology components should be adopted.” The current paper presents an approach to an open source development architecture, named T-infinity, for accelerated research in CFD leveraging the Dependency Inversion Principle to realize plugins that communicate through collections of functions without exposing internal data structures. Steady state flow visualization, mesh adaptation, fluid-structure interaction, and overset domain capabilities are demonstrated through compositions of plugins via standardized abstract interfaces without the need for source code dependencies between disciplines. Plugins interact through abstract interfaces thereby avoiding N 2 direct code-to-code data structure coupling where N is the number of codes. This plugin architecture enhances sustainable development by controlling the interaction between components to limit software complexity growth. The use of T-infinity abstract interfaces enables multidisciplinary application developers to leverage legacy applications alongside newly-developed capabilities. While rein, a description of interface details is deferred until the are more thoroughly tested and can be closed to modification.

O'Connell, Matthew D.

Artemis Deep Space Habitation: Enabling a Sustained Human Presence on the Moon and Beyond

As NASA and its partners’ capabilities for human exploration of deep space continue to mature, so too does its roadmap toward a sustained crewed presence on the surface of the Moon and eventual human missions to Mars. The first launch of the Space Launch System and Orion crew vehicle, the contract award for the first demonstrations of a Human Landing System, and the beginning of construction on the initial elements of the lunar Gateway have marked major milestones toward NASA’s near-term exploration goals: a long-duration outpost in orbit around the Moon and the next footsteps on the lunar surface. At the same time, NASA is in the early phases of planning the capabilities that will be needed for long-term exploration. Among the common elements that will be required by long-duration stays on the lunar surface, transit to Mars, and Martian surface expeditions will be new habitats unlike any flown to date. NASA is currently working on development of both architectures for those habitats and on the technological advancements that will enable them, with an eye toward systems that will not only extend mission operations but also provide for living quarters that will keep the crew happy and healthy throughout their expeditions. Beyond the Gateway habitation needs, these capabilities will need to be defined and advanced to support the initial lunar surface missions and to prepare for human missions to the Mars system. The Surface Habitat is the current concept in consideration to serve as this initial surface habitat that will extend the crew mission durations. It will provide 30-to-60-day habitability for a crew of up to four allowing for the astronauts to explore farther and longer on each visit to the lunar surface. NASA is also currently reviewing opportunities to use current or near-term in-space habitation systems as proving grounds or precursors for keeping astronauts safe and healthy during future transits to Mars. Already, the International Space Station (ISS) is being used for implementation of next-generation life-support systems that will inform those used in exploration habitats, and the operations approach for ISS is providing lessons-learned for future science operations around or on the Moon.1U.S. Government work not protected by U.S. copyright While a suite of habitation concepts is currently under study within NASA, the agency is also working closely with U.S. industry through the Next Space Technologies for Exploration Partnerships (NextSTEP) activity to understand their concepts for commercially provided habitation capabilities as well as close coordination with international partners to understand their desires for in-space and surface habitation. This paper will provide a status of these concepts and partnership activities as well as potential future technology and architecture development paths.

Habitat

Design and Development of an Equipotential Voltage Reference (Grounding) System for a Low-Cost Rapid-Development Modular Spacecraft Architecture

This work describes the design and development effort to adapt rapid-development space hardware by creating a ground system using solutions of low complexity, mass, & cost. The Lunar Atmosphere and Dust Environment Explorer (LADEE) spacecraft is based on the modular common spacecraft bus architecture developed at NASA Ames Research Center. The challenge was building upon the existing modular common bus design and development work and improving the LADEE spacecraft design by adding an Equipotential Voltage Reference (EVeR) system, commonly referred to as a ground system. This would aid LADEE in meeting Electromagnetic Environmental Effects (E3) requirements, thereby making the spacecraft more compatible with itself and its space environment. The methods used to adapt existing hardware are presented, including provisions which may be used on future spacecraft.

Lukash, James A.

Developing new architectures for the Block 2 VLBI correlator system

The overall LSI (large-scale integrated circuits) architecture design and current status of the VBLI (very long baseline interferometry) block 2 correlator is addressed. The VBLI correlator algorithms demand a computing system that provides a throughput of hundreds of millions of instructions per second to perform cross-correlation detection for six baselines. The LSI technology lights the way for the computation of complex parallel process and is raising the upper bound of computerization.

Peterson, J. C.

Lunar Node – 1: Initial Flight Results and the Role of Surface Psuedolites in Lunar Navigation

On February 22, 2024, the Intuitive Machines IM-1 NOVA-C lander, nick-named Odysseus, landed on the lunar surface, carrying with it a cadre of NASA scientific and technology demonstration payloads. These payloads and missions marked the first delivery of NASA instruments to operate from the lunar surface since the Apollo landings. One of these payloads is Lunar Node -1 (LN-1), a navigation beacon demonstration mission. The payload was designed and built by NASA’s Marshall Space Flight Center. The payload’s main goal was to demonstrate and provide insight into the use of lunar surface-based radio navigation aids. As part of the mission, LN-1 successfully conducted multiple one-way transmissions from the NOVA-C vehicle to Deep Space Network ground receivers using its onboard S-band transmitter, while being disciplined by an onboard Space Chip Scale Atomic Clock. LN-1 transmitted to DSN on an almost daily basis during transit to the moon, including two surface passes. The payload was originally plan to conduct 7-10 days of surface operation as an always-on beacon. These passes focused on evaluating two main navigation approaches: performance and stability of ranging using time-based transfer techniques on a cubesat size and grade platform, as well as one-way psuedonoise ranging approaches. To assess performance, the measurements were compared to independent navigation solutions using multiple approaches including: one-way Doppler tracking, two-way Doppler Tracking, and visual verification of the landing location provided by visual observations from orbital platforms. While the mission only conducted limited surface operations, the data provides some initial insight to performance form the lunar surface. These results are compared with initial ground-based testing as well as continued evaluation of the flight-space platform using multiple grades of oscillators for maintaining clock and frequency stability. These focus on the timing stability of platform in a deep-space environment as well variations in state determination. Given these insights, this paper provides additional description and evaluation of how this approach can be utilized as part of a broader lunar navigation architecture, such as being developed and deployed across multiple international space agencies. Analysis is provided to develop overall timing requirements and assessment of operational scenarios, such as orbit and surface location determination. In addition, the results support discussion as to how surface pseudolites could best be used within existing standard signal definitions, such as defined in the LunaNet Interoperability Specifications. This will consider concerns such as the near-/far- problem as well as operational considerations, including whether a beacon is better suited as two- or one-way ranging platform. The use cases are focused on how these psuedolites can provide additional coverage to augment and support planned operational coverage. For example, this analysis provides analysis of mid-latitude surface missions, where there may be limited geometry and availability of orbital relays. The results will show how these navigation psuedolites can fit within the developing architecture to provide additional robustness, capability, and support multiple use cases. Lastly, the paper will discuss challenges and next steps to be addressed in the implementation and testing of a follow-on payload and a continued path towards demonstration and integration of this capability into Lunar PNT architectures.

Evan Anzalone