The Platform

One AI dispatch engine for both missions

Gallatin's route intelligence layer connects to your existing data sources, runs continuous optimization across your fleet, and switches to crisis escalation mode the moment conditions change, without a separate system for each use case.

<90 sec route recalculation time
14+ ERP and TMS connectors
2 modes standard and crisis escalation
Gallatin platform routing interface showing real-time route optimization and dispatch dashboard

How the dispatch engine decides

The engine evaluates every active route against live traffic, road closure feeds, inventory state, and delivery priority tiers every 90 seconds. The result is a continuously updated dispatch plan, not a static route that degrades throughout the day.

Route ID Mode Priority ETA Confidence Action
RT-4821 Standard P2 94% On Track
RT-5034 Standard P1 71% Rerouting
RT-5102 Crisis P0 96% Locked
RT-5209 Crisis P0 43% Needs Review
RT-5318 Standard P3 88% On Track

Continuous re-evaluation

Routes are re-scored every 90 seconds against live data, not only when you manually flag a problem.

Priority tier logic

P0 through P3 tiers let the engine protect your most critical deliveries when resources are constrained.

Crisis escalation mode

A single switch activates humanitarian protocols: shared inventory pools, relaxed time windows, and manual override priority.

Confidence scoring

Every route carries a live ETA confidence score. Routes below 60% surface automatically for dispatcher review.

Connects to the systems you already run

Gallatin does not replace your ERP or TMS. It adds an intelligent dispatch layer on top, pulling live data from your existing stack and pushing updated route plans back through the same APIs.

Transportation Management

  • SAP TM
  • Oracle TMS
  • MercuryGate
  • Descartes

ERP and Inventory

  • SAP S/4HANA
  • Oracle NetSuite
  • Microsoft Dynamics
  • Infor WMS

Traffic and Mapping

  • HERE Maps
  • TomTom Traffic
  • Mapbox
  • OpenStreetMap feeds

Aid Coordination

  • UN OCHA ReliefWeb feed
  • Humanitarian Data Exchange
  • Kobo Toolbox forms
  • Custom webhook API

REST API sample

POST /v1/dispatch/optimize
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "fleet_id": "fleet_chi_01",
  "mode": "standard",
  "routes": [...],
  "constraints": {
    "max_reroute_delta_km": 25,
    "protect_p0": true
  }
}

Live inside your operation in days, not quarters

Gallatin connects to your data sources via API or flat-file export. Most customers complete onboarding and receive their first optimized dispatch plan within five business days of starting the integration process.

01

Connect your data

Your implementation engineer maps your ERP, TMS, and traffic data feeds to Gallatin's ingestion API. Typical mapping takes 1 to 2 business days.

02

Calibrate priority rules

Your operations lead configures priority tiers, delivery time windows, and fleet constraints through the Gallatin configuration UI. No code required.

03

Shadow mode validation

Gallatin runs in shadow mode alongside your existing process for 48 hours, generating parallel route plans your team can compare before going live.

04

Go live

Flip the dispatch switch. Gallatin begins issuing real route plans and your dispatchers manage exceptions from the central console.

Security and data residency requirements are handled at the enterprise tier. All data in transit is encrypted with TLS 1.3. Route and fleet data is never used to train shared models.

See the engine running on your routes.

Bring a sample of your actual route data to the demo call. We will run it through the optimizer live.