Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Engineering management”

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 325 records · Page 18

Engineering Effort Needed to Design Spacecraft with Radiation Constraints

A roadmap is articulated that describes what is needed to allow designers, to include researchers, management, and engineers, to investigate, design, build, test, and fly spacecraft that meet the mission requirements yet, be as low cost as possible. This roadmap describes seven levels of tool fidelity and application: 1) Mission Speculation, 2) Management Overview, 3) Mission Design, 4) Detailed Design, 5) Simulation and Training, 6) Operations, and 7) Research. The interfaces and output are described in top-level detail along with the transport engines needed, and deficiencies are noted. This roadmap, if implemented, will allow Multidisciplinary Optimization (MDO) ideas to incorporate radiation concerns. Also, as NASA moves towards Simulation Based Acquisition (SBA), these tools will facilitate the appropriate spending of government money. Most of the tools needed to serve these levels do not exist or exist in pieces and need to be integrated to create the tool.

Singleterry, Robert C., Jr.↗

Lightning Protection Guidelines for Aerospace Vehicles

This technical memorandum provides lightning protection engineering guidelines and technical procedures used by the George C. Marshall Space Flight Center (MSFC) Electromagnetics and Aerospace Environments Branch for aerospace vehicles. The overviews illustrate the technical support available to project managers, chief engineers, and design engineers to ensure that aerospace vehicles managed by MSFC are adequately protected from direct and indirect effects of lightning. Generic descriptions of the lightning environment and vehicle protection technical processes are presented. More specific aerospace vehicle requirements for lightning protection design, performance, and interface characteristics are available upon request to the MSFC Electromagnetics and Aerospace Environments Branch, mail code EL23.

Goodloe, C. C.↗

National meeting to review IPAD status and goals

A joint NASA/industry project called Integrated Programs for Aerospace-vehicle Design (IPAD) is described, which has the goal of raising aerospace-industry productivity through the application of computers to integrate company-wide management of engineering data. Basically a general-purpose interactive computing system developed to support engineering design processes, the IPAD design is composed of three major software components: the executive, data management, and geometry and graphics software. Results of IPAD activities include a comprehensive description of a future representative aerospace vehicle design process and its interface to manufacturing, and requirements and preliminary design of a future IPAD software system to integrate engineering activities of an aerospace company having several products under simultaneous development.

Fulton, R. E.↗

Flight testing the Digital Electronic Engine Control (DEEC) A unique management experience

The concept for the DEEC had its origin in the early 1970s. At that time it was recognized that the F100 engine performance, operability, reliability, and cost could be substantially improved by replacing the original mechanical/supervisory electronic control system with a full-authority digital control system. By 1978, the engine manufacturer had designed and initiated the procurement of flight-qualified control system hardware. As a precursor to an integrated controls program, a flight evaluation of the DEEC system on the F-15 aircraft was proposed. Questions regarding the management of the DEEC flight evaluation program are discussed along with the program elements, the technical results of the F-15 evaluation, and the impact of the flight evaluation on after-burning turbofan controls technology and its use in and application to military aircraft. The lessons learned through the conduct of the program are discussed.

Putnam, T. W.↗

A Model-Based Framework for NASA Science Mission Formulation

This paper details an effort to implement NASA systems engineering standards and practices using a Digital System Model (DSM), which we also refer to as the system architecture model (SAM). Creating a SAM at the beginning of a design effort helps systems engineer identify errors, inconsistencies, and miscommunications as early as possible. Such issues can then be resolved before it becomes costly and requires significant rework to do so. A pre-formulation SAM also enables advanced trade studies at the earliest stage of concept development. This results in “win-wins” where architecture changes can reduce cost without decreasing effectiveness, or increase effectiveness without increasing cost. SAMs also streamline the creation of project documentation and facilitate superior dialogue between science, engineering, and management stakeholders. Common artifacts such as Master Equipment Lists (MELs), Science Traceability Matrices (STMs), and Mission Traceability Matrices (MTMs), can be automatically maintained through requirements and structural models in the SAM. Key performance parameters (and changes to them) can be tied to simulations in the SAM, allowing far more rapid and extensive trade space exploration. As will be shown in this work, these advantages have been realized for the first time in an actual NASA Goddard Space Flight Center (GSFC) pre-phase A and phase A concept study. Modelbased design tools have been developed in a general, modular manner to maximize reuse on future programs. Focus is placed on structural and requirements architecture modeling. Data is ingested into the SAM from existing discipline model outputs (e.g. MS Excel spreadsheets) and used to update a SysML structural model. A mission requirements model is created within the SAM, containing mission specific as well as standard GSFC mission requirements. With the linked requirements model and structural model, automated compliance checking will be performed as mission parameters evolve without the need for discipline engineers to work directly with the SAM in SysML.

MBSE↗

Evaluation of Howard A. Hanson Dam Juvenile Fish Passage and Survival Study Live Fish Injury Assessment, Sensor Fish, and BioPA Modeling Tasks

The live fish injury assessment, Sensor Fish, and BioPA modeling study tasks were conducted by researchers from Pacific Northwest National Laboratory (PNNL). The four tasks were part of the larger Evaluation of Howard A. Hanson Dam (HAHD) Juvenile Fish Passage and Survival study, which had six total tasks. To achieve study objectives for each of the four tasks, field work occurred at Green Peter Dam (GPR) to evaluate the highest elevation steep slope bypass pipe, at HAHD to evaluate baseline conditions of the horseshoe tunnel, and at PNNL’s Aquatic Research Laboratory (ARL) to evaluate simulated dam passage conditions (i.e., shear forces and collision). Each of these evaluations utilized live fish injury assessment, Sensor Fish, and BioPA modeling. Live fish injury assessment and survival (tagged with and without balloon or passive integrated transponder [PIT] tags) was correlated with Sensor Fish to determine thresholds. The CFD analyses were then performed, and the computed values were compared to the corresponding measured values of Sensor Fish data. The results of the overall injury and survival of fish was also used in the validation of the CFD modeling method. Collectively, the results will aid in future modeling of fish passage at HAHD. Results from these tasks can be used by biologists, engineers, resource managers, and regional decision-makers to inform baseline conditions under current operations and the engineering design of the new FPF at HAHD. This draft report contains initial data and results from the four tasks. Table 8 1, Table 8 2, and Table 8 3, and Figure 8 1, Figure 8 2, and Figure 8 3 depict the CFD modeling findings for the GPR steep slope bypass, HAHD horseshoe tunnel, and laboratory testing. Table 8 4, Table 8 5, and Table 8 6 depict the Sensor Fish findings for the GPR steep slope bypass and HAHD horseshoe tunnel testing. The Mv values observed in the HAHD were significantly lower compared to the laboratory experiments conducted at PNNL. Currently, investigations are underway to understand the reasons for this disparity and to establish an appropriate threshold value for Mv. Survival predictions presented in the tables below should be considered preliminary and should not be used until further analyses and adjustments are completed. The next steps for modeling will include the flow regime, (i.e., density of flow regimes due to water and air mixing ) to continue to improve on the threshold value for Mv.

13 HYDRO ENERGY↗

Integration of design information

The overall concepts of the integrated programs for aerospace-vehicle design (IPAD) from the user's viewpoint are discussed. Also a top-level view of what the user requires from such a system is provided, and the interactions between the system and user are described. The four major components discussed are design process; data storage, management and manipulation; user interface; and project management. Although an outgrowth of aerospace production experience, the basic concepts discussed, and especially their emphasis on integration, are considered applicable to all problem solving. Thus, these concepts may offer a broad base for exploitation by industry in general. This is the first in a set of three papers, the other two being Future Integrated Design Process, by D. D. Mayer, and Requirements for Company-Wide Management of Engineering Information, by J. W. Southall. In addition to tying the three together, how project management can be handled in a computing environment and also the user interface needs are discussed in detail.

Anderton, G. L.↗

Configuration Management File Manager Developed for Numerical Propulsion System Simulation

One of the objectives of the High Performance Computing and Communication Project's (HPCCP) Numerical Propulsion System Simulation (NPSS) is to provide a common and consistent way to manage applications, data, and engine simulations. The NPSS Configuration Management (CM) File Manager integrated with the Common Desktop Environment (CDE) window management system provides a common look and feel for the configuration management of data, applications, and engine simulations for U.S. engine companies. In addition, CM File Manager provides tools to manage a simulation. Features include managing input files, output files, textual notes, and any other material normally associated with simulation. The CM File Manager includes a generic configuration management Application Program Interface (API) that can be adapted for the configuration management repositories of any U.S. engine company.

Follen, Gregory J.↗

A plume spectroscopy system for flight applications

An operational plume spectroscopy system will be an important element of any rocket engine health management system (HMS). The flight capable FPI spectrometer will enable prognosis and response to incipient rocket engine failures as well as diagnosis of wear and degradation for on-condition maintenance. Spectrometer application to development programs, such as the Space Lifter, NASP, and SSTO, will reduce program risks, allow better adherence to schedules and save money by reducing or eliminating redesign and test costs. The diagnostic capability of a proven, calibrated spectrometer will enhance post-burn certification of high value, reusable engines, such as the Space Shuttle Main Engine (SSME), where life and reliability are key cost drivers. This paper describes a prototype FPI spectrometer for demonstration and validation testing on NASA's Technology Test Bed Engine (TTBE) at Marshall Space Flight Center. The TTBE test unit is designed with flight prototype optics and a commercial off-the-shelf data processing system.

Makel, D. B.↗

Development and Testing of Pulse Guns for Combustion Instability Testing

To test liquid rocket engines (LREs) for combustion instabilities, devices such as bombs are often used to create pressure wave disturbances. Bombs, while effective, are inherently dangerous, expensive, and difficult to procure. Over the years, pulse guns have been used as a safer and more cost-effective way to generate controlled pressure disturbances in engine chambers. In anticipation of the need for stability testing of prototype LREs at NASA Marshall Space Flight Center (MSFC), a set of pulse guns have been designed, fabricated, tested, and characterized. The pulse gun program is funded by the RS-25 Engine Program managed out of MSFC and funded by NASA’s Space Launch System (SLS) through the MSFC Liquid Engines Office (LEO). A pulse gun is a simple device – like a traditional gun, it has a breech and barrel section. However, unlike a traditional gun, there is no bullet, as the purpose of the pulse gun is strictly to fire a high pressure pulse. Instead of a firing pin and primer that would normally be used in a traditional gun, an initiator is used to activate the gun powder. The initiator is a highly reliable pyrotechnic initiator. For this study, clone versions of the NASA Standard Initiator (NSI) were used. The initiator is used to ignite a pre-measured amount of gun powder loaded into the breech. When the pressure of the burnt gun powder exceeds the set point of a downstream burst disk, the disk ruptures, allowing the high pressure pulse to travel downstream through the barrel section. A ballistic pressure transducer located in the breech section is used to measure the short duration, high pressure pulse. Some configurations of the pulse gun have barrel sections that include one or more additional ballistic pressure transducers. These additional pressure measurements help track the degradation and damping of the pulse as it travels out of the barrel section. The measurements may also be used to determine the velocity of pulse. The objective of this paper is to present the different variants of this newly-developed pulse gun and characterize performance over a range of parameters. The parameters include breech diameter, barrel length, amount of gun powder used, the way the gun powder is packed, and the pressure setting of the burst disk. There are a total of six pulse guns: three with the 0.25 inch breech and three different length barrels, and three with the 0.40 inch breech and three different length barrels. For both breech sizes, the associated barrels are referred to as standard, one-port, and two-port barrels. The standard barrel has no instrumentation and is likely the barrel that will be used for engine stability testing. The one- and two-port barrels were designed specifically for pulse gun component testing to allow measurements of the magnitude and timing of the high pressure pulse as it makes its way through the pulse gun. The burst disks tested were commercially-available burst disks designed to rupture at 8,000, 16,000, and 24,000 psid. Testing was accomplished by firing the pulse gun into a test chamber pressurized with nitrogen at about 2300 psig. A total of four Model 113B23 High frequency ICP® pressure sensors (10k psi) were mounted in the test chamber, in the same plane as the pulse gun. Two of the sensors had “trimmed” adapters, and two did not. Given the symmetrical configuration of the sensors within the test chamber, different amplitudes of pressure measurements are attributed to the use of trimmed versus untrimmed adapters. The untrimmed adapters, with their narrower passages, tended to amplify the pressure amplitudes by as much as 50%. In total, 41 pulse gun tests have been conducted.Data are still being analyzed, but some trends are apparent. For example, measurements taken within the pulse gun are shown in Figures 3 and 4 for Hot-fires (HFs) # 11 and 39, respectively. Both tests were identical in that the 0.40 inch ID breech, two-port barrel, 8,000 psid burst disk, and same amount of gunpowder (6.639 grains for HF# 11, and 6.576 grains for HF# 39) were used, and the back pressure in the nitrogen test chamber was ~2300 psig. Despite keeping all these variables constant, the results from these two tests look quite different. For both tests, the first pressure peak shown in the P2111 trace within the breech is the firing of the initiator. The second peak and any subsequent peaks are from the combustion of the gunpowder. It should be noted that because the sensors are dynamic, the ~2300 psig baseline static pressure is not shown in the figures. For HF# 11, the burst disk clearly ruptured in a little over 0.1 ms from the time the initiator was fired. This is evident from the abrupt rise in pressure for P2112 followed by another abrupt rise in pressure for P2113. The sensors track the movement of the high pressure pulse through the pulse gun. For HF# 39, however, there was nearly 1 ms delay between the initiator firing and the burst disk rupturing. The only difference between these two tests was the way in which the gunpowder was packed within the breech. For HF# 11, the gunpowder was poured directly into the breech, atop the initiator, and held in place with a vegetable fiber wad appropriately sized for the barrel diameter. Once in place, the wad firmly held the gunpowder in place. For HF# 39, the gunpowder was rolled within cigarette paper with the ends of the paper twisted. The rolled gunpowder was gently pushed down into the breech, toward the initiator, and no wad was used. This method of loading the gunpowder consistently produced longer delays in the rupture of the burst disk, presumably because there was a steady, fuller burning of the gunpowder. The burst disk was rated for 8,000 psid, which means that the burst disk should not have opened until the pressure in the breech reached ~10,300 since there was ~2300 psig back pressure in the test chamber. In the case of HF# 11, the breech pressure only reached roughly 4200 psi before there was leakage either through or past the burst disk, but for HF#39, the breech pressure reached 10,600 psi prior to the burst disk opening. The temperature of the burst disk is certainly a factor in determining when the burst disk will rupture. A sharp rise in the burst disk temperature could weaken it and cause it to stray from the designed set point burst pressure. The burst disks are manufactured of Inconel to try to reduce their sensitivity to temperature, but how the burst disks perform above 900°F is not documented. All burst disks were engineered and tested by the manufacturer for ambient temperature conditions. One theory for why rolling the gunpowder in cigarette paper may produce better results is related to a more controlled temperature environment. The cigarette paper may act as a sheath that protects the burst disk from excessive temperatures during the rapid buildup of pressure in the breech. The ultimate benefit of not breeching the burst disk prematurely is shown in Figures 5 and 6, which graphs the resultant pressure pulse produced in the test chamber. For HF #11, the peak pressure on the P2123 trimmed adapter is about 270 psi, while for HF# 39 it is 343 psi, which is about 1.27 times greater in magnitude. In either case, the pressure pulse is ~20 μs in width once it reaches the test chamber. Another pressure rise about 100 μs later can be seen on the sensors located across from the pulse gun port, P2124 and P2121. These pressures are lower due to attenuation of the pressure wave as it moves across the test chamber. After the wave encounters the wall, it reflects back and forth within the chamber until it completely dissipates.

