Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “design and process development”

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 667 records · Page 37
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

VLSI technology for smaller, cheaper, faster return link systems

Very Large Scale Integration (VLSI) Application-specific Integrated Circuit (ASIC) technology has enabled substantially smaller, cheaper, and more capable telemetry data systems. However, the rapid growth in available ASIC fabrication densities has far outpaced the application of this technology to telemetry systems. Available densities have grown by well over an order magnitude since NASA's Goddard Space Flight Center (GSFC) first began developing ASIC's for ground telemetry systems in 1985. To take advantage of these higher integration levels, a new generation of ASIC's for return link telemetry processing is under development. These new submicron devices are designed to further reduce the cost and size of NASA return link processing systems while improving performance. This paper describes these highly integrated processing components.

Nanzetta, Kathy↗
NASA NTRS1999

National Cycle Program (NCP) Common Analysis Tool for Aeropropulsion

Through the NASA/Industry Cooperative Effort (NICE) agreement, NASA Lewis and industry partners are developing a new engine simulation, called the National Cycle Program (NCP), which is the initial framework of NPSS. NCP is the first phase toward achieving the goal of NPSS. This new software supports the aerothermodynamic system simulation process for the full life cycle of an engine. The National Cycle Program (NCP) was written following the Object Oriented Paradigm (C++, CORBA). The software development process used was also based on the Object Oriented paradigm. Software reviews, configuration management, test plans, requirements, design were all apart of the process used in developing NCP. Due to the many contributors to NCP, the stated software process was mandatory for building a common tool intended for use by so many organizations. The U.S. aircraft and airframe companies recognize NCP as the future industry standard for propulsion system modeling.

Follen, G.↗
DOE OSTI2023

Data Challenges in Multi-Sensor Data Science System for Monitoring a Solvent Extraction Process

Idaho National Laboratory (INL) is maintaining and gaining knowledge into the nuclear fuel cycle by building a test bed to allow researchers the opportunity to study nuclear fuel processing operations. This includes studying solvent extraction processes that use centrifugal contactors. As part of INL’s mission, the goal of this project is to develop a system that utilizes non-traditional measurement sources such as vibration, acoustics, current, light, flow, and temperature in conjunction with data-based, machine learning techniques that will allow for signal discovery. This multisensory data can support the development of safeguards by design, provide operator process awareness, and discover process anomalies. This poster will highlight some of the data collection and analytics challenges for the multi-sensor system as well as the mitigation strategies to build a robust system. Additionally, some preliminary data from the first testing campaign will be shown to help illustrate the data needs of the system.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
DOE OSTI2021

Open Building Control

Best practice control sequences are often not implemented correctly, or are not implemented at all, in large commercial buildings. This typically leads to 10-30 percent energy waste, along with reduced occupant productivity and unnecessary equipment wear. The current process of designing and implementing such control sequences is a manual process that starts with designers who often don’t have adequate training, then requires controls programmers to interpret and program a verbose written sequence. This process has been shown to fail to deliver high performance control sequences at scale. The Open Building Control project digitizes the current control delivery process. The project is developing tools for system designers to select control sequences, assess their energy performance and load flexibility potential using whole building simulation, specify the sequence for implementation using machine-to-machine translation by a control provider and formally testing the as-installed sequences by a commissioning agent. The project developed tools for each stage of this delivery process. The key innovation of the project is the development of the Control Description Language, a language that allows such a digitized control delivery process with end-to-end verification. Libraries of control sequences have been implemented using the Control Description Language, and their performance has been demonstrated using whole building energy simulation. An automated translation of such sequences to a commercial control product line has been conducted using a prototype translator. Tools for formal verification of as-installed control sequences relative to their specification have been developed and demonstrated. The American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) started the process of forming a committee to make this language an ASHRAE/ANSI Standard. This new standard will complement existing and emerging ASHRAE standards for building communication and semantic modeling by providing a standard for expressing the control logic - the actual brain of the building. We expect this language and the process it enables to be an important contribution to the deployment of high performance building control sequences at scale because it allows taming the complexity of the control delivery process, which is continually increasing due to the need for higher performance and increased load flexibility to meet goals for net zero energy and increased renewable integration.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRS1981

Earth feature identification for onboard multispectral data editing: Computational experiments

A computational model of the processes involved in multispectral remote sensing and data classification is developed as a tool for designing smart sensors which can process, edit, and classify the data that they acquire. An evaluation of sensor system performance and design tradeoffs involves classification rates and errors as a function of number and location of spectral channels, radiometric sensitivity and calibration accuracy, target discrimination assignments, and accuracy and frequency of compensation for imaging conditions. This model provides a link between the radiometric and statistical properties of the signals to be classified and the performance characteristics of electro-optical sensors and data processing devices. Preliminary computational results are presented which illustrate the editing performance of several remote sensing approaches.

