Critical Thoughts on Embedded Sustainment & Obsolescence
Critical Thoughts is where we share hard-won insights from the field. It’s not a blog—it’s a working record of what we’ve learned supporting sustainment, managing obsolescence, and partnering with OEMs on legacy challenges that don’t fit the usual models.
These are the strategic, technical, and sometimes messy realities behind keeping embedded systems mission-ready over the long haul.
Legacy product support is one of the biggest challenges facing OEMs today. As customers continue relying on aging systems, manufacturers must balance long-term support obligations with innovation, engineering resources, and product portfolio growth. The question isn’t whether legacy products should be supported—it’s how to do so without slowing the future of your business. You built a great product, and…
The Misunderstanding Around Innovation in Legacy Systems Legacy systems sustainment is often overlooked as a form of innovation. While innovation is commonly associated with new technology, new platforms, and new product development, some of the most valuable innovation occurs when organizations preserve proven operational capability for decades. But in long-lifecycle industries, some of the most valuable innovation…
As a Program Lead or Procurement Officer, you are often caught in an impossible bind. You are faced with a “false binary” for your legacy products. On one hand, you can choose to Sustain them, which forces you to pull your best engineers off their NPI “fire” to go fight a legacy “fire drill,” draining resources and…
The Illusion of “Having the Data” For many organizations, legacy systems sustainment begins with a simple assumption: acquire the Technical Data Package (TDP), transfer the data internally, and supportability will follow. On paper, it feels logical. The design exists. The documentation exists. The product should now be reproducible. But many organizations discover the same reality…
For Embedded OEMs, the risk of legacy isn’t just technical—it’s reputational. When aging products remain in your portfolio without a clear plan for support, the brand you’ve worked so hard to build is what takes the hit. Strategic customers expect continuity. When legacy products fail in the field or can’t be supported, they don’t just blame the product—they question the company. Legacy Isn’t Neutral Holding on to legacy…
Why last time buys fail—and how a structured sustainment strategy protects long-lifecycle programs from recurring supply chain disruption When a critical component goes obsolete, the response is immediate: forecast demand, secure funding, and execute a last time buy before supply disappears. It feels like control—the risk is identified, the inventory is secured, and the issue is closed. Until…
If you treat legacy like a transaction, you’ll keep paying for it. Many OEMs think of end-of-life and sustainment transfers as a simple handoff. You document the product, pick a vendor, issue a PO, and move on. But what happens when that “simple” PO fails an audit? Or when a critical DoD program is grounded because that…
Managing Product Portfolios in Uncertain Markets: Why Now’s the Right Time to Transfer Aging Product Lines In volatile markets, every product in your portfolio should justify its place. If legacy lines aren’t delivering growth or strategic value, why are you still carrying them? For Embedded OEMs, the challenge isn’t just about cutting costs—it’s about ensuring that every product in the portfolio actively…
What Happens When Embedded OEMs Keep Legacy Sustainment In-House? A quiet erosion that often ends in a sudden catastrophe. The risk isn’t always a single, dramatic event; it’s a slow, silent drift. Systems degrade. Critical knowledge walks out the door. Customers grow frustrated. And leadership is often unaware of just how fragile their internal support has become until it’s too late. …
The Cost of Waiting: Why Legacy Failures Are Always More Expensive Later Legacy systems rarely fail all at once. They fail quietly—and expensively. A component reaches end-of-life. A supplier exits the market. Test capability erodes as documentation ages and people move on. None of it feels urgent in isolation. But together, these small degradations create something far…