Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems engineering”

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Model-Based Systems Engineering Approach to Managing Mass Margin

When designing a flight system from concept through implementation, one of the fundamental systems engineering tasks ismanaging the mass margin and a mass equipment list (MEL) of the flight system. While generating a MEL and computing a mass margin is conceptually a trivial task, maintaining consistent and correct MELs and mass margins can be challenging due to the current practices of maintaining duplicate information in various forms, such as diagrams and tables, and in various media, such as files and emails. We have overcome this challenge through a model-based systems engineering (MBSE) approach within which we allow only a single-source-of-truth. In this paper we describe the modeling patternsused to capture the single-source-of-truth and the views that have been developed for the Europa Habitability Mission (EHM) project, a mission concept study, at the Jet Propulsion Laboratory (JPL).

cloud comu↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

MODEL↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

Iwata, Curtis↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System(IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation functionspresent in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

In-time Aviation Safety Management System↗
NASA NTRS1976

Space shuttle engineering and operations support. Avionics system engineering

The shuttle avionics integration laboratory (SAIL) requirements for supporting the Spacelab/orbiter avionics verification process are defined. The principal topics are a Spacelab avionics hardware assessment, test operations center/electronic systems test laboratory (TOC/ESL) data processing requirements definition, SAIL (Building 16) payload accommodations study, and projected funding and test scheduling. Because of the complex nature of the Spacelab/orbiter computer systems, the PCM data link, and the high rate digital data system hardware/software relationships, early avionics interface verification is required. The SAIL is a prime candidate test location to accomplish this early avionics verification.

Broome, P. A.↗
NASA NTRS1994

Systems engineering technology for networks

The report summarizes research pursued within the Systems Engineering Design Laboratory at Virginia Polytechnic Institute and State University between May 16, 1993 and January 31, 1994. The project was proposed in cooperation with the Computational Science and Engineering Research Center at Howard University. Its purpose was to investigate emerging systems engineering tools and their applicability in analyzing the NASA Network Control Center (NCC) on the basis of metrics and measures.

Source record↗
NASA NTRSDate not supplied

What Has ExMC Systems Engineering Been Up To Since Last IWS?

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. This element promotes human health and performance in space by advancing medical systems design and risk-informed decision-making for long-duration deep-space exploration missions (LDEMs). ExMC is using system engineering processes and Model-Based System Engineering (MBSE) tools to identify the user needs and requirements of LDEM medical systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant International Space Station operations to the Earth-independent operations envisioned for LDEMs. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS, an introduction to upcoming SE talks, and the ongoing systems engineering work.

K. McGuire↗
NASA NTRS1979

Optical systems engineering - A tutorial

The paper examines the use of the systems engineering approach in the design of optical systems, noting that the use of such an approach which involves an integrated interdisciplinary approach to the development of systems is most appropriate for optics. It is shown that the high precision character of optics leads to complex and subtle effects on optical system performance, resulting from structural, thermal dynamical, control system, and manufacturing and assembly considerations. Attention is given to communication problems that often occur among users and optical engineers due to the unique factors of optical systems. It is concluded that it is essential that the optics community provide leadership to resolve communication problems and fully formalize the field of optical systems engineering.

Wyman, C. L.↗
NASA NTRS2008

System Engineering for J-2X Development: The Simpler, the Better

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt and Whitney Rocketdyne Company (PWR) as the upper stage engine (USE). The J-2X is an improved higher power version of the original J-2 engine used for Apollo. System Engineering (SE) facilitates direct and open discussions of issues and problems. This simple idea is often overlooked in large, complex engineering development programs. Definition and distribution of requirements from the engine level to the component level is controlled by Allocation Reports which breaks down numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements help eliminate redundancy and potential mistakes inherent in separated systems. Another tool, the Architecture Design Description (ADD), is used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof of an effective process is in successful program accomplishment. SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. This paper describes the simple, better SE tools and techniques used to achieve this success.

Kelly, William M.↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System (IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation function present in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

IASMS↗
NASA NTRS1993

Nuclear Engine System Simulation (NESS). Volume 1: Program user's guide

A Nuclear Thermal Propulsion (NTP) engine system design analysis tool is required to support current and future Space Exploration Initiative (SEI) propulsion and vehicle design studies. Currently available NTP engine design models are those developed during the NERVA program in the 1960's and early 1970's and are highly unique to that design or are modifications of current liquid propulsion system design models. To date, NTP engine-based liquid design models lack integrated design of key NTP engine design features in the areas of reactor, shielding, multi-propellant capability, and multi-redundant pump feed fuel systems. Additionally, since the SEI effort is in the initial development stage, a robust, verified NTP analysis design tool could be of great use to the community. This effort developed an NTP engine system design analysis program (tool), known as the Nuclear Engine System Simulation (NESS) program, to support ongoing and future engine system and stage design study efforts. In this effort, Science Applications International Corporation's (SAIC) NTP version of the Expanded Liquid Engine Simulation (ELES) program was modified extensively to include Westinghouse Electric Corporation's near-term solid-core reactor design model. The ELES program has extensive capability to conduct preliminary system design analysis of liquid rocket systems and vehicles. The program is modular in nature and is versatile in terms of modeling state-of-the-art component and system options as discussed. The Westinghouse reactor design model, which was integrated in the NESS program, is based on the near-term solid-core ENABLER NTP reactor design concept. This program is now capable of accurately modeling (characterizing) a complete near-term solid-core NTP engine system in great detail, for a number of design options, in an efficient manner. The following discussion summarizes the overall analysis methodology, key assumptions, and capabilities associated with the NESS presents an example problem, and compares the results to related NTP engine system designs. Initial installation instructions and program disks are in Volume 2 of the NESS Program User's Guide.

Pelaccio, Dennis G.↗
NASA NTRS2004

Computer-Aided Systems Engineering for Flight Research Projects Using a Workgroup Database

An online systems engineering tool for flight research projects has been developed through the use of a workgroup database. Capabilities are implemented for typical flight research systems engineering needs in document library, configuration control, hazard analysis, hardware database, requirements management, action item tracking, project team information, and technical performance metrics. Repetitive tasks are automated to reduce workload and errors. Current data and documents are instantly available online and can be worked on collaboratively. Existing forms and conventional processes are used, rather than inventing or changing processes to fit the tool. An integrated tool set offers advantages by automatically cross-referencing data, minimizing redundant data entry, and reducing the number of programs that must be learned. With a simplified approach, significant improvements are attained over existing capabilities for minimal cost. By using a workgroup-level database platform, personnel most directly involved in the project can develop, modify, and maintain the system, thereby saving time and money. As a pilot project, the system has been used to support an in-house flight experiment. Options are proposed for developing and deploying this type of tool on a more extensive basis.

Mizukami, Masahi↗
NASA NTRS2021

System Engineering Curriculum Into

This document is intended to provide useful guidance and information on systems engineering for engineering students. It provides a generic description of Systems Engineering (SE) as it should be applied throughout engineering design, implementation, testing, and operations. This document will increase awareness and consistency across engineering fields and advance the practice of SE.

Kenneth Freeman↗
NASA NTRS2005

System Engineering Challenges of Future Space Missions

A viewgraph presentation on the system engineering challenges that face NASA's future space missions is shown. The topics include: 1) Future Space Missions; 2) Trends; and 3) Developing System Engineers.

Hyde, Tristam Tupper↗
NASA NTRS1984

Systems engineering - Space Telescope project

At midpoint in the development of the Space Telescope (ST), a review process was conducted which determined that much benefit could be derived from an expanded systems engineering effort. The Systems Engineering Office thus established is responsible for the running of a management information system whose functions encompass design change control and the implementation of a maintenance and refurbishment program. By these means, interface hardware/software incompatibilities between critical ST modules and subsystems have been revealed and corrected.

Wojtalik, F. S.↗