SAP in the Semiconductor Supply Chain — Research Brief

Outline changes. The approved Phase 0 outline was executed as six sections (1: footprint; 2: partnerships; 3: economics; 4: user pain; 5: financialization intersection; 6: open questions / Alex Zhu probes). No structural changes. One scope clarification: I treated PDF Solutions’ product as “Sapience Manufacturing Hub” (Sapience is the actual SAP- and PDF-published spelling per the SAP product page and the 2022 announcement); Andrzej used “Sapiens” verbally in the 2026-05-22 debrief. The two refer to the same product. Where I cite the interview I keep Andrzej’s phrasing; where I cite public sources I use “Sapience.”

1. SAP’s actual footprint in the semi supply chain — how it connects tiers

The cleanest single statement of the structural reality came from Andrzej Strojwas. “SAP is totally dominating all the transactions happening in semiconductor industry to the tune of like probably 95% — except that they have been really focusing much more on what’s known as the top floor.” [Interview: Andrzej Strojwas, 2026-05-22] That claim has two parts — a market-share assertion and a vantage assertion — and they need to be tested separately.

The market-share assertion is directionally well-supported in public data but not at exactly 95%. SAP itself states that “99 of the 100 largest companies in the world are SAP customers” and that ERP penetration in the Fortune 500 sits above 92% when SAP’s broader portfolio (ERP, HANA, Ariba, SuccessFactors, Business One) is included. [Public: SAP customer fact sheets aggregated by Prospect Wallet and TargetNXT, 2026] SAP serves ~425,000 customers globally as of 2026, with roughly 30,000 still on the legacy ECC on-prem base and the rest on cloud or S/4HANA. [Public: SAP FY2025 results; Constellation Research, 2026] Inside semiconductors specifically, TSMC publicly advertises an SAP ERP System Engineer requisition that names “SAP S/4 HANA, SAP EWM, BI, Group Reporting, and SAP Cloud solutions with cross-system integration” as the in-scope stack for finance, procurement, warehouse, and import/export. [Public: TSMC careers portal, 2026] Intel runs a 1997-vintage strategic partnership with SAP centered on co-development of HANA in-memory on Intel Xeon Scalable; Intel uses SAP ERP “from SAP ECC and SAP Suite to the latest S/4HANA systems.” [Public: Intel partner showcase page, 2025] NXP’s tech stack publicly references SAP Product Lifecycle Management and broader SAP usage. [Public: LeadIQ company profile, 2026] Renesas, ST, and Infineon were all named by Holly Rawlins as either on SAP or converging toward it. [Interview: Holly Rawlins, 2026-04-29] Infineon engaged LTIMindtree in 2023 to “modernise its SAP application landscape” across “both SAP S/4HANA and SAP Cloud Solutions.” [Public: Silicon Semiconductor news brief; LTIMindtree LinkedIn announcement, 2023] LX Semicon went live on SAP S/4HANA Cloud Private Edition with integrated treasury management for overseas-production expansion. [Public: SAP case study, November 2024]

The vantage assertion — that SAP is dominant in transactions but “blind” in manufacturing data — is the more interesting structural claim, and it is the one Andrzej’s company is built around. PDF Solutions’ Sapience Manufacturing Hub was announced in July 2022 explicitly to “connect factory data, including data collected and managed by [PDF’s] Exensio analytics platform, to the enterprise resource planning (ERP) data in SAP S/4HANA.” [Public: PDF Solutions / Globe Newswire, 2022-07-20] Jeff Howell, SAP’s Global VP for High-Tech, framed the use case as exposing “additional ROI from the data they already collect” to “companies that still control their own semiconductor manufacturing.” Kimon Michaels (PDF EVP and Andrzej’s referenced colleague) described the integration as “direct access to new sources of data that can be correlated with existing ERP data.” [Public: PDF Solutions press release, 2022] The fact that a top-100 semiconductor manufacturing intelligence vendor built a dedicated product to bridge SAP’s blind spot is itself the strongest public confirmation that the blind spot is real and economically significant.

How the layers actually slot together — what Andrzej would call the “top floor” and “shop floor” — is roughly this:

Layer	SAP module / product	What it does	What runs alongside
Financial transaction core	SAP ECC (legacy) / SAP S/4HANA (current)	GL, AP/AR, AR aging, COGS, group reporting, period close	Custom Z-reports, Excel exports
Procurement / supplier collaboration	SAP Ariba, SAP Business Network	Supplier onboarding, sourcing events, POs, invoicing, supplier qualification	EDI VANs (OpenText, IBM Sterling), Rainbow (Renesas custom) `[Interview: Holly, 2026-04-29]`
Order management / customer-facing	SAP SD (Sales & Distribution)	Customer master, sales orders, pricing, ATP, allocation	Salesforce (NVIDIA), Rainbow (Renesas)
Supply planning / demand planning	SAP IBP (Integrated Business Planning)	Demand consolidation, S&OP, capacity planning	Baxter Planning (NVIDIA forward demand) `[Interview: Lonny Orona, 2026-05-12]`, custom ML (NVIDIA AI on IBP) `[Public: Diginomica, 2022]`
Warehouse / logistics execution	SAP EWM (Extended Warehouse Management)	Inbound/outbound, putaway, picking, kitting	Expeditors / Omni / DHL (3PL execution) `[Interview: Lonny, 2026-05-12]`
Manufacturing execution / shop floor	SAP MII (legacy, feature freeze 2027 / EOL 2030) → SAP Digital Manufacturing (DM/DMC)	MES, OEE, work-in-process tracking, machine integration	PDF Exensio + Sapience Hub, MES vendors (Critical Mfg, Applied Materials SmartFactory, Camstar), FDC layer (PDF)
Product lifecycle / engineering	SAP PLM → reseller of Siemens Teamcenter (since 2020 partnership; expanded 2024)	BOM, change control, product cost, engineering data	Siemens Teamcenter (primary in semi PLM)
Treasury / risk / compliance	SAP Treasury & Risk Management, SAP GRC	Cash, FX, hedging, internal controls, access governance, international trade	Allianz Trade API into SAP/Oracle/MS, Coface API portal `[Public: Allianz Trade, Coface, 2025]`

