Skip to main content

How does the Route planning work?

Updated yesterday

Route planning solution is designed to:

  1. Plan and optimize the route.

  2. Send the route and its updates to a vehicle/driver (Driver app).

  3. Receive and display on-route information and statuses.

While the route is being planned by the user of the route planning solution, route information is then synchronized with the mobile app allowing the driver to observe the route and its address information and to mark the status of each address on the route consequently.

The route planning solution is operating on a cloud base, all updates are free of charge to the clients who have obtained the route planning license.

The solution is available for a predefined number of vehicles set up on the platform. If you increase or reduce the number of vehicles included in the route planning solution it will also affect the total payment.


Components

Route planning operations are based on the interaction of three systems/components:

Route planning web-based application


Route planning is an add-on to a web-based platform. It ensures the following functionality:

  • Route planning add-on user management (as a part of the fleet management solution);

  • Vehicle management;

  • Route settings, planning and management;

  • Employee application users’ management;

  • Addresses/clients management;

  • Data exchange between route planning and employee application.

  • Communication between platform operators and vehicles drivers.

Tracking devices


Tracking devices are installed on each vehicle. Depending on selected device technical parameters and specifications, those devices track, measure and automatically send to the platform vehicle GPS location, current speed and other information.

Despite tracking devices don't participate directly in route planning functionality. The data received from a device allows overviewing of the actual location of a vehicle to compare it with the route’s path as planned in the platform.

Depending on a selected device model, tracking devices can be also integrated with the vehicle’s onboard computer and/or tachograph system installed in vehicles and thus can send tracked information to the route planning solution, too.

Driver mobile app


The mobile application has to be installed on mobile devices/tablets assigned to each driver or vehicle and ensures the following functionality:

  • Planned route display to the application user;

  • Route updates receiving;

  • Route opening on a selected navigation app for further on-route navigation guidance;

  • Data exchange between employee application and route planning solution;

  • Communication between vehicle drivers and platform operators.

📘 Tracking devices and the mobile application communicate with the route planning solution separately. Namely, if a tracking device malfunctions, the app user will continue receiving route directions and updates from the route planning solution and vice-versa, if the driver’s / vehicle’s mobile device where the application is installed is unable to connect to the route planning solution, the information gathered by tracking device will still be sent to route planning solution.


Route Planning by Vehicles or by Drivers

There are two types of planning that affect route planning and can be used throughout the platform where communication with the driver/vehicle is used. You need to choose one of the communication types and it will be used in all solutions not only in route planning, for example, Messaging. Only one option can be supported. The decision on planning type is commonly based on the specific area/operations of business processes.

By the Driver

The communication specifically with each driver individually. This option is great for companies where drivers use their own devices for communication (for example, cell phones) and drive multiple vehicles. An account for the mobile application has to be created for the driver and messages will be sent and assigned to this specific driver.

If you operate with short distance routes that are completed in less than one day and/or ensure the rotation of drivers within the vehicles of the fleet, then planning by the driver is recommended. In this case, each driver is supplied with a mobile device and the same device is used regardless of the vehicle the driver is currently driving. Indeed, the driver can specify in the app the vehicle he/she is currently driving or, if the tracking device on a vehicle is integrated with a tachograph, this data is then read automatically.

By the Vehicle


Communication with the vehicle, in other words, with any driver that is in the specific vehicle. The option is great for companies whose vehicles have built-in tablets and messages are sent to the vehicle. The company will need to create an account for the vehicle with a login and password to use the mobile application. Messages will be sent and assigned to the vehicle account.

If you operate with long-distance routes that last several days and imply the work of several drivers by shifts, then planning by vehicle is recommended. In this case, each vehicle is supplied with a mobile device and this single device is used by all drivers of the vehicle. Login into the app is made under the vehicle's account and the app allows selecting which of the drivers is currently in charge. Integration of tracking device with vehicle’s tachograph allows uploading the tachograph data into route planning solution for data analysis and processing within our platform.

While common planning, routing and other platform principles and features are the same regardless of the choice, there are some minor variations in the route planning process, namely if the route is being planned for a driver, an additional step of vehicle assignment for each route shall be performed. The most impact is on the principle of mobile application user management: mobile app users are maintained as vehicles (fleet) or drivers.

Did this answer your question?