For electronics and instruments

What is different about this industry

Three things, and they compound. Bills are long — a moderate instrument runs to several hundred lines where a mechanical assembly runs to thirty. Components are volatile — semiconductors go end-of-life on the manufacturer's schedule rather than yours. Substitution is constrained — a footprint-compatible part may still fail qualification on a parameter nobody wrote down.

The consequence is that the expensive failure is almost never a design error. It is a component becoming unobtainable in a product that was otherwise finished, and the cost is a board revision, a qualification and a customer notification for something that had nothing wrong with it.

So the capabilities that matter here are not the ones a mechanical manufacturer would rank first. Reference designator integrity, AML depth and lifecycle joins beat almost everything else.

Reference designators, and the check nobody automates

A quantity should equal the count of its reference designators. Eight of a component against C1, C2, C3 is not a syntax error — both cells are individually valid — and no amount of scrolling catches it.

Manufacturing PLM expands designator ranges, counts them, and raises the mismatch at paste time rather than accepting it. That is the moment it costs nothing to fix; the alternative is a board built with three of a four-place component and an assembler who assumed the BOM was right.

Pasting from an ECAD export is the normal entry path, and four hundred rows arrive as four hundred typed lines: quantities parsed as numbers, units normalised, designator ranges expanded. 1,000 becomes one thousand rather than a string that sorts between 1 and 2.

The AML is the join that everything else hangs on

An internal part typically carries two or three approved manufacturer parts, each with its own lifecycle state and its own approval — preferred, qualified alternate, under evaluation. A single supplier field cannot express that, and in this industry the distinction is the whole game.

Component feeds match on manufacturer part number and nothing else. SiliconExpert, Z2Data, Accuris and Octopart know MPNs; they have never heard of your internal numbering. A part whose AML is empty is invisible to every feed you subscribe to, and the unmatched list is the most concrete argument for maintaining it that anybody has produced.

Where feeds disagree, the disagreement is shown rather than averaged. Two sources reporting active and one reporting not-recommended-for-new-designs usually means a manufacturer signalled something one aggregator caught first — which is precisely the signal worth acting on rather than smoothing away.

Exposure that is worth reading

Risk is computed through resolved structures, so an end-of-life notice reports the products currently shipping with the part rather than every structure that ever mentioned it. A component present only in a superseded revision is not a live risk, and reporting it as one teaches people to skim.

Multi-level where-used walks through purchased sub-assemblies, which matters more here than anywhere: a regulator inside a bought-in power module still resolves to the finished instruments it affects, and that is exactly the case a manual search misses.

Quantities roll up. A capacitor used six times on a board that appears twice in an instrument is twelve, and it is the piece count rather than the product count that tells you how much runway the stock buys.

The Supplier Agent triages the week's notices by what they block, finds alternates already qualified on another product, and drafts the change where one exists — citing the notice, the manufacturer part and the products at every step.

How it meets your ERP

Runway is your ERP's number and it appears on every alert: on-hand, committed, open purchase orders and lead time, read back read-only with an as-of stamp. An alert that says three shipping products, eleven weeks of stock, no qualified alternate is actionable; a lifecycle status change on its own is not.

The released BOM publishes outward on change release, dated to its effectivity, carrying the non-electrical lines too — enclosures, labels, firmware images, packaging — which is what a planning run needs and what an ECAD-driven export leaves out.

The supplier record masters in your ERP; the AML masters here. That split is the default in the system-of-record matrix and it is exactly the split this industry needs, because purchasing owns who you buy from and engineering owns what is qualified.

Where the boundary is

There is no ECAD integration today. Altium and its peers are on the roadmap rather than shipped, so a schematic-driven BOM arrives by export and paste rather than by live sync. For a team whose ECAD tool is the source of truth for the bill, that is a real gap and it is the most likely reason not to choose Manufacturing PLM today.

Manufacturing PLM also does not do parametric component search or maintain a parts library. Finding a 0603 capacitor with the right voltage rating is what your feed vendors' own tools do well, and duplicating them badly would help nobody.