Attention! This module is licensed separately and can be not included in your package.

Wialon gives you an opportunity to track units which go along the route with control points and predefined schedule.

Open the Routes Control panel in the work area on the left. Here you see the list of existing routes and can create a new one. The number of routes allowed can be known from your account parameters (see User Settings => Account).

Let us assume that a vehicle have to transport goods to five points. To control its activity you need to:

1. Prepare the route that is create a line-shaped geofence presenting a consequent movement along the route.
2. Mark five control points in the appropriate places and assign a schedule for them.
3. Create a route based on this geofence (give it a name, assign to needed unit(s).
4. Activate the route when needed.
5. Monitor how the route is accomplished.

A route is based on a geofence. If this is a polygon, the system traces unit presence in the geofence. Much richer possibilities of control exist for line-shaped geofences. They can contain control points and the schedule of visiting them.

Note.
A line-shaped geofence intended for controlling a route should be mapped from its start point toward its end and not vice versa, because the sequence of control points is automatically defined according to line direction and cannot be changed manually.

Control points are added when creating or editing a line-shaped geofence in the Geofences panel. Enter the edit mode , hover the mouse cursor over any point and press New control point button . Fill in the form:

• Control point name that will be used in notifications and reports.
• Control point radius. By default the radius of control point is the same as line thickness, but you can indicate your own value. This is useful if a point to be visited as located not right on the road but at some distance.
• Arrival time is time to arrive to this control point counting from the activation time.
• Arrival time variation (in seconds) is needed to give a unit some degree of freedom to visit the point. For example, if a five minute delay or advance is allowed, enter '300'.
• Departure time is time to leave the control point. It is also calculated from the activation time.
• Departure time variation.

Entries are saved automatically. To delete a control point, press Remove control point button at the top of the form.

Similarly add as many control points as you need.

When the geofence with control points is done, a controllable route can be created on its basis.

Routes are mainly created in the Routes Control panel. Push Create Route button and select unit(s) to assign the route to. Then set basic parameters for the route:

• Route name to be displayed on the routes list, when tracking the route, and in reports.
• Description (optional).
• Geofence: select a geofence to control from the dropdown list.
• Auto delete after finish: check this box if you prefer the route to be deleted when finished. Available if the selected geofence has control points.
• Allow unit to skip control points: check this box to allow skipping points. Available if the selected geofence has control points.
• Activation time: date and time to start the control. The route schedule will be counted from this time. Activation time can be omitted - in this case we consider that the route started when unit has entered the first control point (if points order is default) or any control point (in other modes).
• Enabled. If this flag is off, the route will not be tracked in any circumstances (event when the activation time has come) until it is on. If the route is enabled and points omission is allowed, the route fall under control immediately after its creation. If the route is enabled and points omission is denied, the route control starts when the unit enters the first control point. In both cases no control is possible until the activation time has come.
• Save events to unit history: if activated, any route status change will be stored in unit history, and then you can generate reports about this route. To register events to unit history, you need to have execute commands access to the unit.

After you press OK, the route appears on the list. If you selected several units for route control, several routes will be added. They will have the same names, but if placing the mouse cursor over each of them one can know the details.

There are some alternative ways to create a route - using jobs or notifications. For example, a route can be assigned to unit by preset schedule (job). Or you can create a notification with trigger action to assign a new route after the previous one is finished. One more way to create a route is to do it through the Geofences panel using a special button which is against each geofence on the list.

If there are many routes, they can be sorted by various criterion in the Routes Control panel, for example, finished routes, or waiting for arrival/departure, delayed, etc. The list of filters available see on the dropdown list. Besides, if you have more than one account, you can filter routes by their location on other different accounts.

To quickly find a definite route, use the dynamic filter. Enter route name or its part and observe the results.

When hover the mouse cursor over a route name on the list, in the tooltip you can see its description (if there is such), unit name, geofence used, activation time, and the status: 'inactive' or the progress (like 'waiting for arrival to … at …', 'geofence left at …', etc.).

In the table there is information about the route: route details (in a popup window), route status , etc.

You can also perform the following actions over routes:
enable a route;
disable a route;
change route parameters ( note that it is impossible to change route's unit or geofence, and if the route has been already started, activation time as well);
create a new route on the basis of another route (this is also a way to reassign a route to a different unit);
delete a route.

If you have just view access to the account where a route is located, some actions become not allowed, and the buttons look different:
route is enables, but you cannot make it off,
route is disables, but you cannot make it on,
view route properties (edition not available),
impossible to delete route.

There are several ways to monitor how a unit is accomplishing a route.

In the Monitoring panel on the working list there is a column presenting information on routes for each unit separately. To activate it, go to User Settings => Monitoring Panel and select Routes control. The following icons are used to visualize unit activities on routes:

- no routes are assigned to the unit;
- the unit is moving according to the schedule;
- the unit is in hurry;
- the unit is delayed,
- the route assigned to this unit is not activated yet;
- the route is finished;
- the unit is doing several routes at once;
- the unit left the geofence of control.

Put the cursor over any of these icons to see details in a popup window. For example, it can be specified exactly what time the unit is late.

In the Routes Control panel place the cursor over a route name to see details in a popup window (unit, geofence, status, etc.). Under the horizontal line it is indicated on which stage of the route the unit is at the moment.

The appropriate information can be also shown in unit info tip. To enable it, go to user settings and select Routes control in the section Show in unit info tip.

While a unit is performing a route, you can receive notifications about how it is going. To do this, create notification of the Route control type and adjust it properly depending on your needs. You can be notified when a route has started or finished, if a control point has been skipped, unit has left route geofence, and in other cases. These notifications can be sent by e-mail or SMS, shown online in a popup window, stired in unit history as events or violations. An action can be undertaken when such a notification triggers like execute a command, assign another route, generate a report, and others. See Notifications for details.

Using jobs of the Route control type you can adjust automatic assignment/removal of routes according to preset schedule.

If the option Save events to unit history is activated for the route, then all changes in routes statuses are stored in unit history, and later can be used to form a report: Routes or Route Points.

Route statuses are used in popup tooltips, in reports and in notifications. It is important to understand what they mean and how they are generated.

A route has status Inactive if the activation time has not come yet.

If the activation time is indicated, route falls under control when this time comes. At the same time the route achieves the status Started. Any visits to control points before this time will be ignored, and route status will be Inactive.

If the activation time is not indicated and points omission is denied, route becomes Started when unit enters the first control point.

If the activation time is not indicated and points omission is allowed, route becomes Started immediately, and unit position is analyzed from its last messages received before the route was created.

A route acquires the status Finished when arriving to the last control point.

The status Waiting for arrival to … <control point name> is assigned when the route starts. Then unit is expected to arrive to the first control point regardless whether points omission is allowed or not.

The status Waiting for arrival is also assigned when unit leaves some control point. Then the unit is expected to arrive to the next control point.

Arrival to control point means that a messages with coordinates which fall inside the point radius was received from the unit. The speed is not taken into account, so it does not matter whether the unit stopped there or just passed through. One message inside a control point is enough to register the entrance.

If point omission is not allowed, arrival point must coincide with that which were expected. It means if there was expected the arrival to the second control point and the unit came to the third, this visit will be not registered and the system will continue to wait for arrival to the second point.

The status Waiting for departure from … <control point name> is assigned immediately as an arrival is registered. Then the system starts to wait departure from the same point. In other words, one message from unit can give background to generate two events at once: arrival to a control point and waiting for departure from it.

Departure from a control point is detected when we get a messages from unit according to which the unit is already not inside the point. At that, the previous message must fall inside the point. In unit history this is registered as exit time.

If both entrance and exit were registered for a control point, this point is considered as Visited.

The event of control point omission can be registered only for routes which allow skipping points. If after visiting the second control point the unit comes to the fifth, then the third and forth points will be considered as Skipped. Even if these points are visited later, these visits will not be taken into account.