Search NASA⌕ Search

SEARCH · Search NASA

Results for “system engineering program”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS1985

Initial testing of a variable-stroke Stirling engine

In support of the U.S. Department of Energy's Stirling Engine Highway Vehicle Systems Program, NASA Lewis Research Center is evaluating variable-stroke control for Stirling engines. The engine being tested is the Advenco Stirling engine; this engine was manufactured by Philips Research Laboratories of the Netherlands and uses a variable-angle swash-plate drive to achieve variable stroke operation. The engine is described, initial steady-state test data taken at Lewis are presented, a major drive system failure and subsequent modifications are described. Computer simulation results are presented to show potential part-load efficiency gains with variable-stroke control.

Thieme, L. G.↗
NASA NTRS1994

Temperature measurement using infrared imaging systems during turbine engine altitude testing

This report details the use of infrared imaging for temperature measurement and thermal pattern determination during simulated altitude engine testing in the NASA Lewis Propulsion Systems Laboratory. Three identical argon-cooled imaging systems were installed in the facility exhaust collector behind sapphire windows to look at engine internal surfaces. The report describes the components of each system, presents the specifics of the complicated installation, and explains the operation of the systems during engine testing. During the program, several problems emerged, such as argon contamination system, component overheating, cracked sapphire windows, and other unexplained effects. This report includes a summary of the difficulties as well as the solutions developed. The systems performed well, considering they were in an unusually harsh exhaust environment. Both video and digital data were recorded, and the information provided valuable material for the engineers and designers to quickly make any necessary design changes to the engine hardware cooling system. The knowledge and experience gained during this program greatly simplified the installation and use of the systems during later test programs in the facility. The infrared imaging systems have significantly enhanced the measurement capabilities of the facility, and have become an outstanding and versatile testing resource in the Propulsion Systems Laboratory.

Burns, Maureen E.↗
NASA NTRS1990

An update of engine system research at the Army Propulsion Directorate

The Small Turboshaft Engine Research (STER) program provides a vehicle for evaluating the application of emerging technologies to Army turboshaft engine systems and to investigate related phenomena. Capitalizing on the resources at hand, in the form of both the NASA facilities and the Army personnel, the program goal of developing a physical understanding of engine system dynamics and/or system interactions is being realized. STER entries investigate concepts and components developed both in-house and out-of-house. Emphasis is placed upon evaluations which evolved from on-going basic research and advanced development programs. Army aviation program managers are also encouraged to make use of STER resources, both people and facilities. The STER personnel have established their reputations as experts in the fields of engine system experimental evaluations and engine system related phenomena. The STER facility has STER program provides the Army aviation community the opportunity to perform system level investigations, and then to offer the findings to the entire engine community for their consideration in next generation propulsion systems. In this way results of the fundamental research being conducted to meet small turboshaft engine technology challenges expeditiously find their way into that next generation of propulsion systems.

Bobula, George A.↗
NASA NTRS1992

Design definition of the Laser Atmospheric Wind Sounder (LAWS), phase 2. Volume 1: Executive summary

The LAWS phase 1 and phase 2 studies have been completed on schedule and have led to significant advances in CO2 laser development. The Phase 2 Design Definition Study has shown that a large scanning mirror/high pulse energy laser LAWS Instrument is feasible and within the existing technology. The capability to monitor wind velocities with backscatter ratios of 10(exp 11) m(exp -1) SR(exp -1) is feasible. The weight budget allocated for the baseline LAWS is adequate, and sufficient reserves exist with the potential downsized configuration. With the possible decrease in available power from the baseline of 2.2 kW guideline, power and shot management is critical for the baseline configuration (15 to 20 J). This is particularly true during the 100 day occultation period each year. With the downsized configurations (5 to 7 J), power management is still necessary during the occultation but is primarily limited to shot management over the polar regions. The breadboard effort has produced significant laser advances for a tight 18 month schedule and the minimum budgets available from NASA, Lockheed, and TDS. Using the NASA funds and Lockheed and TDS fixed assets budgets, the breadboard was designed, fabricated, and brought on-line with first laser light within 16 months after ATP. First laser beam was obtained on 21 April 1992 at a 5 J power level. Tests since then have been conducted at sustained, repetitive pulse levels of over 7 J and 20 Hz. This is an increase of over two or three times greater than any system previously developed from this type laser. Increased power levels and additional life tests will be accomplished in the next LAWS phase. The Lockheed LAWS design will operate in the gravity gradient mode on-orbit, and all possible instrument vibration and jitter modes have been considered. Adequate pointing stability and control is state-of-the-art technology for the critical time periods, frequency rates, and control responses required by LAWS. Lockheed recommends a 6-1/2 year phase C/D program for LAWS to provide adequate feedback from the engineering unit and the qualification unit to the final flight unit. Assuming a one year period for LAWS integration to the spacecraft, followed by a six-month period for launch vehicle integration, LAWS could be successfully developed and launched in eight years. Our baseline design or downsized design can be accommodated by either the Atlas 2AS or the Delta launch vehicles. Lockheed's recommendation is that, based on the successful phase 2 design study and breadboard program, a follow-on 18 month extended breadboard testing program and additional system engineering studies, primarily in interfacing with a to be defined platform, be initiated. This should be immediately followed by the phase C/D program, leading to a LAWS launch in late 2001 or early 2002.

Source record↗
NASA NTRS1992

Expert-System Consultant To Operating Personnel

Artificial intelligence aids engineers and technicians in controlling and monitoring complicated systems. Operations Analyst for Distributed Systems (OPERA) software is developmental suite of expert-system computer programs helping engineers and technicians operating from number of computer workstations to control and monitor spacecraft during prelaunch and launch phases of operation. OPERA designed to serve as consultant to operating engineers and technicians. It preprocesses incoming data, using expertise collected from conglomerate of specialists in design and operation of various parts of system. Driven by menus and mouse-activated commands. Modified versions of OPERA used in chemical-processing plants, factories, banks, and other enterprises in which there are distributed-computer systems including computers that monitor or control other computers.

Heard, Astrid E.↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

Jeffrey R. Cohen↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeffrey R. Cohen↗
NASA NTRS2020

Vision for Cross-Center MSBE Collaboration on the Gateway Program

Model-Based Systems Engineering (MBSE) can be a challenge when there is only one modeler and one model involved. For the Gateway Program, due to its unique acquisition approach, the modeling efforts involve multiple NASA centers with each developing their own models. Every additional model to be integrated compounds the difficulties, necessitating stronger ontologies and explicitly defined interfaces between models. To help facilitate this integration, a vision of collaboration between centers is in its beginning stages. This vision includes looking at models as systems themselves and developing their own use cases, requirements and interfaces between each of them. The goal of this presentation is to share the Gateway Program's cross-center vision for model collaboration, the lessons learned in developing and implementing that vision for the various system engineering products needed to satisfy life cycle review criteria and how treating models as systems helped in these efforts.

Crane, Jeremiah↗
NASA NTRS1986

Energy Efficient Engine: Control system preliminary definition report

The object of the Control Preliminary Definition Program was to define a preliminary control system concept as a part of the Energy Efficient Engine program. The program was limited to a conceptual definition of a full authority digital electronic control system. System requirements were determined and a control system was conceptually defined to these requirements. Areas requiring technological development were identified and a plan was established for implementing the identified technological features, including a control technology demonstration. A significant element of this program was a study of the potential benefits of closed-loop active clearance control, along with laboratory tests of candidate clearance sensor elements for a closed loop system.

Howe, David C.↗
NASA NTRSDate not supplied

In-Situ Resource Utilization Modeling of a Lunar Water Processing System

