PCNshark
PCNshark for Altium 365 Teams

Turn Altium BOM Risk Into a Managed PCN Response

Altium 365 helps electronics teams manage designs and BOMs, understand where parts are used, and review lifecycle, compliance, supplier, and sourcing information.

PCNshark manages what happens when an actual supplier PCN, PDN, EOL, or product-change document arrives: extract and verify the affected parts and dates, identify BOM exposure, assign ownership, and drive the response to closure.

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

Scope

PCNshark complements Altium 365. It does not replace PCB design, managed BOMs, parts-used visibility, lifecycle data, compliance information, supplier data, BOM releases, or sourcing analysis.

Integration status

No native Altium 365 integration is implied. PCNshark works from the BOM files you upload and the notices you receive; there is no automatic sync with Altium.

Reviewed by the PCNshark teamLast reviewed

A lifecycle status is not the complete supplier notice

Seeing that a part is EOL, NRND, obsolete, or otherwise risky is an important signal. The supplier document may contain additional information required for action:

PCNshark keeps that source document, extracted information, BOM impact, owners, and final response connected.

Two stages: design and BOM intelligence, then the actual notice response

Altium 365 helps teams understand the components used in their designs. PCNshark turns the supplier notice affecting those components into an owned operational response. These are adjacent stages, not the same job.

Primary job
Altium 365 — design & BOM intelligence

Design and BOM context for the components you use

PCNshark — supplier-notice response

Operational response to a specific supplier notice

What it covers
Altium 365 — design & BOM intelligence

Design/project context, managed BOMs, parts in use

PCNshark — supplier-notice response

Receive the supplier document; extract MPNs and dates

Risk signal
Altium 365 — design & BOM intelligence

Lifecycle and sourcing visibility, BOM releases and comparison

PCNshark — supplier-notice response

Human verification of the actual notice contents

Action
Altium 365 — design & BOM intelligence

Supplier and compliance data for design decisions

PCNshark — supplier-notice response

Notice-to-BOM matching and product exposure

Ownership
Altium 365 — design & BOM intelligence

Within the design environment

PCNshark — supplier-notice response

Owner, deadline, status, and disposition for the response

Use Altium 365 to understand the components in your designs; use PCNshark to manage the supplier notice affecting them.

§ One connected process

From a supplier notice to an owned response

  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 the supplier notice require a design or BOM 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
Supplier change document
  • Manufacturer PCN
  • PDN
  • EOL or NRND notice
  • Material or assembly-site change
  • Distributor notification
PCNshark
PCNshark: notice response
  • Receive the supplier document
  • Extract and verify MPNs and dates
  • Notice-to-BOM matching
  • Identify affected products and assemblies
  • Assign owner, deadline, and action
  • Track to disposition
Controlled change
Your PLM, change, or quality process
  • Design or BOM change if required
  • Controlled release
  • Quality review
  • Approval
Does the supplier notice require a design or BOM change?
No

Record acceptance and disposition

Yes

Take the reviewed impact into your PLM/change process

PCNshark does not connect to Altium 365. It works from the BOM files you upload and the notices you receive, and a person takes the reviewed impact into whatever change or quality process you use.

§ Worked example

Example: a package and assembly-site change — and not every notice needs a BOM change

An illustrative product change notification with a supplier qualification report. Sample data — not a screenshot of a native integration.

Supplier change notice
Notice type
Product change notification
Change
Package-material and assembly-site update
Affected MPNs
36
Effective date
February 1, 2028
Qualification information
Included
PCNshark impact triage
  1. Affected MPNs extracted and verified
  2. Matched against monitored BOMs — 11 BOM matches
  3. 4 affected projects or products surfaced
  4. Owners assigned: Component Engineering and Quality
  5. Response: review qualification data and determine acceptance
Reviewed impact — acceptance may need no BOM change
BOM matches
11
Affected projects or products
4
Owners
Component Engineering, Quality
Likely outcome
No BOM revision if engineering and quality accept the change
Preserved
Review, owner, evidence, and final disposition

Illustrative example. Customer, supplier, product, and BOM information has been replaced. Not every notice requires a design change; PCNshark still preserves the review and disposition.

§ Inbox & spreadsheet vs. PCNshark

After a lifecycle or supplier-change signal

Find the original notice
Manual process

Search inboxes or supplier portals

With PCNshark

Keep the uploaded or forwarded notice

Identify affected MPNs
Manual process

Read the PDF manually

With PCNshark

Extract for verification

Capture dates
Manual process

Spreadsheet or calendar

With PCNshark

