Several drivers can be assigned to a single unit. To assign drivers to units, you need to have access flag Create, edit, and delete drivers towards the resource where those drivers belong.

There are two ways to bind a driver to a unit: manual and automatic.

The manual assignment can be performed in both modes (Drivers, Groups) of the Drivers panel. Use the corresponding switch button Bind / Unbind   to attach or detach drivers to/from units. The button is disabled  if your access is not sufficient.

Click Bind to unit button (), choose a unit the driver to be bound to, and click OK.

 Availability of units in this list depends on the work list in the Monitoring panel. If there are no units in the list, click Add all available button . If the list is still empty, then you have no access rights to these units.

To unbind a driver from a unit, click an icon of a unit opposite to driver name, and then use the corresponding button (). Besides, you can unbind a driver by registering a working shift, or deleting bindings from history.

To detect a driver automatically the corresponding equipment should be installed. For instance, contact memory devices, namely digital electronic keys (e.g. RFID chips) are widely used in personnel access control systems. When getting into the vehicle, the driver applies the electronic key to the reader connected to the tracker. If the parameter received from the tracker contains the key code, the driver gets bound. However, if the value of the parameter is empty, the driver gets unbound.

To use the automatic method of binding, some adjustments should be done in the system beforehand.

1. A special sensors of Driver binding type should be created in the properties of each unit intended for auto-binding. A parameter for this sensor can be avl_driver or some other depending on your equipment and its configuration. One or more driver sensors can be created on the basis of different parameters. If more than one driver binding sensor exist within a unit, the option Validate unbinding can be useful. If the option is activated, a driver bound to a unit automatically can be unbound from this unit only if empty value comes from the same parameter that was used to bind the driver. Otherwise, driver reset coming from any parameter will lead to the reset of all drivers bound to this unit.

 Note.
A driver can be unbound from the unit upon receiving the parameter with the unbinding code configured in the properties of the Driver binding sensor, and also upon the activation of the corresponding notification (for example, upon switching off the engine). When a driver with enabled Exclusive checkbox is assigned to a unit, all others are automatically unassigned. This function is relevant for drivers created within the same resource.

2. Create a list of units for any resource the drivers of which are intended to be bound automatically. In order to do so, click the Auto-binding icon (), and follow the steps listed below.

Upon clicking the Automatic binding icon a list of available resources is opened.  Here you choose a resource the drivers of which will be used in automatic binding (with the units chosen in the next dialog). In order to understand which drivers belong to a particular resource, go back to the Drivers panel, and apply a filter by resource (dropdown menu to the right of Create button).

After choosing a resource, click Next. If only one resource is available, then it will be chosen automatically.

The next dialog contains a list of units to which the drivers from a chosen resource can be bound automatically. Depending on the access rights possessed, the list can be viewed or edited.

Thus, a driver will be automatically bound to a unit with the help of iButton in case that (1) this unit has a special sensor in its properties and (2) this unit is indicated in the list of auto-attachable units applied to the resource where the driver belongs.

Automatic binding of drivers is removed in the same way: summon Automatic binding dialog, choose a resource, and uncheck flags of units for which the automatic binding will not be used.

This option can be used, for example, if you want to register working shift post factum. Use the corresponding button () opposite to a trailer’s name, choose the Register working shift option, and click Next. In the appeared dialog window choose a unit to which the trailer will be assigned in the indicated shift, click Next. Now indicate time of shift beginning and end. Moreover, you can indicate either only beginning or only end time. For example, you have indicated shift beginning, and you would like its end to be registered automatically when a unit arrives to garage (as a geofence). To do so, create a notification of Geofence type with method of action Reset trailer. Anyway, registering a working shift you can use only past dates or current time (no future allowed).

Incorrect registrations of drivers can affect reports and their informational efficiency. That is why sometimes you may need to delete such (un)bindings from the database. In the dialog, choose the last option — Delete bindings — and press Next. Specify time interval and press Show to display all bindings and unbindings of the driver on the interval. Check invalid messages and press OK to delete them.

 Note.
Like with units, the last message from the driver (whether assign or reset) cannot be deleted.

A driver can be bound simultaneously only to one unit. If somehow (for example, through registration of shifts) you are trying to bind a driver to another unit, later assignment cuts off the previous one.

However, several drivers can be assigned to one unit at once. It is reasonable with long-distance truck drivers and truckers.

If you want to avoid situation when a unit may have several drivers assigned to it, use the flag Exclusive in driver properties. If a driver with such a flag is bound to a unit, other previously assigned drivers are reset automatically. Note the following restrictions:

• • For correct operation, all drivers must belong to one resource.

• • It works only in real time, i.e. there are no such rules when registering work shifts of drivers.

• It does not work in reverse way, i.e., if a driver with activated Exclusive checkbox is assigned to a unit at the moment and another driver without that checked is being assigned, both of those drivers will be bound.