SEARCH · Search NASA

Results for “systems architecture systems engineering technology 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.

SourceResearch connectionFrom yearThrough year

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

At least 73 records · Page 4

All sources NASA NTRS DOE OSTI

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 NTRSDate not supplied

Exploration Medical Capability - Advancing Medical System Design and Risk-Informed Decision Making for Deep Space Exploration

BACKGROUND: Within NASA’s Human Research Program, the Exploration Medical Capability (ExMC) Element has three primary focus areas: clinical and scientific research, systems engineering and trade space analysis, and technology development and demonstrations. These focus areas feed into the overarching goal of enabling progressively Earth-Independent Medical Operations (EIMO), a new paradigm that will be necessary for future Artemis and Mars medical and vehicle systems. This EIMO end state aligns with NASA’s Moon to Mars Objectives, which clearly outline the need for NASA deep space exploration missions to reduce their reliance upon Earth and become increasingly autonomous, in preparation for the first human Mars mission. OVERVIEW: To advance exploration medical systems and ultimately, integrated crew health and performance systems, ExMC’s portfolio includes: funding ground development & testing of novel medical capabilities; creation of new approaches for the development of medical protocols and procedures; deployment of innovative technologies into analog environments; technology demonstrations in spaceflight; and eventual transition to operations of new capabilities for deep space exploration missions. The portfolio also includes: pharmaceutical research targeting stability, pharmacokinetics, and pharmacodynamics; integrated data architectures and clinical decision support tools; and systems engineering and trade space analysis tools to assist NASA in the development of future medical system models as well as the medical system requirements that can serve as a foundation for deep space exploration missions. All of these investments are done in a collaborative and coordinated fashion with other NASA stakeholders, such as the Environmental Control and Life Support Systems – Crew Health and Performance System Capability Leadership Team and the Health and Medical Technical Authority. DISCUSSION: In this presentation, ExMC will provide an overview of our work from across our portfolio, all of which will inform future EIMO efforts at NASA. ExMC’s research and development investments are targeted to reduce the human system risks associated with deep space exploration to the Moon and Mars.

Kris Lehnhardt↗

NASA NTRS2009

The Functional Breakdown Structure (FBS) and Its Relationship to Life Cycle Cost

The Functional Breakdown Structure (FBS) is a structured, modular breakdown of every function that must be addressed to perform a generic mission. It is also usable for any subset of the mission. Unlike a Work Breakdown Structure (WBS), the FBS is a function-oriented tree, not a product-oriented tree. The FBS details not products, but operations or activities that should be performed. The FBS is not tied to any particular architectural implementation because it is a listing of the needed functions, not the elements, of the architecture. The FBS for Space Transportation Systems provides a universal hierarchy of required functions, which include ground and space operations as well as infrastructure - it provides total visibility of the entire mission. By approaching the systems engineering problem from the functional view, instead of the element or hardware view, the SPST has created an exhaustive list of potential requirements which the architecture designers can use to evaluate the completeness of their designs. This is a new approach that will provide full accountability of all functions required to perform the planned mission. It serves as a giant check list to be sure that no functions are omitted, especially in the early architectural design phase. A significant characteristic of a FBS is that if architecture options are compared using this approach, then any missing or redundant elements of each option will be ' identified. Consequently, valid Life Cycle Costs (LCC) comparisons can be made. For example, one architecture option might not need a particular function while another option does. One option may have individual elements to perform each of three functions while another option needs only one element to perform the three functions. Once an architecture has been selected, the FBS will serve as a guide in development of the work breakdown structure, provide visibility of those technologies that need to be further developed to perform required functions, and help identify the personnel skills required to develop and operate the architecture. It also wifi allow the systems engineering activities to totally integrate each discipline to the maximum extent possible and optimize at the total system level, thus avoiding optimizing at the element level (stove-piping). In addition, it furnishes a framework that wifi help prevent over or under specifying requirements because all functions are identified and all elements are aligned to functions.

