Search NASA⌕ Search

SEARCH · Search NASA

Results for “ENGINES - SPEED”

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 937 records · Page 52

TF41 Engine Fan Disk Seeded Fault Crack Propagation Test

Uncontained engine failures, although rare in occurrence, can have a catastrophic effect on aircraft performance and safety. Engine disk cracks can eventually lead to these type of failures. A number of techniques to detect engine disk cracks have been developed in recent years. However, these technologies have only been validated by disk spin pit tests, not actual engine tests. Due to this, a project was established to perform seeded fault engine tests on a TF41 engine disk fan. A defect was machined in the first stage fan disk of a TF41 engine. The disk was run in a spin pit to initiate a crack. Once initiated, the disk was run in an actual engine test facility. The engine was cycled by a number of start and stops with the goal of propagating the crack to disk burst through low cycle fatigue. Various crack detection techniques were installed on the engine and run real-time during the test to validate their abilities to detect disk cracks. These techniques were based on methods such as change in mass imbalance using vibration or shaft displacement, change in blade position, acoustic emission, and torsional resonance. At the completion of 4474 test cycles, the crack in the TF41 disk was determined to have grown approximately 0.025 inches. This was far less the predicted crack growth based on a fracture mechanics analysis and finite element stress analysis.

Lewicki, David G.↗

Advanced Health Management System for the Space Shuttle Main Engine

Boeing-Canoga Park (BCP) and NASA-Marshall Space Flight Center (NASA-MSFC) are developing an Advanced Health Management System (AHMS) for use on the Space Shuttle Main Engine (SSME) that will improve Shuttle safety by reducing the probability of catastrophic engine failures during the powered ascent phase of a Shuttle mission. This is a phased approach that consists of an upgrade to the current Space Shuttle Main Engine Controller (SSMEC) to add turbomachinery synchronous vibration protection and addition of a separate Health Management Computer (HMC) that will utilize advanced algorithms to detect and mitigate predefined engine anomalies. The purpose of the Shuttle AHMS is twofold; one is to increase the probability of successfully placing the Orbiter into the intended orbit, and the other is to increase the probability of being able to safely execute an abort of a Space Transportation System (STS) launch. Both objectives are achieved by increasing the useful work envelope of a Space Shuttle Main Engine after it has developed anomalous performance during launch and the ascent phase of the mission. This increase in work envelope will be the result of two new anomaly mitigation options, in addition to existing engine shutdown, that were previously unavailable. The added anomaly mitigation options include engine throttle-down and performance correction (adjustment of engine oxidizer to fuel ratio), as well as enhanced sensor disqualification capability. The HMC is intended to provide the computing power necessary to diagnose selected anomalous engine behaviors and for making recommendations to the engine controller for anomaly mitigation. Independent auditors have assessed the reduction in Shuttle ascent risk to be on the order of 40% with the combined system and a three times improvement in mission success.

Davidson, Matt↗

The Systems Engineering Process for Human Support Technology Development

Systems engineering is designing and optimizing systems. This paper reviews the systems engineering process and indicates how it can be applied in the development of advanced human support systems. Systems engineering develops the performance requirements, subsystem specifications, and detailed designs needed to construct a desired system. Systems design is difficult, requiring both art and science and balancing human and technical considerations. The essential systems engineering activity is trading off and compromising between competing objectives such as performance and cost, schedule and risk. Systems engineering is not a complete independent process. It usually supports a system development project. This review emphasizes the NASA project management process as described in NASA Procedural Requirement (NPR) 7120.5B. The process is a top down phased approach that includes the most fundamental activities of systems engineering - requirements definition, systems analysis, and design. NPR 7120.5B also requires projects to perform the engineering analyses needed to ensure that the system will operate correctly with regard to reliability, safety, risk, cost, and human factors. We review the system development project process, the standard systems engineering design methodology, and some of the specialized systems analysis techniques. We will discuss how they could apply to advanced human support systems development. The purpose of advanced systems development is not directly to supply human space flight hardware, but rather to provide superior candidate systems that will be selected for implementation by future missions. The most direct application of systems engineering is in guiding the development of prototype and flight experiment hardware. However, anticipatory systems engineering of possible future flight systems would be useful in identifying the most promising development projects.

