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 1,045 records · Page 58

Communications and Intelligent Systems Division Overview

Provides expertise, and plans, conducts and directs research and engineering development in the competency fields of advanced communications and intelligent systems technologies for applications in current and future aeronautics and space systems.Advances communication systems engineering, development and analysis needed for Glenn Research Center's leadership in communications and intelligent systems technology. Focus areas include advanced high frequency devices, components, and antennas; optical communications, health monitoring and instrumentation; digital signal processing for communications and navigation, and cognitive radios; network architectures, protocols, standards and network-based applications; intelligent controls, dynamics and diagnostics; and smart micro- and nano-sensors and harsh environment electronics. Research and discipline engineering allow for the creation of innovative concepts and designs for aerospace communication systems with reduced size and weight, increased functionality and intelligence. Performs proof-of-concept studies and analyses to assess the impact of the new technologies.

Intelligent Systems↗

A Prognostic Launch Vehicle Probability of Failure Assessment Methodology for Conceptual Systems Predicated on Human Causal Factors

Create an improved method to calculate reliability of a conceptual launch vehicle system prior to fabrication by using historic data of actual root causes of failures. While failures have unique "proximate causes", there are typically a finite amount of common "root causes". Heretofore launch vehicle reliability evaluation typically hardware-centric statistical analyses, while most root causes of failures are been shown to be human-centric. A method based on human-centric root causes can be used to quantify reliability assessments and focus proposed actions to mitigate problems. Existing methods have been optimistic in their projections of launch vehicle reliability compared to actuals. Hypothesis: reliability of a conceptual launch vehicle can be more accurately evaluated based on a rational, probabilistic approach using past failure assessment teams' findings predicated on human-centric causes."Human Reliability Analysis Methods Selection Guidance for NASA"Chandler F.T., et al., NASA HQ/OSMA study group, July 2006. Outside HRA experts from academia, other federal labs, and the private sector. 50 system reliability methods considered, fourteen selected for further study, four finally selected as best suited for human spaceflight. Probabilistic Risk Analysis (PRA) + Human Reliability Analysis (HRA) enabled incorporating effects and probabilities of human errors. While four down-selected methods deemed appropriate for failure assessment, it did not appear that these methods could be concisely applied to perform major system-wide assessment of probability of failure of a conceptual design without becoming unwieldy."Engineering a Safer World", Detailed, comprehensive study external to NASA Leveson N. G., MIT, 2011.Systems-Theoretic Accident Model and Processes (STAMP). All-encompassing accident model based on systems theory analyzed accidents after they occurred and created approaches to prevent occurrence in developing systems not focused on failure prevention per se, but rather reducing hazards by influencing human behavior through use of constraints, hierarchical control structures, and process models to improve system safetySystem Theoretic Process Analysis (STPA) addresses predictive part of problem (a "hazard analysis"). Includes all causal factors identified in STAMP: "...design errors, software flaws, component interaction accidents, cognitively complex human decision-making errors, and social organizational and management factors contributing to accidents" can guide design process rather than require it to exist before-hand did not appear capable of concise application for system-wide assessment of probability of failure of a conceptual design without becoming unwieldy.

Williams, Craig H.↗

Knowledge engineering for temporal dependency networks as operations procedures

This paper presents a case study of the knowledge engineering process employed to support the Link Monitor and Control Operator Assistant (LMCOA). The LMCOA is a prototype system which automates the configuration, calibration, test, and operation (referred to as precalibration) of the communications, data processing, metric data, antenna, and other equipment used to support space-ground communications with deep space spacecraft in NASA's Deep Space Network (DSN). The primary knowledge base in the LMCOA is the Temporal Dependency Network (TDN), a directed graph which provides a procedural representation of the precalibration operation. The TDN incorporates precedence, temporal, and state constraints and uses several supporting knowledge bases and data bases. The paper provides a brief background on the DSN, and describes the evolution of the TDN and supporting knowledge bases, the process used for knowledge engineering, and an analysis of the successes and problems of the knowledge engineering effort.

Fayyad, Kristina E.↗

