Command disabled: backlink

Trips

In this kind of report all intervals of movement (together with location, time and speed information) are shown. Trips are estimated according to parameters set in Trip Detection. To get information as accurate as possible, it is advised that you configure each parameter individually for every unit.

The following columns can be included in this kind of report:

  • Beginning: date and time when the trip began.
  • Initial location: the address where the device was at the beginning of the trip.
  • End: date and time when the trip ended.
  • Final location: the address where the device was at the end of the trip.
  • Driver: driver's name (if a driver was identified).
  • Duration: time interval of the trip.
  • Total time: time from the first trip beginning to the last trip end (useful if groupping by days is enabled).
  • Off-time: period of time passed from the end of the previous trip to the beginning of the current one.
  • Engine hours: time of engine hours operation during the trip (you can specify engine hours sensor entering name mask for it in the report template).
  • Mileage: the distance traveled in the whole trip.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Urban mileage: the distance traveled in urban area.
  • Suburban mileage: the distance traveled in suburban area. It is calculated in regard to speed. The urban/suburban speed line is indicated in Unit Properties => Advanced (Urban speed limit setting).
  • Initial mileage: mileage counter at the beginning of the trip.
  • Final mileage: mileage counter at the end of the trip.
  • Avg speed: average speed within the trip.
  • Max speed: maximum speed registered within this interval.
  • Trips count: the number of trips made.
  • Counter: counter sensor value.
  • Initial counter: counter value at the beginning of the trip.
  • Finale counter: counter value at the end of the trip.
  • Status: unit status registered during the current trip (if there are several, the first one is displayed).
  • Messages count: the number of messages that formed the trip.

Depending on hardware and software configuration information about fuel can be also included:

  • Consumed by ImpFCS/AbsFCS/InsFCS/FLS/math/rates: the volume of consumed fuel detected by a fuel sensor (like impulse/absolute/instant fuel consumption sensor, fuel level sensor) or calculated by math or rates.
  • Rates deviation by ImpFCS/AbsFCS/InsFCS/FLS: difference between consumed fuel detected by a sensor and consumption rates. If a number in this cell is negative, it means detected consumption does not exceed the indicated rates.
  • Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math/rates: average fuel consumption in the trip detected by one of the methods mentioned above.
  • Avg consumption in idle run by …: average fuel consumption in the trip during idle run.
  • Avg consumption by … (mileage/1l): average fuel consumption in the trip detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the trip.
  • Final fuel level: fuel level at the end of the trip.
  • Max fuel level: maximum fuel level in the trip.
  • Min fuel level: minimum fuel level in the trip.
  • Notes: an empty column for your custom comments.

Details about fuel in reports...

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

:!: Tip:
The tracks of the trips can be displayed on the map. To make use of this feature, select Trips routes on map in report template.

Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2020 Gurtam