Home Конструктор отчетов Report Constructor

Report Constructor

Report Constructor

1. Purpose

The Report Constructor is designed for creating and configuring reports for monitored units. It allows users to build a report template for a specific task, such as monitoring trips, stops, fuel, engine hours, geofence visits, speeding events, and other unit-related activities.

The same template can be used for both a single unit and a group of units. Once configured, the template is saved, so users do not need to select tables, columns, groupings, and other parameters again each time they generate the same type of report.

Important: the Report Constructor is intended not only for viewing data once, but also for creating reusable templates. A configured template can be used repeatedly for different periods, units, or groups of units.

2. Main Features

The Report Constructor allows users to:

  • create report templates;
  • add tables, statistics, and charts to a report;
  • select the required columns in tables;
  • rename indicators and tables;
  • configure the order in which data is displayed;
  • group data by date, unit, shift, day of the week, and other parameters;
  • enable details, row numbering, and totals;
  • use filters for specific table types;
  • view generated reports online;
  • export reports to PDF, XLSX, and CSV;
  • use templates for regular report generation.

3. Report Components

A report can include several components.

Component Purpose
Statistics Shows general report information and summary indicators for the selected period.
Tables The main part of the report. Tables show trips, stops, fuel fillings, fuel drains, engine hours, geofences, and other data.
Charts Used for visual analysis of indicators such as speed, fuel, temperature, voltage, engine RPM, and other values.
Export Allows users to save the report as a file or use it outside the system.

4. Report Template

A report template is a saved report structure with all selected settings.


Figure 1. Creating and configuring a report template

A template can include:

  • report name;
  • table set;
  • statistics set;
  • chart list;
  • selected columns;
  • data display order;
  • groupings;
  • filters;
  • additional display parameters.

A template is used to quickly generate recurring reports of the same type. For example, a user can configure a fuel report, trip report, or engine hours report once and then run it for the required period.

Recommendation: the template name should clearly describe its purpose. Examples: “Vehicle Fuel Control”, “Trips for Selected Period”, “Engine Hours by Unit Group”. This makes it easier to find the required report and reduces the risk of selecting the wrong template.

5. Statistics

Statistics is a summary block of the report. It shows key data for the selected period.


Figure 2. Configuring the statistics block

Statistics may include:

  • report name;
  • unit or unit group;
  • start and end of the reporting period;
  • mileage;
  • engine hours;
  • fuel consumption;
  • number of trips;
  • number of stops;
  • number of fuel fillings and fuel drains;
  • latest unit data.

For a report generated for a group of units, statistics contains a limited set of general data: report name, unit group, start of the period, and end of the period.

When configuring statistics, users can select the required indicators, change their order, and rename the displayed labels if necessary.

Note: statistics shows summary data for the report. It does not replace tables, but helps quickly evaluate the main results for the selected period: mileage, engine hours, fuel consumption, number of trips, stops, fuel fillings, or fuel drains.

6. Report Tables

Tables are the main part of the report. Each table is responsible for a specific type of data.

The following main tables are available in the constructor:


Figure 3. Selecting a table for a report
Table Purpose
Daily Summary Used to analyze key indicators by day.
Trips Used to analyze unit movement.
Engine Hours Used to monitor engine or equipment operating time.
Stops Used to analyze stops and long idle periods.
Fuel Summary Used for general analysis of consumption, fuel fillings, and fuel level.
Fuel Fillings Used to monitor detected fuel fillings.
Fuel Drains Used to monitor possible fuel drains.
Geofences Used to analyze visits to specified zones.
Trips Between Geofences Used to monitor routes between selected zones.
Speeding Events Used to analyze speed limit violations.
Fuel Movement Used to analyze fuel level changes over a period.
Aggregate Sensors Used to monitor sensors with on/off states.
Sensor Tracing Used to view sensor values at specific points in time.

For each table, users can select only the columns they need. This helps avoid overloading the report with unnecessary information.

Important: tables should be added only for a specific analysis task. The fewer unnecessary tables and columns a report contains, the easier it is for users to find the required information.

7. Column Configuration

Each table allows users to configure its column set.


Figure 4. Configuring table columns

Users can:

  • add required columns;
  • remove unnecessary columns;
  • change the column order;
  • rename displayed labels;
  • search through available indicators.

The column order in the settings corresponds to the order in which the columns are displayed in the generated report.

Recommendation: before saving a template, check the column order. It affects how the report will look when viewed online and when exported to a file.

8. Data Grouping

Grouping helps structure the report and makes it easier to analyze.


Figure 5. Configuring data grouping

Depending on the report type, data can be grouped by:

  • date;
  • unit;
  • day of the week;
  • shift;
  • geofence;
  • sensor;
  • trip direction between geofences.

Different grouping options may be available for reports generated for a single unit and for reports generated for a group of units.

If no grouping is selected, the data is displayed as a single list.

Note: grouping changes how data is displayed, not the data itself. For example, the same trips can be shown as a single list, by day, by unit, or by shift.

9. Additional Table Parameters

Tables may include additional parameters:

Parameter Description
Details Allows users to expand grouped data and view nested rows.
Row Numbering Adds row numbers. When grouping is used, numbering becomes multi-level.
Totals Adds a final row with summary or calculated values.

The totals row is used only for values that can be calculated: duration, quantity, mileage, consumption, averages, minimum values, or maximum values.

Important: the totals row is displayed only for indicators that can be calculated correctly. Totals are not generated for addresses, text values, and other non-calculable data.

10. Shifts

Shifts are used to analyze data within specified working intervals.

For example, if a shift lasts from 09:00 to 18:00, the report can show data separately within that shift. This is useful for monitoring vehicles, employees, or equipment operating on a shift schedule.

When configuring shifts, users can apply interval extraction. If it is enabled, only the part of an event that falls within the shift is included in the report. If it is disabled, the event is displayed in full and may be assigned to the “Outside shift” group.

Important: interval extraction affects how events are included in a shift. If it is enabled, only the part of the event within the shift is included in the report. If it is disabled, the event may be displayed in full.

11. Filters

Some tables include additional filters.

Examples:

  • in the Stops table, users can set minimum and maximum stop duration;
  • in the Speeding Events table, users can filter events by violation duration;
  • in geofence reports, users can select specific zones;
  • in the Trips Between Geofences table, users can specify start and end zones;
  • in sensor-related tables, users can specify required sensor names.

Filters help keep only the data that is important for the analysis.

Recommendation: use filters when the report is intended for a specific check. For example, users can keep only long stops, selected geofences, specific sensors, or trips between selected zones.

12. Charts

Charts are used for visual data analysis.

A report template can include charts for the following indicators:

  • voltage;
  • fuel consumption;
  • aggregate sensor operation;
  • speed;
  • temperature;
  • engine RPM.
Example of a chart in a report
Figure 6. Example of a chart in a report

The chart name can be changed.

Charts may display event markers:

  • stops;
  • speeding events;
  • fuel drains;
  • fuel fillings.

The chart background can also be configured to show different unit states, such as trips, stops, engine hours, short stops, or connection loss.

Important: charts are useful for visual analysis of dynamics. They should be added when users need to quickly see changes in speed, fuel, temperature, voltage, or other indicators over a period.

13. Sensor Masks

Sensor masks can be used for some charts and tables.

A mask is useful when a unit has several sensors of the same type and the report needs to display data from a specific sensor.

For example, if a unit has several temperature sensors, users can specify the required sensor so that the chart is built based on that exact sensor.

Note: sensor masks should be used when a unit has several sensors of the same type. This helps select a specific sensor and avoid incorrect data display.

14. Report Export

A generated report can be exported in the following formats:

  • PDF;
  • XLSX;
  • CSV.

Figure 7. Exporting a report to a file

The contents of the exported file depend on the template settings. If tables, columns, groupings, or other parameters are changed in the template, these changes must also be reflected in the exported report.

Important: the exported file must match the template settings. If tables, columns, groupings, or filters are changed in the template, these changes must be reflected in PDF, XLSX, and CSV exports.

15. When to Use the Report Constructor

The Report Constructor should be used when users need to:

  • regularly receive reports based on the same indicators;
  • prepare a report for a client or internal control;
  • compare the operation of one unit or a group of units;
  • monitor fuel, trips, stops, engine hours, or violations;
  • configure a report for a specific task without unnecessary data.

Recommended steps for working with a template:

  1. Create a new report template.
  2. Specify a clear name.
  3. Add the required tables.
  4. Select the required columns.
  5. Configure statistics.
  6. Add groupings if needed.
  7. Enable details, row numbering, or totals if necessary.
  8. Add filters for specific tables.
  9. Add charts if visual analysis is required.
  10. Save the template and check the result using a test report.
Recommendation: after configuring a new template, generate a test report. This helps check the data set, column order, groupings, totals, filters, and export correctness.

17. Summary

The Report Constructor allows users to create flexible templates for different monitoring tasks. Users define which data should be included in the report, in what order it should be displayed, and how it should be grouped.

The main purpose of the constructor is to reduce manual report configuration and make regular unit analytics more convenient and clear.

On this page

Back to the top of the page

Didn't find an answer to your question? Contact us