SEARCH · Search NASA

Results for “architecture definition”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS1983

A study of space station needs, attributes, and architectural options, volume 2, technical. Book 2: Mission implementation concepts

Space station systems characteristics and architecture are described. A manned space station operational analysis is performed to determine crew size, crew task complexity and time tables, and crew equipment to support the definition of systems and subsystems concepts. This analysis is used to select and evaluate the architectural options for development.

Source record↗

NASA NTRS2018

Payload Sensitivities for Human Mars Exploration Transportation Systems

NASA is continuing to investigate mission and transportation system alternatives to support human exploration of Mars. Several publications over the last few years have outlined, in detail, the baseline reference architectures under consideration. These alternatives include SEP-Chemical Hybrid Propulsion Systems, oxygen/methane propulsion stages, and nuclear thermal propulsion systems. Studies to date have focused on identifying mission architectures that leverage these different transportation options to best support a Mars mission within the context of overarching guidelines and constraints. The focus on identifying "closed" reference mission architectures for these transportation options is a key first step in comparing alternatives and supporting the development of technology investment strategies. Architecture closure implies that the architecture identified provides a viable solution which meets all constraints and closely aligns with guidelines. If a viable architecture cannot be identified for a given transportation option, there is no need to continue investigating that option. However, at this early stage of architecture development, metrics of comparison should look beyond how these architectures perform relative to the baseline reference mission. Architectural robustness, or an insensitivity to requirements drift, should also be considered in any comparison of architectures. At this early stage of design, mission requirements have the potential to change as more definition is provided and more analyses are completed. Particularly in relation to the mass of transported elements, including Mars landers and crew habitat, it is recognized that as designs for these elements mature there exists the potential for mass growth. Selection of an architecture alternative carries with it programmatic risks and relative sensitivity to mass growth can provide insight into a particular architecture option's risk of being unable to complete its mission without significant redesign as more element definition is provided. This paper outlines the current understanding of the sensitivity

Percy, Thomas K.↗

NASA NTRS1999

Prototype and Evaluation of AutoHelp: A Case-based, Web-accessible Help Desk System for EOSDIS

AutoHelp is a case-based, Web-accessible help desk for users of the EOSDIS. Its uses a combination of advanced computer and Web technologies, knowledge-based systems tools, and cognitive engineering to offload the current, person-intensive, help desk facilities at the DAACs. As a case-based system, AutoHelp starts with an organized database of previous help requests (questions and answers) indexed by a hierarchical category structure that facilitates recognition by persons seeking assistance. As an initial proof-of-concept demonstration, a month of email help requests to the Goddard DAAC were analyzed and partially organized into help request cases. These cases were then categorized to create a preliminary case indexing system, or category structure. This category structure allows potential users to identify or recognize categories of questions, responses, and sample cases similar to their needs. Year one of this research project focused on the development of a technology demonstration. User assistance 'cases' are stored in an Oracle database in a combination of tables linking prototypical questions with responses and detailed examples from the email help requests analyzed to date. When a potential user accesses the AutoHelp system, a Web server provides a Java applet that displays the category structure of the help case base organized by the needs of previous users. When the user identifies or requests a particular type of assistance, the applet uses Java database connectivity (JDBC) software to access the database and extract the relevant cases. The demonstration will include an on-line presentation of how AutoHelp is currently structured. We will show how a user might request assistance via the Web interface and how the AutoHelp case base provides assistance. The presentation will describe the DAAC data collection, case definition, and organization to date, as well as the AutoHelp architecture. It will conclude with the year 2 proposal to more fully develop the case base, the user interface (including the category structure), interface with the current DAAC Help System, the development of tools to add new cases, and user testing and evaluation at (perhaps) the Goddard DAAC.

Mitchell, Christine M.↗

NASA NTRS2004

Continuing Evolution of Mars Sample Return

This paper addresses the continued evolution of the Groundbreaking MSR concept over the last year. One of the tenets of the low-cost approach is to use substantial heritage from an earlier mission, Mars Science Laboratory (MSL). Recently, the MSL project developed and switched to a revolutionary landing approach, coined 'sky-crane' where the MSL, which is a rover, is lowered gently to the Martian surface from a hovering vehicle. MSR has adopted this approach, again continuing to capitalize on the heritage for a significant portion of the new lander. In parallel, a MSR Technology Board was formed to reexamine MSR technology needs and participate in a continuing refinement of architectural trades. While the focused technology program continues to be definitized through the remainder of this year, the current assessment of what technology development is required, is discussed in this paper. In addition, the results of new trade studies and considerations will be discussed.

Mars Sample Return (MSR)↗

NASA NTRS2012

Miniature EVA Software Defined Radio

As NASA embarks upon developing the Next-Generation Extra Vehicular Activity (EVA) Radio for deep space exploration, the demands on EVA battery life will substantially increase. The number of modes and frequency bands required will continue to grow in order to enable efficient and complex multi-mode operations including communications, navigation, and tracking applications. Whether conducting astronaut excursions, communicating to soldiers, or first responders responding to emergency hazards, NASA has developed an innovative, affordable, miniaturized, power-efficient software defined radio that offers unprecedented power-efficient flexibility. This lightweight, programmable, S-band, multi-service, frequency- agile EVA software defined radio (SDR) supports data, telemetry, voice, and both standard and high-definition video. Features include a modular design, an easily scalable architecture, and the EVA SDR allows for both stationary and mobile battery powered handheld operations. Currently, the radio is equipped with an S-band RF section. However, its scalable architecture can accommodate multiple RF sections simultaneously to cover multiple frequency bands. The EVA SDR also supports multiple network protocols. It currently implements a Hybrid Mesh Network based on the 802.11s open standard protocol. The radio targets RF channel data rates up to 20 Mbps and can be equipped with a real-time operating system (RTOS) that can be switched off for power-aware applications. The EVA SDR's modular design permits implementation of the same hardware at all Network Nodes concept. This approach assures the portability of the same software into any radio in the system. It also brings several benefits to the entire system including reducing system maintenance, system complexity, and development cost.

Pozhidaev, Aleksey↗

NASA NTRS2012

Design and Parametric Sizing of Deep Space Habitats Supporting NASA'S Human Space Flight Architecture Team

NASA's Human Space Flight Architecture Team (HAT) is a multi-disciplinary, cross-agency study team that conducts strategic analysis of integrated development approaches for human and robotic space exploration architectures. During each analysis cycle, HAT iterates and refines the definition of design reference missions (DRMs), which inform the definition of a set of integrated capabilities required to explore multiple destinations. An important capability identified in this capability-driven approach is habitation, which is necessary for crewmembers to live and work effectively during long duration transits to and operations at exploration destinations beyond Low Earth Orbit (LEO). This capability is captured by an element referred to as the Deep Space Habitat (DSH), which provides all equipment and resources for the functions required to support crew safety, health, and work including: life support, food preparation, waste management, sleep quarters, and housekeeping.The purpose of this paper is to describe the design of the DSH capable of supporting crew during exploration missions. First, the paper describes the functionality required in a DSH to support the HAT defined exploration missions, the parameters affecting its design, and the assumptions used in the sizing of the habitat. Then, the process used for arriving at parametric sizing estimates to support additional HAT analyses is detailed. Finally, results from the HAT Cycle C DSH sizing are presented followed by a brief description of the remaining design trades and technological advancements necessary to enable the exploration habitation capability.

Toups, Larry↗

NASA NTRSDate not supplied

Standards Roadmapping for Mission Assurance in Commercial Spaceflight

This paper explores the application of established roadmapping approaches in standards planning and roadmap development to support mission assurance objectives. Mission assurance requires proactive planning across multiple domains including technical, schedule, cost, organizational, and policy. The intersection of these domains happens at the enterprise level, and enterprise systems engineering processes can systematically guide mission assurance activities, including development of standards roadmaps. Standards planning and development is a critical contributor to an effective mission assurance strategy, although standards are often developed and adopted reactively. Technology and standards planning is a key Enterprise Process Management activity, as identified by the Systems Engineering Body of Knowledge, and technology and standards roadmaps are strategic tools used to enable that process. Technology roadmapping has proven effective in guiding enterprise architecture and concept design, and standards planning supports enterprise requirements definition and management. However, there are limited methodologies to guide such standards planning activities. The application of technology roadmapping principles to standards planning formalizes the process and establishes a repeatable framework for standards development and integration. The framework development described in this paper fills a methodological gap by adapting proven roadmapping techniques to standards planning. Through a comparison of roadmapping methodologies and a case study analysis, this approach outlines a systematic process for anticipating and planning standards needs. In the case of developing a standards integration roadmap for NASA’s Office of Safety and Mission Assurance (OSMA), technology roadmapping principles were adapted to develop a roadmap framework to allow NASA and OSMA to define an agency-wide standards integration plan for commercial and industry safety and mission assurance standards. The outcome highlights key adaptations required for roadmapping in a standards context and describes the process steps to formalize a standards planning activity. The roadmapping framework adapted for standards development and integration enables more strategic, forward-looking standards planning and allows for better alignment between evolving capabilities and mission assurance requirements. Beyond its application to mission assurance, this methodology can be transferred to other domains requiring standards development, providing a systematic approach that integrates systems engineering principles into policy strategy and decision-making processes.

