The PCN workflow that happens before your PLM
PLM change control is good at what it was built for: controlled items, formal review, and an approved change record. But a supplier PCN does not arrive as an ECR. It arrives as a PDF, and real work has to happen before anyone knows whether a formal change is needed at all.
This guide covers the gap between a notice arriving and an engineering change request being opened: what that work is, why PLM change control does not cover it, who typically owns it, and what a structured record of it looks like.
The gap between the notice and the ECR
Between arrival and change control sits a triage sequence: read and interpret the notice, identify the affected MPNs, extract the effective and last-time-buy dates, cross-check the MPNs against active BOMs, and decide whether anything you build is exposed.
Only then can someone answer the question the PLM cares about: does this require an engineering change? Many notices do not. A process change with no form, fit, or function impact may be accepted after review. A discontinuance may have no BOM matches at all. Those notices never become ECRs, but each one still needs a recorded answer, because "we looked and it did not affect us" is a decision someone may have to defend later.
Why PLM change control does not cover intake
A PLM change process starts when someone opens a change object against a controlled item. It assumes the affected items are already known. A supplier notice is the opposite case: an unstructured document from outside the company whose internal impact is unknown. Most PLM change models simply have no state for "a supplier notice we have not assessed yet."
Volume is the other reason. Most notices end in acceptance or no exposure, and pushing every raw PDF into formal change control would bury the change board in items that need triage, not approval. The practical pattern is triage outside the PLM, then a formal change for the notices that warrant one.
Who typically owns the pre-PLM work
Ownership varies more here than in any other part of the workflow. Three common patterns:
- Component engineering owns triage end to end: interprets the change, confirms BOM exposure, and opens the ECR when one is needed. Common in larger hardware organizations.
- Sustaining engineering owns it for shipping products, with component engineering consulted on part-level questions. Common where NPI and sustaining are separate teams.
- Supply chain or purchasing owns intake and dates, handing technical assessment to engineering. Common in smaller teams, since supply chain often receives the notices first.
Where PCNshark fits
PCNshark is built for this pre-PLM stretch. You forward or upload the notice; it extracts the affected MPNs and dates, matches them against BOM exports from your PLM or ERP, and holds the assessment, owner, dates, and disposition as one reviewable record with the original document attached.
It works alongside Windchill, Teamcenter, Arena, and Altium 365 rather than replacing them. PCNshark does not create ECRs or modify anything inside your PLM: when a notice does warrant a formal change, a person carries or attaches the reviewed impact record to the change process, and the PLM remains the system of record for the change itself.
What a structured pre-PLM record looks like
Whether you keep it in a tracker or a tool, the record for each notice should capture:
- Source notice
- The original PDF or email, preserved unmodified, so the assessment can always be checked against it.
- Notice type
- Change or discontinuance, and the kind of change: process, material, packaging, or form, fit, and function.
- Verified affected MPNs
- The affected part numbers as confirmed by a person, not just as extracted.
- Critical dates
- Effective, last-time-buy, and last-ship dates that set the response window.
- BOM matches
- Which active BOMs and revisions contain an affected part, or an explicit no-match.
- Affected products
- The products and assemblies behind the matched BOMs.
- Assessment
- The short technical judgment: what the change means for your products.
- Owner and status
- A named person and where the response stands.
- Disposition
- Accept, buy, qualify an alternate, redesign, or no exposure, with the reasoning.
- ECR reference
- If a formal change was opened, the PLM change number this record fed into.
Ready to put this into practice on your own BOMs?
Book a workflow reviewFrequently asked questions
01Does every PCN need an ECR?＋
02Why not handle PCN intake inside the PLM?＋
03Who should own PCN triage?＋
04Does PCNshark replace or integrate with our PLM?＋
Related resources
Where a focused PCN workflow fits before formal PLM change.
Read →What dedicated PCN software does and how to evaluate it.
Read →A tracking process you can run with an inbox and a spreadsheet.
Read →Manual processes, alerts, databases, and workflow tools.
Read →Sources & references
- 01PTC Windchill: PLM product overview
- 02Siemens Teamcenter: PLM product overview
- 03Arena (PTC): cloud PLM product overview
- 04Texas Instruments: product change notification practices (JEDEC J-STD-046 / J-STD-048)
Map the pre-PLM gap in your own process
A 20-minute workflow review traces one notice from arrival to disposition in your current setup and shows where a structured record would sit alongside your PLM. A historical notice and a sanitized BOM export are all it takes.
Start your 14-day free trial on Starter or Team. A payment method is required; cancel before the trial ends to avoid being charged. Scale is a paid plan and starts immediately rather than with a trial.