Data in Reports

Time in Reports

Time when an event happened/begun/finished is given in reports in the form of date and time: YYYY:MM:DD HH:MM:SS.

The duration of a state is given in the format HH:MM:SS. If a duration is bigger than a day, first the number of days is indicated, and then HH:MM:SS. It can look like that: '5 days 12:34:56' which means '5 days, 12 hours, 34 minutes, 56 seconds'.

In some rare cases the duration of a state is '0 seconds'. It can happen if the state is detected by only one message. For example, a speeding was detected in one message, and in previous and next messages there is no speeding. The duration of a speeding is considered a period of time from the first message with speeding to the last messages with speeding in sequence. So, if having only one message with speeding, the duration turns to be zero.

If grouping is used, the time appears as follows:

  • If grouping by days is used, the column called 'Date' is added. It gives the date in the format YYYY:MM:DD. If the columns 'Beginning' and 'End' are selected, they will contain only time (HH:MM:SS). However, if a state began in one day and finished in another, in the 'End' column date and time will be given.
  • If grouping by weeks is used, the column called 'Week' is added. The month and the number of week of year are indicated there. The first week of year is considered the first full week. If a week begins in one month and ends in another, it refers to the month where it begins.
  • If grouping by months is used, the column called 'Month' is added.

:!: Attention!
To receive reliable data for time/duration, it is important to correctly indicate the time zone, the first option in User Settings.

Speed and Mileage

Mileage can appear in reports on trips, geofences, rides, speedings, digital sensors as well as in statistics and processed fuel level chart.

Mileage is calculated according to settings of mileage counter on the General tab in unit properties. Besides, mileage in trips, geofences and rides depends also on Trip Detector because the intervals of movement and stays are detected by it.

In Statistics you can find two possibilities for mileage:

  • Mileage in all messages – the full mileage without any filtration by trip detector. It is always the longest mileage because it includes also all adjustment of data.
  • Mileage in trips – total mileage of all movement intervals found according to trip detector.

Average and maximum speed values can be included in the same reports as mileage: trips, geofences, rides, speedings, digital sensors. Note that the average speed directly depends on mileage because it is calculated by dividing mileage by duration (for example, distance travelled with a sensor on divided by duration of on state. That is why a situation can happen when the average speed is zero and maximum speed is a positive number. It can happen (1) if state duration is zero (see explanation above); (2) if mileage is zero (unit was parked or the mileage counter is set incorrectly); (3) if the mileage is insignificant, for example, '0,01', and the result of division is smaller than one.

Maximum speed has nothing to do with mileage and any counters. To calculate maximum speed within an interval, all messages which get to this interval are analyzed and the largest speed value is selected and displayed in the corresponding cell.

Speed is given only in integer numbers. Mileage if less than 20 (miles pr kilometers) is displayed with accuracy to hundredths (other decimal places are simply cut). Measurement units for speed and mileage (kilometers and kilometers per hour or miles and miles per hour) are selected in additional settings of report template. There you can also set the option Mileage and fuel with accuracy to two decimal places to see mileage always with hundredths.

Fuel in Reports

Many reports can provide information about fuel: fuel level (initial/final), the volume of filled/stolen/registered/consumed fuel, average consumption, etc.

Abbreviations used:

  • FLS – fuel level sensor;
  • ImpFCS – impulse fuel consumption sensor;
  • AbsFCS – absolute fuel consumption sensor;
  • InsFCS – instant fuel consumption sensor.

To receive the most accurate information about fuel, you need to:

However, even if you do not have special fuel sensors, you can control fuel in the following ways:

  • register fillings manually in the Monitoring panel;
  • use mathematical method to calculate fuel consumed (it takes into account urban and suburban cycle, idle running, and moving under load);
  • use consumption rates to calculate fuel consumed (it takes into account consumption rates in winter and summer periods);
  • use mathematical method and consumption rates to calculate average fuel consumption within a given interval of movement.

To calculate fuel consumption by rates or math, you do not need any sensors to be installed. To use these method, it is enough to enter necessary values in the Fuel Consumption tab of unit properties dialog.

In report template several methods of calculating fuel can be selected simultaneously. In this case a separate column will be generated for each method. Above all, if there are several sensors of the same type (or corresponding to the given mask) and they are not summed (the option 'Merge same name sensors' is off), then a separate column will be generated for each of these sensors. If you want a certain sensor to be used for fuel calculations, enter its name mask in the reports templates in the filter called “Sensor masks”. If in the report template you select columns which do not match with unit configuration, in the resulting report there will zeros in those cells.

In statistics, there is no possibility to show a separate row for each sensor. Even if they are not merged, in the rows like 'Avg consumption …', 'Consumed by …', 'Rates deviation …' etc. you can get only one row for each type of fuel sensor (FLS/ImpFCS/AbsFCS/InsFCS). That is why consumed fuel ('Consumed by …') in statistics is the sum of sensors of a type, and average consumption ('Avg consumption …') is the arithmetic mean between those sensors. However, calculation of deviation from rates ('Rates deviation …') depends on sensors adjustments. If a unit has two sensors of the same type with different names (or with the same name and the merging of sensors is disabled), rates deviation is calculated for each sensor separately but for the statistics (as it can be only one row) the sum of those deviations is shown. Thus, the formula is:

  • Rates deviation = (Consumed by FLS1 – Consumed by rates) + (Consumed by FLS2 – Consumed by rates)

If there are two fuel sensors with the same names and the merging is enabled, the formula is:

  • Rates deviation = (Consumed by FLS1 + Consumed by FLS2) – Consumed by rates.

Fuel level is given in integer numbers. The volume of fuel consumed/registered/stolen as well as average consumption are given correct to the nearest hundredth (other decimal places are simply cut). However, if the value is over 50 (liters/gallons), it is shown as integer. However, if you consider it is necessary, you can see fuel always with accuracy to hundredths. For this, check the option Mileage and fuel with accuracy to two decimal places in report template.

If US metrics are selected, fuel is measured in gallons, and average consumption in mpg (miles per gallon) unlike the European system where average consumption is measures as lt/100km (liters per 100 kilometers).

All fuel data is processed before getting to reports. The data is processed according to filtration level set on the Fuel Consumption tab (the option Filter fuel level sensors values).


Address information can be displayed in many reports: initial/final location in trip, place of fuel filling or theft, location where the unit parked or had speeding, location where connection was lost, message received, event registered, etc.

Two things are crucial in defining an address:

  • coordinates sent by device;
  • WebGIS server.

Address is searched in the radius of 1 km from the point where a message was received. If in this radius there is no available address information, then coordinates are displayed.

Sometimes WebGIS may not contain addresses for some regions. In these cases you can use geofences and places (POI) created in the appropriate panels as addresses. Besides, you can make use of this feature to customize some addresses, make them more clear.

To use a geofence instead of usual WebGIS address, this geofence must have the flag Address source, and the option Geofences as address source must be activated in advanced options of report template. If coordinates of unit location get into the geofence, its name will be used in address cell. If two different geofences overlay, the smallest is used.

To use places instead of usual addresses, it is enough to have the option POI as address source checked in report template. If coordinates of unit location get into the radius of 100 meters from this POI (or other radius indicated in unit properties), the address will be takes from its name. If unit location gets into the radius of two or more places, the nearest is used. If both options (geofences and POI as addresses) are activated, the priority is given to places.

By default, geofences and places used in reports as addresses are taken from the account to which report template belongs. However, if the option Use all accounts is activated in report template and user has access to several accounts, all geofences and places which are located in these account will be enabled for the report.

Was this helpful?
Thank you!