An event's occurring/beginning/finishing time is given in reports in the format indicated in 'Advanced settings' section of a report template.

In the tables that include the duration of a state the hours may not be combined into days (if the interval is longer than 24 hours). It means that instead of '5 days 12:34:56' there will be '132:​34:​56'. To disable days and leave only hours, choose the duration format 'hours:minutes:seconds' in the table properties of the report template. This option does not only affect the formatting in the cells, but also the row 'Total'. Moreover, the duration may be shown in in the format of 'hours (with two decimal places). For example, '3.45'​ instead of '​3:​27'​. This is done by means of activating the option 'hours (with two decimal places)'.

If grouping is used, then a table receives additional column 'Grouping' displaying time in the following way:

• Grouping by years shows corresponding years (for example, 2015);
  
• Grouping by months shows months' names (for example, August);
  
• Grouping by weeks shows a number of a week in a year (for example, week 10; note that the first week is considered to be the first full week in a year.)
  
• Grouping by day of the week shows the corresponding day (for example, Friday);
  
• Grouping by day of the month shows the corresponding day (from day 1 to day 31);
  
• Grouping by dates shows the corresponding date in the format chosen in the advanced settings of a report template;
  
• Grouping by shifts shows the corresponding shifts (for example, shift 1).
  

Attention!

Mileage can appear in reports on trips, geofences, rides, speedings, digital sensors, etc., 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 can depend also on Trip Detector because the intervals of movement and parkings are detected by it.

Mileage can be ordinary or adjusted. The adjusted mileage may be useful to coordinate mileage detected by the program and mileage detected by vehicle itself. Correction coefficient is set in unit properties on the 'Advanced' tab.

In Statistics and in various tables, you can find many 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.
  
• Mileage (adjusted): mileage in trips multiplied by correction coefficient.
  
• Mileage in engine hours: mileage in intervals of engine hours.
  
• Urban mileage: distance traveled at speed which is considered as speed in populated areas.
  
• Suburban mileage: distance traveled at speed which is considered as speed outside populated areas. 'Urban speed limit' is a setting in unit properties which defines if unit is moving in urban area or outside it.
  
• Initial mileage: mileage sensor value at the beginning of the interval (trip, street visit, sensor operation, etc.).
  
• Final mileage: mileage sensor value at the end of the interval.
  
• Mileage counter: absolute mileage (mileage counter value at the moment of report generation).
  

In many tabular reports, mileage can be displayed. It can be calculated either by all messages or by messages in trips. Choice of the method of calculation is defined by the flag 'Mileage from trips only' in additional settings of the 'Report Template' dialog.

Mileage if less than 20 (miles or 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 the 'Report Template dialog'. There you can also set the option 'Mileage/fuel/counters with accuracy to two decimal places' to see mileage always with hundredths.

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 traveled 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. Note also that mileage can be calculated either by all messages or by trips only (option in template's advanced settings), and this will obviously affect resulting values of average speed.

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.

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

In most cases to receive information about fuel you need the unit to have corresponding sensors installed. They should be configured on the tab 'Sensors' of 'Unit properties' dialog and the corresponding calculation methods should be chosen on the 'Fuel Consumption' tab.

Abbreviations used:

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

Without special fuel sensors, you can control fuel in the following ways:

• register fillings manually in the 'Monitoring' panel;
  
• use the mathematical calculation of fuel consumption that is based on the consumption rates from ignition, relative o absolute engine hours sensors multiplied by the values of engine efficiency sensors (if any). The latter can be used for taking into account the load, the movement in urban and suburban cycles and the work during different seasons.
  

The consumption by math does not require fuel sensors. The consumption rates and coefficients indicated in the properties of the ignition and engine efficiency sensors will be multiplied by time.

In a report template several methods of calculating fuel can be selected simultaneously. In this case a separate column will be generated for each method. Moreover, if there are several sensors of the same type, then a separate column will be generated for each. If you want a certain sensor to be used for fuel calculation, enter its name mask in the filter 'Sensor masks' of the parameters of the table. If in the report template you select columns that do not correspond to unit's properties, in the resulting report there will be zeros in those cells.

In statistics, there is no possibility to show information for each sensor separately. In the rows like 'Avg consumption …', 'Consumed by …', 'Rates deviation …' etc. you can get only one value for each type of fuel sensor (FLS/ImpFCS/AbsFCS/InsFCS). That is why consumed fuel ('Consumed by …') in statistics is the sum of the sensors of this type, and average consumption ('Avg consumption …') is the arithmetic mean of those sensors. However, the calculation of deviation from rates ('Rates deviation …') depends on sensors' adjustments. If a unit has two sensors of the same type, the deviation from rates 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)
  

Fuel consumption detected by FLS as well as average consumption according to FLS can be calculated including fuel thefts or excluding them. This is adjusted in advanced settings of a report template — the checkbox 'Exclude thefts from fuel consumption'. Depending on this option, you can get summarized information about fuel consumption or information about fuel consumed exactly by a vehicle.

By default the fuel level is given in integer numbers. The volume of the fuel consumed/registered/stolen as well as the average consumption is given correct to the nearest hundredth if their value is below 50 (if it is higher, then integer numbers are used). However, if you consider it necessary, you can see fuel always with accuracy to hundredths. For this, check the option 'Mileage/fuel/counters with accuracy to two decimal places' in the report template (the rest of numbers will be rounded off).

If the U.S. measurements are selected, the fuel is measured in gallons and the average consumption — in mpg (miles per gallon) unlike the European system where the average consumption is measures in l/100km (liters per 100 kilometers).

The fuel calculation algorithms process the messages considering filtration that is configured on the 'Fuel Consumption' tab (the option 'Filter fuel level sensors values').

During the mathematical calculation the fuel consumption is computed separately for each pair of messages.

The following algorithm is used:

1. The status of each engine sensor (engine ignition, absolute and relative engine hours sensors) in the current message is determined.
   
2. For the operating sensors the values indicated in the field Consumed, l/h of their properties are summed.
   
3. The values of the engine efficiency sensors are calculated.
   
4. The received values are summed according to the formula k1 + (k2 - 1) + (k3 - 1) + … + (kn – 1). In that way the coefficient is formed. If the sum of the coefficients is less than 0 or invalid, the total coefficient will be 1.
   
5. To determine the current fuel consumption of the unit, the value from the point 2 is multiplied by the value of the point 4.
   
6. The value from the previous message till the current one is multiplied by the value from the point 5.
   
7. The consumption for each message pair for the indicated interval is summed and in that way the fuel consumption is determined by consumption math.