Jones, Harry↗

Rocket Engine Numerical Simulator (RENS)

Work is being done at three universities to help today's NASA engineers use the knowledge and experience of their Apolloera predecessors in designing liquid rocket engines. Ground-breaking work is being done in important subject areas to create a prototype of the most important functions for the Rocket Engine Numerical Simulator (RENS). The goal of RENS is to develop an interactive, realtime application that engineers can utilize for comprehensive preliminary propulsion system design functions. RENS will employ computer science and artificial intelligence research in knowledge acquisition, computer code parallelization and objectification, expert system architecture design, and object-oriented programming. In 1995, a 3year grant from the NASA Lewis Research Center was awarded to Dr. Douglas Moreman and Dr. John Dyer of Southern University at Baton Rouge, Louisiana, to begin acquiring knowledge in liquid rocket propulsion systems. Resources of the University of West Florida in Pensacola were enlisted to begin the process of enlisting knowledge from senior NASA engineers who are recognized experts in liquid rocket engine propulsion systems. Dr. John Coffey of the University of West Florida is utilizing his expertise in interviewing and concept mapping techniques to encode, classify, and integrate information obtained through personal interviews. The expertise extracted from the NASA engineers has been put into concept maps with supporting textual, audio, graphic, and video material. A fundamental concept map was delivered by the end of the first year of work and the development of maps containing increasing amounts of information is continuing. Find out more information about this work at the Southern University/University of West Florida. In 1996, the Southern University/University of West Florida team conducted a 4day group interview with a panel of five experts to discuss failures of the RL10 rocket engine in conjunction with the Centaur launch vehicle. The discussion was recorded on video and audio tape. Transcriptions of the entire proceedings and an abbreviated video presentation of the discussion highlights are under development. Also in 1996, two additional 3year grants were awarded to conduct parallel efforts that would complement the work being done by Southern University and the University of West Florida. Dr. Prem Bhalla of Jackson State University in Jackson, Mississippi, is developing the architectural framework for RENS. By employing the Rose Rational language and Booch Object Oriented Programming (OOP) technology, Dr. Bhalla is developing the basic structure of RENS by identifying and encoding propulsion system components, their individual characteristics, and cross-functionality and dependencies. Dr. Ruknet Cezzar of Hampton University, located in Hampton, Virginia, began working on the parallelization and objectification of rocket engine analysis and design codes. Dr. Cezzar will use the Turbo C++ OOP language to translate important liquid rocket engine computer codes from FORTRAN and permit their inclusion into the RENS framework being developed at Jackson State University. The Southern University/University of West Florida grant was extended by 1 year to coordinate the conclusion of all three efforts in 1999.

Davidian, Kenneth O.↗

Engine-Scale Combustor Rig Designed, Fabricated, and Tested for Combustion Instability Control Research

Low-emission combustor designs are prone to combustor instabilities. Because active control of these instabilities may allow future combustors to meet both stringent emissions and performance requirements, an experimental combustor rig was developed for investigating methods of actively suppressing combustion instabilities. The experimental rig has features similar to a real engine combustor and exhibits instabilities representative of those in aircraft gas turbine engines. Experimental testing in the spring of 1999 demonstrated that the rig can be tuned to closely represent an instability observed in engine tests. Future plans are to develop and demonstrate combustion instability control using this experimental combustor rig. The NASA Glenn Research Center at Lewis Field is leading the Combustion Instability Control program to investigate methods for actively suppressing combustion instabilities. Under this program, a single-nozzle, liquid-fueled research combustor rig was designed, fabricated, and tested. The rig has many of the complexities of a real engine combustor, including an actual fuel nozzle and swirler, dilution cooling, and an effusion-cooled liner. Prior to designing the experimental rig, a survey of aircraft engine combustion instability experience identified an instability observed in a prototype engine as a suitable candidate for replication. The frequency of the instability was 525 Hz, with an amplitude of approximately 1.5-psi peak-to-peak at a burner pressure of 200 psia. The single-nozzle experimental combustor rig was designed to preserve subcomponent lengths, cross sectional area distribution, flow distribution, pressure-drop distribution, temperature distribution, and other factors previously found to be determinants of burner acoustic frequencies, mode shapes, gain, and damping. Analytical models were used to predict the acoustic resonances of both the engine combustor and proposed experiment. The analysis confirmed that the test rig configuration and engine configuration had similar longitudinal acoustic characteristics, increasing the likelihood that the engine instability would be replicated in the rig. Parametric analytical studies were performed to understand the influence of geometry and condition variations and to establish a combustion test plan. Cold-flow experiments verified that the design values of area and flow distributions were obtained. Combustion test results established the existence of a longitudinal combustion instability in the 500-Hz range with a measured amplitude approximating that observed in the engine. Modifications to the rig configuration during testing also showed the potential for injector independence. The research combustor rig was developed in partnership with Pratt & Whitney of West Palm Beach, Florida, and United Technologies Research Center of East Hartford, Connecticut. Experimental testing of the combustor rig took place at United Technologies Research Center.

