Engineering resource

PCBA component lifecycle: identifying NRND and obsolete parts

PCBA component lifecycle review should identify whether the exact parts in a released BOM can support the intended product plan. It should not stop at finding stock for the next prototype. A component may be available today while carrying a status that deserves engineering attention, and a product-family page may not resolve the position of every package or ordering option.

The useful output is a dated, traceable decision for each affected BOM line: what the manufacturer reports, which exact model the evidence covers, what the project needs and who owns the next action. This article explains how to build that record without treating NRND, a discontinuance notice and distributor inventory as interchangeable signals.

Start with the complete manufacturer part number

Normalize the BOM before checking lifecycle status. Identify the manufacturer, complete ordering code, package and relevant option suffixes for each approved item. A shortened description such as “dual amplifier” or a generic family name can hide the specific model that purchasing will order. Resolve ambiguous entries before assigning a confident lifecycle status.

Keep customer internal numbers linked to the approved manufacturer numbers. If a single internal item allows several alternatives, review each approved alternative separately. The existence of one available option does not automatically establish that all variants remain suitable or purchasable, and a lifecycle concern on one variant should not be silently applied to every other option.

Use a controlled BOM export with a revision and check date. The review should be reproducible: another person should be able to determine exactly which part list was checked. A spreadsheet copied from an early prototype may omit the component that changed during the final design review.

Read lifecycle labels in the manufacturer’s own terms

TI’s product lifecycle page distinguishes preview, active, not recommended for new designs, last time buy and obsolete. In TI’s definitions, NRND products remain available for existing designs while an alternative should be considered for new designs; obsolete products are no longer in production. The distinction matters when deciding between maintaining an existing board and starting a new design.

Do not convert those labels into a universal countdown. A status is evidence about the manufacturer’s current position, not a guaranteed number of years remaining for your project. If the design depends on continued supply for a defined period, obtain the relevant project-specific information and evaluate the risk rather than assigning a lifetime from the label alone.

Keep lifecycle status separate from qualification status. An active component still requires engineering approval for the application. A technically suitable part can carry a lifecycle concern, while a readily available newer device can be unsuitable electrically or mechanically. Combining those decisions into one green check mark makes the review easier to read but less useful.

Distinguish a product family from an orderable model

Analog Devices’ lifecycle information explains that a generic product number represents a range of specific models. Its production definition can mean that at least one model in the family remains in production. ADI directs customers to verify a specific model’s status when necessary and describes the model lists and dates included in discontinuance notices.

For the BOM review, preserve the evidence that matches the full orderable code. Check the affected-parts list in any notice rather than relying only on the family heading. If the exact variant is unclear, record an open question and obtain confirmation through the manufacturer’s support or authorized supply channel.

A package change can be particularly significant. A family may continue in one package while the board uses another. The continuing model may be useful for a redesign, but it does not resolve the current board’s footprint, thermal, assembly or test requirements. Make that difference visible before purchasing assumes that a family-level alternative is a drop-in replacement.

Separate lifecycle evidence from stock evidence

A stock listing answers a near-term availability question for the listed seller and quantity. It does not establish future manufacturing status or guarantee replenishment. Record the stock check separately from the lifecycle check, including the date and the scope of the information. Both can be useful, but they support different decisions.

Likewise, an empty distributor listing does not by itself prove obsolescence. A part can be active yet temporarily unavailable through one channel. Refer to the manufacturer for lifecycle evidence and ask the authorized supplier for the actual procurement position. Avoid turning a search result with no stock into an unsupported engineering conclusion.

Keep the sourcing plan aligned with the approved identity and traceability requirements. A lifecycle problem should trigger a deliberate decision about redesign, supply planning or an approved exception. It should not silently authorize purchasing an unverified substitute or changing the supply channel without the project’s normal review.

Extract the actual dates from the applicable notice

When a discontinuance notice applies, save its identifier, revision, publication date and exact affected model list. Record the final ordering and final shipment dates as separate fields if the notice provides them. Check whether a later revision changes the information. A general lifecycle-policy page is useful context, but the actual notice is the operational document for the affected part.

Do not assume that placing an order and receiving material share the same deadline. The team needs enough time for technical review, demand approval, supplier confirmation and the required commercial process. Work backward from the applicable dates and identify the responsible owner for each action. A reminder on the final day leaves little opportunity to resolve discrepancies.

If documents conflict, ask for clarification and retain the response with the review. Do not choose whichever deadline is more convenient. The manufacturer and authorized supplier should clarify the applicable conditions for the exact model and order, especially when a notice has changed or the available information describes a broad product family.

Prioritize parts by project exposure

Not every lifecycle concern creates the same project impact. Identify whether the part is already qualified, whether the PCB footprint is easy to change, whether firmware depends on it and how much verification a replacement would require. A small inexpensive component can create a major redesign burden if its characteristics are essential to the circuit.

Relate the concern to the planned product horizon. A limited engineering experiment and a product with a long service commitment have different supply needs. Record the assumed build quantities and service obligations instead of treating an unqualified forecast as certain demand. The responsible business and engineering owners should agree those assumptions.

Use a short action classification such as monitor, engineering review required, notice deadline action or release hold. Define the meaning of each category in the project record. The category should lead to a concrete next step; a colorful risk score without an owner or due date does not resolve a procurement problem.

Evaluate replacement suggestions as candidates

A manufacturer cross-reference or recommended replacement is a starting point for engineering evaluation. Compare the complete specifications and the actual circuit requirements. Include package, pin assignment, operating conditions, timing, thermal behavior and any firmware or test dependencies relevant to that device. Do not assume similarity in the product description establishes interchangeability.

Document what must change to use the candidate. It may require a footprint revision, updated passives, a software adjustment or a new verification plan. Those changes belong in the controlled release process. If the candidate is approved only for evaluation, state that limitation so purchasing and production do not interpret it as unrestricted production approval.

Coordinate this work with the agreed component sourcing responsibilities. The supplier can gather availability information and propose options, while the designated design authority makes the technical acceptance decision. Clear ownership avoids delays caused by each party assuming the other has approved the replacement.

Build a demand scenario before a final-purchase decision

For a hypothetical product, assume the approved plan calls for six hundred more boards, each using two units of the affected component. The basic production requirement is twelve hundred units before considering existing usable stock, approved open orders, service needs and process allowances. This arithmetic is a planning example, not a recommendation to place a purchase order.

Separate the demand scenarios rather than burying uncertainty in one large buffer. Show the confirmed production plan, potential additional demand and service assumptions. Then identify the usable supply already controlled by the project. The owners can compare a final purchase with redesign timing using transparent inputs instead of a number whose origin no one can explain.

Also evaluate storage, ownership, inspection and the consequences of unused material. A supply decision that covers the next build may create obligations beyond that build. Obtain the appropriate commercial and technical approval for the actual transaction; the lifecycle spreadsheet itself should not be treated as purchasing authorization.

Keep customer-supplied stock in the same review

In a partial turnkey supply arrangement, customer-owned parts still need clear identity and disposition. Record what quantity is available, what documentation accompanies it and which board revision it is approved for. Do not exclude a line from the lifecycle review merely because the customer intends to supply it.

Reconcile shortages and leftovers at the end of each build. If a controlled stock reserve is being consumed to support an existing design, update the remaining supply against the approved demand assumptions. Otherwise a spreadsheet can continue to show sufficient lifetime coverage long after actual production has used the reserve.

When responsibility transfers between organizations, include the latest lifecycle findings and open actions in the handoff. A buyer’s knowledge of a pending discontinuance is not useful if the assembler receives only an old BOM with no notice reference or release restriction.

Refresh the review at meaningful release points

Repeat the check when a new design is released, a dormant product returns to production, a major build is planned or a manufacturer notice affects the BOM. Assign ownership of notification review so a received message becomes a tracked action where necessary. The exact review frequency should match the product plan and sourcing exposure.

Before the next quotation, check your BOM file for complete identities and attach the dated lifecycle review. Include unresolved model questions, applicable notice references and the approved action for each affected item. This gives the supplier a concrete basis for pricing and planning while keeping engineering approval, procurement availability and lifecycle status distinct.

Your next build,
clearly scoped.
Get a Quote ↗