[Public: SAP product portfolio pages, 2025–2026; Diginomica NVIDIA case, 2022; IIoT Blog DM-vs-MII analysis, 2025; Siemens Teamcenter SAP partnership blog, 2024]

The shape of the integration problem is clearer once that map is laid out. Holly Rawlins described Renesas as running SAP for customer order entry alongside a custom system called Rainbow that “persisted despite years of SAP migration planning — inertia is severe.” [Interview: Holly Rawlins, 2026-04-29] Lonny Orona at NVIDIA described exactly the same shape from the operational support side: “Salesforce (ticketing), SAP (material planning), Baxter (demand planning), Expeditors replacing Omni as 3PL. No integration across them.” [Interview: Lonny Orona, 2026-05-12] Diginomica’s coverage of NVIDIA’s SAP Business Network deployment quantifies the consequence — pre-Mellanox-integration “planning relied on disconnected Excel files causing ‘single source of truth’ issues,” and NVIDIA VP of IT Business Applications & Engineering Ron McCutchen explicitly cited Business Network as a tool to “quickly expand with an existing partner or onboard another partner in weeks” in response to “Suez Canal gets shut down, a new tariff or regulation; a new export control happens.” [Public: Diginomica, 2022] That is the same operational pain Lonny is now drowning in four years later — manual escalation under high-variability supply pressure, with SAP at the financial center but not integrated to the operational systems handling the actual exceptions.

Convergence: Internal interviews (Andrzej, Holly, Lonny) and external public reporting (Diginomica/NVIDIA, SAP customer references, TSMC job posts) agree that SAP is the financial transaction core across IDMs, fabless, foundries, and OSATs. They also agree that SAP does not extend coherently to either the manufacturing/MES layer or the customer-facing order/CRM layer at most semi companies — those layers run on a mix of SAP modules, custom systems (Rainbow), best-of-breed MES, and bolt-on planners (Baxter).

Divergence to flag: Andrzej’s “95%” figure is best treated as [Synthesis] rather than verified. Public ERP-market data supports 85–99% Fortune 100 penetration of SAP products but does not isolate semiconductor-industry transaction volume. The directional claim is sound; the exact figure should be tested against, e.g., a Gartner or IDC semi-industry-specific ERP penetration cut before being quoted externally. [Synthesis]

2. Strategic partnerships with major semi firms

The anchor partnership for Project TBD’s purposes is the SAP–PDF Solutions Sapience Manufacturing Hub, both because Andrzej directly framed it as the SAP blind-spot remediation, and because it is the only publicly documented case of SAP co-developing a semiconductor-industry-specific data integration product with a third-party manufacturing-data vendor. The hub was announced in July 2022. [Public: PDF Solutions / Globe Newswire, 2022-07-20] It links PDF’s Exensio Process Control and Exensio Manufacturing Analytics — both already in SAP’s industry-cloud portfolio — into SAP S/4HANA via SAP Business Technology Platform (BTP). [Public: SAP product page for PDF Sapience Manufacturing Hub, 2025] The traction in 2025 is real: PDF reported “record bookings” for Sapience Manufacturing Hub in Q1 2025, and an “eight-figure contract with a multinational IC manufacturing company to enable collaboration across its enterprise” closed during 2025. [Public: PDF Solutions Q1 2025 release, May 2025; PDF investor materials, 2025] Q1 2026 PDF revenue was $60.1M (up 26% YoY) with platform revenue up 36%; an eight- or nine-figure Exensio Test Operations booking was called out for a geographically distributed customer, and a “fab control software” booking landed with a large Asia fab customer. [Public: PDF Solutions Q1 2026 earnings, 2026-05-07] PDF’s stated 20% annual revenue growth target and the explicit attribution to “secureWISE, Sapience Manufacturing Hub, and Exensio” mean Sapience is now load-bearing for PDF’s growth thesis. [Public: PDF Q1 2026 transcript via Motley Fool, 2026]

Beyond PDF, the partnership map looks like this:

Semi firm	SAP footprint / partnership	Source	Confidence
TSMC	S/4HANA + EWM + BI + Group Reporting + SAP Cloud, in-house SAP engineering team	TSMC careers portal	High `[Public]`
Intel	SAP ECC → S/4HANA; HANA co-developed for Xeon since 1997	Intel partner showcase	High `[Public]`
Infineon	SAP S/4HANA + Cloud Solutions modernization with LTIMindtree (announced 2023)	LTIMindtree / Silicon Semiconductor	High `[Public]`
NXP	SAP PLM + broader SAP ERP stack	LeadIQ profile	Medium `[Public]`
Renesas	SAP for customer order entry alongside Rainbow custom system	Holly Rawlins interview	High `[Interview, 2026-04-29]`
STMicroelectronics	Described as SAP customer in the high-tech industry; specific go-live not located	SAP high-tech materials	Medium `[Synthesis]`
NVIDIA	SAP Business Network (live post-Mellanox 2022); SAP IBP with custom AI/ML; planned S/4HANA migration; SAP Material Planning module live; Joule and Agent Toolkit announcements (GTC 2026)	Diginomica 2022; Lonny Orona; NVIDIA newsroom, VentureBeat GTC 2026	High `[Public+Interview]`
LX Semicon (LG affiliate)	S/4HANA Cloud Private Edition + BTP with LG CNS; integrated treasury	SAP case study	High `[Public, 2024-11]`
Cadence	NVIDIA Agent Toolkit + Nemotron integration for ChipStack AI SuperAgent (EDA); not direct SAP customer-of-record but ecosystem-adjacent	NVIDIA GTC 2026	High `[Public]`
Synopsys	AgentEngineer + NVIDIA Nemotron multi-agent framework	NVIDIA GTC 2026, Synopsys Form 8-K FY2025	High `[Public]`
Siemens (PLM partner, not a fab)	Reseller agreement: SAP positions Siemens Teamcenter under SAP “Design to Operate”; Siemens positions SAP PPM and IAM. Partnership announced 2020, expanded 2024.	Siemens Teamcenter blog; SAP press	High `[Public]`
ASML	PDF’s Securewise covers ASML equipment remote access; no direct public SAP reference found	PDF Solutions / Andrzej	Medium `[Interview + Synthesis]`
Applied Materials	PDF’s Symmetrics acquisition brought equipment connectivity to 300+ clients; SAP-direct relationship not documented in this round	PDF / Andrzej	Low `[Synthesis]`

[Interview: Andrzej Strojwas, 2026-05-22] for the PDF claims, otherwise as noted above.

Two ecosystem-level efforts deserve callout because they extend SAP’s reach beyond a single customer:

Catena-X → Semiconductor-X. Catena-X is the German-initiated automotive data ecosystem (190 members globally as of 2025) where SAP is the leading provider of certified business applications and currently has “the most solutions on the market in the various Catena-X use cases.” [Public: SAP News Center, March 2025] BMW and Schaeffler use SAP Analytics Cloud and SAP Datasphere to implement Catena-X quality management. Ford added Catena-X to supplier contract terms from July 2024 — turning “voluntary collaboration” into “operational necessity.” [Public: Automotive Manufacturing Solutions, 2025] Critically, the broader Manufacturing-X umbrella has spawned a Semiconductor-X workstream alongside Factory-X (mechanical engineering) and Chem-X. [Public: Automotive Manufacturing Solutions; SAP News Center, 2025] Semiconductor-X is at an earlier stage than Catena-X, but the structural play is the same: a federated data-sovereignty model in which SAP positions itself as the canonical integration substrate. If Semiconductor-X reaches even modest critical mass, the de facto data interchange standard between semi tiers will pass through SAP’s certified product portfolio.

Siemens-SAP digital thread. The Siemens-SAP partnership (announced 2020, expanded 2024) creates a single digital thread between Siemens Teamcenter PLM and SAP Business Suite. [Public: Siemens blog, 2024] SAP is now a reseller of Teamcenter under the Design-to-Operate banner. In a semi industry where TSMC, Intel, and ASML all run Siemens MES/PLM software for shop-floor and product lifecycle, this partnership extends SAP’s effective coverage into engineering data without SAP having to build the layer itself.

NVIDIA AI agents / GTC 2026. At GTC 2026, NVIDIA launched the Agent Toolkit with SAP, Salesforce, Adobe, Cadence, Siemens, Synopsys, and 11 others as initial adopters. [Public: VentureBeat; NVIDIA newsroom, 2026] SAP is building Joule (its agentic AI layer) on top, and Cadence’s ChipStack AI SuperAgent runs on the Nemotron + Agent Toolkit stack. This is not a semi-supply-chain product per se, but it is the strongest signal yet that SAP intends to compete in the AI agent / orchestration layer above its transaction core — which is directly relevant to anyone considering an “SAP complement” product strategy.

3. SAP’s economics — how it makes money and where the business is shifting

FY2025 was the inflection year for SAP’s business-model transition. Group revenue was €36.8B, up 8% (11% at constant currency). Cloud revenue was €21.02B, up 23% (26% cc). Cloud ERP Suite revenue (RISE with SAP + GROW with SAP + S/4HANA Cloud) was €18.12B, up 28% (32% cc). IFRS EPS was €6.28, up 135%. Operating cash flow was €9.16B, up 76%. Free cash flow was €8.24B, up 95%. Predictable revenue rose to 86% of total. [Public: SAP Q4 2025 quarterly statement and FY2025 release, January 2026] Named FY2025 RISE go-lives in semiconductor / industrial customers include Lockheed Martin, Rolls-Royce SMR, adidas, BioNTech, Daimler Truck, Deloitte, H&M, and others. [Public: SAP Q4 2025 release] This is a recurring-revenue cloud business now — not the perpetual-license + 22% maintenance business SAP was a decade ago.

The migration deadline is the forcing function. SAP ECC 6 mainstream maintenance ends December 31, 2027, with extended maintenance available at +2 percentage points (~9% uplift on existing maintenance fees) through December 31, 2030. Some complex RISE customers can extend support to 2033. ECC 6 EHP 0–5 already lapsed at end of 2025 with no extension offered. [Public: SAP, summarized by Kellton/SAVIC/TJC/Rimini Street, 2025–2026] Migration projects take 18–36 months, and only ~39% of ECC customers had licensed S/4HANA as of late 2025; SAPinsider’s 2025 benchmark and the DSAG 2026 Investment Report converge on the picture of a market that is structurally behind schedule. [Public: SAPinsider S/4HANA Migration 2025; DSAG Investment Report 2026] The DSAG 2026 survey (n=198 senior leaders, Dec 2025–Jan 2026) found 37% of ECC users targeting end-of-2027 cutover, 4% aiming for 2033, and roughly half the German-speaking SAP user base planning to stay on ECC through 2030 under extended maintenance. [Public: DSAG via The Register and Constellation Research, 2026] 43% of respondents are increasing SAP spend; 28% are decreasing. Investment is “more targeted and critical.” [Public: DSAG Investment Report 2026]

