Reports are one the most powerful features of our software

This is a complete reporting overview. Reports are one the most powerful features of our software. We will teach you how to use them and also what everything means in detail. We have divided everything into smaller sections so you can view what you want when you want to.

Best seller 5(1 Ratings) 1 Students Enrolled
Created By QuickTrackGPS.com Last Updated Mon, 29-Oct-2018 English
What Will I Learn?
  • Transfer from tabular report to messages
  • Report Formats
  • Creating Report Template
  • Advanced Settings
  • Grouping/Sorting
  • Speed/Fuel Consumption Chart
  • Bindings
  • Custom Fields
  • Driver Activity
  • Eco Driving
  • Orders
  • Speeding
  • Much more..

Curriculum For This Course
51 Lessons 06:10:00 Hours
Reporting
51 Lessons 06:10:00 Hours
  • Advanced Reports / Reports 00:20:00
  • Chart Management / Reports 00:05:00
  • Charts / Reports 00:05:00
  • Check Points / Reports 00:10:00
  • Chronology / Reports 00:05:00
  • Counter Sensors / Reports 00:10:00
  • Custom Fields / Reports 00:05:00
  • Data in Reports / Reports 00:05:00
  • Digital Sensors / Reports 00:05:00
  • Driver Activity / Reports 00:05:00
  • Eco Driving / Reports 00:10:00
  • Engine Hours / Reports 00:05:00
  • Events / Reports 00:05:00
  • Export Report to File / Reports 00:10:00
  • Fuel Fillings / Reports 00:05:00
  • Fuel Thefts / Reports 00:05:00
  • Geofences / Reports 00:15:00
  • Geofences on Map / Reports 00:15:00
  • Sorting by Date / Reports 00:10:00
  • Logs / Reports 00:10:00
  • Maintenance / Reports 00:10:00
  • Markers / Reports 00:10:00
  • Messages Tracing / Reports 00:05:00
  • Online Report / Reports 00:10:00
  • Orders / Reports 00:10:00
  • Parkings / Reports 00:10:00
  • Print Report / Reports 00:05:00
  • Profile / Reports 00:05:00
  • Query and View Reports / Reports 00:10:00
  • Report Templates / Reports 00:20:00
  • Reports / Reports 00:10:00
  • Reports on Drivers / Reports 00:05:00
  • Reports on Trailers / Reports 00:05:00
  • Reports on Users / Reports 00:05:00
  • Rides / Reports 00:05:00
  • Rounds (for unit) / Reports 00:05:00
  • Sensor Tracing \ Reports 00:05:00
  • Special Charts / Reports 00:05:00
  • Speeding / Reports 00:05:00
  • Statistics / Reports 00:05:00
  • Stops / Reports 00:05:00
  • Summary / Reports 00:05:00
  • Tables / Reports 00:05:00
  • Thefts detection / Reports 00:05:00
  • Tracks on Map / Reports 00:05:00
  • Trips / Reports 00:05:00
  • Unfinished Rides / Reports 00:05:00
  • Upcoming Maintenance / Reports 00:05:00
  • Utilization Cost / Reports 00:05:00
  • Violations \ Reports 00:05:00
  • Visited Streets / Reports 00:05:00
Requirements
+ View More
Description

Reports

To open the Reports panel, choose a corresponding name in the top panel or click on the necessary item in the main menu customizer.As a result, reports window will appear. Units activity could be presented in reports as tables or charts. Here you can create report templates, generate reports and view them right in the browser or export them to the files of various formats like PDF, XML, XLS (Excel), HTML, CSV.The Reports panel window can be divided into four sections:
  • In the top left-hand corner, the basic parameters to generate a report are adjusted.
  • In the bottom left-hand corner, you create and store your report templates. After an online report is generated, this section changes for the navigation bar.
  • In the top right-hand section, there is the map.
  • In the bottom right-hand section, you see the report itself if it has been generated online. A report appears in the form of tables and charts.
The sizes of the sections are changeable. Click on the horizontal or vertical slider and holding the left mouse button drag it up/down or left/right.

Query and View Reports

To generate a report, set the following parameters:Report templateThe last created or edited report template is chosen in the dropdown list by default. Choose any other template from the dropdown list if necessary. On the right of the selected template, there is a button to display template properties for viewing and editing.  If no templates are available, it is impossible to generate a report. How to create a report template…ItemChoose a system object to apply the report to. Depending on the template selected above, you will be offered to choose unit, unit group, user, driver, route, retranslator, or resource. As in case of templates, on the right of the selected object there is a button to check object's properties. Usually, all objects of the appropriate type and enough access (Query messages or reports is required) are displayed in this dropdown list. However, in case with units, not all units are displayed in this dropdown list but only those which are in the work list of the Monitoring panel at the moment. In case the work list is empty (when dynamic work list is used or when units have been deleted from the work list manually), the units to which you possess the corresponding rights will be displayed.Interval typeUse buttons Today, Yesterday, Week, Month for quick report generation for the most frequently wanted intervals. What concerns the last two, you will get a report for previous week or month (that is last full week or month), and week starts on Monday. Note that if you press one of those four quick buttons, the report launches immediately (no need to press Execute).Otherwise, you can select other types of intervals to specify the reporting period more accurately. Three ways to specify the interval are possible here:
  • Specified interval: specify date and time (to minutes) of the interval beginning and end.
  • Starts 'From' until today: specify the beginning only, and the and will be set automatically as the current date and time.
  • For previous [select the number] minutes/hours/days/weeks/months/years. The digital value of an interval can be entered in the corresponding field using special arrows or scroll wheel. If you press and hold an arrow, the numbers will change at an increased speed. Note that the acceptable values are from 1 to 99. The current day (week, etc.) can be included into the interval or not depending on the state of Include current checkbox.
When report parameters are adjusted, press the Execute button below. Note. There are alternative ways to receive reports in the tracking system:
  • getting reports by e-mail at specified time (adjusted through jobs);
  • getting a report when an event happens (adjusted through notifications);
  • quick report generation from the Monitoring panel (see Monitoring ⇒ Icons Explanation).
 Note that in order units' tracks to be displayed on the map you should check if the corresponding layer icon in the main menu is active.

Online Report

To generate a report online, adjust the parameters described above and push the Execute button. If no tables or charts appear on the right, it means there is no data about the selected object for the selected period or poor report content is selected in the template.After executing a report, the Report Templates panel changes to Report Results that displays report contents and provides navigation through the report. Usually, a report contains several pages. To switch between them, use navigation links in the Report Results panel. The name of the active page is bold and highlighted with a light blue background.The information in reports can be presented in the form of tables or charts. Some information can be visualized on the map, for example, tracks and markers.If the text in a cell is blue, it means that there are coordinates for this point. Click on such a cell to move to that place on the map.To adjust the number of rows to be displayed on one page, choose the number in the dropdown menu: 25, 50, 100, 200, 500. To navigate between the pages, use the blue buttons in the toolkit: go to the next page, go to the previous page, go to the first page, go to the last page.The page number can be entered manually. After entering a number, push on the keyboard to go to the required page.To delete an online report, push Clear. The map and the report itself will be cleaned, and the Report Result panel will be replaced by Report Templates again. However, you can switch between these two panels manually. To do this, just click on the header of the corresponding panel.Other buttons located in the toolkit allow to:  — transfer to messages; — quick export to PDF (landscape orientation, A4 format, and fixed page width is a default setting for PDF file); — quick export to Excel; — export report to a file; — print report.

Transfer from tabular report to messages

The tracking system allows transferring to messages straight from a tabular online report. It can be useful for analysis of unit data messages. To move from table to messages, it is necessary to press the 'Transfer to messages' button in the toolkit. After pressing it, text in some time cells becomes purple and works as a link. By clicking on the link transfer to messages is performed. Depending on the table type columns with time indication can vary, for instance, 'Time', 'Beginning', 'End', etc. Messages are loaded for the whole report period, at that a page with selected message is opened first. The line with this message is highlighted in grey. The map is centered in regard to the selected message which is indicated with a red marker. By default, the transfer button is released. When switching from table to chart it is restored to default state, in spite of the fact that it could be pressed before in one of report tables.

Print Report

After generating an online report, it can be printed without saving it to the disk. To do this, press the Print button that becomes accessible only when there is a report in browser window.In the left part of the Print Report dialog, you see the list of sections which are included in the report. Check those of them that you are going to print. On the right, you can preview all these tables, charts, map, etc. To start printing, press Print. To exit, press Close. Note. In Internet Explorer 10, maps and charts cannot be printed if the option 'Enhanced Protected Mode' is on.

Export Report to File

To get a report in the form of a file that is suitable to save on disk, print or send by e-mail, push the 'Export to file' button .Choose desirable file format or several formats at once and specify parameters. Supported formats are HTML, PDF, Еxcel, XML, CSV. Reports in the form of files can be regularly sent to your e-mail automatically – through jobs and notifications.

Export Parameters

Give the file any name. This is optional and if left empty, a file will be given a default name (like 'Online_report').Specify whether to apply compression to file or not — 'Compress report files' option. Compression is mandatory for HTML and CSV file as well as for cases when more than one format is selected.Indicate the corresponding flag if it is necessary to attach map to the exported report. Graphical objects (like map, chart) can be exported only into HTMLor PDF files. Note that the map will be attached to the file only if any graphical elements (as tracks, markers, geofences, etc.) are chosen in the report template. By default the map is scaled in order track/markers/last unit position to be seen on it. If these elements are not shown on map (not chosen in report template), then the map will not be attached. If the 'Squeeze in all graphics' flag is chosen, then the map is scaled in such a way that POIs and geofences to be shown on map along with the above mentioned elements. Only WBC Fleet Maps can be used for in exported files. Furthermore, the map layer can be hidden ('Hide cartographic basis' option) so that tracks and markers will be shown on the blank background.A function of using a link to display location (coordinates should be available) is supported for the files exported in PDF or Excel. It works the following way: open the exported report (PDF/Excel), place a cursor on the corresponding field of a report, for example, beginning/end time or address information from a unit (cursor pointer changes its shape for a hand), click on the link, and afterwards Google Maps cartographical service is opened in your browser showing unit's location by a special marker. If there is no need in showing unit's location you can disable links to Google Maps in PDF and Excel files by indicating the corresponding flag in export parameters.If necessary, you can disable links to Google Maps in PDF and Excell files by indicating the corresponding flag.More parameters can be adjusted for some file formats. Those additional parameters are described below.Usually you export to a file a report that is already in the browser. However, you can also generate a new one according to the parameters set in the left panel. In this case, you should check the 'Generate report' option.At the end, press OK. Depending on browser settings, you will be offered to open file or save it.

Report Formats

  • HTML: Your report will be generated as Internet page and will open in any browser.
  • PDF: PDF is a widespread format suitable for electronic usage as well as for printing. To view these files Adobe Acrobat Reader is used (for Windows OS only).
You can additionally adjust such page parameters as orientation (landscape or portrait) and page size (A4 or A3). If a table in the report contains many columns, page width option can be also useful. The standard page width is fixed which means it depends on selected page format and orientation. However, if a table is too wide and does not match the fixed page width, this table will not be exported (only the heading will be displayed). In such cases, you can select automatic page width, which means it will correspond to the largest row in the table. If Auto, compact is selected, cell with is equal to the length of the largest word in it. If Auto, no wrap is selected, cell with is equal to the largest phrase in it (no line breaks are applied). Note that if automatic page width is selected, page format and orientation become relative — they define only page height.
  • Еxcel: Your report will be presented as Microsoft Excel electronic table (.xlsx file).
 Note. When exporting PDF, HTML, Excel the alignment is used. The columns containing text (names of sensors, geofences, drivers, users, SMS and notification text, location addresses, etc.) are aligned left. The columns containing numeric data (time, duration, speed, mileage, fuel, payments, count, etc.) are aligned right.
  • XML: XML is a textual data format that is notable for structured data storage and useful for data exchange between programs.
  • CSV: CSV is a textual data format used for the digital storage of data structured in a table of lists form, where each row in the file corresponds to a row of a table, and the columns are separated from each other by a special delimiter. You can additionally set coding (utf8, cp1251) and delimiter (comma or semicolon).

Report Templates

The list of all templates available is located in the bottom left-hand corner of the window under the header Report Templates. Here you can create, edit and delete templates for reports, as well as copy them and move them from one account to another.Templates contain information upon which tables and charts to be included in the resulting report, what kind of content to be presented in tables, sequence order of columns in tables and sections in the report, which graphical elements to be rendered on the map, and many other parameters which define the look of the resulting report.In the tooltip, you see the name of the resource which holds this template (if you have access to more than one resource). If clicking on a template, it becomes selected in the Template field of report generation parameters.When searching for a template on the list, it is convenient to use the dynamic filter. Enter template name or its part into the search text box and observe the results. Additional search parameters are set in the dropdown list where you can choose the resource or leave All.The following actions are available: or  — edit or view a report template (depends on your access level); — create a new template using this one as a basis; — delete a template (if the button is dimmed, you have not enough rights). Note. If a template belongs to some resource to which you do not have access rights to Create, edit, and delete report templates, then you will not be able to edit or delete this template.

Creating Report Template

 To make manipulations with reports templates, you should have at least one resource with the access right Create, edit, and delete report templates.To create a new report template, press the New button. In the dialog enter a name for the template and choose its type:
  • Unit — such template can be applied to separate units;
  • Unit group — such template will be used to gather information about several units at once (see unit group);
  • User — such template can be used to analyze users' activity in the system;
  • Drivers — such template can be used to analyze drivers' work;
  • Resource — such template is used to analyze how resource contents change;
  • Retranslator — such template is used to analyze the work of retranslators;
  • Route — such template can be used to analyze units' performance on routes.
It is not recommended to change template type when editing a previously created template because all template contents will be lost with this action.Report template can be bound to the particular object(s) of the system. For example, you create a report template, choose 'Unit' as its type, and you know for sure that this report is necessary for some particular units (not for all your fleet). If the corresponding units are not chosen for this report, then during request formation you will need to look through the whole list of units to find the necessary ones. However, if the necessary units are bound to the report template, then during request formation the list of elements will contain only the units you have indicated. Note that object binding works for all types of report templates.To bind object(s) to a report template, click the 'Bind' button to the right of the report type field. In the appeared window indicate flags for the necessary objects, and click OK. Note that afterwards a number of bound objects will be shown on the Bind button.Add tables and charts to your template, choose items for statistics, adjust map output, and decide upon other parameters of the report. All added contents will be displayed at the left of the dialog.In the left part of the dialog, you can set the sequence order of the pages and give them custom names if needed. To change section name, click on it and enter any text. To manage template contents, use the following buttons: — drag up/down, — edit a table/chart, — make a copy of a table/chart, — delete page. Note. No matter where you place a chart, in the resulting report all charts follow after all tables, and the Statistics section goes first.