Knowledge-Based Aircraft Automation: Managers Guide on the use of Artificial Intelligence for Aircraft Automation and Verification and Validation Approach for a Neural-Based Flight Controller

The ultimate goal of this report was to integrate the powerful tools of artificial intelligence into the traditional process of software development. To maintain the US aerospace competitive advantage, traditional aerospace and software engineers need to more easily incorporate the technology of artificial intelligence into the advanced aerospace systems being designed today. The future goal was to transition artificial intelligence from an emerging technology to a standard technology that is considered early in the life cycle process to develop state-of-the-art aircraft automation systems. This report addressed the future goal in two ways. First, it provided a matrix that identified typical aircraft automation applications conducive to various artificial intelligence methods. The purpose of this matrix was to provide top-level guidance to managers contemplating the possible use of artificial intelligence in the development of aircraft automation. Second, the report provided a methodology to formally evaluate neural networks as part of the traditional process of software development. The matrix was developed by organizing the discipline of artificial intelligence into the following six methods: logical, object representation-based, distributed, uncertainty management, temporal and neurocomputing. Next, a study of existing aircraft automation applications that have been conducive to artificial intelligence implementation resulted in the following five categories: pilot-vehicle interface, system status and diagnosis, situation assessment, automatic flight planning, and aircraft flight control. The resulting matrix provided management guidance to understand artificial intelligence as it applied to aircraft automation. The approach taken to develop a methodology to formally evaluate neural networks as part of the software engineering life cycle was to start with the existing software quality assurance standards and to change these standards to include neural network development. The changes were to include evaluation tools that can be applied to neural networks at each phase of the software engineering life cycle. The result was a formal evaluation approach to increase the product quality of systems that use neural networks for their implementation.

Broderick, Ron↗

Collection, processing and dissemination of data for the national solar demonstration program

A national solar data system developed for the DOE by IBM provides for automatic gathering, conversion, transfer, and analysis of demonstration site data. NASA requirements for this system include providing solar site hardware, engineering, data collection, and analysis. The specific tasks include: (1) solar energy system design/integration; (2) developing a site data acquisition subsystem; (3) developing a central data processing system; (4) operating the test facility at Marshall Space Flight Center; (5) collecting and analyzing data. The systematic analysis and evaluation of the data from the National Solar Data System is reflected in a monthly performance report and a solar energy system performance evaluation report.

Day, R. E.↗

Role of Process Control in Improving Space Vehicle Safety A Space Shuttle External Tank Example

Developing a safe and reliable space vehicle requires good design and good manufacturing, or in other words "design it right and build it right". A great design can be hard to build or manufacture mainly due to difficulties related to quality. Specifically, process control can be a challenge. As a result, the system suffers from low quality which leads to low reliability and high system risk. The Space Shuttle has experienced some of those cases, but has overcome these difficulties through extensive redesign efforts and process enhancements. One example is the design of the hot gas temperature sensor on the Space Shuttle Main Engine (SSME), which resulted in failure of the sensor in flight and led to a redesign of the sensor. The most recent example is the Space Shuttle External Tank (ET) Thermal Protection System (TPS) reliability issues that contributed to the Columbia accident. As a result, extensive redesign and process enhancement activities have been performed over the last two years to minimize the sensitivities and difficulties of the manual TPS application process.

Safie, Fayssal M.↗

Gaining the Competitive Edge: Design for Manufacturing

The successful design of a commercial aircraft which is intended to be in direct competition with existing aircraft requires a market analysis to establish design requirements, the development of a concept to achieve those goals. and the ability to economically manufacture the aircraft. It is often the case that an engineer designs system components with only the perspective of a particular discipline. The relationship of that component to the entire system is often a minor consideration. In an effort to highlight the interaction that is necessary during the design process, the students were organized into design/build teams and required to integrate aspects of market analysis, engineering design, production and economics into their concepts. In order to facilitate this process a hypothetical "Aeroworld" was established. Having been furnished relevant demographic and economic data for "Aeroworld". students were given the task of designing and building an aircraft for a specific market while achieving an economically competitive design. Involvement of the team in the evolution of the design from market definition to technical development to manufacturing allowed the students to identify critical issues in the design process and to encounter many of the conflicting requirements which arise in an aerospace systems design.

