Routite Twin · Live network twin

A live model of the network you actually have

Twin is the state everything else reads: where each vehicle is, what it carries, which orders are open and which roads are closed. It also runs what-if days on the network graph.

What Twin tracks

  1. VehiclesPosition, load, driver hours
  2. OrdersWindows, status, priority
  3. DepotsDocks, stock, cut-offs
  4. RoadsClosures and travel times

Vehicle timeline · Zone 4

Example
Van 1
Van 2
Van 3
Van 4
Van 5
  • Driving and stops
  • Inserted work
  • Forecast late
  • Break
Example Timeline from 07:00 to 17:00. Van 3 stops at 10:40 after a fault. Values are illustrative.

Stop 01 · Capabilities

What Twin does

State

Live fleet and orders

Merges telematics, order systems and traffic into one model, updated as feeds arrive.

Gaps

Missing data flags

Shows vehicles without a fix and orders without a window, before they spoil a plan.

Timelines

Day view per vehicle

Driving, stops, breaks and inserted work on one timeline.

What-if

Scenario days

Replay a day with a closed depot or two fewer vans on the network graph.

History

Replays

Rebuild any past day from the log to see what happened and when.

Visual

3D twins (planned)

Omniverse views of depots and yards are planned after the graph model.

Stop 02 · How it works

How Twin works

  1. streamingest

    Feeds arrive

    Orders, GPS and traffic stream in through connectors and RAPIDS processing.

    Input Feeds
  2. <1 sdesign target

    State updates

    The graph model updates vehicles, orders and road segments.

    Output Live state
  3. on changetrigger

    Hand-off

    Material changes go to Forecasts and Optimize.

    Next Optimize

Stop 03 · Specification

Specification

Draft specification. Figures are design targets, not measured results.
ItemDetailStatus
ModelNetwork graph of roads, depots, vehicles and ordersIn build
Update latencyUnder 1 s from feed to stateDesign target
HistoryFull replay of past daysIn build
Scenario runsGraph simulationIn build
3D visual twinOmniversePlanned

Stop 04 · Place in the loop

Where Twin sits

Twin starts the loop. It is also where the return leg lands: real arrival times from Edge update the models that predict tomorrow.

Return leg Edge sends real arrival and service times back to Twin. ETA and demand models retrain on them, so tomorrow's first plan starts closer to reality.

Stop 05 · Questions

Questions dispatch teams ask

Is this a 3D digital twin?

Not at first. Version one is a network graph, which is what the solver needs. Omniverse visuals for depots and yards are planned later.

How fresh is the state?

As fresh as your feeds. The target is under a second from feed to state.

Can we replay last Tuesday?

Yes, once your history is loaded. Replays are how pilots start.

Stop 06 · Destination

Next step

See Twin on your own data

A replay of one past day shows what this product would have done, with every assumption written down.