Summary

Summary

This kind of report allows to from a table with diverse data concerning a period of time and at the same independent of any conditions like trips, sensor operation, geofence visit, etc. In other words, summary report processes all the messages for the indicated period regardless to the unit's duration of work, and time spent in motion.

The following columns can be included:

  • Mileage in trips: mileage on the interval by trip detector.
  • Mileage in all messages: mileage on the interval by mileage counter.
  • Mileage (adjusted): mileage on the interval by mileage counter multiplied by mileage coefficient (a setting in unit properties). More about mileage in reports...
  • Avg speed: average speed on the interval.
  • Max speed: maximum speed on the interval. More about speed in reports...
  • Move time: time in trips.
  • Engine hours: time of engine hours operation.
  • Engine efficiency duration: the duration of attached implements operation (if there is an engine efficiency sensor).
  • Parkings: total time of parkings on the interval.
  • Counter: counter sensor value.
  • Initial counter: counter value at the beginning of the interval.
  • Final counter: counter value at the end of the interval.
  • Custom sensor initial value: custom sensor value at the beginning of the interval. If there are more than one custom sensors, a separate column is built for each of them and name is written in brackets. Custom sensors name masks can be indicated in the right part of the template dialog.
  • Custom sensor final value: custom sensor value at the end of the interval.
  • Difference: difference between initial and final values of custom sensor.
  • Utilization: percentage ratio of engine hours duration to engine hours rate (engine hours divided by daily engine hours rate indicated in unit properties).
  • Useful utilization: percentage ratio of engine efficiency duration to engine hours rate.
  • Productivity: percentage ratio of engine efficiency duration to engine hours duration.
  • 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…: 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. Besides, in report template (on the right) you can specify additional parameters to calculate fuel: on the whole intervals, in trips or in engine hours.
  • Avg consumption: average fuel consumption by any sort of fuel sensor. If several such sensors are available, their values sum up.
  • Avg consumption by…: average fuel consumption on the interval. Details about fuel in reports...
  • Avg mileage per unit of fuel by …: average mileage per unit of fuel based on the indications of a sensor. ​
  • Initial fuel level: counter value at the beginning of the interval.
  • Final fuel level: counter value at the end of the interval.
  • Total fillings: number of fuel fillings detected.
  • Total thefts: number of fuel thefts detected.
  • Filled: volume of filled fuel (only fuel fillings detected by a sensor).
  • Stolen: volume of stolen fuel.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.

Fuel can be calculated for the whole interval, in trips or in engine hours, which is chosen in additional parameters of the table. This option affects such columns as 'Consumed…' and 'Avg consumption…'.

As additional settings, you can specify masks for sensors (fuel, counters), including engine hours sensor.

The 'Retrieve Intervals' option is available for this table if grouping by shifts is configured for it of if a value in the field 'Summary by:' is chosen.

'Summary' table is presented by one row — summarized data for a chosen period of time. However, report template parameters for this table contain an individual option — 'Summary by'. This option allows choosing time interval (shifts/days/weeks/months) according to which table data will be arranged. This option can be used either in reports for units or in reports for units groups.

 Note.
Often a value received from analog sensor may differ from the corresponding value in the 'Total' row. It is stipulated by analog data leaping, and application of grouping by days/weeks/months towards the values received as a result of processing such data. In the other words, analog data values (with or without leaps) are divided into intervals and then summarized. That is why the value of the summarized intervals can be sufficiently different from the value not divided into intervals. And so far as the values in the 'Total' row are not divided into intervals, you can receive the difference comparing to the values from analog sensors. For example, calculating fuel, a value in the 'Consumed by FLS' column may differ from the corresponding value in the 'Total' row.


    • Related Articles

    • Logistcs

      Logistics Logistics is a multifunctional program created to implement control over all the working stages of a courier delivery service. Logistics consists of two applications: web and mobile one. Web application is intended to be used by an ...
    • Tables

      he following tables (for units and unit groups) can be added to a report:                                                                                       Table Parameters Intervals Filtration Account Tree (for resource) Chat Check Points ...
    • Tables

      In the New table dialog, specify the name and type. The set of available table types differs depending on the selected type of the report template. The list of tables and their description are presented in the chapters below. Each type of the table ...
    • Data Messages

      If you request messages with data, the table of messages will contain information about the message time, speed, coordinates, location, and available parameters. In addition, in the Statistics section you can find summary information. There you will ...