Advanced Settings

The right part of the Reports Template dialog contains advanced settings. They are divided into four sections:
  • Options
  • Map output
  • Statistics
  • Address
  • Shifts
Depending on template type, all or just several of these sections may be displayed.

Options

Multiple drivers/trailers option usage makes sense if a table containing such columns as 'Driver' or 'Trailer' is added to the report template. If the box is not checked, then regardless of the number of drivers/trailers appointed to a unit for the particular interval (trip, parking, etc.), only the first one of them will be shown in the table. If the box is checked, then all the drivers/trailers appointed to a unit for the particular interval are shown in the table.Mileage/fuel/counters with accuracy to two decimal places. By default, mileage less than 20 and fuel less than 50 is displayed with accuracy to hundredths, and larger values are given as integers (if the value is rounded to 0, the result is printed as 0.00). Counter sensors of any values are by default displayed as integers, too. However, if you consider it is necessary, mileage, fuel, and counters can be shown with accuracy to two decimals (other decimal places are simply cut). If you see '0.00' in a cell, it means the initial value had thousands or even smaller fractions, which can be seen if you export report to XML, CSV or Excel.Exclude thefts from fuel consumption can be chosen if you want to ignore thefts when calculating fuel consumption in different tables and statistics. Normally, thefts are considered as a part of fuel consumption. That is, if the option is enabled, columns like Consumed by FLS and Average consumption by FLS are calculated without considering fuel thefts.Mileage from trips only is an option that affects mileage calculation. Mileage can be calculated either by all messages or by messages in trips (considering trip detector).Consider track-geofence intersections is an option which allows detecting geofence visiting in case a trip intersects a geofence by any segment of its track. This option can be applied for such reports as 'Geofences', and 'Rides'.Persian calendar and Date and time format options are applied to cells of the resulting report where time is shown. These options are adjusted in the same way as in the User Settings dialog.Measurement system option defines the metrics for such parameters as mileage, speed, fuel, and temperature in reports. Note. Depending on the measurement system chosen in a report template for which the intervals filtration has been applied you should consider that the values of filtration parameters will not be converted to the corresponding values of the other measurement system automatically. Nonetheless, the metrics will be changed to the corresponding metrics of the chosen system. For example, if you have 50 kilometers mileage and 100 kilometers per hour speed, after choosing the american measurement system you will receive 50 miles mileage and 100 miles per hour speed.One more option is provided for group reports — Skip empty rows. It is used to withdraw uninformative rows from the resulting table. For example, you create a report about fuel thefts, but not each and every unit in the selected group has thefts, so there can be a lot of empty rows in the table.

Address

Here you choose how address information is presented in the resulting report. 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.Addresses can be taken either from WBC Fleet Maps or from geofences.

Addresses from Map

You can select which address items to be displayed (country, region, city, street, and house are available) and specify their sequence order (for this, drag items up and down with blue arrows). If none of five address items is chosen, coordinates are displayed instead of addresses.For addresses which fall out of city bounds (near or on roads), two settings are important:
  • Max distance from unit says that if unit is located near a road and there is a city (i.e., city, town, village) within the indicated distance, then in the address you will have the road's name and distance to the city.
  • Min radius says that if no city has been found within maximum distance from unit (the previous option), then the address is bound to another city. How big this city should be to form the address, you indicate here — minimum radius of a city. This can be used to eliminate small cities from addresses.
 Note. Addresses for reports can be taken only from WBC Fleet Maps (no Google, Yandex, or other services can be used). If you find inaccurate address information in the reports, updating the map of your region/city may help. For this, make a request to the technical support and enclose a new map in proper format.

Addresses from Geofences

Sometimes WBC Fleet Maps may not contain precise addresses in certain regions. In such cases, you can use geofences as addresses. Besides, you can make use of this feature to customize some addresses, make them clearer.If the option 'Use geofences for addresses' is selected, additional parameters become available. In particular, you can choose to display geofence's description alongside with its name (the option 'Add geofence description to address').The range of geofences used as addresses is adjustable. By default, all geofences that belong to the same resource as the reports template are used. However, geofences from all available resources can be employed if necessary. Alternatively, to narrow this range, you can specify certain group of geofences to be used (it should be created in the same resource as report template itself). Choose one or another option in the dropdown list 'Specify geofences' (groups of geofences are in square brackets).If you choose to use geofences as addresses and coordinates of a unit get into one, its name (and maybe description) will be displayed in the address cell. If two or more geofences are found in this place, then the smallest one will be used. If no geofences are found in given location, the address from the map will be displayed.

Shifts

If the option is enabled, then information in the report will be structured by shifts. For example, a transport company has a vehicle and two drivers. And it has been calculated that profit from the vehicle usage comes only if it is used in two shifts: from 9 a.m. till 7 p.m., and from 9 p.m. till 7 a.m. Assume that we would like to receive any kind of report for the unit in terms of this shifts, and we need no information on what happens with the vehicle in time between shifts. So, it is necessary to adjust shifts correspondingly, and indicate its flag in order this setting to be used. Moreover, for this particular situation it is necessary to apply grouping by shifts and use intervals' retrieving.

Tables

A template can contain any number of tables and charts. You can even add the same table type several times with different configuration of columns, data grouping and other settings.To add any of above mentioned tables to the template, click the Add Table button and choose a table from the list.Each table type has its set of columns that can form this table. After you have chosen table type, the list of columns available is displayed below. Check the columns you would like to include in the resulting table. To select all columns at once, press on the keyboard and click on any checkbox. To make all columns unselected, repeat the same operation. This combination works also for reports where you choose geofences, events, etc.You can rename columns, clicking on their names and editing the text. In the same way you can change the name of the table itself (the Name text box at the top of the dialog). To restore default column names, use the button Restore default (when it is gray, it means the current name is default).Besides, you can apply to the columns any sequence order. Move them up and down dragging the button.

Table Parameters

In the right part of the report template dialog, you can set additional parameters for the table such as:
  • grouping,
  • detalization,
  • row numbering,
  • total row,
  • time limitation.
These parameters can be applied to any kind of table.

Grouping/Sorting

GroupingReports are supported with a grouping feature. It works in the following way: from the available time intervals (year, month, season, week, day of the week, day of the month, date, shift, duration) you choose those by which you would like to group table data. Grouping can be made either by single time interval or by several (or even by all of them). If grouping by several time intervals is chosen, you should indicate the order of nesting for these time intervals. For example, table data can be grouped by years, each year group can contain months' grouping (nested inside), and each month can contain grouping by dates (nested inside). Nesting is adjusted by dragging the corresponding time interval up/down in the list of groupings (the lower items are nested in the higher ones)If grouping by such intervals as season and duration is chosen, then beneath you can find a special block where it is necessary to set intervals' values. Let's see it in detail:
  • For season: It is necessary to indicate season's name (any), for example, summer, autumn, etc. Afterwards, using dropdown lists choose season's duration. Note that season's duration is considered to be a time period from the first day of the month in the first dropdown list to the last day of the month in the second one. Minimum season's duration is 1 month. To indicate minimum duration, choose the same month in both the dropdown lists. To activate an entered season, click '+' button. Maximum number of seasons is 12.
  • For duration: It is necessary to give name for an interval (for example, interval 1), indicate interval's duration in seconds/minutes/hours/days (choose from dropdown list), and activate it by clicking '+' button. Maximum number of durations is 5. On the example of 'Trips' report let's observe how the usage of duration periods influences report data presentation. The following periods are indicated: 'Short' — to 15 minutes, 'Middle' — to 1 hour, 'Long' — to 3 hours. Data in the report will be presented in the following way: short trips — from minimum trip time indicated in trip detector up to 15 minutes, middle trips — from 15 minutes up to 1 hour, long trips — from 1 hour up to 3 hours.
Note that depending on report type additional groupings can be used along with the standard ones (for example, by geofence, route, sensor, user, event, action type, violation type, trips, streets). In this case items in a group are arranged by their name .Sorting: Grouped data can be sorted by any criterion chosen as a column of a table. Opposite to each interval a dropdown list is situated. Each list contains a number of sorting criteria (table columns included in a report). From this dropdown list choose a criterion which will be applied to the nested level of grouping. Moreover, to the left of the dropdown list there is an icon clicking which you can indicate the sorting direction (from min to max or vice versa).Note that table data can be sorted even without grouping applied. To do so, choose the corresponding sorting parameter opposite to the 'Total' interval, and afterwards indicate sorting direction.Let's explore grouping and sorting features on the example. To do so, we create report on trips. We are interested in maximum speed, duration, engine hours, and mileage criteria, so it is necessary to check these flags (table columns). Moreover, we need to divide information by years, months, and dates, and also it would be convenient for us if the dates were sorted by maximum speed (from max to min value).By default a grouping is off, so we receive a detailed report where an individual line corresponds to every criterion, and these lines are displayed in a chronological order, or according to a sorting chosen for a table.But in our case it is necessary to apply grouping. Check the 'Year', 'Month', and 'Date' flags. Adjust nesting (by dragging items in the list). Afterwards, choose a sorting criterion from the dropdown list, and indicate sorting direction (from max to min value). We would like to apply sorting for the level nested into the months (dates), so it is necessary to choose the corresponding criterion from the dropdown list opposite to the month interval. Then click on the sorting direction icon in order to adjust sorting from maximum to minimum values.  Note that usually if a dash is chosen in the dropdown list, then the sorting has chronological order.The report has the following view. The table receives two additional columns, one of them shows grouping, and the other contains the buttons ('+'/'-') using which you can expand/hide nested levels of a grouping applied. Information is grouped by years. You can either expand groupings consequently (by clicking all the pluses one by one), or go straight to the necessary nested level (by clicking the corresponding one in the header of the table). The dates in the table are sorted by maximum speed (from maximum to minimum value).Available time intervals and their application in reports:
  • Total: the top level of grouping (cannot be moved). If the flag is checked, then we receive a groping with data resulting (total duration of any state, total number of registered events, etc.). This grouping contains all the other nested levels (if available).
  • Year: table data is grouped by years.
  • Month: table data is grouped by months.
  • Week: table data is grouped by weeks. The week is presented in the table by its number (for example, week 26, etc.).
  • Day of the week: table data is grouped by days of the week (for example, Monday, Tuesday, Wednesday, etc.).
  • Day of the month: table data is grouped by days of the month (for example, 1st, 2d, etc.).
  • Date: table information is grouped by dates.
  • Shift: table data is grouped by shifts.
Note that if grouping is used, then all the events beginning in the analyzed interval are included in this interval even if they exceed the actual duration of an interval.One more column can be useful for tables with grouping — Total time. The meaning of this column is similar to 'Duration' column but a bit different. 'Duration' shows the sum of intervals, for example, the sum of all trips detected. 'Total time' shows time from the beginning of the first interval to the end of the last, for example, time from the beginning of the first trip on a day to the end of the last trip on the same day (so, you can know real working shift).Retrieve Intervals: This option can be applied only for reports with grouping by shifts. If the 'Retrieve intervals' flag is not indicated, then the whole interval of a trip 'crossing' the shift gets into the report. If the 'Retrieve intervals' flag is indicated, then the report will contain only data from messages received inside the indicated interval.

Detalization

A table with a grouping can be extended by the way of detalization. Detalization is actually a final level of nesting (date and time). To view this level, you can either expand all the previous ones ('+' at the beginning of the line), or click the largest number in the heading of the corresponding column (expands all the enclosed nesting levels).Let's take the previous example with groupings, and extend it by the way of detalization (check the corresponding flag in the table parameters). This example already includes the grouping by years, months, and dates, so the option of detalization allows us to extend the level of nesting directly to the time an event has taken place (hours, minutes, seconds).Note, as it was already mentioned before, sorting is applied to the following level of nesting. And as far as detalization corresponds to the final level of nesting, you can indicate sorting for it as well. Sorting for detalization is indicated in the same way as for the groupings.Detalization can be applied only to grouped tables; it does not affect detailed tables.

Row Numbering

Row numeration can be added to any table type. To switch the numeration on, check Row numbering box in table advanced parameters. The numeration is added to the table as its first column.When numbering and grouping meet together, you get multilevel numbering. The main level is a usual numeration of main rows with integer numbers. The following level is the numeration of nested rows as 'main row number — dot — nested row number'.

Total

The Total row can be added to any table regardless its type, grouping or detalization applied. The total row is added as the last row in the table and contains the resulting information such as total duration of a state, total number of events registered, etc.In online reports the total row is located at the bottom of the window regardless the number of pages in the table or scrolling bar location.Location information is not given in the total row (replaced by dashes).

Time Limitation

Time limitations can be applied to tables to limit data analysis by some time intervals, days of the week, days of the month or months. For example, you can select working days and working time to be considered while generating the table.There are two algorithms available for time limitation. According to the first one ('Cut off intervals' flag is not chosen) if any state (for example, trip) begins inside the indicated time limitation interval, and ends outside it, then such a state will not be terminated, and its full duration will be included in the report. According to the second one ('Cut off intervals' flag is chosen) if any state (for example, trip) begins inside the limitation interval, and ens outside it, then the report will include only the duration of such a state inside the indicated interval, and everything outside the interval will be 'cut off'.For example, if the period from 9:00 till 18:00 is chosen as time limitation interval, and two trips has been registered, the first — from 7:50 till 12:00 and the second — from 13:00 till 18:20, then:
  • according to the first algorithm, only the trip started inside the limitation interval will be entirely included in the report. I.e., there will be one trip from 13:00 till 18:20 in the report.
  • according to the second algorithm, two trips within the indicated limitation interval will be included in the report (from 9:00 till 12:00 and from 13:00 till 18:00).
 To apply time limitation equal to the whole day, insert the interval from 00:01 to 23:59.

Intervals Filtration

Several tables are supplied with additional parameters to filter intervals. There you can set conditions to select information to be displayed in the resulting report. These conditions affect reports that concern selecting intervals from the collection of messages. These reports are: Counter sensors, Digital sensors, Geofences, Engine hours, Parkings and Stops, Rides and Unfinished rides, Speedings, Trips, and others.The set of filtration parameters varies depending on table type. The following parameters are possible: duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, driver, trailer, fuel fillings and thefts, geofences. Adjusting these parameters will limit the scope of intervals getting to the report. For example, you can indicate the minimum duration and minimum mileage for the trips to be displayed. Alternatively, you can query visited geofences with a stop at least 10 minutes in them. Note that all the filters except for the mileage one work with integer values.Incomplete intervalThis filter affects only the last interval in the report. In many cases, reported period ends and the last interval (trip, sensor operation, etc.) still continues. You can choose one of the following options to deal with such unfinished intervals:
  • Show and cut off: show the incomplete interval and consider that it ends with the last message within the reported period;
  • Do not show in report: do not show the incomplete interval in the report;
  • Show and mark as incomplete: the incomplete interval will be shown and will have 'Unknown' as the end time.
