Logistics case: heatmap and mileage

To optimize routes and coverage, combine the map heat layer with distance reports: heat shows where historical activity clustered; reports quantify travel over a time window.

Use both to rebalance bases, adjust shifts, or validate SLAs with stakeholders.

In logistics operations, the recurring question is: am I spending resources where they really matter? Sentinel offers two complementary tools to answer with data: the heatmap layer of the tactical map, showing where fleet activity historically clustered, and distance reports, quantifying kilometers per unit in a time window.

The heatmap is a layer that turns on over the main map and colors zones by past GPS activity density. Red and yellow zones are where the fleet passed many times; green or blue zones are low-presence areas. That visualization alone reveals patterns hard to see in real time: underused corridors, unplanned hot spots, customer zones with insufficient coverage.

Distance reports give concrete numbers: kilometers per unit in the last week, month, or quarter. That quantification helps validate SLAs with customers ('we guarantee X km daily coverage in zone Y'), reconcile fuel and maintenance, and assess whether the current unit-to-base assignment is optimal. A team consistently driving 800 km daily probably needs relief or reassignment.

Combining both views is what gives actionable insight: if the heatmap shows a zone with much activity but the report shows few kilometers, there may be a team going in circles instead of covering ground. If a base generates many kilometers but little presence in strategic zones, review shift planning. These data-driven decisions, instead of intuition, are the kind of continuous improvement that differentiates mature operations.