Supplier risk, read as an execution system.

Concentrated dependencies cascade.

Situation: multi-site supply with concentrated external dependencies. Risk: a single break cascades across markets. Intervention: resilience read of the operating model and cross-functional handoffs — see the global shipment resilience use case. Boundary: execution architecture — not demand planning or QP release.

The vendor master is a risk surface.

• Vendor master data, controls and governance stabilized through the carve-out of Bayer Animal Health (Elanco).
• Ownership per data domain instead of shared ambiguity.
• Controls designed for audit reality — 12 P2P SoX controls developed and implemented.

When price risk becomes conduct risk.

• Toyota Motor Europe (2012–2015): investigation champion in a wire-harness price-cartel case.
• EUR 90M in savings via one-shot D&D payment versus piece-price — commercial structure used as a risk instrument.
• Awarded for process value-added analysis.

Continuity through transformation.

• Stabilization lead through a carve-out while the P2P organization moved from 30 to 17 experts.
• A global power-user network — 130 power users, 35 captains, 35 countries — as continuity infrastructure.
• Daily support operations without ticketing, through hypercare and beyond.

What a resilience read covers.

Operating model, ownership, handoffs, escalation paths and decision rights around your critical suppliers — named, bounded and decision-ready. The output is a read and a next step, not a software rollout.

The honest boundary.

These are employment and assignment contexts — publicly verifiable career facts, no current client relationships implied. Resilience reads support the continuity decision; they do not replace demand planning, quality or regulatory functions.