DeLaat, John C.↗

Parametric (On-Design) Cycle Analysis for a Separate-Exhaust Turbofan Engine With Interstage Turbine Burner

Today s modern aircraft is based on air-breathing jet propulsion systems, which use moving fluids as substances to transform energy carried by the fluids into power. Throughout aero-vehicle evolution, improvements have been made to the engine efficiency and pollutants reduction. The major advantages associated with the addition of ITB are an increase in thermal efficiency and reduction in NOx emission. Lower temperature peak in the main combustor results in lower thermal NOx emission and lower amount of cooling air required. This study focuses on a parametric (on-design) cycle analysis of a dual-spool, separate-flow turbofan engine with an Interstage Turbine Burner (ITB). The ITB considered in this paper is a relatively new concept in modern jet engine propulsion. The ITB serves as a secondary combustor and is located between the high- and the low-pressure turbine, i.e., the transition duct. The objective of this study is to use design parameters, such as flight Mach number, compressor pressure ratio, fan pressure ratio, fan bypass ratio, and high-pressure turbine inlet temperature to obtain engine performance parameters, such as specific thrust and thrust specific fuel consumption. Results of this study can provide guidance in identifying the performance characteristics of various engine components, which can then be used to develop, analyze, integrate, and optimize the system performance of turbofan engines with an ITB. Visual Basic program, Microsoft Excel macrocode, and Microsoft Excel neuron code are used to facilitate Microsoft Excel software to plot engine performance versus engine design parameters. This program computes and plots the data sequentially without forcing users to open other types of plotting programs. A user s manual on how to use the program is also included in this report. Furthermore, this stand-alone program is written in conjunction with an off-design program which is an extension of this study. The computed result of a selected design-point engine will be exported to an engine reference data file that is required in off-design calculation.

Liew, K. H.↗

Development of the Functional Flow Block Diagram for the J-2X Rocket Engine System

The J-2X program calls for the upgrade of the Apollo-era Rocketdyne J-2 engine to higher power levels, using new materials and manufacturing techniques, and with more restrictive safety and reliability requirements than prior human-rated engines in NASA history. Such requirements demand a comprehensive systems engineering effort to ensure success. Pratt & Whitney Rocketdyne system engineers performed a functional analysis of the engine to establish the functional architecture. J-2X functions were captured in six major operational blocks. Each block was divided into sub-blocks or states. In each sub-block, functions necessary to perform each state were determined. A functional engine schematic consistent with the fidelity of the system model was defined for this analysis. The blocks, sub-blocks, and functions were sequentially numbered to differentiate the states in which the function were performed and to indicate the sequence of events. The Engine System was functionally partitioned, to provide separate and unique functional operators. Establishing unique functional operators as work output of the System Architecture process is novel in Liquid Propulsion Engine design. Each functional operator was described such that its unique functionality was identified. The decomposed functions were then allocated to the functional operators both of which were the inputs to the subsystem or component performance specifications. PWR also used a novel approach to identify and map the engine functional requirements to customer-specified functions. The final result was a comprehensive Functional Flow Block Diagram (FFBD) for the J-2X Engine System, decomposed to the component level and mapped to all functional requirements. This FFBD greatly facilitates component specification development, providing a well-defined trade space for functional trades at the subsystem and component level. It also provides a framework for function-based failure modes and effects analysis (FMEA), and a rigorous baseline for the functional architecture.

