Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle analysis”

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.

156 records · Page 9

JPL Innovation Foundry

Space science missions are increasingly challenged today: in ambition, by increasingly sophisticated hypotheses tested; in development, by the increasing complexity of advanced technologies; in budgeting, by the decline of flagship-class mission opportunities; in management, by expectations for breakthrough science despite a risk-averse programmatic climate; and in planning, by increasing competition for scarce resources. How are the space-science missions of tomorrow being formulated? The paper describes the JPL Innovation Foundry, created in 2011, to respond to this evolving context. The Foundry integrates methods, tools, and experts that span the mission concept lifecycle. Grounded in JPL's heritage of missions, flight instruments, mission proposals, and concept innovation, the Foundry seeks to provide continuity of support and cost-effective, on-call access to the right domain experts at the right time, as science definition teams and Principal Investigators mature mission ideas from "cocktail napkin" to PDR. The Foundry blends JPL capabilities in proposal development and concurrent engineering, including Team X, with new approaches for open-ended concept exploration in earlier, cost-constrained phases, and with ongoing research and technology projects. It applies complexity and cost models, projectformulation lessons learned, and strategy analyses appropriate to each level of concept maturity. The Foundry is organizationally integrated with JPL formulation program offices; staffed by JPL's line organizations for engineering, science, and costing; and overseen by senior Laboratory leaders to assure experienced coordination and review. Incubation of each concept is tailored depending on its maturity and proposal history, and its highest leverage modeling and analysis needs.

mission development↗

High Energy Flywheel Containment Evaluation

A flywheel testing facility is being constructed at the NASA Glenn Research Center. This facility is to be used for life cycle testing of various flywheel rotors. The lifecycle testing consists of spinning a rotor from a low rpm (approx. 20,000 ) to a high rpm (approx. 60,000) and then back to the low rpm. This spin cycle will model that which the rotor will see during use. To simulate the lifetime of the rotor, the spin cycle will be performed tens of thousands of times. A typical life cycle spin test is expected to last six months. During this time the rotor will be spun through a cycle every five minutes. The test will run continuously for the six month period barring a flywheel failure. Since it is not reasonable to have the surrounding area evacuated of personnel for the duration of the testing, the flywheel facility has to be designed to withstand a flywheel rotor failure and insure that there is no danger to any personnel in the adjacent buildings or surrounding areas. In order to determine if the facility can safely contain a flywheel rotor failure an analysis of the facility in conjunction with possible flywheel failure modes was performed. This analysis is intended as a worst case evaluation of the burst liner and vacuum tank's ability to contain a failure. The test chamber consists of a cylindrical stainless steel vacuum tank, two outer steel containment rings, and a stainless steel burst liner. The stainless steel used is annealed 302, which has an ultimate strength of 620 MPa (90,000 psi). A diagram of the vacuum tank configuration is shown. The vacuum tank and air turbine will be located below ground in a pit. The tank is secured in the pit with 0.3 m (12 in.) of cement along the base and the remaining portion of the tank is surrounded by gravel up to the access ports. A 590 kg (1300 lb.) bulkhead is placed on top of the pit during operation and the complete facility is housed within a concrete structure which has 7.5 cm (3 in.) thick walls. A cutaway of the facility is shown.

Colozza, Anthony J.↗

Development of a Weather Capability for the Urban Air Mobility Airspace Research Roadmap

