4.1. Experimental Design
Ship schedules and weights are simulated based on real geographical and flight data, enabling us to make decisions and analyze scenarios that closely mirror real-world situations. We consider six ports (
), including Bangkok, Dalian, Hong Kong, Incheon, Shanghai, and Tokyo. A segment refers to a specific leg of a route, typically from an origin port to a destination port. Any two ports in the port set
can be reached from each other and have multiple segments, and a total of 67 segment records are collected from the website Shipxy (Shipxy:
https://routes.shipxy.com/, accessed on 10 April 2024). Since the flight time of the team can only occur during non-working hours to avoid disrupting daytime inspection work, we query the flight ticket prices from the website Google Flights (Google Flights:
https://www.google.com/travel/flights, accessed on 11 April 2024) for each segment from the origin port to the destination port on 28 April 2024. Additionally, the flight time period is selected for non-working hours.
As shown in
Table 3, we include the average information of the segments between any two ports, where “ID” represents the index of each segment. “Distance” is the average sailing distance in nautical miles (nm) between two ports, “Travel time” represents the average travel time of the segment in days (d), “Speed” denotes the average speed in knots (kn) of the ship traveling on this segment, and “Price” is the price of the flight ticket in US dollars (USD) from the origin port to the destination port. For the six ports, there are 67 segments in total, which are then used to generate the schedule for each ship.
We choose a two-week planning horizon, i.e., , with a one-day time unit and set the total ship number . The weight of the ships follows a uniform distribution within the range of . A route of ship s is defined as a series of consecutive segments traveling through the entire planning horizon T. We define as the port set containing the ports on the route of ship . At the beginning of the planning horizon when , all the ships are at the origin port of their first segment . The duration time of ship s staying at port , , is randomly sampled from a closed interval of integers with equal probability, where is the minimum duration time and is the maximum duration time. We assume that each ship departs from the origin port only in the morning. The earliest inspection can be conducted on the day after the ship arrives at the destination port.
The routes for all the ships are generated based on all the segments, and then the route information is converted into the schedule information within the planning horizon. The schedule information for part of the ships, which serves as the parameter
in the IP model, is listed in
Table 4. Each item in the “Ship schedule” represents the duration of the ship staying at the port. The ports are represented by the initial letters of their names, where “B” stands for Bangkok, “D” is Dalian, “H” is Hong Kong, “I” is Incheon, “S” is Shanghai, and “T” is Tokyo. The time range is represented by a closed interval to indicate the range of days during which the ship stays at the port. Taking ship 1 as an example, it stays at Tokyo on day 1 and day 2. Then it travels from Tokyo to Dalian from day 3 and day 6. Then it is at Dalian on day 7 and day 8. After that, ship 1 goes back to Tokyo from day 9 to day 13 and is located at Tokyo on day 14.
The parameters of the experiments are set as shown in
Table 5. Generally, we conduct 151 experiments with experiment ID (EID) ranging from 0 to 150. Each of the experiments is included in the corresponding group with a group ID (GID).
,
, and
are the groups of experiments that aim to illustrate the performance of the IP model in solving instances with different ship numbers (
). Accordingly, the results of
,
, and
are generated by the PRIP model. As for the sensitivity analysis, experiments in
are set with divergence budgets.
is designed for testing the performance of experiments with variable duration time intervals (DTI), and
is set with different inspection capacities (IC). “MT” represents the model type, including the IP model (IP) and the PRIP model (PRIP). In the “
”, “Budget (USD)”, and “IC” columns,
represents a list of numbers generated from
a to
b with a step size of
c. The closed intervals in the “DTI” column have the same meaning as the duration time interval
mentioned above.
4.2. Performance of the IP Model and the PRIP Model
In this section, we analyze the performance of the IP model as well as the PRIP model.
Figure 3 and
Figure 4 show the optimal results of the IP model and the PRIP model, respectively. The
x–axis represents the experiment ID, where instances are arranged in increasing order of the number of ships. The
y–axis corresponds to the values of indicators, including the number of ships (
), the objective of an optimal solution (Obj), the inspected ship number (ISN), the total flight cost (TFC), and the total number of flights (TNF).
As shown in
Figure 3 and
Figure 4, the IP model and the PRIP model generally yield identical results for the Obj and ISN indicators across similar instances. However, differences arise in the TFC and TNF values for certain instances generated by the two models, although many remain the same. As for the performance of each indicator, both Obj and ISN demonstrate an increasing trend as the set size
grows. Specifically, for Obj, as depicted in
Figure 3a and
Figure 4a, there is a noticeable rapid growth in the early stages for groups
and
. This growth becomes more moderate during the mid-term phases (
and
), and eventually, the increase in Obj tapers off, showing a gradual convergence in the later stages (
and
). In contrast, the ISN value surges to 42 with increasing
and remains constant beyond this point, as shown in
Figure 3b and
Figure 4b. The TFC and TNF values start high but significantly decrease in the mid-stage. The following analysis will further dissect these trends for a more nuanced understanding. Additionally, it is noteworthy that Obj, which measures the overall objective value, reflects the effectiveness of the models in optimizing against set constraints and targets, underlining its pivotal role in assessing model performance.
To comprehensively illustrate the results, we divide all instances into three categories based on the number of ships: small-scale, medium-scale, and large-scale.
Table 6 and
Table 7 present the optimal solution results obtained by the IP model and the PRIP model, respectively, for small-scale instances, with the number of ships ranging from 20 to 200. From the results in
Table 6, we can observe that as the number of ships increases, both the Obj and the ISN show a significant increase. The Obj of the instance with
is
, while the Obj of the instance with
increases to
. This is mainly due to the fact that as the total number of ships increases, the actual number of ships inspected gradually increases, as long as the number of inspected ships does not reach the inspection capacity limit of the team. Since the objective function is the sum of the weights of the inspected ships, the objective function increases accordingly. CPU time refers to the solution time consumed by solving the model. As the “CPU time” column shows in
Table 6, the average solution time consumed by solving the IP model is
seconds. Therefore, it is quite efficient to solve small-scale cases by directly using Gurobi as the solver.
For the same instances,
Table 7 presents the results obtained by the PRIP model. We can observe that the Obj and ISN values obtained by the PRIP model are identical to those obtained by the IP model. The average values of TFC obtained by the two models are relatively close, with USD 3621.10 for the IP model and USD 3524.50 for the PRIP model. However, TFC and TNF are not entirely identical, indicating that the flight paths are not entirely the same. This is because there are multiple optimal solutions for the same instance. Therefore, it is possible to have the same Obj but different TFC values for the same instance. The time taken to solve small-scale cases using the PRIP model is roughly the same as that taken by the IP model, with an average of
seconds for both.
For the results of medium-scale instances generated by the IP model, we observe from the results in
Table 8 that as the number of ships increases, the ISN becomes a constant value of 42, while the Obj gradually increases. The ISN remains constant because of the existence of the total inspection capacity limit. In the experiments, the total planning horizon
T is 14 and the inspection capacity of each day
K equals 3. Therefore, the team can only inspect at most 42 ships during the planning horizon. When the number of ships is large enough to reach the total inspection capacity, there is no means to increase Obj by increasing ISN, but Obj can be improved by choosing the ships with larger weights. The expansion of the solution space due to the increase in total ship number allows the team to select ships with larger weights for inspection without changing the overall number of inspected ships. Therefore, the Obj is able to increase slightly.
The results obtained by the PRIP model for instances of medium scale still yield the same Obj as the IP model as shown in
Table 9, with TFC values not entirely identical but having similar average values. The average TFC value is USD 3068.40, which decreases by 14.86% compared to the average TFC of USD 3524.50 for small-scale instances. For medium-scale cases, the average solution times for the IP model and the PRIP model are similar, with
seconds and
seconds, respectively, which is double the average solution time for small-scale cases.
Compared with medium-scale instances, where the magnitude of increase in
is the same, the optimal solutions of large-scale instances also reach the inspection capacity limit but exhibit only a slight rise in Obj from
to
as shown in
Table 10 and
Table 11. This is because although
continues to increase, the distribution of weights for newly added ships remains the same as those that already exist. Therefore, when ISN reaches its limit, even as the overall number of candidate ships increases, its contribution to the Obj is small. Hence, the Obj does not exhibit significant growth. The average CPU times consumed by solving the IP model and the PRIP model are
seconds and
seconds, indicating that the models can also quickly obtain optimal solutions for large-scale cases.
The average TFC of large-scale instances generated by the PRIP model, which is USD 2064.0, has a decrease of compared to the one obtained by using the same model to solve small-scale instances. Accordingly, the average TNF decreases from to . This phenomenon is caused by the increase in for the following reasons. Assuming the team completes the inspection of K ships with relatively large weights at port p on day t, if there are still K ships with higher weights awaiting inspection at port p on day (including ships that stay at port p on days t and , as well as ships that arrive at port p on day t and can be inspected on day ), then the team will still stay at port p on day without the need for consecutive nightly flights. Consequently, the overall TNF will decrease.
This scenario is more likely to occur when is high. If there are fewer ships, then after completing the inspection on day t, there may be no ships to inspect on day at the same port. Even if there are ships available for inspection, the sum of weights of the uninspected ships at port p on day may be relatively small, and thus may not be included in an optimal solution. In such cases, the team needs to fly to another port with larger sums of weights for uninspected ships.