Avoiding obsolescence in design: component selection, second source and modularity
The cheapest discontinuation is the one already planned for in the design. How development teams select components, limit dependencies and build products so that later changes stay small.
Foto: Manuel / Unsplash
In brief: Development decides how expensive later discontinuations will be. Choosing components with long availability and several sources, packing critical functions into replaceable modules and documenting the design properly turns future discontinuations into small changes instead of large projects. Obsolescence cannot be prevented – but its consequences can be significantly limited in the design.
Why development has the biggest lever
Later in the life cycle only expensive options remain: last-time buy, emergency purchase, redesign. In development, on the other hand, a better decision often only costs some time during component selection. A microcontroller that is about to be discontinued is easy to replace in the design – after the product has been approved, it is not.
IEC 62402 dedicates a separate clause to this topic: obsolescence should be considered as early as concept and development, through component selection, architecture, technology planning and documentation. Development is therefore a fixed part of the obsolescence management plan.
Selecting components with the life cycle in mind
Component selection is the most effective lever. Check every new component not only technically but also for its future.
| Criterion | What to look for |
|---|---|
| Life cycle status | only active components, no NRND, no announcement |
| Position in the life cycle | prefer a component at the beginning or in the middle of its life cycle over one that has been on the market for a long time |
| Number of manufacturers | prefer standard components available from several manufacturers in the same package |
| Package | common standard packages instead of special designs |
| Target market of the component | industrial and automotive components often stay available longer than components for consumer electronics |
| Longevity programmes | many manufacturers offer programmes with guaranteed minimum availability for selected components |
| Custom components | only where necessary, with contractually agreed availability and documentation |
| Compliance | foreseeable restrictions from RoHS, REACH or export control |
A component that has only just come onto the market is not automatically the best choice. Some new products do not catch on and are discontinued early. What you want is a component with broad use and a future.
Preferred parts list
A preferred parts list bundles approved components that meet these criteria. It speeds up development, reduces the number of different components in the company and makes monitoring easier. Maintain the list together with purchasing and obsolescence management and check it regularly for status changes.
Plan a second source from the start
Qualifying a second source for critical components during development turns a later discontinuation into a formality. Helpful measures are:
- Approved alternatives in the manufacturer list: several manufacturers per position, checked and documented.
- Compatible footprints: layouts that can take two package variants, for example overlapping land patterns.
- Margins in the design: some headroom in voltage, power, memory and computing power, so that a replacement does not fail at tight limits.
How to evaluate replacement components is described in the article Sourcing discontinued components.
Build modular, define interfaces
Not all components age at the same speed. Processors, memory, displays and communication devices are discontinued more often than passive components or connectors. Pack such fast-ageing functions into separate modules with clearly defined interfaces. Then, in the event of a discontinuation, the module can be replaced without redeveloping and re-approving the entire device.
This includes:
- standardised electrical and mechanical interfaces,
- a specification per module by form, fit and function that another supplier could also meet,
- in the software, an abstraction layer between application and hardware, so that a new processor does not affect the entire software.
Do not forget software and tools
Software also becomes obsolete: operating systems, libraries, compilers and development environments stop receiving updates at some point. Anyone who has to change firmware in ten years needs the matching tool chain. Archive source code, tools, licences and build instructions so that they can still be used years later. For programmable devices, plan how programming will work without the original tool.
Document for later replacement
Anyone who has to replace a component in fifteen years needs the reasons for the original selection. Document:
- the requirements of the circuit for every critical component, not just the selected part number,
- schematics, layout data, test specifications and test programs in readable formats,
- assumptions about margins, tolerances and environmental conditions.
Without these documents, every later change becomes a reverse-engineering task.
Check obsolescence in design reviews
Make the check of the bill of materials a fixed item in every design review. Before release, it should be clear:
- 01How many components are not active or have only one manufacturer?
- 02Which components have a forecast shorter than the planned delivery period of the product?
- 03For which critical components is there an approved alternative?
- 04Is the architecture prepared for later replacement?
What stands out here can be fixed with little effort. After series release, every change becomes more expensive. How to set up the assessment systematically is shown in the article Obsolescence management strategies.
Plan technology instead of just reacting
For products with a very long service life, a technology roadmap pays off: when will which modules probably be outdated, and when does a planned upgrade make sense? Planned upgrades at fixed intervals bundle several discontinuations and are usually cheaper than many unplanned individual solutions.
Typical mistakes
- Components are selected only by technology and price
- The life cycle status is only checked after series release
- Critical functions are fixed on the main board, without module boundaries
- Software accesses the hardware directly, every processor change becomes a major project
- Tools and development environments are not archived
- The reasons for component selection are not documented
Checklist for development
- Every new component is checked for status, forecast and number of manufacturers
- A preferred parts list is used and maintained
- A second source is qualified for critical components
- Fast-ageing functions sit in replaceable modules
- Software is separated from the hardware by an abstraction layer
- Tools, source code and build instructions are archived
- Requirements for critical components are documented
- Obsolescence is a fixed checkpoint in every design review
Frequently asked questions
Can obsolescence be prevented in development?
Not prevented, but greatly limited. Almost every component will be discontinued at some point. The goal is that a discontinuation then only triggers a small, plannable change and not a redesign of the entire product.
What is a preferred parts list?
A list of approved components that have been technically checked and have good prospects of long availability. Developers preferably choose from this list. This reduces the number of different components and makes monitoring easier.
Is modularity worthwhile even for small quantities?
Often especially then. With small quantities and a long service life, redesign and requalification are particularly expensive in relation. A replaceable module limits this effort to one part of the product.
Who is responsible for obsolescence in development?
Development decides on components and architecture, obsolescence management provides data and assessment, purchasing provides supplier information. A fixed checkpoint in the development process where all three come together has proven itself.
What to do if a component is discontinued after all is described in the article Received a discontinuation notice – what now?.
Avoiding obsolescence in development and design according to IEC 62402:2019, clause 8.
New product in development?
In 15 minutes we look together at how you can limit obsolescence risks already in component selection and architecture. Free of charge and without obligation.
Book a free call