The "Templates" tab is intended for editing event templates, which should be triggered by the sensors installed in the object's equipment.

- The system itself creates event templates depending on the system settings and the equipment installed at the facility. These templates are standard and are usually assigned by default.

- The administrator can refine the standard templates to get a different display of the result or change the conditions for calculating events.

It is not recommended to change template settings. These settings must be changed by a specialist.

If the settings have not been changed as required, then you must click the Default button in the event template editing dialog window. The template settings will be reset to default values.

The tab is a list of events that displays the name of the event and the type of installed sensor that should respond to this event.

In the upper part of the Templates tab there is a button for editing the parameters of the event template  . Also, the event template can be called for editing by double-clicking on any line of the event template in the list.

The Calculation Parameters tab is intended for setting the conditions for determining an event. You can assign base conditions for defining an event, as well as conditions based on the results of an event. The assignment of conditions based on the results of the event is intended to clarify the information received from the sensor and additionally check the readings.

Drain/Refill Template

For example, if within 30 seconds. the location of the object did not change beyond 30 meters, and the speed did not exceed 6 km / h, while there is an increase or decrease in fuel for at least 40 seconds by more than 10% of the tank capacity, then the system will recognize such events as Drain / Refuel. In this case, the system does not record events that do not fall within the specified range of conditions. The choice of conditions can have a large impact on the reliability of events. Example - slight fluctuations in the fuel level can be caused by the movement of an object or roughness in the road. The administrator can define event templates that are more suitable for the specifics of individual processes.

If refueling is not reflected, but goes into consumption, while the remaining fuel increases, then it is necessary to adjust the "refueling" template.
Most often, it helps to adjust the time down and remove the "stop(150m)" event




.

For example, if the location of the object did not change beyond 30 meters, the speed did not exceed 6 km/h, the ignition was turned off, and as a result the event lasted more than 30 seconds, then the system will recognize such an event as a Stop.

Template Stop 150 m

For example, if the distance between the points in the data packet is no more than 70 meters, and the total difference from the start of the stop does not exceed 150 meters, then the system will recognize such an event as Stop 150 m.

You can also configure additional options:

- Activation time - from what moment to start counting the event. For example, after 15 seconds, consider the Stop event to have occurred.

- Deactivation time - if the event started, but did not last long enough to be considered complete. For example, if after 15 seconds the car starts moving again, do not consider the Stop event to have occurred.

- No data - if no data was received under the specified conditions and after 15 seconds, consider this event as No data.

Idle pattern

If the ignition sensor indicates that the ignition was made during the stop, then the system recognizes such an event as Idling.

Pattern Speeding

For example, if the car was moving at a speed of more than 100 km/h and the event lasted more than 30 seconds, the system recognizes such an event as Speeding.

Tanker Operation Template (OSS)

For example, if the OSS registers fuel inflow greater than 0.1 units/sec, while the speed is less than 3 km/h, and as a result of the event, the fuel difference is 5 units or more, then the system considers this as sweating.