5.1. Overview of Computation Times
Table 5 shows the average computation times (
), the median value (
), the minimum computation time (
) and the maximum computation time (
) for each instance graph. Each row of the table gives the aggregate results over 81 different instances stemming from the systematic combination of the parameter entries in
Table 4.
As expected, the computing time increases for larger instance classes, up to the maximum of 48 h allowed for the Gurobi solution process. Thus, the size of the network has a significant influence on the computation time. However, even within an instance class, the computing times vary remarkably. Structure C has significantly higher computing times in all instance classes, although the graph size is similar to the other structures. In addition, even within a instance graph, the computing times fluctuate enormously, as indicated by the wide range between minimum and maximum values.
Further, we observe that the median value is significantly smaller than the average for the small and medium instance classes. This is because, within an instance graph, many instances can be solved to proven optimality within seconds, minutes or a few hours, and some instances could not be solved in the given time limit (48 h). The outliers lead to high median values for these instance classes.
However, for large instances, the mean value is always smaller than the median value. This is because most instances could not be solved to optimality within the time limit and consequently have a reported computation time of 48 h.
5.2. Analysis of Solution Process
Moreover, we studied the time needed by Gurobi to find the first feasible solution (), the time after which the solution did not improve anymore (), the size of the Linear Program (LP)-Gap (), and the size of the final Gap () when the time limit was reached. We calculated the LP-Gap as follows: , where indicates the objective function value of the optimal solution and indicates the LP relaxation solution’s objective function value. With this value, we want to describe the quality of the LP relaxation. A low LP-Gap indicates a good LP relaxation and a high value indicates a bad LP relaxation.
Since we have a time limit of 48 h, optimality cannot be proven for all instances. Therefore, the final gap () indicates the gap between the upper and lower bound at the end of the time limit.
In addition, we performed a second numerical investigation in which the average number of equally optimal solutions () was determined for the small instances. We consider solutions as equally optimal if they have the same objective function value as the optimal solution but differ in structure. Gurobi searches for all solutions with the same objective function value as the optimal solution and counts the number. Gurobi stops when all solutions are found or if the total number of equally optimal solutions is higher than 100,000. Due to the time limit, such a computation is not possible for the instances in the medium and large instance classes. Because of the upper limit, the average value of the equally optimal solutions is underestimated.
For all described metrics, the average values of 81 instances for each instance graph are shown in
Table 6.
A first feasible solution is found on average in less than one second in each instance class. This shows that the problem’s difficulty does not lie in finding a feasible solution. This is not surprising as a feasible (but expensive) solution can always be constructed by equipping each link with an ITU and then installing just one PSU.
Compared to the total computation time, a solution that is no longer improved is found after a relatively short time, particularly for small and medium-sized instances. Even for the hard-so-solve large instances, in most of the computation time, no improvement of the incumbent solution occurs.
Figure 10 shows the upper and lower bound course stemming from the Branch-and-Bound process for one exemplary instance of a large-sized instance of structure A. We observe that a feasible solution is found very quickly. The upper bound, i.e., the objective function value of the best solution found so far, improves very strongly at first, then only very slightly. After about 3 h, the upper bound no longer improves. The lower bound slowly approaches the upper bound in the remaining ten hours until the optimization terminates with the proof of optimality of the Branch-and-Bound procedure used by Gurobi.
Table 6 shows that there are many equally optimal solutions for the instances of the small instance class. The high number of equally optimal solutions can be a reason for the long time needed to prove optimality. A large number of equally optimal solutions leads to many nodes to be visited in the Branch-and-Bound process, even if one optimal solution may already have been found. One reason for the high number of equivalent optimal solutions lies in the design of the instances. The links often have the same length and thus the same energy contributions and investments. Hence, many different infrastructure designs lead to the same energy contributions and investments. The structure also highly influences the number of equally optimal solutions and the computation time. If a structure is symmetrically built, many different infrastructures lead to the same energy contributions and investments. This is especially the case for structure C in our study. We observe the highest number of equally optimal solutions for this structure in the small instance class. But above all, we observe the highest computation times in all instance classes.
In addition, and making things worse, symmetric solutions occur, especially when the link length is reduced.
Figure 11 shows an example of a symmetric solution. There is an intermediate node between nodes
and
. Let all links have the same length. In this case, both represented solutions are equivalent because they contribute the same energy to each service request and have the same investment. In any route segment that is not interrupted by an intersection and in which the link lengths are the same, each solution is equivalent in that the sum of the ITUs built in either direction is identical. In the example, the sum of ITUs in each direction equals 1. Consequently, with smaller link lengths, more symmetries are expected since there are significantly more such route sections.
As expected, the final gap increases with increasing problem difficulty. Again, we observe that instances of structure C are more difficult to solve than those of the other two structures. Larger instances mean that it is more likely that the time limit will be reached. For this reason, the final gap is larger with increasing problem size.
The mean value of the LP-Gap has similar sizes for all structures (between 40% and 60%). However, the LP-Gap varies extremely between the individual instances. As
Table 7 shows, the most influential factor is the energy ratio. The table shows the average values of the LP-gap for all instances together with the respective energy ratio
. For an energy ratio of 1.2, the average LP-Gap is only 5%, for a ratio of 3.24 it increases to 26% and for a ratio of 10 even to 115%. For a high energy ratio, it is sufficient to only partially equip links with an ITU, especially if the links are very long. In the solution of the LP-relaxation of the DICP, these links are “utilized” with very small fractionals such as 0.1. Therefore, the LP-Gap is very poor (far away from the ideal of 0%). However, if the energy ratio is low, many ITUs must be built, and partial equipment is not useful. Thus the LP-Gap is smaller, reducing the numerical effort of the Branch-and-Bound process performed by Gurobi. Unfortunately, this numerically attractive situation is not very interesting from a practical point of view. It corresponds to a situation in which ITUs would need to be installed almost everywhere, which is exactly what one would like to avoid in the attempt to find an economically efficient dynamic charging infrastructure.
5.3. Influence of Problem Properties on the Computation Time
The influence of the different instance attributes from
Table 4 on the computation time is shown in
Table 8. The computation times are divided according to structure and the attributes and averaged over 27 values. In the first cell, for example, the times are averaged over all instances that belong to the small instance class of structure A and have only one PSU candidate. They differ in the number of service requests, the energy ratio and the ratio of investments (
). In addition, the computation times of the medium-sized instances are presented graphically in
Figure 12,
Figure 13,
Figure 14 and
Figure 15.
In
Figure 12, we see that the number of PSU candidates strongly influences the computation time. The problem is easy to solve when only one PSU candidate is considered. In this case, no decision has to be made about where to place PSUs, but only where to place ITUs. This makes the problem much easier. Increasing the number of PSU candidates increases the computation time significantly.
Figure 12.
Influence of the number of PSU candidates on the computation time for medium sized instances of structures A, B, and C.
Figure 12.
Influence of the number of PSU candidates on the computation time for medium sized instances of structures A, B, and C.
In
Figure 13, we observe that increasing the number of service requests also leads to increased computation time. However, increasing the number of service requests leads to a much lower increase in the computation time than increasing the number of PSU candidates. On average, the increase from 30% to 70% is greater than the increase from 70% to 100%. The reason is the overlap of the requests. If all requests are included, an extremely high number of service requests is considered. Many of these requests have a high percentage of overlap. It is therefore conceivable that there are service requests that are already covered by the infrastructure requirements of other service requests. This means, for example, that if two service requests are fulfilled, a third request is automatically fulfilled as well. From the perspective of the problem, it makes no difference whether this third service request is considered or not. This effect will especially occur with a very large number of service requests. Thus, if we consider 70% of the requests, nearly all original requests are covered, and the difference between 100% is small. However, considering 30% of the requests will not cover all requests. Thus, the computation time increases substantially from 30% to 70% as more requests with no/few overlapping are added to the instance.
Figure 13.
Influence of the percentage of considered requests on the computation time for large sized instances of structures A, B, and C.
Figure 13.
Influence of the percentage of considered requests on the computation time for large sized instances of structures A, B, and C.
Figure 14 shows the influence of the energy ratio on the computation time. For structure A of the medium instance, a ratio of 1.2 has the highest computation time, and for cases B and C, a ratio of 3.24.
Table 8 also shows that the ratio of 3.24 mostly leads to the highest computation time. The combinatorics of the problem can explain this. An
ratio of 1.2 means that the energy intake is slightly larger than the energy consumption. Thus, almost the entire infrastructure has to be equipped with ITUs. There are few possibilities to realize this. The extreme case
illustrates this: In order to supply sufficient energy to the vehicles, the complete infrastructure must be equipped with ITUs. The only decision to be made is which PSU is to be connected. Therefore, there are only
different feasible solutions. If
is very large, then the energy intake is significantly greater than the energy consumption per distance unit of ITU passed by the vehicle. In this case, only a very small part of the infrastructure has to be equipped. For this reason, a very large part of the solutions can be excluded since they are too expensive. In the case of a medium-sized energy ratio, such as 3.24, many solutions are feasible and not too expansive, and many solutions can potentially be considered. For this reason, the computation time is usually the largest for this value.
Figure 14.
Influence of the energy ratio on the computation time for large sized instances of structures A, B, and C.
Figure 14.
Influence of the energy ratio on the computation time for large sized instances of structures A, B, and C.
Figure 15 shows that increasing the
ratio leads to lower computation times. This means a high investment in PSUs compared to ITUs lead to low computation times. As already shown, lower computing times occur if fewer PSUs are considered. If the PSUs are very expensive compared to the ITUs, it is not economical to build many of them. Rather, more ITUs would be built instead of one additional PSU. The question of how many PSUs should be built is not as difficult if the PSUs are very expensive. However, if the PSUs are less expensive, it may be useful to build multiple PSUs. In this case, there is the question of where to place the PSUs and whether it is better to build additional ITUs instead of one additional PSU. These aspects increase the combinatorial difficulty of the problem and thus the computing times.
In a final study, we re-ran the instances with the features that led to the highest computation times, but now with a CPU time limit of 200 h (as opposed to the initial 48 h).
Table 9 shows the results. Optimality could not be proven for any of the three instances, even after 200 h of computation. On the other hand, the remaining integrality gaps between 3.7% and 8.4% indicate that even for those hard instances, the Gurobi solver was able to find solutions that may be acceptable from a practical point of view as their worst-case deviation from optimality is not too large.
Figure 15.
Influence of the investment ratio on the computation time for medium sized instances of structures A, B, and C.
Figure 15.
Influence of the investment ratio on the computation time for medium sized instances of structures A, B, and C.
Finally, there is the question of what these computational results mean for real problem instances. In real problem instances, there will probably be many possible PSU locations because it is conceivable that there is a connection to the grid at every gate position. Modeling all of them would most likely make the problem intractable. However, several PSU locations close to each other could easily be represented by one PSU candidate. The justification for this approach is that we observed a very large number of equally optimal solutions, so it is non-unjustified to hope that we can drop many PSU candidate positions without losing all the optimal solutions from the solution space.
We further assume that there will be a large volume of traffic on the apron in the future. This is why we are looking at a large number of service requests. Instead of operating with a two-trip structure as in our instance generation process, we could also create instances with single-trip structures. This would reduce the number of requests to consider, making the problem numerically more tractable. On the other hand, it would lead to more infrastructure solutions that would be more expensive but more robust by giving the vehicles more charging opportunities.
As mentioned in
Section 4, the energy ratio of 3.24 is based on actual data from Broihan et al. [
8]. They assumed a power of 100 kW and efficiency of 80% for the wireless power transfer. Since this is still a new technology and the application is very specific, real data for the investments are difficult to find. Most applications consider a single bus. Jeong et al. [
28] mentioned 500
$/m as investment in a meter of an ITU and 50,000
$/unit for a PSU. However, the PSU needed for this application cannot be compared to the application at the airport, where many vehicles are powered simultaneously. Nevertheless, we can summarize that real-world problems mostly have the characteristics that make the problem particularly difficult. In addition, we have made simplifications even in the graphs of the large instance class since we do not consider all gates, depots and parking positions. Furthermore, we have chosen a still very large link length. It is conceivable that there are savings with smaller link lengths. With instances of real problem size, we can therefore assume even significantly higher computation times.