Lifecycle and Procurement Integrity
The selection workflow ends with a released design. The connector, unfortunately, doesn't freeze in time just because your drawing did. Manufacturers change platings and factories, discontinue series, and quote 40-week lead times. Distributors run dry. Lookalikes appear right when the genuine part gets scarce. This page is about keeping a released interface buildable and trustworthy for years, without procurement having to improvise under deadline pressure.
1. The part you picked will change
Connector products move through a lifecycle whether anyone remembers to tell you or not:
| State | What it means for a released design |
|---|---|
| Active | Buy normally — and this is when to record alternates (§5), while there's no pressure |
| NRND (not recommended for new designs) | Existing designs are still supported, but the clock is running; new designs should look elsewhere |
| EOL / discontinuance announced | A last-time-buy (LTB) window with final-order and final-ship dates — the decision point for a bridge buy, an alternate, or a redesign |
| Obsolete | The authorized channel dries up; whatever you buy now needs the scrutiny of §4 |
Each state forces a decision, and the cheap ones come early. The LTB window is the last point where the choice is yours rather than the broker market's.
You'll usually see that state in two places, and they are not equal. The manufacturer's notice is the record. A distributor lifecycle flag is an early hint and nothing more — the same rule as every other distributor-page claim. Also record when somebody last checked the datasheets. A part can quietly go NRND while a released design sits there looking finished.
2. PCN and EOL notices
Manufacturers communicate change through two instruments:
- A PCN (product/process change notification) says the part is changing — material, plating, mold, manufacturing site, marking — while keeping its part number. Most PCNs are harmless to most users. The ones that aren't are the ones that touch your qualified configuration: a plating change is a low-level and requalification question, not an FYI.
- A discontinuance / EOL notice says the part is going away, and names the last-order and last-ship dates.
The electronics industry formalized both practices jointly — JEDEC, ECIA (the connector industry's own association among them), and IPC publish J-STD-046 for change notification and J-STD-048 for discontinuance — and manufacturers issue notices under their own policies in the same shape, with the same traps.1 Two traps in particular:
Notices flow to customers of record, through the authorized channel. Buy through a broker, or through an unregistered account, and the notice for your part goes to someone else. And under the industry notification standard, silence is acceptance: lack of acknowledgement of a PCN within 30 days of its delivery constitutes acceptance of the change — and even an acknowledged notice is deemed accepted if nothing further is said within the 90-day review period.1 Read what each notice actually states; suppliers set their own terms, and the clock starts at delivery, not at reading.
The minimal handling loop for a real program — three answers, written down:
- Who receives? A named inbox (not a person who might leave) registered with each manufacturer or authorized distributor on the BOM.
- Who dispositions? Each notice gets reviewed against the released configuration (§1.5) and its qualification evidence: no impact / delta evidence needed / alternate or LTB decision needed.
- Where is it recorded? Disposition and rationale in the program record, at revision — the same discipline as every other evidence field.
3. Obsolescence management
There are two postures. Reactive: the line is down, the part is gone, and the options are whatever brokers have left. Proactive: the design assumed from day one that parts die, so obsolescence is an event with a procedure instead of an emergency. The DoD's public DMSMS guidebook (SD-22) and IEC 62402 are the formal treatments — worth knowing about even for programs that will never cite them, because they name the practice.2
The proactive hedges are ones this guide already argues for, now with their lifecycle rationale attached:
- Standards-based, multi-source families (§3) — a part defined by a slash sheet or IEC standard with multiple qualified manufacturers is structurally harder to lose than a single-vendor catalog item.
- Second source considered (§10) — upgraded here to recorded: name the second source and its qualification basis at design time (§5).
- QPL/QPD status watched for mil families — listings change; the QPL that justified the choice is a living document.
- Lifecycle status as a selection input (§6) — an NRND part is a poor foundation for a new ten-year design no matter how good its datasheet looks.
When an EOL lands anyway, the resolution ladder is the standard one — confirm real demand, evaluate approved alternates, price a bridge/LTB buy against redesign, and record which rung was taken and why. Quantities and economics are program-specific; the point is that the ladder exists before the notice does.
4. Authorized distribution and counterfeit avoidance
The distribution world has three tiers, and the differences are contractual, not cosmetic:
- Authorized / franchised distributors sell under agreement with the manufacturer: parts arrive with full traceability to the factory, the manufacturer's warranty applies, and PCN/EOL notices flow (§2). This is the default channel for released hardware — the hobby track has been saying the same thing about genuine parts all along.
- Independent distributors / brokers buy and sell outside that agreement. They serve a real function — sourcing obsolete and allocated parts — and the serious ones operate under counterfeit-avoidance controls (the AS6081 class). But traceability is now something to verify per lot, not something the channel guarantees.
- Marketplace and unknown-provenance sellers — for released hardware, this tier is not a procurement channel at all.
The structural fact that makes this a lifecycle topic: counterfeit exposure concentrates exactly where §1–§3 end — scarce, allocated, and obsolete parts, bought under schedule pressure, from whoever still claims stock. That correlation is the reason the aerospace/defense world built a standards family for it: AS5553 for organizations, AS6081 for independent distribution (AS6496 covers authorized distribution), plus the GIDEP alert system and the ERAI reporting database for sharing what's been caught.3 Deliberately out of this page's lane: incoming counterfeit inspection techniques — that is those standards' territory, done by people equipped for it.
For connectors specifically, the everyday version of the problem is less "remarked flatpack" and more the clone: the Micro-Fit-style kit terminal, the "JST-compatible" housing, the GX-style "aviation connector" — parts that imitate a family without its drawing, spring alloy, or plating. The hobby track documents that world as a knowing choice for prototypes; on released hardware, an unchosen clone in the BOM is a counterfeit problem wearing a friendlier name.
5. Approved alternates
The time to qualify a substitute is while the primary is still buyable — an alternate chosen calmly at design time is engineering; the same decision at 2 a.m. during a line-down is the red flag §11 about "equivalent" parts. For each alternate, record in the ICD:
- The alternate P/N and manufacturer, and what "equivalent" was verified to mean — form/fit/function plus the quiet dimensions: plating class (gold-to-tin is a defect, not a substitution), insert/housing material, seal and wire ranges, tooling (an alternate contact with different crimp tooling is a different production line), and qualification basis.
- Who approved it and under what evidence — analysis, delta testing, or full qualification.
Mil-spec QPL families are the institutional version of this: multiple manufacturers qualified to one slash sheet, interchangeable by design intent — which is much of why §3 favors standards-based families. Program and customer rules still control (some programs approve specific QPL sources, not the list), so even here the alternate is recorded and approved, not assumed.
6. Vendor mixing
A separate question from alternates: may the two halves of one mated pair come from different manufacturers?
- QPL mil families: intermateability across qualified sources is the design intent of the specification system — and programs still commonly require verification or restrict sources, so the mix is recorded and approved like any alternate (§5).
- Standards-based commercial families (M12-class and similar): cross-vendor mating is normal practice, with the same record-it discipline.
- Proprietary families and their "compatibles": no drawing arbitrates the mate. The guide already carries the worked instances — the MC4-style no-brand-mixing warning, the DEUTSCH-equivalent verify-before-mixing flag, the clone-kit chaos of the hobby track. Treat every "compatible with" claim as unverified until tested and recorded.
The rule that covers all three cases: vendor mixing is a design decision, recorded in the ICD with its verification basis — never a procurement improvisation. If purchasing can silently change which manufacturer's half arrives, the interface is not configuration-controlled (§1.5).
7. Requalification
Everything above funnels into one question: is the qualification evidence still about the parts being built? A PCN touching form, fit, function, or process; an approved alternate entering production; a manufacturer, site, or plating change; a broker lot with thin traceability — each reopens the evidence question. The Qualification Plan Template's trigger table (§7) is the working tool: the governing spec and program decide the answer (analysis, delta test, or full re-run), but the question is never optional, and §1.5's rule stands — substitution requires formal change control, not a purchasing footnote.
Source status
The standards and programs named here — the JEDEC notice lineage, SD-22, IEC 62402, AS5553/AS6081, GIDEP, ERAI — are cited at listing/program level for what they are and the practice they formalize; no requirement text is reproduced, and none of them is asserted as applying to your program (your contract decides). The lifecycle-state model, the notice-handling loop, the alternates-at-design-time rule, and the vendor-mixing rule are engineering judgment, tracked as heuristics in Source Notes.