Real-time route optimization

Routes that re-plan the moment the day changes.

Morning plans go stale by eleven. Routite keeps a live model of your vehicles, orders and depots, and re-solves the whole network on GPUs when a van breaks down, orders land late or a road closes.

Try the example dispatch board below

Dispatch board · Zone 4

Example
  • Route
  • Stop on time
  • Stop forecast late
  • Inserted order
  • Depot
  • Closed road

Example A toy city of 42 stops solved in your browser with a simple heuristic, so you can see what a re-plan looks like. It is not Routite's GPU solver; every number on this board is illustrative.

Next stops for Van 2

    Dispatch log

      Clock 10:40

      5 of 5Vans running
      42Stops today
      0 kmPlanned distance
      0Stops forecast late
      0 msLast re-solve, in this browser

      Throw a disruption

      Stop 01 · Targets

      What we are building Routite to do

      Routite is pre-launch. These are targets and assumptions we will measure in pilots, not results.

      Design target<10s

      To re-solve a regional fleet of about 1,000 stops after a disruption, warm-started on one GPU.

      Design target15min

      Default re-solve cadence when nothing has gone wrong, so ETAs stay honest.

      Planning assumption1approval

      Every executed change waits for a dispatcher unless you set a rule that it may go through.

      Pilot measurekmper stop

      The first number a pilot reports: distance per delivered stop against your own plan.

      Stop 02 · Problem

      Overnight plans meet a daytime world

      Most fleets plan once, overnight, on CPUs. Routes, dispatch and slotting come out of a batch job and are fixed before the first van leaves the depot.

      Then the day starts. Traffic builds, a customer adds forty cases, a van will not start, a bridge closes. By mid-morning the plan is wrong, and re-solving a vehicle routing problem of that size on a CPU takes too long to help.

      So dispatchers patch the plan by phone and spreadsheet, and the waste shows up as empty kilometres, missed delivery windows, overtime and idle vehicles.

      Today

      Batch planning

      One solve before the shift. Changes after that are manual.

      Today

      Manual patching

      A dispatcher moves stops by hand and hopes the van after it still makes its windows.

      With Routite

      Continuous re-planning

      Each change to the live model triggers a re-solve of the affected routes, with a reason attached.

      With Routite

      Approved, then executed

      The dispatcher sees what moves and why, approves, and drivers get the new stop list.

      Stop 03 · The loop

      Six products, one live plan

      Twin senses, Optimize re-solves, Copilot explains, Edge executes. Warehouse and API use the same engine.

      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 04 · How it works

      From a closed road to a new stop list

      1. 0 sevent

        Something changes

        A telematics feed reports a breakdown, an order arrives, or a traffic service closes a road. Twin updates the live model.

        Who TwinInput GPS, orders, traffic
      2. 1 sdetect

        Disruption is measured

        Forecast services estimate which stops will now miss their windows and by how much. Small slips wait for the next cadence; big ones trigger a re-solve now.

        Who ForecastsOutput Late-risk per stop
      3. <10 sdesign target

        The network is re-solved

        Optimize warm-starts NVIDIA cuOpt from the current plan and re-solves routing and dispatch with every constraint you have encoded.

        Who OptimizeRuns on GPU
      4. ~1 minhuman

        A dispatcher approves

        Copilot shows what moved and why: “Van 3 down, 11 stops moved to vans 1 and 4, two windows widened by 10 minutes.” Approve, edit or reject.

        Who DispatcherTool Copilot
      5. next stopdriver

        Drivers get the change

        Edge pushes the new stop order to driver apps and logs real arrival times for the return leg.

        Who EdgeOutput Stop list, ETAs

      Stop 05 · Who it's for

      Built for operators who run many vehicles

      Distribution

      Distribution and 3PL

      Multi-drop trucks, dock schedules, several clients sharing a network.

      Stop 06 · Stack

      What runs underneath

      SolverNVIDIA cuOptGPU vehicle routing, dispatch and assignment with rich constraints.
      DataRAPIDS cuDFGPU processing of order, route and telemetry tables each cycle.
      ForecastsTriton and TensorRTETA, service-time and demand models served inside the loop.
      CopilotNeMo with guardrailsPlain-language questions, what-ifs and guarded execution.
      TwinNetwork graphA graph simulation first; Omniverse visual twins are planned.
      DeployCloud or NIMRoutite cloud, your VPC, or on-premises with NVIDIA AI Enterprise.
      ExecutionDriver apps and JetsonStop lists to phones today; robot and AMR dispatch is planned.
      AuditChange logEvery executed change with who approved it and why.

      Stop 07 · Developers

      Ask for a re-solve in one call

      Everything the console does goes through the same API. Send the change, get back the new routes, the diff against the current plan and the reasons.

      The API is in design. The request below shows the shape we are building toward; see Routite API for the draft.

      POST /v1/plans/{plan_id}/resolve · draft
      curl -X POST https://api.routite.com/v1/plans/pl_zone4/resolve \
        -H "Authorization: Bearer $ROUTITE_KEY" \
        -d '{
          "event": { "type": "vehicle_down", "vehicle": "van-3" },
          "keep": ["time_windows", "driver_hours"],
          "approve": "dispatcher"
        }'
      # returns: new routes, moved stops, reasons

      Stop 08 · Questions

      Questions dispatch teams ask

      Is Routite available today?

      No. Routite is pre-launch. We are looking for design partners to replay their own historical days through the solver before anything touches live dispatch.

      Do we have to replace our TMS?

      No. Routite sits beside your TMS or WMS: it reads orders and constraints from it and writes approved routes back.

      Why GPUs?

      Vehicle routing is NP-hard. NVIDIA cuOpt runs many candidate improvements in parallel on a GPU, which is what makes re-solving a whole region during the day practical rather than overnight.

      Will it move stops without asking?

      Not unless you say so. By default every executed change waits for a dispatcher. You can allow narrow rules, such as swaps inside one van's route.

      What does a replay need from us?

      One or more past days of orders, vehicles, depots and what actually happened. See the pilot page for the full list.

      Stop 09 · Destination

      Next step

      Send us a day you would rather forget

      We replay one of your past days through Routite: the plan you had, the disruptions that hit it, and what a live re-plan would have done. You keep the report.