Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 199 records · Page 11

Let's Roll! Rolling Out or Deploying SEPG Assets

The topics covered in this slide presentation are: the general approach to software quality improvement (SQI) at Jet Propulsion Institute, the SQI deployment process, and lessons learned in regard to SQI. The Software Engineering Process Group (SEPG) is the group charged with SQI. The initial focus of the Software Quality Improvement (SQI) Project is on mission-critical software for flight projects, their spacecraft and instrument systems, and their ground systems.

process improvements↗

Lessons Learned in Engineering

This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations.

Blair, J. C.↗

Lessons Learned in Engineering

This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations. The supplemental CD contains accompanying PowerPoint presentations.

Blair, James C.↗

Design Thinking, Lean Startup, and High-Technology Marketing for Human-Centered Systems Engineering

The use of design thinking, lean startup, and high-technology marketing in systems engineering are presented as a case study. All were used and evaluated for their potential to improve systems engineering processes and design, address the challenges of culture change, increase the adoption rate of new technology, and engage with potential users and sponsors more effectively. Multiple examples of training and use on a model-based systems engineering initiative at a large government agency showcase how these approaches were tailored and used successfully for significant benefits such as enhanced collaboration and better problem definition and design solutions. Challenges remain for use by quiet thinkers and with virtual teams. These new ways of thinking are well aligned with creating and using new technologies and are suitable for situations involving innovation, uncertainty, and change within organizations. This case study intends to familiarize systems engineers with the application of these human-centered approaches, to interest systems engineers in incorporating these approaches into their work processes ,and to inspire the systems engineering research community to investigate further.

Karen J. Weiland↗

Multi-process tooling for discontinuous carbon and hybrid glass fiber thermoplastics

Expensive tooling often constraints the use of composites in the design and development of automotive parts. While there is significant confidence and knowledge in sheet and bulk metals, composite processes are less understood in mass production environment. The processes used to produce composites and resulting properties are influenced by fiber length attrition, resin to fiber ratio, process waste etc. Tool designs are determined very early in the engineering process. It is cost prohibitive to build additional tools, in the event it becomes obvious a better processing method and material would be beneficial, the original decision is not easily changed. In the present work we recognize the bottleneck of tooling costs and provide an approach of multi-process tooling. The innovation of this work is the design and demonstration of a single tool for different processes namely injection, injection-compression and extrusion-compression. The materials used in this study were long and short fiber thermoplastics (LFTs and SFTs). The resulting structure-property relationships have been reported for the materials and processing methods with a battery tray (BT) tool.

Vaidya, Uday↗

Use of graphics in the design office at the Military Aircraft Division of the British Aircraft Corporation

The CAD/CAM interactive computer graphics system was described; uses to which it has been put were shown, and current developments of the system were outlined. The system supports batch, time sharing, and fully interactive graphic processing. Engineers using the system may switch between these methods of data processing and problem solving to make the best use of the available resources. It is concluded that the introduction of on-line computing in the form of teletypes, storage tubes, and fully interactive graphics has resulted in large increases in productivity and reduced timescales in the geometric computing, numerical lofting and part programming areas, together with a greater utilization of the system in the technical departments.

Coles, W. A.↗

The MSFC Systems Engineering Guide: An Overview and Plan

As systems and subsystems requirements become more complex in the pursuit of the exploration of space, advanced technology will demand and require an integrated approach to the design and development of safe and successful space vehicles and there products. System engineers play a vital and key role in transforming mission needs into vehicle requirements that can be verified and validated. This will result in a safe and cost effective design that will satisfy the mission schedule. A key to successful vehicle design within systems engineering is communication. Communication, through a systems engineering infrastructure, will not only ensure that customers and stakeholders are satisfied but will also assist in identifying vehicle requirements; i.e. identification, integration and management. This vehicle design will produce a system that is verifiable, traceable, and effectively satisfies cost, schedule, performance, and risk throughout the life-cycle of the product. A communication infrastructure will bring about the integration of different engineering disciplines within vehicle design. A system utilizing these aspects will enhance system engineering performance and improve upon required activities such as Development of Requirements, Requirements Management, Functional Analysis, Test, Synthesis, Trade Studies, Documentation, and Lessons Learned to produce a successful final product. This paper will describe the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that will describe the system engineering processes that are used by MSFC in the development of complex systems such as the Ares launch vehicle. It is the intent of this website to be a "One Stop Shop" for our systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

Shelby, Jerry A.↗

FENIX: Towards a Fully Integrated Multiphysics Framework for Plasma Facing Component Modeling

