Last Time Buy Isn’t a Long-Term Solution: Managing Obsolescence Risk in Legacy Systems

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 the assumptions break—and the problem comes back under worse conditions. 

In practice, last time buys rarely behave as planned. Inventory runs out earlier than expected—or sits unused while requirements shift. Storage costs rise. Shelf life and integration constraints become limiting factors. And when demand diverges from the forecast, the program is forced back into the same scramble it thought it had already solved. 

The issue isn’t the last time buy—it’s treating it as a solution instead of a temporary position. 

 

Why Last Time Buys Break Down 

Forecasting Breaks as Programs Evolve 

Even the most disciplined programs cannot perfectly predict usage across long lifecycles. Demand changes as customers request new production—or cancel what was forecasted. Failure rates shift as operational usage changes and systems age. Deployment timelines accelerate or delay far beyond original expectations. 

What begins as a well-modeled forecast becomes misaligned with reality. Inventory is either insufficient when needed—or excessive when conditions change. 

In both cases, program readiness is impacted, and the cost and timeline to recover are significantly worse than before. 

 

Inventory Doesn’t Equal Sustainment 

Owning parts does not guarantee support. 

Components still need to be tested, integrated, repaired, and validated within the system. Repair and test procedures, integration and software support processes, and configuration knowledge must be preserved. Suppliers, knowledge, and equipment must remain viable to ensure that inventory can actually be used. 

Without that infrastructure, inventory becomes static value—not operational capability. 

 

The Escalation Pattern 

When last time buys are treated as the solution, the pattern is predictable. 

Inventory is consumed faster than expected.
Demand shifts away from what was purchased.
Storage and obsolescence risk accumulate.
Eventually, availability gaps emerge. 

At that point, readiness degrades, delivery commitments slip, and escalations accelerate. Engineering and supply chain are pulled back into reactive mitigation—often at much higher cost and with fewer options than during the original buy window. 

The program ends up solving the same problem twice—once in planning, and again under chaos. 

At that point, the program is no longer managing obsolescence—it is reacting to loss of availability. 

 

What Changes When Sustainment Is Planned 

Last time buys are not inherently wrong—they are incomplete when used in isolation. 

When integrated into a broader sustainment strategy, they become one tool within a controlled system rather than a one-time attempt to eliminate risk. This replaces one-time mitigation with a structured sustainment approach—preventing risk from being pushed into a future where options are fewer, costs are higher, and readiness impact is greater. 

Sustainment planning changes how risk is managed across the lifecycle: 

• Demand is continuously monitored and adjusted instead of assumed upfront 

• Inventory is tied to validated test, repair, and configuration capability 

• Supply options remain open through authorized and flexible sourcing paths 

• Risk is distributed and managed over time instead of deferred into a single event 

The result is not the elimination of obsolescence—but control over how and when it impacts the program. 

 

Sustainment Is Not a Transaction 

At its core, a last time buy is a transaction. Sustainment is a system. 

Treating a transactional event as a complete strategy creates false confidence—and eventual disruption. Treating it as one component of a broader sustainment approach creates control. 

This is a leadership decision:
whether to absorb risk up front and hope it holds, or manage it deliberately across the life of the program. 

 

Final Thought 

Last time buys don’t eliminate risk. They shift it. 

Without a sustainment strategy behind them, they delay and amplify disruption rather than prevent it. 

With the right structure, they become the starting point for long-term control. 

 

GDCA helps organizations turn last time buys into part of a controlled, authorized sustainment strategy—so availability remains predictable, engineering stays focused, and programs avoid returning to reactive solutions under pressure.