White, Thomas↗

Method of vibration isolating an aircraft engine

A method for coupling an engine to a support frame for mounting to a fuselage of an aircraft using a three point vibration isolating mounting system in which the load reactive forces at each mounting point are statically and dynamically determined. A first vibration isolating mount pivotably couples a first end of an elongated support beam to a stator portion of an engine with the pivoting action of the vibration mount being oriented such that it is pivotable about a line parallel to a center line of the engine. An aft end of the supporting frame is coupled to the engine through an additional pair of vibration isolating mounts with the mounts being oriented such that they are pivotable about a circumference of the engine. The aft mounts are symmetrically spaced to each side of the supporting frame by 45 degrees. The relative orientation between the front mount and the pair of rear mounts is such that only the rear mounts provide load reactive forces parallel to the engine center line, in support of the engine to the aircraft against thrust forces. The forward mount is oriented so as to provide only radial forces to the engine and some lifting forces to maintain the engine in position adjacent a fuselage. Since each mount is connected to provide specific forces to support the engine, forces required of each mount are statically and dynamically determinable.

Bender, Stanley I.↗

Emergency flight control system using one engine and fuel transfer

A system for emergency aircraft control uses at least one engine and lateral fuel transfer that allows a pilot to regain control over an aircraft under emergency conditions. Where aircraft propulsion is available only through engines on one side of the aircraft, lateral fuel transfer provides means by which the center of gravity of the aircraft can be moved over to the wing associated with the operating engine, thus inducing a moment that balances the moment from the remaining engine, allowing the pilot to regain control over the aircraft. By implementing the present invention in flight control programming associated with a flight control computer (FCC), control of the aircraft under emergency conditions can be linked to the yoke or autopilot knob of the aircraft. Additionally, the center of gravity of the aircraft can be shifted in order to effect maneuvers and turns by spacing such center of gravity either closer to or farther away from the propelling engine or engines. In an alternative embodiment, aircraft having a third engine associated with the tail section or otherwise are accommodated and implemented by the present invention by appropriately shifting the center of gravity of the aircraft. Alternatively, where a four-engine aircraft has suffered loss of engine control on one side of the plane, the lateral fuel transfer may deliver the center of gravity closer to the two remaining engines. Differential thrust between the two can then control the pitch and roll of the aircraft in conjunction with lateral fuel transfer.

Burcham, Jr., Frank W.↗

Environmental Testing of the NEXT PM1R Ion Engine

The NEXT propulsion system is an advanced ion propulsion system presently under development that is oriented towards robotic exploration of the solar system using solar electric power. The subsystem includes an ion engine, power processing unit, feed system components, and thruster gimbal. The Prototype Model engine PM1 was subjected to qualification-level environmental testing in 2006 to demonstrate compatibility with environments representative of anticipated mission requirements. Although the testing was largely successful, several issues were identified including the fragmentation of potting cement on the discharge and neutralizer cathode heater terminations during vibration which led to abbreviated thermal testing, and generation of particulate contamination from manufacturing processes and engine materials. The engine was reworked to address most of these findings, renamed PM1R, and the environmental test sequence was repeated. Thruster functional testing was performed before and after the vibration and thermal-vacuum tests. Random vibration testing, conducted with the thruster mated to the breadboard gimbal, was executed at 10.0 Grms for 2 min in each of three axes. Thermal-vacuum testing included three thermal cycles from 120 to 215 C with hot engine re-starts. Thruster performance was nominal throughout the test program, with minor variations in a few engine operating parameters likely caused by facility effects. There were no significant changes in engine performance as characterized by engine operating parameters, ion optics performance measurements, and beam current density measurements, indicating no significant changes to the hardware as a result of the environmental testing. The NEXT PM1R engine and the breadboard gimbal were found to be well-designed against environmental requirements based on the results reported herein. The redesigned cathode heater terminations successfully survived the vibration environments. Based on the results of this test program and confidence in the engineering solutions available for the remaining findings of the first test program, specifically the particulate contamination, the hardware environmental qualification program can proceed with confidence

Snyder, John S.↗

Sense and Sensibility: The Case for the Nationwide Inclusion of Engineering in the K-12 Curriculum