Pulse Gun↗

Power and Propulsion: Small Core Advanced Thermal Management Project Overview

This presentation is intended to provide an overview of the various efforts under the Advanced Air Transport Technology (AATT) project related to engine thermal management. Sustainable flight is the key motivator for all our efforts, and innovative thermal technologies play a crucial role in achieving this goal. The technologies described in this presentation can be applied to both traditional gas turbines and advanced cycles which utilize alternative fuels. Within our project, we utilize the capabilities of artificial intelligence (AI), machine learning (ML), and additive manufacturing. This ranges from using AI to generate heat exchanger fin topologies, to using ML for a reduction in computational cost which allows for a more thorough design exploration. Many times, the resulting topologies can only be realized through additive manufacturing techniques. Most of what’s presented is currently low TRL, but the intent is to achieve TRL 4 by the end of the project.

Propulsion↗

Some effects of time usage patterns on the productivity of engineers

The performance of the 1500+ engineers at MSFC is critical to the Center's mission. Worker's performance, however, is a variable affected by ability, motivation, role understanding, and other factors. Managing subordinates' performance is a great challenges to managers. Special challenges confront the managers of engineers because engineers often work with general goals, long deadlines, and considerable autonomy. The productivity of a team or branch is a function of the productivity of each of its members. While many managers have personal theories about how to run their work group, surprisingly little systematic scientific knowledge exerts about the effects of various factors on engineers' productivity. This study is intended to help lay the foundation for such a program of research.

