Obsolescence is treated as one problem almost everywhere it’s written about: a part sits unused, nobody claims it, someone eventually writes it off. That framing is too loose to build a program on.
Obsolescence is actually four distinct failure modes, each with its own signal and its own detection logic.
Collapsing them into a single flag is the most common technical weakness in obsolescence programs, and it’s the reason spare parts obsolescence management so often stalls at “watch for EOL notices” instead of producing a defensible, auditable process.
What Is Spare Parts Obsolescence ?
A part can be obsolete for four structurally different reasons. Each needs a different detection method and a different owner.
Design / Engineering
Retrofit, redesign, or decommissioning removes the part from active BOMs. Trigger: an engineering decision.
Manufacturer / supply (DMSMS)
Part still needed, OEM has stopped making it. Trigger: sits outside the plant, on the supply side
Technological
A newer part functionally supersedes the old one, even though the old part may still be purchasable. Trigger: a superior alternative exists.
Demand-Driven / Stock
No consumption for an extended period, cause ambiguous. Most easily confused with a critical low-frequency spare.
The rest of this framework treats these four modes as requiring different detection logic and different governance ownership.
Collapsing them into one flag is what produces false positives on critical low-frequency spares and false negatives on parts an OEM has already discontinued.
Is It Obsolescence, Or Does It Just Look Like It
Zero or low consumption is an ambiguous signal on its own. A part with no issues in three years could be genuinely dead stock, or it could be a critical spare for equipment that simply hasn’t failed yet.
Statistically, this is the same problem addressed in spare parts classification, which is why detection can’t rely on consumption data alone.
The cross-check that resolves the ambiguity is active BOM and equipment linkage.
Zero Consumption, Active Linkage
The part is still tied to non-decommissioned equipment. It should not be flagged obsolete, regardless of how long it has been sitting.
Zero Consumption, No Linkage
No active equipment references the part. This is the pattern that genuinely warrants an obsolescence review.
Zero Consumption, Ambiguous Linkage
BOM records are incomplete or equipment status is unclear. This case routes to manual review, not an automatic flag.
Detection Mechanics: The Quantitative Rules
A defensible process needs quantitative rules that go past a single binary signal.
Last-Issue-Date Threshold
A common approach flags a part after 24, 36, or 60 months of non-consumption. A single fixed threshold applied uniformly is weak.
The defensible version varies the threshold by criticality and lead time: a long-lead-time critical part deserves a longer non-consumption tolerance before flagging, not a shorter one, because a false obsolescence flag on that part costs far more than one on a low-criticality commodity item.
Consumption Trend Slope
A declining usage rate across rolling windows is a leading indicator. A binary moved-or-not-moved flag only detects obsolescence after the fact, once consumption has already stopped.
Stock-To-Consumption Ratio Drift
Months-of-supply climbing steadily is an earlier warning sign than zero consumption. A part whose stock cover quietly stretches from 6 months to 18 months is signaling risk long before it hits zero.
None of these three rules is reliable used alone. The defensible model is a composite score blending all three signal types, weighted rather than treated as independent pass/fail checks.
Data Mechanics Underneath Detection
Detection logic is only as reliable as the data feeding it. Three mechanical issues sit underneath every obsolescence model.
| Data issue | Mechanical problem |
|---|---|
| Lookback window | Obsolescence detection needs a longer window than classification, typically 36–60 months, because slow-moving critical spares need enough history to be distinguished from genuinely dead stock. |
| Supersession chain handling | When Part A is superseded by Part B mid-history, unchained consumption records show a false cliff in Part A’s history that mimics obsolescence onset. This is a data integrity failure, not a modeling nuance. |
| Multi-plant aggregation | A part can be obsolete at one plant and active at another. Running detection at global SKU level versus SKU-per-location produces different, and sometimes wrong, conclusions. |
Each of these is a data governance problem before it’s a scoring problem. Getting MRO data cleansing right at the supersession and location-mapping level is what makes the detection layer trustworthy in the first place.
The walkthrough here shows what this looks like applied against a live inventory dataset, including how the lookback window and BOM-linkage cross-check show up in practice.
With the data layer in place, the next question is what happens when internal signals and external OEM signals disagree.
External Signal Mechanics: OEM Lifecycle And DMSMS
Internal data only tells half the story. The other half comes from the supplier side.
PCN And EOL/LTB Ingestion
- Product Change Notices and End-of-Life/Last-Time-Buy notices are the primary external trigger.
- Most organizations track these manually through supplier emails and portals rather than systematically.
- That manual dependency is a real, nameable technical gap, not a minor inconvenience.
DMSMS Forecasting
- A discipline formalized in the IEC 62402 obsolescence management standard, with roots in aerospace and defense.
- Generates a predictive obsolescence score from part age, technology category, and supplier base concentration.
- Produces a warning before an official EOL notice ever exists.
Conflicts arise when a part looks “alive” internally, still active in a few BOMs, while the OEM has already issued an EOL notice. In that conflict, the external signal should usually win, even though it looks less urgent from inside the plant.
An EOL notice is a hard constraint on future supply; internal activity is not. Multi-site industrial operators applying this kind of structured DMSMS program, scoring parts on lifecycle status, demand criticality, and supplier concentration, report measurable reductions in unplanned parts unavailability as a result.
Last-Time-Buy Quantity Mechanics
LTB quantity calculation is mathematically distinct from standard reorder-point logic. It’s not an ongoing replenishment decision.
It’s a lifetime-demand forecast constrained by a single, final purchase opportunity.
Expected remaining equipment life
Failure / consumption rate
Safety margin
A lifetime-demand forecast constrained by a single final purchase opportunity, not an ongoing reorder decision.
The tradeoff is a variant of Economic Order Quantity, but constrained by the fixed final-buy window rather than an ongoing reorder cycle: LTB quantity versus carrying cost.
Treating LTB as “just buy more” skips this math entirely and leads to over-buying stock that never gets consumed before the equipment is decommissioned.
Form-Fit-Function Substitution: Validation Mechanics
The Validation Protocol
A valid FFF substitution requires a dimensional and tolerance match, a material specification match, and a performance specification match: pressure rating, electrical rating, or the equivalent parameter for the part class in question.
Who Signs Off
This must be an engineering sign-off step, not a procurement assumption. Procurement-led substitution without engineering validation is a real, consequential failure mode: it creates latent quality and safety risk, not just a process gap.
System Representation
Validated substitutes should be represented through a formal equivalent-parts structure, such as the SAP material master’s old material number field or a dedicated interchangeability table, rather than tracked informally in a spreadsheet.
Informal spreadsheet tracking is the common real-world state; the formal structure is the technically correct one.
Remediation Options Beyond Substitution
Substitution is one remediation path among four. Which option dominates depends on the criticality and value profile of the part, not on which option happens to be top of mind.
Reverse engineering and re-manufacturing are viable when the part’s design is well understood and free of IP restrictions; they’re blocked when patent protection or undocumented tolerances make replication legally or technically unsafe.
Repair and refurbishment extend the life of existing stock without a new purchase. Equipment redesign eliminates the part entirely, the highest-cost, longest-horizon option, reserved for parts where obsolescence risk recurs across a whole equipment category.
This is a decision hierarchy driven by cost, lead time, and risk, not a menu chosen case by case, and it connects to critical spares management for how a part’s criticality tier should weight the decision.
Bring Detection, Criticality, and Transfer Intelligence Into One System
See how Verdantis MRO360 connects obsolescence detection to cross-enterprise transfer, so surplus stock at one plant covers a shortfall at another before a new purchase order is raised.
Get a Free DemoFinancial And Accounting Mechanics
Obsolescence is a finance decision as much as an inventory decision. The write-off trigger logic typically moves a part into an inventory obsolescence reserve at the GL level when three conditions are met together:
- Zero consumption for a defined number of periods,
- No active BOM linkage,
- And no LTB flag.
This is FI/CO-relevant territory that most obsolescence content leaves entirely unaddressed.
Cost Of Under-Reacting
- Emergency and expedited sourcing to cover an unplanned obsolescence gap.
- Rush orders commonly carry a 3–10× premium over standard rates in MRO procurement literature.
Cost Of Over-Reacting
- Capital tied up in LTB stock that may never be consumed.
- Storage, insurance, and write-off risk accrue for as long as the part sits unconsumed.
The right framework is not a qualitative tradeoff statement; it’s a breakeven calculation between the expedite premium avoided by holding LTB stock and the carrying cost incurred by holding stock that may never be consumed.
Structured obsolescence risk assessment programs benchmarked across defense and industrial organizations have reported reducing unplanned obsolescence-related costs by up to 40% when this kind of structured breakeven logic replaces ad hoc write-off decisions.
System-Of-Record Mechanics
In SAP-grounded environments, obsolescence status is a workflow, not a flat flag.
Active
Normal use
Owner: OperationsLast-time-buy
window
Owner: Procurement
Trigger: EOL / PCN or risk score
Obsolete but
supported
Owner: Reliability Engineering
Aftermarket / Repair
Fully obsolete
Owner: Procurement + Finance Reserve accounting / DisposalThe four stages map to four distinct material status values, and the transition between them should be governed by a rule, not a habit.
Flagging a part obsolete does not automatically suppress its reorder point trigger in every configuration.
Whether MRP interaction requires manual zeroing of safety stock and reorder parameters is a common real-world failure point: a part flagged obsolete in the material master can still generate a reorder recommendation if the MRP parameters were never manually updated.
A further conflict sits between consumption data on the materials management side and engineering BOM or equipment status on the plant maintenance and PLM side.
When these two sources of truth disagree, which one is treated as authoritative is a governance decision that BOM management practice should resolve directly, before the detection model is trusted at scale.
Predictive And Proactive Obsolescence Modeling
The reactive posture waits for an EOL notice. The proactive posture watches leading indicators before that notice ever arrives: declining supplier count for a part category, part age relative to the typical technology lifecycle for that category, and repeated LTB events across a supplier’s broader catalog signaling a category-wide phase-out.
The technically correct approach is a weighted composite risk score across age, supplier concentration, technology category, and criticality.
The common weak approach is binary: has an EOL notice been received, yes or no. The composite score catches risk months or years before the binary flag would.
Governance: Who Owns Which Decision, And When
Every part moves through the same four lifecycle stages, and each transition needs a named owner and a defined trigger, not an ad hoc review.
Active → Last-Time-Buy: Who Decides, And On What Trigger
Last-Time-Buy → Obsolete But Supported: Who Decides, And On What Trigger
Obsolete But Supported → Fully Obsolete: Who Decides, And On What Trigger
The Governance Gap In Practice
Automating the detection and scoring side of this governance workflow is what an obsolescence-check agent is built to do; the clip here shows one applied against a live spares catalog.
Automation still needs the right inputs, which is why classification and criticality tier have to feed into monitoring intensity rather than sit alongside it.
Interaction With Classification And Criticality
Classification tier should determine obsolescence monitoring intensity, not the other way around.
High-criticality, low-value parts arguably need the most proactive obsolescence monitoring, precisely because a value-based view alone overlooks them: they’re cheap enough to ignore in a cost-driven review, but their absence at the point of failure carries outsized risk.
Criticality scoring approaches that work at the part level rather than the asset level reflect this directly.
Obsolescence status should feed back into classification, not sit as a dead-end flag. An obsolete-but-still-critical part needs different treatment than a routine low-value dead-stock item, even though both are technically “obsolete” by the same definition.
This is a cross-reference point only; classification mechanics themselves belong to spare parts classification, not this piece.
The video below walks through how part-level criticality scoring works in practice, which is the mechanism that should be driving obsolescence monitoring intensity in the first place.
With classification and criticality established as inputs, the remaining failure modes are ones that show up regardless of how well those two layers are built.
Failure Modes: Consolidated
Pulled together rather than scattered, these are the failure modes that recur most often in obsolescence programs.
Supersession chain breaks corrupt consumption history, creating a false obsolescence signal on the superseded part number.
Survivorship bias: a zero-demand critical spare gets misclassified as obsolete without a BOM-linkage cross-check.
Orphaned LTB stock ages silently because no system trigger exists to flag it for write-off once equipment is decommissioned.
FFF validation skipped under time pressure, with procurement approving a substitution without engineering sign-off.
Single-signal detection relies on consumption data alone, rather than a composite score blending internal, external, and BOM-linkage signals.
Manual EOL/PCN tracking depends on inbox monitoring instead of systematic ingestion, so notices get missed or acted on late.
Most of these failure modes trace back to the same root cause: a detection process that leans on a single signal instead of the composite view described earlier in this piece.
Bring Detection, Criticality, And Transfer Intelligence Into One System
See how Verdantis MRO360 connects obsolescence detection to cross-enterprise transfer, so surplus stock at one plant covers a shortfall at another before a new purchase order is raised.
Get a Free DemoFrequently Asked Questions (FAQs)
How Is Obsolescence Different From Slow-Moving Inventory?
Slow-moving inventory still has active consumption, just at a low rate. Obsolescence implies no active demand path at all, whether from engineering removal, OEM discontinuation, technical supersession, or extended non-consumption.
Does Verdantis MRO360 Integrate With SAP For Obsolescence Detection?
Yes. MRO360 reads consumption, BOM, and equipment status data from SAP MM, PM, and PLM modules without requiring an ERP replacement.
How Long Does It Take To Deploy An Obsolescence Detection Program?
A Verdantis MRO360 deployment typically goes live in 8 to 12 weeks, covering initial scoring across the full spares catalog.
Who Should Own The Last-Time-Buy Decision?
Procurement typically owns the transaction, but the quantity calculation should be validated jointly with reliability engineering, since it depends on expected remaining equipment life.
Can An Obsolete Part Still Be Critical?
Yes. A part can be manufacturer-obsolete while remaining tied to critical, non-decommissioned equipment. In that case it moves to last-time-buy or aftermarket support rather than write-off.
What's The Difference Between DMSMS And General Obsolescence Management?
DMSMS is specifically manufacturer and supply-side obsolescence: the part is still needed but the OEM has stopped producing it. General obsolescence management also covers engineering, technological, and demand-driven modes.
Is Obsolescence Detection Suitable For Multi-Site Manufacturers?
It’s most valuable there. Running detection at the SKU-per-location level, rather than a single global rollup, is what prevents a part obsolete at one plant from being wrongly flagged obsolete everywhere.
What Happens To A Part's Reorder Point Once It's Flagged Obsolete?
It depends on the system configuration. In many SAP environments, flagging a material obsolete does not automatically zero its reorder parameters, which requires a manual update to prevent a false reorder recommendation.
How Does Obsolescence Status Affect A Part's Write-Off Accounting?
A common trigger combines zero consumption for a defined period, no active BOM linkage, and no last-time-buy flag, which together move the part into an inventory obsolescence reserve at the GL level.
Should Classification Tier Change How A Part Is Monitored For Obsolescence?
Yes. High-criticality, low-value parts warrant the most proactive monitoring, since a value-only view tends to overlook them until they’re needed and unavailable.