The competitive status of the United States is inextricably linked to innovation just as innovation is inseparable from science, technology, engineering, and mathematics. To stay competitive in innovation requires that the United States produce a 21st century workforce complete with requisite education, training, skills, and motivation. If we accept a priori that science, technology, engineering, and mathematics education are crucial to competitiveness and innovation and that, in terms of innovation, mathematics, science, and engineering are interdependent, why are mathematics and science uniformly ubiquitous in the K-12 curriculum while engineering is conspicuously absent? We are passionate in our belief that the uniform addition of engineering to the K-12 curriculum will help ensure that the nation has "the right" 21st Century workforce. Furthermore, we believe that a nationwide effort, led by a coalition of engineering academics, practitioners, and societies is required to turn this goal into reality. However, accomplishing this goal necessitates, as we are reminded by the title of Jane Austen's timeless novel, "Sense and Sensibility", a workable solution that seeks the "middle ground" between passion and reason. We begin our paper by making two essential points: Engineers are not scientists. Engineering exists separate from science, has its own specialized knowledge community apart from science, and it is largely responsible for many of the most significant advancements and improvements in the quality of our life. Our workable solution requires that K-12 education, nationwide, accommodate the inclusion of engineering as a stand alone curriculum and we offer three reasons to support our position: (1) workforce development, (2) stimulating interest in STEM (science, technology, engineering, and mathematics) courses and careers, and (3) creating a technologically literate society. We conclude with some thoughts on how this important goal can be accomplished.

Lindberg, Robert E.↗

Testing for the J-2X Upper Stage Engine

NASA selected the J-2X Upper Stage Engine in 2006 to power the upper stages of the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Based on the proven Saturn J-2 engine, this new engine will provide 294,000 pounds of thrust and a specific impulse of 448 seconds, making it the most efficient gas generator cycle engine in history. The engine's guiding philosophy emerged from the Exploration Systems Architecture Study (ESAS) in 2005. Goals established then called for vehicles and components based, where feasible, on proven hardware from the Space Shuttle, commercial, and other programs, to perform the mission and provide an order of magnitude greater safety. Since that time, the team has made unprecedented progress. Ahead of the other elements of the Constellation Program architecture, the team has progressed through System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of February 2010, more than 100,000 development engine parts have been ordered and more than 18,000 delivered. Approximately 1,300 of more than 1,600 engine drawings were released for manufacturing. A major factor in the J-2X development approach to this point is testing operations of heritage J-2 engine hardware and new J-2X components to understand heritage performance, validate computer modeling of development components, mitigate risk early in development, and inform design trades. This testing has been performed both by NASA and its J-2X prime contractor, Pratt & Whitney Rocketdyne (PWR). This body of work increases the likelihood of success as the team prepares for testing the J-2X powerpack and first development engine in calendar 2011. This paper will provide highlights of J-2X testing operations, engine test facilities, development hardware, and plans.

Buzzell, James C.↗

From Paper to Production: An Update on NASA's Upper Stage Engine for Exploration

In 2006, NASA selected an evolved variant of the proven Saturn/Apollo J-2 upper stage engine to power the Ares I crew launch vehicle upper stage and the Ares V cargo launch vehicle Earth departure stage (EDS) for the Constellation Program. Any design changes needed by the new engine would be based where possible on proven hardware from the Space Shuttle, commercial launchers, and other programs. In addition to the thrust and efficiency requirements needed for the Constellation reference missions, it would be an order of magnitude safer than past engines. It required the J-2X government/industry team to develop the highest performance engine of its type in history and develop it for use in two vehicles for two different missions. In the attempt to achieve these goals in the past five years, the Upper Stage Engine team has made significant progress, successfully passing System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of spring 2010, more than 100,000 experimental and development engine parts have been completed or are in various stages of manufacture. Approximately 1,300 of more than 1,600 engine drawings have been released for manufacturing. This progress has been due to a combination of factors: the heritage hardware starting point, advanced computer analysis, and early heritage and development component testing to understand performance, validate computer modeling, and inform design trades. This work will increase the odds of success as engine team prepares for powerpack and development engine hot fire testing in calendar 2011. This paper will provide an overview of the engine development program and progress to date.

Kynard, Mike↗

