Recently, the Gurtam experts summed up the results of the global competition IoT project of the year. We held an online ceremony, chatted with partners, and announced the winners. But even then, we launched the second season of the Gurtam meetups. Well, we are already discussing topics that are of particular interest to the telematics community. Keep up with our announcements and join our weekly online meetings!
While one expert group is fully engaged in releasing beneficial meetups, another one is ready to please you with updates of the Wialon apps and new platform features. But before you start testing new options, we kindly recommend reading a detailed overview.
We released an enhancement for counters. Now, the relative sensors' values (relative odometer, relative engine hours) can be used from the previous message. It means that if the mileage and/or engine hours counter is set to a relative sensor, then the values from the previous message can be used in the parameters.
For example, for various special vehicles, the operating time is recorded not in the mileage kilometers but engine hours. Moreover, for such vehicles, the engine hours counter considers the engine operating mode and not the engine ignition sensor. In this case, at nominal engine speed, one engine hour is equal to an hour of engine operation, at a low speed – 0.5 engine hours, at an increased speed – 1.5 engine hours.
These real engine hours can be taken into account in Wialon only thanks to relative engine hours sensors. However, such sensors could only be used in reports since engine hours weren’t accumulated in the unit’s engine hours counter.
The relative sensors' data can be used not only in reports but also for mileage/engine hours counters set to relative sensors thanks to the update. This, in turn, guarantees the correct operation of the maintenance.
We added two new blocks on the Dashboard tab – Top units by fuel consumption and Top units by mileage. The first block displays units from the Monitoring tab with the maximum fuel consumption by FLS for the specified period. The second block displays units from the Monitoring tab with the maximum mileage for the specified period.
The blocks will help analyze these data without the need to build reports alongside the already available option to view the mileage and fuel data by each individual unit.
Previously, the ignition sensor's Timeout value was not considered when calculating the events in the Wialon app for Android and iOS. It could lead to the data difference in reports in the system’s web-version and a mobile app. Now, this value is considered, and data is consistent.
Application example: if for some reason (for example, connection loss) the daily data wasn’t received while the latest ignition status until the moment of receiving the new messages was ‘On,’ the unit’s engine hours in the mobile app were calculated as if the engine was working this entire time, which was not true, of course. With the new function, you will get the correct data.
In the exported Excel reports, we made the following changes:
Now it is easier and more convenient to use the reports.
We added a check for a valid course. Previously, if the unit sent the same course or did not send it at all, then the field cultivation overlaps were not calculated, and the user saw a 0% value. Now, in such conditions, a check for a valid course will be performed, and if it is not available, the course will be calculated directly in Hecterra.
Thanks to the new option, overlaps in the field cultivation will always be calculated correctly, even if the unit sends the wrong course or does not send it at all.
Find more on the new features, as well as comment on the app functionality and user experience on the Gurtam forum.
Now, when deleting service units (units, drivers, trailers) from the fleet, the user will see a notification warning that the service unit is assigned to intervals and/or services.
This new option will prevent users from accidentally deleting units assigned to intervals and/or services.
We modified the cost displaying format in reports in the following way:
With these changes, we have achieved a more convenient displaying format of costs in reports.
Now, in the Total row, in the Total cost column, the user will see the phrase “Excluding parts and labor” instead of “Unaccounted as parts/labor.” It allows displaying two costs: total and considering only parts and labor.
Now the app users can create a detailed cost report. On the Reports tab in the Report type field, there are options:
In reports of this type, the user will see the labor cost and the spare part's name, type, number, cost, etc.
With this information at hand, your clients will have the opportunity to analyze, for example, which parts or services are most in-demand in the fleet. As a result, they will reduce fleet servicing costs and plan future costs according to the report.
We added new types of grouping:
Now the display of report results can be structured according to more parameters to analyze costs in more detail.
We increased the limit of values that can be added to the custom field of the List type. Now users can add up to 20 fixed values in a custom field.
Find more details on Fleetrun new features in this forum topic.
We improved the Custom fields tab functionality. Now it’s possible to change the field sequence in the list using the Custom fields tab settings. To change the sequence, users need to drag the field into the necessary position.
Now custom fields in the order creation/modification dialog will be displayed in the same sequence as in the user settings.
We added a filter for displaying a custom field in the mobile version. In the right corner of the created field line, we placed a switcher that can be either enabled or disabled. By default, it is disabled.
If the switcher is active, then it is possible, when creating a route, to display the corresponding custom fields in all requests in the mobile app until the route gets into history.
Thanks to this feature, the users will transfer the information necessary for delivery to drivers. Please note that the mobile app user will see only the field that is activated in the settings. This way, it’s allowed to decide what information can be transmitted.
Now the custom fields created in the settings can be added both to the template and directly to the import tab. In the template, the fields with the drop-down list will include the columns’ names, where the column name is a custom field from the user settings.
Please pay your attention that the user fills in the values in the new fields in the import table. For example, in the settings on the Custom fields tab, the user has two added fields: "Cargo type" and "Supplier." In the import dialog and the template, the user can select these columns.
If the user has no added fields in the settings, then, respectively, there will be no opportunity to select new columns in the import dialog and the template.
Thanks to this option, it becomes possible to conveniently and quickly import orders with any necessary information.
Visit the forum and read about the new Logistics options. Please share your experience with the updated functionality.
In a month, we will prepare a recap of November features. Meanwhile, feel free to try and test the new features of the platform and apps, as well as leave your comments on the Gurtam forum.