All projects03 / 05Freight and delivery
The dispatcher sees
deviations before the client notices them
Needs a decisionOnly deviations are at the top, sorted by urgency; trips that are on plan are collapsed into one row.
Context
A dispatcher runs dozens of trips at once: trucks, loads, warehouses, drivers, delivery windows and new requests. Trip data already exists in the system of record and with the drivers, but it sits in different places.
Constraint
The system showed all the data but did not say which decision had to be made now.
A deviation was often noticed when the client called, and the decision was made without calculating the consequences for neighboring trips.
How it was
To make one decision, the dispatcher went through five sources. Trips that were on plan took as much attention as the problem ones.
Hypothesis
If trips that are on plan move to the background and only deviations with ready decision options rise to the top, the dispatcher reacts before the client learns about the delay.
Operation model
The system calculates the impact on timing and assembles the options; the decision stays with the dispatcher. The map becomes a supporting layer, not the main screen.
Interface
Dispatcher workspace
Only deviations are at the top, sorted by urgency; trips that are on plan are collapsed into one row.
- 1Deviations by urgency
- 2Who the deviation affects
- 3On-plan trips are collapsed
- 4The map is a supporting layer
For every stop on the route, the expected arrival is shown against the delivery window, along with who a delay would affect.
- 1Delivery window and expected arrival by stop
- 2Who a delay would affect
The stops, windows, truck load and driver are gathered where the decision is made.
- 1Route and stops
- 2Truck load
- 3Contact with the driver
The dispatcher compares the options by their consequences and chooses one; notifications go out after the decision.
- 1Consequences of each option
- 2The dispatcher makes the decision
- 3The driver and the client are notified
Project gallery: screens and close-ups
A click opens the screen full size.
Specification for the technical team
The product side: entities, roles, events and data sources.
- Entities
- Trips, route stops, delivery windows, trucks and their load, drivers, requests.
- Events
- A delay, idle time, a deviation from the route, a new request. Each event gets an estimate of its impact on recipients' windows.
- Decision
- Options are assembled with their consequences for neighboring trips; the choice stays with the dispatcher.
- Notifications
- To the driver and the recipient after the dispatcher's decision.
- Data sources
- System of record, client requests, drivers.
What changed in how the operation runs
The changes are described qualitatively. Figures are published once the client approves them.
- 01Order of attentionThe dispatcher's day starts with deviations, not with the map.
- 02Decision with consequencesBefore choosing, the dispatcher sees how an option will affect neighboring trips and clients.
- 03Client communicationThe notification to the recipient goes out right after the dispatcher's decision.
Metrics
- Deliveries within the windowtracked
- Time from deviation to decisiontracked
- Share of recipients notified in advancetracked