Enterprise Systems Engineering↗

NASA NTRS2006

Software Defined Radio Standard Architecture and its Application to NASA Space Missions

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG's SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Andro, Monty↗

NASA NTRS2006

Space Telecommunications Radio Architecture (STRS)

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG's SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA s current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2007

NASA's SDR Standard: Space Telecommunications Radio System

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA s current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2006

Space Telecommunications Radio Architecture (STRS): Technical Overview

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2009

Long-Lived Venus Lander Conceptual Design: How To Keep It Cool

Surprisingly little is known about Venus, our neighboring sister planet in the solar system, due to the challenges of operating in its extremely hot, corrosive, and dense environment. For example, after over two dozen missions to the planet, the longest-lived lander was the Soviet Venera 13, and it only survived two hours on the surface. Several conceptual Venus mission studies have been formulated in the past two decades proposing lander architectures that potentially extend lander lifetime. Most recently, the Venus Science and Technology Definition Team (STDT) was commissioned by NASA to study a Venus Flagship Mission potentially launching in the 2020- 2025 time-frame; the reference lander of this study is designed to survive for only a few hours more than Venera 13 launched back in 1981! Since Cytherean mission planners lack a viable approach to a long-lived surface architecture, specific scientific objectives outlined in the National Science Foundation Decadal Survey and Venus Exploration Advisory Group final report cannot be completed. These include: mapping the mineralogy and composition of the surface on a planetary scale determining the age of various rock samples on Venus, searching for evidence of changes in interior dynamics (seismometry) and its impact on climate and many other key observations that benefit with time scales of at least a full Venus day (Le. daylight/night cycle). This report reviews those studies and recommends a hybrid lander architecture that can survive for at least one Venus day (243 Earth days) by incorporating selective Stirling multi-stage active cooling and hybrid thermoacoustic power.

Dyson, Ridger W.↗

NASA NTRS2008

Mission Architecture and Technology Options for a Flagship Class Venus In Situ Mission

Venus, as part of the inner triad with Earth and Mars, represents an important exploration target if we want to learn more about solar system formation and evolution. Comparative planetology could also elucidate the differences between the past, present, and future of these three planets, and can help with the characterization of potential habitable zones in our solar system and, by extension, extrasolar systems. A long lived in situ Venus mission concept, called the Venus Mobile Explorer, was prominently featured in NASA's 2006 SSE Roadmap and supported in the community White Paper by the Venus Exploration Analysis Group (VEXAG). Long-lived in situ missions are expected to belong to the largest (Flagship) mission class, which would require both enabling and enhancing technologies beside mission architecture options. Furthermore, extreme environment mitigation technologies for Venus are considered long lead development items and are expected to require technology development through a dedicated program. To better understand programmatic and technology needs and the motivating science behind them, in this fiscal year (FY08) NASA is funding a Venus Flaghip class mission study, based on key science and technology drivers identified by a NASA appointed Venus Science and Technology Definition Team (STDT). These mission drivers are then assembled around a suitable mission architecture to further refine technology and cost elements. In this paper we will discuss the connection between the final mission architecture and the connected technology drivers from this NASA funded study, which - if funded - could enable a future Flagship class Venus mission and potentially drive a proposed Venus technology development program.

Balint, Tibor S.↗

NASA NTRS1995

A user-system interface agent

Agent-based technologies answer to several challenges posed by additional information processing requirements in today's computing environments. In particular, (1) users desire interaction with computing devices in a mode which is similar to that used between people, (2) the efficiency and successful completion of information processing tasks often require a high-level of expertise in complex and multiple domains, (3) information processing tasks often require handling of large volumes of data and, therefore, continuous and endless processing activities. The concept of an agent is an attempt to address these new challenges by introducing information processing environments in which (1) users can communicate with a system in a natural way, (2) an agent is a specialist and a self-learner and, therefore, it qualifies to be trusted to perform tasks independent of the human user, and (3) an agent is an entity that is continuously active performing tasks that are either delegated to it or self-imposed. The work described in this paper focuses on the development of an interface agent for users of a complex information processing environment (IPE). This activity is part of an on-going effort to build a model for developing agent-based information systems. Such systems will be highly applicable to environments which require a high degree of automation, such as, flight control operations and/or processing of large volumes of data in complex domains, such as the EOSDIS environment and other multidisciplinary, scientific data systems. The concept of an agent as an information processing entity is fully described with emphasis on characteristics of special interest to the User-System Interface Agent (USIA). Issues such as agent 'existence' and 'qualification' are discussed in this paper. Based on a definition of an agent and its main characteristics, we propose an architecture for the development of interface agents for users of an IPE that is agent-oriented and whose resources are likely to be distributed and heterogeneous in nature. The architecture of USIA is outlined in two main components: (1) the user interface which is concerned with issues as user dialog and interaction, user modeling, and adaptation to user profile, and (2) the system interface part which deals with identification of IPE capabilities, task understanding and feasibility assessment, and task delegation and coordination of assistant agents.