Computational tools have a crucial role to play in accelerating the deployment of fusion as a clean, reliable, abundant, and sustainable energy source. Multiphysics, high-fidelity simulation capabilities can help model, study, and predict intricate interactions between materials performance, plasma exposure, neutron irradiation, and engineering processes. As such, they can assist in the resolution of scientific and engineering challenges underpinning design, construction, and commission of fusion power plants. To address these needs, ongoing efforts are leveraging the Multiphysics Object-Oriented Simulation Environment (MOOSE) framework and delivering new computational tools for the fusion community. These tools inherit crucial attributes from MOOSE. They are open-source, modular, integrated with nuclear industry-standard software quality assurance processes, and enable multiphysics, multi-fidelity, fully integrated, zero- to three-dimensional, and massively parallel simulations. After a short overview of these capabilities, we will present the development of Fusion ENergy Integrated multiphys-X (FENIX), a MOOSE-based application designed to enable plasma facing component design and performance evaluation. Throughout their lifetime, plasma facing components are exposed to extreme thermal loads, repeated thermal shocks, and irradiation by plasma ions, neutral particles, and high-energy neutrons. Consequently, designing a plasma facing component with acceptable lifetime degradation is extremely challenging. FENIX aims to model the multiphysics environment in which plasma facing components evolve to accelerate their design studies. To that end, FENIX couples existing MOOSE capabilities such as heat transfer, thermomechanics, and thermal hydraulics, with tritium transport via the MOOSE-based Tritium Migration Analysis Program, Version 8 (TMAP8), with neutronics via the MOOSE-based high-fidelity neutron-photon transport and fluid dynamics code Cardinal, and finally with Particle-in-Cell plasma simulation capabilities being developed in this project. In this study, we present the current FENIX capabilities and preliminary results of its application to model the Tritium Plasma Experiment set up at Idaho National Laboratory.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

The JSC Engineering Directorate Product Peer Review Process

The JSC Engineering Directorate has developed a Product Peer Review process in support of NASA policies for project management and systems engineering. The process complies with the requirements of NPR 7120.5, NPR 7123.1 and NPR 7150.2 and follows the guidance in NASA/SP-2007-6105. This presentation will give an overview of the process followed by a brief demonstration of an actual peer review, with audience participation.

Jenks, Kenneth C.↗

The MSFC Systems Engineering Guide: An Overview and Plan

This paper describes the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that describes the system engineering processes used by MSFC in the development of ongoing complex space systems such as the Ares launch vehicle and forthcoming ones as well. It is the intent of this website to be a "One Stop Shop' for MSFC systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of relevant systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

Shelby, Jerry↗

An Altair Overview: Designing a Lunar Lander for 21st Century Human Space Exploration

Altair, the lunar lander element of NASA's Constellation program, was conducted in a different design environment than many other NASA projects of similar scope. Because of this relatively unique approach, there are a number of significant success stories that should be considered during the development of any future lunar landers or human spacecraft. This paper is divided into two separate themes; the first is the approach used during the conceptual design studies, including the systematic analysis cycles and the decision making process associated with each: and the second is a summary of the resulting lessons learned that were compiled after looking back at the lifetime of the Project. Altair was terminated before entering Phase B of its design, and was often criticized for being a very heavy and very large vehicle. While there was specific rationale for all of the decisions that led up to that configuration, future design cycles were specifically planned to re-address the mass challenge. Had the project continued, the deliberate, stepwise design process would have converged on an optimized lander design that balanced mass, risk, cost and capabilities. Some of the specific items that will be addressed in this paper include project development strategy, organizational approach and team dynamics, risk-informed design process, mission architecture constraints, mission key driving requirements, model-based systems engineering process, configuration studies, contingency considerations, subsystem overviews and key trade studies. The paper will conclude with a summary of the lessons identified during the Altair project and make suggestions for application to future studies.

Brown, Kendall K.↗

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗

Introduction to the Navigation Team: Johnson Space Center EG6 Internship

The EG6 navigation team at NASA Johnson Space Center, like any team of engineers, interacts with the engineering process from beginning to end; from exploring solutions to a problem, to prototyping and studying the implementations, all the way to polishing and verifying a final flight-ready design. This summer, I was privileged enough to gain exposure to each of these processes, while also getting to truly experience working within a team of engineers. My summer can be broken up into three projects: i) Initial study and prototyping: investigating a manual navigation method that can be utilized onboard Orion in the event of catastrophic failure of navigation systems; ii) Finalizing and verifying code: altering a software routine to improve its robustness and reliability, as well as designing unit tests to verify its performance; and iii) Development of testing equipment: assisting in developing and integrating of a high-fidelity testbed to verify the performance of software and hardware.

