Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/fatelessdev/translogiX/llms.txt

Use this file to discover all available pages before exploring further.

The route optimization section of the AI Operations dashboard covers three related capabilities: a live GPS map showing where every tracked vehicle is right now, an AI/ML engine that recommends vehicle and route assignments for unassigned shipments, and a rerouting table that factors in real-time traffic and weather to suggest faster paths for in-progress shipments. All three sections refresh together when you click Refresh.

​
Live GPS tracking

The GPS tracking panel renders a Google Maps instance populated with markers for every shipment that has a known latitude and longitude. Each marker is labeled with the last two characters of the package code, so you can identify shipments at a glance even when markers are close together. Clicking a marker shows a tooltip with the full package code and vehicle number. Below the map, a card grid lists each tracked shipment with:
  • Package code and current status
  • Vehicle number and location name
  • Latitude and longitude (four decimal places)

​
When Google Maps is not configured

The map panel requires the NEXT_PUBLIC_GOOGLE_MAPS_API_KEY environment variable to be set. If the key is absent, the map panel is replaced by a notice: 
Add NEXT_PUBLIC_GOOGLE_MAPS_API_KEY to render the actual Google Map.
GPS data is still coming from tracking updates and will appear here once
the key is configured.
The shipment card grid below the panel still renders with full GPS data in this state — only the visual map is suppressed.
Set NEXT_PUBLIC_GOOGLE_MAPS_API_KEY in your deployment environment and redeploy to enable the map. The integration badge on the overview page will change from outlined to filled once the key is detected.

​
AI/ML route optimization

The optimization panel appears alongside the GPS map and targets shipments in CREATED status that have not yet been assigned a vehicle or route. For each unassigned shipment, the engine produces a single recommendation card showing:
  • Package code — the shipment being evaluated
  • Recommended vehicle — the vehicle number the model suggests
  • Recommended route — the route name the model suggests
  • Confidence percentage — how well the recommendation fits the current fleet and route state (displayed as X% fit)
  • Reasoning — a plain-language explanation of why this vehicle and route were selected

​
Applying a recommendation

1

Review the suggestion

Read the recommended vehicle, route, confidence score, and reasoning for the shipment card.
2

Click Assign

Press the Assign button on the card. The button is disabled if no vehicle ID could be resolved.
3

Confirmation and refresh

A success toast confirms the assignment. The dashboard reloads automatically, and the shipment moves out of the optimization queue.
The Assign action calls POST /api/operations-intelligence/actions with action: "assign", the shipmentId, the resolved vehicleId, and the resolved routeId. This sets the vehicle and route on the shipment record directly.
If no CREATED shipments exist, the panel displays “No unassigned created shipments need optimization.” This is the expected state when all shipments are already in progress.

​
Traffic, road, and weather rerouting

The rerouting table lists every active shipment for which the system has computed an alternative route. The table has five columns:
ColumnDescription
PackageThe package code of the shipment
Recommended RouteThe suggested route name, with the current route shown below it in muted text
ConditionsBadges summarizing the traffic and weather state used to compute the recommendation
ETAPredicted travel time on the recommended route, in hours
ImpactTime savings and reasoning, plus the Apply Route button

​
Condition badges

Each row in the Conditions column carries up to five badges:
  • Traffic level — e.g. Low, Moderate, High
  • Weather condition — e.g. Clear, Rain, Fog
  • Distance — route length in kilometers (e.g. 340 km)
  • Traffic source — Google when data comes from the Google Routes API, or Estimated when computed internally
  • Weather source — Live when data comes from OpenWeather, or Estimated when computed internally

​
Applying a reroute

1

Identify a row with time savings

The Impact column shows Xh saved when the recommended route is faster than the current one. Rows that show Keep route have zero or negative savings — their Apply Route button is disabled.
2

Click Apply Route

Press Apply Route in the Impact column. The button is disabled if no route ID could be resolved or if savedHours is zero or negative.
3

Confirmation and refresh

A success toast confirms the reroute. The dashboard reloads and the shipment’s routeId is updated to the recommended route.
The Apply Route button is intentionally disabled when savedHours <= 0. Applying a route that offers no time benefit would not improve the shipment’s ETA and could confuse downstream tracking.
The Apply Route action calls POST /api/operations-intelligence/actions with action: "reroute", the shipmentId, and the resolved routeId.

Build docs developers (and LLMs) love

Get started for freeTalk to us