Wakim, Nagi T.↗

NASA NTRS1990

New Directions in Space: A Report on the Lunar and Mars Initiatives

This report focuses on one aspect of the current space program: The establishment of a manned base on the Moon and the manned exploration of Mars. These missions were announced by the President last year as a major U.S. space policy objective to be implemented under the leadership of the Vice President, acting as Chairman of the National Space Council. On March 8, 1990, the White House released Presidential guidelines for the execution of the lunar and Mars programs. The guidelines stressed the need for new approaches and the development of innovative technologies with a potential for major cost, schedule and performance improvements. They also called for a competitive environment, with several years allotted to the definition of at least two significantly different human space exploration "reference architectures." Selection of the final technical concepts for the mission is scheduled to occur only after the relative merits of the competing reference architectures have been evaluated.

Seitz, Frederick↗

NASA NTRS2016

Evolving Our Evaluation of Lighting Environments Project

Imagine you are an astronaut on their 100th day of your three year exploration mission. During your daily routine to the small hygiene compartment of the spacecraft, you realize that no matter what you do, your body blocks the light from the lamp. You can clearly see your hands or your toes but not both! What were those design engineers thinking! It would have been nice if they could have made the walls glow instead! The reason the designers were not more innovative is that their interpretation of the system lighting requirements didn't allow them to be so! Currently, our interior spacecraft lighting standards and requirements are written around the concept of a quantity of light illuminating a spacecraft surface. The natural interpretation for the engineer is that a lamp that throws light to the surface is required. Because of certification costs, only one lamp is designed and small rooms can wind up with lamps that may be inappropriate for the room architecture. The advances in solid state light emitting technologies and optics for lighting and visual communication necessitates the evaluation of how NASA envisions spacecraft lighting architectures and how NASA uses industry standards for the design and evaluation of lighting system. Current NASA lighting standards and requirements for existing architectures focus on the separate ability of a lighting system to throw light against a surface or the ability of a display system to provide the appropriate visual contrast. Realization that these systems can be integrated is not realized. The result is that the systems are developed independent from one another and potential efficiencies that could be realized from borrowing from the concept of one technology and applying it for the purpose of the other does not occur. This project investigated the possibility of incorporating large luminous surface lamps as an alternative or supplement to overhead lighting. We identified existing industry standards for architectural luminous or brightness uniformity as part of a lighting system definition. The efficiency of the surface lighting technology was evaluated for uniformity and power consumption. Finally, the team investigated possible performance savings if the walls were made to glow via a self luminous surface system instead of creating brightness by use of direct lighting of a highly reflective diffuse surface.

Terrier, Douglas↗

NASA NTRS2017

The Space Mobile Network

The definition and development of the next generation space communications and navigation architecture is underway. The primary goals are to remove communications and navigations constraints from missions and to enable increased autonomy. The Space Mobile Network (SMN) is an architectural concept that includes new technology and operations that will provide flight systems with an similar user experience to terrestrial wireless mobile networks. This talk will describe the SMN and its proposed new features, such as Disruption Tolerant Networking (DTN), optical communications, and User Initiated Services (UIS).

Spacecraft Communications↗

NASA NTRS2009

Applications of Payload Directed Flight

Next generation aviation flight control concepts require autonomous and intelligent control system architectures that close control loops directly around payload sensors in manner more integrated and cohesive that in traditional autopilot designs. Research into payload directed flight control at NASA Ames Research Center is investigating new and novel architectures that can satisfy the requirements for next generation control and automation concepts for aviation. Tighter integration between sensor and machine requires definition of specific sensor-directed control modes to tie the sensor data directly into a vehicle control structures throughout the entire control architecture, from low-level stability- and control loops, to higher level mission planning and scheduling reasoning systems. Payload directed flight systems can thus provide guidance, navigation, and control for vehicle platforms hosting a suite of onboard payload sensors. This paper outlines related research into the field of payload directed flight; and outlines requirements and operating concepts for payload directed flight systems based on identified needs from the scientific literature.'

Ippolito, Corey↗