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 73 records · Page 4

All sources NASA NTRS DOE OSTI

DOE OSTI2025

A techno-economic assessment of carbon dioxide removal pathways via biochemical conversion of lignocellulose to biofuels and bioplastics

Biomass carbon removal and storage (BiCRS) is a promising pathway to mitigate climate change via large scale removal of atmospheric carbon dioxide (CO 2 ). We modeled several fermentation technologies, producing a variety of bioproducts from lignocellulosic feedstocks, to understand their levelized cost of CO 2 removal under multiple scenarios. Lifecycle greenhouse gas (GHG) emissions are accounted to provide cradle-to-grave estimates of carbon intensity (CI). We did not account for the avoided fossil CO 2 emissions from the use of biofuels in our CO 2 removal cost calculations, because avoided emissions do not contribute to CO 2 removal. The main products from the fermentation technologies we modeled include renewable diesel, ethanol, sustainable aviation fuel (SAF), and polyethylene (PE), with co-products including CO 2 , adipic acid, steam, and electricity. PE, depending on its end-of-life management, can serve as a form of biogenic carbon storage. PE has the potential to remove 1.2–1.5 tCO 2 per dry t-biomass, whereas biofuels have the potential to remove 0.3–0.9 tCO 2 per dry t-biomass, indicating that PE production is a more efficient method of carbon removal. We quantify costs of CO 2 removal to be $\$$60 – $\$$675 per metric tCO 2 removed across the various fermentation pathways. Under the scenarios analyzed, bioplastic production from lignocellulosic biomass is a more cost-effective route to CO 2 removal than biofuel production, with costs of CO 2 removal via bioplastics being 50–90 % lower than that of biofuels. Future research should explore the potential benefits and drawbacks of expanding bioplastic production for large-scale CO 2 removal.

09 BIOMASS FUELS↗

NASA NTRS2016

The Core Flight System (cFS) Community: Providing Low Cost Solutions for Small Spacecraft

In February 2015 the NASA Goddard Space Flight Center (GSFC) completed the open source release of the entire Core Flight Software (cFS) suite. After the open source release a multi-NASA center Configuration Control Board (CCB) was established that has managed multiple cFS product releases. The cFS was developed and is being maintained in compliance with the NASA Class B software development process requirements and the open source release includes all Class B artifacts. The cFS is currently running on three operational science spacecraft and is being used on multiple spacecraft and instrument development efforts. While the cFS itself is a viable flight software (FSW) solution, we have discovered that the cFS community is a continuous source of innovation and growth that provides products and tools that serve the entire FSW lifecycle and future mission needs. This paper summarizes the current state of the cFS community, the key FSW technologies being pursued, the development/verification tools and opportunities for the small satellite community to become engaged. The cFS is a proven high quality and cost-effective solution for small satellites with constrained budgets.

System↗

NASA NTRS2019

Requirements Development and Management on the Psyche Project

In January 2017, Psyche was one of two mission concepts selected by NASA for flight as part of the 14th Discovery mission competition. The project has been staffing up and maturing the spacecraft, instrument and mission system baseline designs on the path towards a 2022 launch. During much of 2018, the Project has been executing the lifecycle stage called Phase B, “Preliminary Design and Technology Completion,” one key element of which is the development and management of requirements at various levels. In the case of the Psyche project, this process has been particularly unique for several reasons. The project utilizes a Solar Electric Propulsion (SEP) Chassis from Space Systems Loral (SSL), a high volume manufacturer of commercial geostationary (GEO) telecom spacecraft based on the 1300 satellite bus. While SSL has an extensive, well-vetted set of requirements based on their very successful Earth-orbiting product line, translating that heritage to a deep space science mission required special care. In addition to the differences associated with the deep space environment and longer communication times, new interfaces had to be incorporated. While a substantial portion of the Flight System consists of the SEP Chassis, there were several new interfaces within various subsystems between SSL components and those provided by JPL and other contractors. Managing these interfaces through requirements at a relatively higher level than normally seen on internal or external builds proved challenging. Finally, the Psyche spacecraft plans to host the flight terminal of the Deep Space Optical Communications (DSOC) technology demonstration, which is itself a separate project with its own requirements that must be flowed down and managed. This paper will present an overview of the requirement development and management process for the Psyche project. It will discuss in detail the various challenges summarized above, the methods and decisions chosen to address them, and evaluate their overall effectiveness at this stage in the project.

Elkins-Tanton, Linda T.↗

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 NTRSDate not supplied

End-User Assessment of the NASA SPoRT Lightning AI Product