Aherron, R. M.↗
DOE OSTI2022

Fabrication experience of the pre-production PIP-II SSR2 cavities at Fermilab

The Proton Improvement Plan-II (PIP-II, [1]) linac will include 35 Single Spoke Resonators type 2 (SSR2). A total of eight pre-production SSR2 jacketed cavities will be procured and five installed in the first pre-production cryomodule. The mechanical design of the jacketed cavity has been finalized and it will be presented in this paper along with fabrication and processing experience. The importance of interfaces, quality controls and procurement aspects in the design phase will be remarked as well as lessons learned during the fabrication process. Furthermore, development studies will be presented together with other design validation tests.

43 PARTICLE ACCELERATORS↗
NASA NTRS2022

Run Time Assurance for Electric Vertical Takeoff and Landing Aircraft

NASA is conducting research to demonstrate and evaluate the application of Run Time Assurance (RTA) as a means to assure safety in Electric Vertical Takeoff and Landing (eVTOL) aircraft with highly automated or autonomous flight capability supervised by a single onboard pilot. The work described in this report demonstrates an application of RTA and examines the implications for design and analysis of aircraft functions and systems; aircraft safety hazards; safety assurance; development assurance; and pilot tasks and performance. This research effort also seeks to assess the efficacy of the combined application of traditional Functional Hazard Analysis (FHA) and the more modern System Theoretic Process Analysis (STPA) techniques to perform hazard analyses on aircraft with complex automated and autonomous systems and an onboard pilot. During the research effort we developed architectural designs of two alternate eVTOL aircraft, generally following the process characterized in the SAE standards ARP4754 and ARP4761. The design has focused on the control architectures of these aircraft, which are identical except that one incorporates RTA techniques to reduce the criticality of some key software components. Artifacts of this process include a taxonomy of aircraft-level functions, aircraft-level architecture diagrams, aircraft-level functional hazard assessments (AFHA), function allocations onto aircraft systems and subsystems, functional block diagrams for a select set of control-related functions, and system-level functional hazard assessments (SFHA) for those functions. This project has highlighted the notion that DAL D is something of a sweet spot for low-confidence controllers in an RTA-based design. Among the many activities described in DO-178C, the activities related to requirement verifiability, algorithmic accuracy, and test coverage can be the most challenging for the kinds of advanced control techniques that may be desirable in novel UAM designs, such as adaptive control, machine-learning, artificial intelligence, numerical search, and Monte Carlo based algorithms. Moreover, the standard requires that development teams demonstrate that errors leading to unacceptable failure conditions have been removed from the software. The RTA architecture, which cordons off the low-confidence function, makes it much easier to show this for these kinds of algorithms. With regard to the use of STPA and FHA as complementary hazard analysis techniques, our research effort led us to the conclusion that STPA should be used to derive requirements for hardware and software systems and/or components. Also, STPA is a natural complement to other processes in ARP4754A involving design studies and iteration.

Run-time assurance↗
NASA NTRS2019

A Knowledge-Based Optimization Method for Aerodynamic Design

A new aerodynamic design method, CODISC, has been developed that combines a legacy knowledge-based design method, CDISC, with a simple optimization module known as SOUP. The primary goal of this new design system is to improve the performance gains obtained using CDISC without adding significant computational time. An additional objective of this approach is to reduce the need for a priori knowledge of good initial input variable values, as well as for subsequent manual revisions of those values as the design progresses. Several test cases illustrate the development of the process to date and some of the options available at transonic and supersonic speeds for turbulent flow designs. The test cases generally start from good baseline configurations and, in all cases, were able to improve the performance. Several new guidelines for good initial values for the design variables, as well as new design rules within CDISC itself, were developed from these cases.

SOUP↗
NASA NTRS2003

Analysis and Test Correlation of Proof of Concept Box for Blended Wing Body-Low Speed Vehicle

