Search NASA⌕ Search

SEARCH · Search NASA

Results for “Process Engineering”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS1940

Resonance vibrations in intake and exhaust pipes of in-line engines III : the inlet process of a four-stroke-cycle engine

Using a previously developed method, the boundary process of four-stroke-cycle engines are set up. The results deviate considerably from those obtained under the assumption that the velocity fluctuation is proportional to the cylinder piston motion. The deviation is less at the position of resonance frequencies. By the method developed, the effect of the resonance vibrations on the volumetric efficiency can be demonstrated.

Lutz, O↗
NASA NTRS1995

NASA Systems Engineering Handbook

This handbook brings the fundamental concepts and techniques of systems engineering to NASA personnel in a way that recognizes the nature of NASA systems and environment. It is intended to accompany formal NASA training courses on systems engineering and project management when appropriate, and is designed to be a top-level overview. The concepts were drawn from NASA field center handbooks, NMI's/NHB's, the work of the NASA-wide Systems Engineering Working Group and the Systems Engineering Process Improvement Task team, several non-NASA textbooks and guides, and material from independent systems engineering courses taught to NASA personnel. Five core chapters cover systems engineering fundamentals, the NASA Project Cycle, management issues in systems engineering, systems analysis and modeling, and specialty engineering integration. It is not intended as a directive. Superseded by: NASA/SP-2007-6105 Rev 1 (20080008301).

Shishko, Robert↗
NASA NTRS2012

The Montana ALE (Autonomous Lunar Excavator) Systems Engineering Report

On May 2 1-26, 20 12, the third annual NASA Lunabotics Mining Competition will be held at the Kennedy Space Center in Florida. This event brings together student teams from universities around the world to compete in an engineering challenge. Each team must design, build and operate a robotic excavator that can collect artificial lunar soil and deposit it at a target location. Montana State University, Bozeman, is one of the institutions selected to field a team this year. This paper will summarize the goals of MSU's lunar excavator project, known as the Autonomous Lunar Explorer (ALE), along with the engineering process that the MSU team is using to fulfill these goals, according to NASA's systems engineering guidelines.

Lars Osborne↗
NASA NTRS2016

EDEN: A Novel Approach to Plant Growth in Space

The USU XHAB Eden Team has enjoyed the opportunity to participate in NASA’s X­HAB Challenge. Our project involved constructing a prototype to further investigate the complexities of growing plants in microgravity environments. Attached is the team’s report which covers the research and design of our prototype. Included is a summary of our design, drawings and schematics with an as built status, engineering process documents, and all other documentation necessary to satisfy the requirements of Utah State University’s Engineering Design Course (MAE 4810).

Timothy Taylor↗
NASA NTRS2000

Session on High Speed Civil Transport Design Capability Using MDO and High Performance Computing

Since the inception of CAS in 1992, NASA Langley has been conducting research into applying multidisciplinary optimization (MDO) and high performance computing toward reducing aircraft design cycle time. The focus of this research has been the development of a series of computational frameworks and associated applications that increased in capability, complexity, and performance over time. The culmination of this effort is an automated high-fidelity analysis capability for a high speed civil transport (HSCT) vehicle installed on a network of heterogeneous computers with a computational framework built using Common Object Request Broker Architecture (CORBA) and Java. The main focus of the research in the early years was the development of the Framework for Interdisciplinary Design Optimization (FIDO) and associated HSCT applications. While the FIDO effort was eventually halted, work continued on HSCT applications of ever increasing complexity. The current application, HSCT4.0, employs high fidelity CFD and FEM analysis codes. For each analysis cycle, the vehicle geometry and computational grids are updated using new values for design variables. Processes for aeroelastic trim, loads convergence, displacement transfer, stress and buckling, and performance have been developed. In all, a total of 70 processes are integrated in the analysis framework. Many of the key processes include automatic differentiation capabilities to provide sensitivity information that can be used in optimization. A software engineering process was developed to manage this large project. Defining the interactions among 70 processes turned out to be an enormous, but essential, task. A formal requirements document was prepared that defined data flow among processes and subprocesses. A design document was then developed that translated the requirements into actual software design. A validation program was defined and implemented to ensure that codes integrated into the framework produced the same results as their standalone counterparts. Finally, a Commercial Off the Shelf (COTS) configuration management system was used to organize the software development. A computational environment, CJOPT, based on the Common Object Request Broker Architecture, CORBA, and the Java programming language has been developed as a framework for multidisciplinary analysis and Optimization. The environment exploits the parallelisms inherent in the application and distributes the constituent disciplines on machines best suited to their needs. In CJOpt, a discipline code is "wrapped" as an object. An interface to the object identifies the functionality (services) provided by the discipline, defined in Interface Definition Language (IDL) and implemented using Java. The results of using the HSCT4.0 capability are described. A summary of lessons learned is also presented. The use of some of the processes, codes, and techniques by industry are highlighted. The application of the methodology developed in this research to other aircraft are described. Finally, we show how the experience gained is being applied to entirely new vehicles, such as the Reusable Space Transportation System. Additional information is contained in the original.

