Skip to main content
Unstrat
Use the up and down arrows to move through results, Enter to open, Escape to close.

Obsolescence management

The platform will outlive its parts. Plan for the parts.

Obsolescence management · Land (Land Domain) · Unstrat

What it is

Obsolescence management is the discipline of keeping a system fielded once the components, sub-suppliers and test equipment inside it stop being made. A frigate, an aircraft or a missile serves for decades. The circuit boards, connectors and instruments inside it are commercial electronics with a life measured in a few years. Obsolescence management is the work of closing that gap on purpose, before it closes a squadron.

How it is employed

Think of obsolescence on two horizons. Ahead of the problem, a programme office watches component roadmaps, catches last-time-buy notices while an order can still be placed, and decides whether to stockpile, redesign or re-host. Every obsolete item forces a choice between a last-time buy, a re-host onto current hardware, or a re-buy of a modern equivalent, and each answer carries a different cost, risk and lead time. That planning is a buyer discipline, and the framing here is offered as guidance for it. Once the problem has landed, there is engineering to be done, and that is where the mapped capability sits: reverse-engineering a legacy assembly or a dead test bench so a depot can keep certifying parts long after the original vendor has gone.

Why it matters now

This is DMSMS thinking: diminishing manufacturing sources and material shortages, the slow attrition that retires a capability without a shot fired. It bites hardest on the test equipment nobody thinks about until it dies, the bench that certifies an avionics box or a weapons-system module, built on instruments and interfaces that went out of production a decade ago. When that bench fails, the depot cannot pass parts, and a fleet quietly stops being airworthy. Buyers who depend on a distant vendor to keep old lines running are betting their availability on someone else's commercial appetite for legacy support.

Procurement & integration

Obsolescence is cheapest to plan for at the point of purchase and most expensive to confront in a crisis, so the sensible time for a buyer to scope it is before a contract is signed. What Unstrat delivers today is the sharp end of that: in-country engineering that reverse-engineers and rebuilds the automated test benches a fleet depends on, so a depot keeps testing when the discontinued bench dies and the original vendor has moved on. That work is accountable to the buyer rather than to a foreign vendor's willingness to keep an old line alive. The broader obsolescence plan, with component roadmaps and last-time-buy triggers, is something to agree per programme rather than a fixed service assumed here.

Sourcing routes compared

ConsiderationMajor-power primeIndependent principal via Unstrat
Legacy test equipmentDepot stops certifying parts when a discontinued bench dies and the vendor has moved onDying benches reverse-engineered and rebuilt in-country so the depot keeps testing
When obsolescence is confrontedSurfaces as an availability crisis mid-life, with no one accountable for the fixThe engineering to rebuild a dead bench is available in-country rather than dependent on a distant vendor
Political conditionsDisclosure rules, re-export restrictions and upgrade approvals held by a foreign governmentIndependent, non-aligned origin, accountable to the buyer's flag
SustainmentSupport tied to the supplier's home market and political relationshipSustainment, spares and training delivered in-region for the life of the system

Comparison is qualitative. Detailed specifications are shared under briefing once the export-control position for your market is confirmed.

Delivered by

View all →

Questions buyers ask

What is obsolescence management in defence?

It is the discipline of keeping platforms and munitions serviceable when the parts, materials and electronics they were built from stop being made. A component going out of production does not retire the ship, aircraft or vehicle around it, so the work is finding, qualifying and sustaining substitutes without disturbing the wider system. It is a sustainment problem before it is a purchasing problem.

See: Non-destructive testing capability

Why does obsolescence matter for a national force?

Fleets bought over decades outlive the supply chains that built them. When a part is no longer made, a force either grounds equipment, pays a foreign prime whatever the last-time buy costs, or finds its own way to keep the platform running. The first two hand the readiness decision to someone else, which is the sovereignty question underneath what looks like a spares problem.

See: How we deliver programmes

Is obsolescence a supply problem or a design problem?

Both, and treating it as only one is where programmes come unstuck. A discontinued part is a supply problem the day the vendor stops shipping. It becomes a design problem the moment a substitute changes fit, form or function and the surrounding system has to be re-qualified. Planned obsolescence management addresses the second before the first forces a rushed answer.

See: Non-destructive testing capability

Obsolescence management for a mixed, ageing fleet without original-manufacturer support

This is the common case: equipment acquired from several sources, some of it past the point where the maker still supports it. The work is keeping those platforms serviceable through qualified substitutes and re-manufacture rather than waiting on a supply line that has closed. We scope it around the fleet a force actually operates, not the one a single vendor prefers to support.

See: Non-destructive testing capability

How does re-manufacturing an obsolete part fit with sovereign component supply?

