Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Enabling and Enhancing Space Mission Success and Reduction of Risk through the Application of an Integrated Data Architecture

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.

Brummett, Robert C.↗
NASA NTRS2009

Real-Time Simulation of Ares I Launch Vehicle

The Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) has been developed for use by the Ares I launch vehicle System Integration Laboratory (SIL) at the Marshall Space Flight Center (MSFC). The primary purpose of the Ares SIL is to test the vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment to certify that the integrated system is prepared for flight. ARTEMIS has been designed to be the real-time software backbone to stimulate all required Ares components through high-fidelity simulation. ARTEMIS has been designed to take full advantage of the advances in underlying computational power now available to support HWIL testing. A modular real-time design relying on a fully distributed computing architecture has been achieved. Two fundamental requirements drove ARTEMIS to pursue the use of high-fidelity simulation models in a real-time environment. First, ARTEMIS must be used to test a man-rated integrated avionics hardware and software system, thus requiring a wide variety of nominal and off-nominal simulation capabilities to certify system robustness. The second driving requirement - derived from a nationwide review of current state-of-the-art HWIL facilities - was that preserving digital model fidelity significantly reduced overall vehicle lifecycle cost by reducing testing time for certification runs and increasing flight tempo through an expanded operational envelope. These two driving requirements necessitated the use of high-fidelity models throughout the ARTEMIS simulation. The nature of the Ares mission profile imposed a variety of additional requirements on the ARTEMIS simulation. The Ares I vehicle is composed of multiple elements, including the First Stage Solid Rocket Booster (SRB), the Upper Stage powered by the J- 2X engine, the Orion Crew Exploration Vehicle (CEV) which houses the crew, the Launch Abort System (LAS), and various secondary elements that separate from the vehicle. At launch, the integrated vehicle stack is composed of these stages, and throughout the mission, various elements separate from the integrated stack and tumble back towards the earth. ARTEMIS must be capable of simulating the integrated stack through the flight as well as propagating each individual element after separation. In addition, abort sequences can lead to other unique configurations of the integrated stack as the timing and sequence of the stage separations are altered.

Tobbe, Patrick↗
NASA NTRS2009

Connecting Research and Practice: An Experience Report on Research Infusion with SAVE

NASA systems need to be highly dependable to avoid catastrophic mission failures. This calls for rigorous engineering processes including meticulous validation and verification. However, NASA systems are often highly distributed and overwhelmingly complex, making the software portion of these systems challenging to understand, maintain, change, reuse, and test. NASA's systems are long-lived and the software maintenance process typically constitutes 60-80% of the total cost of the entire lifecycle. Thus, in addition to the technical challenges of ensuring high life-time quality of NASA's systems, the post-development phase also presents a significant financial burden. Some of NASA's software-related challenges could potentially be addressed by some of the many powerful technologies that are being developed in software research laboratories. Many of these research technologies seek to facilitate maintenance and evolution by for example architecting, designing and modeling for quality, flexibility, and reuse. Other technologies attempt to detect and remove defects and other quality issues by various forms of automated defect detection, architecture analysis, and various forms of sophisticated simulation and testing. However promising, most such research technologies nevertheless do not make the transition from the research lab to the software lab. One reason the transition from research to practice seldom occurs is that research infusion and technology transfer is difficult. For example, factors related to the technology are sometimes overshadowed by other types of factors such as reluctance to change and therefore prohibits the technology from sticking. Successful infusion might also take very long time. One famous study showed that the discrepancy between the conception of the idea and its practical use was 18 years plus or minus three. Nevertheless, infusing new technology is possible. We have found that it takes special circumstances for such research infusion to succeed: 1) there must be evidence that the technology works in the practitioner's particular domain, 2) there must be a potential for great improvements and enhanced competitive edge for the practitioner, 3) the practitioner has to have strong individual curiosity and continuous interest in trying out new technologies, 4) the practitioner has to have support on multiple levels (i.e. from the researchers, from management, from sponsors etc), and 5) to remain infused, the new technology has to be integrated into the practitioner's processes so that it becomes a natural part of the daily work. NASA IV&V's Research Infusion initiative sponsored by NASA's Office of Safety & Mission Assurance (OSMA) through the Software Assurance Research Program (SARP), strives to overcome some of the problems related to research infusion.

Lindvall, Mikael↗
NASA NTRS2009

Fully Employing Software Inspections Data

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

Shull, Forrest↗
NASA NTRS2008

Juno Mission Simulation

The Juno spacecraft is planned to launch in August of 2012 and would arrive at Jupiter four years later. The spacecraft would spend more than one year orbiting the planet and investigating the existence of an ice-rock core; determining the amount of global water and ammonia present in the atmosphere, studying convection and deep- wind profiles in the atmosphere; investigating the origin of the Jovian magnetic field, and exploring the polar magnetosphere. Juno mission management is responsible for mission and navigation design, mission operation planning, and ground-data-system development. In order to ensure successful mission management from initial checkout to final de-orbit, it is critical to share a common vision of the entire mission operation phases with the rest of the project teams. Two major challenges are 1) how to develop a shared vision that can be appreciated by all of the project teams of diverse disciplines and expertise, and 2) how to continuously evolve a shared vision as the project lifecycle progresses from formulation phase to operation phase. The Juno mission simulation team addresses these challenges by developing agile and progressive mission models, operation simulations, and real-time visualization products. This paper presents mission simulation visualization network (MSVN) technology that has enabled a comprehensive mission simulation suite (MSVN-Juno) for the Juno project.

space vehicles↗
NASA NTRS2010

Model Based Definition

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.

Rowe, Sidney E.↗
NASA NTRS2010

Engineering Innovations for Exploration Challenges

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.

Dumbacher, Daniel L.↗
NASA NTRS2010

Using Facility Condition Assessments to Identify Actions Related to Infrastructure

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.

Rubert, Kennedy F.↗
NASA NTRS2010

Re-Engineering Complex Legacy Systems at NASA

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.

Ruszkowski, James↗
NASA NTRS2010

Techniques for Assuring NASA Mission Success Using Redundancy and Multi-Functionality Designs

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;.

Shivers, Herb↗
NASA NTRS2010

World, We Have Problems: Simulation for Large Complex, Risky Projects, and Events

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.

Elfrey, Priscilla↗
NASA NTRS2010

NASA Applied Sciences Program

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

Irwin, Daniel↗
NASA NTRS2010

The Search for Interstellar Sulfide Grains

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.

Keller, Lindsay P.↗
NASA NTRS2010

Human Engineering of Space Vehicle Displays and Controls

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.

Whitmore, Mihriban↗
NASA NTRS2011

TAMU: Blueprint for A New Space Mission Operations System Paradigm

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.

Ruszkowski, James T.↗
NASA NTRS2010

Modeling the Frozen-In Anticyclone in the 2005 Arctic Summer Stratosphere

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.

Allen, D. R.↗