The NASA Short-term Prediction Research and Transition (SPoRT) Center has begun to develop products to address operational challenges and enhance safety during the lifecycle of lightning activity, and conduct evaluations in concentrated R2O/O2R efforts. The product evaluated for this study is Lightning Artificial Intelligence (A.I.), which predicts the probability of lightning out to 15 minutes in advance and spatially maps it using filled color contours. Lightning A.I. uses reflectivity, differential reflectivity, and correlation coefficient data from a subset of radars within the NEXRAD network to generate lightning probabilities at approximately 2 km resolution. The domains, spanning 145 x 145 km are centered over NASA-affiliated centers across the CONUS and use radar data which are closest in proximity. Lightning A.I. was developed with intended use by emergency managers at NASA centers. However, National Weather Service (NWS) offices are also often tasked with monitoring and forecasting the threat for lightning within their County Warning Areas for various impact-based decision support services. These forecasts are typically provided for aviation operations and large-scale, outdoor events, which may have varying safety requirements for decision-making based on lightning proximity and recency. The NASA SPoRT center conducted an assessment of the operational uses of Lightning A.I by various collaborative NWS Offices from late July into early September. This assessment included feedback from participants on both the product itself as well as its accessibility within the new, interactive NASA SPoRT Lightning Viewer. This presentation will include background information about Lightning A.I. and highlight results from this assessment. The feedback from the assessment will be used to inform research on any necessary modifications to this and future lightning products to assist end users.

Kelley Murphy↗

NASA NTRS2016

State of the Carbon Cycle - Consequences of Rising Atmospheric CO2

The rise of atmospheric CO2, largely attributable to human activity through fossil fuel emissions and land-use change, has been dampened by carbon uptake by the ocean and terrestrial biosphere. We outline the consequences of this carbon uptake as direct and indirect effects on terrestrial and oceanic systems and processes for different regions of North America and the globe. We assess the capacity of these systems to continue to act as carbon sinks. Rising CO2 has decreased seawater pH; this process of ocean acidification has impacted some marine species and altered fundamental ecosystem processes with further effects likely. In terrestrial ecosystems, increased atmospheric CO2 causes enhanced photosynthesis, net primary production, and increased water-use efficiency. Rising CO2 may change vegetation composition and carbon storage, and widespread increases in water use efficiency likely influence terrestrial hydrology and biogeochemical cycling. Consequences for human populations include changes to ecosystem services including cultural activities surrounding land use, agricultural or harvesting practices. Commercial fish stocks have been impacted and crop production yields have been changed as a result of rising CO2. Ocean and terrestrial effects are contingent on, and feedback to, global climate change. Warming and modified precipitation regimes impact a variety of ecosystem processes, and the combination of climate change and rising CO2 contributes considerable uncertainty to forecasting carbon sink capacity in the ocean and on land. Disturbance regime (fire and insects) are modified with increased temperatures. Fire frequency and intensity increase, and insect lifecycles are disrupted as temperatures move out of historical norms. Changes in disturbance patterns modulate the effects of rising CO2 depending on ecosystem type, disturbance frequency, and magnitude of events. We discuss management strategies designed to limit the rise of atmospheric CO2 and reduce uncertainty in forecasts of decadal and centennial feedbacks of rising atmospheric CO2 on carbon storage.

Carbon Cycle↗

DOE OSTI2024

Prioritizing circular economy strategies for sustainable PV deployment at the TW scale

Global decarbonization requires an unprecedented scale-up of photovoltaic (PV) manufacturing and deployment. The material demand and eventual end of life management associated with multi-TW scale deployment poses many challenges. Circular Economy (CE) and it's associated R-Actions (Reduce, Reuse, Recycle) have been proposed to mitigate end of life management and material sourcing concerns. However, CE metrics typically focus on a single product and only consider mass, excluding energy flows. This work leverages the PV in Circular Economy (PV ICE) tool to quantify the deployment, mass, and energy impacts of R-Actions and proposed sustainable PV designs in the context of achieving energy transition deployment goals (75 TW in 2050). 13 module scenarios are established and evaluated across 6 capacity, mass and energy metrics to identify tradeoffs and priorities. We find that increasing module efficiency can reduce near-term material demands up to 30% and improve energy metrics by up to 9%. Material circularity (recycling) can minimize lifecycle wastes and reduce material demands at the cost of higher energy demands. Increasing module lifetime, including reliability improvements and reuse strategies, is effective at reducing both material (>10%) and energy demands (24%). Uniquely, lifetime improvements maximize benefits and minimize the harms across all six metrics while achieving multi-TW scale deployment.

Photovoltaics↗

NASA NTRS2020

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.

Flight Project↗

NASA NTRS2020

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

Flight Project↗

NASA NTRSDate not supplied

Capturing, Analyzing, Maintaining, and Disseminating Shape Memory Material Data Between Information Management Systems

With an increased demand on reducing the time, cost, and effort to develop new materials, Integrated Computational Materials Engineering (ICME) has received widespread attention in various engineering disciplines as a catalyst for significantly reducing experimental testing during the material design process. An ICME approach to design can enable ‘fit-for-purpose’ materials to be realized in engineering applications by incorporating well-understood process-property-performance relationships between the various length and time scales in a material’s structure, enabling material optimization. However, such an approach requires validated multiscale models at the various length scales for a material, which in turn requires a large amount of data, a robust means of storing the data, and the ability to link data to developed material models. The NASA Vision 2040 [1] has identified nine key elements to enabling ICME approaches in system level design, with one being “Data, Information, and Visualization”, thus outlining the importance of a robust information management system for ICME. As the relationship between microstructure, properties, and material performance become better understood and incorporated into multiscale models that can be leveraged in application design, the emergence of new materials with application-driven properties can be realized. One such new material class that has seen growing attention are shape memory materials (SMM), in which a material can transition between a deformed and undeformed state via a reversible phase transformation when subject to a thermal, mechanical, or magnetic load [2]. SMMs have been used widely in aerospace and biomedical industries, including applications such as actuators, low-shock mechanisms, medical staples, braces, and stents [3, 4]. These materials exhibit unique behavior due to their ability to transition between phases, and thus the mechanisms that enable this transition must be captured in a data information management system and incorporated into SMM material models. At NASA Glenn Research Center, the Shape Memory Materials Database (SMMD) Tool has been developed to capture the necessary information that governs SMM material behavior and provide users the ability to select and visualize various SMMs for a specific application [5]. The database contains point-wise data for published SMM materials, along with the pedigree metadata for traceability necessary for a robust information management system. The database is also capable of storing in-house test data performed at NASA GRC by interacting with the developed Shape Memory Alloy (SMA) Analytics tool to extract the necessary point-wise values and populate the database. Although the SMMD Tool offers its users a single, authoritative source for SMM material data that is critical for model development and material design, the full material pedigree of the in-house test data for SMMs is not currently captured and is out of the scope for the SMMD tool. In this work, the schema for capturing SMM test data within the larger NASA GRC ICME Schema [6, 7, 8, 9] will be developed and implemented for thermomechanical tests conducted at NASA GRC. The developed schema will not only store the relevant data needed for the SMMD tool, but also the material pedigree (i.e., production of the bulk material, bulk material analysis, sample cut-out diagrams, sample fabrication procedure, etc.), test pedigree (i.e., test equipment used, measurement systems used, raw test data), and analysis pedigree (i.e., how the data in the SMMD tool is calculated). Furthermore, a Python-based framework will be developed to seamlessly interact between the SMA Analytics and SMMD tools, which will write the full dataset and associated metadata to the GRC Information Management System before passing the required point-wise data to the SMMD tool. Data informatics is a key element of the NASA Vision 2040, which requires not only that data is stored and maintained throughout the material lifecycle, but that the data is also accessible and reusable such that material development efforts can be minimized. Therefore, for an ICME design approach to be realized, a centralized information management system that drives the ICME process must be able to communicate with other databases. The work that will be presented in this presentation will therefore not only demonstrate the ability of NASA GRC’s information management system to capture SMM data, but also its ability to interact with pre-existing tools specialized for such materials.

Data management↗

NASA NTRS2022

Assurance Equations: A Cost and Criticality Model for Optimizing Quality Assurance Surveillance