Migration cost is the practical chokepoint. Fortune 500 migrations have publicly cost up to ~$400M; mid-market projects run €2M–€7M+. Consulting and custom-code remediation account for 45–60% of total spend. Average overrun is 30–50% over initial budgets. [Public: Liberty Advisor Group; Tachyon; SEIDOR; AiDOOS, 2025–2026] Holly’s “hundreds of millions of dollars and years of implementation time” framing for what it would take to displace SAP at a semi IDM is consistent with the public migration-cost data even for an in-place upgrade. [Interview: Holly Rawlins, 2026-04-29] [Public synthesis: Liberty/Tachyon/SEIDOR]

Where margin sits inside SAP’s stack:

Module / product line	Strategic role	Notes
HANA in-memory database	Co-developed with Intel since 1997; foundational	Powers S/4HANA, IBP, DMC, BTP
S/4HANA (Cloud and on-prem)	Core ERP; primary cloud growth engine	RISE = private cloud / S/4HANA Cloud Private Edition; GROW = public cloud for new/mid-market
Ariba + Business Network	Supplier collaboration and procurement	NVIDIA Mellanox onboarding case study; revenue grouped under Cloud ERP Suite
SuccessFactors	HCM	Slower growth segment; weak cloud backlog flagged by analysts in Q4 2025 `[Public: Nasdaq / ERP.Today, 2026]`
Concur	Travel & expense	Mature, low growth
Business Technology Platform (BTP)	Extension and AI/agent platform; Joule	Hosts PDF’s Sapience integration and Cadence/Synopsys NVIDIA agent integrations
SAP Digital Manufacturing (DM/DMC)	Replaces MII (feature freeze 2027, EOL 2030); cloud-native MES	The product that, in principle, could close Andrzej’s “blind to manufacturing data” gap from inside SAP
Treasury & Risk Management; GRC	Working capital, FX, hedging, controls, trade compliance	LX Semicon explicitly called out “integrated treasury management” as a value from S/4HANA Cloud Private Edition `[Public: SAP, Nov 2024]`

[Public: SAP product portfolio pages; SAP FY2025 release; ERP.Today, 2026]

The headline market dynamic: SAP is converting an installed base of 30,000-plus ECC customers into a recurring-revenue cloud-ERP business, with a hard policy deadline 19 months out (end-2027). Investment in non-core modules (HCM, T&E) is slowing; investment in core S/4HANA, BTP, DMC, IBP, and the Joule/Agent layer is accelerating. For a startup trying to build adjacent to SAP, the implication is that the next two years are the highest-leverage window — every semi customer migrating from ECC to S/4HANA is also re-evaluating its bolt-ons, and the cloud-native posture means SAP is more receptive to API-first partnerships than it has historically been. [Synthesis]

4. User feedback — the “load-bearing but clunky” tension

The clearest single line is from Andy at Skiffra: “SAP is great at reporting, bad at predicting.” [Interview: Skiffra/Andy, 2026-05-01 and 2026-05-02] Skiffra’s entire wedge — operator-floor UX above SAP for heavy industry — is built on this. Their POC at an Indonesian mine generated $100M in permanent annual EBITDA lift on $7M of fees by putting a red/green operator interface (volumetric cameras + weight sensors) on top of data SAP was already capturing but not delivering to the truck loader. Andy framed the structural critique as “We never think about what the guy operating the loader needs — we don’t think of him as a decision maker.” [Interview: Skiffra, 2026-05-02] That critique generalizes well to semiconductor manufacturing: SAP captures the transaction (PO, customer order, material movement) but does not deliver actionable real-time decision support to the person on the shop floor or the inside-sales rep handling a stuck change order. PDF’s Sapience Hub is the same diagnosis from a different angle — SAP knows the financial state but is “blind” to the manufacturing state.

The Renesas evidence sharpens it. Holly described multi-department customer onboarding as a “genuine friction point — industry check, volume threshold, legal, compliance, credit, all sequentially.” EDI setup is “a one-time but painful normalization problem that contractors handle in batches.” [Interview: Holly Rawlins, 2026-04-29] The Rainbow custom tool “persisted despite years of SAP migration planning” because SAP-native customer order entry never quite reached parity for Renesas’s specific workflow. Holly’s unprompted suggestion that “new U.S. manufacturers — perhaps they’re open to a new system” because they lack SAP entrenchment is the most concrete go-to-market hypothesis in our corpus around the inertia problem. [Interview: Holly, 2026-04-29]

Lonny’s NVIDIA account compounds this. He described his reverse-logistics stack as “no integration across them” with Salesforce + SAP + Baxter + Expeditors all siloed, and was explicit that “we have no time for in-house tooling” — meaning the integration tax that SAP’s modular structure imposes is, in 2026, a buy-side budget line item, not an internal build. [Interview: Lonny Orona, 2026-05-12]

The public-data side of practitioner pain is harder to query (Reddit search via WebFetch returned blocked, and broad Reddit searches for r/SAP+supply-chain produced mostly index pages), but the available signal is consistent:

DSAG 2026 investment respondents flagged that “cloud models, new SAP target visions, and AI” still have to “prove their economic benefits” relative to on-prem S/4HANA. 42% are putting medium-to-high investment in S/4HANA on-prem vs. only 6% in public cloud. [Public: DSAG via heise / impulsant, 2026]
Migration overruns average 30–50%; “many migrations are taking approximately 30% longer than originally planned, and in over 60% of surveyed firms, migration projects exceeded budget, schedule, or both.” [Public: SAPinsider 2025 benchmark; Tachyon 2026]
Fiori vs. SAP GUI complaints in the broader SAP community focus on “poorly designed Fiori landscape with poorly structured catalogs and authorisations” and gateway/registration issues that mirror the legacy GUI’s transaction-code complexity. [Public: SAP Community Q&A threads, 2024–2025]
Master data and change orders are the named pain in cross-industry coverage: “engineering teams spend days hunting for documentation… turning 4-hour root cause analyses into multi-week investigations.” [Public: Kinaxis blog on semi supply chain pain points; OpenText traceability blog, 2024–2025]

Two structural responses to this pain are visible in our interview corpus:

Build alongside. PDF (Sapience Manufacturing Hub) and Skiffra (operator-floor UX above SAP) are explicitly building products that sit above or alongside SAP, accepting SAP’s transaction dominance and arbitraging its UX and prediction gaps. PDF’s Q1 2025 “eight-figure contract” with a multinational IC manufacturer is the largest publicly disclosed Sapience deal and validates the build-alongside thesis as commercially viable. [Public: PDF Q1 2025 / Q1 2026 earnings]

Build separately to avoid dependency. Sid at Quince built the company’s vendor portal and supply chain management infrastructure in-house specifically out of “aversion to platform dependency (Shopify, SAP),” and is now positioning that custom stack as a sellable B2B retail platform. [Interview: Sarah Quince, 2026-05-08] Susan Athey’s “Trojan horse” warning generalizes the risk: “add-ons can be quietly strangled by the platform they depend on. This maps directly to any TBD distribution strategy that routes through Bloomberg Terminal, SAP, or Oracle data environments.” [Interview: Susan Athey, 2026-05-06] This is the most pointed disconfirming voice we have on the build-on-SAP strategy.

A third pattern — don’t touch SAP at all — surfaced in Vivian’s account of Taiwan deep-tech sourcing. NVIDIA’s approach to finding suppliers in Taiwan is described as “no centralized platform — entirely network-based sourcing via phone calls and relationships.” [Interview: Vivian, 2026-04-29] SAP doesn’t touch the discovery step. This is a critical scoping point: SAP is dominant in transactions (POs, invoices, financial movement of qualified suppliers) but is largely absent from discovery and qualification of new suppliers in the highest-volatility tiers of the semi supply chain.

Convergence (interviews + public): Both internal voices (Holly, Lonny, Andy, Andrzej) and public reporting (DSAG, SAPinsider, Kinaxis) describe SAP as the unavoidable financial core that has a known and persistent UX/prediction/integration gap, especially on the shop floor and at customer-facing edges.

Divergence to flag: Internal voices (Holly: “greenfield U.S. fabs are open to a new system”; Sid: “built custom to avoid dependency”) suggest the SAP lock-in is breakable in specific contexts. Public reporting on switching costs and DSAG investment behavior suggest the opposite — incumbents are doubling down on S/4HANA migration, not exploring SAP alternatives. The reconciliation is likely segmentation: new entrants (U.S. greenfield fabs, vertically integrated DTC) may be in play, but the IDM/foundry installed base is not. This is the most important question for go-to-market segmentation.

5. Where SAP intersects the financialization wedge

This is the section that most directly tests the active thesis, and it is where the evidence is thinnest and most speculative. The structural question Andrzej posed back to us is the right one: “If a compliance product needs to integrate with how money and orders flow, that is SAP territory — and PDF’s partnership with SAP is a potential channel or constraint worth understanding before building.” [Interview: Andrzej, 2026-05-22, paraphrased from "For Founders" section] The same framing applies, with even more force, to a financialization product whose triggers and payouts depend on real-time visibility into transactions and operational state.

What SAP already offers in this neighborhood. SAP Treasury and Risk Management sits inside S/4HANA’s financial-management portfolio and covers “working capital, long-term liquidity, and mitigation of financial risk.” [Public: SAP product page, 2025] SAP GRC (“Governance, Risk, and Compliance”) is “organized around four pillars: enterprise risk and compliance, identity and access governance, cybersecurity and data protection, and international trade management.” [Public: SAP GRC product page, 2025] LX Semicon’s case study explicitly highlighted “integrated treasury management” as a benefit of moving to S/4HANA Cloud Private Edition. [Public: SAP, November 2024] So the financial-risk workflow layer is in SAP’s portfolio today, but it is internal-controls and corporate-treasury oriented, not external-market-instrument oriented.

