PCNshark
PCNshark for PTC Windchill Teams

Turn Supplier PCNs Into Windchill-Ready Change Actions

Windchill governs product data, controlled engineering changes, approvals, BOM updates, and release.

PCNshark handles the work before formal change control begins: receiving supplier PCNs and discontinuation notices, extracting affected parts and deadlines, identifying BOM exposure, and assigning the initial response. Each affected part carries an organization-wide component record — lifecycle evidence, alternate recommendations (Team plans and above), distributor sourcing estimates, datasheets, and decision history — so the engineering decision has context before a change is opened.

Together, they connect an external supplier change to an internal, controlled product-change process.

Available on Starter and Team. A payment method is required.

Scope

PCNshark works alongside Windchill. It does not replace PLM, product-data management, controlled BOM governance, engineering change control, approvals, effectivity, or release management.

Integration status

No native Windchill integration is implied. PCNshark prepares and preserves the supplier-notice impact record used by your existing change process; the handoff into Windchill is done by a person, not by an automatic sync.

Reviewed by the PCNshark product teamLast reviewed
§ The missing step

What happens before a Windchill Change Notice is created?

A formal change process needs a reliable trigger. Before a Windchill change request or Change Notice is created, someone must capture the supplier notice, understand what changed, identify the affected parts, check product exposure, evaluate the deadline, and decide whether controlled change is required.

Typical manual intake
  1. Supplier email or portal
  2. PDF downloaded
  3. MPNs and dates copied manually
  4. BOM exports searched
  5. Engineering and supply chain contacted
  6. Impact and response debated
  7. Windchill change process initiated when required
With PCNshark
  1. Supplier PCN, PDN, EOL, or NRND notice
  2. PCNshark intake
  3. Affected MPNs, changes, and dates extracted for review
  4. BOM and product exposure identified
  5. Owner, deadline, and initial action assigned
  6. Structured impact record created
  7. Windchill change process initiated when required

Windchill should not need to begin with another unstructured email attachment. PCNshark gives the change owner a reviewed supplier notice, identified product exposure, critical deadlines, and an initial response path.

A supplier Product Change Notification is not a Windchill Change Notice

The terms sound similar, but they represent different stages of the product-change process.

Who creates it
Supplier PCN, PDN, or EOL notice

A component manufacturer or supplier

Windchill Change Notice

Your company's controlled change process

What it represents
Supplier PCN, PDN, or EOL notice

An external component, manufacturing, material, site, process, or lifecycle change

Windchill Change Notice

How an internal product change will be defined and implemented

How it arrives / is managed
Supplier PCN, PDN, or EOL notice

Email, PDF, distributor, supplier portal, or quality channel

Windchill Change Notice

A controlled Windchill change object

What it typically contains
Supplier PCN, PDN, or EOL notice

Affected MPNs, dates, change details, and supplier recommendations

Windchill Change Notice

Affected and resulting objects, tasks, approvals, effectivity, and release actions

Where it sits in the process
Supplier PCN, PDN, or EOL notice

Must first be assessed for BOM and product impact

Windchill Change Notice

Begins after the organization decides controlled action is needed

Whether action is guaranteed
Supplier PCN, PDN, or EOL notice

May require no formal product change

Windchill Change Notice

Governs formal implementation once a change is approved

PCNshark helps determine whether the external supplier notice requires action. Windchill governs the formal internal product change when action is required.

§ One connected process

From supplier notice to controlled product change

  1. External supplier change: a manufacturer PCN, discontinuation, EOL, or NRND notice arrives.
  2. PCNshark receives, extracts, and verifies the notice, matches it against active BOMs, identifies affected products, and assigns an initial owner.
  3. Decision: Does this supplier notice require controlled product change? If no, record the disposition and close. If yes, prepare the formal controlled change.
  4. The team manually carries the reviewed impact into the platform, which governs the controlled change and release. There is no automatic data sync.
External
External supplier change
  • Manufacturer PCN
  • Product discontinuation notice
  • EOL or NRND notice
  • Material or manufacturing-process change
  • Supplier or distributor notification
PCNshark
PCNshark: intake and impact triage
  • Receive the email or document
  • Extract and verify affected MPNs
  • Capture effective dates and lifecycle deadlines
  • Match the notice against active BOMs
  • Identify affected products and assemblies
  • Assign an initial owner and response
  • Preserve the source notice and review history
Controlled change
Windchill: controlled implementation and release
  • Change request or Change Notice
  • Affected and resulting objects
  • Implementation tasks
  • BOM redlines or controlled updates
  • Review and approval
  • Effectivity and release