Rehder, Joe↗
NASA NTRS2011

Space Transportation System Liftoff Debris Mitigation Process Overview

Liftoff debris is a top risk to the Space Shuttle Vehicle. To manage the Liftoff debris risk, the Space Shuttle Program created a team with in the Propulsion Systems Engineering & Integration Office. The Shutt le Liftoff Debris Team harnesses the Systems Engineering process to i dentify, assess, mitigate, and communicate the Liftoff debris risk. T he Liftoff Debris Team leverages off the technical knowledge and expe rtise of engineering groups across multiple NASA centers to integrate total system solutions. These solutions connect the hardware and ana lyses to identify and characterize debris sources and zones contribut ing to the Liftoff debris risk. The solutions incorporate analyses sp anning: the definition and modeling of natural and induced environmen ts; material characterizations; statistical trending analyses, imager y based trajectory analyses; debris transport analyses, and risk asse ssments. The verification and validation of these analyses are bound by conservative assumptions and anchored by testing and flight data. The Liftoff debris risk mitigation is managed through vigilant collab orative work between the Liftoff Debris Team and Launch Pad Operation s personnel and through the management of requirements, interfaces, r isk documentation, configurations, and technical data. Furthermore, o n day of launch, decision analysis is used to apply the wealth of ana lyses to case specific identified risks. This presentation describes how the Liftoff Debris Team applies Systems Engineering in their proce sses to mitigate risk and improve the safety of the Space Shuttle Veh icle.

Mitchell, Michael↗
NASA NTRSDate not supplied

Human Systems Integration Relationships Between Deep Space and Deepwater Exploration Challenges

NASA pursuit of human missions Beyond Earth Orbit (BEO) to the moon and eventually Mars will pose many new challenges. These missions are characterized by increased risks to human performance due to stress, fatigue, radiation exposure, and isolation. Fundamental changes in spaceflight operations will be required as well. A very critical part of future missions will be assisting the crew with problem-solving and contingency resolution using next-generation smart spacecraft systems. Human Systems Integration (HSI) must be included as part of the systems engineering process. Gateway1 will serve as part of the proving ground for maturing technology such as autonomous systems and space operations procedures to help meet moon mission goals and prepare humans for missions to Mars. For deep space missions, risk factors affecting humans such as mission duration, distance, and physiological/psychological effects, must be considered. A human is not a simple component but rather a system in a systems-of-systems application-a system influenced by cognitive and biological factors that are difficult to model/analyze. System complexity will demand an integrated approach that requires multiple viewpoints, including the understanding of the astronauts' capabilities and limitations to enhance safety, performance, and satisfaction on the interaction between all system users in a variety of environments to achieve acceptable mission goals and performance. HSI will play a vital role in the development of these future missions. This paper provides a discussion of HSI used at NASA and the critical role human factors engineering will play in the HSI process for future missions along with the challenges. Industries such as oil and gas (O&G) could benefit from the content of this paper to help improve the safety and operations of deepwater/oil and gas exploration activities. NASA engineering and human systems subject-matter expert personnel reviewed challenges reported in space-related environments for long space duration missions and identified similarities with the challenges encountered in deepwater exploration. The researchers noted the space industry's current solutions and proposed a system development view to solve future deepwater exploration challenges using HSI principles. This paper discusses the results of the review.

George Salazar↗
NASA NTRS1994

Evaluation of NASA's end-to-end data systems using DSDS+