DeHoff, Bryan↗

NASA NTRS1995

An object-oriented, technology-adaptive information model

The primary objective was to develop a computer information system for effectively presenting NASA's technologies to American industries, for appropriate commercialization. To this end a comprehensive information management model, applicable to a wide variety of situations, and immune to computer software/hardware technological gyrations, was developed. The model consists of four main elements: a DATA_STORE, a data PRODUCER/UPDATER_CLIENT and a data PRESENTATION_CLIENT, anchored to a central object-oriented SERVER engine. This server engine facilitates exchanges among the other model elements and safeguards the integrity of the DATA_STORE element. It is designed to support new technologies, as they become available, such as Object Linking and Embedding (OLE), on-demand audio-video data streaming with compression (such as is required for video conferencing), Worldwide Web (WWW) and other information services and browsing, fax-back data requests, presentation of information on CD-ROM, and regular in-house database management, regardless of the data model in place. The four components of this information model interact through a system of intelligent message agents which are customized to specific information exchange needs. This model is at the leading edge of modern information management models. It is independent of technological changes and can be implemented in a variety of ways to meet the specific needs of any communications situation. This summer a partial implementation of the model has been achieved. The structure of the DATA_STORE has been fully specified and successfully tested using Microsoft's FoxPro 2.6 database management system. Data PRODUCER/UPDATER and PRESENTATION architectures have been developed and also successfully implemented in FoxPro; and work has started on a full implementation of the SERVER engine. The model has also been successfully applied to a CD-ROM presentation of NASA's technologies in support of Langley Research Center's TAG efforts.

Anyiwo, Joshua C.↗

NASA NTRS2016

Towards a Reference Architecture for Model-Based Engineering Environments

A key aspect of adopting model-based systems engineering as a practice in an organization is the design and development, and adoption of corresponding processes and tools that support the model-based paradigm. In an effort to enable the unified implementation of such processes and tools, this paper introduces a reference architecture model that serves as a specification for a model-based engineering environment. Current systems engineering practices, products, processes and technologies are used as input for continuously refining the architecture model. In the paper, we introduce and report on the current status of this reference architecture model, and present the methodology applied in developing the reference architecture. We conclude that while there are a very large number of domain- or application-specific processes requiring specialized behavior, these can be reduced through abstraction to a small set of core functions that need to be supported by a realization of a model-based engineering environment. Only very few organization-domain- or application-specific aspects require specialized consideration.

Herzig, Sebastian J. I.↗

NASA NTRS2004

Advanced Technology Lifecycle Analysis System (ATLAS)

Developing credible mass and cost estimates for space exploration and development architectures require multidisciplinary analysis based on physics calculations, and parametric estimates derived from historical systems. Within the National Aeronautics and Space Administration (NASA), concurrent engineering environment (CEE) activities integrate discipline oriented analysis tools through a computer network and accumulate the results of a multidisciplinary analysis team via a centralized database or spreadsheet Each minute of a design and analysis study within a concurrent engineering environment is expensive due the size of the team and supporting equipment The Advanced Technology Lifecycle Analysis System (ATLAS) reduces the cost of architecture analysis by capturing the knowledge of discipline experts into system oriented spreadsheet models. A framework with a user interface presents a library of system models to an architecture analyst. The analyst selects models of launchers, in-space transportation systems, and excursion vehicles, as well as space and surface infrastructure such as propellant depots, habitats, and solar power satellites. After assembling the architecture from the selected models, the analyst can create a campaign comprised of missions spanning several years. The ATLAS controller passes analyst specified parameters to the models and data among the models. An integrator workbook calls a history based parametric analysis cost model to determine the costs. Also, the integrator estimates the flight rates, launched masses, and architecture benefits over the years of the campaign. An accumulator workbook presents the analytical results in a series of bar graphs. In no way does ATLAS compete with a CEE; instead, ATLAS complements a CEE by ensuring that the time of the experts is well spent Using ATLAS, an architecture analyst can perform technology sensitivity analysis, study many scenarios, and see the impact of design decisions. When the analyst is satisfied with the system configurations, technology portfolios, and deployment strategies, he or she can present the concepts to a team, which will conduct a detailed, discipline-oriented analysis within a CEE. An analog to this approach is the music industry where a songwriter creates the lyrics and music before entering a recording studio.

