Here's how obsolescence management works at most companies: an engineer builds a spreadsheet during a quiet week, cross-references the BOM against lifecycle data, color-codes the risky lines, and presents it at a quarterly review. Everyone agrees it's useful. Then the engineer gets pulled onto a product launch, the spreadsheet ages, and eighteen months later a line-down traces back to an EOL notice that arrived - and expired - while nobody was looking.
The spreadsheet wasn't wrong. It was just static, and the problem is continuous.
Why spreadsheets fail at this
Obsolescence isn't an annual event you can audit your way through. Discontinuation notices arrive year-round, alternates gain and lose availability, and lifecycle status shifts every quarter. A point-in-time snapshot starts decaying the day it's saved. Worse, spreadsheets have no owner by design - they belong to whoever made them, which means they belong to no one once that person's priorities change.
What a working plan looks like
The companies that don't get surprised share four habits, none of which require fancy tooling:
- Risk-score the BOM once, properly. Each line gets a lifecycle stage, a sourcing depth (how many real sources exist, not how many are listed), and a consequence rating - what stops if this part disappears. Twenty minutes per critical line, once.
- Monitor continuously, not quarterly. EOL notices, PCN feeds, and lifecycle status changes need to flow to a person whose job includes reading them. The watching has to be someone's job description, not someone's spare time.
- Pre-decide the responses. For each high-risk line, decide before the notice arrives: stockpile, second source, or redesign. An LTB window is a terrible time to start a debate between engineering and finance.
- Budget for last-time-buys annually. If every LTB requires an unbudgeted capital request, every LTB will be late. A standing obsolescence reserve turns a fire drill into a line item.
The maturity test
One question reveals where you stand: "When the next EOL notice affecting us arrives, who reads it, and what happens in the first week?" If the answer involves a specific person and a pre-agreed playbook, you're fine. If it involves "whoever notices it" - that's the gap.
Where VMI absorbs the problem
This is the quiet argument for vendor-managed inventory that rarely makes the brochure. When a supply chain partner manages your stock, lifecycle monitoring stops being a task your team must remember - it's embedded in the replenishment process itself. We watch the notices because replenishing your lines is our job; when one drops on a part you use, you get a call with a recommended buy quantity and a bonded-stock plan, not a surprise.
Our VMI customers carry their last-time-buys in our San Jose warehouse, released against scheduled builds, with the cash impact spread across the consumption window instead of landing in one quarter. The obsolescence plan still exists - it just runs continuously, owned by people whose whole job is the supply chain.
However you implement it - internally or with a partner - the principle is the same: obsolescence management is a process with an owner, or it's a spreadsheet with a date.