Logistics Lab / routing visualization

Replay and inspect
routing solutions.

Inspect routes, requests, and service events over time.

Follow vehicles and other agents as they move, wait, and serve requests.

Study the replay alongside performance measures. See where vehicles wait, when delays occur, and which requests remain unserved.

Example replays

Explore example routing solutions.

Preview an example, or open it in ViaViz.

Why visual inspection?

Examine how a routing solution behaves.

Use the replay to spot vehicles clustering in one area, repeatedly circling between locations, taking unexpected detours, or arriving late.

01

Debug

Trace routes and stops when a solution behaves unexpectedly. Check time windows, service events, loads, and network paths.

02

Validate

Check movement, waiting, and request handling against your operating rules. Inspect dispatch and rebalancing decisions during the replay.

03

Teach and communicate

Walk through a routing solution with students or colleagues. Use the replay and performance measures to discuss what happens and why.

Inspection scope

What you can inspect

Getting started

Inspect a routing solution step by step.

Start with an example, choose an instance from Benchmarks, or load your own compatible route and request data.

  1. 01

    Open an example

    Open an example above, or choose Benchmarks to load an available benchmark instance and solution.

    Try Solomon C101
  2. 02

    Set the playback range

    Set the start and end under Playback range. Use the timeline to move to a specific time, then pause to inspect it.

  3. 03

    Inspect agents and requests

    Select a vehicle or request to inspect its details, including routes, pickup and delivery locations, loads, and timings. Open the fleet, demand, and time-window charts for more context.

  4. 04

    Compare with performance measures

    Check pickup delays, service completion, distance, and utilization alongside the replay. Hover over a measure for its definition.

  5. 05

    Share the view

    Select Share to copy a link to the current view. A portable link saves view settings and requires access to the same data. Deployments with hosted sharing can save a workspace and revoke its link.

Use your own output

Inspect your own routing solution

Load route and request data in ViaViz's documented format. You can export compatible data from your solver or simulation, whether you use Python, Java, Julia, C++, or another language.

The local bridge is a helper that serves selected files from your computer and opens them in the hosted ViaViz workbench. Availability and security depend on your deployment and browser settings.

Example payload aviz-result.v1
{
  "schema_version": "aviz-result.v1",
  "title": "Routing experiment",
  "routes": [
    { "id": "vehicle-01", "path": { "type": "FeatureCollection", "features": [] } }
  ]
}

Include the values your solver produces. Add geometry, demand, timing, and metadata when available.

Background

Developed through research and teaching

Research origin

Origins in mobility research

During Breno's PhD research on mobility-on-demand systems, visual replay helped him examine how routing policies behaved. Vehicles sometimes clustered in areas of high demand or repeatedly moved between attractive regions. Watching the routes helped him investigate patterns that were difficult to explain through aggregate performance measures alone.

Teaching use

Teaching routing algorithms

An earlier version was used in the Transportation and Logistics Management course. Students tested routing algorithms, inspected the resulting routes, and checked whether their solutions behaved as intended.

ViaViz is an early research and teaching prototype.

Logistics Lab

Part of Logistics Lab

Logistics Lab brings together research, tutorials, benchmarks, and software for logistics systems. ViaViz focuses on movement through these systems, including routing, dispatch, and service over time.

Via is Latin for a way, road, or path. Viz is short for visualization.

Research prototype

Open an example and inspect the routes.

Try the prototype and share feedback on its behavior and usability.