O'Neil, Daniel A.↗

NASA NTRS1987

First Annual Workshop on Space Operations Automation and Robotics (SOAR 87)

Several topics relative to automation and robotics technology are discussed. Automation of checkout, ground support, and logistics; automated software development; man-machine interfaces; neural networks; systems engineering and distributed/parallel processing architectures; and artificial intelligence/expert systems are among the topics covered.

Griffin, Sandy↗

NASA NTRS2011

The Development of NASA's Fault Management Handbook

Disciplined approach to Fault Management (FM) has not always been emphasized by projects, contributing to major schedule and cost overruns: (1) Often faults aren't addressed until nominal spacecraft design is fairly stable. (2) Design relegated to after-the-fact patchwork, Band-Aid approach. Progress is being made on a number of fronts outside of Handbook effort: (1) Processes, Practices and Tools being developed at some Centers and Institutions (2) Management recognition. Constellation FM roles, Discovery/New Frontiers mission reviews (3) Potential Technology solutions. New approaches could avoid many current pitfalls (3a) New FM architectures, including model-based approach integrated with NASA's MBSE (Model-Based System Engineering) efforts (3b) NASA's Office of the Chief Technologist: FM identified in seven of NASA's 14 Space Technology Roadmaps. Opportunity to coalesce and establish thrust area to progressively develop new FM techniques. FM Handbook will help ensure that future missions do not encounter same FM-related problems as previous missions. Version 1 of the FM Handbook is a good start: (1) Still need Version 2 Agency-wide FM Handbook to expand Handbook to other areas, especially crewed missions. (2) Still need to reach out to other organizations to develop common understanding and vocabulary. Handbook doesn't/can't address all Workshop recommendations. Still need to identify how to address programmatic and infrastructure issues.

Fault Management↗

NASA NTRS1990

Technology needs of the Exploration Initiative

An overview of the U.S. Space Exploration Initiative (SEI) is presented. The two primary objectives of the initiative are a return to the moon to create a permanent lunar base and a human mission to Mars. Even though mission architectural concepts are not yet defined, previous studies indicate that the SEI will require developments in numerous areas, including advanced engines for space transportation, in-space assembly and construction to support permanent basing of exploration systems in space, and advanced surface operations capabilities including satisfactory levels of power and surface roving vehicles, and technologies to safely support human space operations of long duration. The process of mission definition has begun and it is shown that it is possible to identify a family of fundamental functional building blocks from which all SEI mission architectures will be constructed.

Aldrich, Arnold↗

NASA NTRS1987

The crustal dynamics intelligent user interface anthology

The National Space Science Data Center (NSSDC) has initiated an Intelligent Data Management (IDM) research effort which has, as one of its components, the development of an Intelligent User Interface (IUI). The intent of the IUI is to develop a friendly and intelligent user interface service based on expert systems and natural language processing technologies. The purpose of such a service is to support the large number of potential scientific and engineering users that have need of space and land-related research and technical data, but have little or no experience in query languages or understanding of the information content or architecture of the databases of interest. This document presents the design concepts, development approach and evaluation of the performance of a prototype IUI system for the Crustal Dynamics Project Database, which was developed using a microcomputer-based expert system tool (M. 1), the natural language query processor THEMIS, and the graphics software system GSS. The IUI design is based on a multiple view representation of a database from both the user and database perspective, with intelligent processes to translate between the views.

