Altium and the electronics design seam

What crosses the seam

Three things move from an electronics design tool into Manufacturing PLM, and the file is the least interesting of them.

• The BOM with reference designators — the line set, each line carrying which designators on the board it accounts for. This is the artefact everything downstream depends on.
• The library link — the association between a component in the design library and an item here, which is what makes the BOM resolvable rather than a list of strings.
• The released output set — Gerbers or ODB++, drill files, pick-and-place, assembly drawings, netlist. Held as a versioned set that was released together, because a fabrication package assembled from files of different dates is the classic way to build the wrong board.

Who owns the library

The design tool owns symbols, footprints, simulation models and 3D bodies. Those are design artefacts, they change for design reasons, and a PLM that tries to govern them slows down work it does not understand.

Manufacturing PLM owns which part a library component means. The item, its approved manufacturers, its classification and its lifecycle live here, and the library component carries a link to it rather than a copy of it.

That split has an unglamorous payoff: when an item's approved manufacturer list changes, every design referencing it is affected immediately, and nobody has to remember to update a library field. The library did not change, because the library was never the place that fact lived.

The alternative — manufacturer data maintained inside library components — produces the situation every electronics team recognises, where the library says one thing, the PLM says another, and the correct answer is whichever the person you asked last happens to prefer.

The failure it prevents

A board is released and fabricated. The assembly comes back with one component depopulated that should have been fitted, and the cause is a BOM line that carried a *Do Not Fit* note in the schematic and lost it somewhere between export and the assembly house.

The note existed. It was in a field the exporter did not carry, in a spreadsheet column that got reordered, and in an email from three weeks earlier that the assembler did not have.

A BOM that travels as a spreadsheet arrives as a spreadsheet's worth of certainty. Holding the line set with its designators, its fitted state and its released output package as one versioned thing removes the seams where notes fall out — which is most of what an ECAD integration is actually for.

How it meets the rest of the product

The imported BOM becomes a structure like any other, so where-used, compare, effectivity and variant resolution work on it without special cases. A board is not a different kind of object here; it is an assembly whose lines happen to carry designators.

Designator counts are checked against line quantities on import, which catches the common transcription failure where a quantity says four and the designator list names three. It is a small check that finds a real error often enough to be worth stating.

MPN matching runs on the manufacturer references the import carries, so a BOM arriving with distributor-prefixed part numbers is proposed against your AML rather than accepted as new items — which is how AMLs stay small enough to be meaningful.

Change control treats a board release like any other release. The output set, the structure and the designator map move through the same workflow, so the approval that matters is recorded against the package rather than against whichever file somebody happened to attach to the request.

How it meets your ERP

The ERP does not want designators, and it is worth saying plainly. Purchasing needs item, quantity and unit of measure; the reference designator list is engineering's and it is dropped on publication rather than carried into a field nobody reads.

What the ERP does want is the consolidated line set — the same component appearing at four designators is one purchased line of quantity four — and that consolidation happens in the MBOM transform rather than being asked of the ECAD tool.

Fabrication and assembly packages are published as controlled copies to the ERP's document reference or to the supplier portal, not as attachments on a purchase order. A supplier holding an uncontrolled copy of a Gerber set is the exact problem controlled copies exist to solve.

Where the boundary is

Manufacturing PLM does not open, render or edit ECAD files. There is no schematic viewer and no layout viewer. Files are held with their metadata and their relationships; viewing them is the design tool's job and it does it far better.

There is also no round-trip. Manufacturing PLM does not write into a design project or modify a library, because a PLM writing into an active design is how a designer loses an afternoon's work to a synchronisation they did not ask for.