Optimal Tuner Selection for Kalman-Filter-Based Aircraft Engine Performance Estimation

An emerging approach in the field of aircraft engine controls and system health management is the inclusion of real-time, onboard models for the inflight estimation of engine performance variations. This technology, typically based on Kalman-filter concepts, enables the estimation of unmeasured engine performance parameters that can be directly utilized by controls, prognostics, and health-management applications. A challenge that complicates this practice is the fact that an aircraft engine s performance is affected by its level of degradation, generally described in terms of unmeasurable health parameters such as efficiencies and flow capacities related to each major engine module. Through Kalman-filter-based estimation techniques, the level of engine performance degradation can be estimated, given that there are at least as many sensors as health parameters to be estimated. However, in an aircraft engine, the number of sensors available is typically less than the number of health parameters, presenting an under-determined estimation problem. A common approach to address this shortcoming is to estimate a subset of the health parameters, referred to as model tuning parameters. The problem/objective is to optimally select the model tuning parameters to minimize Kalman-filterbased estimation error. A tuner selection technique has been developed that specifically addresses the under-determined estimation problem, where there are more unknown parameters than available sensor measurements. A systematic approach is applied to produce a model tuning parameter vector of appropriate dimension to enable estimation by a Kalman filter, while minimizing the estimation error in the parameters of interest. Tuning parameter selection is performed using a multi-variable iterative search routine that seeks to minimize the theoretical mean-squared estimation error of the Kalman filter. This approach can significantly reduce the error in onboard aircraft engine parameter estimation applications such as model-based diagnostic, controls, and life usage calculations. The advantage of the innovation is the significant reduction in estimation errors that it can provide relative to the conventional approach of selecting a subset of health parameters to serve as the model tuning parameter vector. Because this technique needs only to be performed during the system design process, it places no additional computation burden on the onboard Kalman filter implementation. The technique has been developed for aircraft engine onboard estimation applications, as this application typically presents an under-determined estimation problem. However, this generic technique could be applied to other industries using gas turbine engine technology.

Simon, Donald L.↗

Space Shuttle Main Engine - The Relentless Pursuit of Improvement

The Space Shuttle Main Engine (SSME) is the only reusable large liquid rocket engine ever developed. The specific impulse delivered by the staged combustion cycle, substantially higher than previous rocket engines, minimized volume and weight for the integrated vehicle. The dual pre-burner configuration permitted precise mixture ratio and thrust control while the fully redundant controller and avionics provided a very high degree of system reliability and health diagnosis. The main engine controller design was the first rocket engine application to incorporate digital processing. The engine was required to operate at a high chamber pressure to minimize engine volume and weight. Power level throttling was required to minimize structural loads on the vehicle early in flight and acceleration levels on the crew late in ascent. Fatigue capability, strength, ease of assembly and disassembly, inspectability, and materials compatibility were all major considerations in achieving a fully reusable design. During the multi-decade program the design evolved substantially using a series of block upgrades. A number of materials and manufacturing challenges were encountered throughout SSME s history. Significant development was required for the final configuration of the high pressure turbopumps. Fracture control was implemented to assess life limits of critical materials and components. Survival in the hydrogen environment required assessment of hydrogen embrittlement. Instrumentation systems were a challenge due to the harsh thermal and dynamic environments within the engine. Extensive inspection procedures were developed to assess the engine components between flights. The Space Shuttle Main Engine achieved a remarkable flight performance record. All flights were successful with only one mission requiring an ascent abort condition, which still resulted in an acceptable orbit and mission. This was achieved in large part via extensive ground testing to fully characterize performance and to establish acceptable life limits. During the program over a million seconds of accumulated test and flight time was achieved. Post flight inspection and assessment was a key part of assuring proper performance of the flight hardware. By the end of the program the predicted reliability had improved by a factor of four. These unique challenges, evolution of the design, and the resulting reliability will be discussed in this paper.

VanHooser, Katherine P.↗

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

Interdisciplinary Interactions During R&D and Early Design of Large Engineered Systems

