← All territories
Territory 02 · Just-in-time cadence

Territory · Substrate signal

02Just-in-time cadence.

VP Jennifer Johnson (publicly): "hot jobs" with four-hour notice require on-the-fly rescheduling traversing inbound material availability, factory throughput, finished-goods inventory, bill-of-materials, labor. OEM line-down penalties + raw-material index lag = working-capital squeeze.

Four-hour notice · five-system traverse.

Detect
OEM call-off changes · 4-hour window
Read
inbound + throughput + finished goods + BOM + labor
Draft
reroute / expedite / reassign / reschedule plan
Execute
one-tap planner approval · writeback to systems

The cadence reality.

VP Jennifer Johnson · public

"How do we orchestrate the convergence of hot jobs with four-hour notice that traverses inbound material availability, factory throughput, finished-goods inventory, BOM, labor."

Palantir LinkedIn

OEM line-down economics

Tier-1 automotive suppliers carry 4-6% adjusted margins. OEM line-down penalties + raw-material index lag = working-capital squeeze. Hot-job execution is margin-defining.

Tier-1 automotive industry benchmarks

Tariff exposure

Tariff exposure called out as a top-tier 2025 problem (Palantir use case #1 with Lear). Hot-job execution under shifting tariff inputs amplifies the orchestration challenge.

Lear-Palantir public material

Three moves · one hot-job loop.

Five-system read

When a hot job lands, Caddie reads inbound material + factory throughput + finished-goods inventory + bill-of-materials + labor in one query.

Drafted execution plan

Drafts the reroute / expedite / reassign / reschedule action across the affected systems for planner one-tap approval.

Writeback + audit trail

Caddie executes the approved chain across SAP + carrier systems + supplier portals · audit trail behind every action.

Where we have shipped this shape.

90 min

Cross-system query → SAP writeback · Fortune 500 manufacturer

4x faster

Exception response · 4-6 hours down to under 30 minutes · across deployments

~99%

Estimated delivery accuracy across multimodal deployments

Questions, fence, timeline.

  1. When a hot job lands at four-hour notice, what's the actual reconciliation flow today across inbound material, factory throughput, finished-goods inventory, and labor?
  2. Is the hot-job orchestration today Palantir Foundry-orchestrated or planner-driven on top of Foundry?
  3. Where would a first-lane pilot land — one plant's hot-job stream, one OEM customer, or one product line?

We would touch

  • Five-system read on hot-job trigger.
  • Drafted execution plan + planner one-tap approval.
  • Writeback to SAP + carrier + supplier systems.
  • Audit trail per hot-job action.

We would not

  • SAP MRP / production scheduling replacement.
  • Palantir Foundry replacement (Caddie sits above).
  • OEM customer call-off systems.
  • Plant labor scheduling systems.
6-8 weeks · one plant's hot-job stream

First lane: one plant's hot-job stream instrumented for five-system read + drafted execution + audit trail, with 90 days of historical hot-job logs for backtest.

← Previous01 · Raw-material volatility All territories Next →03 · Carrier tendering + audit