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.
Calculate theft volume by raw data
... → 'Fuel Fillings/Thefts Detection' block → 'Calculate theft volume by raw data'
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.
Special Case: How a fuel theft is detected?
Time frame of a theft and its volume
A theft is being performed.
Let us suppose that the fuel volume in the current message is Vcurr, the fuel volume in the previous message is Vprev. If the difference d for the current message (d = Vcurr - Vprev) is negative, the message will be considered the initial message of the theft.
Time passes. When the value
d is positive for some message
(that is the fuel volume in the current message is higher than in the
previous one), the message will be considered the
final message of the theft.
If the fuel level doesn't change during the time indicated in the 'Timeout to separate consecutive thefts' parameter on the '
Fuel Consumption' tab of the unit's properties, the theft will be considered finished as well.
The theft volume equals to Vfinal - Vinit (the difference of fuel levels between the final and the initial messages).
Theft timestamp calculation algorithm
Now the timestamp of the theft is being looked for.
The system seeks for a delta with the following message (d = Vnext - Vcurr)
for every message within the theft interval. The delta shows the
decrease in fuel level between the current and the next message.
The message timestamp that has the highest delta is considered to be the
theft timestamp (in other words, the left message with the biggest
delta is chosen from the pair of messages).
It is worth emphasizing that the timestamp of a fuel theft is
calculated dynamically depending on the sensors' values in every
particular situation.