Does this supplier notice require controlled product change?
No

Record the review and close

Yes

Prepare the formal Windchill change process

Not every supplier notice should automatically become an engineering change. The initial review must determine whether an active product is affected, whether the supplier change is acceptable, whether qualification is required, and whether the controlled product definition must change. PCNshark organizes that triage. Windchill governs the resulting controlled change. The move from PCNshark into Windchill is a manual step a person takes — there is no automatic data sync today.

When the lifecycle event requires action

The affected component

Every affected MPN resolves to an organization-wide component record — lifecycle status, BOM usage, prior PCN impacts, datasheets, and decision history — so the review starts from what your organization already knows about the part.

BOM exposure

Affected MPNs are matched against monitored BOMs, with per-line decisions and exclusions and manufacturer mismatches flagged — so the exposure the change owner sees reflects engineering review.

Lifecycle evidence

The lifecycle status (EOL, NRND, last-time-buy, last-ship) is recorded with the notice and evidence behind it. Manual reviewed decisions are never silently overwritten; conflicting signals are flagged for review.

Alternate candidates (Team plans and above)

The manufacturer's recommended replacement is extracted from the notice, and functional candidates are ranked by specification similarity. Similarity is a prioritization signal for engineering review — not qualification, which stays with your team.

Sourcing context

Distributor data across ~15 distributors, refreshed on demand: stock, MOQ, price breaks, estimated lead times, and authorized-vs-independent context. Estimates, not quotes.

Engineering disposition

Accept, qualify an alternate, lifetime buy, redesign, or no action — recorded on the component with who decided, when, and why, connected to the notice that triggered it.

Windchill change where required

When the disposition changes the product definition, the change owner opens the Windchill change and attaches the BOM-impact CSV and PDF impact report. Not every lifecycle decision requires an immediate formal change — a documented monitor or no-action disposition still lives on the component record.

§ Worked example

Turn a supplier document into a Windchill-ready impact assessment

A supplier issues a product discontinuation notice. PCNshark captures it, extracts and reviews the details, identifies BOM exposure, and produces a record the change owner can attach to a Windchill change request. This is an illustrative example — sample data, not a screenshot of a native Windchill integration.

Supplier discontinuation notice
Notice type
Product discontinuation
Affected MPNs
142
Issue date
June 15, 2027
Last-time-buy date
September 30, 2027
Last-ship date
March 31, 2028
Suggested replacement
Provided by the manufacturer
PCNshark impact triage
  1. Affected MPNs extracted and verified by a reviewer
  2. Matched against active BOMs — 4 BOM matches found
  3. 2 affected products surfaced for review
  4. Initial owners assigned: Component Engineering and Supply Chain
  5. Required reviews flagged: lifetime-buy analysis and alternate qualification
Reviewed impact — ready for your Windchill change request
Active BOM matches
4
Affected products
2
Initial owners
Component Engineering, Supply Chain
Status
In review
Formal change required
Yes — substitution + qualification
Handoff
Attach the CSV / PDF impact report to your Windchill change request

Illustrative example. Customer, supplier, product, and BOM information has been replaced. PCNshark does not create Windchill objects; the change owner opens the change request in Windchill.

PCNshark and Windchill solve different parts of the workflow

The question is not whether PCNshark can replace Windchill — it should not. It is whether supplier-notice intake and impact assessment are structured enough before the formal Windchill process begins.

Receive supplier PCN emails and documents
PCNshark

Focused intake for notices received by the team

PTC Windchill

Depends on the organization's configured supplier and change process

Extract MPNs and dates from supplier documents
PCNshark

Purpose-built extraction with human review

PTC Windchill

Not the primary role of PLM change control

Determine supplier-notice BOM exposure
PCNshark

Match affected MPNs against monitored BOMs

PTC Windchill

Controlled product structures and where-used data support downstream analysis

Identify affected products
PCNshark

Surface products and assemblies associated with BOM matches

PTC Windchill

Maintain governed product structures and configurations

Assign initial PCN triage
PCNshark

Record the initial owner, action, deadline, and status

PTC Windchill

Assign formal change roles and implementation tasks

Decide whether formal change is required
PCNshark

Support intake, impact review, and disposition

PTC Windchill

Govern the approved controlled change

Create engineering change requests or notices
PCNshark

Not a PLM replacement

PTC Windchill

Core change-management function

Redline and release controlled BOM changes
PCNshark

Not included

PTC Windchill

Core controlled BOM and change-management function

Manage approvals and effectivity
PCNshark

Not included

PTC Windchill

Governed through the configured Windchill process

Preserve the supplier trigger and PCN disposition
PCNshark

Connected supplier-notice record

PTC Windchill

Preserve formal internal change objects and resulting product records

Best role
PCNshark

External notice intake and impact triage

PTC Windchill

Internal controlled implementation and release

PCNshark does not replace the formal Windchill change process. It helps ensure the process begins with structured, reviewed, and traceable supplier-change information.

§ Inbox & spreadsheet vs. PCNshark

Give the Windchill change process a better starting point

Capture the supplier notice
Manual approach

Leave it in an inbox or manually save the attachment

With PCNshark

Forward the email or upload the document into a structured record

Identify affected MPNs
Manual approach

Read the PDF and copy part numbers

With PCNshark

Extract affected MPNs for human verification

Capture critical dates
Manual approach

Enter dates into a spreadsheet or calendar

With PCNshark

Keep effective and lifecycle deadlines connected to the notice

Determine BOM exposure
Manual approach

Search BOM exports and revisions individually

With PCNshark

Match affected MPNs against monitored BOMs

Identify affected products
Manual approach

Trace where-used relationships through separate files or systems

With PCNshark

Surface relevant products and assemblies

Assign initial responsibility
Manual approach

Coordinate through email, chat, or meetings

With PCNshark

Record an owner, action, deadline, and status

Decide whether formal change is required
Manual approach

Reconstruct context from multiple sources

With PCNshark

Review one connected supplier-notice impact record

Prepare Windchill input
Manual approach

Assemble information manually

With PCNshark

Use a structured notice, product-impact, deadline, and ownership record

Preserve the supplier rationale
Manual approach

Store emails, PDFs, and decisions separately

With PCNshark

Keep the original notice and disposition connected

PCNshark does not replace the formal Windchill change process. It helps ensure the process begins with structured, reviewed, and traceable supplier-change information.

Does PCNshark integrate directly with PTC Windchill?

Manual handoff today — no native integration

PCNshark works alongside Windchill rather than acting as a native Windchill integration.

Teams use PCNshark to process supplier notices, identify affected BOMs and products, assign the initial response, and prepare the structured information needed for their existing Windchill change process.

The current workflow does not automatically create or modify Windchill change objects. There is no API sync or push into Windchill today; a person moves the reviewed impact into the change process.

What works today
  • Export your BOM from Windchill (or your CAD/PLM tool) and upload the file (.csv, .tsv, .txt, .xlsx, .xls, .xlsm)
  • Forward or upload supplier notices, including supported scanned PDFs
  • Review extracted affected parts and dates before acting
  • Identify BOM and product impact
  • Assign the initial owner and response
  • Export a BOM-impact CSV and a PDF impact report to attach to your Windchill change request
  • Reference the PCNshark record during the Windchill change process
Not available today
  • Automatic creation or modification of Windchill change objects
  • A live API sync or push between PCNshark and Windchill
  • Direct import of a BOM straight from Windchill (export the file and upload it)
  • A "Windchill-ready" or ECR-formatted export file

What should be ready before formal Windchill change control begins?

A practical handoff checklist for the supplier notice, copyable and printable — no email required.

Your selections stay in your browser — nothing is uploaded, and no email is required to copy, print, or download.

PCNshark organizes the supplier notice, affected parts, critical dates, BOM exposure, ownership, and disposition that feed this handoff.

§ Roles

One supplier notice, different Windchill stakeholders

Exact responsibilities vary by company, product, quality system, and Windchill configuration.

Component engineering

Verify affected parts, identify product exposure, evaluate the technical impact, and determine whether alternate qualification or redesign is required.

Supply chain and sourcing

Track last-time-buy and last-ship dates, assess inventory and lifetime demand, and coordinate supplier or distributor action.

Quality and compliance

Preserve the original notice, review qualification impact, maintain evidence, and support the controlled disposition.

PLM, configuration, and change-management teams

Receive a structured supplier-change impact record before creating and routing the formal Windchill change process.

PCNshark is a strong fit for Windchill teams when:

PCNshark is not a replacement for:

PCNshark complements these workflows by organizing the supplier notice and BOM-impact analysis that may trigger them.

§ FAQ

Frequently asked questions