A key element of achieving a sustained surface presence, such as defined in NASA’s Artemis plan, is In-Situ Resource Utilization (ISRU). ISRU is the practice of using local resources to provide mission consumables that reduce system launch mass requirements, and regenerate resources (chiefly, water and oxygen) for propulsion and life support supporting both Lunar and Martian missions. ISRU systems require multiple complex processes, such as excavation, chemical reactors, and electrolysis subsystems that must operate in harmony to optimize the overall system process from beginning to end. The Mission Analysis and Integration Tool (MAIT) was previously developed with MATLAB in FY22 to connect individual subsystem models into a customized, flexible framework for the purpose of technology downselect, optimization, and end-to-end process planning. Beginning in FY24, MAIT was updated and became the capital program in the Systems Engineering and Integration (SE&I) ISRU Modeling and Analysis (SIMA) project. Prior work was leveraged and evolved using MATLAB/Simulink due to its ability to communicate with a vast number of other programming languages and makes up the backbone of data flow between inputs and outputs to the subsystem models. MAIT initially evaluated a suite of ISRU-related technologies, including the water processing Lunar Auger Dryer for ISRU (LADI) system with integrated upstream excavation and downstream electrolysis subsystems. With individual models consolidated, the MAIT tool generated over 5,000 cases during its first round of parametric sweeps on the water processing architecture at multiple production targets; the system analysis produced valuable insight into the optimal LADI geometry that minimized energy demands, estimated effects to cold trap size and radiator requirements, and calculated the power dynamics of the electrolysis unit and liquid oxygen storage volume. Additional efforts are being made to demonstrate the ability to scale ISRU technologies supporting the Space Technology Mission Directorate’s (STMD) commercialization strategy and increase the MAIT software capability. Work is ongoing to handle a wide array of ISRU system models beyond the Lunar environment, e.g. production of propellant for a Martian lander.

Avery Carlson↗
NASA NTRSDate not supplied

In-Situ Resource Utilization Modeling of a Lunar Water Processing System

A key element of achieving a sustained surface presence, such as defined in NASA’s Artemis plan, is In-Situ Resource Utilization (ISRU). ISRU is the practice of using local resources to provide mission consumables that reduce system launch mass requirements, and regenerate resources (chiefly, water and oxygen) for propulsion and life support supporting both Lunar and Martian missions. ISRU systems require multiple complex processes, such as excavation, chemical reactors, and electrolysis subsystems that must operate in harmony to optimize the overall system process from beginning to end. The Mission Analysis and Integration Tool (MAIT) was previously developed with MATLAB in FY22 to connect individual subsystem models into a customized, flexible framework for the purpose of technology downselect, optimization, and end-to-end process planning. Beginning in FY24, MAIT was updated and became the capital program in the Systems Engineering and Integration (SE&I) ISRU Modeling and Analysis (SIMA) project. Prior work was leveraged and evolved using MATLAB/Simulink due to its ability to communicate with a vast number of other programming languages and makes up the backbone of data flow between inputs and outputs to the subsystem models. MAIT initially evaluated a suite of ISRU-related technologies, including the water processing Lunar Auger Dryer for ISRU (LADI) system with integrated upstream excavation and downstream electrolysis subsystems. With individual models consolidated, the MAIT tool generated over 5,000 cases during its first round of parametric sweeps on the water processing architecture at multiple production targets; the system analysis produced valuable insight into the optimal LADI geometry that minimized energy demands, estimated effects to cold trap size and radiator requirements, and calculated the power dynamics of the electrolysis unit and liquid oxygen storage volume. Additional efforts are being made to demonstrate the ability to scale ISRU technologies supporting the Space Technology Mission Directorate’s (STMD) commercialization strategy and increase the MAIT software capability. Work is ongoing to handle a wide array of ISRU system models beyond the Lunar environment, e.g. production of propellant for a Martian lander.

Avery Carlson↗
NASA NTRS1986

Radiation View-Factor Program With Interactive Graphics

VIEW is six computer programs for determining view factors, graphically displaying surfaces, and evaluating solar irradiation of assemblage of surfaces. Programs offer thermal engineer powerful system for view-factor determination. Central program of system (VIEWC) computes longwave radiantenergy exchange factors between surfaces that make up enclosure. Other VIEW programs support user working with VIEWC.

Emery, A. F.↗
NASA NTRS2016

Enhancing Systems Engineering Education Through Case Study Writing