The Data Systems Dynamic Simulator (DSDS+) is a software tool being developed by the authors to evaluate candidate architectures for NASA's end-to-end data systems. Via modeling and simulation, we are able to quickly predict the performance characteristics of each architecture, to evaluate 'what-if' scenarios, and to perform sensitivity analyses. As such, we are using modeling and simulation to help NASA select the optimal system configuration, and to quantify the performance characteristics of this system prior to its delivery. This paper is divided into the following six sections: (1) The role of modeling and simulation in the systems engineering process. In this section, we briefly describe the different types of results obtained by modeling each phase of the systems engineering life cycle, from concept definition through operations and maintenance; (2) Recent applications of DSDS+. In this section, we describe ongoing applications of DSDS+ in support of the Earth Observing System (EOS), and we present some of the simulation results generated of candidate system designs. So far, we have modeled individual EOS subsystems (e.g. the Solid State Recorders used onboard the spacecraft), and we have also developed an integrated model of the EOS end-to-end data processing and data communications systems (from the payloads onboard to the principle investigator facilities on the ground); (3) Overview of DSDS+. In this section we define what a discrete-event model is, and how it works. The discussion is presented relative to the DSDS+ simulation tool that we have developed, including it's run-time optimization algorithms that enables DSDS+ to execute substantially faster than comparable discrete-event simulation tools; (4) Summary. In this section, we summarize our findings and 'lessons learned' during the development and application of DSDS+ to model NASA's data systems; (5) Further Information; and (6) Acknowledgements.

Rouff, Christopher↗
NASA NTRS1988

DFT algorithms for bit-serial GaAs array processor architectures

Systems and Processes Engineering Corporation (SPEC) has developed an innovative array processor architecture for computing Fourier transforms and other commonly used signal processing algorithms. This architecture is designed to extract the highest possible array performance from state-of-the-art GaAs technology. SPEC's architectural design includes a high performance RISC processor implemented in GaAs, along with a Floating Point Coprocessor and a unique Array Communications Coprocessor, also implemented in GaAs technology. Together, these data processors represent the latest in technology, both from an architectural and implementation viewpoint. SPEC has examined numerous algorithms and parallel processing architectures to determine the optimum array processor architecture. SPEC has developed an array processor architecture with integral communications ability to provide maximum node connectivity. The Array Communications Coprocessor embeds communications operations directly in the core of the processor architecture. A Floating Point Coprocessor architecture has been defined that utilizes Bit-Serial arithmetic units, operating at very high frequency, to perform floating point operations. These Bit-Serial devices reduce the device integration level and complexity to a level compatible with state-of-the-art GaAs device technology.

Mcmillan, Gary B.↗
NASA NTRSDate not supplied

Integrated Systems and Operational Autonomy for Gateway

The Lunar Gateway space station will be operated with less human oversight and control than any human spacecraft thus far. An autonomous software control architecture has been developed to allow the spacecraft to maintain safe operations of the vehicle during times of no human involvement. The development of these autonomous control functionalities has been both technical and process driven. Given that the Gateway will be built modularly with contributions from all over the world, the systems engineering processes had to be shaped to fit with the contractual and political realities of the construction of the international lunar habitat. This paper will describe these challenges and contributions to the development of human spacecraft for sustainable deep space missions.

J M Badger↗
NASA NTRS2007

Comprehensive Shuttle Foam Debris Reduction Strategies

