SEARCH · Search NASA
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.
The technology that will improve the energy efficiency of propulsion systems for subsonic commercial aircraft is investigated. A reduction of 14.4% in cruise installed sfc (0.572 versus 0.668 for the CF6-50C) and a direct operation cost reduction in excess of the 5% goal is projected. Noise and emissions projections are consistent with the established goals.
This paper shares the findings of NASA's Integrated Learning and Development Program (ILDP) in its effort to reinvigorate the HANDS-ON practice of space systems engineering and project/program management through focused coursework, training opportunities, on-the job learning and special assignments. Prior to March 2005, NASA responsibility for technical workforce development (the program/project manager, systems engineering, discipline engineering, discipline engineering and associated communities) was executed by two parallel organizations. In March 2005 these organizations merged. The resulting program-ILDP-was chartered to implement an integrated competency-based development model capable of enhancing NASA's technical workforce performance as they face the complex challenges of Earth science, space science, aeronautics and human spaceflight missions. Results developed in collaboration with NASA Field Centers are reported on. This work led to definition of the agency's first integrated technical workforce development model known as the Requisite Occupation Competence and Knowledge (the ROCK). Critical processes and products are presented including: 'validation' techniques to guide model development, the Design-A-CUrriculuM (DACUM) process, and creation of the agency's first systems engineering body-of-knowledge. Findings were validated via nine focus groups from industry and government, validated with over 17 space-related organizations, at an estimated cost exceeding $300,000 (US). Masters-level programs and training programs have evolved to address the needs of these practitioner communities based upon these results. The ROCK reintroduced rigor and depth to the practitioner's development in these critical disciplines enabling their ability to take mission concepts from imagination to reality.
One of the propulsion system concepts to be considered for the High-Speed Civil Transport (HSCT) is an underwing, dual-propulsion, pod-per-wing installation. Adverse transient phenomena such as engine compressor stall and inlet unstart could severely degrade the performance of one of these propulsion pods. The subsequent loss of thrust and increased drag could cause aircraft stability and control problems that could lead to a catastrophic accident if countermeasures are not in place to anticipate and control these detrimental transient events. Aircraft system engineers must understand what happens during an engine compressor stall and inlet unstart so that they can design effective control systems to avoid and/or alleviate the effects of a propulsion pod engine compressor stall and inlet unstart. The objective of the Inlet Unstart Propulsion Airframe Integration test program was to assess the underwing flow field of a High-Speed Civil Transport propulsion system during an engine compressor stall and subsequent inlet unstart. Experimental research testing was conducted in the 10- by 10-Foot Supersonic Wind Tunnel at the NASA Glenn Research Center at Lewis Field. The representative propulsion pod consisted of a two-dimensional, bifurcated inlet mated to a live turbojet engine. The propulsion pod was mounted below a large flat plate that acted as a wing simulator. Because of the plate s long length (nominally 10-ft wide by 18-ft long), realistic boundary layers could form at the inlet cowl plane. Transient instrumentation was used to document the aerodynamic flow-field conditions during an unstart sequence. Acquiring these data was a significant technical challenge because a typical unstart sequence disrupts the local flow field for about only 50 msec. Flow surface information was acquired via static pressure taps installed in the wing simulator, and intrusive pressure probes were used to acquire flow-field information. These data were extensively analyzed to determine the impact of the unstart transient on the surrounding flow field. This wind tunnel test program was a success, and for the first time, researchers acquired flow-field aerodynamic data during a supersonic propulsion system engine compressor stall and inlet unstart sequence. In addition to obtaining flow-field pressure data, Glenn researchers determined other properties such as the transient flow angle and Mach number. Data are still being reduced, and a comprehensive final report will be released during calendar year 2000.
This report summarizes the results of a multi-year training grant for the development and implementation of a Multidisciplinary Design and Analysis (MDA) Fellowship Program at Georgia Tech. The Program funded the creation of graduate MS and PhD degree programs in aerospace systems design, analysis and integration. It also provided prestigious Fellowships with associated Industry Internships for outstanding engineering students. The graduate program has become the foundation for a vigorous and productive research effort and has produced: 20 MS degrees, 7 Ph.D. degrees, and has contributed to 9 ongoing Ph.D. students. The results of the research are documented in 32 publications (23 of which are included on a companion CDROM) and 4 annual student design reports (included on a companion CDROM). The legacy of this critical funding is the Center for Aerospace Systems Analysis at Georgia Tech which is continuing the graduate program, the research, and the industry internships established by this grant.
The pilot study is led by the Integration Engineering group in NASA's Launch Services Program (LSP). The Integration Engineering (IE) group is responsible for managing the interfaces between the spacecraft and launch vehicle. This pilot investigates the utility of Model-Based Systems Engineering (MBSE) with respect to managing and verifying interface requirements. The main objectives of the pilot are to model several key aspects of the Mars 2020 integrated operations and interface requirements based on the design and verification artifacts from Mars Science Laboratory (MSL) and to demonstrate how MBSE could be used by LSP to gain further insight on the interface between the spacecraft and launch vehicle as well as to enhance how LSP manages the launch service. The method used to accomplish this pilot started through familiarization of SysML, MagicDraw, and the Mars 2020 and MSL systems through books, tutorials, and NASA documentation. MSL was chosen as the focus of the model since its processes and verifications translate easily to the Mars 2020 mission. The study was further focused by modeling specialized systems and processes within MSL in order to demonstrate the utility of MBSE for the rest of the mission. The systems chosen were the In-Flight Disconnect (IFD) system and the Mass Properties process. The IFD was chosen as a system of focus since it is an interface between the spacecraft and launch vehicle which can demonstrate the usefulness of MBSE from a system perspective. The Mass Properties process was chosen as a process of focus since the verifications for mass properties occur throughout the lifecycle and can demonstrate the usefulness of MBSE from a multi-discipline perspective. Several iterations of both perspectives have been modeled and evaluated. While the pilot study will continue for another 2 weeks, pros and cons of using MBSE for LSP IE have been identified. A pro of using MBSE includes an integrated view of the disciplines, requirements, and verifications leading up to launch. The model allows IE to understand the relationships between disciplines throughout test activities and verifications. Additionally, the relationships between disciplines and integration tasks are generally consistent. The model allows for the generic relationships and tasks to be captured and used throughout multiple mission models should LSP further pursue MBSE. A con of MBSE is the amount of time it takes upfront to understand MBSE and create a useful model. The upfront time it takes to create a useful model is heavily discussed in MBSE literature and is a consistent con throughout the known applications of MBSE. The need to understand SysML and the software chosen also poses the possibility of a "bottleneck" or one person being the sole MBSE user for the working group. The utility of MBSE will continue to be evaluated through the remainder of the study. In conclusion, the original objectives of the pilot study were to use artifacts from MSL to model key aspects of Mars 2020 and demonstrate how MBSE could be used by LSP to gain insight into the spacecraft and launch vehicle interfaces. Progress has been made in modeling and identifying the utility of MBSE to LSP IE and will continue to be made until the pilot study's conclusion in mid-August. The results of this study will produce initial models, modeling instructions and examples, and a summary of MBSE's utility for future use by LSP.
The Space Transportation Propulsion Technology Symposium was held at the Pennsylvania State University on June 25 to 29, 1990. Emphasis was placed on propulsion requirements and initiatives to support current, next generation, and future space transportation systems, with the primary objectives of discerning whether proposed designs truly meet future transportation needs and identifying possible technology gaps, overlaps and other programmatic deficiencies. Key space transportation propulsion issues are addressed through four panels with government, industry, and academia membership. The panel focused on systems engineering and integration; development, manufacturing, and certification; operational efficiency; program development; and cultural issues.
Future aircraft turbine engines, both commercial and military, must be able to accommodate expected increased levels of steady-state and dynamic engine-face distortion. The current approach of incorporating sufficient design stall margin to tolerate these increased levels of distortion would significantly reduce performance. The High Stability Engine Control (HISTEC) program has developed technologies for an advanced, integrated engine control system that uses measurement- based estimates of distortion to enhance engine stability. The resulting distortion tolerant control reduces the required design stall margin, with a corresponding increase in performance and/or decrease in fuel burn. The HISTEC concept was successfully flight demonstrated on the F-15 ACTIVE aircraft during the summer of 1997. The flight demonstration was planned and carried out in two parts, the first to show distortion estimation, and the second to show distortion accommodation. Post-flight analysis shows that the HISTEC technologies are able to successfully estimate and accommodate distortion, transiently setting the stall margin requirement on-line and in real-time. Flight demonstration of the HISTEC technologies has significantly reduced the risk of transitioning the technology to tactical and commercial engines.
Liftoff debris is a top risk to the Space Shuttle Vehicle. To manage the Liftoff debris risk, the Space Shuttle Program created a team with in the Propulsion Systems Engineering & Integration Office. The Shutt le Liftoff Debris Team harnesses the Systems Engineering process to i dentify, assess, mitigate, and communicate the Liftoff debris risk. T he Liftoff Debris Team leverages off the technical knowledge and expe rtise of engineering groups across multiple NASA centers to integrate total system solutions. These solutions connect the hardware and ana lyses to identify and characterize debris sources and zones contribut ing to the Liftoff debris risk. The solutions incorporate analyses sp anning: the definition and modeling of natural and induced environmen ts; material characterizations; statistical trending analyses, imager y based trajectory analyses; debris transport analyses, and risk asse ssments. The verification and validation of these analyses are bound by conservative assumptions and anchored by testing and flight data. The Liftoff debris risk mitigation is managed through vigilant collab orative work between the Liftoff Debris Team and Launch Pad Operation s personnel and through the management of requirements, interfaces, r isk documentation, configurations, and technical data. Furthermore, o n day of launch, decision analysis is used to apply the wealth of ana lyses to case specific identified risks. This presentation describes how the Liftoff Debris Team applies Systems Engineering in their proce sses to mitigate risk and improve the safety of the Space Shuttle Veh icle.
NASA has been interested in technology development for deep space exploration, and one avenue of developing these technologies is via the eXploration Habitat (X-Hab) Academic Innovation Challenge. In 2013, NASA's Deep Space Habitat (DSH) project was in need of sensors that could monitor the power consumption of various devices in the habitat with added capability to control the power to these devices for load shedding in emergency situations. Texas A&M University's Electronic Systems Engineering Technology Program (ESET) in conjunction with their Mobile Integrated Solutions Laboratory (MISL) accepted this challenge, and over the course of 2013, several undergraduate students in a Capstone design course developed five wireless DC Smart Plugs for NASA. The wireless DC Smart Plugs developed by Texas A&M in conjunction with NASA's Deep Space Habitat team is a first step in developing wireless instrumentation for future flight hardware. This paper will further discuss the X-Hab challenge and requirements set out by NASA, the detailed design and testing performed by Texas A&M, challenges faced by the team and lessons learned, and potential future work on this design.
Aerospace problems are highly multidisciplinary. Four or more major disciplines are involved in analyzing any particular vehicle. Moreover, the choice of implementation technology of various subsystems can lead to a change of leading domain or reformation of the driving equations. An excellent example is the change of expertise required to consider aircraft built from composite or metallic structures, or those propelled by chemical or electrical thrusters. Another example is in the major reconfiguration of handling and stability equations with different control surface configuration (e.g., canards, t-tail v four-post tail). Combinatorial problems are also commonplace anytime that a major system is to be designed. If there are only 5 attributes of a design to consider with 4 different options, this is already 1024 options. Adding just 5 more dimensions to the study explodes the space to over one million. Even generous assumptions like the idea that only 10% of the combinations are physically feasible can only contain the problem for so long. To make matters worse, the simple number of combinations is only the beginning. Combining the issue of trade space size with the need to reformulate the design problem for many of the possibilities makes life exponentially more difficult. Advances in software modeling approaches have led to the development of model-driven architecture. This approach uses the transformation of models into inferred models (e.g. inferred execution traces from state machines) or the skeletons for code generation. When the emphasis on transformation is applied to aerospace, it becomes possible to exploit redundancy in the information specified in multiple domain models into a unified system model. F1urther, it becomes possible to overcome the combinatorial nature of specifying integrated system behavior by manually combining the equations governing a given component technology. Transformations from a system specification combined with a system-analysis mapping specification enable one-click combination of domain analyses. This is a flexibility that has been missing from many engineering codes, which often entangle design specification and physical examination much more than is required to conduct the analysis. This capability has been investigated and cultivated within the DARPA F6 program by a team of JPL and Phoenix Integration engineers building the Adapatable Systems Design and Analysis (ASDA) framework. By embracing system modeling with SysML and the Query-View-Transformation (QVT) language, the ASDA team has been able to build a flexible, easily reconfigurable framework for building up and solving large tradespaces. Examples of application and lessons learned in building the framework will be described in this paper. In addition, the motivation will be laid for various tool vendors to develop open model description standards while being able to maintain competitive advantage through proprietary algorithms and approaches. These standards will also be compared to the underpinnings of model-driven architecture and the OMG standards of the Meta-Object Facility (MOF), SysML, and QVT.
The objectives of NASA's MUST (Multipurpose User-oriented Software Technology) program at Langley Research Center are to cut the cost of producing software which effectively utilizes digital systems for flight research. These objectives will be accomplished by providing an integrated system of support software tools for use throughout the research flight software development process. A description of the overall MUST program and its progress toward the release of a first MUST system will be presented. This release includes: a special interactive user interface, a library of subroutines, assemblers, a compiler, automatic documentation tools, and a test and simulation system.
LibertyWorks®, a subsidiary of Rolls-Royce Corporation, first studied CMC (ceramic matrix composite) exhaust mixers for potential weight benefits in 2008. Oxide CMC potentially offered weight reduction, higher temperature capability, and the ability to fabricate complex-shapes for increased mixing and noise suppression. In 2010, NASA was pursuing the reduction of NOx emissions, fuel burn, and noise from turbine engines in Phase I of the Environmentally Responsible Aviation (ERA) Project (within the Integrated Systems Research Program). ERA subtasks, including those focused on CMC components, were being formulated with the goal of maturing technology from Proof of Concept Validation (Technology Readiness Level 3 (TRL 3)) to System/Subsystem or Prototype Demonstration in a Relevant Environment (TRL 6). LibertyWorks®, a subsidiary of Rolls-Royce Corporation, first studied CMC (ceramic matrix composite) exhaust mixers for potential weight benefits in 2008. Oxide CMC potentially offered weight reduction, higher temperature capability, and the ability to fabricate complex-shapes for increased mixing and noise suppression. In 2010, NASA was pursuing the reduction of NOx emissions, fuel burn, and noise from turbine engines in Phase I of the Environmentally Responsible Aviation (ERA) Project (within the Integrated Systems Research Program). ERA subtasks, including those focused on CMC components, were being formulated with the goal of maturing technology from Proof of Concept Validation (Technology Readiness Level 3 (TRL 3)) to System/Subsystem or Prototype Demonstration in a Relevant Environment (TRL 6). Oxide CMC component at both room and elevated temperatures. A TRL≈5 (Component Validation in a Relevant Environment) was attained and the CMC mixer was cleared for ground testing on a Rolls-Royce AE3007 engine for performance evaluation to achieve TRL 6.
Severe weather events are likely occurrences on the Mississippi Gulf Coast. It is important to rapidly diagnose and mitigate the effects of storms on Stennis Space Center's rocket engine test complex to avoid delays to critical test article programs, reduce costs, and maintain safety. An Integrated Systems Health Management (ISHM) approach and technologies are employed to integrate environmental (weather) monitoring, structural modeling, and the suite of available facility instrumentation to provide information for readiness before storms, rapid initial damage assessment to guide mitigation planning, and then support on-going assurance as repairs are effected and finally support recertification. The system is denominated Katrina Storm Monitoring System (KStorMS). Integrated Systems Health Management (ISHM) describes a comprehensive set of capabilities that provide insight into the behavior the health of a system. Knowing the status of a system allows decision makers to effectively plan and execute their mission. For example, early insight into component degradation and impending failures provides more time to develop work around strategies and more effectively plan for maintenance. Failures of system elements generally occur over time. Information extracted from sensor data, combined with system-wide knowledge bases and methods for information extraction and fusion, inference, and decision making, can be used to detect incipient failures. If failures do occur, it is critical to detect and isolate them, and suggest an appropriate course of action. ISHM enables determining the condition (health) of every element in a complex system-of-systems or SoS (detect anomalies, diagnose causes, predict future anomalies), and provide data, information, and knowledge (DIaK) to control systems for safe and effective operation. ISHM capability is achieved by using a wide range of technologies that enable anomaly detection, diagnostics, prognostics, and advise for control: (1) anomaly detection algorithms and strategies, (2) fusion of DIaK for anomaly detection (model-based, numerical, statistical, empirical, expert-based, qualitative, etc.), (3) diagnostics/prognostics strategies and methods, (4) user interface, (5) advanced control strategies, (6) integration architectures/frameworks, (7) embedding of intelligence. Many of these technologies are mature, and they are being used in the KStorMS. The paper will describe the design, implementation, and operation of the KStorMS; and discuss further evolution to support other needs such as condition-based maintenance (CBM).
Engineers and scientists in the advanced fighter technology integration (AFTI) F-16 program investigated the integration of emerging technologies into an advanced fighter aircraft. AFTI's three major technologies included: flight-crucial digital control, decoupled aircraft flight control, and integration of avionics, flight control, and pilot displays. In addition to investigating improvements in fighter performance, researchers studied the generic problems confronting the designers of highly integrated flight-crucial digital control. An overview is provided of both the advantages and problems of integration digital control systems. Also, an examination of the specification, design, qualification, and flight test life-cycle phase is provided. An overview is given of the fault-tolerant design, multimoded decoupled flight control laws, and integrated avionics design. The approach to qualifying the software and system designs is discussed, and the effects of design choices on system qualification are highlighted.
Integrated Analysis Capability (IAC) software system intended to provide highly effective, interactive analysis tool for integrated design of large structures. Supports needs of engineering analysis groups concerned with interdisciplinary problems. Developed to serve as software interface between computer programs from fields of structures, thermodynamics, controls, and dynamics of systems on one hand and executive software system and data base on other hand to yield highly efficient multi-disciplinary system. Special attention given to such users' requirements as handling data and online assistance with operational features and ability to add new modules of user's choice at future date. Written in FORTRAN 77.
The capabilities and design approach of the MIDAS (Man-machine Integration Design and Analysis System) computer-aided engineering (CAE) workstation under development by the Army-NASA Aircrew/Aircraft Integration Program is detailed. This workstation uses graphic, symbolic, and numeric prototyping tools and human performance models as part of an integrated design/analysis environment for crewstation human engineering. Developed incrementally, the requirements and design for Phase 3 (Dec. 1987 to Jun. 1989) are described. Software tools/models developed or significantly modified during this phase included: an interactive 3-D graphic cockpit design editor; multiple-perspective graphic views to observe simulation scenarios; symbolic methods to model the mission decomposition, equipment functions, pilot tasking and loading, as well as control the simulation; a 3-D dynamic anthropometric model; an intermachine communications package; and a training assessment component. These components were successfully used during Phase 3 to demonstrate the complex interactions and human engineering findings involved with a proposed cockpit communications design change in a simulated AH-64A Apache helicopter/mission that maps to empirical data from a similar study and AH-1 Cobra flight test.
An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.
An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).