30-min call with RobBook a proof-of-concept call
Job 04 · Last-time-buy notices

// Electronics manufacturers · Last-time-buy notices

Last-time-buy notices, traced to every assembly and order they put at risk.

For EMS providers and contract electronics manufacturers. One job, tested on notices your team already worked. Each AI draft matches a component maker's end-of-life or change notice to every assembly that uses the part, the open orders behind it and the dates that matter, then drafts a note to each OEM for your program manager. Your buyers and engineers decide what to buy and what to change.

Book a proof-of-concept call30 minutes with Rob
Past notices
20 to 30
Matched on
Manufacturer part number
System access
None

// The one job

A notice arrives. The assemblies at risk come back.

A maker announces that a part is going away, or that its die, package or plant is changing. The notice names the maker's own part numbers and a few dates, and says nothing about your customers. Before the last order date passes, someone has to find every assembly that uses the part, the orders still to ship, the stock and open POs, and every OEM who needs to hear.

In the proof of concept, AI reads copies of notices your team already handled and drafts the impact list and the OEM notes your team would have written: each assembly and revision, the demand still open, the dates from the notice and any replacement it names, with the record behind every line. Your reviewer sets it beside what your buyers and program managers actually did.

Discontinuance noticeFrom the component maker
Notice number
Last order date
Last ship date
Stated replacement
Maker part no.PackageStatus
Invented notice, no real part
Matched to your BOMs,
orders and stock
Assemblies at riskFor your buyer and engineer
Assemblies and revisions
Orders past last ship
Stock and open POs
Note to each OEM
AssemblyOpen demandCustomer
Invented list, for illustration

// What the notice leaves out

Where a last-time buy gets missed

Two kinds of notice run on different clocks. A discontinuance notice ends a part. JEDEC's JESD48, Product Discontinuance, set the floor in its December 2011 revision: at least six months from the notice to place final orders and 12 months from the notice for final shipments. JEDEC has since replaced it with J-STD-048, the notification standard for product discontinuance, and notices still cite either one. A change notice keeps the part but alters it. Under J-STD-046, the customer notification standard for product and process changes, a change that affects form, fit, function, quality or reliability counts as major, and one maker's procedure built on it sends notice at least 90 days before the changed part ships, 180 for automotive parts. A change notice may also give the last date the unchanged part will be made, which matters to any OEM that hasn't approved the change.

The notice speaks in the maker's part numbers. JESD48 requires only two things in a discontinuance notice: the date for placing last purchase orders and the affected supplier part numbers. Your part numbers are optional. It counts as a customer only someone who bought from the supplier in the past two years or has an agreement or request covering such notices, and it has authorized distributors pass the notice on. So a part bought through a distributor reaches you from that distributor, a part bought from a broker may never reach you at all, and the notice for a part an OEM consigns goes to that OEM, which bought it. The draft matches every number the notice lists through your approved vendor list to your own part numbers, and lists consigned lines apart for the OEM.

Exposure is more than a where-used list. For each assembly the draft shows the revisions that use the part, whether it is the primary choice or an approved alternate, the quantity per board, open customer orders and forecast with their ship dates, stock on hand and open POs. It sets that demand against the last order and last ship dates and marks every assembly whose orders run past them. A replacement named in the notice is recorded as the maker's suggestion and checked against your approved vendor list and the OEM's approved list for that assembly. JESD48 also has the supplier help locate an alternate source, and on request discuss a transfer of technology and tooling.

Makers write their own rules on top of the standards. Texas Instruments publishes a schedule of 12 months for the last order and six more to take final delivery, and warns that a faster withdrawal can happen in rare cases. NXP's Product Longevity program holds listed parts for 10 or 15 years from launch, shows the date each one stays in the program until, and says a part is not discontinued automatically when that period ends; its usual end-of-life and change notice policies still apply. IEC 62402, Obsolescence management, was rewritten in 2019 as a standard with requirements, covering an obsolescence management plan, design choices that reduce obsolescence, and how resolutions are selected and carried out. The draft takes every date from the notice itself, never from a policy page.

Your reviewer. The owner names the person who knows your notice handling best, often a commodity buyer, a component engineer or a program manager. They hold each draft against what your team did: part numbers matched, assemblies and revisions found, demand counted against the dates, replacements checked and notes sent to each OEM. Include one notice that reached you through a distributor, one change notice, and one your team decided did not touch you.

// What you send

What your purchasing team gathers

Copies only
End-of-life and change notices
01

20 to 30 past notices as they arrived

End-of-life and change notices from makers and distributors, as emails, PDFs or portal downloads, with any replacement list attached. Add a few that turned out not to touch you.

