Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
user:reports:adv:driver [14/05/2018 07:08]
tagr [SMS Messages]
user:reports:adv:driver [01/10/2018 09:43] (current)
tagr
Line 20: Line 20:
 The following columns can be included in this kind of report: The following columns can be included in this kind of report:
  
 +  * **Unit** — the name of the unit to which the driver was bound.
   * **Beginning** — the date and time when the driver was bound to the unit.   * **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).   * **Initial location** — the initial position, that is, the address at that moment (if available).
Line 25: Line 26:
   * **Final location** — the final position, the address at that moment (if available).   * **Final location** — the final position, the address at that moment (if available).
   * **Duration** — the duration of a work shift.   * **Duration** — the duration of a work shift.
-  * **Total time** —  the time from the beginnig ​of the first trip to the of the last trip.+  * **Total time** —  the time from the beginning ​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** — 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 movement** — the number of engine hours for the interval of movement with the bound driver.
Line 56: Line 57:
  
 :!: 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). :!: 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).
 +
 ===== Custom Fields ==== ===== Custom Fields ====
  
Line 73: Line 75:
   * **Card** —  the state of the digital tachograph (inserted/​not inserted).   * **Card** —  the state of the digital tachograph (inserted/​not inserted).
   * **Activity** — the type of driver'​s activity (rest, work, driving, available, not available).   * **Activity** — the type of driver'​s activity (rest, work, driving, available, not available).
 +  * **Source** — the source of data, which is used to generate information about driver activity. The following column values are available: //E// — the data about trips is used; //T// — the tachograph data is used; //U// — the data about driver unbinding is used; //None// — the data source is unknown.
 +  * **Unit** — the name of the unit to which the driver is bound.
   * **Driving** — the time of driving.   * **Driving** — the time of driving.
   * **Work** — the hours of active work (time spent by the driver on vehicle repair, fuel filling, etc.).   * **Work** — the hours of active work (time spent by the driver on vehicle repair, fuel filling, etc.).
Line 84: Line 88:
 {{ :​reports:​tachograph.png?​nolink }} {{ :​reports:​tachograph.png?​nolink }}
  
-:!: While creating this report template, you should select in the [[user/​reports/​templ/​contents/​tables/​parameters|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. +:!: While creating this report template, you should select in the [[user/​reports/​templ/​contents/​tables/​parameters|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. 
 ===== Eco Driving ===== ===== Eco Driving =====
  
Line 95: Line 100:
   * **Time**: date and time of violation recording.   * **Time**: date and time of violation recording.
   * **Infringement**:​ type of driver'​s activity the conditions of which have been violated.   * **Infringement**:​ type of driver'​s activity the conditions of which have been violated.
-  * **Description**:​ short description of the infringement.+  * **Description**: ​short description of the infringement.
   * **Seriousness**:​ the extent of the infringement.   * **Seriousness**:​ the extent of the infringement.
  
 {{ :​tables:​infringements.png?​nolink }} {{ :​tables:​infringements.png?​nolink }}
  
-:!: While creating this report template you should choose in the [[user/​reports/​templ/​contents/​tables/​parameters|parameters of the table]] 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. +:!: While creating this report template you should choose in the [[user/​reports/​templ/​contents/​tables/​parameters|parameters of the table]] 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 //Bindings and trips// option ​is selected, the report'​s result changes in case of changes in the trip detector'​s settings, deleting messages, bindingsand unbindings, etc. 
 ===== Orders ===== ===== Orders =====
  
Line 107: Line 112:
 ===== SMS Messages ===== ===== SMS Messages =====
  
-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 [[user/​tools/​sms|SMS window]]. The driver sends messages from his mobile phone. This mobile phone number must be indicated in the [[user/​drivers/​new|driver'​s properties]]. ​+This report shows the correspondence ​of the dispatcher with the driver via SMS. The dispatcher (operator) can send messages to the driver from the Wialon interface through a special [[user/​tools/​sms|SMS window]]. The driver sends messages from his mobile phone. This mobile phone number must be indicated in the [[user/​drivers/​new|driver'​s properties]]. ​
  
 The following columns can be included in the table: ​ The following columns can be included in the table: ​
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam