Solution · Supply Chain
Finished-goods inventory, the OEM's call-off schedule, and your carrier ETAs in one agent view. Foreman flags slipping shipments and proposes the recovery while it's still cheaper than the scorecard hit.
The pain
OTIF is the metric that decides next year's contract, and the way most Tier-1 plants track it is by reading the OEM's own scorecard on Monday. By the time you see the dip, the shipment that caused it has already arrived late, the customer has already logged the penalty, and the only thing left is to explain it.
The signals were there. The carrier rescheduled the pickup on Tuesday. Finished goods were short by 8 units on Wednesday. The customs broker held the export documents until Thursday afternoon. Nobody connected the three in time, because nobody was watching the three together.
Your account manager spends Monday morning writing apologies for misses that a quieter system could have prevented, while the planner who actually could have acted only saw two of the three signals — and not the one that mattered.
What Foreman does about it
Foreman watches every open shipment against the OEM's call-off window. The moment finished-goods stock, carrier ETA, or export-clearance status drifts, the shipment's OTIF probability updates — and so does the lead time you have to act.
Built on · Decision Layer · Digital Twin
Partial ship now and follow-up tomorrow? Swap carrier? Expedite? Foreman proposes the recovery path your logistics manager would have chosen — with cost, OEM-impact, and feasibility shown — so the call is made in five minutes, not five emails.
Built on · Agent Engine
When OTIF risk crosses the threshold where a recovery isn't enough, your account manager gets the heads-up before the OEM does — with a drafted note that explains what's slipping, what you're doing, and when the customer will see normal service again.
Built on · Decision Layer
Every OTIF miss, every recovery taken, every contributing cause is logged with its inputs. When the OEM disputes a scorecard entry — or when finance asks why an expedite was paid — the answer is one query away.
Built on · Decision Layer
What we'd move
OTIF improvement on the highest-volume OEM lanes in the first quarter — driven by catching slips while a cheaper recovery is still possible.
Reduction in late-discovery OTIF misses — events where the planner finds out from the OEM scorecard, not their own system.
OTIF events logged with cause, recovery, and outcome — every scorecard dispute defensible by trail, not by memory.
* Discovery-stage estimates from outbound-flow walkthroughs with Tier-1/2 plants. Replaced with measured numbers as pilots run.
The one outcome that matters
Foreman collapses the gap between the first slipping signal and the planner's recovery from hours-after to minutes-before, with the trade-off shown.
Where it lands
ERP & WMS
Finished-goods inventory, allocation, and pick-pack-ship status from SAP, Oracle, Manhattan, or your in-house WMS — read-only by default.
OEM EDI & portals
OEM call-off schedules via EDI 830/862, ASN confirmations, and OEM-portal scorecard signals. Foreman reconciles them against your real outbound state.
Carrier & customs
Carrier-tracking APIs, freight-forwarder feeds, customs-clearance status. Late pickup or delayed export-document release lands in the same view as the OTIF impact it causes.
We don't replace your TMS or WMS — we make the planner running them twice as effective by closing the loop between outbound signal and OEM-scorecard consequence. See the full integration list →
Industry fit
Field notes
A 30-minute call to walk through your outbound flow, your OEM-call-off cadence, and the misses Foreman would have caught a day or two earlier.
