Every load has its own clock. Every customer has its own SLA. The Captain watches both.
Pure-play carriers move physical product across truck, rail, ocean, air, and parcel — across multiple TMS instances, multiple modes, and dozens of shipper SLAs. OpsATC.AI is the AI-native orchestration layer above your TMS, dispatch, EDI gateway, and customer ERP feeds. The Captain reads live dispatch and event data, ranks exceptions by penalty exposure, drafts the response, and answers "where is my freight" with a cited line from the carrier event log — not a hallucinated paragraph.
The five operations that consume your week.
In the discovery conversations we've had with carriers and freight movement companies, a recurring pattern keeps surfacing — different modes, different TMS instances, the same five drains. The Captain is designed around exactly these.
Dispatch & load-planning chaos
Multiple TMS instances, multiple modes, real-time capacity volatility. Drivers idling at docks while planners stitch loads across three systems. Every minute of swivel-chair planning is a minute the asset isn't moving.
Multi-modal visibility blind spots
Truck, rail, ocean, and air segments live in different systems. The customer asks "where's my freight" and ops scrambles across three tools and a carrier portal to reconstruct the answer — usually after the SLA has already drifted.
OTIF + dwell exposure
Every shipper has different OTIF targets, dwell penalties, and accessorial rules. Tracking exposure manually is a full-time job — and the penalty is usually booked before the pattern is visible.
Carrier capacity volatility
Spot rates swing daily, equipment is tight on some lanes and slack on others, and quotes get committed without real-time visibility into available capacity. By the time the gap shows up, you're either turning freight away or buying spot at a margin loss.
Exception management
Delays, dwell, customs holds, accessorials, demurrage — exceptions surface late, often after the penalty clock is already running. Your exception coordinators spend the day routing tickets between dispatch, customer service, and the customs broker.
All five run through the same orchestration layer
The Captain doesn't replace your dispatchers, planners, or exception coordinators. She compresses the time from signal to decision — across all five drains, in the same agent, with the same audit trail, above your existing TMS layer rather than replacing it.
Read · reason · cite · draft. Operator approves.
The Captain reads your live systems via MCP, reasons across them, drafts cited recommendations for each role — and stops at the operator. Every commit happens in your existing tool, with the source records cited and the audit log captured.
Per-persona outcome targets — measured against your baseline.
Design-stage targets, not promised magnitude. The first design-partner pilot is where the delta gets measured against your operator baseline. Below: where The Captain is built to move the needle, by role.
Capacity contracts priced against live lane data
Designed to surface lane-by-lane spot vs. contract variance and equipment-availability patterns before a capacity contract is committed — measured per design-partner against your historical sourcing cycle.
Loads stitched across modes in one queue
Designed to compress per-load planning swivel-chair from minutes-per-load to seconds-per-load — full TMS / dispatch / EDI / carrier-API context already pulled before the planner reviews.
Exception throughput up, on-time pattern visible
Designed to surface the pattern driving on-time drift on a key lane or shipper in days, not weeks — early enough to intervene before the penalty is contractually booked.
Service-level commitments backed by margin-per-lane
Designed to give the executive team a live read on customer service-level commitments and lane-level margin in the same view — so lane economics and customer commitments are made against the same picture.
Escalations answered with the event log, not the phone tree
Designed to redirect a meaningful share of "where is my freight" inbound off the service desk and onto a self-service portal that cites the live carrier event log — and to give the Service Manager an SLA-by-shipper view of where escalations are concentrating.
How OpsATC.AI compares to project44, FourKites, and the category alternatives →
Pre-built MCP connectors for the logistics stack.
OpsATC.AI sits on top of your existing investments — your TMS, dispatch platform, EDI gateway, carrier APIs, and customer ERP feeds. Nothing gets retired. Read-only connectors via Model Context Protocol, with audit trails at the protocol boundary.
Reference adapter implementations are scaffolded for these platforms and validated against synthesized fixtures from public API documentation. Partner-sandbox re-records are pending; production validation happens during the first design-partner pilot. See platform integrations for the full reference-vs-scaffolded breakdown.
TMS & VisibilityMulti-modal tracking, freight visibility
Dispatch & ExecutionLoad planning, driver assignment
EDI & B2BTrading-partner integration · X12 generic adapter
Carrier APIs & MarketplacesSpot capacity, lane pricing, freight matching
Customer ERP feedsTop shippers, direct integration
Customs & ComplianceCross-border, customs holds, trade-compliance
The IT lift is smaller than most carrier ops directors expect.
No data lake. No driver-master extraction. No TMS replatform. The Captain reads your existing TMS, dispatch, EDI gateway, and carrier APIs live via MCP — and adapts on operator feedback, not retraining cycles. See the Day 1 to Day 90 timeline →
What we need
- ✓Read-only TMS access (project44, Oracle TM, SAP TM, or your platform of record)
- ✓Read-only dispatch + load-planning data (Descartes / MercuryGate / Blue Yonder)
- ✓Customer SLA definitions and OTIF/dwell scorecards per top shipper
- ✓Allow-list approval for OpsATC.AI's egress addresses
- ✓One-time field-mapping confirmation per connector
What we don't need
- ✗Your shipper customers' full books of business
- ✗Driver personal data (HR, payroll, PII)
- ✗Your competitive bidding strategy or contract rate cards
- ✗Historical data extraction from your data lake
- ✗Custom adapter work for standard TMS / EDI platforms
Bring your worst dispatch day. We'll walk through how it changes.
Thirty minutes, your live operational pain points — a stuck load, a dwell cascade, an OTIF drop on a top shipper, a customs hold blocking a high-priority lane. We'll walk through how the orchestration layer changes the response, the cycle time, and the cost. Written diagnosis within one business day.