Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62402: Obsolescence Management — A Practical Guide for Engineering Systems
IEC 62402 is the international standard that establishes a systematic framework for managing obsolescence across the entire lifecycle of products, systems, and services. It provides structured processes for identifying, assessing, mitigating, and monitoring obsolescence risks — an essential discipline for industries where system lifetimes exceed component availability.
1. Introduction to Obsolescence Management
IEC 62402 defines obsolescence as the transition of a product from available to unavailable from the original manufacturer or supplier, while still being required by the user. This condition is particularly acute in industries with long product lifecycles such as aerospace, defence, railway signalling, nuclear power, industrial automation, and medical devices, where systems must operate for 20-40 years or more while the components they depend on may become obsolete within 3-5 years.
The standard introduces the concept of a Diminishing Manufacturing Sources and Material Shortages (DMSMS) management process. Rather than treating obsolescence as an unexpected crisis, IEC 62402 advocates a proactive, continuous lifecycle management approach integrated into the organisation’s overall product lifecycle management (PLM) framework.
A proactive obsolescence management programme can reduce lifecycle sustainment costs by 30-50% compared to reactive crisis-driven procurement. The key is establishing a systematic monitoring and risk-assessment cadence aligned with the product’s criticality and operational profile.
2. The Obsolescence Management Process
IEC 62402 defines a closed-loop obsolescence management process consisting of six primary stages:
| Stage | Description | Key Outputs |
|---|---|---|
| 1. Identification | Identify all items (components, assemblies, software, materials, processes) that are subject to obsolescence risk across the product structure. | Obsolescence-sensitive items list (OSIL), Bill of Materials (BOM) with lifecycle codes |
| 2. Monitoring | Continuously track the availability status of each identified item through supplier notifications, distributor data feeds, and market intelligence. | Obsolescence alerts, product change notifications (PCNs), availability status reports |
| 3. Assessment | Evaluate the impact of each obsolescence event on cost, schedule, performance, safety, and regulatory compliance. | Risk assessment matrix, priority ranking, mitigation timeline |
| 4. Mitigation | Select and implement the most appropriate resolution strategy from the available options (last-time buy, lifetime buy, substitute, redesign, aftermarket sourcing, etc.). | Mitigation plan, procurement orders, engineering change requests (ECRs) |
| 5. Implementation | Execute the selected mitigation, including procurement, qualification testing, production integration, and documentation updates. | Qualification test reports, updated BOM, revised production documentation |
| 6. Closure & Review | Verify that the mitigation has been successfully implemented, update the obsolescence register, and feed lessons learned into future product planning. | Closure report, updated obsolescence register, lifecycle lessons learned |
The process is iterative: as new products are introduced or existing products are modified, the identification and monitoring stages are revisited to maintain continuous coverage.
3. Obsolescence Mitigation Strategies
IEC 62402 presents a comprehensive toolkit of mitigation strategies, each suitable for different circumstances. The choice depends on factors such as remaining product life, quantity required, cost constraints, safety classification, and availability of alternatives.
| Mitigation Strategy | Applicability | Advantages | Risks |
|---|---|---|---|
| Last-Time Buy (LTB) | Known end-of-production; short to medium remaining life | Preserves existing design; minimal requalification | Inventory carrying cost; minimum order quantities (MOQ) may exceed needs |
| Lifetime Buy | Expected to cover entire remaining product lifecycle | Single procurement event; guaranteed supply | Large upfront investment; risk of stock obsolescence if demand changes |
| Substitute (Form/Fit/Function) | Alternative component available from another supplier | Quick implementation; no board redesign | Must verify parametric equivalence and reliability; risk of counterfeit |
| Aftermarket / Broker Supply | Components no longer manufactured; limited quantity needed | No engineering change; low upfront cost | Counterfeit risk; limited traceability; variable quality; no warranty |
| Redesign / Technology Refresh | Significant remaining life; multiple obsolete items | Long-term solution; can improve performance | High engineering cost; requalification required; schedule impact |
| Emulation / Re-engineering | Proprietary or obsolete ASICs with no alternative | Drop-in replacement; preserves legacy backplane | Very high NRE cost; requires original specifications or reverse engineering |
| Prognostic / Life Extension | Predicting remaining useful life of existing stock | Extends usage of on-hand inventory | Requires statistical data; uncertainty in predictions |
A common pitfall is relying solely on last-time buy (LTB) without considering total lifecycle inventory requirements. Order only the quantity that can be stored, consumed, and managed within shelf-life constraints. For electrolytic capacitors and batteries, shelf life is typically 2-5 years; for ICs in moisture-sensitive packaging, it can be as little as 12 months.
4. Engineering Design Insights
4.1 Designing for Obsolescence Resilience
The most effective obsolescence strategy is preventative — designing products to withstand component obsolescence before it occurs. Key design principles include:
- Functional abstraction: Use standardised interface layers (e.g., middleware, wrapper drivers) between hardware and software so that a component substitution does not ripple through the entire software stack.
- Multi-sourcing readiness: Wherever possible, select components available from at least two independent manufacturers. Document the parametric envelope (not just the part number) so alternative parts can be qualified without full redesign.
- Package and footprint foresight: Design PCBs with a preferred (primary) land pattern and a compatible secondary footprint for potential alternative packages. For example, a PCB pad layout compatible with both BGA-256 and LGA-256 allows flexibility in sourcing.
- Memory and FPGA over-provisioning: Specify memory devices and FPGAs with spare capacity beyond current requirements, enabling future feature migration or code updates without hardware change.
When designing a long-life product (15+ years), budget at least one major technology refresh cycle and two minor component substitutions during the product’s operational life. Include this as a line item in the total cost of ownership (TCO) model from the outset.
4.2 Establishing an Obsolescence Management Information System
IEC 62402 recommends the use of an Obsolescence Management Information System (OMIS) to automate the monitoring, assessment, and reporting processes. A well-configured OMIS:
- Ingests BOM data from the PLM/ERP system and automatically cross-references component lifecycle status against supplier databases (e.g., SiliconExpert, IHS CAPS, Z2Data).
- Flags components with lifecycle codes such as “Not Recommended for New Design” (NRND), “Last Time Buy” (LTB), or “End of Life” (EOL).
- Generates risk scores based on criteria such as: number of suppliers, lifecycle phase, industry adoption rate, and environmental compliance (RoHS/REACH) status.
- Integrates with the company’s Engineering Change (EC) workflow to automatically generate ECRs when a critical obsolescence event is detected.
Do not outsource all obsolescence intelligence to a third-party database. Supplier PCNs can arrive months before database updates. Maintain direct relationships with key component manufacturers and subscribe to their PCN email feeds. A 3-month delay in detecting an obsolescence event can mean the difference between an orderly LTB and a costly bridge buy.
5. Frequently Asked Questions
Q1: Is IEC 62402 applicable to software obsolescence?
Yes. IEC 62402 explicitly addresses software obsolescence, including operating system versions, compiler toolchains, runtime libraries, and third-party middleware. The same six-stage process applies: monitor for vendor end-of-support announcements, assess impact on system security and functionality, and plan migration to supported versions.
Q2: How often should the obsolescence monitoring cycle run?
The standard recommends a risk-based cadence. For safety-critical or mission-critical systems (e.g., nuclear I&C, flight control), monthly or quarterly monitoring is appropriate. For commercial or industrial systems, semi-annual or annual reviews may suffice. The cadence should be reviewed annually based on observed obsolescence velocity.
Q3: What is the difference between IEC 62402 and SAE TA-STD-0017?
SAE TA-STD-0017 (formerly GEIA-STD-0007) focuses specifically on DMSMS management, with detailed data formats and reporting templates. IEC 62402 is a broader framework that covers the entire obsolescence management process and is applicable across industries globally. The two standards are complementary and can be used together.
Q4: How should obsolescence risk be categorised for complex assemblies?
IEC 62402 recommends a three-tier categorisation: Critical (safety or mission impact, no alternative), High (significant cost/schedule impact, limited alternatives), and Low (minimal impact, readily available alternatives). Each category triggers different review frequencies and approval authorities for mitigation decisions.