Traditionally, the transportation system’s resiliency to the impacts of weather is an area where neglected or incorrect assumptions can lead to difficulties later in the research and development lifecycle. To mitigate this, NASA has ongoing efforts to develop a set of research roadmaps for organizing, integrating, and communicating research into new aviation infrastructure and transportation modalities, within which weather is being addressed early on. An effort has been undertaken to add weather assumptions and requirements to an already-existing roadmap for the Urban Air Mobility (UAM) airspace, seeking to integrate weather requirements early in the system design. This effort addresses the way in which state-of-the art and evolving weather science and technology can enable safe and efficient travel with increasing tempo of UAM operations over time. This paper describes the addition of weather as one of 10 capabilities into the UAM Airspace research roadmap, laying out the anticipated weather technology and information requirements needed to facilitate operations at various UAM Maturity Levels. The process developed and exercised by MIT Lincoln Laboratory researchers produced 41 unique requirements to be satisfied by a Weather capability for the UAM ecosystem, with more than 300 dependencies identified across the system. These requirements cover measurement, analysis, modeling, forecasting, decision support, dissemination, and overarching policy, and are provided with an overview of weather challenges for UAM. The requirements were mainly defined based on subject matter expert review of existing UAM Airspace system requirements, and refined based on iterative feedback with various stakeholders including regulators, academia, and industry. Going forward, this roadmap will help researchers and developers align to a common vision in ensuring that weather is appropriately considered in the UAM ecosystem.

Timothy Bonin↗

Development of a Weather Capability for the Urban Air Mobility Airspace Research Roadmap

Traditionally, the transportation system’s resiliency to the impacts of weather is an area where neglected or incorrect assumptions can lead to difficulties later in the research and development lifecycle. To mitigate this, NASA has ongoing efforts to develop a set of research roadmaps for organizing, integrating, and communicating research into new aviation infrastructure and transportation modalities, within which weather is being addressed early on. An effort has been undertaken to add weather assumptions and requirements to an already-existing roadmap for the Urban Air Mobility (UAM) airspace, seeking to integrate weather requirements early in the system design. This effort addresses the way in which state-of-the art and evolving weather science and technology can enable safe and efficient travel with increasing tempo of UAM operations over time. This paper describes the addition of weather as one of 10 capabilities into the UAM Airspace research roadmap, laying out the anticipated weather technology and information requirements needed to facilitate operations at various UAM Maturity Levels. The process developed and exercised by MIT Lincoln Laboratory researchers produced 41 unique requirements to be satisfied by a Weather capability for the UAM ecosystem, with more than 300 dependencies identified across the system. These requirements cover measurement, analysis, modeling, forecasting, decision support, dissemination, and overarching policy, and are provided with an overview of weather challenges for UAM. The requirements were mainly defined based on subject matter expert review of existing UAM Airspace system requirements, and refined based on iterative feedback with various stakeholders including regulators, academia, and industry. Going forward, this roadmap will help researchers and developers align to a common vision in ensuring that weather is appropriately considered in the UAM ecosystem.

research roadmap↗

Preservation of Provenance and Context to Ensure Future Understandability of Airborne Earth Observations and Derived Data Products

Open-source science goes beyond making data from scientific projects (e.g., on-orbit/satellite missions, airborne and field investigations, and other data producing activities) openly available after they are generated, but involves and open sharing of information throughout the project lifecycle. Preservation of the data and associated information required for understanding and reusing the data well after the scientific projects is a contributor to open-source science as well. Considering the high investment in the on-orbit/satellite missions, we had developed a document titled “NASA Earth Science Data Preservation Content Specification (PCS)” in 2011. This document has been used as a requirement for recent on-orbit/satellite missions by NASA. Recently it became clear that the specifications should be applied to other scientific projects as well. Therefore, the document was revised to cover other types of projects, and a Preservation Content Implementation Guidance (PCIG) document was also developed. The revised PCS, and the PCIG, were published in 2022. The purpose of this presentation is to highlight the contents of these documents as they apply to suborbital/airborne investigations. The PCS calls for content preservation in eight general categories - Measuring Instrument/Platform Description, Instrument and Science Data Products and Metadata, Science Raw Data, Product and Algorithm Documentation, Instrument Calibration, Science Algorithm Software, Science Data Product Algorithm Inputs, Science Data Product Validation, and Science Data Access and Analysis Tools. While all these categories apply to various types of projects, a few clarifying sentences have been added to the descriptions of contents in each of the categories to show which categories are especially important to airborne and field investigations and where some contents are not applicable (or difficult to obtain). The PCIG document provides some general guidance applicable to all types of projects and specific guidance in a separate section for airborne and field investigations. This section calls out typical artifacts produced during such investigations that can meet the spirit of the various PCS categories.

