Statistics is a special table giving general information and results. It can contain reports name, unit name, reported interval, number of messages analyzed for the report, and any statistical information you select.

It is recommended to include Statistics to any report as it contains the basic information about the report itself.

Statistics is adjusted in report template in the section of 'Advanced settings'. Check fields you would like to include in Statistics. For your convenience, items are divided into subgroups. To select all items in a subgroup, tick the checkbox near its name.

If any item in statistics is checked, the section 'Statistics' appears at the left part of the report template. You can edit it if you click on the button  against it. Then you can add and remove items, rename them, and change their position. In the middle column the subgroup is indicated.

In the resulting report, Statistics is always displayed at the beginning of the reports.

The following information can be included in Statistics for reports of 'Unit' type. For other types of reports, statistics is different and can contain just a couple of rows: report template name, object's name, report interval beginning, report interval end, and time of report generation.

• Report: reports template name.
  
• Unit: unit name.
  
• Report execution time: time of report generation when a user executed the report online or it was generated automatically as a job or notification.
  
• Interval beginning: reporting interval beginning.
  
• Interval end: reporting interval end.
  
• Time zone: time zone as it is set in user settings.
  
• Messages: messages analyzed within the reporting period.
  
• Mileage in all messages: mileage in all messages according to the mileage counter selected (without filtration by trip detector).
  
• Consumed: the volume of consumed fuel detected by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• 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.
  
• Avg consumption: average fuel consumption by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• Avg consumption by ImpFCS/​AbsFCS/​InsFCS/​FLS/​math/rates: average fuel consumption in trips detected by one of the methods mentioned above. It can be presented either as liters per 100 kilometers or miles per one gallon. The whole mileage of the reported interval is normally taken for these calculations. However, average consumption by FLS can take either all mileage or mileage by trip detector. ​
  
• Initial fuel level: fuel level at the beginning of the interval.
  
• Final fuel level: fuel level at the end of the interval.
  
• Max fuel level: maximum fuel level.
  
• Min fuel level: minimum fuel level. Details about fuel in reports...
  

• Total counter: the sum of values of all sensors of counter type.
  

• Penalties: overall penalty for Eco Driving.
  
• Rank: received penalty points converted into a grade using 6 point scoring system.
  

• Engine hours: engine hours duration. It can be calculated by engine hours sensor or by ignition sensor depending on unit properties.
  
• Initial engine hours: value of engine hours in the beginning of the interval.
  
• Final engine hours: value of engine hours in the end of the interval.
  
• In movement: time when the unit had been moving within this interval.
  
• Idling: total idling time.
  
• Mileage in engine hours: distance traveled during engine hours operation.
  
• Initial mileage in engine hours: mileage sensor's value at the moment of the beginning of the reporting period.
  
• Final mileage in engine hours: mileage sensor's value at the moment of the end of the reporting period.
  
• Avg engine revs: average rate of engine revolutions.
  
• Max engine revs: maximum rate of engine revolutions.
  
• Engine efficiency duration: the duration of attached implements operation (if having engine efficiency sensor).
  
• Engine efficiency idling: engine hours minus engine efficiency time.
  
• Utilization: percentage ratio of engine hours duration to engine hours rate.
  
• Useful utilization: percentage ratio of engine efficiency duration to engine hours rate.
  
• Productivity: percentage ratio of engine efficiency duration to engine hours duration.
  
• Consumed in e/h: the volume of consumed fuel detected by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• Consumed by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in e/h: fuel volume used in engine hours. It can be detected by a fuel sensor (like impulse/absolute/instant fuel consumption sensor, fuel level sensor) or calculated by math or rates. Details...
  
• Consumed in idle run by ImpFCS/AbsFCS/InsFCS/FLS/math/rates: fuel volume used in engine hours during idle running detected by one of the methods mentioned above.
  
• Avg consumption in e/h: average fuel consumption by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in e/h: average fuel consumption in engine hours detected by one of the methods mentioned above.
  
• Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in e/h in trips: average fuel consumption in engine hours in trips detected by one of the methods mentioned above.
  

• Events count: the number of events registered.
  

• Executed commands: the number of commands sent to unit.
  

• Total filled: the volume of fuel filled during the reporting interval.
  
• Total registered: registered fuel volume regardless binding to sensors and calculation methods.
  
• Difference: the difference between registered and detected fillings.
  
• Total fillings: the number of fuel fillings detected within the reporting period.
  

• Total fuel stolen: the total volume of stolen fuel.
  
• Total thefts: the number of thefts detected within the reporting period.
  

• Images: the number of images received from unit. And if there are any, the resulting report will contain a section with all those images. Supported format is JPEG.
  

• Total maintenance duration: time spent for servicing.
  
• Total maintenance cost: total cost of all maintenance works.
  
• Services count: the number of services performed.
  

• Total orders: total amount of orders within the indicated time period.
  
• Orders visited: courier's arrival to an address is detected or any status is set.
  
• Orders visited in time: an order is visited in time (in advance) or any status is set.
  
• Orders visited late: an order is visited late or any status is set late.
  
• Non-visited orders: courier's arrival to an address is not detected.
  
• Orders fulfilled: courier's arrival to an address is detected, the 'Confirm' status is set.
  
• Orders fulfilled in time: an order is fulfilled in time (in advance), the 'Confirm' status is set.
  
• Orders fulfilled late: an order is fulfilled late, the 'Confirm' status is set.
  
• Orders visited without status: courier's arrival to an address is detected, a status is not set.
  
• Orders rejected: an order for which the 'Reject' status is set.
  
• Order's avg time (estimated): a ratio of time for orders visiting (system calculation) to a total amount of orders.
  
• Order's avg time (actual): a ratio of time spent delivering orders to a total amount of orders.
  
• Avg time deviation in orders: a difference between actual and estimated order's average time.
  
• Order's avg mileage (actual): a ratio of a distance covered by a courier to a total amount of orders.
  
• Order's avg weight: a ratio of orders' total weight to a total amount of orders.
  
• Order's avg volume: a ratio of orders' total volume to a total amount of orders.
  
• Order's avg cost: a ratio of orders' total cost to a total amount of orders.
  
• Avg fuel consumption for an order: a ratio of a total amount of fuel consumed to a total amount of orders.
  
• Orders' estimated mileage: total distance calculated by the system for orders delivery.
  
• Orders' actual mileage: total distance covered by a courier delivering orders.
  
• Fuel consumed in orders: total amount of fuel consumed delivering orders.
  
• Orders' total weight: overall weight of all orders created.
  
• Orders' total volume: overall volume of all orders created.
  
• Orders' total cost: overall cost of all orders created.
  

Moreover, the following data may be included in orders' statistics:

• Percentage of orders visited in time
  
• Percentage of orders visited late
  
• Percentage of non-visited orders
  
• Percentage of orders fulfilled in time
  
• Percentage of orders fulfilled late
  
• Percentage of orders visited without status
  
• Percentage of orders rejected
  

• Parking time: total duration of parkings for the reporting period. Parkings are detected by Trip Detector. IF it is not set properly, there may be no parkings found.
  
• Parkings count: the number of parkings for the reporting period.
  

• SMS messages: the number of SMS messages received from unit.
  

For the report on resource the following fields are available:

• SMS sent: the number of sent SMS messages.
  
• SMS available: the number of SMS available at the moment.
  

 The quantity of SMS messages shown in these fields doesn't depend on the report's execution interval. The information is shown for the period that corresponds to the option Reset of the 'Services' tab of the billing plan's properties.

• Stops count: the number of stops for the reporting period.
  

• Move time: total duration of all trips.
  
• Engine hours: engine hours worked.
  
• Mileage in trips: total distance traveled in all trips.
  
• Mileage (adjusted): the same distance multiplied by mileage coefficient (a setting in unit properties).
  
• Urban mileage in trips: distance traveled at speed which is considered as speed in populated areas.
  
• Suburban mileage in trips: 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 moment of trip beginning. If no saving of mileage parameter was made through the reported period, mileage is counted from 0.
  
• Final mileage: mileage sensor value at the moment of trip ending.
  
• Toll roads mileage: the distance of a trip travelled by the roads where 'Platon' system is used.
  
• Toll roads cost: a sum of money (in RUB) for the toll roads mileage calculated on the basis of covered distance and the 'Platon' tariff.
  
• Average speed in trips: average speed in trips (total mileage divided by move time).
  
• Maximum speed in trips: the maximum speed registered during the trips.
  
• Trips count: the number of trips.
  
• Consumed in trips: the volume of consumed fuel detected by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• Consumed by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in trips: fuel consumed in trips. It can be detected by a fuel sensor (like impulse/absolute/instant fuel consumption sensor, fuel level sensor) or calculated by math or rates. Details...
  
• Rates deviation by ImpFCS/AbsFCS/InsFCS/FLS in trips: the difference between fuel consumption detected by a sensors and fuel consumption rates.
  
• Avg consumption in trips: average fuel consumption by any sort of fuel sensor. If several such sensors are available, their values sum up.
  
• Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in trips: average fuel consumption in trips detected by one of the methods mentioned above.
  
• Avg mileage per unit of fuel by ImpFCS/AbsFCS/InsFCS/FLS/math/rates in trips: average fuel consumption presented as 'kilometers per liter' or as 'miles per gallon' .
  

Note that all items in this section do not depend on report interval. The latest information is taken at the moment of report execution.

• Mileage counter: mileage counter value.
  
• Engine hours counter: engine hours counter value.
  
• GPRS traffic counter: consumed traffic.
  
• Unit last location: the latest unit location detected (address or coordinates).
  
• Last message time: the time when the latest messages from the unit was received.
  

How mileage and engine hours are calculated is adjusted in unit properties on the 'General' tab.

• Total utilization cost: total cost of all registered service works and fuel fillings.
  
• Count of services and fillings: total number of all registered service works and fuel fillings.
  

List of video files received from a unit.

• Violations count: the number of violations registered within the reporting period.
  

• Streets count: the number of found visits of streets.