Gualdoni, Matthew↗

NASA Systems Engineering Research Consortium: Defining the Path to Elegance in Systems

The NASA Systems Engineering Research Consortium was formed at the end of 2010 to study the approaches to producing elegant systems on a consistent basis. This has been a transformative study looking at the engineering and organizational basis of systems engineering. The consortium has engaged in a variety of research topics to determine the path to elegant systems. In the second year of the consortium, a systems engineering framework emerged which structured the approach to systems engineering and guided our research. This led in the third year to set of systems engineering postulates that the consortium is continuing to refine. The consortium has conducted several research projects that have contributed significantly to the understanding of systems engineering. The consortium has surveyed the application of the NASA 17 systems engineering processes, explored the physics and statistics of systems integration, and considered organizational aspects of systems engineering discipline integration. The systems integration methods have included system exergy analysis, Akaike Information Criteria (AIC), State Variable Analysis, Multidisciplinary Coupling Analysis (MCA), Multidisciplinary Design Optimization (MDO), System Cost Modelling, System Robustness, and Value Modelling. Organizational studies have included the variability of processes in change evaluations, margin management within the organization, information theory of board structures, social categorization of unintended consequences, and initial looks at applying cognitive science to systems engineering. Consortium members have also studied the bidirectional influence of policy and law with systems engineering.

Watson, Michael D.↗

NASA Systems Engineering Research Consortium: Defining the Path to Elegance in Systems

The NASA Systems Engineering Research Consortium was formed at the end of 2010 to study the approaches to producing elegant systems on a consistent basis. This has been a transformative study looking at the engineering and organizational basis of systems engineering. The consortium has engaged in a variety of research topics to determine the path to elegant systems. In the second year of the consortium, a systems engineering framework emerged which structured the approach to systems engineering and guided our research. This led in the third year to set of systems engineering postulates that the consortium is continuing to refine. The consortium has conducted several research projects that have contributed significantly to the understanding of systems engineering. The consortium has surveyed the application of the NASA 17 systems engineering processes, explored the physics and statistics of systems integration, and considered organizational aspects of systems engineering discipline integration. The systems integration methods have included system energy analysis, Akaike Information Criteria (AIC), State Variable Analysis, Multidisciplinary Coupling Analysis (MCA), Multidisciplinary Design Optimization (MDO), System Cost Modeling, System Robustness, and Value Modeling. Organizational studies have included the variability of processes in change evaluations, margin management within the organization, information theory of board structures, social categorization of unintended consequences, and initial looks at applying cognitive science to systems engineering. Consortium members have also studied the bidirectional influence of policy and law with systems engineering.

Watson, Michael D.↗

Development of a Human Systems Integration Plan

NASA defines Human Systems Integration (HSI) as part of the overall systems engineering and acquisition strategy for space systems. The HSI Plan defines how HSI activities will be implemented across the lifecycle of the mission, as required by NPR 7123.1C, NASA Systems Engineering Processes and Requirements, and NPR 8705.2C Human-Rating Requirements for Space Systems. The goal of this presentation is to share with government and industry how an HSI Plan can be implemented. The presentation will cover HSI implementation for flight systems, vehicle processing, and interfaces. These are divided into six NASA HSI Domains: human factors engineering, operations resources, safety, training, maintainability and supportability, habitability and environment. HSI activities go across the mission’s lifecycle from pre-formulation and acquisition through design, development, operations, maintenance, and decommissioning. The HSI Plan includes a description of the HSI activities and products that are essential for human rating, operability, maintainability, supportability, and affordability of the mission systems. It also describes the role of the HSI Team required as part of the Human Rating process. The HSI Plan utilizes the operational expertise within NASA to ensure designs and testing are successful, leading to acceptable human spaceflight vehicles.

Jackelynne Silva-Martinez↗

Cyber-Informed Engineering Validation Methods and Guidance

Validation is an important step in any systems engineering process to ensure the correct system was made to fulfill stakeholders’ needs, goals, and expectations. In the context of Cyber-Informed Engineering (CIE), validation ensures cyber impact is reduced through implemented design choices and CIE requirements. This document details a process in validating CIE-based design choices relative to their effectiveness at mitigating high consequence events. The document includes a case study to illustrate the CIE validation process. The case study explores the implementation of CIE validation within the engineering lifecycle of a chemical mixing plant.

42 ENGINEERING↗