Electronic Component Lifecycle Status: Active, NRND, EOL, and Obsolete

Why lifecycle status matters

Lifecycle status is a small field with a long reach. It decides whether a part is allowed into a new design, whether a buyer keeps placing routine orders or opens a last-time-buy analysis, how much inventory a program carries, and whether an engineer spends the next six weeks qualifying an alternate. Few other component attributes touch that many decisions.

The cost of getting it wrong runs in both directions. A part carried as Active after the manufacturer has announced discontinuation means an ordering window can close while the team is still planning around steady supply. A part carried as obsolete when it is still in normal production means a redesign nobody needed, or an open-market purchase at open-market prices for something an authorized distributor still stocks.

Status is also rarely one person's field. Design engineering reads it as permission to use, sourcing reads it as supply risk, quality reads it as an input to change control, and program leadership reads it as schedule risk. Those readers do not always consult the same source on the same day, which is where most internal lifecycle disputes begin.

Active

Active means the manufacturer is producing the part, supports it, and is willing to see it designed into new products. On most published scales it is the ordinary state for a part that is neither brand new nor winding down; several manufacturers use a separate Preview or Pre-production state for parts that have been announced but are not yet in volume production.

What Active does not tell you matters as much as what it does. It is not a statement about availability — an Active part can be on allocation, quoted at a 52-week lead time, or effectively unbuyable through your usual channel. It is not a commitment to any particular number of years unless the manufacturer publishes one; longevity or product-assurance programs, common on industrial and automotive lines, are a separate commitment layered on top of the status and are worth checking for parts going into long-lived products.

Active also has a shelf life as information. It is true as of the day the manufacturer last reviewed it, and nothing in the label itself tells you when that was.

NRND — Not Recommended for New Designs

NRND stands for Not Recommended for New Designs. The part is still in production and still orderable, and the manufacturer intends to keep supplying the customers already building with it — but it is steering new designs elsewhere, usually with a suggested replacement attached.

What NRND implies:

• +Production continues. NRND is not obsolescence, and an NRND part on a shipping product rarely needs an emergency response.
• +A clock has started. NRND is frequently the state a part occupies before a discontinuance notice — though there is no fixed interval, and some parts sit in NRND for years.
• +A replacement usually exists. Manufacturers generally name a recommended part alongside the status change. That recommendation is a starting point for evaluation, not a qualification.
• +New designs should treat the part as closed. Designing in an NRND part starts the obsolescence work of the next product before that product ships.

What NRND does not mean

NRND is misread in both directions — treated as an alarm by teams that stop shipping over it, and ignored entirely by teams that read it as marketing language. Three clarifications cover most of the confusion:

• +It does not mean a last-time-buy date exists. NRND puts nothing on the calendar; a discontinuance notice does that, and it may be years away or may never come.
• +It does not mean availability has changed. NRND parts frequently have normal stock, normal lead times, and normal pricing.
• +It does not require you to redesign a product already in production. It is a recommendation about new designs, which is exactly what the name says.

EOL — end of life

End of life means the manufacturer has decided to stop producing the part and has said so. The formal vehicle is a product discontinuance notice (PDN), the discontinuance counterpart to a product change notice. Semiconductor discontinuance notices follow JEDEC J-STD-048, and most manufacturers publish their own notification policy on top of it.

EOL is an announcement, not an immediate cutoff. Between the announcement and the last ship date the part is still manufactured and still buyable, and that interval is the entire window your team has to work in. What matters on an EOL notice is therefore not the label but the dates: when ordering closes, when shipping closes, and how much demand you have left to cover.

EOL notices reach different companies through different channels — a manufacturer subscription email, a distributor account manager, a portal that requires a login, or a rep who mentions it on a call. It is common for one part of a company to hold a notice that another part has never seen, which is a distribution problem rather than a data problem.

Last-time buy

Last-time buy is a phase more than a steady state, and some manufacturers publish it as its own lifecycle stage. It is the interval after a discontinuance announcement during which the manufacturer will still accept orders. Two dates define it, and confusing them is expensive:

• +Last-time-buy (LTB) date — the deadline to place final orders. Demand analysis, inventory review, funding, and approval all have to finish before this date, so it is the one to plan backwards from.
• +Last-ship date — the last date the manufacturer will ship. It usually falls months after the LTB date and constrains delivery scheduling of the final order, not the decision itself.

Obsolete and discontinued

Obsolete — published by some manufacturers as Discontinued, and by others simply as End of Life once the dates have passed — means the manufacturer no longer produces the part. Ordering is closed. Anything still available is inventory that already exists somewhere in the channel.

That distinction changes how you read every sourcing number attached to the part. Stock figures describe real inventory. A quoted lead time is a shipping estimate against that inventory, not a factory lead time, because there is no factory queue to join. Pricing drifts away from the last catalog price as remaining supply thins, and the further you move from authorized inventory into the independent market, the more the provenance of the material becomes part of the decision rather than a footnote to it.

The remaining options are the expensive ones: buy what is left and accept the diligence that comes with open-market sourcing, qualify an alternate, or redesign. Each of those deserves a written record, because someone will ask why in two years — often a customer, sometimes an auditor, occasionally the engineer who has to revisit the same part on the next program.

