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.
The videos (Powerhead and Ducts, Test and Flight Operations) review the Space Shuttle Main Engine (SSME) program from Pratt and Whitney Rocketdyne. They include highlights from the engine's development and lifecycle through the engine testing to the deployment in the space shuttle.
Standard approach to evaluate and configure adaptable and sustainable program and mission supply chains at an enterprise level. End-to-end view. Total Lifecycle. Evaluate the readiness of the supply chain during the supply chain development phase.
In September 2007, the Engineering Directorate at the Marshall Space Flight Center (MSFC) created the Design System Focus Team (DSFT). MSFC was responsible for the in-house design and development of the Ares 1 Upper Stage and the Engineering Directorate was preparing to deploy a new electronic Configuration Management and Data Management System with the Design Data Management System (DDMS) based upon a Commercial Off The Shelf (COTS) Product Data Management (PDM) System. The DSFT was to establish standardized CAD practices and a new data life cycle for design data. Of special interest here, the design teams were to implement Model Based Definition (MBD) in support of the Upper Stage manufacturing contract. It is noted that this MBD does use partially dimensioned drawings for auxiliary information to the model. The design data lifecycle implemented several new release states to be used prior to formal release that allowed the models to move through a flow of progressive maturity. The DSFT identified some 17 Lessons Learned as outcomes of the standards development, pathfinder deployments and initial application to the Upper Stage design completion. Some of the high value examples are reviewed.
This slide presentation reviews some of the engineering innovations requirements for the challenges of space exploration which NASA has and will be involved in. It reviews some significant successes in space transportation, exploration and science accomplished during 2009, and it reviews some of the places that are available for exploration in the near term and the specific missions that NASA has assigned to Marshall. It also reviews the project lifecycle management model, that is designed to reduce undefined, but known, risks. It also demonstrates the sustainable long-term program of block upgrades that contribute to long-term success of programs.
To support cost effective, quality research it is essential that laboratory and testing facilities are maintained in a continuous and reliable state of availability at all times. NASA Langley Research Center (LaRC) and its maintenance contractor, Jacobs Technology, Inc. Research Operations, Maintenance, and Engineering (ROME) group, are in the process of implementing a combined Facility Condition Assessment (FCA) and Reliability Centered Maintenance (RCM) program to improve asset management and overall reliability of testing equipment in facilities such as wind tunnels. Specific areas are being identified for improvement, the deferred maintenance cost is being estimated, and priority is being assigned against facilities where conditions have been allowed to deteriorate. This assessment serves to assist in determining where to commit available funds on the Center. RCM methodologies are being reviewed and enhanced to assure that appropriate preventive, predictive, and facilities/equipment acceptance techniques are incorporated to prolong lifecycle availability and assure reliability at minimum cost. The results from the program have been favorable, better enabling LaRC to manage assets prudently.
The Flight Production Process (FPP) Re-engineering project has established a Model-Based Systems Engineering (MBSE) methodology and the technological infrastructure for the design and development of a reference, product-line architecture as well as an integrated workflow model for the Mission Operations System (MOS) for human space exploration missions at NASA Johnson Space Center. The design and architectural artifacts have been developed based on the expertise and knowledge of numerous Subject Matter Experts (SMEs). The technological infrastructure developed by the FPP Re-engineering project has enabled the structured collection and integration of this knowledge and further provides simulation and analysis capabilities for optimization purposes. A key strength of this strategy has been the judicious combination of COTS products with custom coding. The lean management approach that has led to the success of this project is based on having a strong vision for the whole lifecycle of the project and its progress over time, a goal-based design and development approach, a small team of highly specialized people in areas that are critical to the project, and an interactive approach for infusing new technologies into existing processes. This project, which has had a relatively small amount of funding, is on the cutting edge with respect to the utilization of model-based design and systems engineering. An overarching challenge that was overcome by this project was to convince upper management of the needs and merits of giving up more conventional design methodologies (such as paper-based documents and unwieldy and unstructured flow diagrams and schedules) in favor of advanced model-based systems engineering approaches.
Topics include NASA centers around the country; 2009 highlights of significant successes in space transportation, exploration, and science; significant accomplishments; places to explore include Lagrange points, near-Earth objects, Mars and the Moon, and International Space Station research; Marshall's missions include propulsion and transportation systems, life support systems, and earth and space science spacecraft, systems, and operations; project lifecycle management model; motivation of avionics fault-tolerance, redundancy needs and concerns, redundancy versus reliability; parallel-series configurations; effect of adding redundancy on mission success; example of rules-based approach where reliability and safety interaction impacts design; impact of common cause failure; approach ot bottom-up reliability analysis; three factors that lead to redundant system failure; Apollo 13 multi-functional reliability and example; and mitigating the risk of single string spacecraft architecture;.
Prior to a spacewalk during the NASA STS/129 mission in November 2009, Columbia Broadcasting System (CBS) correspondent William Harwood reported astronauts, "were awakened again", as they had been the day previously. Fearing something not properly connected was causing a leak, the crew, both on the ground and in space, stopped and checked everything. The alarm proved false. The crew did complete its work ahead of schedule, but the incident reminds us that correctly connecting hundreds and thousands of entities, subsystems and systems, finding leaks, loosening stuck valves, and adding replacements to very large complex systems over time does not occur magically. Everywhere major projects present similar pressures. Lives are at - risk. Responsibility is heavy. Large natural and human-created disasters introduce parallel difficulties as people work across boundaries their countries, disciplines, languages, and cultures with known immediate dangers as well as the unexpected. NASA has long accepted that when humans have to go where humans cannot go that simulation is the sole solution. The Agency uses simulation to achieve consensus, reduce ambiguity and uncertainty, understand problems, make decisions, support design, do planning and troubleshooting, as well as for operations, training, testing, and evaluation. Simulation is at the heart of all such complex systems, products, projects, programs, and events. Difficult, hazardous short and, especially, long-term activities have a persistent need for simulation from the first insight into a possibly workable idea or answer until the final report perhaps beyond our lifetime is put in the archive. With simulation we create a common mental model, try-out breakdowns of machinery or teamwork, and find opportunity for improvement. Lifecycle simulation proves to be increasingly important as risks and consequences intensify. Across the world, disasters are increasing. We anticipate more of them, as the results of global warming prove more and more ominous-glaciers melting in Bolivia, floods in Saudi Arabia, the Maldives sinking and salt rising along the Nile. Fear grows about potential asteroid crashes and nightly television images raise awareness of victims of floods, hurricanes, cyclones and typhoons, fire, tornado, tsunami, bombings, landslides, and cross-boundary criminality. The Red Cross says that disasters impact 250 million people each year. That means that 700,000 people are having a very bad day today. Modeling and simulation is and must be part of the solution.
Goal 1: Enhance Applications Research Advance the use of NASA Earth science in policy making, resource management and planning, and disaster response. Key Actions: Identify priority needs, conduct applied research to generate innovative applications, and support projects that demonstrate uses of NASA Earth science. Goal 2: Increase Collaboration Establish a flexible program structure to meet diverse partner needs and applications objectives. Key Actions: Pursue partnerships to leverage resources and risks and extend the program s reach and impact. Goal 3:Accelerate Applications Ensure that NASA s flight missions plan for and support applications goals in conjunction with their science goals, starting with mission planning and extending through the mission life cycle. Key Actions: Enable identification of applications early in satellite mission lifecycle and facilitate effective ways to integrate end-user needs into satellite mission planning
The lifecycle of sulfur in the galaxy is poorly understood. Fe-sulfide grains are abundant in early solar system materials (e.g. meteorites and comets) and S is highly depleted from the gas phase in cold, dense molecular cloud environments. In stark contrast, sulfur is essentially undepleted from the gas phase in the diffuse interstellar medium, indicating that little sulfur is incorporated into solid grains in this environment. It is widely believed that sulfur is not a component of interstellar dust grains. This is a rather puzzling observation unless Fe-sulfides are not produced in significant quantities in stellar outflows, or their lifetime in the ISM is very short due to rapid destruction. Fe sulfide grains are ubiquitous in cometary samples where they are the dominant host of sulfur. The Fe-sulfides (primarily pyrrhotite; Fe(1-x)S) are common, both as discrete 0.5-10 micron-sized grains and as fine (5-10 nm) nanophase inclusions within amorphous silicate grains. Cometary dust particles contain high abundances of well-preserved presolar silicates and organic matter and we have suggested that they should contain presolar sulfides as well. This hypothesis is supported by the observation of abundant Fe-sulfides grains in dust around pre- and post-main sequence stars inferred from astronomical spectra showing a broad 23 micron IR feature due to FeS. Fe-sulfide grains also occur as inclusions in bona fide circumstellar amorphous silicate grains and as inclusions within deuterium-rich organic matter in cometary dust samples. Our irradiation experiments show that FeS is far more resistant to radiation damage than silicates. Consequently, we expect that Fe sulfide stardust should be as abundant as silicate stardust in solar system materials.
Proper attention to the integration of the human needs in the vehicle displays and controls design process creates a safe and productive environment for crew. Although this integration is critical for all phases of flight, for crew interfaces that are used during dynamic phases (e.g., ascent and entry), the integration is particularly important because of demanding environmental conditions. This panel addresses the process of how human engineering involvement ensures that human-system integration occurs early in the design and development process and continues throughout the lifecycle of a vehicle. This process includes the development of requirements and quantitative metrics to measure design success, research on fundamental design questions, human-in-the-loop evaluations, and iterative design. Processes and results from research on displays and controls; the creation and validation of usability, workload, and consistency metrics; and the design and evaluation of crew interfaces for NASA's Crew Exploration Vehicle are used as case studies.
The Transferable, Adaptable, Modular and Upgradeable (TAMU) Flight Production Process (FPP) is a System of System (SOS) framework which cuts across multiple organizations and their associated facilities, that are, in the most general case, in geographically disperse locations, to develop the architecture and associated workflow processes of products for a broad range of flight projects. Further, TAMU FPP provides for the automatic execution and re-planning of the workflow processes as they become operational. This paper provides the blueprint for the TAMU FPP paradigm. This blueprint presents a complete, coherent technique, process and tool set that results in an infrastructure that can be used for full lifecycle design and decision making during the flight production process. Based on the many years of experience with the Space Shuttle Program (SSP) and the International Space Station (ISS), the currently cancelled Constellation Program which aimed on returning humans to the moon as a starting point, has been building a modern model-based Systems Engineering infrastructure to Re-engineer the FPP. This infrastructure uses a structured modeling and architecture development approach to optimize the system design thereby reducing the sustaining costs and increasing system efficiency, reliability, robustness and maintainability metrics. With the advent of the new vision for human space exploration, it is now necessary to further generalize this framework to take into consideration a broad range of missions and the participation of multiple organizations outside of the MOD; hence the Transferable, Adaptable, Modular and Upgradeable (TAMU) concept.
Immediately following the breakup of the 2005 Arctic spring stratospheric vortex, a tropical air mass, characterized by low potential vorticity (PV) and high nitrous oxide (N2O), was advected poleward and became trapped in the easterly summer polar vortex. This feature, known as a "Frozen-In Anticyclone (FrIAC)", was observed in Earth Observing System (EOS) Aura Microwave Limb Sounder (MLS) data to span the potential temperature range from approximately 580 to 1100 K (approximately 25 to 40 km altitude) and to persist from late March to late August 2005. This study compares MLS N2O observations with simulations from the Global Modeling Initiative (GMI) chemistry and transport model, the GEOS-5/MERRA Replay model, and the VanLeer Icosahedral Triangular Advection isentropic transport model to elucidate the processes involved in the lifecycle of the FrIAC which is here divided into three distinct phases. During the "spin-up phase" (March to early April), strong poleward flow resulted in a tight isolated anticyclonic vortex at approximately 70-90 deg N, marked with elevated N2O. GMI, Replay, and VITA all reliably simulted the spin-up of the FrIAC, although the GMI and Replay peak N2O values were too low. The FrIAC became trapped in the developing summer easterly flow and circulated around the polar region during the "anticyclonic phase" (early April to the end of May). During this phase, the FrIAC crossed directly over the pole between the 7th and 14th of April. The VITA and Replay simulations transported the N2O anomaly intact during this crossing, in agreement with MLS, but unrealistic dispersion of the anomaly occurred in the GMI simulation due to excessive numerical mixing of the polar cap. The vortex associated with the FrIAC was apparently resistant to the weak vertical hear during the anticyclonic phase, and it thereby protected the embedded N20 anomaly from stretching. The vortex decayed in late May due to diabatic processes, leaving the N2O anomaly exposed to horizontal and vertical wind shears during the "shearing phase" (June to August). The observed lifetime of the FrIAC during this phase is consistent with time-scales calculated from the ambient horizontal and vertical wind shear. Replay maintained the horizontal structure of the N2O anomaly similar to NILS well into August. The VITA simulation also captured the horizontal structure of the FrIAC during this phase, but VITA eventually developed fine-scale N2O structure not observed in MLS data.
Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.
Traffic congestion is an ongoing problem of great interest to researchers from different areas in academia. With the emerging technology for inter-vehicle communication, vehicles have the ability to exchange information with predecessors by wireless communication. In this paper, we present an agent-based model of traffic congestion and examine the impact of having CACC (Cooperative Adaptive Cruise Control) embedded vehicle(s) on a highway system consisting of 4 traffic lanes without overtaking. In our model, CACC vehicles adapt their acceleration/deceleration according to vehicle-to-vehicle inter-communication. We analyze the average speed of the cars, the shockwaves, and the evolution of traffic congestion throughout the lifecycle of the model. The study identifies how CACC vehicles affect the dynamics of traffic flow on a complex network and reduce the oscillatory behavior (stop and go) resulting from the acceleration/deceleration of the vehicles.
The Rendezvous and Proximity Operations Program (RPOP) is real-time guidance, navigation, and control (GN&C) domain piloting-aid software that provides 3D Orbiter graphics and runs on the Space Shuttle's Criticality-3 Payload and General Support Computer (PGSC) in the crew cockpit. This software provides the crew with Situational Awareness during the rendezvous and proximity operations phases of flight. RPOP can be configured from flight to flight, accounting for mission-specific flight scenarios and target vehicles, via initialization load (I-load) data files. The software provides real-time, automated, closed-loop guidance recommendations and the capability to integrate the crew s manual backup techniques. The software can bring all relative navigation sensor data, including the Orbiter's GPC (general purpose computer) data, into one central application to provide comprehensive situational awareness of the rendezvous and proximity operations trajectory. RPOP also can separately maintain trajectory estimates (past, current, and predicted) based on certain data types and co-plot them, in order to show how the various navigation solutions compare. RPOP s best estimate of the relative trajectory is determined by a relative Kalman filter processing data provided by the sensor suite s most accurate sensor, the trajectory control sensor (TCS). Integrated with the Kalman filter is an algorithm that identifies the reflector that the TCS is tracking. Because RPOP runs on PC laptop computers, the development and certification lifecycles are more agile, flexible, and cheaper than those that govern the Orbiter FSW (flight software) that runs in the GPC. New releases of RPOP can be turned around on a 3- to 6-month template, from new Change Request (CR) to certification, depending on the complexity of the changes.
Aerosols influence the earth s climate through direct, indirect, and semi-direct effects. There are large uncertainties in quantifying these effects due to limited measurements and observations of aerosol-cloud-precipitation interactions. As a major terrestrial source of atmospheric aerosols, dusts may serve as a significant climate forcing for the changing climate because of its effect on solar and thermal radiation as well as on clouds and precipitation processes. Latest satellites measurements enable us to determine dust aerosol loadings and cloud distributions and can potentially be used to reduce the uncertainties in the estimations of aerosol effects on climate. This study uses sensors on various satellites to investigate the impact of mineral dust on cloud microphysical and precipitation processes in mesoscale convective complex (MCC). A trans-Atlantic dust outbreak of Saharan origin occurring in early March 2004 is considered. For the observed MCCs under a given convective strength, small hydrometeors were found more prevalent in the dusty stratiform regions than in those regions that were dust free. Evidence of abundant cloud ice particles in the dust regions, particularly at altitudes where heterogeneous nucleation of mineral dust prevails, further supports the observed changes of clouds and precipitation. The consequences of the microphysical effects of the dust aerosols were to shift the size spectrum of precipitation-sized hydrometeors from heavy precipitation to light precipitation and ultimately to suppress precipitation and increase the lifecycle of cloud systems, especially over stratiform areas.
A JPL-created set of standard processes is to be used throughout the lifecycle of software development. These SDSPs cover a range of activities, from management and engineering activities, to assurance and support activities. These processes must be applied to software tasks per a prescribed set of procedures. JPL s Software Quality Improvement Project is currently working at the behest of the JPL Software Process Owner to ensure that all applicable software tasks follow these procedures. The SDSPs are captured as a set of 22 standards in JPL s software process domain. They were developed in-house at JPL by a number of Subject Matter Experts (SMEs) residing primarily within the Engineering and Science Directorate, but also from the Business Operations Directorate and Safety and Mission Success Directorate. These practices include not only currently performed best practices, but also JPL-desired future practices in key thrust areas like software architecting and software reuse analysis. Additionally, these SDSPs conform to many standards and requirements to which JPL projects are beholden.