Use Cases

Re-planning routes from what drivers actually report

Driver messages about accidents, closures and delays become routing constraints the planner can act on — not calls a dispatcher has to decode

A line of white semi-trucks driving along a highway at sunset

USE CASE / FLEET ROUTING

Published product metrics

Objective vs rule-based pipeline (Solomon R101)

+3.7%

Real-log phrasings a rule-based parser missed

82%

Semantic inference time, any network size

~2 ms

These figures match the published metrics on the Predictim GenOR-Twin product page — this walkthrough is a composite scenario, not a specific engagement.

The challenge

Driver messages about accidents, closures and delays become routing constraints the planner can act on — not calls a dispatcher has to decode

Segment: Delivery and freight fleets

Rule-based parsing handles the phrasings someone thought of in advance and misses the rest; in the published evaluation, a rule-based extractor failed on 82% of the varied phrasing found in real logs. The result is a dispatcher reading messages, guessing which routes are affected and adjusting by hand, while time windows at downstream stops quietly slip.

The approach

How the deployment was structured

From message to edge update

The driver's message is translated into a constraint on the network model — this road segment, this extra delay — rather than a free-text note someone has to interpret later.

Checked against the network

Before it counts, the constraint is validated: the segment exists in the routing network, the delay starts now rather than in the past, and the duration is within realistic bounds.

Re-sequence, re-plan, or ask

If only the affected stops need re-sequencing, that's a local repair. If the delay breaks time windows across several routes, the routing model re-optimizes. If the message is too vague to act on, the dispatcher confirms one reading.

What changed

Vehicle routing is one of the six problem types GenOR-Twin was validated on. On the Solomon R101 benchmark it produced a 3.7% better objective than a rule-based extraction pipeline, and the language-model step took about 2 milliseconds regardless of problem size — so the speed of a re-plan is set by the routing solver, not by reading the message.

Product used