Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “system engineering system process”

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 919 records · Page 51

SLS Navigation Model-Based Design Approach

The SLS Program chose to implement a Model-based Design and Model-based Requirements approach for managing component design information and system requirements. This approach differs from previous large-scale design efforts at Marshall Space Flight Center where design documentation alone conveyed information required for vehicle design and analysis and where extensive requirements sets were used to scope and constrain the design. The SLS Navigation Team has been responsible for the Program-controlled Design Math Models (DMMs) which describe and represent the performance of the Inertial Navigation System (INS) and the Rate Gyro Assemblies (RGAs) used by Guidance, Navigation, and Controls (GN&C). The SLS Navigation Team is also responsible for the navigation algorithms. The navigation algorithms are delivered for implementation on the flight hardware as a DMM. For the SLS Block 1-B design, the additional GPS Receiver hardware is managed as a DMM at the vehicle design level. This paper provides a discussion of the processes and methods used to engineer, design, and coordinate engineering trades and performance assessments using SLS practices as applied to the GN&C system, with a particular focus on the Navigation components. These include composing system requirements, requirements verification, model development, model verification and validation, and modeling and analysis approaches. The Model-based Design and Requirements approach does not reduce the effort associated with the design process versus previous processes used at Marshall Space Flight Center. Instead, the approach takes advantage of overlap between the requirements development and management process, and the design and analysis process by efficiently combining the control (i.e. the requirement) and the design mechanisms. The design mechanism is the representation of the component behavior and performance in design and analysis tools. The focus in the early design process shifts from the development and management of design requirements to the development of usable models, model requirements, and model verification and validation efforts. The models themselves are represented in C/C++ code and accompanying data files. Under the idealized process, potential ambiguity in specification is reduced because the model must be implementable versus a requirement which is not necessarily subject to this constraint. Further, the models are shown to emulate the hardware during validation. For models developed by the Navigation Team, a common interface/standalone environment was developed. The common environment allows for easy implementation in design and analysis tools. Mechanisms such as unit test cases ensure implementation as the developer intended. The model verification and validation process provides a very high level of component design insight. The origin and implementation of the SLS variant of Model-based Design is described from the perspective of the SLS Navigation Team. The format of the models and the requirements are described. The Model-based Design approach has many benefits but is not without potential complications. Key lessons learned associated with the implementation of the Model Based Design approach and process from infancy to verification and certification are discussed

Oliver, T. Emerson↗

NASA Data Acquisition System Software Development for Rocket Propulsion Test Facilities

Current NASA propulsion test facilities include Stennis Space Center in Mississippi, Marshall Space Flight Center in Alabama, Plum Brook Station in Ohio, and White Sands Test Facility in New Mexico. Within and across these centers, a diverse set of data acquisition systems exist with different hardware and software platforms. The NASA Data Acquisition System (NDAS) is a software suite designed to operate and control many critical aspects of rocket engine testing. The software suite combines real-time data visualization, data recording to a variety formats, short-term and long-term acquisition system calibration capabilities, test stand configuration control, and a variety of data post-processing capabilities. Additionally, data stream conversion functions exist to translate test facility data streams to and from downstream systems, including engine customer systems. The primary design goals for NDAS are flexibility, extensibility, and modularity. Providing a common user interface for a variety of hardware platforms helps drive consistency and error reduction during testing. In addition, with an understanding that test facilities have different requirements and setups, the software is designed to be modular. One engine program may require real-time displays and data recording; others may require more complex data stream conversion, measurement filtering, or test stand configuration management. The NDAS suite allows test facilities to choose which components to use based on their specific needs. The NDAS code is primarily written in LabVIEW, a graphical, data-flow driven language. Although LabVIEW is a general-purpose programming language; large-scale software development in the language is relatively rare compared to more commonly used languages. The NDAS software suite also makes extensive use of a new, advanced development framework called the Actor Framework. The Actor Framework provides a level of code reuse and extensibility that has previously been difficult to achieve using LabVIEW. The

