Feature Description

Fuel Guard detects fuel refill and loss as well as DEF/AdBlue fuel events.
An alarm is sent to the DataPortal when one of these events occurs.

This functionality differentiates between normal fuel consumption patterns and abnormalities (possibly labelled as tank leak or theft for example).
A DataPortal event essentially informs you about such events in the interest of further investigation.

The Fuel Guard feature is a paid DataPortal feature, see also Activation.

Use Cases

The Fuel Guard feature detects four different types of fuel events.
They are Fuel Refill (Refuel), DEF/AdBlue Refill, and Fuel Loss, and DEF Loss events.

These event types provide insights into the fuel supply for the fleet of machines.
The Refill event happens when someone fills up a machine with Fuel (Refuel event) or AdBlue (DEF/AdBlue Refill event).

These events are displayed in the Events menu of the DataPortal, see also DataPortal User Manual → "Event Functionality".

DEF/AdBlue Refill Event Detection

The DEF/AdBlue Refill event detection detects rapidly changing (positive changes) in the fuel level data.

Fuel Loss Event Detection

The Fuel Loss event detection works like the inverse function of the Refill event detection.
That might be a tank leak or even theft.
It detects decreasing rapid changes in the fuel level data.

Activation

In the DataPortal, you can activate the Fuel Guard feature via the Feature Switch, see Feature Switch.

Note

To enable the Fuel Guard feature, it must be ordered beforehand.
To do so, contact your Proemion representative.

After activating the Fuel Guard feature, the fuel events are going to be listed in the Events section from the next day on, see Event Functionality.

Configuration

To receive the following Fuel Guard events, your machine needs to deliver the following signals.
These need to be configured in the PDC.

1. Define the signals as described in the following table within the PDC, see PDC Manual → "ValueDefinition".
   Consider that signals that are required for a certain function should be recorded at the same time.

   Signal	Signal Key
   Fuel Level	value.common.engine.fuel.level
   DEF/AdBlue Level	value.common.engine.def.level
   Fuel Consumption Total (to determine "Fuel Loss" and "DEF/AdBlue Loss")	value.common.engine.fuel.used.total

2. The following events can be then obtained via the REST API, see Events, to be shown in the DataPortal.

   Warning

   The system uses buckets of 5 min and there must be a minimum of 20 buckets with data of the required signals each day - The minimum data points of 20 are required for a daily run.
   It is recommended to record the data every 5 min (180000 ms).
   The logging interval should NOT be greater than or equal to 10 minutes (360000 ms).
   Otherwise, the detection does not work properly.

   Parameter	Values	Additional Information
   Event keys for Historical Weather Data	Fuel Refill (Refuel) - event.common.consumables.fuel.refill
   	DEF/AdBlue Refill - event.common.consumables.def.refill
   	Fuel Loss - event.common.consumables.fuel.loss
   	DEF Loss - event.common.consumables.def.loss
   Ignore machines	name : ["Test", "Demo"] cu.name : ["missing"] model.name : ["missing", "Default"]	Can be used to exclude machines from being visible for other users.
   Bucket size	e.g.180000 ms	5 minutes