scispace - formally typeset
Search or ask a question
Journal ArticleDOI

Editorial Software Obsolescence—Complicating the Part and Technology Obsolescence Management Problem

TL;DR: There are a growing number of methodologies, databases and tools that address status, forecasting, risk, mitigation and management of electronic parts obsolescence, but the one common attribute of all the methodologies in use today is that they focus exclusively on the hardware life cycle.
Abstract: As a result of the rapid growth of the electronics industry, many of the electronic parts in products have a procurement life cycle that is significantly shorter than the life cycle of the system they go into. A part becomes obsolete when it is no longer manufactured, either because demand has dropped to low enough levels that manufacturers choose not to continue to make it, or because the materials or technologies necessary to produce it are no longer available. The military refers to this situation as Diminishing Manufacturing Sources and Material Shortages (DMSMS). Avionics and military systems may encounter obsolescence before being fielded and always experience obsolescence problems during their field life, [1]. Today there are a growing number of methodologies, databases and tools that address status, forecasting, risk, mitigation and management of electronic parts obsolescence, [2]. However, the one common attribute of all the methodologies, databases and tools that are in use today, whether reactive, proactive or strategic, is that they focus exclusively on the hardware life cycle. In most complex systems, software life cycle costs (redesign, re-hosting and re-qualification) contribute as much or more to the total life cycle cost as the hardware, and the hardware and software must be concurrently sustained.
Citations
More filters
Journal ArticleDOI
TL;DR: Results of this analysis suggest that system capability shortcomings, limited availability of system support, and low levels of technical integration were key determinants of increased intentions to replace an existing system.
Abstract: Limited attention has been directed toward examining post-adoption stages of the information system life cycle. In particular, the final stages of this life cycle have been largely ignored despite the fact that most systems eventually reach the end of their useful life. This oversight is somewhat surprising given that end-of-life decisions can have significant implications for user effectiveness, the value extracted from IS investments, and organizational performance. Given this apparent gap, a multi-method empirical study was undertaken to improve our understanding of organizational level information system discontinuance. Research commenced with the development of a broad theoretical framework consistent with the technology-organization-environment (TOE) paradigm. The resulting framework was then used to guide a series of semi-structured interviews with organizational decision makers in an effort to inductively identify salient influences on the formation of IS discontinuance intentions. A set of research hypotheses were formulated based on the understanding obtained during these interviews and subsequently tested via a random survey of senior IS decision makers at U.S. and Canadian organizations. Data obtained from the survey responses was analyzed using partial least squares (PLS). Results of this analysis suggest that system capability shortcomings, limited availability of system support, and low levels of technical integration were key determinants of increased intentions to replace an existing system. Notably, investments in existing systems did not appear to significantly undermine organizational replacement intentions despite support for this possibility from both theory and our semi-structured interviews.

215 citations

Journal ArticleDOI
TL;DR: In this paper, the authors provide a comprehensive literature review on the problem of obsolescence in "sustainment-dominated systems" that require support for many decades, taking into account not only electronic components but also other aspects of the system such as mechanical components, software, materials, skills and tooling.
Abstract: This paper provides a comprehensive literature review on the problem of obsolescence in “sustainment-dominated systems” that require support for many decades. Research on this topic continues to grow as a result of the high impact of obsolescence on the in-service phase of long-term projects. Research on obsolescence also seeks to understand how it can be managed, mitigated and resolved. The paper aims to clarify and classify the different activities that may be included in an obsolescence management planning, taking into account not only electronic components but also other aspects of the system such as mechanical components, software, materials, skills and tooling. The literature review shows that although there are many commercial tools available that support the obsolescence management during the in-service phase of the life cycle of a system, little research has been done to forecast the costs incurred.

82 citations


Cites background from "Editorial Software Obsolescence—Com..."

  • ... Software and Media In most complex systems, as Sandborn [36] stated, “software life cycle costs (redesign, rehosting and re-qualification) contribute as much or more to the total life cycle cost as the hardware, and the hardware and software must be concurrently sustained”....

    [...]

  • ...Indeed very few organisations in the defence industry are managing and costing software obsolescence properly [36, 37,38]....

    [...]

  • ...24 Singh, Sandborn and Feldman, from the University of Maryland, have designed a software tool that enables the prediction of the optimum design refresh plan (MOCA tool) [2,4,6,10,17,20,22,43,61,68]....

    [...]

  • ...Sandborn et al. [43] expressed concern about the importance of the data at the system’s design stage and developed data mining based algorithms that allow finding out more information, increasing the predictive capabilities....

    [...]

  • ...PartMiner's Life Cycle Forecast data is derived using mathematical algorithms developed in conjunction with Sandborn and the University of Maryland....

    [...]

Journal ArticleDOI
TL;DR: In this paper, the authors adopt a longer-term perspective to better understand the overall transition towards zero-emissions road transport by empirically and theoretically contributing to the strategic management of lithium-ion powered, vehicle electrification.
Abstract: Industrial advances and academic enquiry into the transition towards electrified mobility has been arguably preoccupied with the earlier phases of technological development, while less consideration has been given to the end-of-life phase. One example of this is the current technical and economic difficulties surrounding Battery Electric Vehicle (BEV) recycling; and specifically, their high voltage lithium-ion batteries. In this study of the automotive sector, we adopt a longer-term perspective to better understand the overall transition towards “zero-emissions” road transport by empirically and theoretically contributing to the strategic management of lithium-ion powered, vehicle electrification. Through the careful exploration of BEV end-of-life, this paper forecasts a dynamic end-of-life stockpile of lithium-ion batteries, using the UK as a case study. By establishing the ‘dynamic stockpile’ as the central problematique, this paper then describes various technical challenges, business model implications and policy debates around reuse, recycling and disposal that countries will have to contend with as first generation BEVs begin to enter technological obsolescence. While innovation and technological progress are desirable, industry, governments and society must remain aware – and prepared – for the significant economic and environmental costs and opportunities associated with not only the diffusion, but also the waste generated by new technologies.

64 citations

Journal ArticleDOI
TL;DR: A review of DfX methods with recommended design stages for their use from the published literature and a thematic clustering for their application along with a maturity index for each Df X concept is provided.
Abstract: Despite the availability of numerous "Design for X (DfX)" concepts/methods, their application is challenging for two reasons: • because methods have been developed with different foci (e.g., manufacturing vs. quality), it is difficult to know how different methods complement each other • in what sequence and where at the design stage they should be applied. We address this challenge with a review of DfX methods with recommended design stages for their use from the published literature. We also provide a thematic clustering for their application along with a maturity index for each DfX concept.

60 citations


Cites methods from "Editorial Software Obsolescence—Com..."

  • ...The problem of software obsolescence has been addressed in Sandborn (2007) by considering mitigation, downgrade, redevelopment, requalifying, rehosting, media management and case resolution when the software is not capable with the complex system....

    [...]

Journal ArticleDOI
TL;DR: In this paper, the authors explore the potential of information systems (IS) for supporting circular material flows in the context of a circular economy, and propose directions for IS research that develop knowledge of how IS can help understand and enact circular material flow to intensify and extend use of products and components and recycle waste materials.
Abstract: One of today's grand societal challenges is to replace the current ‘take‐make‐waste’ economic model with a circular economic model that allows a gradual decoupling of economic activities from the consumption of finite virgin resources. While circular economy (CE) scholars have long lauded digital technologies such as sensors, distributed ledgers, or platforms as key enablers, our own community has not fully explored the potentials of information systems (IS) for a CE. Considering recent technological advances in software and hardware and our history of helping address wicked challenges, we believe the time is ripe to mobilise IS scholarship for a CE. Our findings from an interdisciplinary literature review show that research has primarily examined IS potentials for increasing efficiency of isolated intra‐organisational processes while neglecting the larger sustainability potential of IS to establish circular material flows—that is, slow down and close material loops across entire product lifecycles. In response, we propose directions for IS research that develop our knowledge of how IS can help understand and enact circular material flows to intensify and extend use of products and components and recycle waste materials. Our directions offer pathways to building and evaluating the problem‐solution pairing that could characterise a prolific CE‐IS relationship.

43 citations


Cites background from "Editorial Software Obsolescence—Com..."

  • ...…such as dematerialization have received some scholarly attention (Ryen, Babbitt, Tyler, & Babbitt, 2014), negative impacts such as faster obsolescence of interdependent software and hardware (Ixmeier & Kranz, 2020; Jenab, Noori, Weinsier, & Khoury, 2014; Sandborn, 2007) are under-researched....

    [...]

References
More filters
Journal ArticleDOI
TL;DR: This article presents a methodology for performing optimum design refresh planning for sustainment-dominated electronic systems based on forecasted technology obsolescence and a mix of Obsolescence mitigation approaches ranging from lifetime buys to part substitution.
Abstract: Many technologies have life cycles that are shorter than the life cycle of the product they are in. Life cycle mismatches caused by the obsolescence of technology (and particularly the obsolescence of electronic parts) results in high sustainment costs for long field life systems, e.g., avionics and military systems. This article presents a methodology for performing optimum design refresh planning for sustainment-dominated electronic systems based on forecasted technology obsolescence and a mix of obsolescence mitigation approaches ranging from lifetime buys to part substitution. The methodology minimizes the life cycle cost by determining the optimum combination of design refresh schedule for the system (i.e., when to design refresh) and the design refresh content for each of the scheduled design refreshes. The analysis methodology can be used to generate application-specific economic justifications for design refresh approaches to obsolescence management.

118 citations


"Editorial Software Obsolescence—Com..." refers background in this paper

  • ...…software terminates: The original supplier no longer sells the software as new (end-of-sale) The inability to expand or renew licensing agreements (legally unprocurable) Software maintenance terminates - the original supplier and/or third parties no longer support the software (end-of-support) 3....

    [...]

Journal ArticleDOI
TL;DR: An initiative to develop an affordable, systematic approach to dealing with obsolete electronic parts and developing reliability models for commercially manufactured electronics used in defense systems is being launched.
Abstract: The US Air Force has launched an initiative to develop an affordable, systematic approach to dealing with obsolete electronic parts. In addition to management and reengineering tools, the initiative is developing reliability models for commercially manufactured electronics used in defense systems.

70 citations


"Editorial Software Obsolescence—Com..." refers background in this paper

  • ...These costs may include tracking various resolution metrics, version control, and database management....

    [...]

Proceedings ArticleDOI
13 Feb 2006
TL;DR: This paper reveals the Obsolescence problem in development, integration, test, production, and program management environments; a different perspective compared to the typical focus on obsolescence risk management and mitigation in the end-user, operational environment.
Abstract: Software is the primary focus of integration efforts for development of open architected, scalable, adaptable solutions in today's defense systems of systems. Unfortunately, successful software vendors obsolete their own product versions to maintain the pace with the market, without regard for the military need for continued support or expandability. Recognized by many professionals as being of equal gravity as the hardware obsolescence issue, software obsolescence has to-date not enjoyed the same level of visibility. This paper reveals the obsolescence problem in development, integration, test, production, and program management environments; a different perspective compared to the typical focus on obsolescence risk management and mitigation in the end-user, operational environment. Despite the portfolio of methods implemented for the effective management of COTS hardware obsolescence on a growing number of military programs, the software obsolescence problem is not being managed or mitigated. Could software obsolescence become more overwhelming than the hardware obsolescence dilemma?.

41 citations

01 Jan 2007
TL;DR: This paper describes the creation of a taxonomy and evaluation criteria for organizing and assessing DMSMS tools, databases, and services to lay the ground work for constructing an ontology that will be necessary to achieve webcentric, enterprise-wide D MSMS management solutions.
Abstract: This paper describes the creation of a taxonomy and evaluation criteria for organizing and assessing DMSMS tools, databases, and services. These activities are useful in the short term to assess the state of the present DMSMS management tools and the gaps that may be present within them; and necessary in the longer term to lay the ground work for constructing an ontology that will be necessary to achieve webcentric, enterprise-wide DMSMS management solutions.

9 citations


"Editorial Software Obsolescence—Com..." refers background in this paper

  • ...Analogously, hardware obsolescence can be categorized similarly to software obsolescence: functional obsolescence in hardware is driven by software upgrades that will not execute correctly on the hardware (e.g., Microsoft Office 2005 will not function on a 80486 processor based PC); technological…...

    [...]