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 1,261 records · Page 70
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Analysis of Possible Explosions at Kennedy Space Center Due to Spontaneous Ignition of Hypergolic Propellants

NASA's Constellation Program plan currently calls for the replacement of the Space Shuttle with the ARES I & V spacecraft and booster vehicles to send astronauts to the moon and beyond. Part of the ARES spacecraft is the Orion Crew Exploration Vehicle (CEV), which includes the Crew Module (CM) and Service Module (SM). The Orion CM's main propulsion system and supplies are provided by the SM. The SM is to be processed off line and moved to the Vehicle Assembly Building (V AB) for stacking to the first stage booster motors prior to ARES move to the launch pad. The new Constellation Program philosophy to process in this manner has created a major task for the KSC infrastructure in that conventional QD calculations are no longer viable because of the location of surrounding facilities near the VAB and the Multi Purpose Processing Facility (MPPF), where the SM will be serviced with nearly 18,000 pounds of hypergolic propellants. The Multi-Payload Processing Facility (MPPF) complex, constructed by NASA in 1994, is located just off E Avenue south of the Operations and Checkout (O&C) building in the Kennedy Space Center industrial area. The MPPF includes a high bay and a low bay. The MPPF high bay is 40.2 m (132 ft) long x 18.9 m (60 ft) wide with a ceiling height of 18.9 m (62 ft). The low bay is a 10.4 m (34 ft) long x 10.4 m (34 ft) wide processing area and has a ceiling height of6.1 m (20 ft). The MPPF is currently used to process non-hazardous payloads. Engineering Analysis Inc. (EAI), under contract with ASRC Aerospace, Inc. in conjunction with the Explosive Safety Office, NASA, Kennedy Space Center (KSC), has carried out an analysis of the effects of explosions at KSC in or near various facilities produced by the spontaneous ignition ofhypergolic fuel stored in the CEV SM. The facilities considered included (1) Vehicle Assembly Building (VAB) (2) Multi-Payload Processing Facility (MPPF) (3) Canister Rotation Facility (CRF) Subsequent discussion deals with the MPPF analysis. Figure 1 provides a view of the MPPF from the northwest. An interior view ofthe facility is shown in Figure 2. The study was concerned with both blast hazards and hazardous fragments which exceed existing safety standards, as described in Section 2.0. The analysis included both blast and fragmentation effects and was divided into three parts as follows: (1) blast (2) primary fragmentation (3) secondary fragmentation Blast effects are summarized in Section 3.0, primary fragmentation in Section 4.0, and secondary fragmentation (internal and external) in Section 5.0. Conclusions are provided in Section 6.0, while references cited are included in Section 7.0. A more detailed description of the entire study is available in a separate document.

Brown, Stephen↗
NASA NTRS2010

The ICARE Method

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

Henke, Luke↗
NASA NTRS2022

New Rover Conops with High-Performance Onboard Computing: Give Up Raw Data to Reduce Ops Cost and Do More Science

A major portion of time during the tactical operation of Mars rovers is spent for selecting, prioritizing, and coordinating sciences and engineering activities such that they fit within resource constraints, including the downlink data volume, energy, and time. In particular, the downlink data volume constraint is getting particularly tighter in recent missions because modern instruments produce increasingly high data volume while the communication bandwidth is essentially bounded by the law of physics. Tactical operation would be substantially simplified, hence the operation cost could be reduced, if the data volume constraint is relaxed or even removed. In this abstract, we propose a new operation paradigm for achieving this goal. The key observation is that, both in science and engineering applications, the bit size of raw data is typically much greater than the volume of processed information that is needed for scientific or engineering analysis. For example, a full-resolution image from Mastcam-Z, the main science camera on Perseverance, is about 700 kB in volume and we downlinked 29,685 images up to Sol 243, totaling ~20 GB of data. But of course, scientists do not use every pixel of these images; what they really look for in the images are geological features, typically represented by specific geometric configurations or textures. An end product after processing hundreds of Mascam-Z images could be a single geological map summarizing the spatial distribution of the features. For another example, a 100-meter drive of Perseverance produces 7-12 MB of drive telemetry, which records every detail of the rover's motion at 8 Hz, including position, attitude, steering angles, encoder readings, motor currents and many other information. But what the ground engineers eventually pay attention to is the signs of anomaly, such as excessive motor currents or high slip; if a drive is nominal, the vast majority of this data is unused. What if, then, we process the raw data onboard and only downlink the processed data that is relevant to scientific or engineering analyses, such as a list of detected science features (with cropped images) or a list of potential signs of anomaly while driving? A major roadblock for such onboard, high-level information processing has been the onboard computational resource. RAD750, the main onboard computer of Perseverance, is obviously not sufficient for performing complex image or signal processing such as object detection, semantic segmentation, or anomaly detection. Interestingly, RAD750 is not the best processor that Perseverance has; Qualcomm's Snapdragon 801, a modern mobile processor, is on her Heli Base Station, a device for communicating with Mars Helicopter Ingenuity; also, Intel's Atom E3845 processors are on engineering cameras. In the reminder of this paper, we will introduce two particular uses cases of these high-performance co-processors (meaning auxiliary CPU, GPU, or other types of processors that are separate from the main processor that runs the main flight software) for lowering operation cost and accommodating more science activities for a given communication constraint.