Herbert, Phillip W., Sr.↗

Review of Combustion-acoustic Instabilities

Combustion-acoustic instabilities occur when the acoustic energy increase due to the unsteady heat release of the flame is greater than the losses of acoustic energy from the system. The problem of combustion-acoustic instability is a concern in many devices for various reasons, as each device may have a unique mechanism causing unsteady heat release rates and many have unique boundary conditions. To accurately predict and quantify combustion-acoustic stabilities, the unsteady heat release rate and boundary conditions need to be accurately determined. The present review brings together work performed on a variety of practical combustion devices. Many theoretical and experimental investigations of the unsteady heat release rate have been performed, some based on perturbations in the fuel delivery system particularly for rocket instabilities, while others are based on hydrodynamic processes as in ramjet dump combustors. The boundary conditions for rocket engines have been analyzed and measured extensively. However, less work has been done to measure acoustic boundary conditions in many other combustion systems.

Oyediran, Ayo↗

IEEE/AIAA/NASA Digital Avionics Systems Conference, 9th, Virginia Beach, VA, Oct. 15-18, 1990, Proceedings

The present conference on digital avionics discusses vehicle-management systems, spacecraft avionics, special vehicle avionics, communication/navigation/identification systems, software qualification and quality assurance, launch-vehicle avionics, Ada applications, sensor and signal processing, general aviation avionics, automated software development, design-for-testability techniques, and avionics-software engineering. Also discussed are optical technology and systems, modular avionics, fault-tolerant avionics, commercial avionics, space systems, data buses, crew-station technology, embedded processors and operating systems, AI and expert systems, data links, and pilot/vehicle interfaces.

Source record↗

Spacecraft Electrical Connector Selection and Application Processes

This assessment was initiated by the NASA Engineering & Safety Center (NESC) after a number of recent "high profile" connector problems, the most visible and publicized of these being the problem with the Space Shuttle's Engine Cut-Off System cryogenic feed-thru connector. The NESC commissioned a review of NASA's connector selection and application processes for space flight applications, including how lessons learned and past problem records are fed back into the processes to avoid recurring issues. Team members were primarily from the various NASA Centers and included connector and electrical parts specialists. The commissioned study was conducted on spacecraft connector selection and application processes at NASA Centers. The team also compared the NASA spacecraft connector selection and application process to the military process, identified recent high profile connector failures, and analyzed problem report data looking for trends and common occurrences. The team characterized NASA's connector problem experience into a list of top connector issues based on anecdotal evidence of a system's impact and commonality between Centers. These top issues are as follows, in no particular rank order: electrically shorted, bent and/or recessed contact pins, contact pin/socket contamination leading to electrically open or intermittencies, connector plating corrosion or corrosion of connector components, low or inadequate contact pin retention forces, contact crimp failures, unmated connectors and mis-wiring due to workmanship errors during installation or maintenance, loose connectors due to manufacturing defects such as wavy washer and worn bayonet retention, damaged connector elastomeric seals and cryogenic connector failure. A survey was also conducted of SAE Connector AE-8C1 committee members regarding their experience relative to the NASA concerns on connectors. The most common responses in order of occurrence were contact retention, plating issues, worn-out or damaged coupling mechanisms, bent pins, contact crimp barrel cracking and torn seals. In addition to these common themes, responses included issues with markings, dimensional errors on the build, contact/socket damage (handling), manufacturing defects and customer misapplication and mishandling. The NESC team concluded that considering the large quantity and wide variety of connectors successfully flown on human and robotic space applications, the number of failures is quite low. However, "high profile" failures with significant cost, schedule, safety, and/or mission success impacts continue to occur. It was also concluded that connector failures occur throughout a system's life-cycle with the majority of connector issues application related. A number of recommendations were identified for improving NASA connector selection processes and overall space connector reliability and performance.

Iannello, Chris↗

Benefits of Using a Mars Forward Strategy for Lunar Surface Systems