The Low Speed Vehicle (LSV) is a 14.2% scale remotely piloted vehicle of the revolutionary Blended Wing Body concept. The design of the LSV includes an all composite airframe. Due to internal manufacturing capability restrictions, room temperature layups were necessary. An extensive materials testing and manufacturing process development effort was underwent to establish a process that would achieve the high modulus/low weight properties required to meet the design requirements. The analysis process involved a loads development effort that incorporated aero loads to determine internal forces that could be applied to a traditional FEM of the vehicle and to conduct detailed component analyses. A new tool, Hypersizer, was added to the design process to address various composite failure modes and to optimize the skin panel thickness of the upper and lower skins for the vehicle. The analysis required an iterative approach as material properties were continually changing. As a part of the material characterization effort, test articles, including a proof of concept wing box and a full-scale wing, were fabricated. The proof of concept box was fabricated based on very preliminary material studies and tested in bending, torsion, and shear. The box was then tested to failure under shear. The proof of concept box was also analyzed using Nastran and Hypersizer. The results of both analyses were scaled to determine the predicted failure load. The test results were compared to both the Nastran and Hypersizer analytical predictions. The actual failure occurred at 899 lbs. The failure was predicted at 1167 lbs based on the Nastran analysis. The Hypersizer analysis predicted a lower failure load of 960 lbs. The Nastran analysis alone was not sufficient to predict the failure load because it does not identify local composite failure modes. This analysis has traditionally been done using closed form solutions. Although Hypersizer is typically used as an optimizer for the design process, the failure prediction was used to help gain acceptance and confidence in this new tool. The correlated models and process were to be used to analyze the full BWB-LSV airframe design. The analysis and correlation with test results of the proof of concept box is presented here, including the comparison of the Nastran and Hypersizer results.

Spellman, Regina L.↗
DOE OSTI2020

The Wave Energy Converter Design Process: Methods Applied in Industry and Shortcomings of Current Practices

Wave energy is among the many renewable energy technologies being researched and developed to address the increasing demand for low-emissions energy. The unique design challenges for wave energy converter design—integrating complex and uncertain technological, economic, and ecological systems, overcoming the structural challenges of ocean deployment, and dealing with complex system dynamics—have lead to a disjointed progression of research and development. There is no common design practice across the wave energy industry and there is no published synthesis of the practices that are used by developers. In this paper, we summarize the methods being employed in WEC design as well as promising methods that have yet to be applied. We contextualize these methods within an overarching design process. We present results from a survey of WEC developers to identify methods that are common in industry. From the review and survey results, we conclude that the most common methods of WEC design are iterative methods in which design parameters are defined, evaluated, and then changed based on evaluation results. This leaves a significant space for improvement of methods that help designers make better-informed decisions prior to sophisticated evaluation, and methods of using the evaluation results to make better design decisions during iteration. Despite the popularity of optimization methods in academic research, they are less common in industry development. We end this paper with a summary of the areas of WEC design in which the testing and development of new methods is necessary, and where more research is required to fully understand the influence of design decisions on WEC performance.

16 TIDAL AND WAVE POWER↗
NASA NTRS2012

Designing Mission Operations for the Gravity Recovery and Interior Laboratory Mission

NASA's Gravity Recovery and Interior Laboratory (GRAIL) mission, to understand the internal structure and thermal evolution of the Moon, offered unique challenges to mission operations. From launch through end of mission, the twin GRAIL orbiters had to be operated in parallel. The journey to the Moon and into the low science orbit involved numerous maneuvers, planned on tight timelines, to ultimately place the orbiters into the required formation-flying configuration necessary. The baseline GRAIL mission is short, only 9 months in duration, but progressed quickly through seven very unique mission phases. Compressed into this short mission timeline, operations activities and maneuvers for both orbiters had to be planned and coordinated carefully. To prepare for these challenges, development of the GRAIL Mission Operations System began in 2008. Based on high heritage multi-mission operations developed by NASA's Jet Propulsion Laboratory and Lockheed Martin, the GRAIL mission operations system was adapted to meet the unique challenges posed by the GRAIL mission design. This paper describes GRAIL's system engineering development process for defining GRAIL's operations scenarios and generating requirements, tracing the evolution from operations concept through final design, implementation, and validation.

MOS↗
NASA NTRS2003

Optimizing spacecraft design - optimization engine development : progress and plans

At JPL and NASA, a process has been developed to perform life cycle risk management. This process requires users to identify: goals and objectives to be achieved (and their relative priorities), the various risks to achieving those goals and objectives, and options for risk mitigation (prevention, detection ahead of time, and alleviation). Risks are broadly defined to include the risk of failing to design a system with adequate performance, compatibility and robustness in addition to more traditional implementation and operational risks. The options for mitigating these different kinds of risks can include architectural and design choices, technology plans and technology back-up options, test-bed and simulation options, engineering models and hardware/software development techniques and other more traditional risk reduction techniques.

risk↗
NASA NTRS1985

Processing technology for high efficiency silicon solar cells