Didier, A.↗
NASA NTRS2011

Systems Engineering Simulator (SES) Simulator Planning Guide

The simulation process, milestones and inputs are unknowns to first-time users of the SES. The Simulator Planning Guide aids in establishing expectations for both NASA and non-NASA facility customers. The potential audience for this guide includes both internal and commercial spaceflight hardware/software developers. It is intended to assist their engineering personnel in simulation planning and execution. Material covered includes a roadmap of the simulation process, roles and responsibilities of facility and user, major milestones, facility capabilities, and inputs required by the facility. Samples of deliverables, facility interfaces, and inputs necessary to define scope, cost, and schedule are included as an appendix to the guide.

McFarlane, Michael↗
NASA NTRS1991

Development of life prediction capabilities for liquid propellant rocket engines. Post-fire diagnostic system for the SSME system architecture study

This system architecture task (1) analyzed the current process used to make an assessment of engine and component health after each test or flight firing of an SSME, (2) developed an approach and a specific set of objectives and requirements for automated diagnostics during post fire health assessment, and (3) listed and described the software applications required to implement this system. The diagnostic system described is a distributed system with a database management system to store diagnostic information and test data, a CAE package for visual data analysis and preparation of plots of hot-fire data, a set of procedural applications for routine anomaly detection, and an expert system for the advanced anomaly detection and evaluation.

Gage, Mark↗
NASA NTRS2004

NEXT Ion Engine 2000 Hour Wear Test Results

The results of the NEXT 2000 h wear test are presented. This test was conducted with a 40 cm engineering model ion engine, designated EM1, at a 3.52 A beam current and 1800 V beam power supply voltage. Performance tests, which were conducted over a throttling range of 1.1 to 6.9 kW throughout the wear test, demonstrated that EM1 satisfied all thruster performance requirements. The ion engine accumulated 2038 h of operation at a thruster input power of 6.9 kW, processing 43 kg of xenon. Overall ion engine performance, which includes thrust, thruster input power, specific impulse, and thrust efficiency, was steady with no indications of performance degradation. The ion engine was also inspected following the test. This paper presents these findings.

Soulas, George C.↗
NASA NTRS2013

Workflow-Based Software Development Environment

The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment

Izygon, Michel E.↗
NASA NTRS2018

A Systems Architecting Methodology Using Bloom’s Taxonomy to Promote Creative Engineering Synthesis

Architecting complex systems requires high-level cognitive processing and extensive knowledge of the system elements, functions, relationships, and constraints. This paper describes a systems architecting methodology implemented through cognitive psychological creative processes using Bloom’s taxonomy as a framework to generate the expert knowledge required to effectively and systematically synthesize new systems. Systems architecting activities were carried out to identify, develop, and capture factual and conceptual knowledge relevant to the system subject matter and functional elements, as well as to facilitate active processing of the knowledge through remembering, understanding, applying, analyzing, evaluating, and creating. Dual channel and limited capacity principles of learning were incorporated into the format of the systems engineering tools developed to assist with information processing and retention. Meta-cognitive strategies associated with memory and creative idea generation were implemented into the methodology to effectively and efficiently develop system alternatives using the full collection of knowledge. Synthesis of an orbiting sample capture and orientation system architecture to enable spacecraft-based on orbit capture of a Mars sample container for a potential Mars Sample Return campaign was used as a case study.

Adajian, Rama↗
NASA NTRSDate not supplied

Propulsion-Airframe Integration for Conceptual Redesign of a Low-Boom Supersonic Transport