The Columbia Accident Investigation Board (CAIB) was clear in its assessment of the loss of the Space Shuttle Columbia on February 3, 2003. Foam liberated from the External Tank (ET) impacting the brittle wing leading edge (WLE) of the orbiter causing the vehicle to disintegrate upon re-entry. Naturally, the CAB pointed out numerous issues affecting this exact outcome in hopes of correcting systems of systems failures any one of which might have altered the outcome. However, Discovery s recent return to flight (RTF) illustrates the primacy of erosion of foam and the risk of future undesirable outcomes. It is obvious that the original RTF focused approach to this problem was not equal to a comprehensive foam debris reduction activity consistent with the high national value of the Space Shuttle assets. The root cause is really very simple when looking at the spray-on foam insulation for the entire ET as part of the structure (e.g., actual stresses > materials allowable) rather than as some sort of sizehime limited ablator. This step is paramount to accepting the CAB recommendation of eliminating debris or in meeting any level of requirements due to the fundamental processes ensuring structural materials maintain their integrity. Significant effort has been expended to identify root cause of the foam debris In-Flight Anomaly (FA) of STS-114. Absent verifiable location specific data pre-launch (T-0) and in-flight, only a most probable cause can be identified. Indeed, the literature researched corroborates NASNTM-2004-2 13238 disturbing description of ill defined materials characterization, variable supplier constituents and foam processing irregularities. Also, foam is sensitive to age and the exposed environment making baseline comparisons difficult without event driven data. Conventional engineering processes account for such naturally occurring variability by always maintaining positive margins. Success in a negative margin range is not consistently achieved. Looking at the ET S spray-on foam insulation as part of the structural system (e.g., glass half full mentality) will create an environment where ET debris levels as low as reasonably achievable (ALARA) can be realized. ALARA is a NASA requirements philosophy deployed for the complex, mission altering radiation exposure requirements for life safety of astronauts. In the Shuttle s case, reasonableness is established by exhaustive engineering rigor, allowable debris size/quantity, technology maturity and programmatic constraints. A more robust urethane foam thermal protection system (TPS) will enhance the hctionality of the new Ares I Crew Launch Vehicle (CLV) Upper Stage. This paper will outline the strategy for a comprehensive effort to reduce ET foam debris and outline steps leading to an improved foam TPS. The NASA must remain committed to such an approach no matter what becomes of the next flight s actual debris field lest we fall back into a false sense of security. This commitment along with full implementation of all the other CAB recommendations such as orbiter hardening will significantly improve the Shuttle system, the engineering workforce, future capabilities & alternate policy offramps, national human resource protection, high value national asset protection and increase the level of service to the overall NASA mission.

Semmes, Edmund B.↗
NASA NTRS2012

On Using SysML, DoDAF 2.0 and UPDM to Model the Architecture for the NOAA's Joint Polar Satellite System (JPSS) Ground System (GS)

The JPSS Ground System is a lIexible system of systems responsible for telemetry, tracking & command (TT &C), data acquisition, routing and data processing services for a varied lIeet of satellites to support weather prediction, modeling and climate modeling. To assist in this engineering effort, architecture modeling tools are being employed to translate the former NPOESS baseline to the new JPSS baseline, The paper will focus on the methodology for the system engineering process and the use of these architecture modeling tools within that process, The Department of Defense Architecture Framework version 2,0 (DoDAF 2.0) viewpoints and views that are being used to describe the JPSS GS architecture are discussed. The Unified Profile for DoOAF and MODAF (UPDM) and Systems Modeling Language (SysML), as ' provided by extensions to the MagicDraw UML modeling tool, are used to develop the diagrams and tables that make up the architecture model. The model development process and structure are discussed, examples are shown, and details of handling the complexities of a large System of Systems (SoS), such as the JPSS GS, with an equally complex modeling tool, are described

Hayden, Jeffrey L.↗
NASA NTRSDate not supplied

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗
NASA NTRSDate not supplied

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗
NASA NTRS2016

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

This document is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

Steven R Hirshorn↗
NASA NTRSDate not supplied

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗
NASA NTRS1991

Software Engineering Laboratory (SEL) cleanroom process model

The Software Engineering Laboratory (SEL) cleanroom process model is described. The term 'cleanroom' originates in the integrated circuit (IC) production process, where IC's are assembled in dust free 'clean rooms' to prevent the destructive effects of dust. When applying the clean room methodology to the development of software systems, the primary focus is on software defect prevention rather than defect removal. The model is based on data and analysis from previous cleanroom efforts within the SEL and is tailored to serve as a guideline in applying the methodology to future production software efforts. The phases that are part of the process model life cycle from the delivery of requirements to the start of acceptance testing are described. For each defined phase, a set of specific activities is discussed, and the appropriate data flow is described. Pertinent managerial issues, key similarities and differences between the SEL's cleanroom process model and the standard development approach used on SEL projects, and significant lessons learned from prior cleanroom projects are presented. It is intended that the process model described here will be further tailored as additional SEL cleanroom projects are analyzed.

Green, Scott↗