They are the same argument seen from two ends. Independent machining can produce a part a foreign prime no longer sells, and inspection certifies it is safe to field without shipping samples abroad. A force that owns both can answer an obsolescence notice by making the part rather than accepting a last-time buy on the vendor's terms.

See: Tungsten components capabilityNon-destructive testing capability

Managing electronics obsolescence when the original chips are no longer made

Electronics age fastest, and a discontinued chip can strand an otherwise sound platform. Part of the answer is design that expects change: capability that lives in software and hardware built to be updated rather than replaced ages more gracefully than a fixed board. Where a substitute part is needed, the surrounding system still has to be re-qualified, which is why the planning matters as much as the sourcing.

See: Space-proven electronics capabilitySoftware-defined radios capability

Obsolescence management that keeps fleet condition data out of a foreign prime's hands

Running life-extension through a foreign prime's service network means that network learns what is failing, how often, and how close the fleet is to the edge. Handling substitution, re-manufacture and certification nationally keeps that picture national. The readiness of a force is exactly the thing a supplier and an adversary should not be able to read from its spares orders.

See: Where condition data lands

Building a national obsolescence programme rather than buying spares case by case

Case-by-case buying reacts to each end-of-life notice as a fresh emergency. A programme reads the fleet, flags what is going out of production before it does, and lines up qualified substitutes or re-manufacture in advance. We structure that as one accountable engagement so a force plans obsolescence rather than being surprised by it.

See: How we deliver programmes

Our supplier has issued a last-time-buy notice on a critical part. What are our actual options besides paying it?

A last-time buy answers the next few years and leaves the same problem waiting at the end of the stockpile. The alternatives are qualifying an equivalent part, re-manufacturing the original against the drawings, or redesigning the sub-assembly so it no longer depends on the discontinued item. Each needs the substitute proven and the surrounding system re-certified. We scope which route fits the platform and the fleet rather than defaulting to the stockpile.

See: Tungsten components capabilityNon-destructive testing capability

How much does an obsolescence management programme cost compared with just buying more spares?

The site does not publish figures, and a number quoted without a defined fleet and scope is guesswork. What we can say is what drives the cost: how many parts are near end of life, how deeply each is embedded in a larger system, whether a substitute needs re-qualification, and how much of the capability a force wants to own rather than rent. A last-time buy looks cheaper until the stockpile runs out and the part still is not made, at which point the deferred cost returns with interest.

See: How we deliver programmes

We keep platforms in service for decades. How does obsolescence management change how we should specify new equipment?

Service lives measured in decades make the supply chain behind a platform part of the specification, not an afterthought. Favour designs that expect change, capability in software, hardware built to be updated, and parts with a documented substitution path, over sealed systems that depend on one vendor staying in business. Writing supply continuity and substitution rights into the tender is cheaper than discovering their absence a decade in.

See: Software-defined radios capabilityThe evidence we stand behind

Where does obsolescence management sit alongside inspection and sovereign manufacturing when we are building national sustainment?

They form one chain. Inspection tells a force what is wearing out and what is safe to keep flying; independent manufacture produces the substitute when the original supplier has stopped; obsolescence management is the planning that connects the two before an end-of-life notice forces a rushed decision. A nation building sustainment usually needs all three under its own control, which is why we scope them as related capabilities rather than isolated buys.

See: Non-destructive testing capabilityTungsten components capability

If relations with a foreign prime deteriorate, what happens to a fleet that depends on their obsolescence support?

That is the risk a national programme is built to answer. When the substitute, the drawings and the qualification data all sit behind a foreign prime, a policy shift can stall support at the moment of greatest need. Holding the substitution and re-manufacture chain nationally keeps a fleet answerable to the buyer's flag rather than the supplier's foreign policy.

See: The independent route against foreign-held support

How do we qualify a substitute part without grounding the platform it goes into?

Qualification runs as a staged process: prove the substitute against the original drawings and acceptance criteria, certify it with inspection, then phase it in once the evidence is accepted. Because the work is governed and documented rather than improvised under deadline, it can run alongside the platform's normal service so the substitute is proven before the fleet depends on it. The site does not publish component-level tolerances here, so specify them in the tender.

See: Non-destructive testing capabilityHow we deliver programmes

Should we buy obsolescence support as a service, or build a national capability to run it ourselves?

It turns on how much of the readiness decision a force wants to own. A service keeps platforms running without building the estate, and suits a buyer content to depend on the provider staying willing. A national capability puts the substitution, re-manufacture and certification chain under the buyer's own flag, which is the point when readiness is a sovereignty question. We scope the model to the fleet, the staffing reality and the ambition rather than selling one answer.

See: How we deliver programmesDiscuss a national requirement

Contact us

Tell us the requirement. Specifications and the export position are confirmed in briefing, not published here.