Skip to content
Product data & engineeringElectronics & SensorsMachinery & Plant EngineeringAutomotive SuppliersMedical Technology+1

Spot component end-of-life notices early

For each notice you see the affected BOMs, orders and units in the field, plus the remaining demand.

Today

Component makers send change and end-of-life notices that are read late or not at all. What follows is a line stop or a redesign under time pressure.

An example

Wallner+Hardt Sensortechnik receives a discontinuation notice for a microcontroller. demi finds it on 3 boards, in the WS-410 pressure sensor (IO-Link, 0–10 bar) and the ST-220 controller, and in about 1,200 units in the field. The agent calculates a last-time buy that covers service for the contracted years.
Fictional company, typical workflow.

Your data, wherever it lives

Today discontinuation and change notices arrive as PDFs by e-mail or sit in supplier portals, BOMs and where-used lists in the PLM, stock, open orders and demand in the ERP, and units in the field in a service spreadsheet. demi reads, understands and links them per manufacturer part number, with your rights. For every notice the AI finds all affected BOMs, orders and units in minutes and calculates the remaining demand, instead of the notice going unread, and management decides on the last-time buy.

Where the data lives today

  • PDFs
  • E-mails
  • Web & portals
  • PLM
  • ERP
  • Office files
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the ERP, PLM, e-mail and supplier portals. demi replaces nothing and links every notice to BOMs, where-used lists, open orders, stock, demand forecasts and the installed base. demi writes a last-time buy into the ERP only after approval.

  2. 2 · PermitPermission Layer

    Purchasing and engineering see the risk list. Management decides on a last-time buy, the final order before the part disappears, and that approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent matches each notice by exact manufacturer part number and ranks risk by usage and stock coverage. It calculates the last-time-buy quantity from recorded demand including service, step by step with sources, and proposes successors for review.

How it runs

  1. 1

    Collect notices from e-mail and supplier portals

  2. 2

    Find affected BOMs, products and installed units by manufacturer part number

  3. 3

    Rank the risk and calculate remaining demand, service included

  4. 4

    Propose possible successors for review, with every data-sheet difference

  5. 5

    Approve a last-time buy or a redesign and set it in motion

What changes

  • Discontinuations seen while there is still time

  • Planned last-time buys instead of panic orders

  • Redesigns started in time

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+216 hfreed per year

Assumptions and calculation

demi shows the affected bills of materials, orders and remaining demand for each notice; you decide.

90 min → 54 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

30 discontinuation notices × 90 min × 40% × 1.0 (manual) × 12 months = 12,960 min = 216 h

Value per year, before demi costs

Freed per year+216 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$14,040

gained per year

216 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Where do the discontinuation notices come from?

From the channels they already arrive through: e-mails to purchasing or engineering, supplier portals and documents on file shares. demi reads them there and maps them to parts. You do not need a new process with every supplier.

How is the last-time-buy quantity calculated?

From data you already record: open orders, forecasts, stock and spare-part demand of the installed base. The agent shows the calculation step by step with every input. The quantity is a proposal; you decide.

Does it take service obligations into account?

Yes, if the promised service periods are in contracts or the ERP. demi links them to the delivered units and adds the spare-part demand up to the end of the commitment.

What if there is no suitable successor?

demi says so plainly and lists the affected products for a redesign. Possible alternatives go to engineering for review, with every data-sheet difference listed.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases