If any routes were assigned to unit and events about routes were stored in unit history, a report based on these event can be generated:

  • Beginning: route beginning time (activation time or entrance in the first control point).
  • Initial location: unit location at the beginning of the route.
  • End: route end time (entrance to the last point).
  • Final location: unit location at the end of the route.
  • Route name: route name.
  • Geofence: the name of the geofence which was used for the route.
  • Result: Finished (the route was activated successfully, and later on the entrance to the last point was detected) or Not finished (the lat point was not visited).
  • Skipped points: the number of control point skipped (on this bases more detailed report can be generated - see Route points).
  • Duration: time taken to perform the route.
  • Mileage: distance traveled while performing the route.
  • Avg speed: average speed on the route.
  • Max speed: maximum speed on the route.
  • Count: the number of routes.
  • Driver: driver's name or code if available.
  • Notes: an empty column for your custom comments.

How different route statuses are defined (route beginning, route end, point skipped, point visit, etc.), find here.

In addition in report template you can indicate masks for geofences and routes. It means, you can get in a report not all routes performed by a unit within the indicated period, but only the routes which use a certain geofence or which correspond to the given mask of route name. Both filters can be used simultaneously or separately from each other.

Besides, these filters affect the data layout in the table if the grouping by days/weeks/month is used. For instance, if the data is grouped by days and the filter by geofence is on, the table is built on the basis of geofences:

If the data is grouped by days and the filter by routes is on, the table is built on the basis of routes:

If both filters are activated, the sorting is made on the basis of both.

Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, stops, parkings, sensors, driver, fuel thefts, fillings, and geofences/units.

Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon   |   Copyright © 2002-2019 Gurtam