A low-boom supersonic transport was designed for a cruise Mach of 1.7 and 40 passengers. This low-boom aircraft, referred to as the Mach 1.7 40-PAX concept, was generated using computational fluid dynamics (CFD) based sonic boom analysis at the start of overland cruise (SOC). The engine for the Mach 1.7 40-PAX concept was designed using the Numerical Propulsion System Simulation (NPSS) and modeled as a flow-through nacelle for CFD analysis. To understand how the engine plume affects the undertrack ground signature, the Mach 1.7 40-PAX concept is redesigned using an aeropropulsive CFD simulation. A process for approximation of the NPSS engine at SOC by a CFD engine is developed. The generated CFD engine has the identical nozzle boundary conditions and approximately the same mass flow and thrust as those of the NPSS engine at SOC. Then, the configuration with the CFD engines is optimized to approximately restore the low-boom characteristics of the Mach 1.7 40-PAX concept. Finally, the CFD simulation data for the optimized concept with the CFD engines is used to calibrate the low-fidelity aerodynamic analyses for mission analysis of this concept. The cyclic dependency of the involved disciplinary analyses is resolved using an iteration method for a consistent coupling of the mission analysis, NPSS engine analysis, and low-boom redesign using the aeropropulsive CFD simulation. This low-boom redesign study is used as an example to demonstrate how the propulsion-airframe integration could be implemented for conceptual design of low-boom supersonic transports.

Low-boom supersonic transport↗
NASA NTRS2010

Cost/Effort Drivers and Decision Analysis

Engineering trade study analyses demand consideration of performance, cost and schedule impacts across the spectrum of alternative concepts and in direct reference to product requirements. Prior to detailed design, requirements are too often ill-defined (only goals ) and prone to creep, extending well beyond the Systems Requirements Review. Though lack of engineering design and definitive requirements inhibit the ability to perform detailed cost analyses, affordability trades still comprise the foundation of these future product decisions and must evolve in concert. This presentation excerpts results of the recent NASA subsonic Engine Concept Study for an Advanced Single Aisle Transport to demonstrate an affordability evaluation of performance characteristics and the subsequent impacts on engine architecture decisions. Applying the Process Based Economic Analysis Tool (PBEAT), development cost, production cost, as well as operation and support costs were considered in a traditional weighted ranking of the following system-level figures of merit: mission fuel burn, take-off noise, NOx emissions, and cruise speed. Weighting factors were varied to ascertain the architecture ranking sensitivities to these performance figures of merit with companion cost considerations. A more detailed examination of supersonic variable cycle engine cost is also briefly presented, with observations and recommendations for further refinements.

Seidel, Jonathan↗
NASA NTRS1979

Restoration Process

In the accompanying photos, a laboratory technician is restoring the once-obliterated serial number of a revolver. The four-photo sequence shows the gradual progression from total invisibility to clear readability. The technician is using a new process developed in an applications engineering project conducted by NASA's Lewis Research Center in conjunction with Chicago State University. Serial numbers and other markings are frequently eliminated from metal objects to prevent tracing ownership of guns, motor vehicles, bicycles, cameras, appliances and jewelry. To restore obliterated numbers, crime laboratory investigators most often employ a chemical etching technique. It is effective, but it may cause metal corrosion and it requires extensive preparatory grinding and polishing. The NASA-Chicago State process is advantageous because it can be applied without variation to any kind of metal, it needs no preparatory work and number recovery can be accomplished without corrosive chemicals; the liquid used is water.

Source record↗
NASA NTRS2024

Core/Combustor-Noise Measurements and Source Separation for the DGEN Aeropropulsion Research Turbofan

Acoustic data obtained using a small turbofan engine are further analyzed with the aim to ultimately enable improved prediction methods and mitigation techniques for turbofan core/combustor noise. The relative impact of this propulsion-noise source for civilian-transport aircraft on airport community noise is expected to significantly increase in the future. Simultaneous high-data-rate acoustic measurements acquired using a circumferential infinite-tube-probe array at the core-nozzle exit in conjunction with a far-field microphone array are processed. The test matrix contains engine operational points from idle to engine-maximum setting, with measurements repeated for different circumferential array configurations, as well as for redundancy. The combustor-noise contribution to the far-field noise signature is obtained using an advanced source-separation method that correlates far-field microphone measurements with a modal decomposition of the unsteady pressure field at the core-nozzle exit. The advantages of the present approach compared to the classical two-signal source-separation method are discussed.

