Skip to content
← Back to uRoutes software

Transportation Management System

uRoutes TMS — how each program works

RouterEngine, MobilityApp, and Deliveries Portal (read-only tower: map, authorized, liquidated, POF, exports). Plan, execution, proof, and ops visibility on one thread.

Below each card you’ll find the module’s Synthesia player (matches site language).

TMS · TransportTMS
TMS · System|webOptimizador

Routing engine

TMS-uRoutes-RouterEngine

Watch video

Routing engine — spreadsheet import, CVRPTW optimization (OR-Tools), interactive map, manual edits with Google Maps and Firestore authorization; once authorized, the itinerary goes to Mobility.

CVRPTW / OR-Tools optimizationInteractive map and plan KPIsAuthorization handoff to mobile execution

Operational Workflow

Inputs
  • Orders and destinations (import or capture)
  • Fleet and constraints (capacity, windows, pickup/delivery)
  • Cost parameters (fuel, tolls, service times)
Processing Engine

Route optimization engine

The solver assigns stops to vehicles and sequencing under constraints; the planner validates on the map, edits and authorizes the plan.

Outputs
  • Routes and stop order per unit
  • Estimated operational cost of the plan
  • Authorized plan ready for Mobility / tower

Key Benefits for Your Operation

Fewer kilometers and better fleet utilization for the same volume.

Explicit compliance with windows and business rules — less same-day spreadsheet routing.

A defensible plan: same policies, same solver; foundation for plan vs actual in dashboards.

Routing engine

TMS · TransportTMS
TMS · System|appEntregas

Mobility — deliveries

TMS-uRoutes-MobilityApp

Watch video

Mobility — deliveries — Android app for drivers and last mile: itinerary, proof (photos, signature), incidents, settlement, Firestore/Storage sync and offline-first work.

Offline-first modePOD and stop evidenceSOS and route events

Operational Workflow

Inputs
  • Authorized itinerary or trip
  • Driver actions at each stop
  • GPS signal and incident events
Processing Engine

Execution and capture on the road

The driver executes the trip; evidence and status sync to the cloud; tower and customer align with field reality.

Outputs
  • Digital dossier per stop
  • Trip states for core and TMS
  • Data package for settlement and audit

Key Benefits for Your Operation

Digital POD and less paperwork.

Faster trip close and lower dispute risk.

Visibility for control tower and settlement without retyping paper.

Mobility — deliveries

TMS · TransportTMS
TMS · System|silo_web_dashEntregas

Deliveries portal

TMS-uRoutes-Delivery

Watch video

Deliveries portal — web console (FastAPI + Firestore): order status, live fleet, settled history and analytics. Read-only; does not replace field capture (that is Mobility).

Live map and alarmsAuthorized vs liquidated layersPOF, plan vs actual, analytics, export

Operational Workflow

Inputs
  • Mobility event stream and plan references
  • Session and filters per tenant / DC
  • POF rules and thresholds
Processing Engine

Read-only aggregation

Authorized users browse a safe read layer without mutating critical collections from this surface.

Outputs
  • Unified operational dashboards
  • KPIs and incidents in archive
  • Exports for finance and quality

Key Benefits for Your Operation

24/7 visibility for dispatch and supervision.

Fewer manual reports and a common baseline to audit service.

Continuous improvement with plan vs actual and POF — facts, not opinions.

Deliveries portal

Videos · Silodisa

Clear videos about how we operate

Introduction, uRoutes app-by-app catalog, WMS, TMS, CRM, receiving, dispatch, and platform. Click to watch full screen.

View full library