SEARCH · Engineering Papers
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.
This presentation highlights the history of DELMIA at MSFC; provides an overview of the Constellation Program; examines the manufacturing of Ares 1 Upper Stage; explains the digital manufacturing implementation for Ares 1 Upper Stage; and, discusses manufacturing and development problems and challenges.
This presentation considers the use of new launch vehicles in defense against near-Earth objects, building upon expertise in launch vehicle and spacecraft design, astronomy and planetary science and missile defense. This work also seeks to demonstrate the synergy needed between architectures for human/robotic exploration initiatives and planetary defense. Three different mitigation operations were baselined for this study--nuclear standoff explosion, kinetic interceptor, and solar collector--however, these are not the only viable options. The design and predicted performance of each of these methods is discussed and compared. It is determined that the nuclear interceptor option can deflect NEOs of smaller size (100-500 m) with 2 years or more time before impact, and larger NEOs with 5 or more years warning; kinetic interceptors may be effective for deflection of asteroids up to 300-400 m but require 8-10 years warning time; and, solar collectors may be able to deflect NEOs up to 1 km if issues pertaining to long operation can be overcome. Ares I and Ares V vehicles show sufficient performance to enable the development of a near-term categorization and mitigation architecture.
The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt and Whitney Rocketdyne Company (PWR) as the upper stage engine (USE). The J-2X is an improved higher power version of the original J-2 engine used for Apollo. System Engineering (SE) facilitates direct and open discussions of issues and problems. This simple idea is often overlooked in large, complex engineering development programs. Definition and distribution of requirements from the engine level to the component level is controlled by Allocation Reports which breaks down numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements help eliminate redundancy and potential mistakes inherent in separated systems. Another tool, the Architecture Design Description (ADD), is used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof of an effective process is in successful program accomplishment. SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. This paper describes the simple, better SE tools and techniques used to achieve this success.
The Exploration Supply Chain Simulation project was chartered by the NASA Exploration Systems Mission Directorate to develop a software tool, with proper data, to quantitatively analyze supply chains for future program planning. This tool is a discrete-event simulation that uses the basic supply chain concepts of planning, sourcing, making, delivering, and returning. This supply chain perspective is combined with other discrete or continuous simulation factors. Discrete resource events (such as launch or delivery reviews) are represented as organizational functional units. Continuous resources (such as civil service or contractor program functions) are defined as enabling functional units. Concepts of fixed and variable costs are included in the model to allow the discrete events to interact with cost calculations. The definition file is intrinsic to the model, but a blank start can be initiated at any time. The current definition file is an Orion Ares I crew launch vehicle. Parameters stretch from Kennedy Space Center across and into other program entities (Michaud Assembly Facility, Aliant Techsystems, Stennis Space Center, Johnson Space Center, etc.) though these will only gain detail as the file continues to evolve. The Orion Ares I file definition in the tool continues to evolve, and analysis from this tool is expected in 2008. This is the first application of such business-driven modeling to a NASA/government-- aerospace contractor endeavor.
A SALT effort was initiated in late 2005 with seed funding from the Office of Safety and Mission Assurance Human Factors organization. Its objectives included demonstrating human behavior and performance modeling and simulation technologies for launch team analysis, training, and evaluation. The goal of the research is to improve future NASA operations and training. The project employed an iterative approach, with the first iteration focusing on the last 70 minutes of a nominal-case Space Shuttle countdown, the second iteration focusing on aborts and launch commit criteria violations, the third iteration focusing on Ares I-X communications, and the fourth iteration focusing on Ares I-X Firing Room configurations. SALT applied new commercial off-the-shelf technologies from industry and the Department of Defense in the spaceport domain.
LLEGO is a model for understanding recurring launch and landing operations costs at Kennedy Space Center for human space flight. Launch and landing operations are often referred to as ground processing, or ground operations. Currently, this function is specific to the ground operations for the Space Shuttle Space Transportation System within the Space Shuttle Program. The Constellation system to follow the Space Shuttle consists of the crewed Orion spacecraft atop an Ares I launch vehicle and the uncrewed Ares V cargo launch vehicle. The Constellation flight and ground systems build upon many elements of the existing Shuttle flight and ground hardware, as well as upon existing organizations and processes. In turn, the LLEGO model builds upon past ground operations research, modeling, data, and experience in estimating for future programs. Rather than to simply provide estimates, the LLEGO model s main purpose is to improve expenses by relating complex relationships among functions (ground operations contractor, subcontractors, civil service technical, center management, operations, etc.) to tangible drivers. Drivers include flight system complexity and reliability, as well as operations and supply chain management processes and technology. Together these factors define the operability and potential improvements for any future system, from the most direct to the least direct expenses.
The ATK Launch Vehicle (ALV-X1) provided an opportunity to measure liftoff acoustic noise data. NASA Marshall Space Flight Center (MSFC) engineers were interested in the ALV-X1 launch because the First Stage motor and launch pad conditions, including a relativity short deflector ducting, provide a potential analogue to future Ares I launches. This paper presents the measured liftoff acoustics on the vehicle and tower. Those measured results are compared to predictions based upon the method described in NASA SP-8072 "Acoustic Loads Generated by the Propulsion System" and the Vehicle Acoustic Environment Prediction Program (VAEPP) which was developed by MSFC acoustics engineers. One-third octave band sound pressure levels will be presented. This data is useful for the ALV-X1 in validating the pre-launch environments and loads predictions. Additionally, the ALV-X1 liftoff data can be scaled to define liftoff environments for the NASA Constellation program Ares vehicles. Vehicle liftoff noise is caused by the supersonic jet flow interaction with surrounding atmosphere or more simply, jet noise. As the vehicle's First Stage motor is ignited, an acoustic noise field is generated by the exhaust. This noise field persists due to the supersonic jet noise and reflections from the launch pad and tower, then changes as the vehicle begins to liftoff from the launch pad. Depending on launch pad and adjacent tower configurations, the liftoff noise is generally very high near the nozzle exit and decreases rapidly away from the nozzle. The liftoff acoustic time range of interest is typically 0 to 20 seconds after ignition. The exhaust plume thermo-fluid mechanics generates sound at approx.10 Hz to 20 kHz. Liftoff acoustic noise is usually the most severe dynamic environment for a launch vehicle or payload in the mid to high frequency range (approx.50 to 2000 Hz). This noise environment can induce high-level vibrations along the external surfaces of the vehicle and surrounding launch facility structures. The acoustic pressure fluctuations will induce severe vibrations in relatively large lightweight structures. Consequently, there is the potential for failure of the structure or attached electrical components. Due to these potential failures, the liftoff acoustic noise is one of the noise source inputs used to determine the vibro-acoustic qualification environment for a launch vehicle and its components.
The engineering phases of design, development, test, and evaluation (DDT and E) and subsequent planning, preparation, and operation (Ops) of space vehicles in a complex and distributed environment requires massive and continuous flows of information across the enterprise and across temporal stages of the vehicle lifecycle. The resulting capabilities at each subsequent stage depend in part on the capture, preparation, storage, and subsequent provision of information from prior stages. The United States National Aeronautics and Space Administration (NASA) is currently designing a fleet of new vehicles that will replace the Space Shuttle and expand space operations and exploration capabilities. This includes the 2 stage human rated lift vehicle Ares 1 and its associated crew vehicle the Orion, and a service module; the heavy lift cargo vehicle, Ares 5, and an associated cargo stage known as the Earth Departure Stage; and a Lunar Lander vehicle that contains a descent stage, and ascent stage, and a habitation module. A variety of concurrent assorted ground operations infrastructure including software and facilities are also being developed, assorted technology and assembly designs and development for equipment such as EVA suits, life support systems, command and control technologies are also in the pipeline. The development is occurring in a distributed manner, with project deliverables being contributed by a large and diverse assortment of vendors and most space faring nations. Critical information about all of the components, software, and procedures must be shared during the DDT and E phases and then made readily available to the mission operations staff for access during the planning, preparation, and operations phases, and also need to be readily available for system to system interactions. The Constellation Data Systems Project (CxDS) is identifying the needs, and designing and deploying systems and processes to support these needs. This paper details the steps and processes that NASA is applying within the Constellation Program to manage this data and information, and to insure that the correct information is available, correctly annotated, and can be provisioned digitally to enhance response times, and support engineering analysis and anomaly resolution.
This powerpoint presentation describes the occupant protection project for the Orion Crew Vehicle. Background information on the Orion Crew Vehicle along with comparisons of the Space Shuttle, Ares I, Ares V, Saturn V and Soyuz-FG are also described. The contents include: 1) Background and Overview; 2) Crew health and safety overview; 3) Occupant Protection project overview; and 4) Suit Element injury risk.
An assessment methodology is developed to guide quantitative predictions of adverse physical environments and the subsequent effects on the Ares-1 crew launch vehicle associated with the loss of containment of cryogenic liquid propellants from the upper stage during ascent. Development of the methodology is led by a team at Sandia National Laboratories (SNL) with guidance and support from a number of National Aeronautics and Space Administration (NASA) personnel. The methodology is based on the current Ares-1 design and feasible accident scenarios. These scenarios address containment failure from debris impact or structural response to pressure or blast loading from an external source. Once containment is breached, the envisioned assessment methodology includes predictions for the sequence of physical processes stemming from cryogenic tank failure. The investigative techniques, analysis paths, and numerical simulations that comprise the proposed methodology are summarized and appropriate simulation software is identified in this report.
Based on the Apollo-era J-2 that powered the second and third stages of the Saturn V, the current J-2X is the liquid hydrogen and oxygen high-altitude rocket engine in development for both the Ares I Upper Stage and Ares V Earth Departure Stage. During my summer 2009 internship, J-2X was at a stage in its design maturity where verification testing needed to be considered for the benefit of adequate test facility preparation. My task was to focus on gimbal requirements and gimbal related hot-fire test plans. Facility capabilities were also of interest, specifically for hot-fire testing slated to occur at test stands A-1, A-2, and A-3 at Stennis Space Center(SSC) in Bay St. Louis, Mississippi. Gimbal requirements and stage interface conditions were investigated by applying a top-to-bottom systems engineering approach, which involved system level requirements, engine level requirements from both government and engine contractor perspectives, component level requirements, and the J-2X to Upper Stage and Earth Departure Stage interface control documents. Previous hydrogen and oxygen liquid rocket engine gimbal verification methods were researched for a glimpse at lessons learned. Discussion among the J-2X community affected by gimballing was organized to obtain input relative to proper verification of their respective component. Implementing suggestions such as gimbal pattern, angulated dwell time, altitude testing options, power level, and feed line orientation, I was able to match tests to test stands in the A Complex at SSC. Potential test capability gaps and risks were identified and pursued. The culmination of all these efforts was to coordinate with SSC to define additional facility requirements for both the A-3 altitude test stand that is currently under construction and the A-1 sea level test stand which is being renovated
The Ares I, NASA s new solid rocket based crew launch vehicle, is a two stage in line rocket that has made its waytothe forefront of NASA s endeavors. The Ares I s Upper Stage (US) will be propelled by a J-2X engine which is fueled by liquid hydrogen and liquid oxygen. The J-2X is a variation based on two of its predecessor s, the J-2 and J-2S engines. ET50 is providing the design support for hardware required to run tests on the J-2X Gas Generator (GG) that increases the delivery pressure of the supplied combustion fuels that the engine burns. The test area will be running a series of tests using different lengths and curved segments of pipe and different sized nozzles to determine the configuration that best satisfies the thrust, heat, and stability requirements for the engine. I have had to research the configurations that are being tested and gain an understanding of the purpose of the tests. I then had to research the parts that would be used in the test configurations. I was taken to see parts similar to the ones used in the test configurations and was allowed to review drawings and dimensions used for those parts. My job over this summer has been to use the knowledge I have gained to design, model, and create drawings for the un-fabricated parts that are necessary for the J-2X Workhorse Gas Generator Phase IIcTest.
This chapter will provide a thorough end-to-end description of the process for evaluation of three different data-driven algorithms for anomaly detection to select the best candidate for deployment as part of a suite of IVHM (Integrated Vehicle Health Management) technologies. These algorithms were deemed to be sufficiently mature enough to be considered viable candidates for deployment in support of the maiden launch of Ares I-X, the successor to the Space Shuttle for NASA's Constellation program. Data-driven algorithms are just one of three different types being deployed. The other two types of algorithms being deployed include a "nile-based" expert system, and a "model-based" system. Within these two categories, the deployable candidates have already been selected based upon qualitative factors such as flight heritage. For the rule-based system, SHINE (Spacecraft High-speed Inference Engine) has been selected for deployment, which is a component of BEAM (Beacon-based Exception Analysis for Multimissions), a patented technology developed at NASA's JPL (Jet Propulsion Laboratory) and serves to aid in the management and identification of operational modes. For the "model-based" system, a commercially available package developed by QSI (Qualtech Systems, Inc.), TEAMS (Testability Engineering and Maintenance System) has been selected for deployment to aid in diagnosis. In the context of this particular deployment, distinctions among the use of the terms "data-driven," "rule-based," and "model-based," can be found in. Although there are three different categories of algorithms that have been selected for deployment, our main focus in this chapter will be on the evaluation of three candidates for data-driven anomaly detection. These algorithms will be evaluated upon their capability for robustly detecting incipient faults or failures in the ground-based phase of pre-launch space shuttle operations, rather than based oil heritage as performed in previous studies. Robust detection will allow for the achievement of pre-specified minimum false alarm and/or missed detection rates in the selection of alert thresholds. All algorithms will also be optimized with respect to an aggregation of these same criteria. Our study relies upon the use of Shuttle data to act as was a proxy for and in preparation for application to Ares I-X data, which uses a very similar hardware platform for the subsystems that are being targeted (TVC - Thrust Vector Control subsystem for the SRB (Solid Rocket Booster)).
As modern space propulsion and exploration systems improve in capability and efficiency, their designs are becoming increasingly sophisticated and complex. Determining the health state of these systems, using traditional parameter limit checking, model-based, or rule-based methods, is becoming more difficult as the number of sensors and component interactions grow. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. System health can be monitored by comparing real-time operating data with these nominal characterizations, providing detection of anomalous data signatures indicative of system faults or failures. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. The scope of IMS based data-driven monitoring applications continues to expand with current development activities. Successful IMS deployment in the International Space Station (ISS) flight control room to monitor ISS attitude control systems has led to applications in other ISS flight control disciplines, such as thermal control. It has also generated interest in data-driven monitoring capability for Constellation, NASA's program to replace the Space Shuttle with new launch vehicles and spacecraft capable of returning astronauts to the moon, and then on to Mars. Several projects are currently underway to evaluate and mature the IMS technology and complementary tools for use in the Constellation program. These include an experiment on board the Air Force TacSat-3 satellite, and ground systems monitoring for NASA's Ares I-X and Ares I launch vehicles. The TacSat-3 Vehicle System Management (TVSM) project is a software experiment to integrate fault and anomaly detection algorithms and diagnosis tools with executive and adaptive planning functions contained in the flight software on-board the Air Force Research Laboratory TacSat-3 satellite. The TVSM software package will be uploaded after launch to monitor spacecraft subsystems such as power and guidance, navigation, and control (GN&C). It will analyze data in real-time to demonstrate detection of faults and unusual conditions, diagnose problems, and react to threats to spacecraft health and mission goals. The experiment will demonstrate the feasibility and effectiveness of integrated system health management (ISHM) technologies with both ground and on-board experiments.
The National Aeronautics and Space Administration (NASA) was established in 1958, and its Marshall Space Flight Center was founded in 1960, as space-related work was transferred from the Army Ballistic Missile Agency at Redstone Arsenal, where Marshall is located. With this heritage, Marshall contributes almost 50 years of systems engineering experience with human-rated launch vehicles and scientific spacecraft to fulfill NASA's mission exploration and discovery. These complex, highly specialized systems have provided vital platforms for expanding the knowledge base about Earth, the solar system, and cosmos; developing new technologies that also benefit life on Earth; and opening new frontiers for America's strategic space goals. From Mercury and Gemini, to Apollo and the Space Shuttle, Marshall's systems engineering expertise is an unsurpassed foundational competency for NASA and the nation. Current assignments comprise managing Space Shuttle Propulsion systems; developing environmental control and life support systems and coordinating science operations on the International Space Station; and a number of exploration-related responsibilities. These include managing and performing science missions, such as the Lunar Crater Observation and Sensing Satellite and the Lunar Reconnaissance Orbiter slated to launch for the Moon in April 2009, to developing the Ares I crew launch vehicle upper stage and integrating the vehicle stack in house, as well as designing the Ares V cargo launch vehicle and contributing to the development of the Altair Lunar Lander and an International Lunar Network with communications nodes and other infrastructure.
NASA's current models to predict lift-off acoustics for launch vehicles are currently being updated using several numerical and empirical inputs. One empirical input comes from free-field acoustic data measured at three Space Shuttle Reusable Solid Rocket Motor (RSRM) static firings. The measurements were collected by a joint collaboration between NASA - Marshall Space Flight Center, Wyle Labs, and ATK Launch Systems. For the first time NASA measured large-thrust solid rocket motor plume acoustics for evaluation of both noise sources and acoustic radiation properties. Over sixty acoustic free-field measurements were taken over the three static firings to support evaluation of acoustic radiation near the rocket plume, far-field acoustic radiation patterns, plume acoustic power efficiencies, and apparent noise source locations within the plume. At approximately 67 m off nozzle centerline and 70 m downstream of the nozzle exit plan, the measured overall sound pressure level of the RSRM was 155 dB. Peak overall levels in the far field were over 140 dB at 300 m and 50-deg off of the RSRM thrust centerline. The successful collaboration has yielded valuable data that are being implemented into NASA's lift-off acoustic models, which will then be used to update predictions for Ares I and Ares V liftoff acoustic environments.
Mission: Common upper stage engine for Ares I and Ares V. Challenge: Use proven technology from Saturn X-33, RS-68 to develop the highest Isp GG cycle engine in history for 2 missions in record time . Key Features: LOX/LH2 GG cycle, series turbines (2), HIP-bonded MCC, pneumatic ball-sector valves, on-board engine controller, tube-wall regen nozzle/large passively-cooled nozzle extension, TEG boost/cooling . Development Philosophy: proven hardware, aggressive schedule, early risk reduction, requirements-driven.
John C. Stennis Space Center (SSC) is the premier test facility for liquid rocket engine development and certification for the National Aeronautics and Space Administration (NASA). Therefore, it is no surprise that the SSC will play the most prominent role in the engine development testing and certification for the J-2X engine. The Pratt & Whitney Rocketdyne J-2X engine has been selected by the Constellation Program to power the Ares I Upper Stage Element and the Ares V Earth Departure Stage in NASA s strategy of risk mitigation for hardware development by building on the Apollo program and other lessons learned to deliver a human-rated engine that is on an aggressive development schedule, with first demonstration flight in 2010 and human test flights in 2012. Accordingly, J-2X engine design, development, test, and evaluation is to build upon heritage hardware and apply valuable experience gained from past development and testing efforts. In order to leverage SSC s successful and innovative expertise in the plume diagnostics for the space shuttle main engine (SSME) health monitoring,1-10 this paper will present a blueprint for plume diagnostics for various proposed ground testing activities for J-2X at SSC. Complete description of the SSC s test facilities, supporting infrastructure, and test facilities is available in Ref. 11. The A-1 Test Stand is currently being prepared for testing the J-2X engine at sea level conditions. The A-2 Test Stand is currently being used for testing the SSME and may also be used for testing the J-2X engine at sea level conditions in the future. Very recently, ground-breaking ceremony for the new A-3 rocket engine test stand took place at SSC on August 23, 2007. A-3 is the first large - scale test stand to be built at the SSC since the A and B stands were constructed in the 1960s. The A-3 Test Stand will be used for testing J-2X engines under vacuum conditions simulating high altitude operation at approximately 30,480 m (100,000 ft). To achieve the simulated altitude environment, chemical steam generators using isopropyl alcohol, LOX, and RELEASED - Printed documents may be obsolete; validate prior to use. water would run for the duration of the test and would generate approximately 2096 Kg/s of steam to reduce pressure in the test cell and downstream of the engine. The testing at the A-3 Test Stand is projected to begin in late 2010, meanwhile the J-2X component testing on A-1 is scheduled to begin later this year.