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

Actuation and system design and evaluation OMS engine shutoff valve, Volume 1

A technology program was conducted to identify and verify the optimum valve and actuation system concept for the Space Shuttle Orbit Maneuvering System engine. Of major importance to the valve and actuation system selection was the ten-year, 100-mission, 10,000-cycle life requirement, while maintaining high reliability, low leakage, and low weight. Valve and actuation system concepts were comparatively evaluated against past valve failure reports and potential failure modes due to the shuttle mission profile to aid in the selection of the most optimum concept for design, manufacture and verification testing. Two valve concepts were considered during the preliminary design stage; i.e., the moving seat and lifting ball. Two actuation systems were manufactured and tested. Test results demonstrate the viability of a lifting ball concept as well as the applicability of an ac motor actuation system to best meet the requirements of the shuttle mission.

Dunn, V. B.↗
NASA NTRS2000

NASA's Design and Development of a Field Goniometer Instrument Using Solid Works

With NASA suffering severe funding cutbacks, engineers at NASA are required to produce state-of-the-art hardware with limited personnel and financial resources. In light of these constraints, the new NASA mandate is to build better, faster and cheaper. In April of 1998, Stennis Space Center's Commercial Remote Sensing Program contracted to the Systems Engineering Division at NASA Ames Research Center to develop a device known as a Field Goniometer. A Field Goniometer is a device that measures bi-directional reflectance of a target, such as vegetation, relative to the sun and an imaging system in an aircraft or spacecraft. The device is able to provide a spectral fingerprint of the surface it is measuring in wavelengths from 350nm-2500nm using a hyperspectral imager. To accomplish this project, several obstacles had to be overcome. First, the design had to be completed in less than four months. Second, due to the complexity of the design, the use of solid modeling was highly desirable but most of the group's solid modelers were assigned to other jobs. Third, the amount of funding available from the customer was one half to one third the funding typically expended for a job of this nature. Our choices for this project were to design with standard 2-D CAD systems currently used in-house or train additional engineers on our existing solids package or purchase a new solid model package. The use of a 2D CAD system was very undesirable due to the complexity of the design. Using our existing solids modeler would have required a learning curve for our engineers that would be incompatible with our schedule. Prior to this project, a member of our design group researched the solid modeling industry and decided to purchase SolidWorks. After examining the product for ease of use, modeling capability, training time required and cost, we decided our highest probability of success would be to design with Solidworks. During the design phase, our fabrication group was able to provide input at the very early stages, which added significant benefit to the final product. Fabrication cost and schedule savings have been realized by having complex part geometries translated directly from the SolidWorks design models to Surfcam and other computer-aided manufacturing (CAM) software. This direct model translation capability optimized the fabrication processes. The end result was that we were able to successfully complete the project on time and on budget. Other advantages of using SolidWorks, as cited by the design team, include a rapid negotiation of the initial learning curve, the ability to develop solid model hardware prototypes (used to communicate the design intent to both the customer and the fabricator), and the ability to work as a team collaborating on a large, complex model. These types of tools and efforts represent our response to NASA's challenge to produce higher quality products within shorter design and fabrication times.

Turner, Mark↗
NASA NTRS1990

Program For Engineering Electrical Connections

DFACS is interactive multiuser computer-aided-engineering software tool for system-level electrical integration and cabling engineering. Purpose of program to provide engineering community with centralized data base for putting in and gaining access to data on functional definition of system, details of end-circuit pinouts in systems and subsystems, and data on wiring harnesses. Objective, to provide instantaneous single point of interchange of information, thus avoiding error-prone, time-consuming, and costly shuttling of data along multiple paths. Designed to operate on DEC VAX mini or micro computer using Version 5.0/03 of INGRES.

Billitti, Joseph W.↗
NASA NTRS1991

Manned space nuclear systems design guidelines

The philosophy utilized on space nuclear system design and safety has evolved gradually over the last 30 years in the United States. Past programs have primarily been concerned with unmanned systems, except for the ROVER/NERVA engine development program which was in support of a manned mission to Mars. This papear proposes top level design guidelines for the use of nuclear devices for manned space applications. The guidelines presented cover failure and redundancy criteria, payload and flight vehicle specifications, environmental compatibility, mission operational constraints, construction and servicing, and radiation constraints. This paper also raises design and operational concerns requiring further examination. The purpose of this paper is to provide direction for the development of manned space nuclear systems currently envisioned for the Space Exploration Initiative.