Lifecycle status is not always universally consistent

Two competent sources can publish different statuses for the same part on the same day without either being wrong. The usual causes are structural:

• +Different update cadences. A manufacturer updates its own page when the internal decision is made; a distributor updates when its data feed refreshes; a third-party database updates on its own schedule. Skew of days to months is ordinary.
• +Manufacturer versus distributor perspective. A manufacturer describes what it produces. A distributor describes what it can sell you — a related but different question. A distributor may mark a part as end-of-life in its own catalog because it has stopped stocking it, while the manufacturer continues to produce it for direct and contract customers.
• +Regional and channel variation. A part can be actively produced for one region or one large customer while being unavailable through general distribution elsewhere. Both statements can appear, side by side, as contradictory statuses.
• +Package-level versus family-level status. Lifecycle decisions are usually made at the orderable part number — a specific package, temperature grade, and packing option — but status is often summarized at the family level. The tape-and-reel variant can be discontinued while the tube variant continues.
• +Renames, transfers, and acquisitions. When a product line moves between manufacturers, the former owner's page can sit stale for a long time while the new owner's page reflects current reality — or the reverse, if the transfer is recent.
• +Statuses that were never published. A field applications engineer can tell you a part goes NRND next quarter and be exactly right. The website will not say so for another two months.

Where lifecycle evidence comes from

Behind every status there is a source, and the sources have different strengths. Knowing which one you are looking at is the difference between a defensible position and a guess:

• +Product change notice (PCN). A formal notice of a change to a part — process, materials, site, packaging, or specification. A PCN is not itself a lifecycle change, but it frequently carries one, and it is dated, specific, and attributable.
• +Product discontinuance notice (PDN) or EOL notice. The strongest common form of lifecycle evidence: it names the affected part numbers and the deadlines, and it comes from the party that makes the decision. Keep the original document, not a summary of it.
• +Manufacturer website, portal, or lifecycle tool. Authoritative in principle, and the right place to check an orderable part number rather than a family. Its weakness is latency — you cannot usually tell when the page was last reviewed.
• +Authorized distributor. Fast to check and closest to what you can actually buy through the authorized channel. It reflects catalog decisions as well as manufacturer decisions, so it can lead or lag the manufacturer in either direction.
• +Independent distributor and the open market. A useful signal about scarcity and price direction, not a lifecycle authority. If a part appears only in the independent market, that absence from authorized stock is itself evidence worth recording.
• +Supplier, rep, or contract-manufacturer communication. Frequently the earliest warning you will get, and often the only warning for parts you buy indirectly. An email is evidence — keep it with the part rather than in an inbox.
• +Direct conversation. A call with an applications engineer or account manager is regularly the most current information available and the least durable. Write it down the same day, with who said it and when, or it effectively did not happen.

Treat lifecycle status as a decision with provenance

The habit worth building is to stop storing lifecycle status as a word and start storing it as a decision. A decision has four parts:

• +Status — the position your organization is acting on: Active, NRND, EOL, obsolete, or an internal state of your own definition.
• +Evidence — what that position rests on: a specific PCN or PDN, an uploaded document, a distributor listing, a named supplier email, a logged conversation.
• +Decision maker — the person who reviewed the evidence and set the position. Not a system and not a data feed; a person with a name.
• +Timestamp — when they set it. This is what makes it possible to say later whether the position is current or stale.

Why the provenance form holds up

Written out, an entry reads: NRND, based on the manufacturer's PCN dated 12 March, set by the component engineer on 18 March. That is a sentence a program manager, an auditor, or a customer can act on. “NRND” by itself is not — it cannot be checked, it cannot be aged, and it cannot be defended when someone disagrees with it.

The provenance form is also the only one that survives disagreement. A bare status field has no way to represent a conflict; it can only be overwritten, which silently destroys the fact that there was ever a question. A decision with provenance can hold both at once: the position the organization is acting on, and the newer evidence that has not been reviewed yet.

PCNshark records lifecycle status in this shape — a status a person sets, attached to its evidence (a PCN held in the workspace, an uploaded document, or a stated source), with the part-level decision history kept alongside it; when newer conflicting evidence arrives, the record is flagged for review rather than rewritten.

What to do when sources conflict

When two sources disagree, the instinct is to resolve the field: pick one, type it in, move on. That is the move that quietly destroys information, because the next person to open the record sees a single confident status and no trace that there was ever a question.

The short version of a better process is four steps. Identify which source each claim came from. Preserve both pieces of evidence rather than the winner only. Decide which position your organization will act on, and record who decided and when. Then mark the unresolved conflict so it is reviewed rather than forgotten. A newer source is not automatically a more correct source, and the most recent update is not the same thing as the most authoritative one.

Lifecycle conflicts are common enough, and consequential enough, to deserve their own treatment — including a rough authority hierarchy with its caveats, the distinction between observed evidence and organizational truth, and what to do when new evidence contradicts a decision your team has already reviewed. The companion guide on conflicting lifecycle sources, linked below, covers that ground.