DurationMinimum and/or maximum duration of the interval.MileageMinimum and/or maximum distance traveled in the interval. Either integer or non-integral values can be indicated as a filter. For non-integral values use dot as a delimiter.Engine hours sensorEnter name mask for engine hours sensor. It affects calculations in reports which contain any information on engine hours as well as engine hours filter below.Engine hoursMinimum and/or maximum duration of engine hours. In addition, engine hours sensor mask can be specified in the filter Engine hours sensor.Speed rangeIndicate minimum and/or maximum speed to be considered. It means that only those intervals will be displayed in the report which contain at least one message with speed falling into the range. But more helpful might be retrieving intervals. If you check the Retrieve intervals box, the report will focus on intervals where all speeds fall into the range.TripsThis filter is used to show only intervals which somehow intersect with trips or, on the contrary, do not intersect.StopsTick the checkbox and choose one of the two possibilities: With stops or Without stops. Then in the resulting table, only intervals that meet the given condition will be shown. If the Stops option is not selected, then all intervals are displayed regardless if there were any stops or not.ParkingsThe settings are similar to those for stops. In addition, you can indicate the minimum parking duration. For instance, you can query geofences where there is a parking of a specified time (the Minimum duration flag). Besides, the parking time can be summed up (the Sum up intervals flag). That means the geofences where the total parkings make up the specified time will be displayed.SensorsThe intervals where there are messages with sensor on or off can be selected. In addition, you can indicate minimum and/or maximum time of sensor's on/off state. Like in parkings, the duration can be summed up (the Sum up intervals flag). Besides, the intervals of on/off state can be retrieved, and each of them can be presented as a separate row of the table (the Retrieve intervals flag). To indicate a certain sensor to be controlled, type its mask below. If you select several, then the intervals which contain points with all these sensors on/off (simultaneously) will be selected. If no masks are specified, then all sensors will be considered.Sensors masksHere you can enter sensor masks which will be considered upon report generating. Sensors masks can affect Sensors filter, Counter column, and information on fuel (if any of these options is selected in the report template). Note that engine hours mask is indicated individually in the corresponding field.DriverThis filter allows selecting intervals with a certain driver or driver group or without them. Choose the option With driver and specify the driver's name mask. The resulting table will contain only the intervals with the corresponding driver — it does not matter whether this driver is at the beginning, in the middle, at the end or in all course of the interval. If the option Driver group is chosen, while generating a report only those intervals that have some driver belonging to a group (the group’s name mask can be indicated as well) will be analyzed. In addition, you can enable the option Retrieve intervals to get only those segments that contain the specified driver or group from the scope of intervals.If the option Without driver is selected, the resulting table will consist of intervals which contain segments without any drivers or driver groups. Those segments can be retrieved as well.TrailerThis filter works in the same way as the previous one, but it allows to filter intervals according to presence or absence of a trailer assigned to a unit.Fuel fillingsIntervals with fillings or without fillings can be displayed in the table. If the first case is chosen, then you can additionally indicate max and min filling volume. Fillings can be summed up. In this case, the indicated filling volume will be applied to the total of fillings found.Fuel theftsIntervals with fuel thefts or without thefts can be displayed. If the first case is chosen, then you can additionally indicate max and min theft volume. Like fillings, fuel thefts can be summed up.Geofences/UnitsThe filter is divided into two parts — geofences and units. In the upper part you can select geofences to be analyzed for the report. You can focus on unit activity in or out of a geofence. To put a geofence under control, move the marker from None to In or Out against a required geofence. Only geofences that belong to the same resource as the reports template itself can be displayed here.  To facilitate the process, you can indicate flags for groups of geofences (displayed in square brackets). Indicating the flag for a group of geofences equals to indicating flags for every geofence of this group. Note that number of geofences in a group is dynamic (adding to/deleting from groups of geofences), and notifications come considering this dynamics. In the same way you can choose units (they are considered as 'moving geofences'). In this case, indicate radius for these units. Thus, you can get information about unit activity in or out of the area of selected units. Only units to which you have Query reports or messages access are displayed here. To quickly find a necessary geofence or unit, use the dynamic filter. To select all items at once, use the key. In addition, you can enable the option Retrieve intervals to retrieve only segments inside or outside selected geofences or units.Each of described above limitations can be applied either independently or along with other limitations. If the option Retrieve intervals (in the Sensors or Speed sections) is combined with other conditions, then the filtration by other conditions is applied after retrieving the appropriate intervals.The above described filters can be used either independently or in combination with each other. Each filter is applied directly to the indicated time interval, and a generated report shows a value meeting the parameters of all the filters used.

Account Tree (for resource)

This report provides you with information concerning the structure of an account. In other words, a table helps you to understand which object types an account consists of, and also understand the hierarchy among these objects.A table may contain the following columns:
  • Object type: accounts, resources, users, units, unit groups, retranslators, routes.
  • Name: name of an object.
Moreover, to narrow the object type line, it is necessary to indicate the object type which hierarchy you are interested in. To do so, indicate the corresponding flags in report template parameters section.Note that objects' hierarchy will be presented more obviously, if the grouping by object type is chosen in a report template.

Chat

