Territory · Substrate signal

01The leadership-evolution playbook.

New supply-chain leadership arrived from a peer that built control-tower + AI = published €100M operational value + Gartner Top 25 (first time). The data layer at SBD exists. The orchestration layer above is the unbuilt floor.

Where Caddie sits

One layer above your existing data plumbing.

Customers · retail · dealers · plants

↓

CADDIE · agentic execution · read · draft · execute · audit

↓

SAP S/4 + Central Finance

The SAP planning layer

SAP Ariba + Keelvar

Manufactory 4.0

IoT / RFID telemetry

Caddie reads across the existing stack, drafts cross-system actions, executes on dispatcher approval, leaves audit trail.

Read

cross-system query in plain English

Draft

cross-system action proposed

Execute

dispatcher one-tap · writeback to systems

Audit

trail behind every action

What we read

The board · the appointment · the playbook precedent.

Board framing · Jun 2025

"As the company approaches the end of its supply-chain transformation and looks ahead to the next horizon."

SBD Newsroom

Chief Supply Chain Officer appointment · Dec 2025

Hire from a peer where they ran end-to-end SC across 50 plants + 13 DCs.

SBD Newsroom

The peer playbook · €100M

Control tower + AI → 6-day inventory reduction · 6-day delivery reduction · €100M+ value · €30M productivity. Topped Gartner Top 25.

DC Velocity · SCMR

What Enmovil delivers here

Three surfaces. One orchestration layer.

Cross-system visibility

Reads across SAP + planning + telemetry into one delivery estimate-and-landed-cost picture. Sits above existing IoT/RFID + control-tower data.

Caddie · agentic execution

Drafts cross-system action on exception. Dispatcher one-taps. Caddie writes back across the systems of record. Audit trail.

Conversational query → SAP writeback

Plain-English in. Decision out. Writeback on approval. Minutes, not the multi-hour SAP-native reporting cycle.

Proof anchor

Where we've shipped this shape.

90 min

Conversational query → SAP writeback · a Fortune 500 manufacturer

40 → 5 min

Manual reports compressed · same deployment

16h → 0h

Overnight forecast job retired entirely · same deployment

40% / 30%

Fewer client inquiries · faster exception resolution · a global lead-logistics provider operating across 50+ countries

For the conversation

Questions, fence, timeline.

Replicate the architectural shape on top of S/4 + Manufactory 4.0, or rebuild from the data layer up?
What sits ON the orchestration layer above your existing data plumbing today — homegrown, integrator-built, or empty?
If a first-lane Caddie deployment showed measurable cycle-time effect inside one quarter, where does the second lane land?

We'd touch

Cross-system reconciliation · SAP + planning + carriers + customers
Drafted decision + dispatcher approval + audit trail
Conversational query → SAP writeback
The orchestration layer above existing data infrastructure

We wouldn't

SAP S/4HANA replacement
the SAP planning layer replacement
Sourcing optimization (Keelvar)
Shop-floor / Manufactory 4.0

6-8 weeks · one cross-system flow

SAP ECC integration is Enmovil's deployed baseline (3-4 weeks); S/4HANA Cloud variants run longer. First lane: one instrumented flow + 90-day historical backtest.

Who's building this

Enmovil · the technology thought partner for autonomous supply chains.

One AI-native platform. Demand sensing, inventory, dispatch, execution, freight settlement, sustainability reporting. All on one intelligence layer that sits above the systems you already own.

Under orchestration

~100K

Trucks per day across the deployment base

Daily delivery accuracy

99%

Road, rail, ocean, air

Forecast accuracy

97%

Demand sensing across deployments

Logistics cost savings

8 to 15%

Measured across deployments