Recent advances in silicon solar cell processing have led to attainment of conversion efficiency approaching 20%. The basic cell design is investigated and features of greatest importance to achievement of 20% efficiency are indicated. Experiments to separately optimize high efficiency design features in test structures are discussed. The integration of these features in a high efficiency cell is examined. Ion implantation has been used to achieve optimal concentrations of emitter dopant and junction depth. The optimization reflects the trade-off between high sheet conductivity, necessary for high fill factor, and heavy doping effects, which must be minimized for high open circuit voltage. A second important aspect of the design experiments is the development of a passivation process to minimize front surface recombination velocity. The manner in which a thin SiO2 layer may be used for this purpose is indicated without increasing reflection losses, if the antireflection coating is properly designed. Details are presented of processing intended to reduce recombination at the contact/Si interface. Data on cell performance (including CZ and ribbon) and analysis of loss mechanisms are also presented.

Spitzer, M. B.↗
DOE OSTI2021

Radiological Handling and Containment Considerations in Support of an American Medical Isotope Producer

This work will discuss evaluation and design of new and modified facility level radiological containment, transfer, and handling systems in support of the United States’ American Medical Isotope Production Act. In the United States alone, Molybdenum-99 (Mo-99) is used as a precursor to locally generate its decay product, technetium-99m (Tc-99m), for use in approximately 40,000 medical procedures every day to detect cancer and heart disease. Currently, however, Mo-99 is primarily produced overseas and typically requires highly enriched uranium (HEU) which is classified as weapon -usable. This poses a serious security risk to the United States and, in 2012, Congress passed the American Medical Isotope ACT which aimed to cease all Mo-99 production that requires HEU and support American based companies who have found safer production methods. Through this effort, a system was designed and developed to access irradiated material in processing hot cells for ease of material introduction and removal in the confined area. The proposed solution uses a double-door design that allows for easy access to material while also providing shielding through a mechanically manipulated carousel. A system was also designed to transport irradiated materials from target reactors to a target receipt box using a rail guide system, pneumatic motor, and lead screw drive.

07 ISOTOPE AND RADIATION SOURCES↗
NASA NTRS1986

ECUT (Energy Conversion and Utilization Technologies Program). Biocatalysis Project

Presented are the FY 1985 accomplishments, activities, and planned research efforts of the Biocatalysis Project of the U.S. Department of Energy, Energy Conversion and Utilization Technologies (ECUT) Program. The Project's technical activities were organized as follows: In the Molecular Modeling and Applied Genetics work element, research focused on (1) modeling and simulation studies to establish the physiological basis of high temperature tolerance in a selected enzyme and the catalytic mechanisms of three species of another enzyme, and (2) determining the degree of plasmid amplification and stability of several DNA bacterial strains. In the Bioprocess Engineering work element, research focused on (1) studies of plasmid propagation and the generation of models, (2) developing methods for preparing immobilized biocatalyst beads, and (3) developing an enzyme encapsulation method. In the Process Design and Analysis work element, research focused on (1) further refinement of a test case simulation of the economics and energy efficiency of alternative biocatalyzed production processes, (2) developing a candidate bioprocess to determine the potential for reduced energy consumption and facility/operating costs, and (3) a techno-economic assessment of potential advancements in microbial ammonia production.

Source record↗
NASA NTRS1998

Development and Testing of Automatically Generated ACS Flight Software for the MAP Spacecraft

By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.

ODonnell, James R., Jr.↗
DOE OSTI2025

Serpentine Magnet Designs for the Interaction Region of the Electron-Ion Collider (EIC)

The Electron-Ion Collider (EIC), hosted by Brookhaven National Laboratory, is designed to deliver a peak luminosity of 1 × 10 34 cm −2 sec −1 . The interaction region (IR) of the EIC imposes several constraints in terms of field quality, aperture, and spatial layout, which necessitates the development of several unique superconducting serpentine direct wind magnets. These magnets are constructed using either a single strand or a small-diameter 6-around-1 NbTi cable, presenting unique challenges for design and optimization. This paper introduces a new computational code specifically developed to streamline and integrate the design process for these magnets, enabling faster design iterations while addressing their complex requirements. Here, in this paper, we first introduce the code, which builds on established electromagnetic fundamentals. The code incorporates tools for optimizing winding patterns and for correcting magnetic multipoles; additionally, it interfaces with established magnet design software. We also present the design of several serpentine magnets for the EIC IR, demonstrating the code’s capability to deliver precise and efficient solutions. These designs highlight the code’s ability to accelerate the development cycle, ensuring the serpentine magnets meet the demanding specifications of the EIC project.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