This report unites commands of the kind Send message to driver and replies from the driver. How to carry a chat with a driver…
  • Time: date and time when the message was received.
  • Sender: driver or operator (operator's username in brackets).
  • Text: message text.
  • Count: the number of messages.
  • Notes: an empty column to add your custom comments after printing or exporting the report.

Check Points

Route points refer to check points indicated when creating a route. The table can include:
  • Point name: the name given to this check point while creating it.
  • Real arrival: time when the unit entered this point.
  • Scheduled arrival: time when the unit was supposed to be there according to the schedule.
  • Initial location: location at that time.
  • Real departure: time when the unit left this point.
  • Scheduled departure: time when the unit was supposed to leave the point according to the schedule.
  • Final location: location at that time.
  • Result: Visited (both entrance and exit were detected), Entrance only, Exit only, Skipped.
  • Route: the name of the route to which this check point belongs.
  • Schedule: schedule name.
  • Round: round name.
  • Arrival time deviation: positive value if delayed, negative value if in a hurry in regard to arrival time set in point properties.
  • Departure time deviation: the same for departure time.
  • Presence duration: time spent in the check point.
  • Presence mileage: mileage in the check point.
  • Section duration: time spent to travel from the previous check point to this one.
  • Section mileage: mileage from the previous check point.
  • Count: points count.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Notes: an empty column for your custom comments.

Chronology

This kind of report gives information about all actions and changes in unit state during the indicated period of time. Unlike most of other tables which are dedicated to certain things (parkings, sensors, trips, etc.), this table can gather events of various kinds which allows to estimate movement history in the whole.The following things can be included to the chronology (in the template select necessary):
  • Trips
  • Parkings
  • Stops
  • Engine hours
  • Fillings
  • Thefts
  • Events
  • Drivers
  • Trailers
  • Speedings
  • Connection loss
  • Sensor trigger (enter one or two masks to indicate needed sensors; note that when you enter a mask the sensors are firstly filtered by their type (digital sensors), and then by name)
The following columns can be selected to form the table:
  • Type: trip, parking, stop, engine hours, filling (or reg. filling), theft, event (or violation), driver, connection loss, sensor.
  • Beginning: when the detected activity began.
  • Initial location: unit location at the moment of activity beginning.
  • End: when the detected activity finished.
  • Final location: unit location at the moment of activity end.
  • Duration: how long this activity lasted.
  • Description: for trips and speedings — mileage, for events and violations — the text of notification, for engine hours — duration, for drivers — registered driver name or 'driver unbound', for fuel fillings and thefts — the volume of fuel and sensor name, for sensors — sensor activation/deactivation.
  • Notes — an empty column for your custom comments.
 Note that the system does not calculate state duration for such activity types as fillings and thefts. Therefore, beginning and end time for fillings/thefts are the same in the 'Chronology' table, and duration column displays zero value.

Connection Problems

This kind of report lists periods when no data has been generated and/or send to the system from a unit. The parameters for this report are adjusted in Unit Properties ⇒ Advanced where you set Maximum interval between messages.The following information can be presented in this kind of report:
  • Beginning: date and time when connection loss happened.
  • End: date and time when connection was recovered.  Note that if the time passed between receiving the last message on a report interval and the end of a report interval exceeds a value of a maximum interval between messages, then a connection loss interval will be added to the report. The beginning of this interval corresponds to the time of last message receiving, and the end corresponds to the end of a report interval.
  • Duration: time interval of connection loss.
  • Location: the address where the unit was right before the connection broke.
  • Count: the number of connection gaps detected.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Notes: an empty column for your custom comments.
Additional filtration by driver, trailer, and geofences/units can be applied to this report.

Counter Sensors

This table shows the operation of counter type sensors. In the template, you set the mask (filter) for sensors or choose All sensors. Possible columns are:
  • Sensor: sensor name.
  • Activated: activation time.
  • Deactivated: deactivation time.
  • Duration: operation time.
  • Total time: time from the first activation beginning to the last activation end (useful if grouping by days is enabled).
  • Location: unit location when counter was activated.
  • Mileage: distance traveled for the operation period.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Avg speed: average speed in this period.
  • Max speed: maximum speed in this period.
  • Counter: the value (can be sown with accuracy to two decimal places – see Advanced Settings).
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, drivers, fuel fillings, fuel thefts, and geofences/units.Counter sensor's value can be visualized in the chart that shows counter's operation intervals and its value. More about charts…

Custom Fields

The table Custom fields represents the list of custom fields entered in the corresponding tab of unit properties dialog (see Unit Properties ⇒ Custom Fields).To get this report, you need the access 'View custom fields' and/or 'View admin fields' for a unit/user/unit group. The type of fields is selected in the right part of the report template dialog (all/general/admin fields).Possible columns:
  • Name: custom field name.
  • Value: custom field value.
  • Notes: an empty column for your custom comments.
There is no point to apply additional parameters such as grouping, Total row, and numbering to this kind of report. It does not matter what interval you choose for the report, because only the current fields contained in unit properties can be displayed.To get custom fields for unit group (see Advanced Reports), make sure the option Detalization is enabled. Pay attention that individual fields of each unit will be displayed, and not the fields of the selected unit group. To get the fields of group itself, check the option Group itself in report template.

Digital Sensors

Usually, digital sensors have two states: on/off, activated/deactivated, busy/free and so on. For example, it can be ignition sensor or cargo load sensor. All sensors are configured in Unit Properties ⇒ Sensors.In the report template you can select up to four sensors using masks. Enter sensor's full name or a part of the name using wildcard symbols like asterisk * (replaces several characters) or question mark ? (replaces one symbol). Sensor name cannot contain commas. Check the All sensors check box to automatically select all existing digital sensors. If no sensors are selected or sensors are indicated incorrectly, the table cannot be formed.The table can contain the following columns:
  • Sensor: the name of the sensor under control.
  • On: time when the sensor was activated.
  • Off: time when the sensor was deactivated.
  • Duration: the interval when the sensor was on.
  • Total time: time from the beginning of first activation to the end of last last (useful if grouping by days is enabled).
  • Location: unit location at the moment of activation.
  • Mileage: the distance traveled while the sensor was on.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Initial mileage: mileage counter value at the moment of a sensor activating. If no saving of mileage parameter was made through the reported period, then mileage is counted from 0.
  • Final mileage: mileage counter value at the moment of a sensor deactivating.
  • Avg speed: average speed of movement when the sensor was on
  • Max speed: maximum speed detected in the interval.
  • Activations count: the number of activations (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, driver, trailer, fuel fillings, fuel thefts, and geofences/units.

Eco Driving

The report provides you with the information on how a driver treats the entrusted vehicle. Analyses of driving behaviour could help you to prolong vehicle life, reduce fuel costs, ensure cargo safety, and also understand the reason for any case of emergency.Before generating 'Eco Driving' report it is necessary to indicate settings on the corresponding tab of unit properties dialog.A table may contain the following information:
  • Violation: a type of violation.
  • Beginning: time of violation beginning.
  • Initial location: an address of unit location on the moment of violation beginning.
  • End: time of violation end.
  • Final location: an address of unit location on the moment of a violation end.
  • Value: parameter value during violation.
  • Avg speed: average speed during violation.
  • Max speed: maximum speed during violation.
  • Penalty: penalty value indicated on the 'Eco Driving' tab of unit properties.
  • Rank: received penalty points converted into a grade using 6 point scoring system (can be useful if grouping by years, months, weeks, days, shifts, or trips has been applied ).
  • Mileage: distance covered on a violation or grouping interval.
  • Mileage (adjusted): mileage considering a coefficient set in unit properties ('Advanced' tab).
  • Initial mileage: mileage counter value at the moment of violation beginning. If no saving of mileage parameter was made through the reported period, then mileage is counted from 0.
  • Final mileage: mileage counter value at the moment of violation end.
  • Duration: duration of a violation or grouping interval.
  • Count: number of violations of such type.
  • Driver: name of a driver on this vehicle.
Note that it is easier to analyse the received report, if a grouping option has been applied to a report template. Information received in a report can be grouped on the basis of different criteria, such as time (year, month, week, day, shift), type of violation, and trips.Moreover, in addition to grouping an option of detalization can be applied. This option allows viewing the final level of nesting (date and time) inside of grouping. Though, take into consideration that penalty and rank can be given for the violation taken place on some interval of time (not immediately). That is why on the final level of nesting (date and time) a dash is given in the 'Rank' column, and the 'Penalty' column receives the value indicated on the 'Eco Driving' tab of unit properties.

Penalty Scoring System

The value of penalty points for a particular criterion is indicated on the 'Eco driving' tab of a unit properties dialog. Afterwards the indicated points are used in the report for driving quality evaluation. The calculation of penalty points is made using the special algorithm. The main peculiarities are presented below.Without grouping
  • If no averaging has been used, then the penalty value (earlier indicated on the 'Eco Driving' tab) is displayed opposite to every criterion in the corresponding column. And the 'Total' line (if available) contains the value which corresponds to the sum of points scored for violations.
  • If averaging (by mileage/by time) has been used, then the main difference is that the 'Total' value corresponds to the quotient received as a result of division of the scored penalty points total number by the number of minute intervals (averaging by time), or by the number of kilometer intervals (averaging by mileage) in a trip.
With grouping
  • If no averaging has been used, then a total number of penalty points for the violations of a particular group is displayed opposite to every group in the corresponding column. And the 'Total' line (if available) contains a sum of penalty scores received for all the violations.
  • If averaging (by mileage/by time) has been used, then this averaging is applied to every group of parameters in the report table. Besides, if the 'Total' line is available, then the averaging will be applied to the total number of the scored penalty points. The algorithm of averaging is described above. You can also get acquainted with it on the 'Eco Driving' tab of a unit properties dialog.

Penalty–Rank Conversion

The system provides the algorithm to convert received penalties into a rank:
PenaltyRankLess than 205.920-505.050-1004.0100-2003.0200-5002.0More than 5001.0

Engine Hours

Engine hours report shows working actively of a unit, its productivity and utilization as well as fuel consumption and some more things. The activity and efficiency of work of attached implements can be also analyzed.To generate this report, the unit is supposed to have sensors like ignition, engine efficiency or absolute/relative engine hours sensor.The method of calculating engine hours is set in Unit Properties ⇒ General. In Unit Properties ⇒ Advanced you can also set Daily engine hours rate to calculate utilization and productivity.There are two properties which can be used in engine hours report. They are timeout (to be indicated for a sensor) and maximum interval between messages (to be set for a unit). Both properties are used to cut off invalid intervals during defining of engine hours amount. If values for both timeout and maximum interval between messages are indicated, then the system will use the property with minimum value indicated.Additionally, you can specify engine hours sensor to be used in this report. For this, enter its name mask in a special filter in the reports template. It allows creating a separate table for each engine if there are several.In the table, you can see:
  • Beginning: time when engine hours interval begins.
  • Initial location: location at that moment.
  • End: time when engine hours interval ends.
  • Final location: location at that moment.
  • Engine hours: value of engine hours on the interval. For accurate engine hours calculation, the equipment should send a valid parameter value of an engine sensor. In case of receiving an invalid value, it is necessary to replace sensor with validator using the correct value (for example, 0).
  • 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.
  • Total time: duration of the interval. If grouping by days is enabled, it shows time from the beginning of the first engine hours interval to the end of last interval.
  • Off-time: period of time passed from the end of the previous interval to the beginning of the current one (to be defined beginning from the second interval).
  • In movement: time when the unit had been moving within this interval.
  • Idling: time when the unit was standing with the engine on. Note that idling cannot be detected if an equipment sends no messages containing speed value.
  • Mileage: distance traveled for an interval of engine operation.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Avg speed: average speed for an interval of engine operation.
  • Max speed: maximum speed for an interval of engine operation.
  • Counter: counter sensor value.
  • Initial counter: counter value at the beginning.
  • Finale counter: counter value at the end.
  • Avg engine revs: average rate of engine revolutions.
  • Max engine revs: maximum rate of engine revolutions.
  • Avg temperature: average temperature value registered for an interval of engine operation.
  • Min temperature: minimum temperature value registered for an interval of engine operation.
  • Max temperature: maximum temperature value registered for an interval of engine operation.
  • Initial temperature: temperature value upon the beginning of engine hours operation.
  • Final temperature: temperature value upon the end of engine hours operation.
  • Status: unit status registered during engine hours operation (if there are several, the first one is displayed).
  • Cargo weight: weight of a transported cargo.
  • Driver: driver's name if such was identified.
  • Trailer: trailer's name if any was bound.
  • Movement productivity: percentage ratio of engine hours in movement to engine hours duration.
  • Engine efficiency duration: the duration of attached implements operation (if having engine efficiency sensor).
  • Engine efficiency idling: engine operation time after deduction of efficiency time (total engine hours subtract engine efficiency duration).
  • 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 ImpFCS/AbsFCS/InsFCS/FLS/math/rates: 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 about fuel in reports…
  • 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 consumption in engine hours.
  • Consumed in motion by …: fuel volume used in engine hours while moving.
  • Avg consumption in motion by …: average consumption in engine hours while moving.
  • Consumed in idle run by …: fuel volume used in engine hours during idle running.
  • Avg consumption in idle run by …: average fuel consumption in idling.
  • Avg consumption by … in trips: average fuel consumption in trips.
  • 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.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, driver, trailer, fuel fillings, fuel thefts, and geofences/units.

Events

All events registered by the system (including violations) can be shown in the report on events.There are different ways to add events to unit history:
  1. Triggered notifications which method of delivery is Register event for unit.
  2. Events registered manually by the user in events registrar.
  3. Manipulations with counters (change, store, reset counter value) with the help of corresponding jobs or notifications.
  4. When unit performs a route (if it was chosen to save events on route).
To make a report dedicated just to events of a certain kind, in report template enter a mask to filter events text/description (like *speed*, *traffic*, *filling*, etc.). Only those messages which text corresponds to the given mask will be added to the table.The following columns can be included to this table:
  • Event time: time when the event happened.
  • Time received: time when the server received this data.
  • Event text: notification text or event description.
  • Location: unit location at the moment of an event. If an event is registered manually then unit's location is detected on the basis of messages received upon event registration. The same is true for events registered by storing counters' values in unit properties.
  • Driver: driver's name if identified.
  • Count: the count of events.
  • Notes: an empty column for your custom comments.
In addition, you can use special markers for this report: a green flag means event, a red flag means violation. In the tooltip you can find the detailed information.

Executed Commands

This kind or report gives a list of commands sent to a unit and successfully executed. Possible columns are:
  • Sending time: time when the command was sent to the unit.
  • User: login name of the user who performed the command (hidden if you do not have access rights to some user).
  • Command name: command name as it is written in unit properties.
  • Command type: command type (see the list).
  • Parameter: additional parameter in the command (for messages it is text).
  • Execution time: time when the command was executed.
  • Channel: channel type used to transmit the command (TCP, UDP, Virtual, SMS).
  • Count: the number of sent commands.
  • Notes: an empty column for your custom comments.
This is a list of successfully executed commands. To see all commands sent to the unit regardless their execution, go to the Messages panel.

Fuel Fillings

These reports show where and when a vehicle was filled up. The parameters for this report to be generated are set in Unit Properties ⇒ Fuel Consumption. At that, fillings registered manually are not taken into account.
  • Time: date and time of filling.
  • Location: unit location upon filling (if a filling is registered manually, then unit's location is detected on the basis of messages received upon filling registration).
  • Initial fuel level: fuel level before the filling.
  • Filled: the volume of filled fuel (sensor name may be indicated in brackets).
  • Final fuel level: fuel level after the filling.
  • Registered: the volume of registered fuel.
  • Difference: difference between detected and registered filling volume.
  • Sensor: sensor which detected the filling.
  • Driver: driver's name if one was identified.
  • Trailer: trailer's name if any was bound.
  • Count: the number of fillings.
  • Mileage: distance traveled from the interval start to the filling end.
  • Notes: an empty column for your custom comments.
Intervals filtration by geofences/units, driver, trailer, and filling volume can be additionally applied to this table.You can use special markers for this report to mark places of fillings on the map. Attention! If no fillings were detected, the table is not generated. Furthermore, registered fillings are ignored then, too.

Fuel Thefts

This report is aimed to show all thefts — when, where and how much fuel was stolen. The parameters for this report are set in Unit Properties ⇒ Fuel Consumption.In the table, you can have:
  • Beginning: date and time when the theft began.
  • Initial location: unit location at that moment.
  • Time: moment of the most significant drop of fuel level.
  • Final location: unit location at that moment.
  • Initial fuel level: fuel level before the theft.
  • Initial speed: speed at the beginning.
  • Stolen: stolen fuel volume.
  • Final fuel level: fuel level after the theft.
  • Final speed: speed at the end.
  • Sensor name: sensor which detected fuel theft.
  • Driver: driver's name if any was identified.
  • Trailer: trailer's name if any was bound.
  • Count: the number of thefts.
  • Counter: counter sensor value.
  • Mileage: distance traveled from the interval start to the theft end.
  • Notes: an empty column for your custom comments.
Intervals filtration by geofences/units, driver, trailer, and theft volume can be additionally applied to this table.Special markers can be shown on the map in the places of thefts.

Geofences

This report shows when and how often a unit visited different geofences. In the right part of the template dialog, the list of all geofences is displayed. You can indicate one or more geofences to put them under control of this report, otherwise the report will not be generated. The list of geofences includes only those geofences which belong to the same resource as the report template itself (so, you need to have access to them). Geofences on the list are sorted by name.The following columns can be selected for this table:
  • Geofence: geofence name.
  • Type: polygon, line, circle, unit (if units and not geofences are selected in the report template).
  • Area: total area of the geofence (if the metric system is used, then area will be indicated in hectares).
  • Perimeter: perimeter of the geofence. Perimeter for a line is its length (line thickness is not taken into account).
  • Description: taken from geofence properties.
  • Time in: the time when the unit entered the geofence.
  • Time out: time when the unit left the geofence.
  • Duration in: duration of the visit.
  • Total time: time from the first visit beginning to the last visit end (useful if grouping by days is enabled).
  • Parkings duration: time spent in parkings.
  • Off-time: time between the previous visit and the current one (to be defined beginning from the second geofence visit).
  • Mileage: mileage in this visit.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Counter: value of counter sensor.
  • Initial counter: counter value at the entrance.
  • Finale counter: counter value at the exit.
  • Avg engine revs: average rate of engine revolutions.
  • Max engine revs: maximum rate of engine revolutions.
  • Avg temperature: average temperature value registered inside a geofence.
  • Min temperature: minimum temperature value registered inside a geofence.
  • Max temperature: maximum temperature value registered inside a geofence.
  • Initial temperature: temperature value upon entering a geofence.
  • Final temperature: temperature value upon leaving a geofence.
  • Off-mileage: mileage traveled from previous visit.
  • Off-mileage (adjusted): mileage traveled from previous visit subjected to the coefficient.
  • Avg speed: average speed the unit was moving in the geofence.
  • Max speed: maximum speed detected in that visit.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Visits: the number of visits (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • 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. Details about fuel in reports…
  • 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 by one of the methods mentioned above.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
Instead of geofences, you can choose units in the reports template. Additionally, you indicate radius for these units (in meters). In this case, those units are considered as 'moving geofences', and the activity of the unit selected to generate the report is analyzed in regard to these moving geofences. The access Query reports or messages is required to those units.Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, drivers, trailers, fuel fillings and thefts.Geofences can be displayed on the map. To do so, choose Render geofences option in the report template. Note that monitoring system provides a possibility of detecting geofence visit in case a trip intersects a geofence by any segment of its track. This option can be enabled in the advanced settings of a report template.

GPRS Traffic

To apply this report to a unit, this unit must have registered events of GPRS traffic counter reset or traffic storage should be adjusted in jobs.
  • Time: time when the counter value was registered.
  • Current value: value at the moment of registration.
  • Absolute value: GPRS traffic total size by the moment of registration.
  • Reset: Yes — reset was fulfilled, No — no reset was fulfilled.
  • Notes: empty column for your custom notes.

Logs

The Log table can be generated for any type of an object presented in reports, i.e., for unit, unit group, user, resource, retranslator, or route. Log contains records about changes made in object's properties or its contents. To see the log of a unit, it is no enough to have Query messages or reports access to it; in addition, you need Manage log access.
  • Time: date and time when the change was done (saved).
  • User: name of the user who did it. You can specify user's name mask in report template and so get only changed made by a certain user.
  • Item type: unit, unit group, user, resource, retranslator, or route.
  • Action: description of the change performed.
  • Host: the address of the computer from which the user did the change or it can be 'job' or 'notification' if the action was automatic.
  • Notes: empty column for custom notes.
Log example for a resource:User's log provides with two types of information: changes made by this user and changes made by other users in regard to this user as system object. One more column is available in this report — 'Item name':The log of a unit group has an additional parameter — 'Group itself'. If this checkbox is disabled, the log shows changes made to units in the group (detalization is required in this case):If the option 'Group itself' is enabled, the log shows changes made to this unit group as system object:

Maintenance

This table contains the list of service works (maintenance) done during the indicated period and registered by users who have at least edit access to this unit. The table can be composed of the following columns:
  • Service time: date and time indicated upon a registration.
  • Registration time: date and time when the event was registered.
  • Kind of work: the text from the field 'Kind of work'.
  • Comment: the text from the field 'Description'.
  • Location: location indicated upon a registration.
  • Duration: duration of work.
  • Cost: service cost.
  • Mileage: mileage counter value at the moment of registration.
  • Engine hours: engine hours counter value at the moment of registration.
  • Count: the number of services.
  • Notes: an empty column for your custom comments.
 Attention! Blue rows mean that the place was indicated on the map during the registration.

Messages Tracing

The main target of this report is to facilitate the work with parameters from messages. To do so, parameters are not presented as single data array, but have a particular structure. It means that every parameter is located in its own column.Along with the values of parameters this report contains other columns as well:
  • Time: date and time of sending a message.
  • Speed: speed of a unit.
  • Coordinates: unit's coordinates.
  • Location: address of a unit location.
  • Value: value of a parameter sent in a message.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Notes: an empty column to add your custom comments after printing or exporting the report.
Note that you can view the position of a unit on map by clicking on a link in such columns as 'Time', 'Coordinates', and 'Speed'.

Non-visited Geofences

This report gives the list of geofences that were not visited during the indicated time period. In report template, choose geofences to be checked when generating the table. The list of geofences includes only those geofences that belong to the same account as the report template itself. Geofences on the list are sorted by name. If the list is large, it is convenient to use name mask to quickly find necessary geofences.Let us assume, we have 11 stores (geofences) to be visited every day. We would like to find out whether there are geofences which were ignored within the work week from 1st to 5th of June. To do this, we enable grouping by days (with detalization), select necessary geofences and columns for the table.
  • Geofence: geofence name.
  • Type: geofence type (line, polygon, or circle).
  • Area: total geofence area (if the metric system is used, then area will be indicated in hectares).
  • Perimeter: geofence perimeter.
  • Count: the number of geofences that were skipped.
  • Notes: an empty column for your custom comments.
From this report we see that on 1st of June 'Point 11' and 'Point 7' were ignored, on 4th of June — 'Point 2', and on 5th of June — five geofences. 2nd and 3rd are missed in the list, and it means that all predefined geofences were visited on those days. You can click on geofences' names to move the map to the first point of a geofence.When the table is applied to a unit group, you can find one more parameter in the report template — Consider group as a whole. When the flag is off, a group report is structured in the same way as individual report, and the information is given for each separate unit from the group. When the flag 'Consider group as a whole' is on, report structure is different — you get the list of geofences that were visited by none of the units in the group.

Orders

 Attention! To generate a report, activate the 'Orders' service first.This kind of report shows detailed information concerning orders. A table may contain the following columns:
  • Name: a name of an order.
  • Time from: time from which an order should be delivered (beginning of a delivery interval).
  • Time to: time to which an order should be delivered (end of a delivery interval).
  • Estimated arrival time: approximate time of arriving to a destination point (system calculation).
  • Actual arrival time: actual time of arriving to a destination point.
  • Deviation: difference between actual and estimated arrival time.
  • Estimated mileage: approximate distance to a destination point (system calculation).
  • Actual mileage: actual distance covered to a destination point.
  • Estimated time to point: approximate time for covering distance between previous and current destination points (system calculation).
  • Actual time to point: actual time spent for covering distance between previous and current destination points.
  • Fuel consumed: amount of fuel spent for an order delivery.
  • Status: сorder delivery state (confirmed/rejected/not set).
  • Comment: comment entered upon status indication.
  • Address: delivery point's address.
  • Weight: total weight of goods in the order.
  • Volume: a quantitative value (for example, items) of an order indicated upon its creation.
  • Cost: total cost of goods in the order.
Additional parameters can be chosen for this kind of report. In other words, a report on orders can be generated on the basis of orders of a particular type:
  • All orders — all orders for an indicated time period.
  • Visited — courier's arrival to an address is detected or any status is set.
  • Visited late — orders are visited late or any statuses are set late.
  • Fulfilled — courier's arrival to an address is detected, the 'Confirm' status is set.
  • Rejected — orders with the 'Reject' statuses set.
  • Visited without status — courier's arrival to an address is detected, a status is not set.
  • Non-visited — courier's arrival to an address is not detected.

Parkings

Parkings are estimated according to parameters set in Trip Detection when configuring a unit. To get information as accurate as possible, it is advised that you configure each parameter individually for every piece of equipment.A parking is an interval of time when the following conditions are satisfied:
  1. Insignificant speed. The speed detected must fall in the range from 0 to the Minimum moving speed. When this speed is achieved, unit's behavior is regarded as movement (=trip), if by time and distance it corresponds to trip definition (Minimum trip time and Minimum trip distance parameters). Then the parking finishes. However, if by time or distance the movement does not fall into trip definition, the parking is prolonged.
  2. Sufficient time interval. Insignificant speed must continue not less than Minimum parking time. If this time is not achieved, unit's behaviour is not regarded as parking. It may be regarded as a stop, but only in case there was a zero speed registered.
  3. Insignificant location change. As it has been already noted above, the parking is also an insignificant movement in space, that is a travel which in not longer than Minimum trip distance if by time it not shorter than Minimum parking time.
The following information is presented in this kind of report:
  • Beginning: the time when the parking started.
  • End: the time when the parking ended.
  • Duration: time interval of the parking.
  • Total time: time from the first parking beginning to the last parking end (useful if grouping by days is enabled).
  • Off-time: time interval from the previous parking end to the current parking beginning (to be defined beginning from the second parking).
  • Location: the address where the unit was stationary. If there was an insignificant movement detected, the initial address is used.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Counter: counter sensor values.
  • Initial counter: counter value at the beginning of the parking.
  • Finale counter: counter value at the end of the parking.
  • Avg temperature: average temperature value registered for the parking interval.
  • Min temperature: minimum temperature value registered for the parking interval.
  • Max temperature: maximum temperature value registered for the parking interval.
  • Initial temperature: temperature value in the beginning of the parking interval.
  • Final temperature: temperature value in the end of the parking interval.
  • Avg weight: average weight value registered for the parking interval.
  • Min weight: minimum weight value registered for the parking interval.
  • Max weight: maximum weight value registered for the parking interval.
  • Initial weight: weight value in the beginning of the parking interval.
  • Final weight: weight value in the end of the parking interval.
  • Status: unit status registered during the current parking interval (if there are several, the first one is displayed).
  • Count: the number of parkings (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).

Profile

This kind of report shows profile information indicated on the corresponding tab of unit properties dialog.The following columns can be included in the table:
  • Name: name of an element.
  • Value: indicated value.
  • Notes: an empty column for your custom comments.

Rides

A ride is a travel from one point (called ride beginning) to another (called ride ending). A ride can be done many times in a specified time period. Rides are useful, for example, when controlling cargo transportation form one point to another in several attempts.For the report to be generated, two factors are significant: 1) when a unit leaves the ride beginning geofence; 2) when a unit enters the ride ending geofence. If both of these factors occur, then a ride is completed and can be included in the report. In addition, trip detector is taken into consideration.

Preparing a Ride

To get a report on rides performed, geofences are needed to indicate ride beginning and ride end. The beginning and the end can be the same geofence if the ride starts and ends in one place, for example, if it is necessary to travel ride around some shops and come back to the base.Let us assume that the task is to transport goods from one place to another, and more than one ride will be required for this. To control this process, we create two geofences and then assign them starting and terminal points appropriately in the report template.

Ride Parameters

When you create a template for rides, pay attention on additional parameters to be set.Allow circle ride: Circle ride is a ride that starts and finishes in the same geofence, that is a unit must leave this geofence and return after a while. Such a geofence must have both flags — ride beginning and ride end.Show the rides finished with a stop: This can be used as an additional filter. If activated, it means that the ride ends if a unit stops in the destination geofence. Note that stop is considered to be a unit state in which its speed is less than the minimum moving speed indicated in trip detector. The ride begins upon leaving the departure geofence. If a unit enters a destination geofence (after the ride beginning has been detected), but does not make a stop there, then the ride is continued. The ride ends only upon making a stop in the destination geofence.Starting and terminal points: In this section you choose which geofences and units will be analyzed in the report. The list of geofences includes only those geofences that belong to the same resource as the report template itself. Besides, you can choose units as so-called 'moving geofences'. For them, set radius to outline unit's area. Geofences and units on the lists are sorted by name. If the list is large, it is convenient to use name mask to quickly find necessary items. You can even set ride beginning at unit's area and ride end at an ordinary geofence.Besides, intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensor state, driver, trailer, fuel thefts, fillings, and geofences/units. Note that monitoring system provides a possibility of detecting geofence visit in case a trip intersects a geofence by any segment of its track. This option can be enabled in the advanced settings of a report template.

Report on Rides

The report on rides gives the list of all performed rides. The table can contain the following information:
  • Ride: ride mane consists of starting geofence name and final geofence name hyphenated compound.
  • Ride from: can be used instead of the previous column. Only the departure geofence is indicated here.
  • Ride to: destination geofence.
  • Beginning: date and time when the ride began.
  • End: date and time when the ride ended.
  • Mileage: distance traveled in this ride.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Ride duration: how much time it took to perform the ride.
  • Total time: time from the first ride beginning to the last ride end (useful if grouping by days is enabled).
  • Parkings duration: time spent in parkings.
  • Avg speed: average speed calculated for this ride.
  • Max speed: maximum speed registered during this ride.
  • Driver: driver's name if he was identified.
  • Trailer: trailer's name if any was bound.
  • Counter: counter sensor value (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Initial counter: counter value at the beginning.
  • Finale counter: counter value at the end.
  • Count: the number of rides.
  • Status: unit status registered during the current ride (if there are several, the first one is displayed).
  • Cargo weight: weight of a cargo transported within a trip between geofences.
  • 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 the ride detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the ride.
  • Final fuel level: fuel level at the end of the ride.
  • Max fuel level: maximum fuel level.
  • Min fuel level: minimum fuel level.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.

Rounds (for unit)

If any routes were assigned to unit and events about routes were stored in unit history, a report based on these events can be generated:
  • Route: route name.
  • Schedule: schedule name.
  • Round: round name.
  • Beginning: round beginning time (activation time or entrance in the first check point).
  • Initial location: unit location at the beginning of the route.
  • End: round end time (entrance to the last point).
  • Final location: unit location at the end of the route.
  • Result: Finished (the route was activated successfully, and later on the entrance to the last point was detected) or Not finished (the last point was not visited).
  • Skipped points: the number of check points skipped (on this basis more detailed report can be generated — see Check Points).
  • Duration: time taken to perform the route.
  • Total time: time from the first route beginning to the last route end (useful if grouping by days is enabled).
  • Mileage: distance traveled while performing the route.
  • Avg speed: average speed on the route.
  • Max speed: maximum speed on the route.
  • Count: the number of routes.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Notes: an empty column for your custom comments.
How different route statuses are defined (route beginning, route end, point skipped, point visit, etc.), find here.In addition, in report template, you can indicate masks for geofences and routes. It means you can get in a report not all routes performed by a unit within the indicated period, but only the routes which use a certain geofence or which correspond to the given mask of route name. Both filters can be used simultaneously or separately from each other.Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, driver, trailer, fuel thefts, fillings, and geofences/units.

Rounds (for route)

A special report can be built to show units' performance of a certain route. The following columns can be presented:
  • Beginning: round beginning time (activation time or entrance in the first check point).
  • Last activity: time of latest event concerning this round.
  • Round: round name.
  • Schedule: schedule name.
  • Order: check points order.
  • Unit: name of unit performing the round.
  • Status: Finished (the route was activated successfully, and later on the entrance to the last point was detected) or Not finished (the last point was not visited).
  • Points: total number of check points in the route (on this bases more detailed report can be generated — see Check Points).
  • Skipped: the number of check points skipped.
  • Visited: the number of check points visited.
Report type should be Route.

Sensor Tracing

This table shows sensor values in certain point in time. The table can be exported in MS Excel where you can build any custom charts based on the data provided.The report can include all messages or take a value in a time interval (like take a value every 10 minutes). One or the other alternative is chosen when configuring report template. If tracing interval is indicated, the system will search and display sensor value from the message which is the closest to the necessary point in time.Available columns:
  • Speed: unit's speed from the message from which the value was taken.
  • Coordinates: unit's coordinates from the message.
  • Location: unit's location at the moment of sending the message with the sensor's value.
  • Sensor: sensor name.
  • Time: the time of the message from which the value was taken.
  • Value: the value (numbers only).
  • Formatted value: the value in the indicated units of measurement.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Notes: an empty column for custom notes.
Activate the appropriate checkbox to get a separate column for each sensor. This option is available only in reports for single units, not for unit groups. If you choose this option, the columns 'Values' or/and 'Formatted value' will be generated for each sensor individually (sensor name is given in brackets then). This allows exporting sensor values to MS Excel and eventually building various charts and diagrams on this basis.If you activate the options 'Each sensor in separate column' and 'Skip invalid values' simultaneously, only the lines that have at least one sensor's value will be shown in the generated report. The lines without any sensor's value will not be shown.In addition, you can choose a driver/trailer and geofences/units to be controlled (see intervals filtration for details).

Invalid Values

If a received value is out of range (the bounds are indicated in sensor properties), then there will be a dash (« —– ») in the lines with the sensor's values. To exclude such rows, flag the option Skip invalid values in the report template.The cases when a sensor sends text values (as opposed to numeric) or no values at all are also considered 'invalid'.

SMS Messages (for unit)

This report gives possibility to view all SMS messages received from a unit in a specified period. Here you see date and time when the message was received and the text of the message.
  • Time received: date and time when the data was received by the server.
  • SMS text: message text.
  • Count: the number of messages.
  • Notes: an empty column for your custom comments.

SMS Messages (for resource)

This report provides a possibility to view information about all the SMS messages sent by users of any resource for the indicated period of time. The information may contain the following columns:
  • Time: time of sending a message.
  • User: name of a user sending a message.
  • Phone: a phone number the message is sent to.
  • Parts: number of parts the message consists of.

Speeding

This kind of report shows speed limitation violations. The parameters for this report are set in Unit Properties ⇒ Advanced in the block of speeding. The messages (at least two in succession) containing a speed value greater than set in that parameter will become the basis for this report. If these messages are several in succession, they are united in one speeding event.The following information can be presented in this kind of report:
  • Beginning: date and time when the speed limit was exceeded.
  • Location: device location at that moment.
  • Duration: how long the violation continued.
  • Total time: time from the first speeding beginning to the last speeding end (useful if grouping by days is enabled).
  • Max speed: maximum speed within this period.
  • Speed limit: maximum allowed speed on particular road section or in unit properties.
  • Mileage: the distance traveled with exceeded speed.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Initial mileage: mileage counter value at the moment of speeding beginning. If no saving of mileage parameter was made through the reported period, then mileage is counted from 0.
  • Final mileage: mileage counter value at the moment of speeding interval's end.
  • Avg speed: average speed within the interval.
  • Average excess: average speed excess within the interval.
  • Driver: driver's name (if a driver was identified).
  • Trailer: trailer's name if any was bound.
  • Count: the number of speed violations.
  • Notes: an empty column for your custom comments.

Stops

A stop is one or more consecutive messages with a zero speed. Stops can be registered at lights, intersections, in traffic jams, etc.Stops should be distinguished from parkings. Parameters to detect trips, parkings, and stops are adjusted in the trip detector. If there are several messages in succession, they are united in one stop. If total time of such a stop reaches Minimum parking time, it is registered as a parking (not a stop).The following information is presented in this kind of report:
  • Beginning: the time when the stop started.
  • End: the time when the stop ended.
  • Duration: total time of the stop.
  • Total time: time from the first stop beginning to the last stop end (useful if grouping by days is enabled).
  • Off-time: time from the end of the previous stop to the beginning of this one (to be defined beginning from the second stop).
  • Location: the address where the unit stopped.
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Count: the number of stops.
  • Counter: counter sensor values (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Notes: an empty column for your custom comments.

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 having 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…
  • 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.'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.

Trips

This kind of report shows intervals of movement with indication of time, location, and other parameters such as speed, mileage, fuel, and many others. Intervals of movement (trips) are detected according to parameters set in Trip Detection and adjusted for each unit individually.The following columns can be included in this kind of report:
  • Beginning: date and time when the trip began.
  • Initial location: the address where the device was at the beginning of the trip.
  • End: date and time when the trip ended.
  • Final location: the address where the device was at the end of the trip.
  • Driver: driver's name (if a driver was identified).
  • Trailer: trailer's name if any was bound.
  • Duration: time interval of the trip.
  • Total time: time from the first trip beginning to the last trip end (useful if grouping by days is enabled).
  • Off-time: period of time passed from the end of the previous trip to the beginning of the current one (to be defined beginning from the second trip).
  • Following off-time: period of time passed from the end of a current trip to the beginning of a next one.
  • Engine hours: time of engine hours operation during the trip (you can specify engine hours sensor entering name mask for it in the report template).
  • Mileage: the distance traveled in the whole trip.
  • Mileage (adjusted): mileage considering a coefficient set in unit properties (Advanced tab).
  • Urban mileage: the distance traveled in urban area.
  • Suburban mileage: the distance traveled in suburban area. It is calculated in regard to speed. The urban/suburban speed line is indicated in Unit Properties ⇒ Advanced (Urban speed limit setting).
  • Initial mileage: mileage counter 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 counter 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.
  • Avg speed: average speed within the trip.
  • Max speed: maximum speed registered within this interval.
  • Trips count: the number of trips made.
  • Counter: counter sensor value.
  • Initial counter: counter value at the beginning of the trip.
  • Final counter: counter value at the end of the trip.
  • Avg engine revs: average rate of engine revolutions.
  • Max engine revs: maximum rate of engine revolutions.
  • Avg temperature: average temperature value registered in a trip.
  • Min temperature: minimum temperature value registered in a trip.
  • Max temperature: maximum temperature value registered in a trip.
  • Initial temperature: temperature value in the beginning of a trip.
  • Final temperature: temperature value in the end of a trip.
  • Status: unit status registered during the current trip (if there are several, the first one is displayed).
  • Cargo weight: weight of a cargo transported within a trip.
  • Messages count: the number of messages that formed the trip.
  • 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. Details about fuel in reports…
  • Rates deviation by ImpFCS/AbsFCS/InsFCS/FLS: difference between consumed fuel detected by a sensor and consumption rates. If a number in this cell is negative, it means detected consumption does not exceed the indicated 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 the trip detected by one of the methods mentioned above.
  • Avg consumption in idle run by …: average fuel consumption in the trip during idle run.
  • Avg mileage per unit of fuel by …: average fuel consumption (per one liter/gallon) in the trip detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the trip.
  • Final fuel level: fuel level at the end of the trip.
  • Max fuel level: maximum fuel level in the trip.
  • Min fuel level: minimum fuel level in the trip.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
 Attention! Availability of the columns 'Toll roads mileage' and 'Toll roads cost' is stipulated by a special service. Contact your service provider if you would like to use this functionality.See Data in Reports to discover more about formatting time, mileage, fuel, etc.Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, stops, sensors, driver, fuel fillings, fuel thefts, and geofences/units. For example, you can query trips with a sensor onThe tracks of the trips can be displayed on the map. To make use of this feature, select Tracks on map option in report template.

Unfinished Rides

See the Rides topic to learn how to prepare rides for this report.Unfinished is a ride when a unit left a beginning-ride geofence and after a while entered a beginning-ride geofence again. This can be the same geofence (if circle rides are not allowed) or another one.The structure of the report is the same as for usual rides:
  • Ride: departure and destination geofences.
  • Ride from: can be used instead of the previous column. Only the departure geofence is indicated here.
  • Ride to: destination geofence.
  • Beginning: date and time when the ride began.
  • End: date and time when the ride ended.
  • Mileage: distance traveled in this ride.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Ride duration: how much time it took to perform the ride.
  • Parkings duration: time spent in parkings.
  • Avg speed: average speed calculated for this ride.
  • Max speed: maximum speed registered during this ride.
  • Driver: driver's name if he was identified.
  • Trailer: trailer's name if any was bound.
  • Counter: counter sensor value.
  • Initial counter: counter value at the beginning.
  • Final counter: counter value at the end.
  • Count: the number of rides (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Status: unit status registered during the current ride (if there are several, the first one is displayed).
  • 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. Details about fuel in reports…
  • 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 the ride detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the ride.
  • Final fuel level: fuel level at the end of the ride.
  • Max fuel level: maximum fuel level.
  • Min fuel level: minimum fuel level.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
See Rides to find out more information about additional parameters for Unfinished rides.

Upcoming Maintenance

Upcoming maintenance table contains a list of service works set for a unit, and status of their execution. A table may include the following columns:
  • Service interval: a name of a service work indicated on the 'Service Intervals' tab of a unit properties dialog in the 'Service name' field. The work should be repeatedly done in a particular interval which is also indicated on the 'Service Intervals' tab.
  • State: an overall state of service work execution. In other words, it corresponds to the left or exceeded interval of mileage, engine hours, and days.
  • State by mileage: left or expired mileage interval.
  • State by engine hours: left or expired engine hours interval.
  • State by days: left or expired days interval.
  • Description: information taken from the corresponding field on the 'Service Intervals' tab.
  • Frequency: an interval (mileage, engine hours, or days) showing how often a vehicle maintenance should be executed.
  • Notes: an empty column for your custom comments.
 Note that there is no need in indicating time interval for the 'Upcoming maintenance' report generation, because this table provides you with the information on all the indicated service works regardless to the time period.Moreover, an individual parameters of grouping (without any connection to time intervals) are used in the 'Upcoming maintenance' table. Data can be grouped on the basis of state (planned/expired maintenance), service interval, or unit (for reports on unit groups).

Utilization Cost

The table on utilization costs unites two kinds of expenses: maintenance and fillings. Both of these things have their own detailed tables (see Maintenance and Fuel Fillings). This table is designed to show running costs. Note that only fillings registered manually in a special Events Registrar get here (no fillings detected by a fuel sensor).The table can be composed of the following columns:
  • Time: date and time that were indicated during the registration.
  • Registration time: date and time when the event was registered.
  • Expense item: maintenance or filling.
  • Description: custom description entered when registering.
  • Location: location indicated while registering (together with comments entered manually).
  • Cost: service or filling cost.
  • Count: the number of services and/or fillings.
  • Notes: an empty column for your custom comments.
Blue rows mean that the place was indicated on the map during the registration.

Violations

Violations are particular case of events. The report on violations gives the list of violations detected and registered in unit history.Violations are:
  1. Triggered notifications which method of delivery is Register as violation;
  2. Manually registered custom events if they have the Violation flag.
To make a report dedicated just to violations of a certain kind, in report template enter a mask to filter violations text/description (like *speed*, *accident*, *temperature*, etc.). Only those messages which text corresponds to the given mask will be added to the table.The following information can be presented in this kind of report:
  • Violation time: time when the violation happened.
  • Time received: time when the server received this data.
  • Violation text: notification text or event description.
  • Location: unit location at that moment.
  • Driver: driver's name if identified.
  • Count: the number of violations.
  • Notes: an empty column for your custom comments.
In addition, you can use special markers for this report.

Visited Streets

This report shows which streets were visited and when. Highways, roads, and other places with available addresses are also considered as streets in this report.The following columns can be presented in this kind of report:
  • Street: street, roads, highway, etc. name.
  • Initial location: place where the first messages from this street was received. It can be the same as the previous cell or more detailed (for example, it can additionally contain house number).
  • Beginning: time when the unit started moving along this street.
  • End: time when the unit left the street.
  • Duration: total time the unit was there.
  • Mileage: distance that was traveled by the unit while moving through this street.
  • Mileage (adjusted): mileage subject to the coefficient set in advanced unit properties. About mileage in reports…
  • Avg speed: average speed while moving along this street.
  • Max speed: maximum speed detected while moving along this street. About speed in reports…
  • Streets count: the number of performed visits (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Notes: an empty column for your custom comments.
When clicking on a green cell in the table, the map is moved in such a way to display a point where the unit entered or left the indicated street, or reached the maximum speed, and this place is highlighted by a special marker.Sometimes there can be gaps in cells. It may happen when only one message from a place was received in succession. In such cases, just the name of the street and arrival time are given.Intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, fuel fillings and thefts. For example, you can get streets where a sensor was on or the streets where a sensor was off.

Charts

Some reports give information in the form of a chart. For instance, it can be a chart showing how a unit speed varied with time or a chart showing dependence of fuel consumption on speed, and many other kinds of charts.To receive charts in reports you need to have corresponding equipment (sensors) properly installed and configured (except for some charts like Speed or Altitude which do not require any special sensors). How to create and configure sensors, read in the section Sensors.To add a char to a report template, click the Add Chart button in the template properties dialog.  A chart cannot be included to a report if report type is Unit group.Enter a name for a chart or live default Chart (the same for all charts).

Regular Charts

There are several types of charts. First of all, this is Regular type. Their X axis always presents time scale, and you choose data for Y axis:
  • Speed
  • Altitude
  • Engine operation
  • Voltage
  • Temperature
  • Engine revs
  • Cargo weight
  • Counter sensor
  • Custom sensors
  • Custom digital sensors
  • Absolute mileage
  • Mileage in trips
  • Instant mileage
  • Fuel level (no filtration is applied)
  • Processed fuel level (filtration is applied)
  • Fuel consumption by ImpFCS
  • Fuel consumption by AbsFCS
  • Fuel consumption by InsFCS
  • Fuel consumption by FLS
  • Fuel consumption by math
  • Fuel consumption by rates
The names of these items are editable. However, when building a curve for a sensor, it will borrow sensor name.Select data set for the chart checking necessary items in the list. You can select two items, then the chart will contain two curves, for example, speed and engine revs. You can select even more items but note that only two variables can exist in one chart in addition to time. It means if Y axis presents speed scale at the left and temperature scale at the right, there is no place for engine revs. But if Y axis presents speed scale at the left and consumption by ImpFCS at the right, it is still possible to add consumption by AbsFLS and other methods because all they are measured in the same metrics and will use Y right scale.In the picture below there a speed chart united with fuel level chart. To receive such a chart, it is needed to set Regular chart type and select Speed and Fuel level for data set.If there are more than one curve in the chart, they are displayed in different colors. At the top of the chart you can see the names of all lines as they are indicated in the report template or sensors names. In addition, the metrics are indicated for all axes.Fuel Level Charts: Fuel level chart represents 'raw' data. On the contrary, Processed fuel level chart shows filtered data.Mileage Charts: Four kinds of mileage chart can be created: absolute mileage, mileage in trips, instant mileage, and instant mileage smoothed. The first two show how mileage changed (increased) with time. Absolute mileage chart is built on the bases of all messages. That means any inaccuracy and outlying data affect the resulting chart. Mileage in trips chart considers trip detector that is chows mileage in trips only. Below you see the chart with curves: absolute mileage (blue) and mileage in trips (orange).Instant mileage represents data in the form 'mileage from the previous message to the current one' that is the distance between two adjacent messages. This kind of chart can be useful to detect excessive mileage during connection loss, or to detect made-up additions to the mileage.

Chart Parameters

Sensors Masks

In the parameters block (right part of the dialog) you can indicate particular sensors on the basis of which the corresponding charts will be built. This selection does not affect such charts as 'Speed', 'Altitude', 'Fuel consumption by math' and 'Fuel consumption by rates' because these charts can be built regardless to unit sensors availability.To indicate the necessary sensors, enter the corresponding masks. You can indicate full sensor name or its part using wildcard symbols like asterisk * (replaces any number of characters) or question sign ? (replaces one character). A sensor name cannot contain comma. If no masks are indicated, then the system automatically defines sensors of a required type to build charts.

Markers

In this section you can choose markers to visualize corresponding events on a chart. The same markers are used on the map.

Background

The following intervals of events can be used as a chart background: stops, parkings, trips, connection losses, and work of engine hours. Using these backgrounds you can correlate a chart value and an interval to which it corresponds. Different colors can be chosen for a background (click the color box).  Note that backgrounds are opaque and they have a priority of visualization. In other words, an upper interval covers the bottom ones. To change a priority, drag and drop a corresponding event interval.

Split Sensors

If there are several sensors of the same type and a chart of the same type is created, the curves for all sensors will appear in one chart. To split them, choose the appropriate option Split sensors. Then an individual chart will be built for each sensor. For example, there is a unit with two voltage sensors – external voltage and internal voltage. If creating a voltage chart for this unit, we can get one chart with two curves on it or two chart with one curve on each (if Split sensors option is enabled).If several data is selected for the chart and for each several sensors exist, the upper one will be split. Let us assume that a unit has two voltage sensors and two temperature sensors, and you are building a voltage/temperature chart for it. If Split sensors option is off, you will get one chart with four curves in it. If Split sensors option is on, you will get two charts with three curves on each: one chart will contain the first voltage sensor and both temperature sensors, and another one will contain the second voltage sensor and again two temperature sensors.

Smoothing

Almost all regular charts can be presented in two forms: raw and smoothed. Raw charts are drawn from one message to another in a linear way and have angular look. Smoothed charts look more streamlined. The smoothing algorithm is the same for all chart kinds.Below is an example where the orange line displays a raw speed chart, and the blue line displays a smoothed speed chart.

Special Charts

Along with the regular charts, you can generate the following charts:
  • Processed fuel level
  • Speed/Fuel Consumption by…
A data set for these charts is fixed. Though, you can adjust chart parameters, for example, indicate sensors' masks or split sensors.

Processed Fuel Level

Processed fuel level chart shows the values which are used while calculating fuel level, fillings and thefts in tables.The chart shows how fuel level changes in time or depending on mileage. The caption of the tab will be correspondingly Time/Fuel level or Mileage/Fuel level. The chart Time/Fuel level is built only if in unit configuration the option Time-based fuel level sensors consumption is on. In all other cases, the chart Mileage/Fuel level is built. Besides, the data is processed according to filtration level set on the Fuel Consumption tab (the option Filter fuel level sensors values) or in sensor properties.Below are two fuel level charts: the first one is processed (time-based FLS is on, filtration is on, filtration level is 25), and the second one is not processed.A special chart Processed fuel level should be distinguished from two similar regular charts:Regular chart Fuel level represents the raw data (no filtration is applied). The flag Time-based fuel level sensors consumption does not affects the chart. Regular chart Processed fuel level represents dependence of filtered and smoothed on the basis of mileage data from time. These regular charts can represent data only in the form Time/Fuel level. Besides, it is possible to overlay other charts, such as voltage chart, for example. Special charts cannot be combined with other charts.

Speed/Fuel Consumption Chart

This chart shows dependence of average fuel consumption on speed. The data for these charts can be taken from fuel consumption sensors of different types (as impulse, absolute, instant) or fuel level sensor, or predefined consumption by math or rates. The appropriate calculation methods must be indicated in unit properties on the Fuel Consumption tab.For example, to create this chart, a unit with instant fuel consumption sensor (InsFCS) was used.

Chart Management

A handy interface provides enough tools to work with charts. You can adjust a needed zoom, move along the chart left and right, get a precise sensor value in the indicated point, etc.Above the chart, there is a toolkit with useful buttons:
Scroll right/leftTo navigate a chart along the X axis, use the corresponding arrow-shaped buttons. They are useful if the current zoom level does not hold the whole chart. The chart shifts right and left by a quarter of its visible part.Y axis auto zoomUse this button to scale the Y axis. If the button is pressed and you are changing chart zoom along the X axis, then the Y scale is recalculated automatically in such a way to use the maximum of chart space. If the button is released, the Y scale always stays unchanged.Zoom in/outThe buttons to scale a chart along the X axis make visible area of the chart twice as wide or twice as narrow in regard to the current position. At that, the center of the chart stays in its place.Custom zoomWhen the custom zoom is activated, a mouse cursor is displayed as a blue vertical line. Holding the left mouse button you can select a needed area of a chart to increase it. You can repeat the operation several times.ResetTo see the chart in its initial position and scale, press the Reset button.
Pay attention that there is one more parameter which affects chart zoom. This option is set in report template and called Count from zero. If it is on, the Y axis will always have zero despite of the position of the Y axis auto zoom button.Chart tracingTo get a sensor value in a given point, activate Trace chart values option. A mouse cursor is then displayed as a red vertical line. Place it over any place on the chart and get detailed information at that point (as in the picture above). Three sections can be contained in the popup tooltip:
  1. Time where the cursor is placed and all values of the curves for this point.
  2. Message nearest to this point: time (can slightly differ from the time of the cursor!), location, speed, coordinates, altitude.
  3. Values of all visible sensors at this point.
If the X axis shows time, you can click on any place of the chart to move to the corresponding location on the map.Transfer from chart to messagesYou can move to unit's messages straight from an online chart to analyze initial data. To do this, press the 'Transfer to messages' button in the toolkit. Then, click on any place of the chart to load messages for the reported period with focus on clicked point. Other functionality is the same as with tables.When switching between charts, the button is released automatically.

Chart Legend

A chart legend can be found in the work area. The legend contains several sections of information on the chosen charts and their parameters. Using the legend you can choose parameters to be shown on a chart (all of them are shown by default). To enable/disable any parameter, click it in the legend.

Map Output

In the Reports panel, the map can be scaled and moved in the same way as everywhere else: zoom, move, apply tools, change the map source, etc. Even being in the Reports panel you can still track your units. Besides, some specific map options can be applied exactly to reports.The map with tracks can be also exported to HTML or PDF file together with report text. To include the map to the exported report, in the Export dialog check the box Attach map.In such reports as 'Trips', 'Parkings', 'Fuel fillings' and many others which contain information about unit location, this location can be easily shown on the map. To move to a place where something happened, click on a green row of the table. The map will be centered on the place and a marker will appear there. A similar feature is available in the regular charts (where the X axis displays time): when using the trace tool, you move to the requested massage on the map.Some elements can be drawn on the map as a part of the report. They can be selected in the Map output section of the report template dialog. These can be routes traveled by unit, created geofences, as well as special markers in the form of small icons which can be put in the places of events, fillings, thefts, speedings, etc.All graphical elements are shown for the current report. If generating a new report, all tracks and markers from the previous report will be erased and replaced by new.When switching to other panels, all graphical elements from the current online report as well as map position and zoom remain on the map. To remove them, return to the Reports panel and push the Clear button. Alternatively, the graphics of any panel can be hidden or displayed again. To do this, check the corresponding boxes in the horizontal menu.

Tracks on Map

The routes traveled by a unit in a chosen period of time can be shown on the map. To do this, in advanced settings a report template dialog select the corresponding options — Trips routes or All messages on map. These options are similar but a bit different. In case of Trip routes, only the intervals considered as trips (according to Trip Detector) will be displayed as tracks. In case of All messages on map, all messages with valid coordinates will be converted into a track. If in unit history there are intervals where the connection has been lost (no messages for a long time) or coordinates miss in messages, such intervals are displayed with a dashed line.By default the routes are drawn with blue color. However, you can choose another color or even have many-colored tracks according to speed or sensor state. The set of colors to be used in tracks is defined in Unit Advanced Properties).Besides, to get information about track points, hover mouse cursor over and see information in a tooltip (time, speed, coordinates, altitude, sensor values). Note that messages are searched in the radius of 50 pixels to the cursor.If tracks or all messages are on, then in such tables as Trips, Rides, Engine hours, Speedings will be supplied with an additional first column containing the icon of the binoculars. When clicking on the icon, the map is centered at a certain segment of the track, and this segment is highlighted by a thick red line on the map.Tracks can be rendered for units groups, too (see Advanced Reports). It is reasonable to assign different colors for units in group to differentiate them on the map. However note that the number of simultaneously drawn messages can be limited by your service provider.

Geofences on Map

Created geofences can be a part of a report. They will be displayed on the map if you check the corresponding box — Render geofences — in the section 'Map' of the report template.Geofences are displayed with their captions and images or icons (if you have chosen any). The color and the font size of the caption is taken from their properties. Apart from that, additional options can be applied to geofences:
  • Group icons: The geofences that overlap each other can be replaced by one conditional item, and its tooltip will contain the detailed information. The same can be applied to markers.
  • Consider geofence visibility scale: By default, all the geofences are rendered on the map. However, they can be seen or hidden according to their visibility parameter set in the properties.
 Note. Geofences are taken only from the same account as the report template itself.

Markers

Most kinds of reports can have additional information visualized on the map with the help of special markers. To get these markers in a report, select necessary markers in a report template.The table below presents all possible markers and their icons. Note. When enabling event markers, in addition to event markers you will get violation markers because violation is a special case of event.Markers appear on the map after report is generated. If you see no markers, it means there is no events of the indicated type or the current map scale is not enough (try to zoom in).When hover the mouse cursor over a marker, in a tooltip you see additional information: for stops and parkings — starting time and duration, for events and violations — time and notification text, for fillings and thefts — time and fuel volume, for speedings — starting time, speed limitation as it is defines in unit properties, how much the speed is exceeded, and duration of this speeding.Moreover, markers as well as geofences can be grouped in case they overlap each other — indicate the Group icons option in report template for it. In case of markers grouping, a number of elements included in a group is indicated. More detailed information about what happened in that place will be available in the tooltip. However, if there are more than 100 grouped markers, only their names appear in the tooltip, without detailed information.You can enable Marker numbering option in report template. In this case, each marker will have its sequence number which is indicated below the marker in red color. Numbers are assigned chronologically, and each marker type has its own numeration.

Unit Last Location

The last location of the unit can be displayed on the map. To enable this feature, select the Unit last location checkbox in map output settings of report template. Last location does not depend on the reported interval, it is taken from the latest message received from the unit. Units are displayed on the map by their icons or by motion state signs (depending on User Settings. In the popup tooltip you will find time when message received, speed at that point, altitude, and the values of mileage and engine hours counters.

Statistics

Statistics is a table consisting of two columns where the first one contains the parameters you have chosen, and the second one shows their values.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.Statistics
  • 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…
Counter sensors
  • Total counter: the sum of values of all sensors of counter type.
Eco driving
  • Penalties: overall penalty for Eco Driving.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
Engine hours
  • 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.
  • 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
  • Events count: the number of events registered.
Executed commands
  • Executed commands: the number of commands sent to unit.
Fuel fillings
  • 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.
Fuel thefts
  • Total fuel stolen: the total volume of stolen fuel.
  • Total thefts: the number of thefts detected within the reporting period.
Images
  • 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.
Maintenance
  • Total maintenance duration: time spent for servicing.
  • Total maintenance cost: total cost of all maintenance works.
  • Services count: the number of services performed.
Orders
  • 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
Parkings
  • 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.
Rides
  • Rides count: the number of accomplished rides.
SMS messages
  • SMS messages: the number of SMS messages received from unit.
Stops
  • Stops count: the number of stops for the reporting period.
Trips
  • 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 counter 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 counter 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' .
Unfinished rides
  • Unfinished rides count: the number of unfinished rides.
Unit latest dataNote 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.Utilization cost
  • 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.
Video
  • List of video files received from a unit.
Violations
  • Violations count: the number of violations registered within the reporting period.
Visited streets
  • Streets count: the number of found visits of streets.

Advanced Reports

Advanced reports are reports on unit groups and users (except the Log table), all tables for drivers, trailers, and their groups, as well as report on logins for resource.These report types are defined when creating a template.

Reports on Unit Groups

Data from several units can be gathered in one report if these units from a unit group. To get a report on several units, select the Unit group type for the report template.The functionality of these reports is very similar to reports on separate units but has a number of peculiarities and restrictions.In Unit group reports the following features are available:
  • Any tables;
  • Graphical elements on map: geofences, any markers, unit last location icons, tracks and all messages on map;
  • Some graphs in Statistics: 'Report', 'Group', 'Interval beginning', 'Interval end', 'Report execution time';
  • Advanced options: U.S. measurements, address format, etc.
All tables available for units are available for unit groups, too. Besides, the table Unit latest data is available for unit groups only.In Unit group reports the following features are not available:
  • Charts;
  • Most of statistics excluding those mentioned above.
Note that if in 'Total' line of unit group report you would like to receive correct data on the initial or final fuel levels, then in report template such parameter as 'Unit' should occupy the main position (drag to the top) in the grouping list.

Tables for Unit Groups

There are some peculiarities in configuring tables for unit groups. The first column of the table shows the list of all units included into a selected group (alphabetical order). This column is put in front of all the other ones indicated in a template. The 'Count' column (if included in a report template) shows the number of events registered for the reporting period of a given unit.Below is an example of a table on parkings for a group of 5 units. The table provides us with the following data: beginning of the first parking, end of the last parking, summarized duration of all parkings for the reported period. Every line is dedicated to a single unit.If the option of detalization is applied, the nesting level appears. That means you can expand the contents of a basic line ('+' at the beginning of a line, or corresponding number in the heading of the column) and see a detailed list of events for a given unit. The number of hidden lines corresponds to the number in the 'Count' column.In addition to detalization, you can apply the grouping by years/months/weeks/days/shifts. In this case table data is grouped by a chosen time interval. If several grouping intervals are chosen, then they will be arranged in several levels of nesting. In case with groupings a detalization is situated on the final level of nesting, and still shows a detailed list of events for a given unit.To expand enclosed information, click on the plus-shaped button at the beginning of each line. It is also possible to expand the nested levels by clicking the corresponding numbers-buttons in the heading of the nesting column. To hide all the expanded lines, click on the button '1'.If there is no data for the given unit, all the cells except for the name will contain only dashes. In some cases it is not convenient, then you can disable such uninformative lines. To do so, enable the option Skip empty rows in the report template.Unit Latest DataThis kind of table available only for unit groups. As for separate units, this information is available in statistics. The table presents last location and counters values known.The following columns can be selected to form the table:
  • Unit: unit name.
  • Last message: time when the latest message form the unit was received.
  • Last coordinates: time when the latest message with valid coordinates was received (not always coincides with the previous column).
  • Location: address or coordinates of the last location.
  • Speed: speed according to the last message.
  • Mileage: mileage counter value.
  • Engine hours: engine hours counter value.
  • Traffic: GPRS traffic counter value.
  • Driver: name of driver (if any detected).
  • Trailer: name of trailer (if any detected).
  • Notes: an empty column for your custom comments.
By default, the latest information refers to report execution time. However, it can be bound to the end of reporting interval. To do this, enable the Consider report interval checkbox in the template.Apart from that, filtration by geofences/units can be used for this report. This allows to quickly find units which are situated in a certain place or close to other units.Last location can be visualized on the map by units icons — activate the option Unit last location in the report template.

Reports on Users

Several tables and charts can be generated for users. The Log is highly standard and was described above.In the Statistics the following fields are available: report template name, user name, reporting interval (beginning/end), report execution time, total time spent in the system, and logins count.

Logins Table

This kind of table shows user activity: logins to different services. The table can contain the following columns:
  • Login time: time when user logged in a service.
  • Logout time: time when user exited the service.
  • Duration: time interval user was online on the service.
  • Host: the address of the computer from which user logged in.
  • Site: the name of service where user logged in.
  • Count: the number of logins.
  • Notes: empty column for custom notes.
The same parameters as for all tables can be applied to user logins table: grouping, detalization, row numbering, total row, and time limitations. In the example below you can see user logins table with grouping by days, detalization, numbering, and total row.One report can display logins of more than one user. However, in this case, report type should be not User but Resource. All users belonging to an account, for which such report is executed, will get into the report. Example:

Charts Applied to Users

Two kinds of charts can be attached to the report on user logins: Logins/Hours and Logins/Days of week. To get these charts, in report template push the button Add Chart and choose the type in the dropdown list.Logins/Hours chart shows how user's activity in different hours of the day:

Reports on Drivers

The following types of tables can be applied to drivers:
  • Bindings,
  • Custom fields,
  • Driver activity,
  • Eco driving,
  • Infringements,
  • Orders,
  • SMS messages.
To generate reports on drivers or driver groups, the proper access to the resource where those drivers or groups belong is required — 'Query reports or messages' flag.

Bindings

A table of Bindings can be built for each driver. This report shows which units the selected driver was working on, for how long, how much fuel was consumed, distance traveled etc.The following columns can be included in this kind of report:
  • Beginning: date and time when the driver was assigned.
  • Initial location: the address (if available) at that moment.
  • End: date and time when the driver was reset.
  • Final location: the address (if available) at that moment.
  • Duration: duration of a working shift.
  • Total time: time from the first trip beginning to the last trip end (useful if grouping by days is enabled).
  • Engine hours: total amount of engine hours for a working interval of a bound driver.
  • Engine hours in movement: an amount of engine hours for an interval of unit's movement.
  • Engine hours in idle run: an amount of engine hours for an interval of unit's idling.
  • Mileage: the distance traveled within the period.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties (Advanced tab).
  • Urban mileage: the distance traveled in urban area.
  • Suburban mileage: the distance traveled in suburban area. It is calculated in regard to speed. The urban/suburban speed line is indicated in Unit Properties ⇒ Advanced (Urban speed limit setting).
  • Avg speed: average speed within the interval.
  • Max speed: maximum speed registered within this working shift.
  • Counter: counter sensor value.
  • Status: unit status registered during the interval (if there are several, the first one is displayed).
  • Violations: the number of violations occurred.
  • Count: the number of bindings found.
  • 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 the trip detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the working shift.
  • Final fuel level: fuel level at the end of the working shift.
  • Penalties: penalties calculated for adjusted Eco Driving criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.
When creating/editing a report template, you can also choose units to be under control of this report. Their list is on the right of the columns list. If no units are selected, it means that all units will be considered.The report is designed in such a way that the first column is the list of units on which the driver was working. It is recommended to apply the detalization option to this table to get a possibility to expand any unit and see more detailed information about all working shifts on it.

Custom Fields

The table Custom fields represents the list of custom fields entered in the corresponding tab of driver's properties. Possible columns:
  • Name: custom field name.
  • Value: custom field value.
  • Notes: an empty column for your custom comments.

Driver Activity

Driver activity table shows such information as type of driver's action, crew size of a vehicle, tachograph card state. It may include the following columns:
  • Beginning: date and time of message coming.
  • Card: digital tachograph card state (inserted/not inserted).
  • Activity: type of driver's activity (rest, work, driving, available, not available).
  • Driving: driving time interval.
  • Work: active working hours (time spent by a driver for vehicle repairing, fuel filling, etc.).
  • Availability: passive working hours (time spent by a second driver in the moving vehicle).
  • Rest: driver's rest time interval (vehicle is stopped, driver takes rest in a special place or equipped cabin).
  • Overall work: time spent by a driver working, driving, or being available.
  • Slot: slot for digital tachograph card (Driver or Co-driver).
  • Status: vehicle crew size (single/crew).
  • Daily mileage: distance covered by an attached driver during the day (24 hours).
 Note that creating this report template, it is necessary to choose driver activity source (DDD files or online data) in the table parameters block.

Eco Driving

This reports is the same as report for a unit.

Infringements

This report shows information on the violation of labor routine by the driver. It may include the following columns:
  • Time: date and time of violation recording.
  • Infringement: type of driver's activity the conditions of which have been violated.
  • Description: short description of the infringement.
  • Seriousness: the extent of the infringement.
 Note that creating this report template, it is necessary to choose driver activity source (DDD files or online data) in the table parameters block.

Orders

This reports is the same as report for a unit.

SMS Messages

This report shows chat of a dispatcher with a driver via SMS messages. A dispatcher (operator) can send messages to a driver from WBC Fleet interface through a special SMS window. A driver sends messages from his mobile phone. This mobile phone number must be indicated in driver's properties.The following columns can be included in the table:
  • Time: date and time when message came.
  • Type: message type: sent (a message that was sent by a dispatcher) or received (a message that was received from a driver).
  • Text: text of the message.
  • Phone: driver's phone number.
  • Modem phone: phone number of the modem that sent/received SMS.

Additional Possibilities

In addition, you can query statistics for such reports, which can include the following fields: report template name, driver name, report interval (beginning and end), and report generation time.Tracks of driver's movements can be built on the map.Most tables can be generated for a group of drivers.:!:Note. The Total row cannot be used in reports on driver and trailer groups.

Reports on Trailers

To generate reports on trailers or trailer groups, the proper access to the resource where those trailers or groups belong is required — 'Query reports or messages' flag.Two tables are possible for trailers:
  • Bindings
  • Custom Fields
  • Bindings
This table shows working intervals if the chosen trailer if it was bound to units. It comes along with information on fuel consumed, distance traveled etc. Parameters and possible columns for this table are the same as in the similar table for drivers (with the exception that the column 'Violations' is absent). The Bindings table can be also generated for trailer groups — it gives possibility to build complicated four-level reports (trailers –> units –> dates/weeks/months –> single bindings).

Custom Fields

This table represents the list of custom fields created in trailer properties. It is not available for trailer groups.

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.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'. However, duration larger than 24 hours can be not combined into days. So, there will be “132:34:56” instead of “5 days 12:34:56”. To disable days and leave only hours, go to report template properties dialog and set the Duration format option to Hours and minutes. This parameter affects not only time formatting in the cells but in the Total row as well.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 YYYY:MM:DD format (for example, 2015-07-30);
  • Grouping by shifts shows the corresponding shifts (for example, shift 1).
 Attention! To receive reliable data for time/duration, it is important to correctly indicate the time zone and DST options in User Settings.

Mileage

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 counter value at the beginning of the interval (trip, street visit, sensor operation, etc.).
  • Final mileage: mileage counter 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.

Speed

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.

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:
  • install fuel sensors on your unit;
  • properly configure the sensors in unit properties;
  • on the Fuel Consumption select calculation methods corresponding to these sensors.
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 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 additional options 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.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/fuel/counters with accuracy to two decimal places in report template.If the U.S. measurements 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).

Data preparation

 Note: Ellipsis (…) substitutes 'Unit properties → Fuel consumption' is option paths.Among important options the next list should be mentioned:
  • Option: Ignore the messages after the start of motion;
  • Option: Merge same name sensors;
  • Special Case: Mileage-based calculation VS Time-based calculation.
Ignore the messages after the start of motion
... → 'Fuel fillings/thefts detection' block → 'Ignore the messages after the start of motion, sec'
This option allows messages being ignored after motion has started for a period of time in seconds. Messages which are frontier ones to ignored time period are joined by drawn line.Here is whole algorithm more precisely:
  1. all starts with start motion message, it is used to define the amount of messages being ignored;
  2. this message is regarded as left-frontier message;
  3. then we add seconds set in the option to this message timestamp to get end moment of ignored time period;
  4. all FLS messages being within this time period are ignored while processing;
  5. the first message which comes after ignored period (p.3), is called right-frontier message;
  6. Both left- and right-frontier messages are joined by line being drawn (instead taking ignored messages into account while building graph).
All processed graphs have the option for such correction (except for the Regular graphs, where data is raw).This is the graph with no ignoring:This graph is being ignore option 10 set:

Merge same name sensors

... → 'General sensors parameters' block → 'Merge same name sensors (fuel level)'
... → 'General sensors parameters' block → 'Merge same name sensors (fuel consumption)'
In case of desire to group an amount of sensors into one result please use the next approach: set the same sensor type ('Unit properties'→ 'Sensors' → Choose desired sensor → 'Properties', 'Sensor type' field); set the same sensor name (the same menu, “Name” field);The table below shows 'option ↔ sensor type' matching:
OptionSensor type'Merge same name sensors (fuel level)'- fuel level sensor; — impulse fuel level sensor'Merge same name sensors (fuel consumption)'— impulse fuel consumption sensor; — absolute fuel consumption sensor; — instant fuel consumption sensor
 Note. You can group several sensor types (up to all types you got in the list).

Mileage-based calculation VS Time-based calculation

... → 'Fuel fillings/thefts detection' block → 'Time-based calculation of fillings'
... → 'Fuel fillings/thefts detection' block → 'Time-based calculation of thefts'
... → 'Fuel level sensors' block → 'Time-based calculation of fuel consumption'
Convergence of data (i.e., when sum of interval results equals to whole interval result) is guaranteed when all mentioned options activated/deactivated:
  1. time-based calculation of fillings;
  2. time-based calculation of thefts;
  3. time-based calculation of fuel consumption.
While 'Time-based calculation' (all three options) switched on the x-axis is time:
  • fuel consumption/idling looks like slowly descending curve on graph;
  • thefts/fillings — quick falling of fuel level on a small period of time (theft/filling processing time).
While 'Time-based calculation' switched off (data is calculated as mileage-based) the x-axis is mileage:
  • fuel consumption in motion looks like slowly descending curve;
  • idling – because mileage is not incremented, should be seen as vertical falling of fuel level;
  • thefts/fillings on stops — because mileage is not incremented, should be seen as vertical rising of fuel level.

Filtration

 Note: Ellipsis (…) substitutes 'Unit properties → Fuel consumption' is option paths.Two options are connected with filtering:
  • Option: 'Filter fuel level sensors values';
  • Option: 'Filtration level (0..255)'.

Filtration enabling and filtration level setting

... → 'Fuel level sensors' block → 'Filter fuel level sensors values';
... → 'Fuel level sensors' block → 'Filtration level (0..255)'.
To use filtration be sure to:
  1. check 'Fuel level sensors' area ('Unit properties → Fuel consumption');
  2. check 'Filter fuel level sensors values';
  3. set non-zero value for 'Filtration level (0…255)'.
It is OK to use filtration when wrong messages appeared, i.e., with unreasonably bigger/smaller values. During filtering median smoothing is used. Attention!
  • If value 0 is set in 'Filtration level' option, a user must be aware of that filtration is not disabled this way, but its minimal level is used instead (three messages being filtered, because that is the minimum input required for median smoothing).
  • Any number from 1 to 255 being set in 'Filtration level' is multiplied by 5. The result number is the amount of messages to be filtered.
  • To disable filtration completely please uncheck 'Filter fuel level sensors values' option.
There is the chart filtration disabled:This chart is for enabled filtration 10:

Fillings Detection

 Attention! In order to detect fillings the processed data is used (it is done on 'Data preparation' and 'Filtration' steps). Note: Ellipsis (…) substitutes 'Unit properties → Fuel consumption' is option paths.Three options are attached to this detection:
  • Option: Minimum fuel filling volume, liters;
  • Option: Detect fuel filling only while stopped;
  • Option: Ignore filtration when calculating filling volume;
  • Special Case: How a filling is processed?

Minimum fuel filling volume

... → 'Fuel fillings/thefts detection' block → 'Minimum fuel filling volume, liters'
This option helps to quit false fillings, because in motion sensors may send false data rise.

Detect fuel filling only while stopped

... → 'Fuel fillings/thefts detection' block → 'Detect fuel filling only while stopped'
In normal conditions transport vehicles are fueled on stops. This option narrows its search to stops/parkings.

Ignore filtration when calculating filling volume

... → 'Fuel level sensors' block → 'Ignore filtration when calculating filling volume'
When filtration switched on then some fuel level deviations may occur at the beginning and end of a filling. To avoid it the system uses unfiltered data when filling volume calculated.

Special Case: How a filling is processed?

Filling time frontiers and its volumeThe filling is processing. Assume, that fuel volume in this message is Vcurr, previous message fuel volume — Vprev. If the difference d (=Vcurr - Vprev) for the current message is positive, then current message will be marked as initial filling message. Time passes by. The filling is close to finish. When d-value for some message becomes negative (i.e., the current message fuel volume is less than in previous one), then it is called final filling message. Filling volume equals to Vfinal - Vinit (difference in fuel volumes between final and initial filling messages).Filling timestamp calculation algorithmNow it's time to find the filling timestamp. Iteratively for every message within filling interval (exclude the last one) the system seeks delta(=Vnext - Vcurr) for the next message which shows the fuel level growth between the current message and the next one. Message timestamp which delta is the ultimately biggest among others is regarded as filling timestamp (in other words, the left message is chosen from the message pair which delta is the biggest one). Worth highlighting, that a filling timestamp is calculated dynamically depend on the current unique case.

Thefts detection

 Attention! In order to detect thefts the processed data is used (it is done on 'Data preparation' and 'Filtration' steps). Note: Ellipsis (…) substitutes 'Unit properties → Fuel consumption' is option paths.The next options are crucial while detecting thefts:
  • Minimum fuel theft volume, liters;
  • Idling;
  • Detect fuel theft in motion;
  • Ignore filtration when calculating theft volume.

Minimum fuel theft volume

... → 'Fuel fillings/thefts detection' block → 'Minimum fuel theft volume, liters'
This option defines applicable fuel level falling minus fuel consumption for motion/idling to call such falling the theft and detect it.

Idling

... → 'Consumption math' block → 'Idling, liters per hour'
The option allows to detect thefts on stops/parkings. System finds difference between fuel volume spent according to sensors and mathematically calculated one. In case of non-zero difference which is equal to or more than value set in minimum fuel theft volume option then fuel theft detected.

Detect fuel theft in motion

... → 'Fuel fillings/thefts detection' block → 'Detect fuel theft in motion'
On default this option is unchecked. In case there is a necessity to control thefts in motion a user may use the option. But if sharp fuel level drop takes place then false theft may be detected.

Ignore filtration when calculating theft volume

... → 'Fuel level sensors' block → 'Ignore filtration when calculating theft volume'
Similar to fillings, filtration may deviate start and end fuel level values on thefts. To ignore such deviations the system uses unfiltered data while computing theft volume.

Consumption calculation

 Attention! In order to calculate consumption the processed data is used (it is done on 'Data preparation' and 'Filtration' steps). Note: Ellipsis (…) substitutes 'Unit properties → Fuel consumption' is option paths.Two options and special case are toughly connected with this step:
  • Replace invalid values with math consumption;
  • Reports → Report Template Properties → Options → Exclude thefts from fuel consumption;
  • Special Case: filling/theft is sliced with one of interval frontiers.

Replace invalid values with math consumption

... → 'Fuel level sensors' block → 'Replace invalid values with math consumption'
In case of values falseness, they are replaced with math calculation which uses data set in 'Consumption math' area. Algorithm: Let's say Vinit — initial volume for the interval (the way what interval is taken is defined in specified report template), Vfinal — final volume. Then difference is calculated between them with respect to fillings volume like Vinit – Vfinal + Vfill. In case of caluclated value is equal to or greater than zero the interval is marked as correct. But if the result value is negative then consumption is treated as falsy and math consumption takes place (with further whole interval falsy values replacing).

Exclude thefts from fuel consumption

Reports → Report Template Properties → Options → 'Exclude thefts from fuel consumption'
That option defines whether a theft took part in consumption while computing different indices. Keeping this option switched on is valuable when ignoring deviations because of detected thefts. Switch it off when discharge is authorized, as an example, agriculture vehicles are being filled with refueller and the user is to get fuel turnover being spent during specified period of time.

Special Case: filling/theft is sliced with one of interval frontiers. What is the way filling/theft being detected?

Let's examine the case on a filling example. Assume we've sliced the filling with the interval initial frontier. As described in how a filling is processed section a filling timestamp is defined dynamically according to the unique case. Since we've sliced the filling with interval, the second interval message becomes the initial filling message and it informs that fuel level has grown compared to the previous value (the first message is the reference used to calculate the delta (d=Vcurr - Vprev) for the second message, it cannot be calculated for the first message because of the absence of its previous one). The filling final message remains the same. The filling volume declines compared to unsliced filling reference (because of the initial message shifts to the right). The filling timestamp might hold the position/shift to the right, because it is all about the case whether the message, which timestamp is regarded as unsliced filling timestamp, is taking into account during calculation the time where the filling has occurred.
+ View More
Other Related Courses
About The Instructor
  • 3 Reviews
  • 27 Students
  • 27 Courses
+ View More
test
test
Student Feedback
5
Average Rating
  • 0%
  • 0%
  • 0%
  • 0%
  • 100%
Reviews
  • Sun, 28-Oct-2018
    Rob Schenck
$9.99
Buy Now
Includes:
  • 06:10:00 Hours On Demand Videos
  • 51 Lessons
  • Full Lifetime Access
  • Access On Mobile And Tv