remote sensing↗

Cloud Modeling Using Field Project Data for the Study of Precipitation Processes

The use of cloud-resolving models (CRMs) in the study of precipitation process and their relation to the large-scale environment can be generally categorized into two approaches. The first approach is so called "cloud ensemble modeling". In this approach, many clouds of different size in various stages of their lifecycles can be present at any model simulation time. Large-scale effects are derived from observations and imposed into the model as the main forcing. The advantage of this approach is that the modeled convection will be forced to have the same intensity, thermodynamic budget and organization as the obserations.This approach will also allow CRMs to perform multi-day or multi-week time integrations. The second approach usually requires initial temperature and water vapor profiles that have a medium to large CAPE, and open lateral boundary conditions are used. The modeled clouds could be termed "self-forced convection". Model improvements, such as in the microphysics, are achieved using the second approach. In cloud ensemble modeling, accurate large-scale advective tendencies for temperature and water vapor are the main forcing for the CRMs. We found that the large-scale advective terms for temperature and water vapor are not always consistent, For example, large-scale forcing could indicate strong drying which would produce cooling in the model through evaporation but not contain large-scale advective heating to compensate. This discrepancy in forcing would cause differences between the observed and modeled latent heating profiles. Good measurements of other quantities (i.e., surface fluxes and radiation) are also required to perform variational objective analysis that computes and minimizes a "cost function" that constrains the difference between the large-scale advective forcing in temperature and water vapor. With self-forced convection, accurate vertical distributions of temperature, moisture (water vapor), and horizontal winds are required. The timing of the measurements relative to cloud development is crucial (i.e., prior to cloud triggering). Microphysical measurements (i.e., the cloud number concentration and size distribution) can also be used in this second approach but are of secondary importance with cloud ensemble modeling. In this paper, data collected during TRMM field campaigns (FCs; i.e., SCSMEX, LBA and KWAJEX) which were aimed at validating TRMM products (i.e., rainfall and the vertical distribution of latent heating) will be used to examine the impact of errors in the initial conditions (e.g.., soundings an large-scale forcing) on simulated rainfall distributions and brightness. Rainfall and precipitations simulated from a CRM will also be compared with those estimated by a schocastic model.

Tao, W.-K.↗

Methodology Development for Assessment of Spaceport Technology Returns and Risks

As part of Kennedy Space Center's (KSC's) challenge to open the space frontier, new spaceport technologies must be developed, matured and successfully transitioned to operational systems. R&D investment decisions can be considered from multiple perspectives. Near mid and far term technology horizons must be understood. Because a multitude of technology investment opportunities are available, we must identify choices that promise the greatest likelihood of significant lifecycle At the same time, the costs and risks of any choice must be well understood and balanced against its potential returns The problem is not one of simply rank- ordering projects in terms of their desirability. KSC wants to determine a portfolio of projects that simultaneously satisfies multiple goals, such as getting the biggest bang for the buck, supporting projects that may be too risky for private funding, staying within annual budget cycles without foregoing the requirements of a long term technology vision, and ensuring the development of a diversity of technologies that, support the variety of operational functions involved in space transportation. This work aims to assist in the development of in methods and techniques that support strategic technology investment decisions and ease the process of determining an optimal portfolio of spaceport R&D investments. Available literature on risks and returns to R&D is reviewed and most useful pieces are brought to the attention of the Spaceport Technology Development Office (STDO). KSC's current project management procedures are reviewed. It is found that the "one size fits all" nature of KSC's existing procedures and project selection criteria is not conducive to prudent decision-making. Directions for improving KSC's - procedures and criteria are outlined. With help of a contractor, STDO is currently developing a tool, named Change Management Analysis Tool (CMAT)/ Portfolio Analysis Tool (PAT), to assist KSC's R&D portfolio determination. A critical review of CMAT/PAT is undertaken. Directions for the improvement of this tool are provided. STDO and KSC intend to follow up on many, if not all, of the recommendations provided.