02

What your team did with each

The where-used list your team built, the buy it placed or declined, and the note each program manager sent to an OEM.

03

BOMs, orders and stock from the time

BOMs with approved vendor lists, open customer orders and forecasts, inventory and open POs, exported from near each notice's date. Lists your team made back then will do.

04

An NDA before any file moves

Signed first, since BOMs and customer orders show what your OEMs build and in what volume. No login to your ERP, a distributor portal or a maker's notification account.

05

Look-alike notices, if files stay put

Where an OEM's terms keep its BOMs in your building, we build look-alike notices and BOMs with you that keep the same kinds of part numbers, dates and replacements.

// Before it starts

Settled before the first notice is copied

The owner and your purchasing lead agree on each of these before any notice or BOM is shared.

Before the proof of conceptOwner decides
Your reviewer
Named by the owner, often a commodity buyer or component engineer
Success criteria
In writing: assemblies that must be found, and how OEM notes are scored
Records
BOMs, orders and stock as they stood on each notice's date
Price
A range for live notice review, given before the test
Notices
Commercial and industrial programs, end-of-life and change notices alike

// How it's scored

Your team's response, beside the draft

Notice by notice
assembly by assembly
Compared on the same noticesWhat your team didThe AI draft
Time from notice received to impact list ready for reviewFilled in from your noticesFilled in from your notices
Maker part numbers matched to your parts and approved vendor listFilled in from your noticesFilled in from your notices
Assemblies and revisions using the part, alternates includedFilled in from your noticesFilled in from your notices
Open orders and forecast running past the last ship dateFilled in from your noticesFilled in from your notices
Stock, open POs and consigned lines countedFilled in from your noticesFilled in from your notices
Stated replacement recorded and checked against approved listsFilled in from your noticesFilled in from your notices
Notes to each OEM, against the ones your program managers sentFilled in from your noticesFilled in from your notices
No numbers yet. Every cell stays blank until drafts from your own past notices have been scored.Your reviewer marks each row, and that call holds.

// After a yes

About 30 days on new notices

After a yes, every new end-of-life or change notice gets a draft impact list and OEM notes as it arrives, for about 30 days.

Your buyer decides whether and how much to buy and places every order, your engineer judges each replacement, and your program manager edits and sends each note. Nothing moves in your ERP or reaches a customer until a person does it, and scoring runs through the month.

// Later, ranked

Where notice review could lead

Options to weigh, not a plan
Each one live before the next
  1. 01

    Product change notices

    A maker's change to a die, package, plant or material matched to the assemblies it reaches, with each OEM that must approve it listed.

    Next
  2. 02

    Compliance declarations

    Customer RoHS, REACH and minerals requests answered from your suppliers' declarations, for your quality lead to sign.

    Then
  3. 03

    ECOs for approved replacements

    The engineering change each approved replacement needs, with the jobs, stock and open POs it touches listed for your engineer.

    After that

// One hard limit

It never places a last-time buy or tells an OEM anything.

How much to buy, whether to accept a replacement and what each OEM hears are decisions for your buyers, engineers and program managers. The draft works on copies, shows where each line came from and stops there: no order, and no message to a maker, a distributor or a customer. Only commercial and industrial programs come into the test.

Notice review is priced as a job of its own: a range before the test, then a fixed price before you sign.

The range depends on how many notices reach you in a month and how many assemblies and OEMs a typical notice touches.

// Questions

Last-time-buy questions from EMS buyers

Will it work out how many parts to buy?
It shows the demand your open orders and forecast hold through the last ship date, assembly by assembly. The quantity, and whether to buy at all, stay with your buyer and the OEM.
Notices reach us by email, PDF and distributor portals. Can it read them all?
Yes, from copies. Emails, PDFs and spreadsheets come in as files, and portal notices as downloads or screenshots, because the test never signs in anywhere. A notice it can't read clearly goes to your reviewer.
Does it look up lifecycle status online?
Not in the test. It works from the notices you received and the records your team kept, so it is judged on what your team knew at the time.
Will it email our OEMs?
No. It drafts each note for your program manager, who edits it and decides whether it goes out. Nothing reaches a customer or a supplier from the test.
What about parts our OEMs consign to us?
They are listed apart, with the assemblies and orders they reach, because the OEM owns and buys that stock. Your program manager decides what to tell that OEM.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Test it on notices your team already worked.

A 30-minute call with Rob. Expect questions about your company and role, which job to test first and roughly how many end-of-life and change notices land each month. Send no BOMs or order data until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.