Short, Nicholas M., Jr.↗

NASA NTRS2011

Joint Radioisotope Electric Propulsion Studies - Neptune System Explorer

The Neptune System Explorer (NSE) mission concept study assessed opportunities to conduct Cassini-like science at Neptune with a radioisotope electric propulsion (REP) based spacecraft. REP is based on powering an electric propulsion (EP) engine with a radioisotope power source (RPS). The NSE study was commissioned under the Joint Radioisotope Electric Propulsion Studies (JREPS) project, which sought to determine the technical feasibility of flagship class REP applications. Within JREPS, special emphasis was given toward identifying tall technology tent poles, as well as recommending any new RPS technology developments that would be required for complicated REP missions. Based on the goals of JREPS, multiple RPS (e.g. thermoelectric and Stirling based RPS) and EP (e.g. Hall and ion engines) technology combinations were traded during the NSE study to determine the most favorable REP design architecture. Among the findings from the study was the need for >400We RPS systems, which was driven by EP operating powers and the requirement for a long-lived mission in the deep solar system. Additionally multiple development and implementation risks were identified for the NSE concept, as well as REP missions in general. Among the strengths of the NSE mission would be the benefits associated with RPS and EP use, such as long-term power (approx. 2-3kW) at Neptune and flexible trajectory options for achieving orbit or tours of the Neptune system. Although there are still multiple issues to mitigate, the NSE concept demonstrated distinct advantages associated with using REP for deep space flagship-class missions.

radioisotope power source (RPS)↗

NASA NTRS2014

Software Engineering for Human Spaceflight

The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world‐class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in‐house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software‐related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.

Fredrickson, Steven E.↗

NASA NTRS1999

Summary of LO2/Ethanol OMS/RCS Technology and Advanced Development 99-2744

NASA is pursuing non-toxic propellant technologies applicable to RLV and Space Shuttle orbital maneuvering system (OMS) and reaction control system (RCS). The primary objectives of making advancements in an OMS/RCS system are improved safety, reliability, and reduced operations and maintenance cost, while meeting basic operational and performance requirements. An OMS/RCS has a high degree of direct interaction with the vehicle and crew and requires subsystem and components that are compatible with integration into the vehicle with regard to external mold-line, power, and thermal control. In July 1997, a Phase I effort for the technology and advanced development of an upgrade of the space shuttle was conducted to define the system architecture, propellant tank, feed system, RCS thrusters, and OMS engine. Phase I of the project ran from July 1997 to October 1998. Phase II is currently being planned for the development and test of full-scale prototype of the system in 1999 and 2000. The choice of pressure-fed liquid oxygen (LO2) and ethanol is the result of numerous trade studies conducted from 1980 to 1996. Liquid oxygen and ethanol are clean burning, high-density propellants that provide a high degree of commonality with other spacecraft subsystems including life support, power, and thermal control, and with future human exploration and development of space missions. The key to this pressure-fed system is the use of subcooled liquid oxygen at 350 psia. In this approach, there is 80 degrees R of subcooling, which means that boil-off will not occur until the temperature has risen 80 R. The sub-cooling results naturally from loading propellants at 163 R, which is the saturation temperature at 14.7 psia, and then pressurizing to 350 psia on the launch pad. Thermal insulation and conditioning techniques are then used to limit the LO2 temperature to 185 R maximum, and maintain the sub-cooling. The other key is the wide temperature range of ethanol, -173 F to +300 F, which can provide heat to gasify liquid oxygen or provide a good coolant.

Curtis, Leslie A.↗

NASA NTRS2003

Optimizing spacecraft design - optimization engine development : progress and plans