This paper identifies potential risk reduction, cost savings and programmatic procurement benefits of a Mars Forward Lunar Surface System architecture that provides commonality or evolutionary development paths for lunar surface system elements applicable to Mars surface systems. The objective of this paper is to identify the potential benefits for incorporating a Mars Forward development strategy into the planned Project Constellation Lunar Surface System Architecture. The benefits include cost savings, technology readiness, and design validation of systems that would be applicable to lunar and Mars surface systems. The paper presents a survey of previous lunar and Mars surface systems design concepts and provides an assessment of previous conclusions concerning those systems in light of the current Project Constellation Exploration Architectures. The operational requirements for current Project Constellation lunar and Mars surface system elements are compared and evaluated to identify the potential risk reduction strategies that build on lunar surface systems to reduce the technical and programmatic risks for Mars exploration. Risk reduction for rapidly evolving technologies is achieved through systematic evolution of technologies and components based on Moore's Law superimposed on the typical NASA systems engineering project development "V-cycle" described in NASA NPR 7120.5. Risk reduction for established or slowly evolving technologies is achieved through a process called the Mars-Ready Platform strategy in which incremental improvements lead from the initial lunar surface system components to Mars-Ready technologies. The potential programmatic benefits of the Mars Forward strategy are provided in terms of the transition from the lunar exploration campaign to the Mars exploration campaign. By utilizing a sequential combined procurement strategy for lunar and Mars exploration surface systems, the overall budget wedges for exploration systems are reduced and the costly technological development gap between the lunar and Mars programs can be eliminated. This provides a sustained level of technological competitiveness as well as maintaining a stable engineering and manufacturing capability throughout the entire duration of Project Constellation.

Mulqueen, Jack↗

An expert system for integrated structural analysis and design optimization for aerospace structures

The results of a research study on the development of an expert system for integrated structural analysis and design optimization is presented. An Object Representation Language (ORL) was developed first in conjunction with a rule-based system. This ORL/AI shell was then used to develop expert systems to provide assistance with a variety of structural analysis and design optimization tasks, in conjunction with procedural modules for finite element structural analysis and design optimization. The main goal of the research study was to provide expertise, judgment, and reasoning capabilities in the aerospace structural design process. This will allow engineers performing structural analysis and design, even without extensive experience in the field, to develop error-free, efficient and reliable structural designs very rapidly and cost-effectively. This would not only improve the productivity of design engineers and analysts, but also significantly reduce time to completion of structural design. An extensive literature survey in the field of structural analysis, design optimization, artificial intelligence, and database management systems and their application to the structural design process was first performed. A feasibility study was then performed, and the architecture and the conceptual design for the integrated 'intelligent' structural analysis and design optimization software was then developed. An Object Representation Language (ORL), in conjunction with a rule-based system, was then developed using C++. Such an approach would improve the expressiveness for knowledge representation (especially for structural analysis and design applications), provide ability to build very large and practical expert systems, and provide an efficient way for storing knowledge. Functional specifications for the expert systems were then developed. The ORL/AI shell was then used to develop a variety of modules of expert systems for a variety of modeling, finite element analysis, and design optimization tasks in the integrated aerospace structural design process. These expert systems were developed to work in conjunction with procedural finite element structural analysis and design optimization modules (developed in-house at SAT, Inc.). The complete software, AutoDesign, so developed, can be used for integrated 'intelligent' structural analysis and design optimization. The software was beta-tested at a variety of companies, used by a range of engineers with different levels of background and expertise. Based on the feedback obtained by such users, conclusions were developed and are provided.

Source record↗

Telemetry Boards Interpret Rocket, Airplane Engine Data