Sanders, Jerry B.↗
NASA NTRS1999

Dynamic Altitude Simulation System Performance Modeling

The "Dynamic Altitude Simulation Prediction Program," DASSPP, is a program to predict the transient response of an engine, test cell, ejector system under engine shutdown conditions. These transients are important to know so that corrective modifications can be adapted to prevent any damage to the engine or test cell. The "Dynamic Altitude System Simulation Prediction Program," DASSPP, is a major rewrite of the existing program "RL-1000" written in BASIC. The RL-1000 program was written to analyze the transients of the RL-10 system only. The new program is written to run in Excell 97 and utilizes the Visual BASIC language in Excell. The program has many added features not included in the original "Rl-1000" program. The program utilizes the ejector models developed during the summer of 1997. The new program is very user friendly and utilizes a dialog box for data input.

LaFrance, Leo J.↗
NASA NTRS1978

Applications of hybrid and digital computation methods in aerospace-related sciences and engineering

The computing equipment in the engineering systems simulation laboratory of the Houston University Cullen College of Engineering is described and its advantages are summarized. The application of computer techniques in aerospace-related research psychology and in chemical, civil, electrical, industrial, and mechanical engineering is described in abstracts of 84 individual projects and in reprints of published reports. Research supports programs in acoustics, energy technology, systems engineering, and environment management as well as aerospace engineering.

Huang, C. J.↗
NASA NTRS1996

A Database for Propagation Models and Conversion to C++ Programming Language

The telecommunications system design engineer generally needs the quantification of effects of the propagation medium (definition of the propagation channel) to design an optimal communications system. To obtain the definition of the channel, the systems engineer generally has a few choices. A search of the relevant publications such as the IEEE Transactions, CCIR's, NASA propagation handbook, etc., may be conducted to find the desired channel values. This method may need excessive amounts of time and effort on the systems engineer's part and there is a possibility that the search may not even yield the needed results. To help the researcher and the systems engineers, it was recommended by the conference participants of NASA Propagation Experimenters (NAPEX) XV (London, Ontario, Canada, June 28 and 29, 1991) that a software should be produced that would contain propagation models and the necessary prediction methods of most propagation phenomena. Moreover, the software should be flexible enough for the user to make slight changes to the models without expending a substantial effort in programming. In the past few years, a software was produced to fit these requirements as best as could be done. The software was distributed to all NAPEX participants for evaluation and use, the participant reactions, suggestions etc., were gathered and were used to improve the subsequent releases of the software. The existing database program is in the Microsoft Excel application software and works fine within the guidelines of that environment, however, recently there have been some questions about the robustness and survivability of the Excel software in the ever changing (hopefully improving) world of software packages.

Kantak, Anil V.↗
NASA NTRS1989

Large liquid rocket engine transient performance simulation system

Phase 1 of the Rocket Engine Transient Simulation (ROCETS) program consists of seven technical tasks: architecture; system requirements; component and submodel requirements; submodel implementation; component implementation; submodel testing and verification; and subsystem testing and verification. These tasks were completed. Phase 2 of ROCETS consists of two technical tasks: Technology Test Bed Engine (TTBE) model data generation; and system testing verification. During this period specific coding of the system processors was begun and the engineering representations of Phase 1 were expanded to produce a simple model of the TTBE. As the code was completed, some minor modifications to the system architecture centering on the global variable common, GLOBVAR, were necessary to increase processor efficiency. The engineering modules completed during Phase 2 are listed: INJTOO - main injector; MCHBOO - main chamber; NOZLOO - nozzle thrust calculations; PBRNOO - preburner; PIPE02 - compressible flow without inertia; PUMPOO - polytropic pump; ROTROO - rotor torque balance/speed derivative; and TURBOO - turbine. Detailed documentation of these modules is in the Appendix. In addition to the engineering modules, several submodules were also completed. These submodules include combustion properties, component performance characteristics (maps), and specific utilities. Specific coding was begun on the system configuration processor. All functions necessary for multiple module operation were completed but the SOLVER implementation is still under development. This system, the Verification Checkout Facility (VCF) allows interactive comparison of module results to store data as well as provides an intermediate checkout of the processor code. After validation using the VCF, the engineering modules and submodules were used to build a simple TTBE.

Mason, J. R.↗
NASA NTRS1986

Software engineering environment tool set integration