Joglekar, Prafulla↗

Establishing and Maintaining the Digital Thread of Additively Manufactured Materials and Applications

Additive Manufacturing (AM) and Integrated Computational Materials Engineering (ICME) are complementary enabling technologies for design and manufacturing of “fit-for-purpose” materials. Both technologies will impact rapid material design, reduction in cost- and time-to-market for new applications, and discovery and implementation of new materials. An ICME approach to design, however, requires experimentally validated material models at multiple length and time scales, an integrated framework that can connect analysis tools with one another to ensure the digital thread of an application is maintained, and the manufacturing (e.g., AM) capability to leverage processing-structure-property-performance (PSPP) relationships to achieve spatially varying material properties where desired. AM enables the implementation of the design of an optimized, spatially varying microstructure through careful selection of the processing parameters used during an additively manufactured build. In order to establish these PSPP relations, a large amount of data is necessary, and that data must be properly captured, analyzed and maintained in an information management system that can establish the required traceability between various aspects of the design process to ensure an application’s digital thread is maintained (from design to end of life). Such an information management system must be able to capture feedstock material pedigree, resulting microstructure from various build parameters, subsequent mechanical properties derived from testing, developed material models, and enable spatial variations in material assignment in an engineering application. Furthermore, the information management system should be easily integrated with traditionally engineered materials in a single, centralized platform to enable an ICME optimization tool to explore both types of manufacturing processes. At NASA GRC, a robust, 21st century materials information management system has been previously developed with a focus towards enabling ICME. In this work, GRC’s ICME schema is extended to accommodate additively manufactured materials, enabling storage of both traditionally and additively manufactured materials in the same construct. The methodology for properly capturing additively manufactured materials across the entire material lifecycle is presented, following the previously established database best practices, as a potential framework for establishing PSPP relationships for additively manufactured materials and applying them to engineering applications.

Data management↗

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

[Redesign of the Spacesuit Long Life Battery and the Personal Life Support System Battery]

This fall I was working on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the department. The purpose of this document is to create a standard process and ensure that the data in the same way no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own all while taking notes on the procedure. These notes were used to write the final work instruction that will become is the department standard. My second project continued the work of the summer co-op before me. I was testing aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks were designed by the summer intern but there was not much time for testing before he left. We ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (energy systems test area) and are providing very promising results that safe, high performing (greater than 180 Wh/kg) designs are possible. My main project was a redesign of the LLB battery. Another summer intern did some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the current design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density and the rest of the design was up to me. First, I created new heat sink banks in Creo using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve greater than 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options of cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan is to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Some of my side projects included working on the CAD data for the PLSS with EC and attending the NASA Aerospace Battery Workshop in Huntsville. I was also a member of the Tours and Lectures Committee for the USRA and Pathways interns. I coordinated Apollo Evening and was on the committee for touring KSC and seeing an Atlas 5 launch. I really enjoyed my time at JSC and I would like to continue working for NASA or another aerospace company in the future. I have worked other internships prior to this, but I think the heavy research and development focus is the best fit for me. I originally thought I would need to go to grad school to work in an environment like this, but I now see it is possible with a bachelor’s degree and hard work. I would like to go into the workforce and maybe continue my education with night classes.

Scharf, Stephanie↗

[Fall 2015 Abstract by Stephanie Scharf]