The cost of quality vs cost of failure correction has been a long-running topic of discussion within the Aerospace community. It leads directly to concepts of “risk tolerance”, and risk-based decision-making. It would be valuable if there was a way to compute the optimal investment in customer-executed quality assurance activities using defect significance with respect to performance objectives, the activities’ defect detection effectiveness, and the cost-penalty for late discovery of impactful defects. This optimization is particularly of interest to projects whose budget constraints significantly limit their risk management options.The cost to fix defects (i.e., failure correction) escalates as the project matures. There have been studies attempting to determine the relative cost of fixing defects discovered during various phases of a project life cycle with important implications, all of which suggest growth factors are large. The commonly referred to 1:10:100 rule represents a cost multiplier for repair/rework across the Design to Fab to Test hardware development phases. Cost premiums for QA activities also accumulate when they are treated as mandatory (due to schedule drag) or are performed later than their assigned phase.This paper describes the modeling of development phase -dependencies in the conduct of typical customer-executed quality assurance activities. Our initial modeling encompasses:• Distinct phases of the production lifecycle• Multiple kinds of Defects, each with some a-priori likelihood of being present• Each defect’s impact on performance Objectives for a type of hardware• The cost and efficacy of assurance techniques at detecting such Defects• The costs of fixing those Defects detected in a given phase of the production lifecycleThe model captures assurance activities’ abilities to Detect defects. Upon detection it is assumed that the Defect is immediately fixed. Defects that “escape” detection by some activity may thereafter be detected by a later activity, but by then the cost of fixing the Defect may have escalated. Defects are related to the performance Objectives they would detract from, were those Defects to remain present in the operating system.We have constructed and are exploring, a model that relates the importance of hardware system elements to mission objectives, the impact of types of Defects on those hardware types, the cost of customer-executed assurance activities (i.e., supplier controls) and their effectiveness towards reducing an impactful quality escape, and the cost of Defect correction across production phase. We describe the approach taken to select the key model aspects, why they are relevant to our NASA mission, and our efforts to populate it with relevant and contemporary data. We use a notional example to illustrate model design and function.

Plante, Jeannette↗

DOE OSTI2024

Circular Economy for Photovoltaics in Service of Energy Transition

The challenge of energy transition is immediate and immense; current projections target 75 TW of photovoltaics (PV) capacity by 2050. While any transition to renewable energy technology is preferable to the current fossil-based system, it is ideal to improve the sustainability of PV to minimize negative environmental and social impacts. Circular economy (CE) has been proposed as a method to improve the sustainability of PV, especially for emerging materials like perovskites. CE is a set of actions, principles, and systems which aim to design out waste and keep products and materials in use, to reduce environmental impacts and enable sustainable development. At the most basic level, CE is "reduce, reuse, recycle", the R-actions, in ranked order. CE of a PV technology can be metricized in a variety of ways, such as the Material Circularity Indicator (Smith and Jones, Ellen MacArthur Foundation, 2019) or recycling rates. Unfortunately, standard CE metrics have several shortcomings for measuring renewable energy technologies in the context of deployment for energy transition (Figge 2018, Saidani 2019): 1) Only measure mass flows; 2) De-prioritization of the use phase in favor of mass circularity when scoring; and 3) Tight focus on a single product scale The use phase and energy flows of PV are key to energy transition, and therefore need to be quantified. Additionally, correlating product-scale to system-scale is necessary for quantifying the environmental impacts of energy transition. Life Cycle Assessment (LCA) can address some of these concerns, but also focuses on a single product scale and has trouble capturing the dynamics of system-scale energy transition, such as the interaction of module lifetime with manufacturing demands for energy transition deployment schedules. Therefore, we developed an open-source Python-based system dynamics model to quantify the mass, energy and carbon impacts of CE R-actions for PV technologies in the energy transition; PV in the CE (PV ICE) (Ovaitt & Mirletz 2021). The tool captures supply chains from material extraction through end of life, incorporating 5 circular end of life pathways. PV ICE takes in any evolving bill of materials, module properties and deployment schedule to support researchers and decision makers with data-backed insights. In this work, we quantify and compare proposed CE sustainable PV module designs and lifecycle management strategies, spanning currently commercialized technologies, government and industry technology targets, and several low Technology Readiness Level (TRL) emerging PV technologies, including perovskites. Our analyses capture the projected evolutions of lifetime, efficiency and material circularity of these PV technologies, as well as their material supply chains. Our analyses emphasize the importance of examining a suite of metrics to identify priorities and tradeoffs, and inform design or lifecycle management decisions holistically. Previous analyses have demonstrated the central importance of PV module lifetime to support energy transition while minimizing impacts. High levels of material circularity (>90%) enable minimizing lifecycle wastes, can reduce virgin material demands if paired with improving efficiency, but demonstrate tradeoffs in energy return on investment. In the fervor of new material and technology development, it is important to remember that CE is not the end goal; decarbonization and energy transition are the end goal. CE should be used in service to improve the sustainability of PV, and R-actions evaluated for their usefulness and efficacy to this end.

carbon↗

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. Four categories of HRP EDs exist: standards, requirements, countermeasures, and tools/technology. 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.

HRP research external deliverables↗

DOE OSTI2026

Integrated System Planning: Emerging Software Requirements in the Power Industry