Space Transportation System Division (STSD) Engineering has a program to promote excellence within the engineering function. This program resulted in a capital funded facility based on a VAX cluster called the Rockwell Operational Engineering System (ROSES). The second phase of a three phase plan to establish an integrated software engineering environment for ROSES is examined. It discusses briefly phase one which establishes the basic capability for a modern software development environment to include a tool set, training and standards. Phase two is a tool set integration. The tool set is primarily off-the-shelf tools acquired through vendors or government agencies (public domain). These tools were placed into categories of software development. These categories are: requirements, design, and construction support; verification and validation support; and software management support. The integration of the tool set is being performed through concept prototyping and development of tools specifically designed to support the life cycle and provide transition from one phase to the next.

Selfridge, William P.↗
NASA NTRS2019

Assessment of MON-25/MMH Propellant System for Deep-Space Engines

Hypergolic propellant system of oxidizer MON-25 and fuel MMH has been considered in propulsion trade studies for NASA science mission concepts. A propulsion system using this bi-propellant combination will be capable of operating at a lower temperature as compared to traditional MON-3/MMH for heater power reduction. Operation robustness can also be realized since such a propellant system is utilized under a wide range of temperatures. Propulsion system designs and engine test programs for MON-25/MMH have been carried out since 2008. Several engine development programs have been conducted. The thrust classes of 22-Newton [5-lb(sub f)] and 445-Newton [100-lb(sub f)] were tested with the capability of a pulse mode operation for a wide range of duty cycles. Additional engine development tests are followed. Outcomes of the development efforts suggest that there is a balance of mission benefits and potential engine design and operation challenges, although the propellants can handle a low temperature. This paper will report an assessment of using the MON-25/MMH system for deep- space application.

Trinh, Huu P.↗
NASA NTRS1991

Telecommunications, navigation and information management concept overview for the Space Exploration Initiative program

An overview is provided of the Space Exploration Initiative (SEI) concepts for telecommunications, information systems, and navigation (TISN), and engineering and architecture issues are discussed. The SEI program data system is reviewed to identify mission TISN interfaces, and reference TISN concepts are described for nominal, degraded, and mission-critical data services. The infrastructures reviewed include telecommunications for robotics support, autonomous navigation without earth-based support, and information networks for tracking and data acquisition. Four options for TISN support architectures are examined which relate to unique SEI exploration strategies. Detailed support estimates are given for: (1) a manned stay on Mars; (2) permanent lunar and Martian settlements; short-duration missions; and (4) systematic exploration of the moon and Mars.

Bell, Jerome A.↗
NASA NTRS1997

The Goddard High Resolution Spectrograph Scientific Support Contract

In 1988, Computer Sciences Corporation (CSC) was selected as the Goddard High Resolution Spectrograph (GHRS) Scientific Support Contractor (SSC). This was to have been a few months before the launch of NASA's first Great Observatory, the Hubble Space Telescope (HST). As one of five scientific instruments on HST, the GHRS was designed to obtain spectra in the 1050-3300 A ultraviolet wavelength region with a resolving power, lambda/Delta(lambda) , of up to 100,000 and relative photometric accuracy to 1%. It was built by Ball AeroSpace Systems Group under the guidance of the GHRS Investigation Definition Team (IDT), comprised of 16 scientists from the US and Canada. After launch, the IDT was to perform the initial instrument calibration and execute a broad scientific program during a five-year Guaranteed Time Observation (GTO) period. After a year's delay, the launch of HST occurred in April 1990, and CSC participated in the in-orbit calibration and first four years of GTO observations with the IDT. The HST primary mirror suffered from spherical aberration, which reduced the spatial and spectral resolution of Large Science Aperture (LSA) observations and decreased the throughput of the Small Science Aperture (SSA) by a factor of two. Periodic problems with the Side 1 carrousel electronics and anomalies with the low-voltage power supply finally resulted in a suspension of the use of Side 1 less than two years after launch. At the outset, the GHRS SSC task involved work in four areas: 1) to manage and operate the GHRS Data Analysis Facility (DAF); 2) to support the second Servicing Mission Observatory Verification (SMOV) program, as well as perform system engineering analysis of the GHRS as nesessary; 3) to assist the GHRS IDT with their scientific research programs, particularly the GSFC members of the team, and 4) to provide administrative and logistic support for GHRS public information and educational activities.

Source record↗