Where third-party financial instruments plug in. Allianz Trade — the global trade credit insurance leader with ~32% market share — offers an API “to integrate business intelligence and policy features into SAP, Oracle, Microsoft, and other ERP systems in real-time.” Coface (#2 at ~15%) offers an analogous Coface API Portal. [Public: Allianz Trade and Coface API pages, 2025] These are the existing analog: third-party financial risk-transfer products plug into SAP at the procurement / AR layer via API, without SAP itself being the underwriter. Munich Re and Swiss Re both offer parametric insurance products structured around “predetermined triggers and payout schemes” but neither has a publicly documented direct SAP integration partnership at the time of writing. [Public: Munich Re parametric solutions page; Swiss Re corporate solutions page, 2025]

The signal from the CME compute futures launch (2026-05-12). CME Group and Silicon Data launched the first compute-futures product on May 12, 2026 — derivatives on GPU rental rates, not physical chips. [Public: CME/CNBC, 2026-05-12, cross-referenced in Glencore-of-semiconductors brief, 2026-05-13] This is a real-world example of a financialization product that bypasses SAP entirely because the underlying (GPU rental rates per index) is observable from outside any ERP. The implication for Project TBD: where the trigger can be sourced from non-ERP data (telemetry from a fab parametric sensor, public memory spot prices, GPU rental indices), SAP integration is not required. Where the trigger or payout requires customer-specific transaction or operational state, SAP integration becomes the path of least resistance — and possibly the structural channel.

The “if 95% of transactions flow through SAP” framing in practice. A parametric insurance trigger that depends on “this fab shipped fewer wafers than X last week” or “this OSAT’s average dwell time exceeded Y” or “this customer’s contract LTA was breached” requires SAP-side data, because that is where the financial events are recorded. A trigger that depends on “humidity in the cleanroom” or “spot price of DDR5 16GB DIMM” does not. The first class of triggers is the higher-leverage class for capturing willingness-to-pay (it is closer to the company’s actual P&L), but it is exactly the class where SAP can decide to become a partner, a channel, or a ceiling. The Athey “Trojan horse” warning lives in this gap. [Interview: Athey, 2026-05-06]

Falsification check — “What would make this wrong?”

If a Munich Re / Swiss Re / Allianz announces a direct SAP-integrated parametric product for industrial supply chains in the next 12 months, the channel question becomes “we ride alongside or under that partnership, not in front of it.” No such announcement has surfaced in this round of research. [Public, 2025–2026]
If the financialization wedge can be entirely sourced from non-ERP data (sensor telemetry, public price indices, public logistics data), SAP integration is not required at all, and the build-alongside-PDF analog becomes irrelevant. The CME compute-futures example shows this is possible in adjacent markets.
If SAP itself launches a parametric insurance / supply-chain risk-transfer product as part of its BTP/Joule push, the wedge gets compressed from above (Athey’s threat-of-complements scenario realized inside SAP’s own portfolio). We have not found public signal of this in 2025–2026, but it is the canonical incumbent-suppression risk for any product built as an SAP add-on. [Synthesis]
If Semiconductor-X reaches critical mass and becomes the canonical inter-tier data interchange standard, the data substrate for parametric triggers passes through SAP-certified BTP applications by default, and again the channel/partner question dominates. [Public: Manufacturing-X / Semiconductor-X scope, 2025]

What would be useful from Alex Zhu specifically on this section: does NVIDIA’s Treasury group already hedge wafer-pricing or warranty-exposure risk through any external instruments, and if so, does that flow touch SAP Treasury & Risk Management, or sit entirely outside in a separate treasury management system?

6. Open questions and Alex Zhu-specific probes

High-priority open questions across the brief

Sanity-check the 95% figure. Andrzej’s “95% of semiconductor transactions” claim is directionally well-supported (85–99% Fortune 100 SAP penetration) but not directly verified at the semi-industry level. Who could answer: a Gartner SCM or IDC semi-industry analyst; the SAP High-Tech industry lead (Jeff Howell, quoted in the PDF announcement); or a CTO/CIO at a top-15 fabless company.
Where exactly is SAP “blind” vs. “covered”? Andrzej framed manufacturing data as the blind spot. But SAP Digital Manufacturing (DMC) is a real product replacing MII by 2030. Is DMC closing the gap, or is its semiconductor adoption marginal? Who could answer: Kimon Michaels (PDF EVP, Andrzej offered intro); John Kibarian (PDF CEO, also offered); Jeff Howell (SAP).
What is the SAP-side commercial model for Sapience Manufacturing Hub? Is it bundled into a customer’s existing S/4HANA spend, sold as a BTP industry-cloud module, or sold standalone by PDF? The answer determines whether the build-alongside model scales. Who could answer: PDF investor relations or a Sapience customer.
What is the ARR/ACV per large semi customer? Public SAP filings don’t disclose per-customer spend, but Fortune 500 enterprises commonly spend in the high single-digit to low nine-figure range annually on SAP licensing + maintenance + services. Who could answer: an SAP account exec covering semiconductor accounts; a CIO who has run the budget.
How does Semiconductor-X compare to Catena-X in maturity? Semiconductor-X is the most consequential ecosystem play for cross-tier data sharing — and the most direct competitor to any “supply chain digital twin” wedge that doesn’t ride on SAP rails. Who could answer: a Manufacturing-X working-group participant (likely Fraunhofer, ZVEI, or a German semi industrial — Infineon or Bosch).
Are there documented SAP–parametric insurer partnerships in 2025–2026? None surfaced. Who could answer: Munich Re / Swiss Re / Allianz commercial product team; SAP BTP industry-cloud lead.
Holly’s “greenfield U.S. fab” hypothesis. Does TSMC Arizona, Intel Ohio, or Samsung Taylor have an ERP greenfield posture — or is it just SAP again? Who could answer: a director of operations or IT at one of those facilities, or a systems integrator on those projects.
Is Rainbow real elsewhere? The Renesas Rainbow case suggests every major IDM has at least one persistent custom workflow tool alongside SAP. Identifying these tools is identifying the most leveragable integration surfaces. Who could answer: Inside-sales or operations veterans across Infineon, ST, NXP, ON Semi.

Alex Zhu-specific probes (layered on top of the existing briefing)

The existing briefing (memory/synthesis/briefing-alex-zhu-2026-05-27-final.md) covers Alex’s likely vantage point and 9 opening questions. The SAP-specific layer to add is:

“You came in with an SAP SD background. From where you sit at NVIDIA, what does SAP actually own end-to-end, and where does it hand off to other systems?” Tests Alex’s own articulation of the SAP footprint — and whether his definition matches Andrzej’s “95% of transactions” framing.
“NVIDIA’s been on SAP Business Network since the Mellanox integration. From your seat, has that delivered the supplier onboarding speed Ron McCutchen described in 2022, or is the integration tax Lonny described — Salesforce, SAP, Baxter, Expeditors all siloed — still the dominant pattern?” Tests whether the four-years-on reality matches the 2022 Diginomica narrative. [Public: Diginomica, 2022] vs. [Interview: Lonny, 2026-05-12]
“Where is NVIDIA on the ECC-to-S/4HANA path, and how does that migration interact with the reverse-logistics build-out?” Lonny mentioned SAP material planning but did not name S/4HANA specifically; Alex’s SAP lineage is the right test for whether NVIDIA is mid-migration. Migration timing affects when adjacent tooling buys happen.
“Have you seen SAP Digital Manufacturing or SAP Manufacturing Integration in scope for NVIDIA, or is manufacturing execution entirely owned by the contract manufacturers (Wistron, FoxConn, Quanta)?” Tests whether the “SAP blind to manufacturing” framing applies — NVIDIA outsources manufacturing, so the answer is plausibly “we don’t run an MES because TSMC/Wistron do,” in which case the Andrzej framing doesn’t bind NVIDIA in the same way it binds IDMs.
“From the SAP side, where do warranty reserve, RMA accounting, and advance replacement inventory actually live? Treasury? Operations? Material Planning?” NVIDIA held $8.22B in warranty reserves at end of FY2025 per the existing reverse-supply-chain brief — that is exactly the kind of balance-sheet item a warranty-insurance product would address, and Alex’s SAP lineage is the right channel to ask whether it touches SAP Treasury & Risk Management or sits separately.
“Have you seen any third-party financial-risk products plug into SAP at NVIDIA — trade credit, supply chain finance, parametric? Or is risk transfer entirely handled in a separate treasury system?” Direct test of the financialization-wedge channel question.
“Renesas had a custom tool called Rainbow alongside SAP. Does NVIDIA have an equivalent — a system that didn’t get displaced when SAP rolled in, or one built specifically because SAP wasn’t enough?” Specific, concrete, non-leading.
“If a third party built a product designed to plug into SAP and cover one specific blind spot, what would you tell them to focus on?” Open invitation for Alex to volunteer a target.

Tiered intro requests to consider after the call

Tier 1 (already offered): Greg DeLoccio (systems integration lead, NVIDIA), per Lonny.
Tier 1 (already offered): John Kibarian (PDF CEO) and Kimon Michaels (PDF EVP, Sapience Manufacturing Hub product owner), per Andrzej.
Tier 2 (to ask Alex): Anyone in NVIDIA Treasury or Risk Management who manages the warranty reserve / supply-chain risk-transfer side.
Tier 2 (to ask Andrzej, if natural): Jeff Howell (SAP Global VP, High-Tech) — quoted in the 2022 Sapience announcement; the closest publicly named SAP-side semi industry executive.
Tier 3: A Manufacturing-X / Semiconductor-X working-group contact (likely via Fraunhofer or Infineon).

Surprises and contradictions

The PDF–SAP partnership has measurable commercial traction. When the Andrzej meeting happened, it was unclear whether Sapience Manufacturing Hub was an early-stage joint-marketing partnership or a real product with bookings. Public 2025 earnings disclose “record bookings” and an “eight-figure contract with a multinational IC manufacturing company.” [Public: PDF Q1 2025 / Q1 2026] The structural blind-spot problem is real and somebody is being paid to fix it. That tightens the competitive landscape for any TBD product targeting the same gap.
Semiconductor-X exists. The Catena-X automotive consortium has explicitly spawned a semiconductor-industry workstream as part of the Manufacturing-X umbrella. [Public: SAP News Center / Automotive Manufacturing Solutions, 2025] This had not surfaced in our prior interviews and is potentially the most consequential ecosystem play we have not yet investigated — it is the canonical inter-tier data interchange standard, and SAP is positioning itself as the dominant certified-applications vendor inside it.
NVIDIA’s SAP IBP deployment used custom AI/ML models in 2022. Ron McCutchen’s 2022 Diginomica interview describes a more sophisticated SAP IBP + custom AI integration than Lonny’s 2026 account suggests is in place on the reverse side. [Public: Diginomica, 2022] vs. [Interview: Lonny, 2026-05-12] This is a real contradiction worth pressing Alex on. Either the IBP+AI work was concentrated on forward demand and the reverse side was never built out, or Lonny’s “manual at scale” perception is incomplete because his team is one of four pillars and he doesn’t see the upstream IBP work.
Half of German SAP customers will stay on ECC through 2030 under extended maintenance. DSAG 2026 confirms that even a 19-month policy deadline is not a forcing function for ~50% of the installed base. [Public: DSAG via The Register, 2026] This challenges the narrative that the S/4HANA migration is a creating a uniform window of disruption — it is creating a segmented window where roughly half the market is migrating and half is paying the maintenance premium to delay. The TBD-relevant question is which segment has the higher willingness-to-pay for adjacent products.
SAP DMC sunsets MII in 2030 — but SAP is also a reseller of Siemens Teamcenter. SAP’s own manufacturing-execution product is being modernized (MII → DM/DMC by 2030, feature freeze 2027), while at the same time SAP positions Siemens Teamcenter as part of its Design-to-Operate stack. [Public: IIoT Blog 2025; Siemens Teamcenter blog 2024] SAP is simultaneously building and reselling in the manufacturing-data layer Andrzej identified as the blind spot. The blind spot may be closing from two directions at once — and PDF’s Sapience Hub may be a middle-layer product whose addressable space narrows as DMC matures.
Athey’s “Trojan horse” warning lands differently in 2026. When Athey said it on 2026-05-06, the canonical example in her framing was Bloomberg Terminal. By 2026-05-12 — six days later — CME Group + Silicon Data had launched compute futures, which is a parametric financial product that doesn’t run through Bloomberg at all. [Public: CME/CNBC, 2026-05-12] The “Trojan horse” risk is real, but so is the existence of paths that route around the incumbent data layer. The question for SAP specifically is whether the parametric financialization layer can also route around it, or whether the transaction-state requirement forces dependence.
The “build alongside SAP” model has stronger traction than the “displace SAP” model. PDF Sapience Hub bookings, Allianz Trade and Coface APIs into SAP, the Siemens-SAP reseller deal, and the NVIDIA Agent Toolkit + SAP Joule integration all point in the same direction. No public 2025–2026 evidence emerged of a successful “displace SAP at a semi IDM” play. Holly’s “greenfield U.S. fab” hypothesis remains untested but is the strongest contrary case in our corpus. [Interview: Holly, 2026-04-29]
Vivian’s “no centralized platform — entirely network and phone” describes a layer SAP doesn’t touch at all. Supplier discovery and qualification in the highest-volatility tiers of the Taiwan ecosystem happens outside SAP entirely. [Interview: Vivian, 2026-04-29] This is a scoping correction to Andrzej’s 95%: SAP dominates the transaction layer after a supplier is qualified, but not the discovery layer before. A product that targets discovery and qualification is not in SAP’s shadow.

Confidence summary

Claim	Confidence	Basis
SAP is the dominant ERP across the major semi IDMs, foundries, fabless, and OSATs	High	Multiple public references (TSMC, Intel, Infineon, NXP, LX Semicon, NVIDIA) + Holly/Andrzej/Lonny interviews
Andrzej’s “95% of transactions” is directionally correct	Medium-High	Consistent with 85–99% Fortune 100 SAP penetration; not directly verified at semi-industry granularity
SAP is structurally weak in manufacturing data (“shop floor”) at IDMs	High	Andrzej’s interview + PDF Sapience Hub product existence + SAP’s own DMC roadmap acknowledges the gap
The PDF Sapience Manufacturing Hub has real commercial traction	High	PDF Q1 2025 “record bookings” + 2025 eight-figure contract + 2026 platform revenue +36% YoY
SAP ECC mainstream maintenance ends 2027 with extended-maintenance option to 2030 (2033 for RISE)	High	SAP public roadmap + DSAG + Rimini Street consensus
~Half of German SAP customers plan to stay on ECC through 2030	High	DSAG 2026 Investment Report
NVIDIA runs SAP Business Network + IBP + SAP material planning, with Baxter and Salesforce alongside	High	Diginomica 2022 public + Lonny 2026 interview
Semiconductor-X is a real and active workstream	Medium-High	Multiple public references; maturity vs. Catena-X unverified
There is no documented SAP–parametric-insurer partnership in 2025–2026	Medium	Absence of evidence in 2025–2026 search; not exhaustive
Build-alongside-SAP has stronger 2025–2026 traction than displace-SAP	Medium-High	PDF Sapience, Allianz/Coface APIs, Siemens-SAP reseller, NVIDIA-SAP-Cadence-Synopsys Agent Toolkit — all converging
Athey’s “Trojan horse” suppression risk applies to any SAP add-on	Medium	Theoretical framework from STRAMGT 3862; no specific SAP-add-on suppression case identified in 2025–2026
SAP DMC will close the manufacturing-data blind spot Andrzej described	Speculation	SAP’s stated roadmap; semi-industry adoption pace unknown

Sources

Internal (vault):

/home/ssm-user/project-tbd/memory/interviews/2026-05-22-mtng-w-andrzej-strojwas-pdf-and-bliss-perry-and-dustin-ross.md
/home/ssm-user/project-tbd/memory/interviews/2026-04-29-call-holly-rawlins-re-renesas.md
/home/ssm-user/project-tbd/memory/interviews/2026-05-12-lonny-orona.md
/home/ssm-user/project-tbd/memory/interviews/2026-05-01-zoom-dustin-ross-skiffra.md
/home/ssm-user/project-tbd/memory/interviews/2026-05-02-zoom-dustin-ross-skiffra.md
/home/ssm-user/project-tbd/memory/interviews/2026-05-06-stramgt-3862-athey.md
/home/ssm-user/project-tbd/memory/interviews/2026-05-08-sarah-quince-dustin-gsb.md
/home/ssm-user/project-tbd/memory/interviews/2026-04-29-vivian-bliss-dustin.md
/home/ssm-user/project-tbd/memory/synthesis/2026-05-08-working-hypotheses.md
/home/ssm-user/project-tbd/memory/synthesis/glencore-of-semiconductors-2026-05-13.md
/home/ssm-user/project-tbd/memory/synthesis/reverse-supply-chain-research-2026-05-13.md
/home/ssm-user/project-tbd/memory/synthesis/briefing-alex-zhu-2026-05-27-final.md

External:

Brief authored 2026-05-27 by Project TBD research workflow. Anchor interview: Andrzej Strojwas (PDF Solutions, CMU), 2026-05-22. Companion call: Alex Zhu (NVIDIA Operations), 2026-05-27 — see briefing-alex-zhu-2026-05-27-final.md for the call-specific brief that this background research feeds into.

Project TBD Memory Vault

Explorer

sap-in-semiconductor-supply-chain-2026-05-27