Jackson, Conrad N.↗

Application of probabilistic analysis/design methods in space programs - The approaches, the status, and the needs

The prospective improvement of probabilistic methods for space program analysis/design entails the further development of theories, codes, and tools which match specific areas of application, the drawing of lessons from previous uses of probability and statistics data bases, the enlargement of data bases (especially in the field of structural failures), and the education of engineers and managers on the advantages of these methods. An evaluation is presently made of the current limitations of probabilistic engineering methods. Recommendations are made for specific applications.

Ryan, Robert S.↗

Systems Engineering and Integration for Advanced Life Support System and HST

Systems engineering (SE) discipline has revolutionized the way engineers and managers think about solving issues related to design of complex systems: With continued development of state-of-the-art technologies, systems are becoming more complex and therefore, a systematic approach is essential to control and manage their integrated design and development. This complexity is driven from integration issues. In this case, subsystems must interact with one another in order to achieve integration objectives, and also achieve the overall system's required performance. Systems engineering process addresses these issues at multiple levels. It is a technology and management process dedicated to controlling all aspects of system life cycle to assure integration at all levels. The Advanced Integration Matrix (AIM) project serves as the systems engineering and integration function for the Human Support Technology (HST) program. AIM provides means for integrated test facilities and personnel for performance trade studies, analyses, integrated models, test results, and validated requirements of the integration of HST. The goal of AIM is to address systems-level integration issues for exploration missions. It will use an incremental systems integration approach to yield technologies, baselines for further development, and possible breakthrough concepts in the areas of technological and organizational interfaces, total information flow, system wide controls, technical synergism, mission operations protocols and procedures, and human-machine interfaces.

Kamarani, Ali K.↗

Marshall Space Flight Center Ground Systems Development and Integration

Ground Systems Development and Integration performs a variety of tasks in support of the Mission Operations Laboratory (MOL) and other Center and Agency projects. These tasks include various systems engineering processes such as performing system requirements development, system architecture design, integration, verification and validation, software development, and sustaining engineering of mission operations systems that has evolved the Huntsville Operations Support Center (HOSC) into a leader in remote operations for current and future NASA space projects. The group is also responsible for developing and managing telemetry and command configuration and calibration databases. Personnel are responsible for maintaining and enhancing their disciplinary skills in the areas of project management, software engineering, software development, software process improvement, telecommunications, networking, and systems management. Domain expertise in the ground systems area is also maintained and includes detailed proficiency in the areas of real-time telemetry systems, command systems, voice, video, data networks, and mission planning systems.

Wade, Gina↗

Reliability growth models for NASA applications

The objective of any reliability growth study is prediction of reliability at some future instant. Another objective is statistical inference, estimation of reliability for reliability demonstration. A cause of concern for the development engineer and management is that reliability demands an excessive number of tests for reliability demonstration. For example, the Space Transportation Main Engine (STME) program requirements call for .99 reliability at 90 pct. confidence for demonstration. This requires running 230 tests with zero failure if a classical binomial model is used. It is therefore also an objective to explore the reliability growth models for reliability demonstration and tracking and their applicability to NASA programs. A reliability growth model is an analytical tool used to monitor the reliability progress during the development program and to establish a test plan to demonstrate an acceptable system reliability.

Taneja, Vidya S.↗

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↗

Gamma ray observatory productivity showcase

The Gamma Ray Observatory (GRO) Program has been proclaimed to be the showcase productivity program for NASA and TRW. Among the multiple disciplines of a large-scale program, there is opportunity and need for improved efficiency, effectiveness, and reduction in the cost of doing business. The efforts and tools that will or have been implemented to achieve this end are described. Since the GRO Program is mainly an engineering program with the build of one satellite, the primary emphasis is placed on improving the efficiency and quality of management and engineering.

Davis, R. L.↗