Differences

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

Link to this comparison view

Both sides previous revision Previous revision
user:reports:tables:rounds [05/08/2016 09:40]
daev [Rounds (for unit)]
user:reports:tables:rounds [11/05/2018 12:11] (current)
tagr
Line 2: Line 2:
 ====== Rounds (for unit) ====== ====== Rounds (for unit) ======
  
-If any [[user/​routes/​routes|routes]] were assigned to unit and events about routes were stored in unit history, a report based on these events can be generated: ​+If any [[user/​routes/​routes|routes]] were assigned to unit and events about routes were stored in the unit history, a report based on these events can be generated: ​
  
-  * **Route**: route name.  +  * **Route** ​— the name of the route given during its creation.  
-  * **Schedule**: schedule ​name.  +  * **Schedule** ​— the name of the schedule on the basis of which the route was created.  
-  * **Round**: round name. +  * **Round** ​— the name of the round
-  * **Beginning**: round beginning ​time (activation time or entrance in the first check point).  +  * **Beginning** ​— the start time of the round (activation time or entrance in the first check point).  
-  * **Initial location**unit location at the beginning of the route.  +  * **Initial location** ​— the unit location at the beginning of the route.  
-  * **End**: round end time (entrance to the last point).  +  * **End** ​— the end time of the round (entrance to the last point).  
-  * **Final location**unit location at the end of the route.  +  * **Final location** ​— the unit location at the end of the route.  
-  * **Result**//​Finished//​ (the route was activated successfully,​ and later on the entrance to the last point was detected) or //Not finished// (the last point was not visited).  +  * **Result** ​— //​Finished//​ (the route was activated successfully,​ and later on the entrance to the last point was detected) or //Not finished// (the last point was not visited).  
-  * **Skipped points**the number of check points ​skipped (on this basis more detailed report can be generated — see [[points|]]).  +  * **Skipped points** ​— the number of skipped ​checkpoints ​(detailed report can be generated — [[points|]]).  
-  * **Duration**time taken to perform the route.  +  * **Duration** ​— the time taken to perform the route.  
-  * **Total time**time from the first route beginning ​to the last route end.  +  * **Total time** ​— the time from the beginning of the first route to the end of the last route.  
-  * **Mileage**distance traveled while performing the route.  +  * **Mileage** ​— the distance traveled while performing the route.  
-  * **Avg speed**average speed on the route.  +  * **Avg speed** ​— the average speed on the route.  
-  * **Max speed**maximum speed on the route.  +  * **Max speed** ​— the maximum speed on the route.  
-  * **Count**the number of routes.  +  * **Count** ​— the number of routes.  
-  * **Driver**: driver'​s ​name if available.  +  * **Driver** ​— the name of the driver (if available).  
-  * **Trailer**: trailer'​s ​name if any was bound. +  * **Trailer** ​— the name of the trailer (if bound)
-  * **Notes**an empty column for your custom comments. ​+  * **Notes** ​— an empty column for your custom comments. ​
  
 {{ :​tables:​rounds.png?​nolink }} {{ :​tables:​rounds.png?​nolink }}
  
-How different route statuses are defined (route beginning, route end, point skipped, point visit, etc.), find [[user/​routes/​control#​route_statuses|here]]. ​+More information on how different route statuses are defined (route beginning, route end, point skipped, point visit, etc.) can be found [[user/​routes/​control#​route_statuses|here]]. ​
  
-In addition, in [[../​templ/​templ|report template]], you can indicate **masks for geofences and routes**. ​It means you can get in a report ​not all routes ​performed ​by unit within ​the indicated ​period, but only the routes which use a certain geofence ​or which correspond to the given mask of route name. Both filters can be used simultaneously ​or separately from each other+In addition, in [[../​templ/​templ|report template]], you can indicate **masks for geofences and routes**. ​That is, not all routes ​completed ​by the unit for the specified ​period ​can be displayed in the report, but only those that correspond to the specified route name mask or use a certain geofence(-s). Both filters can used separately or simultaneously.
  
-[[filtration|Intervals filtration]] can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, driver, trailer, fuel thefts, fillings, and geofences/​units. ​+[[user/​reports/​templ/​contents/​tables/​filtration|Intervals filtration]] can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, driver, trailer, fuel thefts, fillings, and geofences/​units. ​
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam