SEARCH · Engineering Papers

Results for “product lifecycle management”

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.

SourceResearch connectionFrom yearThrough year

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

At least 55 records · Page 3

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Managing the Digital Thread for Structural Applications With Fit for Purpose Materials

With the increased emphasis on reducing the cost and time to market of new materials, the need for analytical tools that enable the virtual design and optimization of materials throughout their processing - internal structure - property - performance envelope, along with the capturing and storing of the associated material and model information across its lifecycle, has become critical. This need is also fueled by the demands for higher efficiency in material testing; consistency, quality and traceability of data; product design; engineering analysis; as well as control of access to proprietary or sensitive information. Consequently, at NASA Glenn Research Center a robust information management system that manages the digital thread across the full material life (i.e., capture, analysis, maintenance, and dissemination of data) cycle directed at the design of ‘fit-for-purpose materials’ is under development. To this end the Application Table has been incorporated within NASA Glenn Research Center’s ICME Information Management framework within the ANSYS Granta MI tool. The Application Table provides a place where material and structural application information/requirements can be linked to marry the “design-the-material” (structural engineering) and the “design-with-material” (material science) paradigms and thereby enable application-driven design and optimization of materials and structures. In additional several associated toolsets, specifically: AIMAOS (Automated Information Management Across Organizations and Scales), Py MILab, and JARIMIS (Just A Rather Intelligent Material Interrogation System) are also under development to assist in the judicious automation of this process. AIMOAS offers users an interactive graphical user interface for connecting material information management systems with both commercial and in-house simulation tools at various length scales to enable such automation in the handoff across scales and maintenance of material digital twins and the digital thread. Py MILab, is an automatic framework for the capture, analysis, maintenance, and storage of material test data. Py MILab uses a modular approach for capturing raw data, analyzing the data, and storing the data in a database, interfaced by neutral file structures, to promote plug-and-play capabilities for various analysis types. Finally, JARIMIS is an expert system that integrates various materials informatics tools (e.g., MicroNet, Surrogate ML models, ANSYS Granta MI, etc.) to enable inverse design of materials and facilitate the application of machine learning (ML) and data science with human in the loop decision making to rapidly discover and optimize new materials.

Digital Transformation↗

NASA NTRS1984

SAGA: A project to automate the management of software production systems

The project to automate the management of software production systems is described. The SAGA system is a software environment that is designed to support most of the software development activities that occur in a software lifecycle. The system can be configured to support specific software development applications using given programming languages, tools, and methodologies. Meta-tools are provided to ease configuration. Several major components of the SAGA system are completed to prototype form. The construction methods are described.

Campbell, R. H.↗

NASA NTRS2003

Fuel cell environmental life cycle assessment : a progress report

Energy generation using fuel cells offers the possibility of high conversion efficiency and reduced pollution. Thus, in the futue, conventional methods of energy generation using coalfired power plants, natural gas turbines and internal combustion engines can potentially be replaced by fuel cells. The United States, Japan and several countries in Europe are currently developing fuel cells for transportation, distributed energy generation and portable electronics applications. On a system basis, the efficiency of chemical to electrical energy conversion in fuel cells can be as high as 45%. Also, because of the lower operating temperatures compared to turbines and internal combustion engines, emissions such as carbon monoxide and nitrogen oxides are extremely small. An assessment of the environmental impact of fuel cells over the entire lifecycle is needed to determine the specific benefits in various application scenarios. Such a comparative pollutants assessment must include a "cradle to grave" approach encompassing fuel production, fuel transportation, materials/manufacturing processes, waste management, and recycling. A comparative pollutant model would be a useful tool for industry and government in estimating energy savings and environmental credits, and providing a holistic understanding on regulatory needs. Another important benefit would be the ability to make appropriate comparisons with competitive energy generation technologies such as hybrids, turbines, and internal combustion engines, and to set up realistic targets. Also, exercising the model will assist in the initial screening for potential hot spots and showstoppers and focus on the right component technologies design for manufacturing, designs for input substitution and waste minimization, and prevent any unforeseen burdens.

Narayanan, S. R.↗

NASA NTRSDate not supplied

A PPE Use Case on Configuration Management Approach for MBSE

Systems engineers worldwide have been working to implement Model-based Systems Engineering (MBSE) environments, tools, and methodologies. MBSE is a formalized application of modeling to support systems engineering, including requirements, design, analysis, verification, and validation activities over the project’s lifecycle[1]; MBSE captures the system data into a digital environment. Significant benefits of MBSE includes a reduction in the time in performing systems engineering activities and an improvement higher fidelity data production. As more Systems Engineers are using MBSE, the models it produces are becoming the source of truth for Systems Engineering artifacts. As we move towards using these models as the source of truth, a more rigorous Configuration Management (CM) infrastructure is needed. Many of the MBSE tools provide CM options but utilizing them efficiently and effectively can be challenging. More rigorous methods and tools are needed to assist with keeping track of changes in the model, making sure inadvertent changes to baseline data did not occur, visibility of changes in the different model versions, and the impacts of changes to the models. System engineers and configuration management personnel from the Power and Propulsion Element (PPE) project at NASA Glenn Research Center have been working to develop a modeling construct that allows models to be the source of truth and maintain a configuration managed baseline. This paper presents a process that leverages the existing CM tools and describes how PPE used this process to manage changes more rigorously. It will describe the process behind building the model architecture that utilizes the MBSE tool capabilities and the configuration management process. It will contain some of the advantages and disadvantages of the architecture that the PPE project had settled upon utilizing, as well as some enhanced capabilities that the PPE MBSE team has developed.

MBSE↗

NASA NTRS2005

Design Methods and Practices for Fault Prevention and Management in Spacecraft

Integrated Systems Health Management (ISHM) is intended to become a critical capability for all space, lunar and planetary exploration vehicles and systems at NASA. Monitoring and managing the health state of diverse components, subsystems, and systems is a difficult task that will become more challenging when implemented for long-term, evolving deployments. A key technical challenge will be to ensure that the ISHM technologies are reliable, effective, and low cost, resulting in turn in safe, reliable, and affordable missions. To ensure safety and reliability, ISHM functionality, decisions and knowledge have to be incorporated into the product lifecycle as early as possible, and ISHM must be considered as an essential element of models developed and used in various stages during system design. During early stage design, many decisions and tasks are still open, including sensor and measurement point selection, modeling and model-checking, diagnosis, signature and data fusion schemes, presenting the best opportunity to catch and prevent potential failures and anomalies in a cost-effective way. Using appropriate formal methods during early design, the design teams can systematically explore risks without committing to design decisions too early. However, the nature of ISHM knowledge and data is detailed, relying on high-fidelity, detailed models, whereas the earlier stages of the product lifecycle utilize low-fidelity, high-level models of systems and their functionality. We currently lack the tools and processes necessary for integrating ISHM into the vehicle system/subsystem design. As a result, most existing ISHM-like technologies are retrofits that were done after the system design was completed. It is very expensive, and sometimes futile, to retrofit a system health management capability into existing systems. Last-minute retrofits result in unreliable systems, ineffective solutions, and excessive costs (e.g., Space Shuttle TPS monitoring which was considered only after 110 flights and the Columbia disaster). High false alarm or false negative rates due to substandard implementations hurt the credibility of the ISHM discipline. This paper presents an overview of the current state of ISHM design,and a review of formal design methods to make recommendations about possible approaches to enable the ISHM capabilities to be designed-in at the system-level, from the very beginning of the vehicle design process.

Tumer, Irem Y.↗

NASA NTRS2002

A Virtual Mission Operations Center: Collaborative Environment

The Virtual Mission Operations Center - Collaborative Environment (VMOC-CE) intent is to have a central access point for all the resources used in a collaborative mission operations environment to assist mission operators in communicating on-site and off-site in the investigation and resolution of anomalies. It is a framework that as a minimum incorporates online chat, realtime file sharing and remote application sharing components in one central location. The use of a collaborative environment in mission operations opens up the possibilities for a central framework for other project members to access and interact with mission operations staff remotely. The goal of the Virtual Mission Operations Center (VMOC) Project is to identify, develop, and infuse technology to enable mission control by on-call personnel in geographically dispersed locations. In order to achieve this goal, the following capabilities are needed: Autonomous mission control systems Automated systems to contact on-call personnel Synthesis and presentation of mission control status and history information Desktop tools for data and situation analysis Secure mechanism for remote collaboration commanding Collaborative environment for remote cooperative work The VMOC-CE is a collaborative environment that facilitates remote cooperative work. It is an application instance of the Virtual System Design Environment (VSDE), developed by NASA Goddard Space Flight Center's (GSFC) Systems Engineering Services & Advanced Concepts (SESAC) Branch. The VSDE is a web-based portal that includes a knowledge repository and collaborative environment to serve science and engineering teams in product development. It is a "one stop shop" for product design, providing users real-time access to product development data, engineering and management tools, and relevant design specifications and resources through the Internet. The initial focus of the VSDE has been to serve teams working in the early portion of the system/product lifecycle - concept development, proposal preparation, and formulation. The VMOC-CE expands the application of the VSDE into the operations portion of the system lifecycle. It will enable meaningful and real-time collaboration regardless of the geographical distribution of project team members. Team members will be able to interact in satellite operations, specifically for resolving anomalies, through access to a desktop computer and the Internet. Mission Operations Management will be able to participate and monitor up to the minute status of anomalies or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities, and technologies.

Medina, Barbara↗

NASA NTRS2011

Framework for Integrating Science Data Processing Algorithms Into Process Control Systems

A software framework called PCS Task Wrapper is responsible for standardizing the setup, process initiation, execution, and file management tasks surrounding the execution of science data algorithms, which are referred to by NASA as Product Generation Executives (PGEs). PGEs codify a scientific algorithm, some step in the overall scientific process involved in a mission science workflow. The PCS Task Wrapper provides a stable operating environment to the underlying PGE during its execution lifecycle. If the PGE requires a file, or metadata regarding the file, the PCS Task Wrapper is responsible for delivering that information to the PGE in a manner that meets its requirements. If the PGE requires knowledge of upstream or downstream PGEs in a sequence of executions, that information is also made available. Finally, if information regarding disk space, or node information such as CPU availability, etc., is required, the PCS Task Wrapper provides this information to the underlying PGE. After this information is collected, the PGE is executed, and its output Product file and Metadata generation is managed via the PCS Task Wrapper framework. The innovation is responsible for marshalling output Products and Metadata back to a PCS File Management component for use in downstream data processing and pedigree. In support of this, the PCS Task Wrapper leverages the PCS Crawler Framework to ingest (during pipeline processing) the output Product files and Metadata produced by the PGE. The architectural components of the PCS Task Wrapper framework include PGE Task Instance, PGE Config File Builder, Config File Property Adder, Science PGE Config File Writer, and PCS Met file Writer. This innovative framework is really the unifying bridge between the execution of a step in the overall processing pipeline, and the available PCS component services as well as the information that they collectively manage.

Mattmann, Chris A.↗

NASA NTRSDate not supplied

The Dark Target aerosol retrieval algorithm applied to Low Earth Orbit and GEOstationary imagers: progress towards an integrated LEO-GEO view of global aerosol

The relatively simple dark-target (DT) aerosol retrieval algorithm provides products of spectral aerosol optical depth (AOD) from measurements of multi-spectral reflectance in visible, near-infrared and shortwave infrared wavelength bands. Originally developed for Moderate-resolution Imaging Spectroradiometer (MODIS aboard Terra and Aqua) in Low-Earth Orbit (LEO), DT has been ported to Visible Infrared Imaging Suite (VIIRS aboard Suomi-NPP and NOAA-20, also in LEO), to enhanced-MODIS Airborne Simulator (eMAS, on an airborne platform), and now to sensors in GEOstationary orbit (Advanced Himawari Imager - AHI aboard Himawari-8 and Advanced Baseline Imagers – ABI aboard GOES-16 and 17). Together, these new datasets not only extend upon the 20+ year MODIS aerosol record, but also expand the temporal sampling and/or spatial resolution. Between July and October of 2019, NASA participated in two field experiments on opposite sides of the globe. These included FIREX-AQ which focused on fire and smoke in the Western U.S., and then CAMP2EX which targeted aerosol/cloud interactions around the Philippines. We have performed DT aerosol retrievals on all images from all sensors during these three months, validated against ground observations from stationary and mobile sunphotometer sites, and have begun to develop a synergy that represents semi-global observations every half hour. The resulting aerosol products are being used as context and for model assimilation, thus providing the framework for more complete characterization of global aerosol transport and lifecycle. Here, we report on progress, as well as remaining challenges such as data management, computer processing, and accounting for differences between GEO and LEO observation geometry and surface reflectance parameterization.

dark target↗

NASA NTRSDate not supplied

Surface Systems Capability Gaps for Enabling NASA’s Sustainable Lunar Operations

This paper discusses the NASA Ground, Test, and Surface Systems Taxonomy (TX-13) related capability gaps, including details of architecture, technology, engineering, and policy gaps for enabling sustainable lunar surface operations and subsequent Mars missions. Architecture gaps include standardized architectures and interfaces, multi-element systems engineering and integration, design for supportability, and nuclear payload processing and launch approach. Technology gaps, primarily focused on uncrewed surface operations, include automated/autonomous cryogenic loading, transfer, servicing, and storage of commodities; health determination and fault management; automated/autonomous planning and scheduling; automated/autonomous inspection, maintenance and repair; logistics management and reliability; launch and landing site preparation; commodity management; and advanced umbilicals and dust tolerant interfaces. Engineering gaps include high-purity propellant production for ground and surface applications and large-scale xenon servicing capabilities. The policy gap includes nuclear propulsion acceptance testing and qualification approach. Strategically identifying human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle is essential for achieving the mission objectives for a sustainable human lunar presence, improving performance and mission effectiveness, reducing operations costs and reliance on humans to perform tasks, and accommodating ground communication delays.

Surface Systems↗

NASA NTRSDate not supplied

Contracting Quality Early in the Lifecycle Using AS9145 Data Deliverables

Development schedules and a highly dynamic supply chain are a challenge to developers of complex systems produced at low volume. Flaws in designs, parts and materials availability problems, poor manufacturability, and a lack of knowledge about critical items and key process attributes can be realized well before traditional second-party quality assurance activities begin. Supplier audits and product inspections may have little mitigating effect once these foundational problems have been realized. Their impacts can be significant lifecycle disruption, cost overruns, inability to deliver to plan, and even project cancellation. AS9145, Requirements for Advanced Product Quality Planning and Production Part Approval Process, can be used to drive quality engineering practices into early development lifecycles to significantly reduce this late-cycle risk and to reduce the cost of quality overall. Since its initial publication in 2016, it has had very limited adoption by the DoD, no adoption by NASA, and sparse adoption in the aerospace and defense supply chain. A task group within the Aerospace Industries Association's (AIA) Joint Strategic Quality Council (JSQC) identified that both acquirers and suppliers see as AS9145 as a cost-adder and are hesitant to use it as an alternative to late-stage-heavy quality assurance approaches. A lack of prior use creates large capability gaps in request-for-proposal (RFP) teams, proposal teams, suppliers’ quality management systems (QMS), and in experienced personnel executing the early lifecycle approach. To create a more realizable on-ramp for using AS9145 in the space and defense sectors, the AIA JSQC task team created five deliverable requirements descriptions (DRDs) that can be used in a contract to begin to engage both parties in early lifecycle quality engineering and quality assurance activities, that reduce exposure to late-stage cost and schedule collapse due to unidentified risks in design, supply chain, and manufacturability. These DRDs drive the parties to engage in planning and analysis discussions early on to understand what production risks can be known and how they will focus resources based on safety criticality and the key elements of design and construction. The suppliers and acquirers who will produce the data and information required by the DRD will be able to incrementally evolve their QMS and the acquirer will incrementally be able to track and understand the benefits of cost shifting from late to early development phases. A white paper describing this approach and the five recommended DRDs will be published by the AIA in late 2024 or early 2025.

Jeannette Plante↗

NASA NTRSDate not supplied

Managing HRP's External Deliverables: The Process and the Customers

The Human Research Program’s (HRP) external deliverables (EDs) are the final outcomes of the research that the HRP Elements develop and execute. The NASA Human Health and Performance directorate’s primary stakeholders, i.e., the customers for the EDs, include the Office of the Chief Health and Medical Officer (OCHMO) (Standards Team, Chief Health and Performance Officers and Chief Medical Officers, Human System Risk Board), and the agency’s System Capability Leadership Teams. The EDs may address the need of a specific customer, a specific design reference mission, or a vehicle lifecycle milestone. HRP’s Maturation and Integration Office External Programs facilitates the process of delivering the EDs to the targeted customers according to the customer’s expectations. This presentation describes this coordinated process and provides an overview of the nature of different types of EDs and how they impact the customers’ products. Successful transfer of the EDs to the customers will help mitigate the health and performance risks that crewmembers will face during NASA’s future exploration missions.

research↗

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 NTRS2008

Human Factors in Human-Systems Integration

Any large organization whose mission is to design and develop systems for humans, and train humans needs a well-developed integration and process plan to deal with the challenges that arise from managing multiple subsystems. Human capabilities, skills, and needs must be considered early in the design and development process, and must be continuously considered throughout the development lifecycle. This integration of human needs within system design is typically formalized through a Human-Systems Integration (HSI) program. By having an HSI program, an institution or organization can reduce lifecycle costs and increase the efficiency, usability, and quality of its products because human needs have been considered from the beginning.

Fitts, David J.↗

DOE OSTI2024

ORNL Package Testing Program Software Quality Assurance Plan

The Oak Ridge National Laboratory (ORNL) Package Testing Program (PTP) uses commercial off-the-shelf (COTS) software in performing data collection of thermal test results for package designs that contain radioactive materials. Specifically, this software is used to collect temperature data from the furnace, packages, and ambient air to prepare and execute the thermal test specified in 10 CFR 71.73, “Thermal Test.” This software quality assurance (SQA) plan sets forth the guidelines, standards, and procedures that shall be used to provide SQA for PTP software applications. This is a living document that will be maintained for the lifecycle of the PTP program. The SQA plan follows the requirements set forth in ORNL Standards Based Management System (SBMS): Information Technology; Subject Area: Software Quality Assurance. When applicable to the requirements as described in ORNL SBMS, Software Quality Assurance, the software shall be listed in the ORNL Software Registration System (SRS). Exemptions to this SBMS are COTS and firmware that are not modified; spreadsheet applications and personal productivity tools that do not have a utility or safety application, research applications, legacy software, system software, vendor-supplied software used to interface with the vendor’s services, software used within the organization to facilitate processing or management of information, and software developed for applications not specific to the US Department of Energy (DOE).

97 MATHEMATICS AND COMPUTING↗

NASA NTRSDate not supplied

The Interplay of Humor and Team Cohesion Over Time

Team bonding and interpersonal relationships are increasingly important as we continue understanding the effects of the pandemic on team dynamics. Specifically, team cohesion, defined as having a sense of belonging and commitment towards the group, has been found to be important for key team outcomes such as performance, relationships, and productivity (Beal, Cohen, Burke, & McLendon, 2003; Bell & Marentette, 2011). Research has stressed the benefits of positive humor on cohesion, with humor creating positive emotions and decreasing social distance (e.g., Robert & Wilbanks, 2012; Robinson & Smith-Lovin, 2001; Romero & Pescosolido, 2008). However, research around the impact of negative humor on cohesion is scarce. This study aims to examine the impact of both positive and negative humor on cohesion for teams over time. The longitudinal design allows us to examine the interplay of humor and cohesion throughout a team’s lifecycle to guide relationship development and management (Romero & Pescosolido, 2008). Humor is defined as remarks recognized as amusing or funny (Martin, 2007). Positive humor can be categorized as good-natured aimed to create mutual agreement, while negative humor is defined as aggressive, hostile, and unreciprocated (Coan & Gottman, 2007). Research has concluded the many benefits of positive humor, showing it can increase open communication, social support, and create a pleasant environment (Martineau, 1972; Robinson & Smith-Lovin, 2001; Romero & Pescosolido, 2008). The Humor Wheel model suggests that positive humor is contagious due to the positive affect produced and mimicked (Lehmann-Willenbrock & Allen 2014). Research has suggested positive humor would increase over time based on the norm of reciprocity; those treated positively are likely to respond similarly (Gouldner, 1960). Multiple parties’ involvement in humor exchanges highlights the interpersonal nature of humor. Thus, long-term consequences on relationships should be considered, such as cohesion (Robert & Wilbanks, 2012). It would be instrumental to understand how humor interactions could weaken or strengthen group cohesion through relational and emotional bonds over time (Martineau, 1972; Romero & Pescosolido, 2008). Positive humor should fundamentally increase team cohesion (Mesmer-Magnus, Glew, & Viswesvaran, 2012; Walter & Baruch, 2008) by promoting group harmony, team member attractiveness, and ingroup identity (Holmes, 2006). Thus, it is expected there is a positive relationship between positive humor and team cohesion over time (hypothesis 1). Humor is not always beneficial, especially when it elicits negative emotions (Dikkers, Doosje, & de Lange, 2011). Negative humor can be used to humiliate, tease, or insult (Coan & Gottman, 2007; Collinson, 1988; Romero & Cruthirds, 2006). It tends to cause distress and damage relationships, and in turn, decrease organizational performance and production (Avolio, Howell, & Sosik, 1999; Janes & Olson, 2000; Yerkes, 2001). Research concludes negative humor may create subgroups and decrease cooperation (Romero & Arendt, 2011). Research has also indicated positive implications for negative humor under specific circumstances. Negative humor could help to solidify ingroup identity and strengthen bonds when directed outside the team (Terrion & Ashforth, 2002; Thomae & Pina, 2015). For example, sport teams may use negative humor towards their opponent before a game, which emphasizes their differences and lowers the status and power of their opponent, ultimately promoting solidarity and cohesion inside the group. For this study, it is anticipated that negative humor toward other teammates will decrease team cohesion over time due to the damage to relationships and negative affect produced (Duncan, Smeltzer, & Leap, 1990; Maples, Dupey, Torres‐Rivera, Phan, Vereen, & Garrett, 2001). We also predicted that negative humor focused on something or someone outside the team will increase cohesion by enhancing ingroup ties and creating a common identity (Thomae & Pina, 2015). Thus, the relationship between negative humor and cohesion will be moderated by the target of the humor. The relationship will be negative when the target is within the team and positive when the target is outside (hypothesis 2).

Melissa M. Vazquez↗

NASA NTRS1994

SCOS 2: An object oriented software development approach

