Comoving Systems
← AI-powered applications

Supply chain · Synthetic dispatch example

Is the bypass worth the toll?

The dispatch board

One truck leaves at 7:30.

The driver can take the bridge or pay $12 to use the bypass, then visit two receivers in either order. East has a firm appointment. West’s booking email says, “If you arrive after 8:30, we charge $80.”

East dock
The truck must arrive by 8:20 in either traffic scenario.
West dock
An arrival after 8:30 incurs an $80 late fee.
Truck time
$1 per minute until the second unload is complete. Each unload takes 10 minutes.

Comoving would connect the booking inbox to the dispatcher’s route planner. An AI agent matches West’s email to the booking and shows the fee, the cutoff and the sentence they came from. If the terms conflict with the booking, it flags the discrepancy. The dispatcher confirms which terms the planner should use. A booking that already supplies those fields goes straight to the planner.

A nearest-neighbour forecast would select the ten past mornings whose approach speeds at departure most closely match today’s. The example gives the summary count alone. Three heavy-traffic mornings out of ten give that scenario a 30% weight. The planner checks all four plans against East’s deadline and ranks the feasible plans by expected cost.

Dispatch recommendation

Take the bypass. Deliver to East first.

With East first, the bridge is 1.5 minutes faster on average. In heavy traffic it puts the truck at West at 8:46. The bypass reaches West at 8:30, exactly at the cutoff. At today’s forecast, paying the toll saves $10.50 in expected cost. The dispatcher chooses the route.

Expected time and cost with East first
RouteMean timeMean cost (CAD)
Bridge60.8 min$84.80
Bypass62.3 min$74.30
Trace the four possible plans
Driving minutes for each leg
LegOrdinaryHeavy
Bridge to East1848
Bridge to West1432
Bypass to East2732
Bypass to West2027
Between docks, either way1218

Use one traffic column for the whole trip. Visiting West first puts the truck at East at 8:30 via the bridge or 8:25 via the bypass in heavy traffic. Both miss East’s deadline.

With East first, the bridge costs $50 in ordinary traffic and $166 in heavy traffic, including the late fee. The bypass costs $71 and $82, including the toll. Weight each pair 70% and 30% to recover the table above.

When does the decision change?

At a 20% chance of heavy traffic, both plans cost $73.20 on average. Below that point the bridge costs less. One fewer congested morning in the ten would put today’s estimate exactly at the tie. The unloading time matters, too. In heavy traffic, one extra minute at East would cost the bypass its on-time arrival at West.

Test the forecast on later mornings using only information available at departure. Independent travel-time observations can help evaluate the route the truck did not take. Compare manual entry with agent-assisted review on the same new bookings. Keep the forecast and planner fixed. Time each booking through verification. Check each fee and cutoff against the confirmed booking terms, and count all missing or incorrect entries. Report how many bookings contained an error and how often an error changed the expected cost or the recommended route.

Bertsimas and Kallus (2020), From Predictive to Prescriptive Analytics, describe how to use observations to inform decisions under uncertainty. The travel times and charges here are illustrative.

How would the app plan for a fleet?

The worked run isolates one decision. Across a fleet, an updated traffic forecast would prompt the app to reassign uncollected loads and reorder the stops still open to change. Loads already aboard would stay on their trucks. Confirmed appointments and committed trips would stay fixed.

Each plan would have to fit the payload of every truck and the number of unloading bays available at each dock and time. The solver would minimize the fleet’s expected total cost of truck time, tolls and late fees. A dispatcher would see the proposed changes and approve them before drivers receive new instructions.

Discuss a dispatch workflow