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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS2021

Future Model-Based Systems Engineering Vision and Strategy Bridge for NASA

A vision for the future of model-based systems engineering (MBSE) at NASA in 2029 and a strategy bridge towards that future are presented. Strategic thinking and leading change concepts were used to analyze reports and presentations on global trends and visionary thinking about the future of systems and digital engineering. The context, strategic time horizon, stakeholders, strategic challenges, strategic advantages, driving forces, and opportunities were considered. The analysis resulted in a future vision of MBSE that shows what NASA systems engineers and digital machines will do to perform rapid, extraordinary, and unprecedented missions. The NASA systems engineer, in this future vision, works with a global project team in a virtual and collaborative environment, engineers the system, and uses digital approaches as the routine and default way of working. The digital machines provide data-driven and automated mission designs; have a backbone of program and project management, systems engineering, and product life-cycle management; and are a knowledge-sharing infrastructure. The NASA systems engineer and the systems engineering team are envisioned to use digital machines to plan and perform rapid exploration missions, develop a digital twin that lasts across the life cycle, and develop enduring and adaptable systems. NASA has an engineering enterprise and a life-cycle management framework that endure, adapt, and respond. A strategy bridge based on the Baldrige Criteria for Performance Excellence Framework and lessons learned from a recent MBSE initiative illuminates a way forward from today to this desired future. The bridge lays out a strategy for leaders and recommends investments of today for immediate benefits and for benefits in 2029.

model-based systems engineering, digital engineeri↗
NASA NTRS1989

A systems engineering management approach to resource management applications

The author presents a program management response to the following question: How can the traditional practice of systems engineering management, including requirements specification, be adapted, enhanced, or modified to build future planning and scheduling systems for effective operations? The systems engineering management process, as traditionally practiced, is examined. Extensible resource management systems are discussed. It is concluded that extensible systems are a partial solution to problems presented by requirements that are incomplete, partially immeasurable, and often dynamic. There are positive indications that resource management systems have been characterized and modeled sufficiently to allow their implementation as extensible systems.

Hornstein, Rhoda Shaller↗
NASA NTRS1973

Shuttle cryogenic supply system optimization study. Volume 5A-2: Users manual for Space shuttle orbit injection system analysis (SOPSA)

SOPSA (Shuttle Orbit Injection Propulsion System Analysis) is a computer program to aid in the preliminary design of propellant feed systems for the space shuttle orbiter main engines. The primary purpose of the program is to evaluate propellant tank ullage pressure requirements imposed by the need to accelerate propellants rapidly during the engine start sequence. These requirements can influence the system design for a given engine as well as the suitability of a given system for use with different engines. During the vehicle design phase, the SOPSA program is used to establish feed system weight variations as a function of nominal line diameter and component and line configurations. The weight data are used in conjunction with pertinent cost data to establish optimum feed system designs.

Source record↗
NASA NTRS1972

Integration of safety engineering into a cost optimized development program.

A six-segment management model is presented, each segment of which represents a major area in a new product development program. The first segment of the model covers integration of specialist engineers into 'systems requirement definition' or the system engineering documentation process. The second covers preparation of five basic types of 'development program plans.' The third segment covers integration of system requirements, scheduling, and funding of specialist engineering activities into 'work breakdown structures,' 'cost accounts,' and 'work packages.' The fourth covers 'requirement communication' by line organizations. The fifth covers 'performance measurement' based on work package data. The sixth covers 'baseline requirements achievement tracking.'

Ball, L. W.↗
NASA NTRS1973

Cost estimation for unmanned lunar and planetary programs

A basic model is presented for estimating the cost of unmanned lunar and planetary programs. Cost data were collected and analyzed for eight lunar and planetary programs. Total cost was separated into the following components: labor, overhead, materials, and technical support. The study determined that direct labor cost of unmanned lunar and planetary programs comprises 30 percent of the total program cost. Twelve program categories were defined for modeling: six spacecraft subsystem categories (science, structure, propulsion, electrical power, communications, and guidance and integration, test and quality assurance, launch and flight operations, ground equipment, systems analysis and engineering, and program management). An analysis showed that on a percentage basis, direct labor cost and direct labor manhours compare on a one-to-one ratio. Therefore, direct labor hours is used as the parameter for predicting cost, with the advantage of eliminating the effect of inflation on the analysis.

Dunkin, J. H.↗
NASA NTRS1999

1998 NASA Seal/Secondary Air System Workshop

The 1998 NASA Seal/Secondary Air System Workshop was divided into three major areas with limited materials presented in Volume II: (1) overviews of the (NASAs high speed research (HSR) and DOE's advanced turbine engine systems (ATS)) gas turbine programs and the general aviation program (GAP) with emphasis on sealing methods and results; (2) sealing concepts and methods and results including experimental facilities and numerical predictions; and (3) reviews of the numerical engine simulation and aerospace vehicles and concepts (Trailblazer, Bantam, and X-38).

Bruce Steinetz↗
NASA NTRS1983

Scale model performance test investigation of mixed flow exhaust systems for an energy efficient engine /E3/ propulsion system

As part of the NASA Energy Efficient Engine program, scale-model performance tests of a mixed flow exhaust system were conducted. The tests were used to evaluate the performance of exhaust system mixers for high-bypass, mixed-flow turbofan engines. The tests indicated that: (1) mixer penetration has the most significant affect on both mixing effectiveness and mixer pressure loss; (2) mixing/tailpipe length improves mixing effectiveness; (3) gap reduction between the mixer and centerbody increases high mixing effectiveness; (4) mixer cross-sectional shape influences mixing effectiveness; (5) lobe number affects mixing degree; and (6) mixer aerodynamic pressure losses are a function of secondary flows inherent to the lobed mixer concept.

Kuchar, A. P.↗
NASA NTRS1991

Configuration management plan. System definition and project development. Repository Based Software Engineering (RBSE) program

This is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.

Mckay, Charles↗
NASA NTRS1993

Systems engineering and integration and management for manned space flight programs

This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.

Morris, Owen↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Journey to Developing a Concept of Operations

Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.

Jeffrey Robert Cohen↗
NASA NTRS1973

Steady-state simulation program for attitude control propulsion systems

The formulation and the engineering equations employed in the steady state attitude control propulsion system simulation program are presented. The objective of this program is to aid in the preliminary design and development of propulsion systems used for spacecraft attitude control. The program simulates the integrated operation of the many interdependent components typically comprising an attitude control propulsion system. Flexibility, generality, ease of operation, and speed consistent with adequate accuracy were overriding considerations during the development of this program. Simulation modules were developed representing the various types of fluid components typically encountered in an attitude control propulsion system. These modules are basically self-contained and may be arranged by the program user into desired configuration through the program input data.

Heinmiller, P. J.↗
NASA NTRS1984

Automotive Stirling engine systems development

The objective of the Automotive Stirling Engine (ASE) program is to develop a Stirling engine for automotive use that provides a 30 percent improvement in fuel economy relative to a comparable internal-combustion engine while meeting emissions goals. This paper traces the engine systems' development efforts focusing on: (1) a summary of engine system performance for all Mod I engines; (2) the development, program conducted for the upgraded Mod I; and (3) vehicle systems work conducted to enhance vehicle fuel economy. Problems encountered during the upgraded Mod I test program are discussed. The importance of the EPA driving cycle cold-start penalty and the measures taken to minimize that penalty with the Mod II are also addressed.

Richey, A. E.↗