Batill, Stephen M.↗

Cassini Information Management System in Distributed Operations Collaboration and Cassini Science Planning

Launched on October 15, 1997, the Cassini-Huygens spacecraft began its ambitious journey to the Saturnian system with a complex suite of 12 scientific instruments, and another 6 instruments aboard the European Space Agencies Huygens Probe. Over the next 6 1/2 years, Cassini would continue its relatively simplistic cruise phase operations, flying past Venus, Earth, and Jupiter. However, following Saturn Orbit Insertion (SOI), Cassini would become involved in a complex series of tasks that required detailed resource management, distributed operations collaboration, and a data base for capturing science objectives. Collectively, these needs were met through a web-based software tool designed to help with the Cassini uplink process and ultimately used to generate more robust sequences for spacecraft operations. In 2001, in conjunction with the Southwest Research Institute (SwRI) and later Venustar Software and Engineering Inc., the Cassini Information Management System (CIMS) was released which enabled the Cassini spacecraft and science planning teams to perform complex information management and team collaboration between scientists and engineers in 17 countries. Originally tailored to help manage the science planning uplink process, CIMS has been actively evolving since its inception to meet the changing and growing needs of the Cassini uplink team and effectively reduce mission risk through a series of resource management validation algorithms. These algorithms have been implemented in the web-based software tool to identify potential sequence conflicts early in the science planning process. CIMS mitigates these sequence conflicts through identification of timing incongruities, pointing inconsistencies, flight rule violations, data volume issues, and by assisting in Deep Space Network (DSN) coverage analysis. In preparation for extended mission operations, CIMS has also evolved further to assist in the planning and coordination of the dual playback redundancy of highvalue data from targets such as Titan and Enceladus. This paper will outline the critical role that CIMS has played for Cassini in the distributed ops paradigm throughout operations. This paper will also examine the evolution that CIMS has undergone in the face of new science discoveries and fluctuating operational needs. And finally, this paper will conclude with theoretical adaptation of CIMS for other projects and the potential savings in cost and risk reduction that could potentially be tapped into by future missions.

Equils, Douglas J.↗

Advanced thrust chamber technology for in-space propulsion system

Two new concepts, the afterburning technique and the spray optimization method for the purpose of upgrading the combustion efficiency and C efficiency, are examined to assess the technical merits and hurdles that need to be resolved. Details of combustion and aerodynamic processes of monomethylhydrazine and nitrogen tetroxides in a toroidal shaped combustion chamber of a variable thrust engine, devised with a wall impingement cooling system and the secondary injection of an oxidizer from the chamber wall for an afterburning, are investigated for the selected secondary injection conditions. With an appropriate injection condition, the combustion efficiency was found to be almost 23 percent higher than that of an engine without afterburning.

Chiu, H. H.↗

The selection of imaging systems for planetary photography from space vehicles.

Discussion of the selection of a type of imaging system for a specific mission which will maximize the return of scientific data while keeping development risk and cost to acceptable limits. A representative example is given which shows that the parameters of the optimizing process range from the scientific objectives through the engineering and programming constraints of the spacecraft and mission, to the characteristics of the types of systems. The selections for all planetary missions flown to date have been imaging systems using image tube cameras. Film cameras and mechanical scan cameras, however, have unique advantages which should find application in planetary exploration.

Smokler, M. I.↗

Overview of the NCC

