Component risk, end-of-life and what ships with it
An end-of-life notice is only useful if somebody can answer, that same day, which products contain the part and how much time the stock buys. That is a matching problem and a traversal problem, and both are solved here rather than in a buyer's inbox.
What it is, and what it is not
Component risk is the ingestion of external lifecycle data — from SiliconExpert, Z2Data, Accuris and Octopart — matched against the manufacturer parts on your approved manufacturer list, and scored against the products those parts actually ship in.
It is not a subscription to a parts database with a search box. The data is widely available; what is scarce is the join. A feed knows a manufacturer part is going end of life. It has no idea that you buy it, under which internal part number, in which three products, two of which are shipping.
It is also not a replacement for your buyers' judgement. The system produces the join and the exposure; deciding whether to last-time-buy, redesign or qualify an alternate is a commercial decision made by people with a budget.
The mechanism: the join is the product
Matching runs on manufacturer part number against the AML entries attached to your internal parts, not on descriptions and not on internal numbers. An internal part typically has two or three approved manufacturer parts behind it, each with its own lifecycle state, and the risk belongs to those rather than to the internal number.
That distinction is why a house number matches nothing, correctly. SPC-4410 is meaningful inside your organisation and invisible to every feed on earth. Rather than guessing at a similar-looking part, the system surfaces it as unmatched for a person to resolve — because a wrong match is worse than a missing one, and considerably harder to notice.
Where feeds disagree, the disagreement is shown rather than averaged. Two sources saying active and one saying not-recommended-for-new-designs is a meaningful signal, and collapsing it to a score throws away the only part a buyer would act on.
The failure it prevents
The manufacturer issues the notice in March. It reaches a distributor mailbox, which forwards to a person who left the company in January. Nobody malicious, nobody careless — just a routing that used to work.
In November the line stops. The replacement part has a sixteen-week lead time and a different footprint, so the board needs a revision, which needs a qualification, which needs a customer notification. A problem worth two hours in March costs a quarter in November.
The mechanism that prevents it is not a better inbox. It is that the notice arrives attached to the manufacturer part, which is attached to your internal part, which is in a resolved structure, which is in two shipping products — so the alert that reaches a human already says which products and how much runway the on-hand stock buys.
How it meets the rest of the product
Exposure is computed through resolved structures rather than stored ones, so “which shipping products contain this part” is a different and correct answer from “which structures mention it anywhere”. A part only present in a superseded revision is not a live risk and is not reported as one.
Supplier change notifications compute their own affected-product sets through the same path, so a notice from a supplier and a feed-driven end-of-life alert produce comparable answers rather than two views that disagree.
The Supplier Agent works this surface at the tier you set: summarising the week's notices, ranking exposure by shipping volume and runway, and drafting the change where an alternate is already approved on another product. Each claim cites the objects and revisions behind it.
Risk scoring stays four steps deliberately — ok, watch, at risk, critical. Engineers stop trusting a scale they cannot hold in their head, and a five-point scale invites arguments about the middle.
How it meets your ERP
Runway is the number people act on, and it comes from your ERP. On-hand quantity, committed stock, open purchase orders and lead time read back from NetSuite, SAP, Dynamics, Epicor or Acumatica, and sit alongside the engineering exposure so an alert reads as “three products, eleven weeks of stock, no alternate qualified” rather than as a status change.
The supplier record itself masters in your ERP — terms, pricing, the vendor part number a buyer transacts against — and renders read-only here. What Manufacturing PLM owns is which manufacturer parts engineering has approved and qualified for a given internal part. Those are two different questions and a single supplier field cannot answer both.
Nothing transactional is written. Manufacturing PLM does not raise a last-time-buy purchase order or reserve stock; it produces the exposure that makes those decisions well-informed, and the buyer makes them where they already work.
Where the boundary is
The system cannot see risk in parts it does not know about. A component consumed under a house number with no AML entry behind it has nothing to match against, and no amount of processing changes that — which is the practical argument for maintaining the AML rather than a feature gap to work around.
It also does not predict. Lifecycle data is what four commercial feeds report, with their disagreements visible. Manufacturing PLM does not forecast obsolescence, and a system that claimed to would be selling confidence rather than information.
Facts
| Feeds | SiliconExpert · Z2Data · Accuris · Octopart |
| Matched on | Manufacturer part number, against your AML |
| Unmatched | Surfaced for a person — never guessed |
| Disagreement | Shown, not averaged into a score |
| Exposure | Computed through resolved structures only |
| Scale | Four steps — ok · watch · at risk · critical |
| Runway | On-hand, committed and open orders, from your ERP |
| Never | Raises a purchase order, reserves stock, or forecasts |
Frequently asked
Why match on manufacturer part number?
Because that is what the feeds know. An internal part usually has two or three approved manufacturer parts behind it, each with its own lifecycle state, and the risk belongs to those. Matching on internal numbers or descriptions produces confident wrong answers rather than missing ones.
What happens to our house numbers?
They are surfaced as unmatched rather than matched to something similar. A house number is meaningful inside your organisation and invisible to every feed, and a wrong match is worse than a missing one because nobody goes looking for it afterwards.
What if two feeds disagree?
The disagreement is shown. Two sources reporting active and one reporting not-recommended-for-new-designs is a real signal, and collapsing it into a single score discards the part a buyer would actually act on. Averaging conflicting data is a way of hiding it.
How is exposure calculated?
Through resolved structures, so it answers which shipping products contain the part rather than which structures mention it anywhere. A component present only in a superseded revision is not a live risk, and reporting it as one trains people to ignore the alerts.
Where does the runway number come from?
Your ERP. On-hand, committed stock, open purchase orders and lead time read back read-only and sit next to the engineering exposure, so an alert says three products with eleven weeks of stock and no qualified alternate rather than announcing a status change.
Does it place a last-time-buy order?
No. Nothing transactional is written in either direction. Manufacturing PLM produces the exposure that makes the decision well-informed — which products are affected, how much runway the stock buys, and whether an alternate is already qualified elsewhere — and the buyer places the order where they already work.
Does it predict future obsolescence?
No, and a system claiming to would be selling confidence rather than information. What you get is what four commercial feeds report, with their disagreements visible, joined to the parts you actually buy and the products that actually ship with them.