01Can Windchill manage supplier Product Change Notifications?
Windchill governs internal, controlled product and engineering change. How a supplier notice reaches Windchill depends on each organization's configured process — the notice must first be captured, interpreted, and assessed for BOM impact. PCNshark provides that supplier-notice intake and impact-triage step, then your team takes the result into its Windchill change process.
02What is the difference between a supplier PCN and a Windchill Change Notice?
A supplier PCN, PDN, or EOL notice is created externally by a manufacturer or supplier and communicates a component, material, site, process, or lifecycle change. A Windchill Change Notice is created inside your controlled change process and governs how an approved internal product change is implemented. The supplier notice must be assessed for impact first; it may or may not require a formal Windchill change.
03Does PCNshark replace Windchill?
No. PCNshark does not replace PLM, product-data management, controlled BOM governance, engineering change control, approvals, effectivity, or release. Keep Windchill as your system of record. PCNshark handles supplier-notice intake, impact assessment, and response triage before formal change control begins.
04Does PCNshark integrate directly with Windchill?
No. There is no native integration, API sync, or automatic push into Windchill today. PCNshark prepares and preserves a structured supplier-notice impact record, and a person carries that result into the existing Windchill change process. If a native integration matters to you, book a workflow review so we can understand the requirement.
05Can PCNshark work with BOM exports from Windchill?
Yes — export your BOM from Windchill (or your CAD/PLM tool) and upload the file. PCNshark accepts .csv, .tsv, .txt, .xlsx, .xls, and .xlsm. It does not import a BOM directly from Windchill; you upload the exported file.
06Can PCNshark identify which Windchill-managed products are affected?
PCNshark matches affected MPNs against the BOMs you upload and surfaces the affected products and assemblies in those BOMs. It does not read your live Windchill product structures; it works from the BOM exports you provide.
07Does PCNshark automatically create Windchill Change Notices?
No. PCNshark does not create or modify Windchill objects. It produces a reviewed impact record — exportable as a BOM-impact CSV and a PDF impact report — that your change owner can reference and attach when opening a change request in Windchill.
08Should every supplier PCN become a Windchill change?
No. Many supplier notices require no formal product change. PCNshark helps determine whether an active product is affected, whether the supplier change is acceptable, and whether qualification or a controlled change is required — so a formal Windchill change is opened only when it is actually needed.
09Can PCNshark be used before an engineering change request is created?
Yes — that is its primary role. PCNshark captures and triages the supplier notice and determines whether controlled change is required, before a change request is opened in Windchill.
10Can PCNshark track last-time-buy and last-ship deadlines?
PCNshark captures the effective date and lifecycle status (EOL, NRND, last-time-buy, last-ship) from the notice for review, and keeps those deadlines connected to the affected parts and products so the right owner can act before they pass.
11Does PCNshark recommend replacement parts?
It surfaces candidates; it does not select or approve them. Manufacturer-recommended replacements are extracted from the notice, and spec-ranked functional alternates are shown with a match percentage and the differing specs (Team plans and above). Qualification and the final choice remain engineering decisions your team makes and documents.
12Can PCNshark preserve the original supplier notice and disposition?
Yes. PCNshark keeps the original notice, the extracted and reviewed data, the BOM matches, the deadlines, the assigned owner, and the final disposition connected as one record.
13Can PCNshark work with other PLM systems?
Yes. PCNshark complements PLM, ERP, and sourcing systems generally — it is not specific to Windchill. It works from the BOM exports and supplier notices your team provides, regardless of which PLM governs your controlled change process.
14What happens after the 14-day trial?
Starter and Team include a 14-day trial and require a payment method. After the trial, the plan continues unless you cancel. Scale begins as a paid subscription rather than a trial. See the pricing page for current plans.

Give your Windchill change process a structured PCN starting point

Process the supplier notices your team receives, identify affected BOMs and products, assign the initial response, and preserve the evidence needed for controlled product change. Keep Windchill as your product and change-management system of record. Use PCNshark for supplier-notice intake, impact assessment, and response triage.

Starter and Team include a 14-day trial. A payment method is required. Scale begins as a paid subscription. No PLM replacement is required.
§ Keep reading

Related resources

§ Sources

Sources & references

  1. 01PTC — Windchill change management overviewControlled change requests, Change Notices, tasks, effectivity, release.
  2. 02PTC Help Center — Windchill change managementChange objects, affected/resulting objects, approvals, effectivity.

Product and workflow descriptions are based on publicly available documentation and PCNshark's current production capabilities. Windchill implementations vary by company and configuration. Confirm specific Windchill behavior with your internal PLM administrator or PTC representative.

PCNshark is an independent product and is not affiliated with, endorsed by, sponsored by, or certified by PTC. PTC and Windchill are trademarks of their respective owner.