The Spacecraft Control and Operations System 2 (SCOS 2), is intended to provide the generic mission control system infrastructure for future ESA missions. It represents a bold step forward in order to take advantage of state-of-the-art technology and current practices in the area of software engineering. Key features include: (1) use of object oriented analysis and design techniques; (2) use of UNIX, C++ and a distributed architecture as the enabling implementation technology; (3) goal of re-use for development, maintenance and mission specific software implementation; and (4) introduction of the concept of a spacecraft control model. This paper touches upon some of the traditional beliefs surrounding Object Oriented development and describes their relevance to SCOS 2. It gives rationale for why particular approaches were adopted and others not, and describes the impact of these decisions. The development approach followed is discussed, highlighting the evolutionary nature of the overall process and the iterative nature of the various tasks carried out. The emphasis of this paper is on the process of the development with the following being covered: (1) the three phases of the SCOS 2 project - prototyping & analysis, design & implementation and configuration / delivery of mission specific systems; (2) the close cooperation and continual interaction with the users during the development; (3) the management approach - the split between client staff, industry and some of the required project management activities; (4) the lifecycle adopted being an enhancement of the ESA PSS-05 standard with SCOS 2 specific activities and approaches defined; and (5) an examination of some of the difficulties encountered and the solutions adopted. Finally, the lessons learned from the SCOS 2 experience are highlighted, identifying those issues to be used as feedback into future developments of this nature. This paper does not intend to describe the finished product and its operation, but focusing on the journey to arrive there, concentrating therefore on the process and not the products of the SCOS 2 software development.

Symonds, Martin↗

NASA NTRSDate not supplied

End-user Assessment of the NASA SPoRT GLM Stoplight Product

National Weather Service (NWS) offices monitor and forecast the threat for lightning within their County Warning Areas for various impact-based decision support services (IDSS). These forecasts are provided routinely for aviation operations, but irregularly for large-scale, outdoor events, which typically have varying safety requirements with regards to lightning. Lightning monitoring and forecasting can require synthesizing a plethora of data, so products that make this process more efficient and effective are sought by the operational community. The NASA Short-term Prediction Research and Transition (SPoRT) Center has begun to develop several products to address these operational challenges during the lifecycle of lightning activity, and conduct evaluations in concentrated (Research-to-Operations/Operations-to-Research) efforts. The product evaluated for this study is the Geostationary Lightning Mapper (GLM) Stoplight product, which addresses lightning safety specifically with regards to lightning recency and cessation. The GLM Stoplight product displays the spatial extent of lightning and uses color-coded pixels to show the recency of lightning in 10-minute increments. This presentation highlights results from an assessment of the GLM Stoplight product by select NWS offices, as well as emergency managers, that took place over a 5-week period from May 1st to June 2nd. Feedback was collected on the GLM Stoplight product and on a new and interactive lightning viewer, which allowed participants to tailor visualization of the product based on their location and desired application. Results will help NASA SPoRT gain a better understanding of how forecasters and emergency managers use lightning data for safety applications. In addition, the assessment will inform research on any necessary modifications to this and future lightning products to assist end users.

Kelley Murphy↗

DOE OSTI2026

Life Cycle Inventories and Data Gap Analysis for Rare Earth Elements: Neodymium and Dysprosium from Mining to Magnets

The United States demand for Neodymium-Iron-Boron (NdFeB) magnets, produced from rare earth elements (REEs) such as (Nd) and Dysprosium (Dy), far exceeds its nascent domestic production capacity, rendering it reliant on vulnerable global supply chains dominated by China. To guide research and development investments in securing U.S. REE supply, defensible benchmark metrics across environmental, economic, and social dimensions are needed. In this study, we built globally-representative, process-based cradle-to-cradle life cycle inventories for Nd and Dy in NdFeB magnets lifecycles, encompassing primary material acquisition, beneficiation, smelting and refining, metal processing, specialty alloy and chemical transformation, subcomponent manufacturing, consumer application (use phase) and end-of-life management. We carried out detailed literature review, and applied process engineering principles to build industry-representative upscaled life cycle inventories for both metals. We used these models to conduct bottom-up literature review and gap analysis on existing literature, compilation of data sources for each life cycle stage (and transformations where necessary), and a preliminary technoeconomic analysis (TEA)/life cycle costing analysis (LCCA). Findings from this work emphasize the need for metal specific, representative REE LCIs to establish robust benchmarks for advancing sustainable REE technologies and guiding R&D in REE supply chains.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