Designing Large-Scale Complex Engineered Systems (LaCES) such as aircraft and submarines requires the input of thousands of engineers and scientists whose work is proximate in neither time nor space. Comprehensive knowledge of the system is dispersed among specialists whose expertise is in typically one system component or discipline. This study examined the interactive work practices among such specialists seeking to improve engineering practice through a rigorous and theoretical understanding of current practice. This research explored current interdisciplinary practices and perspectives during R&D and early LaCES design and identified why these practices and perspectives prevail and persist. The research design consisted of a three-fold, integrative approach that combined an open-ended survey, semi-structured interviews, and ethnography. Significant empirical data from experienced engineers and scientists in a large engineering organization were obtained and integrated with theories from organization science and engineering. Qualitative analysis was used to obtain a holistic, contextualized understanding. The over-arching finding is that issues related to cognition, organization, and social interrelations mostly dominate interactions across disciplines. Engineering issues, such as the integration of hardware or physics-based models, are not as significant. For example, organization culture is an important underlying factor that guided researchers more toward individual sovereignty over cross-disciplinarity. The organization structure and the engineered system architecture also serve as constraints to the engineering work. Many differences in work practices were observed, including frequency and depth of interactions, definition or co-construction of requirements, clarity or creation of the system architecture, work group proximity, and cognitive challenges. Practitioners are often unaware of these differences resulting in confusion and incorrect assumptions regarding work expectations. Cognitively, the enactment and coconstruction of knowledge are the fundamental tasks of the interdisciplinary interactions. Distributed and collective cognition represent most of the efforts. Argument, ignorance, learning, and creativity are interrelated aspects of the interactions that cause discomfort but yield benefits such as problem mitigation, broader understanding, and improved system design and performance. The quality and quantity of social interrelations are central to all work across disciplines with reciprocity, respectful engagement, and heedful interrelations being significant to the effectiveness of the engineering and scientific work.

McGowan, Anna-Maria Rivas↗

Combustion Stability Characteristics of the Project Morpheus Liquid Oxygen/Liquid Methane Main Engine

The Project Morpheus liquid oxygen (LOX) / liquid methane rocket engines demonstrated acousticcoupled combustion instabilities during sea‐level ground‐based testing at the NASA Johnson Space Center (JSC) and Stennis Space Center (SSC). High‐amplitude, 1T, 1R, 1T1R (and higher order) modes appear to be triggered by injector conditions. The instability occurred during the Morpheus‐specific engine ignition/start sequence, and did demonstrate the capability to propagate into mainstage. However, the instability was never observed to initiate during mainstage, even at low power levels. The Morpheus main engine is a JSC‐designed ~5,000 lbf‐thrust, 4:1 throttling, pressure‐fed cryogenic engine using an impinging element injector design. Two different engine designs, named HD4 and HD5, and two different builds of the HD4 engine all demonstrated similar instability characteristics. Through the analysis of more than 200 hot fire tests on the Morpheus vehicle and SSC test stand, a relationship between ignition stability and injector/chamber pressure was developed. The instability has the distinct characteristic of initiating at high relative injection pressure drop (dP) at low chamber pressure (Pc); i.e., instabilities initiated at high dP/Pc at low Pc during the start sequence. The high dP/Pc during start results during the injector /chamber chill‐in, and is enhanced by hydraulic flip in the injector orifice elements. Because of the fixed mixture ratio of the existing engine design (the main valves share a common actuator), it is not currently possible to determine if LOX or methane injector dP/Pc were individual contributors (i.e., LOX and methane dP/Pc typically trend in the same direction within a given test). The instability demonstrated initiation characteristic of starting at or shortly after methane injector chillin. Colder methane (e.g., sub‐cooled) at the injector inlet prior to engine start was much more likely to result in an instability. A secondary effect of LOX sub‐cooling was also possibly observed; greater LOX sub‐ cooling improved stability. Some tests demonstrated a low‐amplitude 1L‐1T instability prior to LOX injector chill‐in. The Morpheus main engine also demonstrated chug instabilities during some engine shutdown sequences on the flight vehicle and SSC test stand. The chug instability was also infrequently observed during the startup sequence. The chug instabilities predictably initiated at low dP/Pc at low Pc. The chug instabilities were always self‐limiting; startup chug instabilities terminated during throttle‐up and shutdown chug instabilities decayed by shutdown termination.

Melcher, J. C.↗