Evolving Ground System Engineering Practices to Meet the Needs of Future Space Missions
No abstract available
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.
No abstract available
A study was performed to develop a fluid system design and show the feasibility of constructing an integrated modular engine (IME) configuration, using an expander cycle engine. The primary design goal of the IME configuration was to improve the propulsion system reliability. The IME fluid system was designed as a single fault tolerant system, while minimizing the required fluid components. This study addresses the design of the high pressure manifolds, turbopumps and thrust chambers for the IME configuration. A physical layout drawing was made, which located each of the fluid system components, manifolds and thrust chambers. Finally, a comparison was made between the fluid system designs of an IME system and a non-network (clustered) engine system.
Excavation will hold a key role for future lunar missions. NASA has stated that "advances in lunar regolith mining have the potential to significantly contribute to our nation's space vision and NASA space exploration operations." [1]. The Lunabotics Mining Competition is an event hosted by NASA that is meant to encourage "the development of innovative lunar excavation concepts from universities which may result in clever ideas and solutions which could be applied to an actual lunar excavation device or payload." [2]. Teams entering the competition must "design and build a remote controlled or autonomous excavator, called a lunabot, that can collect and deposit a minimum of 10 kilograms of lunar simulant within 10 minutes." [2]. While excavation will play an important part in lunar missions, there will still be many other tasks that would benefit from robotic assistance. An excavator might not be as well suited for these tasks as other types of robots might be. For example a lightweight rover would do well with reconnaissance, and a mobile gripper arm would be fit for manipulation, while an excavator would be comparatively clumsy and slow in both cases. Even within the realm of excavation it would be beneficial to have different types of excavators for different tasks, as there are on Earth. The Alabama Lunabotics Team at the University of Alabama has made it their goal to not only design and build a robot that could compete in the Lunabotics Mining Competition, but would also be a multipurpose tool for future NASA missions. The 2010-2011 resulting robot was named the Modular Omnidirectional Lunar Excavator (MOLE). Using the Systems Engineering process and building off of two years of Lunabotics experience, the 20ll-2012 Alabama Lunabotics team (Team NASACAR) has improved the MOLE 1.0 design and optimized it for the 2012 Lunabotics Competition rules [I]. A CAD model of MOLE 2.0 can be seen below in Fig. 1.
The objectives of this program were to develop health monitoring systems and physics-based fault detection models for engine sub-systems including the start, lubrication, and fuel. These models will ultimately be used to provide more effective sub-system fault identification and isolation to reduce engine maintenance costs and engine down-time. Additionally, the bearing sub-system health is addressed in this program through identification of sensing requirements, a review of available technologies and a demonstration of a demonstration of a conceptual monitoring system for a differential roller bearing. This report is divided into four sections; one for each of the subtasks. The start system subtask is documented in section 2.0, the oil system is covered in section 3.0, bearing in section 4.0, and the fuel system is presented in section 5.0.
NASA's Space Launch System (SLS) is being developed with the primary purpose of returning people to the Moon and eventually landing people on Mars. With these lofty goals, ensuring mission completion is paramount even in the event of an in-flight mishap. One possible mishap is the loss of an engine in flight. While SLS was not required to show full engine out capability, the program took an ``assess to'' approach to see when the launch vehicle could complete the mission after an engine failure versus when the launch vehicle targets required a down-mode to an alternate mission target to ensure at least some flight objectives were complete, or at a minimum ensure safe return of Orion and the Crew. While this paper will focus on Artemis I, an uncrewed mission, some comparisons will be made to how the engine out capability will change for the subsequent Crewed flights of SLS and Orion.
Current full-scale engine development programs are discussed, and efforts to improve the available technology base are presented. The Lewis full-scale engine test facilities are described. Several typical engine programs and plans for research in aeromechanical instability or flutter are summarized. An overview of Lewis studies of flow distortion and its effects on engine stability is presented. The origins and nature of the distortion problem are summarized, and some of the results and methods for both steady and time-varying distortions are discussed.
An important part of rocket engine design is the calculation of random dynamic loads resulting from internal engine "self-induced" sources. These loads are random in nature and can greatly influence the weight of many engine components. Several methodologies for calculating random loads are discussed and then compared to test results using a dynamic testbed consisting of a 60K thrust engine. The engine was tested in a free-free condition with known random force inputs from shakers attached to three locations near the main noise sources on the engine. Accelerations and strains were measured at several critical locations on the engines and then compared to the analytical results using two different random response methodologies.
Recent results using the Aestus engine operated with LOx/ethanol propellant are presented. An experimental program at Rocketdyne Propulsion and Power is underway to adapt this engine for the Boeing Reusable Space Systems Division non-toxic Orbital Maneuvering System/Reaction control System (OMS/RCS) system. Daimler-Chrysler Aerospace designed the Aestus as an nitrogen tetroxide/monomethyl hydrazine (NTO/MMH) upper-stage engine for the Ariane 5. The non-toxic OMS/RCS system's preliminary design requires a LOx/ethanol (O2/C2H5OH) engine that operates with a mixture ratio of 1.8, a specific impulse of 323 seconds, and fits within the original OMS design envelope. This paper describes current efforts to meet these requirements including, investigating engine performance using LOx/ethanol, developing the en-ine system sizing package, and meeting the vehicle operation parameters. Data from hot-fire testing are also presented and discussed.
AS9100 has little to say about how to apply a Quality Management System (QMS) to aerospace test programs. There is little in the quality engineering Body of Knowledge that applies to testing, unless it is nondestructive examination or some type of lab or bench testing. If one examines how the systems engineering processes are implemented throughout a test program; and how these processes can be mapped to AS9100, a number of areas for involvement of the quality professional are revealed.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
The results are presented of an investigation of the factors which affect the determination of Spacelab (S/L) minimum interface main dc voltage and available power from the orbiter. The dedicated fuel cell mode of powering the S/L is examined along with the minimum S/L interface voltage and available power using the predicted fuel cell power plant performance curves. The values obtained are slightly lower than current estimates and represent a more marginal operating condition than previously estimated.
Program enables proof-of-concepts tests of expert systems under development. AESOP is rule-based inference engine for expert system, which makes decisions about particular situation given user-supplied hypotheses, rules, and answers to questions drawn from rules. If knowledge base containing hypotheses and rules governing environment is available to AESOP, almost any situation within that environment resolved by answering questions asked by AESOP. Questions answered with YES, NO, MAYBE, DON'T KNOW, DON'T CARE, or with probability factor ranging from 0 to 10. AESOP written in Franz LISP for interactive execution.
Ares is an integral part of NASA s Constellation architecture that will provide crew and cargo access to the International Space Station as well as low earth orbit support for lunar missions. Ares replaces the Space Shuttle in the post 2010 time frame. Ares I is an in-line, two-stage rocket topped by the Orion Crew Exploration Vehicle, its service module, and a launch abort system. The Ares I first stage is a single, five-segment reusable solid rocket booster derived from the Space Shuttle Program's reusable solid rocket motor. The Ares second or upper stage is propelled by a J-2X main engine fueled with liquid oxygen and liquid hydrogen. This paper describes the advanced systems engineering and planning tools being utilized for the design, test, and qualification of the Ares I first stage element. Included are descriptions of the current first stage design, the milestone schedule requirements, and the marriage of systems engineering, detailed planning efforts, and roadmapping employed to achieve these goals.
The overall requirements necessary for sensing bearing distress and the related criteria to select a particular rotating sensor were established during the phase I. The current phase II efforts performed studies to evaluate the Robustness and Durability Enhancement of the rotating sensors, and to design, and develop the Built-in Telemetry System concepts for an aircraft engine differential sump. A generic test vehicle that can test the proposed bearing diagnostic system was designed, developed, and built. The Timken Company, who also assisted with testing the GE concept of using rotating sensors for the differential bearing diagnostics during previous phase, was selected as a subcontractor to assist General Electric (GE) for the design, and procurement of the test vehicle. A purchase order was prepared to define the different sub-tasks, and deliverables for this task. The University of Akron was selected to provide the necessary support for installing, and integrating the test vehicle with their newly designed test facility capable of simulating the operating environment for the planned testing. The planned testing with good and damaged bearings will be on hold pending further continuation of this effort during next phase.
Explore the source record for details and available documents.
The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.