1

Report on Not Utilized Units

Topic: Report on Not Utilized Units

Is there a way to create a report for units that have not been used (no ignition on) in more than 3 days?   If possible I would like to have 1 report that shows units with no movement in 3 or more days and another report that shows units with no ignition on in 3 or more days.

2

Report on Not Utilized Units

Re: Report on Not Utilized Units

Hello,
Yes, there is more solution.

1- You can use a notification connections loss and in sitting time interval use 4320 Min, transferring units to a specific group and then extracting a report "Unit latest data" for this group.

2- You can use the report " Sensor tracing" and in the sitting report tracing interval use 4320 Min and filtration in the sensor mask "ignition sensor ".


Thanks.

Qusai Al-Haj | Technical Support Engineer
alhajq@gmail.com | Qusai@trak-link.net | +962 78 6594964
Jordan Company for Managing & Tracking Vehicles
Office: +962 (06) 541-2281  Ext. 71 | Fax: +962 (06) 541-2282
3

Report on Not Utilized Units

Re: Report on Not Utilized Units

chrissie wrote:

units that have not been used (no ignition on) in more than 3 days

Recommendation №1 of alhajq may suit you, but probably you should use "Sensor value" notification instead of "Connection loss", if you need to control ignition status.

@ Oleg Zharkovsky
Technical Consulting / Training Team
"Timely is the best. But still better late than never."
4

Report on Not Utilized Units

Re: Report on Not Utilized Units

zark wrote:
chrissie wrote:

units that have not been used (no ignition on) in more than 3 days

Recommendation №1 of alhajq may suit you, but probably you should use "Sensor value" notification instead of "Connection loss", if you need to control ignition status.

It's possible create a counter parameter when the ignition is off,you start a counter with the current date to the specific date limit?

5

Report on Not Utilized Units

(edited by phillype_loredo 06/01/2021 08:36:28)

Re: Report on Not Utilized Units

The demand related by the user could be extentended to other problems:"Hello,
Problem:
Availability is a metric to control whether the vehicle was or not in maintenance. Big fleet companies have some dificulties controlling the time of which the vehicles are in maintenances, many times vehicles stays in maintenances for months and they need a way to avoid this.

Solution:
This metric added inside Fleetrun can help them to control this mistakes. Knowing which vehicles have the smallest times of availability makes possible you acting faster or even renewing vehicles.

Users:
Will have fewer vehicles deactivate"


this was the point that i've propose:

"If we look to the notes of fleetrun, it's possible see that  fleetrun show the actual mileage and the total mileage.Consequently if the vehicle is stopped ,your   total mileage  will be less than the other vehicles.

The reasoning will be the same to this problem:https://forum.gurtam.com/viewtopic.php?id=17640,the only considerations it's the development of a  counter parameter.

What it's possible to do it's the user inform the vehicle it's in maintenance.When the user point that the vehicle it's in maintenance and the ingnition it's off, you could start  a counter paramater (hours,day,etc),when  the service is finished (the user shoud point) and the ingnition it's on,you finished the counter and compute the   difference final  between the final value- initial value.

If the value it's to large,the user should  specify the parameters:More than two days when the ingtion it's off,the counter the should be initialized,to compute the indicator."


https://forum.gurtam.com/viewtopic.php? … 40#p186640

With this problem reported by the user  you could analyse the possibility to extend to the other modules,due to the logic it's the same:The fleet's need to plain their maintenance,they need to know at logistics the time of a load and unload a truck,in agriculture in many time occurs inter-harvest period.

The only variables that  we know :It's when the ignition is on or off,and the selection of the parameters that the user do.

6

Report on Not Utilized Units

Re: Report on Not Utilized Units

phillype_loredo wrote:

It's possible create a counter parameter when the ignition is off,you start a counter with the current date to the specific date limit?

It is not possible to create such parameters by Wialon. Parameters are sent by trackers, and some devices can have a built-in logical algorithms to count something like you need.

Still it is possible to display in reports the data you requested. Some possible solutions were already mentioned in previous messages. Here is one more:
1. Create ignition sensor with a name "Engine status" (that's just an example).
2. Create a custom digital sensor with a name "Engine is off" and formula: const1-[Engine status]
3. Use table "Digital Sensors" to display duration of active sensor status.
    Don't forget to set a sensors mask "Engine is off" to show only this sensor. To filter minimal duration of 3 days use "Min duration" option.
    Both of mentioned options can be found in intervals filtration in table settings.

phillype_loredo wrote:

The demand related by the user could be extentended to other problems: https://forum.gurtam.com/viewtopic.php? … 40#p186640

With this problem reported by the user  you could analyse the possibility to extend to the other modules,due to the logic it's the same:The fleet's need to plain their maintenance,they need to know at logistics the time of a load and unload a truck,in agriculture in many time occurs inter-harvest period.

The only variables that  we know :It's when the ignition is on or off,and the selection of the parameters that the user do.

Not sure I can help you with it here. You were right to send this message to the forum branch about the Fleetrun application. Please wait for my colleague to answer you there.

@ Oleg Zharkovsky
Technical Consulting / Training Team
"Timely is the best. But still better late than never."
7

Report on Not Utilized Units

(edited by phillype_loredo 06/01/2021 13:14:24)

Re: Report on Not Utilized Units

The demand it's understandble:The user want a report that selects when the sensor was deactivated to the current date( today for example)     for the current date plus one day.The interval compute the difference of time  when the sensor was on and off   in a day  ,or "compute the   difference   between the final value- initial value".

i'm right?

8

Report on Not Utilized Units

Re: Report on Not Utilized Units

phillype_loredo wrote:

The interval compute the difference of time  when the sensor was on and off   in a day  ,or "compute the   difference   between the final value- initial value".

The interval can be longer than 1 day.
And I want to underline this table shows only the intervals when sensor is on. But if you create a sensor like I proposed, then active sensor "Engine is off" shows when engine is off.

@ Oleg Zharkovsky
Technical Consulting / Training Team
"Timely is the best. But still better late than never."
9

Report on Not Utilized Units

Re: Report on Not Utilized Units

zark wrote:
phillype_loredo wrote:

The interval compute the difference of time  when the sensor was on and off   in a day  ,or "compute the   difference   between the final value- initial value".

The interval can be longer than 1 day.
And I want to underline this table shows only the intervals when sensor is on. But if you create a sensor like I proposed, then active sensor "Engine is off" shows when engine is off.


Ok thank you,it's possible understand that logic well:The interval compute a difference of data when the vehicle was "on" and off (a boolean value).When the vehicle it's "off" ,it's the situation that you have said.