Retain with the notice

Check BOM exposure
Manual process

Search BOMs and project exports

With PCNshark

Match against monitored BOMs

Identify products
Manual process

Trace projects and assemblies

With PCNshark

Surface affected products

Assign response
Manual process

Email or meetings

With PCNshark

Owner, action, and status

Track LTB or qualification
Manual process

Separate tracker

With PCNshark

Connected deadline and follow-up

Preserve the decision
Manual process

Files and comments across tools

With PCNshark

Notice and disposition together

PCNshark does not replace Altium's design, managed-BOM, lifecycle, compliance, or sourcing capabilities. It manages the response to the supplier notice.

Does PCNshark integrate directly with Altium 365?

Manual handoff today — no native integration

PCNshark currently works alongside Altium 365 rather than acting as a native Altium integration.

Teams can upload supported BOM files to PCNshark, process supplier notices, identify notice-specific BOM impact, and reference the resulting record during their Altium, PLM, quality, or change process.

PCNshark does not read from or write to Altium 365. There is no API sync today.

What works today
  • Export your BOM from Altium (or another 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
  • Identify notice-specific BOM and product impact
  • Assign the owner and response
  • Export a BOM-impact CSV and a PDF impact report
  • Preserve the original notice and disposition
Not available today
  • Reading live designs, managed BOMs, or parts-in-use data from Altium 365
  • A live API sync or push between PCNshark and Altium 365
  • Direct import of a managed BOM straight from Altium (export the file and upload it)
  • A replacement for Altium's lifecycle, compliance, or sourcing data

PCNshark is a strong fit for Altium teams when:

PCNshark does not replace:

PCNshark complements these by managing the response to the actual supplier notice.

§ FAQ

Frequently asked questions

01Does Altium 365 already show lifecycle and EOL risk?
Yes. Altium 365 surfaces lifecycle status and related risk for the parts in your designs and managed BOMs. PCNshark does not replace that; it manages the response when an actual supplier notice arrives — extracting the affected parts and dates, matching them to your BOMs, assigning ownership, and tracking the response.
02How is PCNshark different from Altium BOM Portal?
Altium's BOM tools help you understand and manage the BOM and the parts in it, including lifecycle and sourcing context. PCNshark is the operating workflow for a specific supplier notice: capture the document, verify the affected parts and dates, match them to your BOMs, assign ownership, and preserve the disposition.
03Can PCNshark process supplier PCN PDFs?
Yes. Forwarded emails and uploaded PCN/PDN PDFs, including supported scanned documents, are PCNshark's primary intake. It extracts the affected MPNs, change details, and dates for review.
04Can PCNshark use BOM exports from Altium?
Yes. Export your BOM from Altium and upload the file — PCNshark accepts .csv, .tsv, .txt, .xlsx, .xls, and .xlsm. It does not import a managed BOM directly from Altium 365.
05Does PCNshark integrate directly with Altium 365?
No. There is no native integration or API sync today. PCNshark works from the BOM files you upload and the notices you receive.
06Can PCNshark identify affected projects or products?
PCNshark matches affected MPNs against the BOMs you upload and surfaces the affected products or assemblies in those BOMs.
07Does every PCN require a BOM change?
No. Many notices are accepted after engineering and quality review with no BOM revision. PCNshark still preserves the review, owner, evidence, and final disposition.
08Can PCNshark track LTB and qualification actions?
Yes. It keeps last-time-buy and last-ship deadlines and qualification follow-ups connected to the affected parts and products, with an owner and status.
09Can PCNshark preserve the supplier notice and disposition?
Yes. It keeps the original notice, the extracted and reviewed data, the BOM matches, the deadlines, the owner, and the final disposition connected as one record.

Move from BOM risk visibility to an owned supplier-notice response

Keep using Altium 365 to design and understand your BOMs. Let PCNshark manage the supplier notices that affect them: extract the affected parts and dates, match them to your BOMs, assign owners, and preserve the disposition.

Starter and Team include a 14-day trial. A payment method is required. Scale begins as a paid subscription. Keep Altium 365 as your design and BOM environment.
§ Keep reading

Related resources

§ Sources

Sources & references

  1. 01Altium 365 — overviewCloud design, managed BOMs, parts and supplier data.
  2. 02Altium 365 — BOM Portal / managed BOMsManaged BOMs, parts-in-use, lifecycle and sourcing context.

Product descriptions are based on publicly available Altium documentation and PCNshark's current production capabilities. Altium 365 capabilities and configurations vary. Confirm platform-specific behavior with your administrator or an Altium representative.

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