At JPL and NASA, a process has been developed to perform life cycle risk management. This process requires users to identify: goals and objectives to be achieved (and their relative priorities), the various risks to achieving those goals and objectives, and options for risk mitigation (prevention, detection ahead of time, and alleviation). Risks are broadly defined to include the risk of failing to design a system with adequate performance, compatibility and robustness in addition to more traditional implementation and operational risks. The options for mitigating these different kinds of risks can include architectural and design choices, technology plans and technology back-up options, test-bed and simulation options, engineering models and hardware/software development techniques and other more traditional risk reduction techniques.

risk↗

NASA NTRSDate not supplied

Impact of Emerging Computing Architectures and Opportunities for Process Systems Engineering Applications

Moore’s “law” was the observation that the number of transistors in an integrated circuit doubled approximately every two years. This trend has distinctly failed to hold in recent years. The death of Moore’s law has left researchers and practitioners in the computational sciences searching for technologies to provide the speedups formerly supported by Moore’s law. Previously overlooked chip architectures and other computing technologies are now receiving more development resources. Critically, these technologies are gaining more mature software support, opening their adoption by researchers in algorithms and applications. In this article, we review some of these computing technologies, their relationship with various algorithms and applications, and their potential benefits (or pitfalls). We close with recommendations for future work by the process systems engineering community specifically.

Emerging hardware↗

NASA NTRS1988

Computer sciences

The Computer Science Program provides advanced concepts, techniques, system architectures, algorithms, and software for both space and aeronautics information sciences and computer systems. The overall goal is to provide the technical foundation within NASA for the advancement of computing technology in aerospace applications. The research program is improving the state of knowledge of fundamental aerospace computing principles and advancing computing technology in space applications such as software engineering and information extraction from data collected by scientific instruments in space. The program includes the development of special algorithms and techniques to exploit the computing power provided by high performance parallel processors and special purpose architectures. Research is being conducted in the fundamentals of data base logic and improvement techniques for producing reliable computing systems.

Smith, Paul H.↗

NASA NTRS2018

System-of-Systems Tools for the Analysis of Technological Choices in Space Propulsion

Difficulties in space mission architecture design arise from many factors. Performance, cost, and risk constraints become less obvious due to complex interactions between the systems involved in the mission; decisions regarding long-term goals can heavily impact technological choices for short-term parts of the mission, while conversely decisions in the near future will impact the whole flexibility of long-term plans. Furthermore, the space community is broadening its borders, and space agencies from different countries are collaborating with industry and commercial partners towards large-scale endeavors. This paradigm shift is prompting the development of non-traditional approaches to the design of space missions. This paper reports the results of the first year of a continuing collaboration of the authors to develop and demonstrate System-of-System engineering methodologies for the deep analysis of dependencies and synthesis of robust architectures in exploration mission contexts. We present the procedure that we followed to develop and apply our methodology, obstacles found, steps taken to improve the methods based on the needs of experts and decision makers, required data for the analysis, and results produced by our holistic analysis. In particular, we focus on the analysis of technological choices for space propulsion for a generic cislunar mission, including both complex interactions between subsystems in different type of propulsion and availability of different providers. We identify critical systems and sets of systems based on cascading effects of performance degradation, assessment of the robustness of different designs in the operational domain, and simultaneous analysis of schedule dependencies between the constituent systems.

Guariniello, Cesare↗

NASA NTRS2004

GSFC Information Systems Technology Developments Supporting the Vision for Space Exploration

The Vision for Space Exploration will guide NASA's future human and robotic space activities. The broad range of human and robotic missions now being planned will require the development of new system-level capabilities enabled by emerging new technologies. Goddard Space Flight Center is actively supporting the Vision for Space Exploration in a number of program management, engineering and technology areas. This paper provides a brief background on the Vision for Space Exploration and a general overview of potential key Goddard contributions. In particular, this paper focuses on describing relevant GSFC information systems capabilities in architecture development; interoperable command, control and communications; and other applied information systems technology/research activities that are applicable to support the Vision for Space Exploration goals. Current GSFC development efforts and task activities are presented together with future plans.

Hughes, Peter↗