The following types of tables can be applied to drivers:

• Bindings,
  
• Custom fields,
  
• Driver activity,
  
• Eco driving,
  
• Infringements,
  
• Orders,
  
• SMS messages.
  

The Bindings table shows when and to which unit the driver was assigned, how long his work shifts lasted, how much fuel was spent, the distance traveled, etc.

The following columns can be included in this kind of report:

• Beginning — the date and time when the driver was bound to the unit.
  
• Initial location — the initial position, that is, the address at that moment (if available).
  
• End — the date and time when the driver was unbound from the unit.
  
• Final location — the final position, the address at that moment (if available).
  
• Duration — duration of a work shift.
  
• Total time — the time from the beginnig of the first trip to the of the last trip.
  
• Engine hours — the total amount of engine hours for a working interval of the driver.
  
• Engine hours in movement — the number of engine hours for the interval of movement with the bound driver.
  
• Engine hours in idle run — the number of engine hours for the interval of idling with the bound driver.
  
• Mileage — the distance traveled within the period.
  
• Mileage (adjusted) — mileage taking into account the coefficient set in the unit properties on the Advanced tab.
  
• Urban mileage — the distance traveled in the urban area.
  
• Suburban mileage — the distance traveled in the suburban area. It is calculated in regards to speed. The urban/suburban speed line is indicated in Unit Properties => Advanced (the Urban speed limit setting).
  
• Avg speed — average speed in a given interval.
  
• Max speed — the maximum speed registered within this work shift.
  
• Counter — the value of the counter sensor.
  
• Status — the status of the unit registered during the interval (if there are several, the first one is displayed).
  
• Violations — the number of violations.
  
• Count — the number of bindings found on a given interval.
  
• Consumed — the amount of fuel consumed in total for all fuel sensors.
  
• Consumed by ImpFCS/AbsFCS/InsFCS/FLS/math/rates — the volume of consumed fuel detected by any fuel sensor (such as impulse/absolute/instant fuel consumption sensor, fuel level sensor) or calculated by math or rates.
  
• Avg consumption — the average fuel consumption, determined from the available fuel sensors.
  
• Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math/rates — the average fuel consumption in the trip detected by one of the methods mentioned above.
  
• Initial fuel level — fuel level at the beginning of the work shift.
  
• Final fuel level — fuel level at the end of the work shift.
  
• Penalties — penalties calculated for the adjusted Eco Driving criteria.
  
• Rank — penalty points, converted into a grade using 6-point rating system.
  
• Notes — an empty column for your custom comments.
  

In addition, in the report template to the right of the list of columns, you can specify the units to which the report will be applied. If no units are selected in this section, the report will be applied to all available units.

The report is designed in such a way that the first column is the list of units to which the driver was bound. It is recommended to apply the  option to this table to get a possibility to expand any unit and see more detailed information about all work shift.

 To determine the intervals of binding, the messages from the unit are also taken into account. If there are such messages, they are considered to be of more priority than the messages about binding (the intervals are counted according to them).

The Custom fields represents the list of custom fields entered in the corresponding tab of the driver's properties. Possible columns:

• Name — custom field name.
  
• Value — custom field value.
  
• Notes — an empty column for your custom comments.
  

The Driver Activity table shows such information as the type of driver's action, the crew of a vehicle, the state of the tachograph cards. It may include the following columns:

• Beginning — the date and time when activity begins..
  
• Card — the state of the digital tachograph (inserted/not inserted).
  
• Activity — the type of driver's activity (rest, work, driving, available, not available).
  
• Driving — the time of driving.
  
• Work — active work hours (time spent by the driver on vehicle repair, fuel filling, etc.).
  
• Availability — passive work hours (time spent by the second driver in the moving vehicle).
  
• Rest — the time for rest of the driver (vehicle is stopped, the driver rests in a specially designated place).
  
• Overall work — the total time spent by the driver on such actions as driving, work, reserve.
  
• Slot — slot for digital tachograph card (Driver or Co-driver).
  
• Status — vehicle crew size (single/crew).
  
• Daily mileage — the distance covered by the bound driver during the day (24 hours).
  

 While creating this report template, you should select in the parameters of the table the way to determine driver activity: DDD files (are sent by the tachograph), online data (generated online on the basis of the events of bindings and trips) or bindings and trips (messages are used as the source). If the Bindings and trips option is selected, the result of the report changes when you change the settings of the trip detector, delete messages, bind and unbind, etc.

This reports is similar to the report for a unit.

This report shows information on the violation of labor routine by the driver. It may include the following columns:

• Time: date and time of violation recording.
  
• Infringement: type of driver's activity the conditions of which have been violated.
  
• Description: short description of the infringement.
  
• Seriousness: the extent of the infringement.
  

While creating this report template you should choose in the a driver activity source: DDD files (are sent by the tachograph), online data (are formed online on the basis of the events of bindings and trips) or bindings and trips (messages are used as the source). If the option 'Bindings and trips' is chosen, the report's result changes in case of changes in the trip detector's settings, deleting messages, bindings and unbindings, etc.

This reports is similar to the report for a unit.

This report shows the correspondece of the dispatcher with the driver via SMS. The dispatcher (operator) can send messages to the driver from the Wialon interface through a special SMS window. The driver sends messages from his mobile phone. This mobile phone number must be indicated in the driver's properties.

The following columns can be included in the table:

• Time — date and time when the message arrived.
  
• Type — message type: sent (message sent by the dispatcher) or received (message received from the driver).
  
• Text — the text of the message.
  
• Phone — driver's phone number.
  
• Modem phone — the phone number of the modem that sent/received SMS.
  

For the Binding and SMS messages tables, you can apply grouping by days/weeks/months, but you need to take into account that in these tables only one level of nesting is possible, i.e. at the first level - units, on the second — generalized information for the specified date/week/month (the second level is not disclosed).

In addition, you can query statistics for the reports, where the following fields are possible: report template name, driver name, report interval (beginning and end), and report generation time.

Tracks of the driver's movements can be displayed on the map.

Most tables can be generated for a group of drivers.

 Note.