Developing and refining methods for teaching systems engineering is part of Systems Engineering grand challenges and agenda for research in the SE research community. Retention of systems engineering knowledge is a growing concern in the United States as the baby boom generation continues to retire and the faster pace of technology development does not allow for younger generations to gain experiential knowledge through years of practice. Government agencies, including the National Aeronautics and Space Administration (NASA), develop their own curricula and SE leadership development programs to "grow their own" systems engineers. Marshall Space Flight Center (MSFC) conducts its own Center-focused Marshall Systems Engineering Leadership Development Program (MSELDP), a competitive program consisting of coursework, a guest lecture series, and a rotational assignment into an unfamiliar organization engaged in systems engineering. Independently, MSFC developed two courses to address knowledge retention and sharing concerns: Real World Marshall Mission Success course and its Case Study Writers Workshop and Writers Experience. Teaching case study writing and leading students through a hands-on experience at writing a case study on an SE topic can enhance SE training and has the potential to accelerate the transfer of experiential knowledge. This paper is an overview of the pilot experiences with teaching case study writing, its application in case study-based learning, and identifies potential areas of research and application for case study writing in systems engineering education.

Stevens, Jennifer Stenger↗
NASA NTRS1987

A NASA initiative: Software engineering for reliable complex systems

The objective is the development of methods, technology, and skills that will enable NASA to cost-effectively specify, build, and manage reliable software which can evolve and be maintained over an extended period. The need for such software is rooted in the increasing integration of software and computing components into NASA systems. Current NASA Software Engineering expertise was applied toward some of the largest reliable systems including: shuttle launch; ground support; shuttle simulation; minor control; satellite tracking; and scientific data systems. Unfortunately, no theory exists for reliable complex software systems. NASA is seeking to fill this theoretical gap through a number of approaches. One such approach is to conduct research on theoretical foundations for managing complex software systems. It includes: communication models, new and modified paradigms, and life-cycle models. Another approach is research in the theoretical foundations for reliable software development and validation. It focuses upon formal specifications, programming languages, software engineering systems, software reuse, formal verification, and software safety. Further approaches involve benchmarking a NASA software environment, experimentation within the NASA context, evolution of present NASA methodology, and transfer of technology to the space station software support environment.

Holcomb, Lee B.↗
NASA NTRSDate not supplied

Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA

NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.

Risk Posture↗
NASA NTRS2004

Explanation Constraint Programming for Model-based Diagnosis of Engineered Systems

We can expect to see an increase in the deployment of unmanned air and land vehicles for autonomous exploration of space. In order to maintain autonomous control of such systems, it is essential to track the current state of the system. When the system includes safety-critical components, failures or faults in the system must be diagnosed as quickly as possible, and their effects compensated for so that control and safety are maintained under a variety of fault conditions. The Livingstone fault diagnosis and recovery kernel and its temporal extension L2 are examples of model-based reasoning engines for health management. Livingstone has been shown to be effective, it is in demand, and it is being further developed. It was part of the successful Remote Agent demonstration on Deep Space One in 1999. It has been and is being utilized by several projects involving groups from various NASA centers, including the In Situ Propellant Production (ISPP) simulation at Kennedy Space Center, the X-34 and X-37 experimental reusable launch vehicle missions, Techsat-21, and advanced life support projects. Model-based and consistency-based diagnostic systems like Livingstone work only with discrete and finite domain models. When quantitative and continuous behaviors are involved, these are abstracted to discrete form using some mapping. This mapping from the quantitative domain to the qualitative domain is sometimes very involved and requires the design of highly sophisticated and complex monitors. We propose a diagnostic methodology that deals directly with quantitative models and behaviors, thereby mitigating the need for these sophisticated mappings. Our work brings together ideas from model-based diagnosis systems like Livingstone and concurrent constraint programming concepts. The system uses explanations derived from the propagation of quantitative constraints to generate conflicts. Fast conflict generation algorithms are used to generate and maintain multiple candidates whose consistency can be tracked across multiple time steps.

Narasimhan, Sriram↗