A multi-disciplinary design/analysis tool for combustion systems is critical for optimizing the low-emission, high-performance combustor design process. Based on discussions between then NASA Lewis Research Center and the jet engine companies, an industry-government team was formed in early 1995 to develop the National Combustion Code (NCC), which is an integrated system of computer codes for the design and analysis of combustion systems. NCC has advanced features that address the need to meet designer's requirements such as "assured accuracy", "fast turnaround", and "acceptable cost". The NCC development team is comprised of Allison Engine Company (Allison), CFD Research Corporation (CFDRC), GE Aircraft Engines (GEAE), NASA Glenn Research Center (LeRC), and Pratt & Whitney (P&W). The "unstructured mesh" capability and "parallel computing" are fundamental features of NCC from its inception. The NCC system is composed of a set of "elements" which includes grid generator, main flow solver, turbulence module, turbulence and chemistry interaction module, chemistry module, spray module, radiation heat transfer module, data visualization module, and a post-processor for evaluating engine performance parameters. Each element may have contributions from several team members. Such a multi-source multi-element system needs to be integrated in a way that facilitates inter-module data communication, flexibility in module selection, and ease of integration. The development of the NCC beta version was essentially completed in June 1998. Technical details of the NCC elements are given in the Reference List. Elements such as the baseline flow solver, turbulence module, and the chemistry module, have been extensively validated; and their parallel performance on large-scale parallel systems has been evaluated and optimized. However the scalar PDF module and the Spray module, as well as their coupling with the baseline flow solver, were developed in a small-scale distributed computing environment. As a result, the validation of the NCC beta version as a whole was quite limited. Current effort has been focused on the validation of the integrated code and the evaluation/optimization of its overall performance on large-scale parallel systems.

Liu, Nan-Suey↗

Object Based Numerical Zooming Between the NPSS Version 1 and a 1-Dimensional Meanline High Pressure Compressor Design Analysis Code

Within NASA's High Performance Computing and Communication (HPCC) program, NASA Glenn Research Center is developing an environment for the analysis/design of propulsion systems for aircraft and space vehicles called the Numerical Propulsion System Simulation (NPSS). The NPSS focuses on the integration of multiple disciplines such as aerodynamics, structures, and heat transfer, along with the concept of numerical zooming between 0- Dimensional to 1-, 2-, and 3-dimensional component engine codes. The vision for NPSS is to create a "numerical test cell" enabling full engine simulations overnight on cost-effective computing platforms. Current "state-of-the-art" engine simulations are 0-dimensional in that there is there is no axial, radial or circumferential resolution within a given component (e.g. a compressor or turbine has no internal station designations). In these 0-dimensional cycle simulations the individual component performance characteristics typically come from a table look-up (map) with adjustments for off-design effects such as variable geometry, Reynolds effects, and clearances. Zooming one or more of the engine components to a higher order, physics-based analysis means a higher order code is executed and the results from this analysis are used to adjust the 0-dimensional component performance characteristics within the system simulation. By drawing on the results from more predictive, physics based higher order analysis codes, "cycle" simulations are refined to closely model and predict the complex physical processes inherent to engines. As part of the overall development of the NPSS, NASA and industry began the process of defining and implementing an object class structure that enables Numerical Zooming between the NPSS Version I (0-dimension) and higher order 1-, 2- and 3-dimensional analysis codes. The NPSS Version I preserves the historical cycle engineering practices but also extends these classical practices into the area of numerical zooming for use within a companies' design system. What follows here is a description of successfully zooming I-dimensional (row-by-row) high pressure compressor results back to a NPSS engine 0-dimension simulation and a discussion of the results illustrated using an advanced data visualization tool. This type of high fidelity system-level analysis, made possible by the zooming capability of the NPSS, will greatly improve the fidelity of the engine system simulation and enable the engine system to be "pre-validated" prior to commitment to engine hardware.

Follen, G.↗

NASA's MERBoard: An Interactive Collaborative Workspace Platform

This chapter describes the ongoing process by which a multidisciplinary group at NASA's Ames Research Center is designing and implementing a large interactive work surface called the MERBoard Collaborative Workspace. A MERBoard system involves several distributed, large, touch-enabled, plasma display systems with custom MERBoard software. A centralized server and database back the system. We are continually tuning MERBoard to support over two hundred scientists and engineers during the surface operations of the Mars Exploration Rover Missions. These scientists and engineers come from various disciplines and are working both in small and large groups over a span of space and time. We describe the multidisciplinary, human-centered process by which this h4ERBoard system is being designed, the usage patterns and social interactions that we have observed, and issues we are currently facing.