This Fall I worked on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the Branch. The purpose of this document is to create a standard process and ensure that the data is collected in the same way, no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own, all while taking notes on the procedure. These notes were used to write the final work instruction, which will become the Branch standard. My second project continued the work of the Summer co-op before me. I tested aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks had been designed by the previous Summer co-op, but there was not much time for testing before he left. We thus ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (Energy Systems Test Area) and are providing very promising results, indicating that safe, high performing (>180 Wh/kg) designs are possible. My main project was a redesign of the LLB (Lightweight Lithium Battery). Another summer intern had done some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the existing design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density, and the rest of the design was up to me. First, I created new heat sink banks in CREO, using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place, and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve > 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options for cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan was to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Cutting open a cell for DPA After photo from oven heat-to-vent test

Scharf, Stephanie↗

Airspace Technology Demonstration 2 (ATD-2): Analysis of APREQ Flights at CLT

5/22/2019 National Aeronautics and Space Administration 1 Airspace Technology Demonstration 2 (ATD-2) Analysis of APREQ Flights at CLT May 22, 2019 5/22/2019 Objective 2 Quantify impact of IADS Phase 1 & 2 capabilities on APREQ flights at CLT with respect to: • Compliance to the Controlled Take Off Time (CTOT) • Benefits for APREQ flights that use IDAC to renegotiate for an earlier CTOT • Benefits of pre-scheduling APREQ flights using the Earliest Off Block Time (EOBT) • Relationship between EOBT compliance and rescheduling CTOT 5/22/2019 CLT APREQ Daily Compliance(Compliance Improvement Since ATD-2 Start) 3 Steady increase of APREQ compliance over the life of the project. Reduced variation in compliance leading to improved predictability. In addition to overall improved compliance into TBM systems, the predictability is increasing 5/22/2019 APREQ Compliance 10K Rolling Window 4 The most substantial APREQ compliance improvements started with Phase 2 capability (AEFS integration, ZTL IDAC, pre-scheduling and scheduler updates). 5/22/2019 IADS Phase 1 & 2 Benefit Mechanisms 5 1. Collaborative surface metering •Reduced engine run time •Reduced fuel consumption and emissions 2. Overhead stream operational integration a.Scheduling controlled flights at the gate •Reduced engine run time •Reduced fuel consumption and emissions b.APREQ renegotiating for an earlier slot •Reduced total delay •Passenger value of time and crew costs •Reduced engine run time •Reduced fuel consumption and emissions Benefits (1) and (2a) achieved through tactical gate holds Benefit (2b) achieved through APREQ renegotiation process described below Step 1: APREQ flight has a release time but is capable of taking off earlier Step 2: FAA TMC uses the IDAC green space / red space to identify and request an earlierslot in the overhead stream Step 3: Aircraft receives earlierrelease time and the difference between the release times is the reduction in delay 5/22/2019 Benefits for APREQ flights using IDAC to renegotiate for earlierCTOT 6 LBS Fuel 270.7 hours of delay saved by electronically renegotiating a better overhead stream time for 2,071 flights. • The benefits described here are associated with better use of existing capacity in the overhead stream, and technology to reduce surface delay. •These benefits are in addition to (distinct from) surface metering savings. 5/22/2019 APREQ Delay For Pre-Scheduled Flights into KATL Have Been Reduced and are More Predictable For the Last Five Months 7 Substantial Improvements in predictability of delay for the last 5 months 5/22/2019 EOBT Compliance / CTOT Reschedulefor Pre-Scheduled Flights into KATL 8 5/22/2019 Wrap-up 9 • Compliance to the CTOT has improved throughout the lifecycle of ATD-2 with biggest improvements following the introduction of Phase 2 capabilities • Rescheduling APREQ flights using IDAC has reduced 270.7 hours of delay at CLT • Predictability of local surface delay for APREQ flights is substantially improved via pre-scheduling with the IADS system • Pre-scheduled flights that reschedule for later times tend to call ready later with respect to EOBT

CLT↗