Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
user:reports:tables:fuel_traffic [16/11/2017 14:08]
tagr zark
user:reports:tables:fuel_traffic [11/05/2018 09:27] (current)
tagr
Line 2: Line 2:
 ===== Fuel Traffic ===== ===== Fuel Traffic =====
  
-This report is designed to display ​in one table the data about fuel fillings and thefts, as well as the intervals of operation of the counter sensor of the unit. +This report is designed to display the data about fuel fillings and thefts, as well as the intervals of operation of the counter sensor of the unit in one table
  
-For each type of activity (fuel filling, theft, counter operation) you can customize its [[[user/​reports/​tables/​filtration|intervals filtration]] in the parameters of the table. If in the filtration parameters there are other selected units and at the moment of activity they were close to the unit on which the report is executed, the algorithm of fuel fillings analysis is run. Thus, when executing, for example, a report on a tanker, one can see not only its fuel activity, but also the amount of fuel received by the units near it (at least one message from such units should be received during the activity interval from a distance less than the radius specified in the filtration parameters).+For each type of activity (fuel filling, theft, counter operation) you can customize its [[user/​reports/​templ/​contents/​tables/​filtration|intervals filtration]] in the parameters of the table. If in the filtration parameters there are other selected units and at the moment of activity they were close to the unit for which the report is executed, the algorithm of fuel fillings analysis is run. Thus, when executing, for example, a report on a tanker, one can see not only its fuel activity, but also the amount of fuel received by the units near it (at least one message from such units should be received during the activity interval from a distance less than the radius specified in the filtration parameters).
  
 Read about setting the parameters used in the report in the //​[[cms/​units/​fuel|Fuel Consumption]]//​ and //​[[cms/​units/​sensors/​props|Sensor Properties]]//​ sections. Read about setting the parameters used in the report in the //​[[cms/​units/​fuel|Fuel Consumption]]//​ and //​[[cms/​units/​sensors/​props|Sensor Properties]]//​ sections.
Line 17: Line 17:
   * **Volume** — depending on the type — the quantity calculated by the counter sensor or the data from the //Filled// or //Stolen// columns taken from the columns of the same name in the corresponding tables.   * **Volume** — depending on the type — the quantity calculated by the counter sensor or the data from the //Filled// or //Stolen// columns taken from the columns of the same name in the corresponding tables.
   * **Sensor name** — the name of the sensor by which the type was determined.   * **Sensor name** — the name of the sensor by which the type was determined.
-  * **Geofences/​Units** — the column that includes the names of the geofences or units with which an intersection was recorded during a given interval. Necessary geofences and units are indicated in the [[user/​reports/​tables/​filtration|filtration parameters]]. If there are several geofences or units that have been triggered, the report displays the name of the geofence with the smallest surface or the name of the unit with the smallest radius of approximation. If the sizes coincide, all the names are included.+  * **Geofences/​Units** — the column that includes the names of the geofences or units with which an intersection was recorded during a given interval. Necessary geofences and units are indicated in the [[user/​reports/​templ/​contents/​tables/​filtration|filtration parameters]]. If there are several geofences or units that have been triggered, the report displays the name of the geofence with the smallest surface or the name of the unit with the smallest radius of approximation. If the sizes coincide, all the names are included.
   * **Filled** — the sum of the fuel fillings (if any) of the units shown in the //​Geofences/​Units//​ column. Only the fillings registered automatically and the time of which is within the interval from //​Beginning//​ to //End// are taken into account.   * **Filled** — the sum of the fuel fillings (if any) of the units shown in the //​Geofences/​Units//​ column. Only the fillings registered automatically and the time of which is within the interval from //​Beginning//​ to //End// are taken into account.
   * **Deviation** — the difference between the values of the //Volume// and //Filled// columns. ​   * **Deviation** — the difference between the values of the //Volume// and //Filled// columns. ​
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam