Introduction
Within Pavelink, shift planning is used to link data. All collected data, from weighing ticket information, track and trace of trucks, project location, location unloads, waiting times, travel times, etc., are all linked to the shift. Therefore, to view information in Pavelink, a shift is mandatory.
The four ways of planning within Pavelink:
- No planning: Pavelink auto-creates shifts
- Shift planning
- Trip planning
- API (application programming interface)
No planning: Pavelink auto-creates shifts
In case no shift is created in Pavelink, Pavelink creates its own shifts if needed. Of course, these shifts are never planned as precisely as a planner can do, but it helps to use Pavelink very easily and without any effort.
How does it work? As soon as the digital equivalent of a weighing ticket is received, Pavelink checks whether there is a shift scheduled for the project in question. If not, Pavelink automatically creates a shift. The weighing is then automatically linked to this shift.
At the jobsite, a foreman/screed machinist opens the shift and enters the amount of asphalt to be processed. In this way, progress can be monitored.
Shift planning
With shift planning, in most cases an asphalt coordinator enters the planned shifts into Pavelink, including the quantities of asphalt mixes ordered. By entering the data, Pavelink automatically calculates lap times and toll charges if applicable. This data can be used to check the planned situation against the realized situation.
At the jobsite, a foreman/screed operator opens the shift in his app, checks whether the planned quantities still apply, and only adjusts the amounts if applicable. Since quantities are already in Pavelink, progress can also be monitored here.
Trip planning
Trip planning is a module within Pavelink that helps to plan the number of trucks needed and to calculate the paver speed and asphalt consumption. This module is an add-on for Pavelink Basic and is only available if ordered.
With trip planning, it is possible to make a time table when and how many trucks are necessary.
API (application programming interface)
When a contractor uses shift scheduling software, it is possible to connect that software to Pavelink through an interface. Topcon has made available an API that allows the customer's software to connect and automatically transmit shift schedules to Pavelink.
Combinations
All of the above four ways can also be combined. A few examples illustrate some of the possibilities:
Example 1
Let’s say most work is not planned, and the contractor is more than happy to use the auto-create shift functionality. For an important, high-end project, they want to plan upfront with shift planning and also want to create a trip planning. That is exactly how Pavelink works. For all other jobs, the shifts are created automatically, except for the planned shift; that shift is already in the system and doesn’t need to be created by Pavelink.
Example 2
A contractor uses the API to link his own planning system to Pavelink. The plans as made in his own system are automatically implemented in Pavelink. Both IT systems exchange data automatically without human intervention. Then something changes in the planning last minute. This can be a repair job, but also another project due to a delay in milling. Regardless of the reason and despite the automated link, it can mean that these ad hoc changes are not immediately processed in the in-house planning system and therefore not passed on. In such cases, a contractor can choose to have these shift plannings automatically created by Pavelink. Pavelink checks with each received weighing whether a shift planning is present. If not, Pavelink will check if the auto-create shift functionality is enabled (customer choice) and create the shift automatically if desired.
Example 3
A contractor plans each shift as best as possible in Pavelink. For this example it doesn't matter if it is done via the manual shift planning or via the API. For certain projects, people find it interesting to make a trip planning as well. This can be done beforehand to get a better estimate of the number of trucks needed, or afterwards to verify if the chosen method was the most efficient one. Because the trip planning can be used both before and afterward, a contractor can constantly adjust the process to make more profit.
