Supplier records, from engineering's side

What a supplier record holds here

Four things that engineering needs and a vendor master generally does not carry.

• Qualification scope — what this supplier is approved to produce. Not *approved* as a flag, but approved for these processes, these material classes, these tolerance bands. A supplier qualified for sheet metal is not thereby qualified for machined titanium.
• Certifications with expiry dates — ISO 9001, AS9100, IATF 16949, ITAR registration, and any customer-specific approvals, each with the date it lapses.
• Audit history — when they were last audited, by whom, findings raised, and whether those findings closed.
• Linked parts — which items and which AML entries name them, which is what turns any of the above into an operational fact rather than a filing cabinet.

The link is the whole point

A supplier record disconnected from parts is a document. A supplier record linked to the AML entries that name it is a queryable relationship, and the queries it enables are the ones that get asked in a crisis.

Which products stop shipping if this supplier does? That is where-used, run from a supplier rather than a part, resolved through every structure that consumes anything they make. It is not a report anybody maintains; it is the same resolution engine answering a different starting question.

The reverse query matters as much. Given a product, which suppliers does it depend on, and are any of their certifications expiring inside the build window? That question is asked before a certification lapses rather than after, which is the entire difference.

Both queries are only as good as the linking, which is why AML entries carry supplier references rather than free-text manufacturer names. A supplier named as a string is a supplier no query can find.

The failure it prevents

A supplier's AS9100 certification lapses. Nobody notices for eleven weeks, because the certificate is a PDF in a shared folder and the expiry date is a fact inside it.

Parts received during those eleven weeks went into eight products, three of which shipped to a customer whose contract requires every supplier in the chain to hold current certification. The disclosure is worse than the lapse.

An expiry date is only useful as a date the system knows. Held as a typed field with a watcher on it, the lapse raises a task ninety days out, names the eight products, and becomes a scheduling conversation instead of a customer notification.

How it meets the rest of the product

The AML links items to approved manufacturers, and manufacturers to supplier records. That chain is what makes the queries above resolvable, and it is the thing worth getting right early because retrofitting it means re-linking thousands of entries.

The supplier portal is the same record from the other side. A supplier holds controlled copies, receives change notifications and responds to requests against the record you hold about them, which means the qualification scope governing what they may be asked to build and the documents they receive are the same object.

The supplier agent watches certification expiries, audit follow-ups and single-source concentration at Recommend tier — raising tasks with the affected products named, never changing a qualification or a sourcing decision, which are judgements with commercial consequences.

Quality records reference suppliers directly, so a nonconformance attributed to received material accumulates against the supplier record rather than against a note in a spreadsheet. Over a year that history is the most useful thing in the record, because it is the part nobody could reconstruct.

Access control applies here as everywhere: a supplier record for a restricted programme is invisible to people outside it, and a where-used run from that supplier returns only the products the person running it may see, with the omission stated rather than silent.

How it meets your ERP

The vendor master and the supplier record are different objects about the same company, and both should exist. Your ERP holds payment terms, addresses, tax registration and purchase history; Manufacturing PLM holds qualification, certification and the engineering relationship.

They are linked by an identifier rather than merged, and the system-of-record matrix records which fields belong to which. The failure to avoid is a qualification flag maintained in both places that disagrees — because the version the buyer sees is the one that governs what actually gets ordered.

Where an ERP purchase history read is configured, spend and volume appear alongside the engineering view, which is what makes a single-source risk conversation concrete: this supplier is single-sourced on fourteen items, and here is what that represents.

Where the boundary is

Manufacturing PLM does not source, quote, negotiate or place orders. It holds engineering's view of a supplier and the relationships that make that view queryable. Commercial activity belongs in your ERP or your sourcing system.

It also does not score suppliers automatically. Delivery and quality performance are read where the integration exists and shown as data; turning them into a rating is a judgement with commercial weight, and a number generated by software carries an authority it has not earned.