Trimble, Jay↗

The Nimbus 5 data catalog. Volume 1: Data orbits 104 through 693, 19 December 1972 - 31 January 1973

Nimbus 5 was successfully launched from the Western Test Range at Vandenburg AFB, California, into a near circular orbit (1089 km x 1102 km) at 07 hr 56 min 00 sec GMT on 11 December 1972. All experiments and subsystems were successfully turned on. Satellite operations from launch (11 December) through orbit 103 (18 December) consisted of engineering evaluation of all spacecraft systems. As a result of that effort, data reception, accountability, and processing were intermittent during that period. Therefore, this catalog reflects documentation from orbit 104 (19 December 1972) through orbit 693 (31 January 1973). The pitch bias history, surface composition mapping radiometer, and infrared temperature profile radiometer are discussed.

Source record↗

The Nimbus 6 data catalog. Volume 6: Data orbits 4339 through 5155

Satellite operations from launch through 14 July (orbit 425) consisted of engineering evaluation of all spacecraft systems. As a result of that effort, data reception, accountability and processing were intermittent during that period. During orbit 4905 (12 June), Nimbus 6 successfully completed one year operations. A summary of the documentation for each Nimbus 6 Data Catalog volume is presented. The pitch of the Nimbus 6 satellite has been made to alternate between +2.0 degrees, +0.6 degrees, and 0.0 degrees since launch. A positive pitch angle of 0.6 degrees moves the nadir-looking position 11.5 kilometers ahead of the subsatellite point. A positive pitch angle of 2.0 degrees moves the nadir-looking position 38.3 kilometers ahead of the subsatellite point. At these pitch angles, a scanner-type instrument no longer scans the earth along a great circle arc through the subpoint, but scans along the small circle formed by the intersection of the scan plane with the earth. Since the plane of the small circle is tilted with respect to the nominal scan plane, points on the arc are displaced farther from the great circle as the scan angle increases. As noted above, a pitch angle of 0.6 degrees causes a displacement of 11.5 kilometers at nadir, but when the scanner turns 45 degrees away from nadir the displacement increases slightly to 12.8 kilometers. Similarly, for a 2.0 degree pitch the displacement is 38.3 kilometers at nadir and increases to 42.6 kilometers at a 45 degree scan angle. Thus, although the instrument records in lines normal to the orbit plane (in the absence of yaw) the perpendicular displacement from the perfect-attitude scan line is not uniform across the scan line.

Source record↗

The Nimbus 6 data catalog, volume 12: Data orbits 9227 through 10043

Nimbus 6 was successfully launched from the Western Test Range, Vandenberg Air Force Base, California at 08 hr. 12 min. 00 sec. GMT on 12 June 1975. The orbit was nearly circular at 1093 x 1105 km. Satellite operations from launch through 14 July (orbit 425) consisted of engineering evaluation of all spacecraft systems. As a result of that effort, data reception, accountability and processing were intermittent during that period. This volume reflects the operational changes that occurred to each individual subsystem on a bi-monthly basis. Also this volume incorporates significant findings and various subsystem summaries as detailed by the respective experimenter. During orbit 9793 (12 June 1977) Nimbus 6 successfully completed two years of operations.

Source record↗

Power processing and control requirements of dispersed solar thermal electric generation systems

Power Processing and Control requirements of Dispersed Receiver Solar Thermal Electric Generation Systems are presented. Kinematic Stirling Engines, Brayton Engines and Rankine Engines are considered as prime movers. Various types of generators are considered for ac and dc link generations. It is found that ac-ac Power Conversion is not suitable for implementation at this time. It is also found that ac-dc-ac Power Conversion with a large central inverter is more efficient than ac-dc-ac Power Conversion using small dispersed inverters. Ac-link solar thermal electric plants face potential stability and synchronization problems. Research and development efforts are needed in improving component performance characteristics and generation efficiency to make Solar Thermal Electric Generation economically attractive.

Das, R. L.↗