Aeroacoustics↗
NASA NTRS2014

A Process for the Creation of T-MATS Propulsion System Models from NPSS Data

A modular thermodynamic simulation package called the Toolbox for the Modeling and Analysis of Thermodynamic Systems (T-MATS) has been developed for the creation of dynamic simulations. The T-MATS software is designed as a plug-in for Simulink(Trademark) and allows a developer to create system simulations of thermodynamic plants (such as gas turbines) and controllers in a single tool. Creation of such simulations can be accomplished by matching data from actual systems, or by matching data from steady state models and inserting appropriate dynamics, such as the rotor and actuator dynamics for an aircraft engine. This paper summarizes the process for creating T-MATS turbo-machinery simulations using data and input files obtained from a steady state model created in the Numerical Propulsion System Simulation (NPSS). The NPSS is a thermodynamic simulation environment that is commonly used for steady state gas turbine performance analysis. Completion of all the steps involved in the process results in a good match between T-MATS and NPSS at several steady state operating points. Additionally, the T-MATS model extended to run dynamically provides the possibility of simulating and evaluating closed loop responses.

gas path dynamics↗
NASA NTRS1997

Software Design Improvements: Software Quality and the Design and Inspection Process - Part 2

The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.

Lalli, Vincent R.↗
NASA NTRS2014

A Process for the Creation of T-MATS Propulsion System Models from NPSS Data

A modular thermodynamic simulation package called the Toolbox for the Modeling and Analysis of Thermodynamic Systems (T-MATS) has been developed for the creation of dynamic simulations. The T-MATS software is designed as a plug-in for Simulink(Registered TradeMark) and allows a developer to create system simulations of thermodynamic plants (such as gas turbines) and controllers in a single tool. Creation of such simulations can be accomplished by matching data from actual systems, or by matching data from steady state models and inserting appropriate dynamics, such as the rotor and actuator dynamics for an aircraft engine. This paper summarizes the process for creating T-MATS turbo-machinery simulations using data and input files obtained from a steady state model created in the Numerical Propulsion System Simulation (NPSS). The NPSS is a thermodynamic simulation environment that is commonly used for steady state gas turbine performance analysis. Completion of all the steps involved in the process results in a good match between T-MATS and NPSS at several steady state operating points. Additionally, the T-MATS model extended to run dynamically provides the possibility of simulating and evaluating closed loop responses.

gas path dynamics↗
NASA NTRS2014

A Process for the Creation of T-MATS Propulsion System Models from NPSS data

A modular thermodynamic simulation package called the Toolbox for the Modeling and Analysis of Thermodynamic Systems (T-MATS) has been developed for the creation of dynamic simulations. The T-MATS software is designed as a plug-in for Simulink (Math Works, Inc.) and allows a developer to create system simulations of thermodynamic plants (such as gas turbines) and controllers in a single tool. Creation of such simulations can be accomplished by matching data from actual systems, or by matching data from steady state models and inserting appropriate dynamics, such as the rotor and actuator dynamics for an aircraft engine. This paper summarizes the process for creating T-MATS turbo-machinery simulations using data and input files obtained from a steady state model created in the Numerical Propulsion System Simulation (NPSS). The NPSS is a thermodynamic simulation environment that is commonly used for steady state gas turbine performance analysis. Completion of all the steps involved in the process results in a good match between T-MATS and NPSS at several steady state operating points. Additionally, the T-MATS model extended to run dynamically provides the possibility of simulating and evaluating closed loop responses.

gas path dynamics↗
NASA NTRS2015

Human Systems Integration (HSI) Practitioner's Guide

The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).

Zumbado, Jennifer Rochlis↗
NASA NTRS1996

Turbulence Modeling: Progress and Future Outlook

Progress in the development of the hierarchy of turbulence models for Reynolds-averaged Navier-Stokes codes used in aerodynamic applications is reviewed. Steady progress is demonstrated, but transfer of the modeling technology has not kept pace with the development and demands of the computational fluid dynamics (CFD) tools. An examination of the process of model development leads to recommendations for a mid-course correction involving close coordination between modelers, CFD developers, and application engineers. In instances where the old process is changed and cooperation enhanced, timely transfer is realized. A turbulence modeling information database is proposed to refine the process and open it to greater participation among modeling and CFD practitioners.

Marvin, Joseph G.↗