End-of-life, EOL, is a manufacturer ending a part. A product change notice, a PCN, is the warning that should come first, and in 2025 it came for under half of the parts that ended.
At 16:20 a distributor notice arrives by e-mail: a memory part goes end-of-life with a last order date in March. Juno reads the manufacturer part number from the notice, matches it to item 7741-M2 in SAP S/4HANA and to the same part under its own number in the Oracle Fusion division, and finds it on nine active bills of materials.
The exposure is on the record within the hour: 14 weeks of stock at plant 1210 against 60 weeks of remaining demand to the end of production life, and one open purchase order line. One qualified alternate from Acme Components GmbH is already on the approved manufacturer list for a sister board. Juno drafts a last-time buy of 38,000 units worth $214,000 and a change request for the alternate.
D. Okafor, buyer, sees the requisition in his queue with the demand curve and the distributor’s allocation, and approves it at 16:50. The product engineer approves the alternate for qualification. On Monday the obsolescence board chooses the alternate for new builds and the buy for the rest, and the case record holds every step. showcase estate
The scale is a data vendor’s count, and it is large. Manufacturers discontinued over 620,000 electronic parts in 2025, about 150,000 more than two years earlier; 323,286 of them, 52%, reached end-of-life before any product change notice was issued, and 27% of the notices met the standard of JEDEC, the electronics industry’s standards body (Z2Data, 13 March 2026) 22. Components now last two to five years on average before discontinuation (Z2Data, 22 January 2026) 23.
The cost baselines are older, and they come from government surveys. Resolving one obsolete part cost a mean $5,234 as a life-of-need buy, $25,410 as a complex substitute, $1.09 million as a next-higher-assembly redesign and $10.3 million as a system replacement, across 4,562 reported issues (US Department of Commerce BIS, 2015) 25. An alternate source took 11 weeks and a redesign 42 to 64 weeks (US BIS, September 2010) 26.
Vendors sell pieces of the answer. Oracle ships a Component Replacement agent that reads part numbers from change notices, runs where-used and adds use-up detail to the change request (Oracle, 10 February 2026; Oracle, 30 July 2026) 5, 6. Propel One flags replacements from live quality and supply data, notifies engineers and triggers change orders, with Allegro MicroSystems an early adopter, on a single source (Propel, 9 October 2025) 14. SiliconExpert and Z2Data sell alerting, years-to-end-of-life forecasting and alternates (SiliconExpert, checked 23 September 2026) 24, and PTC Arena adds supply chain intelligence for risk visibility (PTC Arena, 11 August 2026) 18.
The adoption signal is indirect. Semiconductor executives put procurement and supply chain first for future generative AI deployments (KPMG, 19 March 2026, 151 executives) 50. 66% of manufacturing professionals say AI is mostly ineffective unless it can reach product data (ASSEMBLY, 25 August 2026) 15. The case for the platform is that a notice touches the data service, the product lifecycle management (PLM) system, two ERPs, the planning suite and the distributor portal, and each vendor’s agent sees one of them.
Notices arrive by e-mail from manufacturers and distributors or as alerts from a component data service, and a component engineer logs them in a tracker. The engineer matches each manufacturer part number to internal items in PLM and ERP, then runs where-used across active bills of materials at every plant. A planner pulls stock, open purchase orders and demand to the end of production life and works out the use-up date and the last-time-buy quantity.
The component engineer searches for alternates of the same form, fit and function and checks their qualification status. A buyer requests distributor quotes and checks allocation and lead time. An obsolescence review board chooses between last-time buy, alternate and redesign. A change order is raised, the approved manufacturer list is updated and the purchase order is placed. Weeks to months per case: 11 weeks for an alternate source and 40 for a complex substitute (US BIS, September 2010) 26, while half the parts reach end-of-life before a notice arrives (Z2Data, 13 March 2026) 22.
Illustrative weeks for a case done by hand; the 11-week and 40-week figures are US BIS, September 2010 26.
This is the use case where the platform’s map across systems does most of the work: the notice names a manufacturer part, the ERPs know it by internal item numbers, the PLM system by its own, and the exposure lives in stock, orders and demand across plants. The six stages below say how those would be joined, and who would approve the buy and the alternate.
| Row | Kind | What it tests or does | Data it reads | Then |
|---|---|---|---|---|
| 01 | Check | The manufacturer part matches an internal item on an active bill of materials | manufacturer part number, approved manufacturer list, BOM status | carry on; an unmatched part goes to the component engineer |
| 02 | Check | The lifecycle status is end-of-life, or the last order date falls inside 12 months | notice, data-service status, last order date | carry on |
| 03 | Action | Compute the exposure: stock and open orders against demand to the end of production life, per plant | stock, open purchase order lines, demand forecast, end-of-production date | row 04 |
| 04 | Action | Propose the qualified alternate with the lowest change cost; draft a last-time buy where an alternate is missing or takes longer than the notice window | alternate parts, qualification status, lead time, distributor quotes | row 05 decides the route |
| 05 | Limit | Requisition value against $25,000 and $150,000 | requisition value | under $25,000: the buyer’s queue · above: the buyer, and finance above $150,000 |
The policy sentence and the planning table it would compile to. Illustrative values; the mechanics are the product’s.
The market runs this from inform to draft-and-approve: the data services alert and forecast, one ERP vendor’s agent analyses and e-mails, and one PLM vendor’s flags, notifies and triggers change orders that people approve (2025 to 2026) 5, 14, 24. The blueprint designs the write-back roles at A2, with the buyer and the component engineer as named approvers: lifecycle and EOL trigger watch, long-lead material commitment and product change notice issuance at A2, the supply readiness scorecard at A3, and the two impact assessment roles at A3 because they read before anyone writes.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Every end-of-life or product change notice on a part in an active bill of materials is caught, sized and answered inside its notice window | The component engineering lead, in a sentence | New version |
| Data scope | Component data service, notice inbox, PLM items and manufacturer parts; SAP S/4HANA and Oracle Fusion material master, approved manufacturer list, stock, purchasing and demand; distributor portal | A. Novak, data lead | New version |
| Rules | The end-of-life policy and its planning table: exposure to end of production life; the qualified alternate with the lowest change cost; a last-time buy where the alternate is missing or late | The component engineering lead with the Planner Agent | New version, simulated first |
| Trigger | On each notice or feed alert; a nightly scan at 02:00 for lifecycle changes and years-to-end-of-life forecasts under two years on active parts | The component engineering lead | At once |
| Actions permitted | Open a case · write a change request to PLM · draft a requisition · update the approved manufacturer list after approval · block a part for new designs · notify a distributor · draft a PCN | The component engineering lead, owner | New version |
| Limits | Requisitions above $25,000 go to the buyer with the demand curve · above $150,000, finance as well · a buy covers demand to end of life plus 10% · confidence floor 0.85 on a part match | The component engineering lead and J. Harrison, finance | New version |
| Escalation | A part on a product in ramp, to the programme manager at once · an unmatched manufacturer part, to the component engineer · a failed write-back, to the owner | The component engineering lead | At once |
| Level | A2 Supervised with D. Okafor approving requisitions and the component engineer approving part matches and alternates | The engineering director | Up on evidence, down in one step |
| Feedback | The board’s choice against each recommendation is recorded and used | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Idea-to-Market lists the rest of the map for this chain.
| Measure |
|---|
| Notices caught against parts reaching end-of-life, baseline: 52% of parts reached end-of-life before a notice in 2025 (Z2Data) |
| Time from notice to resolution, baseline 11 to 64 weeks by path (US BIS, 2010) |
| Cost per resolution, baseline $5,234 to $10.3 million by path (US BIS, 2015) |
| Share of active bill-of-materials parts with lifecycle risk |
| Last-time-buy inventory value and later write-off |
| Line-down events caused by obsolescence |
Baseline notices caught against parts reaching end-of-life first, because it says whether the watch works at all: how many of last year’s end-of-life parts on active bills had a notice on record before the last order date, against the market count, where 52% of parts reached end-of-life before a notice 22. Time from notice to resolution follows, by path; the write-off on last-time-buy stock takes a year to read.
The nightly scan watches the data service’s lifecycle status and its years-to-end-of-life forecast on every active part, so a part that ends quietly still opens a case when its status changes or its forecast drops under the threshold.
The obsolescence review board or the product line manager, at the weekly review, with the exposure and the options on one page. Juno proposes; the choice is recorded against the proposal and used next time.
Against demand to the end of production life from the planning suite, plus the policy’s allowance, and against the distributor’s allocation. D. Okafor approves above $25,000 and J. Harrison above $150,000; the write-off a year later is read back against the buy.
The alternate is qualified and the last-time buy is placed. Twelve weeks before a launch, what else has to be true before the first production order can be released?
Every readiness item, from long-lead orders to part numbers and test program release, checked daily against its source, fixed within rules or routed to its owner.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.