Hardware Supply Chain & Sourcing POST 9 OF 16

Every component in your product will eventually be discontinued. The question is whether you find out with enough time to manage the transition or whether you find out when your factory tries to place a purchase order and gets an error message.

Component obsolescence is one of the most underappreciated risks in hardware supply chain management, and it is particularly insidious because it is entirely predictable — semiconductor manufacturers publish end-of-life notices in advance, typically 12 to 24 months before a component is discontinued — but still catches companies unprepared with surprising regularity. The reason is structural: the teams responsible for managing obsolescence — supply chain and procurement — often don’t have deep visibility into the product designs, while the teams responsible for the product designs — engineering — often don’t have a systematic process for monitoring component lifecycle status. The result is a gap that nobody owns, and components that move from active to last-time-buy to obsolete without triggering the response they should.

When a component goes end-of-life, the manufacturer issues a Product Change Notice — a PCN — specifying the last date on which orders for the component will be accepted and the last date on which it will be shipped. This notice triggers a decision process for every company that uses the component: do we place a last-time-buy order to stock enough inventory to cover the product’s remaining production life, or do we redesign the product to use an alternative component? Both options have significant cost and time implications. A last-time-buy order for a component used in a product with a 5-year remaining production life requires forecasting 5 years of demand and purchasing all of it at once — tying up capital in inventory that will sit for years and carrying the risk that demand forecasts are wrong in either direction. A redesign requires engineering time, new qualification activities, potentially new regulatory approvals, and a production transition that must be managed carefully to avoid introducing quality issues.

The financial exposure from obsolescence mismanagement can be severe. A company that fails to respond to a PCN in time and misses the last order date has no authorised source for the component. Its options are the spot market — with all the price and quality risks that entails — or an emergency redesign under time pressure, which is the most expensive and highest-risk version of a redesign. Companies have been materially damaged by this scenario: production lines stopped, shipments missed, redesigns conducted in crisis mode, all because a component lifecycle notice was not properly tracked and acted on.

The right approach is systematic: a process that monitors the lifecycle status of every component in the BOM on a regular basis, flags components that are entering end-of-life status, triggers an evaluation of last-time-buy versus redesign options, and escalates the decision to the appropriate level based on the financial and strategic significance of the choice. This process should be owned clearly — by a specific person or team — and should be integrated with the product roadmap, because the decision of whether to redesign for an obsolete component is often inseparable from questions about the product’s future development direction.

For investors and executives, the obsolescence question is a straightforward one to ask: what is the process for monitoring component lifecycle status across all active BOMs, and when was the last time an end-of-life notice triggered a formal response? A company that can describe a functioning process and give you a recent example of it working correctly has this risk managed. A company that responds with uncertainty — or that discovers, when you ask, that several of its critical components have recently entered last-time-buy status that nobody has responded to — has a live financial exposure that deserves immediate attention.