For all the data gathered by the space shuttle while in orbit, NASA engineers are just as concerned about the information it generates on the ground. From the moment the shuttle s wheels touch the runway to the break of its electrical umbilical cord at 0.4 seconds before its next launch, sensors feed streams of data about the status of the vehicle and its various systems to Kennedy Space Center s shuttle crews. Even while the shuttle orbiter is refitted in Kennedy s orbiter processing facility, engineers constantly monitor everything from power levels to the testing of the mechanical arm in the orbiter s payload bay. On the launch pad and up until liftoff, the Launch Control Center, attached to the large Vehicle Assembly Building, screens all of the shuttle s vital data. (Once the shuttle clears its launch tower, this responsibility shifts to Mission Control at Johnson Space Center, with Kennedy in a backup role.) Ground systems for satellite launches also generate significant amounts of data. At Cape Canaveral Air Force Station, across the Banana River from Kennedy s location on Merritt Island, Florida, NASA rockets carrying precious satellite payloads into space flood the Launch Vehicle Data Center with sensor information on temperature, speed, trajectory, and vibration. The remote measurement and transmission of systems data called telemetry is essential to ensuring the safe and successful launch of the Agency s space missions. When a launch is unsuccessful, as it was for this year s Orbiting Carbon Observatory satellite, telemetry data also provides valuable clues as to what went wrong and how to remedy any problems for future attempts. All of this information is streamed from sensors in the form of binary code: strings of ones and zeros. One small company has partnered with NASA to provide technology that renders raw telemetry data intelligible not only for Agency engineers, but also for those in the private sector.

Source record↗

Coupled Reactor and Engine Nuclear Thermal Propulsion Modeling Methodology

The design and development process of a Nuclear Thermal Propulsion (NTP) system requires extensive multiphysics modeling to couple the neutron physics and thermal feedback effects to determine the reactor’s power shape. Propulsion system performance codes utilize this power shape to determine NTP key performance parameters. While the power shape is heavily dependent on the temperature profile and geometry of the reactor, many analyses either assume a constant power shape, or use neutronics analysis to determine a power shape for a specific reactor configuration. The development of a coupling interface for a propulsion system performance code and a Monte Carlo neutron transport code (OpenMC) allows for the reactor power shape to be calculated in a Picard iteration.

Jacob Stonehill↗

Coupled Reactor and Engine Nuclear Thermal Propulsion Modeling Methodology

The design and development process of a Nuclear Thermal Propulsion (NTP) system requires extensive multiphysics modeling to couple the neutron physics and thermal feedback effects to determine the reactor’s power shape. Propulsion system performance codes utilize this power shape to determine NTP key performance parameters. While the power shape is heavily dependent on the temperature profile and geometry of the reactor, many analyses either assume a constant power shape, or use neutronics analysis to determine a power shape for a specific reactor configuration. The development of a coupling interface for a propulsion system performance code and a Monte Carlo neutron transport code (OpenMC) allows for the reactor power shape to be calculated in an iteration loop. The interface utilizes a file share system to transfer geometry dimensions, temperatures, and material identifiers to OpenMC, which is used to perform a neutron transport simulation of a design like the government Testing Reference Design reactor. The interface is then able to post-process the results from OpenMC and use the same file share system to share a power shape and other important neutron transport parameters to the system performance code. Initial results show that neglecting the changes to power shape when comparing reactor configurations can yield inaccurate results. Furthermore, utilizing propellants other than hydrogen gas can cause significant changes to the power shape, and thus, the thermal performance of a specific reactor design. This methodology is being expanded to allow for multiple families of NTP reactors to be analyzed, including block moderator, particle bed, and NERVA-derived reactors.

multiphysics coupling↗

Coupled Reactor and Engine Nuclear Thermal Propulsion Modeling Methodology

The design and development process of a Nuclear Thermal Propulsion (NTP) system requires extensive multiphysics modeling to couple the neutron physics and thermal feedback effects to determine the reactor’s power shape. Propulsion system performance codes utilize this power shape to determine NTP key performance parameters. While the power shape is heavily dependent on the temperature profile and geometry of the reactor, many analyses either assume a constant power shape, or use neutronics analysis to determine a power shape for a specific reactor configuration. The development of a coupling interface for a propulsion system performance code and a Monte Carlo neutron transport code (OpenMC) allows for the reactor power shape to be calculated in an iteration loop. The interface utilizes a file share system to transfer geometry dimensions, temperatures, and material identifiers to OpenMC, which is used to perform a neutron transport simulation of a design like the government Testing Reference Design reactor. The interface is then able to post-process the results from OpenMC and use the same file share system to share a power shape and other important neutron transport parameters to the system performance code. Initial results show that neglecting the changes to power shape when comparing reactor configurations can yield inaccurate results. Furthermore, utilizing propellants other than hydrogen gas can cause significant changes to the power shape, and thus, the thermal performance of a specific reactor design. This methodology is being expanded to allow for multiple families of NTP reactors to be analyzed, including block moderator, particle bed, and NERVA-derived reactors.

multiphysics coupling↗

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗

ELISA, a demonstrator environment for information systems architecture design

This paper describes an approach of reusability of software engineering technology in the area of ground space system design. System engineers have lots of needs similar to software developers: sharing of a common data base, capitalization of knowledge, definition of a common design process, communication between different technical domains. Moreover system designers need to simulate dynamically their system as early as possible. Software development environments, methods and tools now become operational and widely used. Their architecture is based on a unique object base, a set of common management services and they host a family of tools for each life cycle activity. In late '92, CNES decided to develop a demonstrative software environment supporting some system activities. The design of ground space data processing systems was chosen as the application domain. ELISA (Integrated Software Environment for Architectures Specification) was specified as a 'demonstrator', i.e. a sufficient basis for demonstrations, evaluation and future operational enhancements. A process with three phases was implemented: system requirements definition, design of system architectures models, and selection of physical architectures. Each phase is composed of several activities that can be performed in parallel, with the provision of Commercial Off the Shelves Tools. ELISA has been delivered to CNES in January 94, currently used for demonstrations and evaluations on real projects (e.g. SPOT4 Satellite Control Center). It is on the way of new evolutions.

Panem, Chantal↗

Maturation of Additive Manufactured Aerospace Alloys and Development of Mechanical and Thermophysical Properties for Space Applications

The National Aeronautics and Space Administration (NASA) has been involved in the development and maturation of metal additive manufacturing (AM) for space applications since the late 2000’s. Several efforts have focused on the understanding of AM processes through design optimization, component fabrication, material characterization, testing, standards development, and infusion into propulsion development for flight applications. NASA and partners have matured commonly used aerospace alloys from various alloy families (Nickel, Steel, Iron, Aluminum, and Titanium) and AM processes. An extensive effort has been ongoing between NASA, industry partners, and academia to complete detailed AM process and heat treatment characterization, in addition to generating temperature-dependent mechanical and thermophysical properties. This presentation highlights the characterization and property results using laser powder bed fusion (L-PBF) and laser powder directed energy deposition (LP-DED) processes among various alloys. In addition to commonly used alloys, there is a need for ongoing AM optimized alloys using integrated computational materials engineering (ICME) and process development for high performance applications. The applications targeted are launch vehicles, liquid rocket engines, advanced propulsion systems, advanced power systems, and in-space propulsion with high heat fluxes, high pressure, and that utilize propellants such as hydrogen, which can degrade alloys. This presentation will also discuss some of the ongoing novel alloy development and maturation using AM for use in these harsh environments, such as GRCop-42, GRCop-84, NASA HR-1, and C-103. The results from these processes have demonstrated that AM can enable rapid development and new AM optimized alloys can yield higher performance. These alloys have undergone modeling, fundamental metallurgical evaluations, heat treatment studies, and microstructure characterization and mechanical testing campaigns. This, combined with direct application-specific component fabrication and hot-fire testing, can enable the increase of the Technology Readiness Level (TRL) through high duty-cycle testing. This presentation provides a background and overview of these various common and AM-enabled alloys and processing developments including the initial effort related to metallurgical, mechanical, and thermophysical property studies. It also covers the latest advancement in the parallel component development, hot-fire testing, and future developments for these alloys.

Additive Manufacturing↗

The Role of Computers in Research and Development at Langley Research Center

This document is a compilation of presentations given at a workshop on the role cf computers in research and development at the Langley Research Center. The objectives of the workshop were to inform the Langley Research Center community of the current software systems and software practices in use at Langley. The workshop was organized in 10 sessions: Software Engineering; Software Engineering Standards, methods, and CASE tools; Solutions of Equations; Automatic Differentiation; Mosaic and the World Wide Web; Graphics and Image Processing; System Design Integration; CAE Tools; Languages; and Advanced Topics.

Wieseman, Carol D.↗

Multidisciplinary Expert-aided Analysis and Design (MEAD)

The MEAD Computer Program (MCP) is being developed under the Multidisciplinary Expert-Aided Analysis and Design (MEAD) Project as a CAD environment in which integrated flight, propulsion, and structural control systems can be designed and analyzed. The MCP has several embedded computer-aided control engineering (CACE) packages, a user interface (UI), a supervisor, a data-base manager (DBM), and an expert system (ES). The supervisor monitors and coordinates the operation of the CACE packages, the DBM; the ES, and the UI. The DBM tracks the control design process. Models created or installed by the MCP are tracked by date and version, and results are associated with the specific model version with which they were generated. The ES is used to relieve the control engineer from tedious and cumbersome tasks in the iterative design process. The UI provides the capability for a novice as well as an expert to utilize the MCP easily and effectively. The MCP version 2(MCP-2.0) is fully developed for flight control system design and analysis. Propulsion system modeling, analysis, and simulation is also supported; the same is true for structural models represented in state-space form. The ultimate goal is to cover the integration of flight, propulsion, and structural control engineering, including all discipline-specific functionality and interfaces. The current MCP-2.0 components and functionality are discussed.

Hummel, Thomas C.↗

Advanced Turbine Technology Applications Project (ATTAP)

The Advanced Turbine Technologies Application Project (ATTAP) is in the fifth year of a multiyear development program to bring the automotive gas turbine engine to a state at which industry can make commercialization decisions. Activities during the past year included reference powertrain design updates, test-bed engine design and development, ceramic component design, materials and component characterization, ceramic component process development and fabrication, ceramic component rig testing, and test-bed engine fabrication and testing. Engine design and development included mechanical design, combustion system development, alternate aerodynamic flow testing, and controls development. Design activities included development of the ceramic gasifier turbine static structure, the ceramic gasifier rotor, and the ceramic power turbine rotor. Material characterization efforts included the testing and evaluation of five candidate high temperature ceramic materials. Ceramic component process development and fabrication, with the objective of approaching automotive volumes and costs, continued for the gasifier turbine rotor, gasifier turbine scroll, extruded regenerator disks, and thermal insulation. Engine and rig fabrication, testing, and development supported improvements in ceramic component technology. Total test time in 1992 amounted to 599 hours, of which 147 hours were engine testing and 452 were hot rig testing.

Source record↗

Process Algebra Approach for Action Recognition in the Maritime Domain

The maritime environment poses a number of challenges for autonomous operation of surface boats. Among these challenges are the highly dynamic nature of the environment, the onboard sensing and reasoning requirements for obeying the navigational rules of the road, and the need for robust day/night hazard detection and avoidance. Development of full mission level autonomy entails addressing these challenges, coupled with inference of the tactical and strategic intent of possibly adversarial vehicles in the surrounding environment. This paper introduces PACIFIC (Process Algebra Capture of Intent From Information Content), an onboard system based on formal process algebras that is capable of extracting actions/activities from sensory inputs and reasoning within a mission context to ensure proper responses. PACIFIC is part of the Behavior Engine in CARACaS (Cognitive Architecture for Robotic Agent Command and Sensing), a system that is currently running on a number of U.S. Navy unmanned surface and underwater vehicles. Results from a series of experimental studies that demonstrate the effectiveness of the system are also presented.

process algebras↗