6-4-5
Release 6.4.5
In this release, we introduce new enhancements.
- Maintenance Enhancement
We are excited to introduce the new enhancements in our maintenance feature.
First of all, it’s possible now to apply a margin of your choice on the due tasks after which the task will become overdue unless it’s been resolved/progressed. the margin can be applied through the task generator wizard (step 4) and can be edited in the generators list page as shown below:
If any of the set margins have been violated while the task is still in the due state (not in progress nor resolved), the task will become overdue.
the available margins are:
- elapsed distance: if the vehicle traveled for a distance greater than the threshold set here and no updates were made on the task (still in due state), the task becomes overdue.
- elapsed ignition time: if the vehicle was ignited on for more than the time threshold set here and no updates were made on the task (still in due state), the task becomes overdue.
- elapsed time: if it’s passed longer than the time threshold set here and no updates were made on the task (still in due state), the task becomes overdue.
In correspondence, the maintenance dashboard’s widgets now show the statistics of the overdue tasks
On top of that, we now started to record the task’s movement between the different states and will display them in the history table of the due task explorer. The history table can be accessed from the new column “History” on the due task explorer.
Notes about overdue tasks:
- Once a task becomes due while it has some margin to monitor, the system will start accumulating the margin-related values and store the last achieved value before resolving/turning the task into in-progress.
- If you unresolve or un-progress a task, it will return back to its previous state (due, in progress, or overdue — as it was) and the system will continue accumulating the margin-related values over the stored ones and validate if the task became overdue.
- The task generators work every hour (at minute 00) to generate tasks and the margins are checked every hour at minute 30th.
- Dynamic Driver Module Enhancement
We introduce a new enhancement to the company configuration in the dynamic driver module. The “Create Driver Dynamically Upon Receiving Unknown Driver ID” feature is now more flexible in that you can choose whether to save the received key as is or in a reversed way. This notably facilitates your work when your device already sends the driver key in reverse mode but you need to save it in the correct mode so you can use it when sending “add driver” commands to the devices. Moreover, you can enable this enhancement per device type/model; just click the “edit” button to choose the device(s) type and model — that easy!
- Augmented Argument Enhancement
continuing our persistent improvement to our “Augmented Tracking” feature, we are happy to announce that now you can determine the digital input responsible for reporting the passenger seatbelt via the augmented arguments. like any other argument, you can select the argument type in the second step and then select “passenger seatbelt from digital input” in the third step if your passenger seatbelt is connected to a digital input of the AVL unit, choose the digital input number, and the meaning of a high voltage on the chosen input. if the passenger seatbelt status is reported via CAN-Bus, please select the “Blank” choice in this step.