Component Obsolescence Management: From EOL Notice to BOM-Level Response

What component obsolescence is

Component obsolescence is the point at which a part is no longer produced or recommended, forcing a sourcing or design response. Managing it systematically is the subject of an international standard, IEC 62402 (Obsolescence Management), which defines policy, an obsolescence-management plan, and resolution strategies — and is adopted for use by the US Department of Defense.

Obsolescence rarely arrives without warning. It is signaled by lifecycle-status changes and by formal notices — and the teams that handle it well are the ones that see those signals early and route them to the right owner.

Lifecycle stages, NRND, and EOL

Manufacturers publish a lifecycle status for each part. Texas Instruments, for example, uses the stages PREVIEW → ACTIVE → NRND → LAST TIME BUY → OBSOLETE. Two stages matter most for risk:

• +NRND (Not Recommended for New Designs): still available for existing designs, but the manufacturer recommends an alternate for new ones — an early warning.
• +EOL / OBSOLETE: the part is being or has been discontinued and will no longer be produced.

EOL notices, PDNs, last-time-buy, and last-ship dates

Discontinuation is communicated through a product discontinuance notice (PDN), issued under JEDEC J-STD-048. A PDN typically defines two deadlines: a last-time-buy (LTB) date, the cutoff to place final orders, and a last-ship date, the last date the manufacturer will ship.

These dates are the action triggers. Miss the last-time-buy window and your options narrow to redesign or the broker market — so the notice has to reach the right owner with enough runway to decide.

BOM exposure: which products are affected

A lifecycle change only matters if it touches something you build. BOM exposure analysis answers “which of our products and assemblies use this part?” by matching the affected part numbers against your active bills of materials and revisions.

Without it, a discontinuation is just a notice in an inbox. With it, it becomes a specific, ownable list of affected products and deadlines.

Second-source evaluation and internal response

Once exposure is known, the response is a decision: place a last-time-buy bridge, qualify a second source or alternate, accept the change, or redesign. Each needs an owner, a deadline, and a record of what was decided and why.

This is where many teams struggle — not in finding lifecycle data, but in routing each signal to a person and tracking the response to closure. A clear owner and an auditable trail are what turn obsolescence data into managed risk.

Where PCNshark fits

PCNshark focuses on the PCN and PDN operational workflow: it takes the change and discontinuance notices you receive, extracts the affected parts and key dates (including last-time-buy and last-ship), matches them against your BOMs to show exposure, and lets you assign an owner and track the response as an auditable record.

It is deliberately not a complete obsolescence suite. PCNshark does not forecast EOL across your component base, monitor distributor availability, or run compliance reporting — for those, a lifecycle-data provider or a broad component-intelligence platform is the right tool, and PCNshark can run alongside it as the operational layer for acting on notices.