Power system planning software remains fragmented across organizational boundaries, with specialized tools for capacity expansion, production cost modeling, power flow, and dynamic analysis operating on incompatible data models and assumptions. This article argues that the fragmentation is not merely a technical problem but a predictable consequence of Conway's law: software architectures mirror the departmental structures within which they are developed. Regulatory milestones like Federal Energy Regulatory Commission (FERC) Order 888 formalized these divisions, but the roots trace back to the distinct engineering disciplines-mechanical, chemical, and electrical-that staffed generation and transmission planning departments in vertically integrated utilities. As the industry moves toward integrated system planning (ISP) that coordinates generation, transmission, and distribution investment decisions, the software ecosystem must evolve accordingly. We identify five categories of software requirements to enable this transition: coherent data inputs decoupled from individual applications, unified and extensible data schemas, modular component representations that support multiple abstraction levels, lifecycle management of planning datasets, and well-defined application programming interface (API) contracts that separate data exchange from algorithmic control. We examine how these requirements interact with three common workflow patterns-serial gate clearing, sequential multiapplication, and convergence oriented-and discuss the interface design principles each demands. We then outline a vision for platform-based planning architectures where specialized analytical services compose through standardized interfaces and where artificial intelligence (AI)/machine learning (ML) tools augment decision support within a disciplined software infrastructure. The practices proposed here offer a path from today's siloed tool collections toward collaborative planning ecosystems capable of handling the complexity of modern power system transformation.

24 POWER TRANSMISSION AND DISTRIBUTION↗

NASA NTRS2008

Modifying the Heliophysics Data Policy to Better Enable Heliophysics Research

The Heliophysics (HP) Science Data Management Policy, adopted by HP in June 2007, has helped to provide a structure for the HP data lifecycle. It provides guidelines for Project Data Management Plans and related documents, initiates Resident Archives to maintain data services after a mission ends, and outlines a route to the unification of data finding, access, and distribution through Virtual observatories. Recently we have filled in missing pieces that assure more coherence and a home for the VxOs (through the 'Heliophsyics Data and Model Consortium'), and provide greater clarity with respect to long term archiving. In particular, the new policy which has been vetted with many community members, details the 'Final Archives' that are to provide long-term data access. These are distinguished from RAs in that they provide little additional service beyond servicing data, but critical to their success is that the final archival materials include calibrated data in useful formats such as one finds in CDAWeb and various ASCII or FITS archives. Having a clear goal for legacy products, to be detailed as part of the Mission Archives Plans presented at Senior Reviews, will help to avoid the situation so common in the past of having archival products that preserve bits well but not readily usable information. We hope to avoid the need for the large numbers of 'data upgrade' projects that have been necessary in recent years.

Hayes, Jeffrey↗

NASA NTRS2017

Applying Standard Independent Verification and Validation (IVV) Techniques Within an Agile Framework: Is There a Compatibility Issue?

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IVV), however, the adoption of these hybrid Agile frameworks is becoming somewhat problematic. Hence, we find it prudent to question the compatibility of conventional IVV techniques with (hybrid) Agile practices.This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IVV techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IVV methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IVV techniques that are fully compatible with the hybrid lifecycles, (2) IVV techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IVV techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.

Agile↗

NASA NTRS2004

Transitioning to Intel-based Linux Servers in the Payload Operations Integration Center

The MSFC Payload Operations Integration Center (POIC) is the focal point for International Space Station (ISS) payload operations. The POIC contains the facilities, hardware, software and communication interface necessary to support payload operations. ISS ground system support for processing and display of real-time spacecraft and telemetry and command data has been operational for several years. The hardware components were reaching end of life and vendor costs were increasing while ISS budgets were becoming severely constrained. Therefore it has been necessary to migrate the Unix portions of our ground systems to commodity priced Intel-based Linux servers. hardware architecture including networks, data storage, and highly available resources. This paper will concentrate on the Linux migration implementation for the software portion of our ground system. The migration began with 3.5 million lines of code running on Unix platforms with separate servers for telemetry, command, Payload information management systems, web, system control, remote server interface and databases. The Intel-based system is scheduled to be available for initial operational use by August 2004 The overall migration to Intel-based Linux servers in the control center involves changes to the This paper will address the Linux migration study approach including the proof of concept, criticality of customer buy-in and importance of beginning with POSlX compliant code. It will focus on the development approach explaining the software lifecycle. Other aspects of development will be covered including phased implementation, interim milestones and metrics measurements and reporting mechanisms. This paper will also address the testing approach covering all levels of testing including development, development integration, IV&V, user beta testing and acceptance testing. Test results including performance numbers compared with Unix servers will be included. need for a smooth transition while maintaining real-time support. An important aspect of the paper will involve challenges and lessons learned. product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support. This paper will also address the deployment approach including user involvement in testing and the , This includes COTS product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support.

Guillebeau, P. L.↗

NASA NTRS2005

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