# Container Terminal Berth and Yard Collaborative Allocation for Import and Export Synchronous Operations by Computational Logistics

Authors: Bin Li; Xiong Jiang; Junhan Lei
Journal: Discrete Dynamics in Nature and Society
 (2022)

---

## Abstract

Container terminal operators have practical and clear requirements on improving operational efficiency and service level to address running challenges. The resource allocation and collaborative scheduling of quayside berth and storage yard are vital issues in the optimization of container terminal handling systems (CTHSs). The allocation of berth in quayside and blocks on storage yard directly affects the running efficiency of CTHS. Consequently, we focus on the berth and yard collaborative allocation for import and export synchronous operations (BYCA-IESOs) and propose the BYCA-IESO research model based on synchronous or asynchronous integrated scheduling strategy by computational logistics. The BYCA-IESO model is a mixed integer quadratic programming model to minimize multiple time consumption of calling liners and the total horizontal transferring distances of yard trailers at container terminals. Furthermore, we design other two allocation policies for comparison on the BYCA-IESO, which are both multistage scheduling strategy profiles. CPLEX 20.1.0 is applied to implement and solve the model and tactics of BYCA-IESO. Accordingly, the feasibility, validity, and relative merits of the models and strategies are obtained and verified by analyzing and comparing multiple numerical experimental results.


---

## Body

## 1. Introduction

The container terminal is a backbone hub node in the international trade logistics network, which is an important distribution center to change the mode of transportation or hand over cargos. The scale and quantity of container terminals both have grown steadily in the influence of economic globalization and with the rapid development of container freight and large-scale container ships. Moreover, the container terminal has definite trends of deep water, operational specialization, and running integration [1–3]. Generally, a container terminal may serve a certain number of vessels simultaneously and the terminal operators need to handle a huge quantity of containers even in a very short period of time. This is undoubtedly conducive to the development of container terminals. When facing a huge development opportunity, challenges to the operation of container terminal handling systems (CTHSs) also become greater than ever. The competition among terminals is fierce and furious. However, as the close links among the economic activities of every country, container terminals play an increasingly important role in the import and export trade of each country. By improving the competition of container terminals, it can promote the economic development and logistics service of the country dramatically where they are located. Hence, it is very necessary and urgent to improve the level of operation and management of CTHS.Promoting competitiveness of container terminals relies on pushing the continuous improvement of their handling technology and operation efficiency at the tactical and executive levels in significant measure [4, 5]. It is just about improving resource utilization and task scheduling in the container terminal handling systems (CTHSs). The core production resource at container terminal is always limited and scarce in most situations, such as quayside berths, yard bays, quay cranes, and yard trailers. As the increasing number of vessels and containers needs to be served or handled, the CTHS must ensure that all calling liners can moor to be operated and all accompanying containers can be handled in a finite period of time. If the terminal operator cannot allocate the production resource wisely, the departure time of liners has a high probability of delay. Once the delays on some vessels become severe, it not only leads to the congestion for the given terminal but also influences the arrival time of the container ships to the next harbor. Consequently, the container terminal is going to become less competitive gradually since the shipping line is unwilling to choose this terminal. As a result, it is of paramount importance for container terminal operators to arrange resources more availably and rationally and improve the utilization efficiency and response time of key resource pool [6, 7].Generally, the operator of container terminal will develop an operational plan and scheduling schemes over a period of time according to the estimated arrival schedule of liners and the occupation windows of terminal resources. The planning cycle of terminal operators may be hours, days, or weeks. For the CTHS, both berth and yard are the most important tactical and executive resources and lie at the heart of port competition because the working spaces of CTHS are pivotal and depletable [8, 9]. Hence, a rational, efficient, and robust collaborative allocation of berths and yards can keep CTHS running smoothly and improve terminal operational efficiency dramatically [10].While developing the running plan by a fixed or flexible cycle, the operator needs to determine where the vessel is planned to moor and where the concomitant containers are expected to be stored. The quayside berth allocation and the yard bay allotment both influence the turnaround time and the hatch hours of calling liners. Besides, they also affect each other because both decide the transferring distance of yard trailers directly. Nevertheless, if only the optimal allocation of quayside berth or one of the storage yards is emphasized separately, the maximum utilization and synergy effect of berth and yard resources cannot be obtained and implemented. It is likely that either berth allocation or yard allotment is optimal. However, the collaborative allocation of berth and yard is not optimal, even not the feasible solution of high quality. Furthermore, the total horizontal transferring distance of yard tailers, which is between quayside and yard, is even less satisfactory. Therefore, it is necessary and significant to consider berth allocation and yard allotment simultaneously.In this paper, we aim to design and implement the berth and yard collaborative allocation for import and export synchronous operation (BYCA-IESO) optimization by computational logistics. In Section2, we conduct a literature review of berth allocation problem, yard allotment problem, and computational logistics. The problem description and abstraction of the BYCA-IESO with computational logistics are given in Section 3. We expatiate the formulating process of the BYCA-IESO model in Section 4, and the solutions to BYCA-IESO with different time ticks and allocation strategies are also introduced in this section. In Section 5, the numerical experiments for BYCA-IESO are deigned, executed, contrasted, and evaluated according to the production practice at container terminals by different scheduling time ticks and collaborative allocation strategies within the conceptual framework of computational logistics. Section 6 concludes the paper with some discussions and extensions.


## 2. Literature Review and Related Works

The quayside berth and storage yard are the core resources of CTHS, and the resource utilization, handling capacity, and load balancing of both directly determine the formulation, implementation, and adjustment of container terminal production plan. Accordingly, the berth allocation problem (BAP) and the yard allocation problem (YAP) are two significant scheduling issues in CTHS, which both have the complexity of nonlinearity and uncertainty and are difficult to describe with accurate mathematical models [11–17]. The berth allocation of calling liners affects the yard allotment of import and export containers synchronously, while the resource distribution of storage yard has also a powerful influence on the berth allocation efficiency. The resource allocation of berth and yard influence and constrain each other, and both have strong coupling. Consequently, the service level of CTHS depends on the collaborative allocation and integrated scheduling ability of the above two core resources to a large extent. In order to improve the service level of CTHS, scholars have done a series of research on the BAP, YAP, and the cooperative operation between them.The BAP has always been the focus and difficulty of scholars’ research. In the research of BAP, some scholars have studied the discrete berth scheduling problem. The berth scheduling problem is to reasonably assign the berth of terminal to the given vessels, optimizing the total service time and the utilization of berth [18]. Imai et al. [19] discussed the static berth scheduling problem and established a mathematical model aiming at minimizing the total stay time of ships in port and the dissatisfaction of ship berthing. Hammouti Issam et al. [20] considered the situations that two vessels could moor in a berth at the same time into the model and aimed to optimize the staying cost of vessels at the terminal. Xiang et al. [21] analyzed the factors that influence the execution of operation plan in reality. They proposed a mixed integer programming model to optimize the baseline cost. Xiang and Liu [8] minimized the total cost of deviations between the planned and expected berthing time of the vessel. Agra and Oliveira [22] introduced a model to minimize the service completion time of liners. Barbosa et al. [23] considered the time window constraints in solving discrete berth allocation problem. Sheikholeslami [24] et al. aimed to minimize the vessels’ delay time of departure and proposed a model to realize the goal by considering tide effects in terminal with discrete berth.In fact, in order to make better use of scarce shoreline resources, most berths of container terminals are regarded as being continuously distributed. Yang [25] et al. considered the problem of dynamic arrival of ships under continuous berths and established an integer linear programming model with the goal of minimizing the service time of ships in port. Liu [26] et al. aimed to improve the service level by considering some uncertain factors about the arrival and operation time of vessels. Malekahmadi et al. [27] proposed a model to minimize the time of waiting berthing and the total handling time. Thanos [28] et al. aimed to minimize the container transshipment distances between the berth and yard area. Wang [29] et al. intended to optimize the total delay time of completing the operation, cost of quay crane, and carbon emission tax. Abou Kasm [30] et al. introduced a model to optimize the berth and quay crane scheduling, minimizing the total time consumption of waiting to handling. Tan [31] et al. integrated the berth allocation problem and quay crane assignment problem to minimize the time of waiting and delay departure. Al-Refaie and Abedalqader [32] considered continuous berth scheduling problem and proposed two models that mainly aimed to reduce terminal operating costs and improve terminal operation efficiency. Mahpour [33] et al. analyzed several factors affecting terminal operation and obtained the best time to serve vessels. Lin [34] et al. optimized the berth allocation in container terminal by considering the service time and penalty cost.In reality, quay berths and storage yards, as scarce resources of container terminals, cannot expand indefinitely. With the growth of container throughput, the problems of terminal congestion and low operation efficiency become more and more serious and prominent. In view of the current situations, scholars have considered the scheduling of berths and storage yards synchronously, but the existing results are relatively few. Zhen [35] et al. established a mixed integer model to minimize the ship service cost and yard transportation length by integrating the berth plate and yard plate planning, considering the uncertainty of the location of the ship occupying the berth and the time in port. Le and Zhao [36] dynamically linked berth scheduling and yard container area assignment through the optimal berthing position and established a nonlinear mixed integer model with the goal of minimizing the total activity cost, but it did not consider the time factor. Wang et al. [37] also proposed a mixed integer programming model with the minimum total activity cost for the comprehensive optimization of wharf resources such as discrete berths, yard space, and quay cranes. Li and Jia [38] established a joint optimization model for berth and yard scheduling under uncertain environment by introducing scene variables, which could effectively reduce the wharf congestion rate, but it still did not consider the influence of time factor. Han [39] et al. considered the uncertain factors of ship arrival time and established a mixed integer programming model based on random scenarios. However, in terms of yard scheduling, it only included the constraints related to the total amount of import and export container area. Guo et al. [40, 41] meant to optimize the yard trailer travel distance in discrete terminal, but the authors only considered the operation of export container in container terminal. Obviously, the operation of import containers also affects the yard trailer travel distance. Nishimura [42] aimed to minimize the total service time by estimating the handling time in discrete berth. Jian et al. [43] proposed a strategy to solve the berthing congestion problem considering the integrated scheduling in berth and yard system in transshipment container terminal. Hendriks [44] et al. presented the berth and yard allocation problem at a tactical level and intended to minimize the total container travel distance by solving a mixed integer quadratic program model. Ma [45] et al. considered the berth allocation problem and yard allocation problem simultaneously to minimize the total travel container distance with discrete berth at container terminals. Xu [46] et al. put forward a mixed integer nonlinear programming to minimize the total operating time of CTHS.Most scholars have considered the berth and yard allocation in transshipment container terminal when researching on the integrated scheduling of the berth and yard. In addition, some researchers have also considered the operation scheduling for import and export containers. Little research on integrating the berth and yard scheduling simultaneously in general container terminal has been done, compared with that in transshipment terminal. However, the existing discussion only considered the operation of export containers. Actually, the import and export containers coexist in operation of container terminals. We cannot simply optimize the handling of export container or import container in making the running plan of berth and yard. In this paper, we expect to integrate the berth and yard scheduling for import and export container in CTHS simultaneously, which is the superposition of nondeterministic polynomial complete problems essentially. The proposal of computational logistics indicates a new approach to the BYCA-IESO with the controllable, customizable, and acceptable computational complexity [47]. The container terminal oriented logistics generalized computation (CTO-LGC) provides the foundation of abstraction and automation for the BYCA-IESO [48]; moreover, the corresponding computing and storage abstract and automated architecture have been initially defined [49]. Consequently, the multiobjective optimization of BYCA-IESO is supposed to be designed and implemented by computational logistics, which is just about to minimize the time of vessels consumed and the transferring distances of yard trailers at the container terminal by optimizing the assignment of quayside berth and the storage yard for import and export containers synchronously.


## 3. Problem-Oriented Exploration of Berth and Yard Joint Scheduling by Computational Logistics

### 3.1. Problem-Oriented Exploration Using Computational Logistics

In view of the current research situations and ongoing practical requirements, we focus on the BYCA-IESO at container terminals by computational logistics. The mixed integer quadratic programming (MIQP) models for BYCA-IESO are proposed to optimize the integrated scheduling of berth and yard simultaneously. The fundamental principles and internal mechanisms are transferred, customized, and targeted purposefully from computer science and engineering to BYCA-IESO within the conceptual framework of computational logistics. As a matter of fact, the classic operation research and the distinct computational logistics are integrated to be as a comprehensive solution to scheduling and decision of CTHS whether in theory or in practice. This is exactly one of the unfinished works in our previous research on computational logistics, and it is just about an important piece of the puzzle for computational logistics. The problem-oriented exploration of BYCA-IESO is a sound, positive, and representative annotation and demonstration of the above critical piece.Now, the BYCA-IESO is abstracted from the visual angle of problem-oriented exploration by the computational logistics. The resource discretization and time tick are the central themes of the abstraction and automation of BYCA-IESO by computational logistics [50]. On the one hand, the resource abstraction of quayside berth is the kernel of BYCA-IESO for the computing mechanization and automation in a broad sense. The traditional BAP can be categorized into two broad categories: discrete berth allocation and continuous berth allocation. We combine both approaches to deal with BAP. With reference to the design ideas and working principles of the computer systems, the quayside berth is resource discretized as fine-grained as possible to make full use of berth resources. The flat length can be 10 meters or 15 meters, or 20 meters at the most, and it is based on the plane layout, equipment configuration, calling liners, and target throughput of the given container terminal. In consideration of the planning cycle periods in CTHS, the decision time tick of BYCA-IESO may be quarter hour, half an hour, or one hour for berth allocation. The above space and time partition matrices are the scheduling cores of the BYCA-IESO.In a similar manner, the storage yard is divided into four kinds of container sections, which are the import heavy container zones, the import empty container zones, the export heavy container zones, and the export empty container zones, respectively. Every kind of yard zone contains a certain number of blocks, and each block covers some bays, and every bay is a two-dimensional physical matrix for container storage. The storage capacity of every block is constant, which is determined by the civil infrastructure, plane layout, handling technology, and equipment configuration. Consider that every block serves some different purposes that include loading, discharging, collection, distribution, marshalling, and pre-relocation simultaneously. As a result, one block is only assigned to a couple of calling liners at a particular moment. The above is the very discrete space abstraction of storage yard. Meanwhile, the decision time tick of BYCA-IESO is half an hour, one, two or three hours, and four hours at most, for yard allocation according to the actual situations of production practice in CTHS. In other words, the CTO-LGC in quayside berth and storage yard is implemented and executed by the synchronous or asynchronous modes. The quayside berth and storage yard both are the core memory resources at container terminals if the CTHS is considered as the CTO-LGC dedicated system by computational logistics, which two correspond, respectively, to the processor cache and the main memory of CTHS. Thereupon, the above scheduling mode with hybrid time ticks is highly similar to the running of computer systems, especially between processor cache and main memory.To be more specific, more information about the quayside berth layout and the storage yard configuration of the CTHS is shown in Figure1. The proposed model is based on the operational analysis of the handling technology and service objects at container terminals. From Figure 1, we can see the logistics service process of the import and export containers for calling liners in terms of quayside berth and storage yard. It mainly consists of three parts, which are shown as follows.(i)
Quay crane loading and discharging containers: after the calling liners moor by the quayside berth, the quay crane (QC) along the quayside is to discharge firstly their import containers needed to be unloaded and then load the export containers that need to be loaded to the given vessel. All arrived vessels must complete this operation within a planning time window according to the shipping schedule.(ii)
Yard trailer horizontal transferring containers: the import containers unloaded from the vessel mooring the berth are going to be horizontally transferred to the assigned blocks of storage yard by the yard trailer (YT). For the export containers needed to be loaded to the vessel, they are also transferred to the assigned berth by the YT. In terms of the whole container terminal, the CTO-LGC for import and export containers is implemented and executed synchronously from an executive level.(iii)
Yard crane stacking, retrieving, receiving, and fetching containers: when the unloaded import containers are transported to the assigned blocks of yard, the yard crane (YC) is to discharge them from the YTs to the blocks of storage yards. The blocks are going to conserve them for a certain time. For the export containers needed to be loaded to the vessels, they are usually stacked in the assigned blocks of yards for a period of time before the vessels arrive at the terminal. When the liners arrive at the terminal, the export containers are going to be retrieved and loaded from the block to the YTs by the YC. In addition, the YC fulfills the functions of receiving and fetching containers during the collection and distribution of CTHS.Figure 1
Abstract collaborative storage architecture for CTHS by computational logistics.By reasons of the foregoing, the QC, YT, and YC all can be abstracted as the parallel, heterogeneous, and reconfigurable CTO-LGC processor farms by computational logistics. Consequently, the quayside berth and the storage yard construct the heterogeneous, three-dimensional, discrete, and unit collaborative storage architecture, which is similar to the synergy between processor cache and main memory in computer systems. Accordingly, both form the operational center of CTHS. Naturally, the problem-oriented exploration of BYCA-IESO become an important issue of planning and scheduling of CTHS, especially at the tactical and executive levels.


### 3.2. Berth and Yard Collaborative Allocation Problem Description

No matter in theory or in practice, the shipping company can provide the estimated time of arrival, estimated time of departure, and the number of containers to be loaded and unloaded for the liners. The terminal operator can make the berth allocation plan according to the above obtained information, and the container terminal operator is to formulate a loading and discharging plan of the import and export containers for the calling liners. When the planners assign the berth along quayside and the blocks on yard for the given calling liner, they must take its arrival time, departure time, and handling container volume into account.Actually, the container ship is dynamically arriving at the terminal, instead of just following the schedule. Thus, the terminal operator can only formulate the loading and unloading plan according to a certain planning time window. At the same time, the working plan is rolling update dynamically. The planning time window consists of several time segments. The length of time segment is just the above time tick of BYCA-IESO, which is the running frequency of CTHS and may be different for the berth allocation and the yard allotment separately.The container ship arrived at the port within a planning window is going to occupy the quayside berth and storage yard resources in a certain period of time dynamically. It should be emphasized that the holding time of berth and yard is distinctly different for a container ship, and the latter is far longer than the former because of the depositing time of export containers and the retention time of import containers.However, the working space resources of quayside berth and storage yard in CTHS are very limited and scarce, so the terminal operator must ensure to reduce the occupation of berth and yard by vessels as far as possible under the conditions of meeting the running requirements of vessels to improve the operational efficiency of the port. When the vessels within the planning window arrive at the terminal one after another, they are to moor at the assigned berth according to the production plan formulated by the terminal operator to launch the operation of unloading import containers and loading export containers. The YT implements the horizontal transferring of the import containers unloaded from vessels to the designated blocks, and the YT also executes the horizontal transferring of the export containers in the designated spot that need be loaded to the vessels to the assigned quayside berth.At the same time, the distribution of the quayside berth and the storage yard determine the total horizontal transferring distances of YTs, which affect the loading and unloading efficiency of the vessel in significant measure. Therefore, it is extremely necessary to integrate scheduling of the berth and yard by considering the situations of the berth allocation, the yard allocation, and the total horizontal transferring distances of YTs, so as to improve the CTO-LGC running efficiency of CTHS. Consequently, the occupancy resources of quayside berth and storage yard by vessels can be represented from the dimensions of time and space under the multiple constraints. It is a typical multispace cooperative allocation problem by computational logistics. There are already available, mature, efficient, and robust solutions to this problem, which is just the classical and productive collaboration between processor cache and main memory in computer systems. The problem description of BYCA-IESO proceeds as follows.In terms of multiple time dimensional constraints, for the BAP, there are three major parts of time to be considered in the BYCA-IESO as follows. (1) The first is the time of waiting for berth on the vessels after it arrives at the port to prepare for loading and discharging operations. (2) The second is the handling time of the moored vessels. (3) The last is the hold-up time that moored vessels occupy the berth. For the YAP, it is mainly to meet the requirements of container temporary storage. For import containers, they still need to be retained for a period of time after being unloaded and transported to the storage yard for storage. Therefore, for the import containers, the resource occupying duration of import storage yard is from its time of beginning unload operation to its ending storage time in yard. For export containers, the port usually performs the pre-storage operation, which is delivering all containers that need to be loaded onto the arrived vessel to the storage yard before the vessel arrives at the port. Therefore, the period time of the export containers occupying the blocks of the export storage yard is from the start time of the pre-storage operation to the end time of the loading for the specific liner.In terms of multiple space dimensional constraints, terminal operators assign quayside berths according to the length of vessels and determine the range of container blocks that can be allocated to vessels according to the quantity of import and export containers that need to be loaded and discharged. The berth allocation of vessels affects their choice of blocks that need to be occupied in the yard. At the same time, the option of the occupied blocks on storage yard also exerts significant influences over berth allocation. As a CTO-LGC horizontal transferring processor, the YT connects the wharf apron production subsystem and the storage yard service subsystem. Therefore, in order to jointly dispatch the berth and yard and improve the CTO-LGC efficiency of the terminal, the travel path of the YT must be optimized, rather than only considering from the single dimension of time constraints. In addition, in terms of berths allocation and yard allotment, there are certain constraints in space constraints. For example, the berth can only be occupied by one vessel at most at one point, and no more than two vessels can be allowed to carry out the stacking operation at the same time in the same block.The above abstraction of BYCA-IESO is remarkably similar to the storage architecture in computer systems. Nevertheless, the running of BYCA-IESO is much more complicated than the situations of computer systems because the constraint conditions of the BYCA-IESO are more complex and harsher than the corresponding part of computer systems. The changes in constraint conditions are mainly because the target objects of CTO-LGC, which is just about manifold liners and containers, have numerous physical properties that include physical dimensions, handling specifications, logistics execution, collection and distribution modes, and so on.In this paper, we aim to optimize the total consumption time of vessels at the terminal and the total transferring distances of the YT during a planning window. For the terminal operator, the most intuitive way to improve the operation efficiency of the CTHS is to optimize the time consumption of arriving ships and the travel path of the YTs. For the shipping company, the less the time spent by vessels at the target port, the smaller the cost of cargo transportation and the higher the efficiency of cargo transportation are. Therefore, it is reasonable to take the total consumption time of vessels at the given terminal and the total transferring distances of the YT set as the optimization objectives of BYCA-IESO.


## 3.1. Problem-Oriented Exploration Using Computational Logistics

In view of the current research situations and ongoing practical requirements, we focus on the BYCA-IESO at container terminals by computational logistics. The mixed integer quadratic programming (MIQP) models for BYCA-IESO are proposed to optimize the integrated scheduling of berth and yard simultaneously. The fundamental principles and internal mechanisms are transferred, customized, and targeted purposefully from computer science and engineering to BYCA-IESO within the conceptual framework of computational logistics. As a matter of fact, the classic operation research and the distinct computational logistics are integrated to be as a comprehensive solution to scheduling and decision of CTHS whether in theory or in practice. This is exactly one of the unfinished works in our previous research on computational logistics, and it is just about an important piece of the puzzle for computational logistics. The problem-oriented exploration of BYCA-IESO is a sound, positive, and representative annotation and demonstration of the above critical piece.Now, the BYCA-IESO is abstracted from the visual angle of problem-oriented exploration by the computational logistics. The resource discretization and time tick are the central themes of the abstraction and automation of BYCA-IESO by computational logistics [50]. On the one hand, the resource abstraction of quayside berth is the kernel of BYCA-IESO for the computing mechanization and automation in a broad sense. The traditional BAP can be categorized into two broad categories: discrete berth allocation and continuous berth allocation. We combine both approaches to deal with BAP. With reference to the design ideas and working principles of the computer systems, the quayside berth is resource discretized as fine-grained as possible to make full use of berth resources. The flat length can be 10 meters or 15 meters, or 20 meters at the most, and it is based on the plane layout, equipment configuration, calling liners, and target throughput of the given container terminal. In consideration of the planning cycle periods in CTHS, the decision time tick of BYCA-IESO may be quarter hour, half an hour, or one hour for berth allocation. The above space and time partition matrices are the scheduling cores of the BYCA-IESO.In a similar manner, the storage yard is divided into four kinds of container sections, which are the import heavy container zones, the import empty container zones, the export heavy container zones, and the export empty container zones, respectively. Every kind of yard zone contains a certain number of blocks, and each block covers some bays, and every bay is a two-dimensional physical matrix for container storage. The storage capacity of every block is constant, which is determined by the civil infrastructure, plane layout, handling technology, and equipment configuration. Consider that every block serves some different purposes that include loading, discharging, collection, distribution, marshalling, and pre-relocation simultaneously. As a result, one block is only assigned to a couple of calling liners at a particular moment. The above is the very discrete space abstraction of storage yard. Meanwhile, the decision time tick of BYCA-IESO is half an hour, one, two or three hours, and four hours at most, for yard allocation according to the actual situations of production practice in CTHS. In other words, the CTO-LGC in quayside berth and storage yard is implemented and executed by the synchronous or asynchronous modes. The quayside berth and storage yard both are the core memory resources at container terminals if the CTHS is considered as the CTO-LGC dedicated system by computational logistics, which two correspond, respectively, to the processor cache and the main memory of CTHS. Thereupon, the above scheduling mode with hybrid time ticks is highly similar to the running of computer systems, especially between processor cache and main memory.To be more specific, more information about the quayside berth layout and the storage yard configuration of the CTHS is shown in Figure1. The proposed model is based on the operational analysis of the handling technology and service objects at container terminals. From Figure 1, we can see the logistics service process of the import and export containers for calling liners in terms of quayside berth and storage yard. It mainly consists of three parts, which are shown as follows.(i)
Quay crane loading and discharging containers: after the calling liners moor by the quayside berth, the quay crane (QC) along the quayside is to discharge firstly their import containers needed to be unloaded and then load the export containers that need to be loaded to the given vessel. All arrived vessels must complete this operation within a planning time window according to the shipping schedule.(ii)
Yard trailer horizontal transferring containers: the import containers unloaded from the vessel mooring the berth are going to be horizontally transferred to the assigned blocks of storage yard by the yard trailer (YT). For the export containers needed to be loaded to the vessel, they are also transferred to the assigned berth by the YT. In terms of the whole container terminal, the CTO-LGC for import and export containers is implemented and executed synchronously from an executive level.(iii)
Yard crane stacking, retrieving, receiving, and fetching containers: when the unloaded import containers are transported to the assigned blocks of yard, the yard crane (YC) is to discharge them from the YTs to the blocks of storage yards. The blocks are going to conserve them for a certain time. For the export containers needed to be loaded to the vessels, they are usually stacked in the assigned blocks of yards for a period of time before the vessels arrive at the terminal. When the liners arrive at the terminal, the export containers are going to be retrieved and loaded from the block to the YTs by the YC. In addition, the YC fulfills the functions of receiving and fetching containers during the collection and distribution of CTHS.Figure 1
Abstract collaborative storage architecture for CTHS by computational logistics.By reasons of the foregoing, the QC, YT, and YC all can be abstracted as the parallel, heterogeneous, and reconfigurable CTO-LGC processor farms by computational logistics. Consequently, the quayside berth and the storage yard construct the heterogeneous, three-dimensional, discrete, and unit collaborative storage architecture, which is similar to the synergy between processor cache and main memory in computer systems. Accordingly, both form the operational center of CTHS. Naturally, the problem-oriented exploration of BYCA-IESO become an important issue of planning and scheduling of CTHS, especially at the tactical and executive levels.


## 3.2. Berth and Yard Collaborative Allocation Problem Description

No matter in theory or in practice, the shipping company can provide the estimated time of arrival, estimated time of departure, and the number of containers to be loaded and unloaded for the liners. The terminal operator can make the berth allocation plan according to the above obtained information, and the container terminal operator is to formulate a loading and discharging plan of the import and export containers for the calling liners. When the planners assign the berth along quayside and the blocks on yard for the given calling liner, they must take its arrival time, departure time, and handling container volume into account.Actually, the container ship is dynamically arriving at the terminal, instead of just following the schedule. Thus, the terminal operator can only formulate the loading and unloading plan according to a certain planning time window. At the same time, the working plan is rolling update dynamically. The planning time window consists of several time segments. The length of time segment is just the above time tick of BYCA-IESO, which is the running frequency of CTHS and may be different for the berth allocation and the yard allotment separately.The container ship arrived at the port within a planning window is going to occupy the quayside berth and storage yard resources in a certain period of time dynamically. It should be emphasized that the holding time of berth and yard is distinctly different for a container ship, and the latter is far longer than the former because of the depositing time of export containers and the retention time of import containers.However, the working space resources of quayside berth and storage yard in CTHS are very limited and scarce, so the terminal operator must ensure to reduce the occupation of berth and yard by vessels as far as possible under the conditions of meeting the running requirements of vessels to improve the operational efficiency of the port. When the vessels within the planning window arrive at the terminal one after another, they are to moor at the assigned berth according to the production plan formulated by the terminal operator to launch the operation of unloading import containers and loading export containers. The YT implements the horizontal transferring of the import containers unloaded from vessels to the designated blocks, and the YT also executes the horizontal transferring of the export containers in the designated spot that need be loaded to the vessels to the assigned quayside berth.At the same time, the distribution of the quayside berth and the storage yard determine the total horizontal transferring distances of YTs, which affect the loading and unloading efficiency of the vessel in significant measure. Therefore, it is extremely necessary to integrate scheduling of the berth and yard by considering the situations of the berth allocation, the yard allocation, and the total horizontal transferring distances of YTs, so as to improve the CTO-LGC running efficiency of CTHS. Consequently, the occupancy resources of quayside berth and storage yard by vessels can be represented from the dimensions of time and space under the multiple constraints. It is a typical multispace cooperative allocation problem by computational logistics. There are already available, mature, efficient, and robust solutions to this problem, which is just the classical and productive collaboration between processor cache and main memory in computer systems. The problem description of BYCA-IESO proceeds as follows.In terms of multiple time dimensional constraints, for the BAP, there are three major parts of time to be considered in the BYCA-IESO as follows. (1) The first is the time of waiting for berth on the vessels after it arrives at the port to prepare for loading and discharging operations. (2) The second is the handling time of the moored vessels. (3) The last is the hold-up time that moored vessels occupy the berth. For the YAP, it is mainly to meet the requirements of container temporary storage. For import containers, they still need to be retained for a period of time after being unloaded and transported to the storage yard for storage. Therefore, for the import containers, the resource occupying duration of import storage yard is from its time of beginning unload operation to its ending storage time in yard. For export containers, the port usually performs the pre-storage operation, which is delivering all containers that need to be loaded onto the arrived vessel to the storage yard before the vessel arrives at the port. Therefore, the period time of the export containers occupying the blocks of the export storage yard is from the start time of the pre-storage operation to the end time of the loading for the specific liner.In terms of multiple space dimensional constraints, terminal operators assign quayside berths according to the length of vessels and determine the range of container blocks that can be allocated to vessels according to the quantity of import and export containers that need to be loaded and discharged. The berth allocation of vessels affects their choice of blocks that need to be occupied in the yard. At the same time, the option of the occupied blocks on storage yard also exerts significant influences over berth allocation. As a CTO-LGC horizontal transferring processor, the YT connects the wharf apron production subsystem and the storage yard service subsystem. Therefore, in order to jointly dispatch the berth and yard and improve the CTO-LGC efficiency of the terminal, the travel path of the YT must be optimized, rather than only considering from the single dimension of time constraints. In addition, in terms of berths allocation and yard allotment, there are certain constraints in space constraints. For example, the berth can only be occupied by one vessel at most at one point, and no more than two vessels can be allowed to carry out the stacking operation at the same time in the same block.The above abstraction of BYCA-IESO is remarkably similar to the storage architecture in computer systems. Nevertheless, the running of BYCA-IESO is much more complicated than the situations of computer systems because the constraint conditions of the BYCA-IESO are more complex and harsher than the corresponding part of computer systems. The changes in constraint conditions are mainly because the target objects of CTO-LGC, which is just about manifold liners and containers, have numerous physical properties that include physical dimensions, handling specifications, logistics execution, collection and distribution modes, and so on.In this paper, we aim to optimize the total consumption time of vessels at the terminal and the total transferring distances of the YT during a planning window. For the terminal operator, the most intuitive way to improve the operation efficiency of the CTHS is to optimize the time consumption of arriving ships and the travel path of the YTs. For the shipping company, the less the time spent by vessels at the target port, the smaller the cost of cargo transportation and the higher the efficiency of cargo transportation are. Therefore, it is reasonable to take the total consumption time of vessels at the given terminal and the total transferring distances of the YT set as the optimization objectives of BYCA-IESO.


## 4. Model Formulation of Berth and Yard Collaborative Allocation with Computational Logistics

We have described the main service processes of the berth and yard in the Section3 and are aiming at the multiobjective optimization of BYCA-IESO. To achieve the optimization goal, we construct and design the MIQP models by the two different integrated scheduling strategies. One of the integrated scheduling strategies considers a simple situation that the time ticks for the quayside berth service system and storage yard production system are synchronous. We call this strategy berth and yard integrated scheduling with synchronous decision time ticks (BYIS-SDTT). The other scheduling strategy is more flexible and more complicated than BYIS-SDTT. In the actual operations in CTHS, the time ticks for the berth service subsystem and yard operating subsystem are asynchronous while assigning the berth and yard at container terminals. We call it berth and yard integrated scheduling with asynchronous decision time ticks (BYIS-ADTT). Actually, the BYIS-SDTT is the basic scheduling strategy compared to the BYIS-ADTT, and the BYIS-SDTT is a particular case of the BYIS-ADTT. We also propose two other different scheduling strategies for comparison based on the following MIQP models. Thus, there are mainly four kinds of berth and yard collaborative allocation scheduling strategies in this paper. The first two kinds are the main models based on integrated scheduling strategy that are BYIS-SDTT and BYIS-ADTT. The latter two scheduling strategies are for comparisons with the first two strategies based on staged scheduling strategy. In this section, we are going to define the formulation of the BYCA-IESO model and all the four collaborative allocation strategies for berth and yard.


### 4.1. Description of Symbols and Variables

#### 4.1.1. Input Variables

V: set of all vesselsi.J: set of berth segment k.T: set of all time periodst that allow vessels to loading and unloading operation.T1: set of all time periodst1 that allow vessels to perform pre-storage operation.T2:set of all time periodst2 that allow unloaded containers to retain in the storage yard.S1: set of all blocks hl of the import heavy container storage yard.S2: set of all blocks el of the import empty container storage yard.Q1: set of all blocks hq of the export heavy container storage yard.Q2: set of all blocks eq of the export empty container storage yard.αi1,βi1: the range of blocks that vessel i can occupy in import heavy container yard.αi2,βi2: the range of blocks that vessel i can occupy in import empty container yard.ξi1,ηi1: the range of blocks that vessel i can occupy in export heavy container yard.ξi2,ηi2: the range of blocks that vessel i can occupy in export empty container yard.Li: the length of vessel i.Ai: the arrival time of vessel i.Hi: the loading and unloading operation time of vessel i.Pti: the pre-storage operation time of vessel i.Eti: the retain time of vessel i.Dihl: the distance from the berth segment that vessel i occupied to the block hl.Diel: the distance from the berth segment that vessel i occupied to the block el.Dihq: the distance from the berth segment that vessel i occupied to the block hq.Dieq: the distance from the berth segment that vessel i occupied to the block eq.M: a sufficiently large real number.ω1: the weight coefficient of the total consumption time of the given calling liner set in the objective function.ω2: the weight coefficient of the total horizontal distances of the given yard trail set in the objective function.


#### 4.1.2. Decision Variables

bi: the upper bound of berth segment that vessel i occupied.Hsi: the start time of the pre-storage operation for vessel i.gi: the time that vessel i starts mooring by the assigned berth.si: the start loading and unloading operation time of vessel i.ei: the end loading and unloading operation time of vessel i.di: the departure time of vessel i.Hri: the time that the import containers of vessel i leave the import container yard.Cij: binary variables, 1 if vessel i is on the left side of vessel j, and 0 otherwise.Aij: binary variables, 1 if vessel i arrives earlier than vessel j, and 0 otherwise.Nik: binary variables, 1 if vessel i is moored in berth segment k, and 0 otherwise.Xit11: binary variables, 1 if the import container of vessel i is in the import container storage yard area at time t, and 0 otherwise.Xit22: binary variables, 1 if the export container of vessel i is in the export container storage yard at time t, and 0 otherwise.σihl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard, and 0 otherwise.σiel2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard, and 0 otherwise.φihq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard, and 0 otherwise.φieq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard, and 0 otherwise.μit1hl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard at time t, and 0 otherwise.μit1el2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard at time t, and 0 otherwise.υit2hq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard at time t, and 0 otherwise.υit2eq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard at time t, and 0 otherwise.


### 4.2. Model Formulation of Berth and Yard Integrated Scheduling with Synchronous Decision Time Tick

The objective function of the MIQP model for the integrated scheduling of berth and yard resources is to optimize the berth and yard scheduling scheme of expected arriving ships within a flexible and tunable planning cycle from multiple operational constraints originating from the dimensions of time and space. For the time dimension, this paper mainly optimizes the total consumption time at the terminal. For the spatial dimension, this paper mainly aims to optimize the total horizontal transferring distances of the YT.The total consumption time in CTHS in a planning cycle mainly includes three indicators, which are the waiting time of liners for mooring, the berthing time of vessels at the terminal, and the handling time of liners. The waiting time of liners for mooring means the waiting time of all vessels before they moor to the berth after arriving at the port in a given planning cycle. The berthing time of vessels at the terminal refers to the total time of all vessels occupying berths in the planning cycle. The handling time is the time consumption for the execution of loading and discharging operation of all vessels in the planning cycle.The waiting time of vesseli for mooring can be calculated by the following formula:(1)F1i=gi−Ai.The berthing time of vesseli at the port can be calculated by the following formula:(2)F2i=di−gi.The loading and unloading time of vesseli can be calculated by the following formula:(3)F3i=ei−si.Therefore, the total time consumption of vesseli at the port in a planning period can be obtained by the following formula:(4)Fi=f1i+f2i+f3i.The total horizontal transferring distances of the YT refers to the distances from the mooring location of vesseli to the blocks it occupies on the storage yard, which can be calculated by the following formula:(5)Ri=Nik⋅σihl1⋅Dihl1+σiel2⋅Diel2+φihq1⋅Dihq1+φieq2⋅Dieq2.Since the objective function involves the dimension of time and space and has different dimensions and dimensional units, in order to eliminate the dimensional influences between the two indicators, the data related to the two indicators need to be normalized to eliminate the unit limitation between the two indicators. As for the selection of normalization processing treatment, we adopt the max-min standardization method to carry out the normalization processing of objective function indicators. The formula of this method is as follows:(6)X′=X−minXmaxX−minX.The total time consumption at terminals and the total travel distances of the YT, which both constitute the objective function of BYCA-IESO, are not constant and are going to change with different scheduling schemes. Therefore, we adopt the empirical constantsm and n to represent the maximum and minimum values among them. Therefore, the normalization of the total consumption time at port and the total travel distance of the truck can be processed by the following formula:(7)F′i=fi−nm−n,R′i=ri−nm−n.Consequently, the proposed MIQP model of BYCA-IESO is formulated as follows:(8)MinZ=∑i∈Vω1⋅F’i+∑i∈Vω2⋅R’i,s.t.(9)Hsi=gi−Ai,∀i∈V,(10)Hri=ei+Eti,∀i∈V,(11)gi≥Ai,∀i∈V,(12)si−gi≥1,∀i∈V,(13)ei−si≥Hi,∀i∈V,(14)Di−ei≥1,∀i∈V,(15)Hsi≤t1⋅Xit11+M⋅1−Xit11,∀i∈V,∀t1∈T1,(16)Ei≥t1⋅Xit11,∀i∈V,∀t1∈T1,(17)∑t1∈T1Xit11=ei−Hsi+1,∀i∈V,(18)Hri≥t2⋅Xit22,∀i∈V,∀t2∈T2,(19)si≤t2⋅Xit22+M⋅1−Xit22,∀i∈V,∀t2∈T2,(20)∑t2∈T2Xit22=Hri−si+1,∀i∈V,(21)bi−Li≥0,∀i∈V,(22)di≤gj+M⋅1−Aij,∀i,j∈V,i≠j,(23)bi≤bj−Lj+M⋅1−Cij,∀i,j∈V,i≠j,(24)Aij+Aji+Cij+Cji≥1,∀i,j∈V,i≠j,(25)bi≥k⋅Nik,∀i∈V,∀k∈J,(26)bi≤k⋅Nik+M⋅1−Nik,∀i∈V,∀k∈J,(27)∑t2∈T2Nik=1,∀i∈V,(28)αi1≤∑l∈S1σil1≤βi1,∀i∈V,(29)αi2≤∑l∈S2σil2≤βi2,∀i∈V,(30)ξi1≤∑q∈Q1φiq1≤ηi1,∀i∈V,(31)ξi2≤∑q∈Q2φiq2≤ηi2,∀i∈V,(32)μit1l1≤σil1+Xit112,∀i∈V,∀t1∈T1,(33)μit1l1≥σil1+Xit11−12,∀i∈V,∀t1∈T1,(34)μit1l2≤σil2+Xit112,∀i∈V,∀t1∈T1,(35)μit1l2≥σil2+Xit11−12,∀i∈V,∀t1∈T1,(36)νit2q1≤φiq1+Xit222,∀i∈V,∀t2∈T2,(37)νit2q1≥φiq1+Xit22−12,∀i∈V,∀t2∈T2,(38)νit2q2≤φiq2+Xit222,∀i∈V,∀t2∈T2,(39)νit2q2≥φiq2+Xit22−12,∀i∈V,∀t2∈T2,(40)∑l∈S1μit1l1≤2,∀i∈V,∀t1∈T1,(41)∑l∈S2μit1l2≤2,∀i∈V,∀t1∈T1,(42)∑q∈Q1νit2q1≤2,∀i∈V,∀t2∈T2,(43)∑q∈Q2νit2q2≤2,∀i∈V,∀t2∈T2.Objective function (8) aims to minimize the weighted sum of the total time consumption at port and the total horizontal transferring distances of the YT for the all expected arriving vessels within a planning cycle. The summation of the two weight coefficients ω1 and ω2 is 1. Constraint (9) calculates the variable Hsi, and it means the start time of the pre-storage operation for vessel I that is equal to its arrival time Ai minus its export containers’ pre-storage operation time Pti. Constraint (10) calculates the variable Hri, and it means the end retention time of vessel i for its import containers that equals its end operating time ei plus its import container retention time Eti. Constraint (11) ensures that the vessel berthing completion time gi is not earlier than its arrival time Ai. Constraint (12) intends that the vessel launching loading and discharging operation time si is not earlier than its mooring completion time gi. Constraint (13) implies that the interval between the vessel starting handling operation time si and its ending handling operation time ei is greater than its operation time Hi. Constraint (14) ensures that the vessel departure time di is not earlier than its completion time ei. Constraints (15) and (16) determine the time period when the import containers are in the import container storage yard by variable Xit11. Constraint (17) guarantees that the variable Xit11 always equals 1 when the import container is in the import container storage yard at time t1. Constraints (18) and (19) determine the time period when the export containers are in the export container storage yard by variable Xit22. Constraint (20) guarantees that the variable Xit22 always equals 1 when the import container is in the import container storage yard at time t2. Constraint (21) ensures that the lower bound berth segment occupied by vessel i does not exceed the berth boundary. Constraints (23)–(25) guarantee that the berth occupied by the arrived vessel at the port has no conflict in the two dimensions of time and space. Constraints (25) and (26) determine the upper berth segment k the vessel i occupies by variable Nik. Constraint (27) ensures that the vessel i can only moor at a certain berth segment. Constraint (28) guarantees that the total blocks occupied by each vessel in the import heavy container storage yard do not exceed the upper and lower limits it can occupy. Constraint (29) ensures that the total blocks occupied by each vessel in the import empty container storage yard do not exceed the upper and lower limits it can occupy. Constraint (30) ensures that the total blocks occupied by the given vessel in the export heavy container storage yard do not exceed the upper and lower limits it can occupy. Constraint (31) ensures that the total blocks occupied by each vessel in the export empty container storage yard do not exceed the upper and lower limits it can take up. Constraints (32) and (33) imply that μit1hl1 = 1, if σihl1 = 1 and Xit11 = 1. It indicates whether each vessel occupies the export heavy container block hl at time t1. Constraints (34) and (35) imply that μit1el2 = 1, if σiel2 = 1 and Xit11 = 1. It indicates whether each vessel occupies the export empty container block el at time t1. Constraints (36) and (37) imply that υit2hq1 = 1, if υit2hq1 = 1 and Xit22 = 1. It indicates whether each vessel occupies the import heavy container block hq at time t2. Constraints (38) and (39) imply that υit2eq1 = 1, if υit2eq1 = 1 and Xit22 = 1. It indicates whether each vessel occupies the import empty container block eq at time t2. Constraint (40) ensures that the block hl in the import heavy container storage yard can occupy no more than two vessels simultaneously. Constraint (41) ensures that the block el in the import empty container storage yard can occupy no more than two vessels simultaneously. Constraint (42) ensures that the block hq in the export heavy container storage yard can occupy no more than two vessels simultaneously. Constraint (43) assures that the block eq in the export empty container storage yard can occupy no more than two vessels concurrently. The above is the MIQP for BYCA-IESO with the BYIS-SDTT, which makes good use of computational logistics to describe the operation of BYCA-IESO.


### 4.3. Model Formulation of Berth and Yard Integrated Scheduling with Asynchronous Decision Time Tick

In the proposed model in Section4.2, we mainly consider that the blocks on the storage yard cannot be occupied by more than three vessels at the same moment. The time tick for the berth allocation and yard allotment is the same. However, the updating speed of block occupation on the storage yard is slower than that of quayside berth in practice. Meanwhile, the container of each vessel stored in the yard areas takes much more time than its berthing time in the terminal. The container inventory in these four different container zones does not change in real time. Only when there are vessels to operate in the terminal, the inventory of yard areas will change. While the terminal operators allocate the berth and yard resources, they make allocation plans based on the different time ticks. That is, the hold-up time when the container is stored in the yard and the time when the ship is moored are not completely synchronized. Therefore, the scheduling time tick of the storage yard is not synchronized with that of the berth system.We build another model with wider applicability based on the model proposed in Section4.2. Most of the variables are the same between them. To formulate this new model, we firstly need to define several new variables, which are shown as follows:T3: set of all time periods t3 that allow vessels to perform pre-storage operation.T4: set of all time periods t4 that allow unloaded containers to retain in the storage yard.k: the time step length in yard is k times that in berth.Yit3: binary variables, 1 if the import container of vessel i is in the import container storage yard area at time t, and 0 otherwise.Yit4: binary variables, 1 if the export container of vessel i is in the export container storage yard at time t, and 0 otherwise.The new model is formulated as follows:(44)MinZ=∑i∈Vω1⋅F’i+∑i∈Vω2⋅R’i,s.t. constraints (9)–(32), and (41)–(44):(46)Yit3≥Xij1,(47)Yit3≤∑j=k⋅t3Xij1,(48)Yit4≥Xij2,(49)Yit4≤∑j=k⋅t4Xij2,(50)μit1l1≤σil1+Yit32,∀i∈V,∀t1∈T1,(51)μit1l1≥σil1+Yit3−12,∀i∈V,∀t1∈T1,(52)μit1l2≤σil2+Yit32,∀i∈V,∀t1∈T1,(53)μit1l2≥σil2+Yit3−12,∀i∈V,∀t1∈T1,(54)νit2q1≤φiq1+Yit42,∀i∈V,∀t2∈T2,(55)νit2q1≥φiq1+Yit4−12,∀i∈V,∀t2∈T2,(56)νit2q2≤φiq2+Yit42,∀i∈V,∀t2∈T2,(57)νit2q2≥φiq2+Yit4−12,∀i∈V,∀t2∈T2,(58)Xij1∈0,1,j=k⋅t3,k⋅t3−1,⋯,k⋅t3−k−1,(59)Xij2∈0,1,j=k⋅t4,k⋅t4−1,⋯,k⋅t4−k−1.Constraints (46)–(49) are to convert the scheduling time tick of the quayside berth to the time tick of the storage yard. Constraints (50) and (51) imply that μit3hl1 = 1, if σihl1 = 1 and Yit3 = 1. It indicates whether each vessel occupies the export heavy container block hl at time t3. Constraints (52) and (53) imply that μit3el2 = 1, if σiel2 = 1 and Xit22 = 1. It indicates whether each vessel occupies the export empty container block el at time t1. Constraints (54) and (55) imply that υit4hq1 = 1, if υit4hq1 = 1 and Yit4 = 1. It indicates whether each vessel occupies the import heavy container block hq at time t4. Constraints (56) and (57) imply that υit4eq1 = 1, if υit4eq1 = 1 and Yit4 = 1. It indicates whether each vessel occupies the import empty container block eq at time t4.Figure2 shows the procedure of the MIQP model for BYCA-IESO with the BYIS-ADTT to determine the berth and yard allocation scheme. Essentially, the MIQP model with the BYIS-ADTT covers that with the BYIS-SDTT. The difference between both is whether there is the component to determine if the scheduling time ticks for the quayside berth and the storage yard are identical or not. The MIQP model for BYCA-IESO with BYIS-SDTT is a special situation of that with BYIS-ADTT, and the scheduling time tick of the former for berth and yard allocation is the same. There are four main steps to determine the optimal berth and yard allocation scheme in the MIQP model for BYCA-IESO by BYIS-ADTT. The details of these steps are shown as follows.Figure 2
The solving process of integrated scheduling strategies for BYIS-SDTT and BYIS-ADTT.Step one: startup and initializing the values of input variables of the BYCA-IESO model.Step two: allocating the berth to each vessel expected to arrive. In this step, the mooring berth time, the start handling time, the end handling time, and the departure time for each liner all are determined explicitly. The berth segments that are occupied by each vessel are also confirmed. After working out the berth allocation plan for the liners, the related time to each service procedures for liners is acquired one by one. Subsequently, we need to determine whether there are some conflicts on the constraints of time and space. If there are any conflicts, restart the berth allocation scheduler. Otherwise, the procedure goes to the next step.Step three: allocating the yard blocks to each calling liners. The yard allocation is based on the berth allocation in step two. Above all, we allocate the four types of blocks to each vessel separately. Then, we need to determine the time spans for each type of containers occupying the blocks. After defining those, we judge whether the scheduling time ticks for berth service and yard production are same. If the two are identical, we directly determine the time span of occupying blocks based on the time tick related to the given vessel mooring by berth. If not, we need to convert the time tick for berthing into the time tick of storage yard running. After that, we can determine the occupying time of each vessel for the corresponding blocks. If each block in four types of yard zones is occupied by no more than three vessels, the procedure goes to the next step. If not, restart the yard allocation scheduler.Step four: compare and determine the optimal allocation scheme. In this step, the berth allocation and the yard allotment are determined simultaneously. We calculate the objective values and the corresponding gap. If the gap of objective value is lower than the default setting or the solving time reaches the total solving time limitation, the procedure stops solving and outputs the optimal schemes. If not, the procedure goes to step two.


### 4.4. Berth and Yard Collaborative Allocation Scheduling Strategy

As previously mentioned, we propose a MIQP model based on the integrated scheduling of berth and yard resources for the operations of import and export containers simultaneously, which are just about BYIS-SDTT and BYIS-ADTT. To verify the superiority and validity of the model and tactics, we will introduce other scheduling strategies to compare with them.The scheduling strategies to compare are the staged scheduling tactics, which are to consider berth allocation and yard allotment separately. In this section, we mainly define two staged collaborative allocation strategies, which are the berth and yard collaborative allocation with two staged independent scheduling strategy (BYCA-TSIS) and berth and yard collaborative allocation with two staged coupling scheduling strategy (BYCA-TSCS). The model of the BYCA-TSIS and BYCA-TSCS may be based on the BYCA-IESO model of BYIS-SDTT or BYIS-ADTT. On the one hand, the BYIS-SDTT or BYIS-ADTT is to verify the feasibility, availability, and superiority of the BYCA-IESO model. On the other hand, the BYCA-TSIS and BYCA-TSCS provide the staged and lightweight solution to BYCA-IESO with low computational complexity in comparison to BYIS-SDTT or BYIS-ADTT under the same running constraints of quayside berth and storage yard. Figure3 demonstrates the solving process of BYCA-TSIS and BYCA-TSCS from the perspective of contrast.Figure 3
The solving process of staged scheduling strategies for BYCA-TSIS and BYCA-TSCS.More importantly, from Figures2 and3, it is easy to conclude the similarities and differences among BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS. The optimization goals of the four tactics are all same that are just about the weighted sum of the total time consumption of calling liners and the total horizontal transferring distances of YTs. For one thing, whether the BYIS-SDTT or the BYIS-ADTT both take integrated scheduling of berth allocation and yard assignment into account. The two consider the optimization goals in multiple associated dimensions of time and space simultaneously and determine the optimal berth and yard allocation scheme as an organic whole.For another, as for BYCA-TSIS and BYCA-TSCS, the two are to determine the optimal berth allocation scheme firstly and then to determine the optimal yard allocation plan. In the first stage, both only consider minimizing the optimization objectives in terms of time costs for the berth allocation. In the second stage, they are only to optimize the horizontal transferring distances of YTs. From Figure3, the differences between BYCA-TSIS and BYCA-TSCS can be seen in the dotted box. Although they both optimize berth allocation and yard distribution, respectively, the BYCA-TSIS only focuses on the berth allocation problem in the first solution phase and does not consider the influence of berth optimization results on subsequent yard allocation. The influence is mainly in the aspect of the time costs. On the contrary, the BYCA-TSCS takes the yard allocation rules and constraints into account in the first solution stage while working out the berth allocation plan. Whether BYCA-TSIS or BYCA-TSCS, both are to determine the yard allocation plan in the time and space based on the foregoing berth scheme solved in the first stage. All four scheduling strategies provide different planning emphasis and scheduling paradigm for BYCA-IESO from the synergy service of processor cache and main memory by the abstraction and automation of computational logistics.


## 4.1. Description of Symbols and Variables

### 4.1.1. Input Variables

V: set of all vesselsi.J: set of berth segment k.T: set of all time periodst that allow vessels to loading and unloading operation.T1: set of all time periodst1 that allow vessels to perform pre-storage operation.T2:set of all time periodst2 that allow unloaded containers to retain in the storage yard.S1: set of all blocks hl of the import heavy container storage yard.S2: set of all blocks el of the import empty container storage yard.Q1: set of all blocks hq of the export heavy container storage yard.Q2: set of all blocks eq of the export empty container storage yard.αi1,βi1: the range of blocks that vessel i can occupy in import heavy container yard.αi2,βi2: the range of blocks that vessel i can occupy in import empty container yard.ξi1,ηi1: the range of blocks that vessel i can occupy in export heavy container yard.ξi2,ηi2: the range of blocks that vessel i can occupy in export empty container yard.Li: the length of vessel i.Ai: the arrival time of vessel i.Hi: the loading and unloading operation time of vessel i.Pti: the pre-storage operation time of vessel i.Eti: the retain time of vessel i.Dihl: the distance from the berth segment that vessel i occupied to the block hl.Diel: the distance from the berth segment that vessel i occupied to the block el.Dihq: the distance from the berth segment that vessel i occupied to the block hq.Dieq: the distance from the berth segment that vessel i occupied to the block eq.M: a sufficiently large real number.ω1: the weight coefficient of the total consumption time of the given calling liner set in the objective function.ω2: the weight coefficient of the total horizontal distances of the given yard trail set in the objective function.


### 4.1.2. Decision Variables

bi: the upper bound of berth segment that vessel i occupied.Hsi: the start time of the pre-storage operation for vessel i.gi: the time that vessel i starts mooring by the assigned berth.si: the start loading and unloading operation time of vessel i.ei: the end loading and unloading operation time of vessel i.di: the departure time of vessel i.Hri: the time that the import containers of vessel i leave the import container yard.Cij: binary variables, 1 if vessel i is on the left side of vessel j, and 0 otherwise.Aij: binary variables, 1 if vessel i arrives earlier than vessel j, and 0 otherwise.Nik: binary variables, 1 if vessel i is moored in berth segment k, and 0 otherwise.Xit11: binary variables, 1 if the import container of vessel i is in the import container storage yard area at time t, and 0 otherwise.Xit22: binary variables, 1 if the export container of vessel i is in the export container storage yard at time t, and 0 otherwise.σihl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard, and 0 otherwise.σiel2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard, and 0 otherwise.φihq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard, and 0 otherwise.φieq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard, and 0 otherwise.μit1hl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard at time t, and 0 otherwise.μit1el2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard at time t, and 0 otherwise.υit2hq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard at time t, and 0 otherwise.υit2eq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard at time t, and 0 otherwise.


## 4.1.1. Input Variables

V: set of all vesselsi.J: set of berth segment k.T: set of all time periodst that allow vessels to loading and unloading operation.T1: set of all time periodst1 that allow vessels to perform pre-storage operation.T2:set of all time periodst2 that allow unloaded containers to retain in the storage yard.S1: set of all blocks hl of the import heavy container storage yard.S2: set of all blocks el of the import empty container storage yard.Q1: set of all blocks hq of the export heavy container storage yard.Q2: set of all blocks eq of the export empty container storage yard.αi1,βi1: the range of blocks that vessel i can occupy in import heavy container yard.αi2,βi2: the range of blocks that vessel i can occupy in import empty container yard.ξi1,ηi1: the range of blocks that vessel i can occupy in export heavy container yard.ξi2,ηi2: the range of blocks that vessel i can occupy in export empty container yard.Li: the length of vessel i.Ai: the arrival time of vessel i.Hi: the loading and unloading operation time of vessel i.Pti: the pre-storage operation time of vessel i.Eti: the retain time of vessel i.Dihl: the distance from the berth segment that vessel i occupied to the block hl.Diel: the distance from the berth segment that vessel i occupied to the block el.Dihq: the distance from the berth segment that vessel i occupied to the block hq.Dieq: the distance from the berth segment that vessel i occupied to the block eq.M: a sufficiently large real number.ω1: the weight coefficient of the total consumption time of the given calling liner set in the objective function.ω2: the weight coefficient of the total horizontal distances of the given yard trail set in the objective function.


## 4.1.2. Decision Variables

bi: the upper bound of berth segment that vessel i occupied.Hsi: the start time of the pre-storage operation for vessel i.gi: the time that vessel i starts mooring by the assigned berth.si: the start loading and unloading operation time of vessel i.ei: the end loading and unloading operation time of vessel i.di: the departure time of vessel i.Hri: the time that the import containers of vessel i leave the import container yard.Cij: binary variables, 1 if vessel i is on the left side of vessel j, and 0 otherwise.Aij: binary variables, 1 if vessel i arrives earlier than vessel j, and 0 otherwise.Nik: binary variables, 1 if vessel i is moored in berth segment k, and 0 otherwise.Xit11: binary variables, 1 if the import container of vessel i is in the import container storage yard area at time t, and 0 otherwise.Xit22: binary variables, 1 if the export container of vessel i is in the export container storage yard at time t, and 0 otherwise.σihl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard, and 0 otherwise.σiel2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard, and 0 otherwise.φihq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard, and 0 otherwise.φieq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard, and 0 otherwise.μit1hl1: binary variables, 1 if vessel i occupies the block hl of the import heavy container storage yard at time t, and 0 otherwise.μit1el2: binary variables, 1 if vessel i occupies the block el of the import empty container storage yard at time t, and 0 otherwise.υit2hq1: binary variables, 1 if vessel i occupies the block hq of the export heavy container storage yard at time t, and 0 otherwise.υit2eq2: binary variables, 1 if vessel i occupies the block eq of the export empty container storage yard at time t, and 0 otherwise.


## 4.2. Model Formulation of Berth and Yard Integrated Scheduling with Synchronous Decision Time Tick

The objective function of the MIQP model for the integrated scheduling of berth and yard resources is to optimize the berth and yard scheduling scheme of expected arriving ships within a flexible and tunable planning cycle from multiple operational constraints originating from the dimensions of time and space. For the time dimension, this paper mainly optimizes the total consumption time at the terminal. For the spatial dimension, this paper mainly aims to optimize the total horizontal transferring distances of the YT.The total consumption time in CTHS in a planning cycle mainly includes three indicators, which are the waiting time of liners for mooring, the berthing time of vessels at the terminal, and the handling time of liners. The waiting time of liners for mooring means the waiting time of all vessels before they moor to the berth after arriving at the port in a given planning cycle. The berthing time of vessels at the terminal refers to the total time of all vessels occupying berths in the planning cycle. The handling time is the time consumption for the execution of loading and discharging operation of all vessels in the planning cycle.The waiting time of vesseli for mooring can be calculated by the following formula:(1)F1i=gi−Ai.The berthing time of vesseli at the port can be calculated by the following formula:(2)F2i=di−gi.The loading and unloading time of vesseli can be calculated by the following formula:(3)F3i=ei−si.Therefore, the total time consumption of vesseli at the port in a planning period can be obtained by the following formula:(4)Fi=f1i+f2i+f3i.The total horizontal transferring distances of the YT refers to the distances from the mooring location of vesseli to the blocks it occupies on the storage yard, which can be calculated by the following formula:(5)Ri=Nik⋅σihl1⋅Dihl1+σiel2⋅Diel2+φihq1⋅Dihq1+φieq2⋅Dieq2.Since the objective function involves the dimension of time and space and has different dimensions and dimensional units, in order to eliminate the dimensional influences between the two indicators, the data related to the two indicators need to be normalized to eliminate the unit limitation between the two indicators. As for the selection of normalization processing treatment, we adopt the max-min standardization method to carry out the normalization processing of objective function indicators. The formula of this method is as follows:(6)X′=X−minXmaxX−minX.The total time consumption at terminals and the total travel distances of the YT, which both constitute the objective function of BYCA-IESO, are not constant and are going to change with different scheduling schemes. Therefore, we adopt the empirical constantsm and n to represent the maximum and minimum values among them. Therefore, the normalization of the total consumption time at port and the total travel distance of the truck can be processed by the following formula:(7)F′i=fi−nm−n,R′i=ri−nm−n.Consequently, the proposed MIQP model of BYCA-IESO is formulated as follows:(8)MinZ=∑i∈Vω1⋅F’i+∑i∈Vω2⋅R’i,s.t.(9)Hsi=gi−Ai,∀i∈V,(10)Hri=ei+Eti,∀i∈V,(11)gi≥Ai,∀i∈V,(12)si−gi≥1,∀i∈V,(13)ei−si≥Hi,∀i∈V,(14)Di−ei≥1,∀i∈V,(15)Hsi≤t1⋅Xit11+M⋅1−Xit11,∀i∈V,∀t1∈T1,(16)Ei≥t1⋅Xit11,∀i∈V,∀t1∈T1,(17)∑t1∈T1Xit11=ei−Hsi+1,∀i∈V,(18)Hri≥t2⋅Xit22,∀i∈V,∀t2∈T2,(19)si≤t2⋅Xit22+M⋅1−Xit22,∀i∈V,∀t2∈T2,(20)∑t2∈T2Xit22=Hri−si+1,∀i∈V,(21)bi−Li≥0,∀i∈V,(22)di≤gj+M⋅1−Aij,∀i,j∈V,i≠j,(23)bi≤bj−Lj+M⋅1−Cij,∀i,j∈V,i≠j,(24)Aij+Aji+Cij+Cji≥1,∀i,j∈V,i≠j,(25)bi≥k⋅Nik,∀i∈V,∀k∈J,(26)bi≤k⋅Nik+M⋅1−Nik,∀i∈V,∀k∈J,(27)∑t2∈T2Nik=1,∀i∈V,(28)αi1≤∑l∈S1σil1≤βi1,∀i∈V,(29)αi2≤∑l∈S2σil2≤βi2,∀i∈V,(30)ξi1≤∑q∈Q1φiq1≤ηi1,∀i∈V,(31)ξi2≤∑q∈Q2φiq2≤ηi2,∀i∈V,(32)μit1l1≤σil1+Xit112,∀i∈V,∀t1∈T1,(33)μit1l1≥σil1+Xit11−12,∀i∈V,∀t1∈T1,(34)μit1l2≤σil2+Xit112,∀i∈V,∀t1∈T1,(35)μit1l2≥σil2+Xit11−12,∀i∈V,∀t1∈T1,(36)νit2q1≤φiq1+Xit222,∀i∈V,∀t2∈T2,(37)νit2q1≥φiq1+Xit22−12,∀i∈V,∀t2∈T2,(38)νit2q2≤φiq2+Xit222,∀i∈V,∀t2∈T2,(39)νit2q2≥φiq2+Xit22−12,∀i∈V,∀t2∈T2,(40)∑l∈S1μit1l1≤2,∀i∈V,∀t1∈T1,(41)∑l∈S2μit1l2≤2,∀i∈V,∀t1∈T1,(42)∑q∈Q1νit2q1≤2,∀i∈V,∀t2∈T2,(43)∑q∈Q2νit2q2≤2,∀i∈V,∀t2∈T2.Objective function (8) aims to minimize the weighted sum of the total time consumption at port and the total horizontal transferring distances of the YT for the all expected arriving vessels within a planning cycle. The summation of the two weight coefficients ω1 and ω2 is 1. Constraint (9) calculates the variable Hsi, and it means the start time of the pre-storage operation for vessel I that is equal to its arrival time Ai minus its export containers’ pre-storage operation time Pti. Constraint (10) calculates the variable Hri, and it means the end retention time of vessel i for its import containers that equals its end operating time ei plus its import container retention time Eti. Constraint (11) ensures that the vessel berthing completion time gi is not earlier than its arrival time Ai. Constraint (12) intends that the vessel launching loading and discharging operation time si is not earlier than its mooring completion time gi. Constraint (13) implies that the interval between the vessel starting handling operation time si and its ending handling operation time ei is greater than its operation time Hi. Constraint (14) ensures that the vessel departure time di is not earlier than its completion time ei. Constraints (15) and (16) determine the time period when the import containers are in the import container storage yard by variable Xit11. Constraint (17) guarantees that the variable Xit11 always equals 1 when the import container is in the import container storage yard at time t1. Constraints (18) and (19) determine the time period when the export containers are in the export container storage yard by variable Xit22. Constraint (20) guarantees that the variable Xit22 always equals 1 when the import container is in the import container storage yard at time t2. Constraint (21) ensures that the lower bound berth segment occupied by vessel i does not exceed the berth boundary. Constraints (23)–(25) guarantee that the berth occupied by the arrived vessel at the port has no conflict in the two dimensions of time and space. Constraints (25) and (26) determine the upper berth segment k the vessel i occupies by variable Nik. Constraint (27) ensures that the vessel i can only moor at a certain berth segment. Constraint (28) guarantees that the total blocks occupied by each vessel in the import heavy container storage yard do not exceed the upper and lower limits it can occupy. Constraint (29) ensures that the total blocks occupied by each vessel in the import empty container storage yard do not exceed the upper and lower limits it can occupy. Constraint (30) ensures that the total blocks occupied by the given vessel in the export heavy container storage yard do not exceed the upper and lower limits it can occupy. Constraint (31) ensures that the total blocks occupied by each vessel in the export empty container storage yard do not exceed the upper and lower limits it can take up. Constraints (32) and (33) imply that μit1hl1 = 1, if σihl1 = 1 and Xit11 = 1. It indicates whether each vessel occupies the export heavy container block hl at time t1. Constraints (34) and (35) imply that μit1el2 = 1, if σiel2 = 1 and Xit11 = 1. It indicates whether each vessel occupies the export empty container block el at time t1. Constraints (36) and (37) imply that υit2hq1 = 1, if υit2hq1 = 1 and Xit22 = 1. It indicates whether each vessel occupies the import heavy container block hq at time t2. Constraints (38) and (39) imply that υit2eq1 = 1, if υit2eq1 = 1 and Xit22 = 1. It indicates whether each vessel occupies the import empty container block eq at time t2. Constraint (40) ensures that the block hl in the import heavy container storage yard can occupy no more than two vessels simultaneously. Constraint (41) ensures that the block el in the import empty container storage yard can occupy no more than two vessels simultaneously. Constraint (42) ensures that the block hq in the export heavy container storage yard can occupy no more than two vessels simultaneously. Constraint (43) assures that the block eq in the export empty container storage yard can occupy no more than two vessels concurrently. The above is the MIQP for BYCA-IESO with the BYIS-SDTT, which makes good use of computational logistics to describe the operation of BYCA-IESO.


## 4.3. Model Formulation of Berth and Yard Integrated Scheduling with Asynchronous Decision Time Tick

In the proposed model in Section4.2, we mainly consider that the blocks on the storage yard cannot be occupied by more than three vessels at the same moment. The time tick for the berth allocation and yard allotment is the same. However, the updating speed of block occupation on the storage yard is slower than that of quayside berth in practice. Meanwhile, the container of each vessel stored in the yard areas takes much more time than its berthing time in the terminal. The container inventory in these four different container zones does not change in real time. Only when there are vessels to operate in the terminal, the inventory of yard areas will change. While the terminal operators allocate the berth and yard resources, they make allocation plans based on the different time ticks. That is, the hold-up time when the container is stored in the yard and the time when the ship is moored are not completely synchronized. Therefore, the scheduling time tick of the storage yard is not synchronized with that of the berth system.We build another model with wider applicability based on the model proposed in Section4.2. Most of the variables are the same between them. To formulate this new model, we firstly need to define several new variables, which are shown as follows:T3: set of all time periods t3 that allow vessels to perform pre-storage operation.T4: set of all time periods t4 that allow unloaded containers to retain in the storage yard.k: the time step length in yard is k times that in berth.Yit3: binary variables, 1 if the import container of vessel i is in the import container storage yard area at time t, and 0 otherwise.Yit4: binary variables, 1 if the export container of vessel i is in the export container storage yard at time t, and 0 otherwise.The new model is formulated as follows:(44)MinZ=∑i∈Vω1⋅F’i+∑i∈Vω2⋅R’i,s.t. constraints (9)–(32), and (41)–(44):(46)Yit3≥Xij1,(47)Yit3≤∑j=k⋅t3Xij1,(48)Yit4≥Xij2,(49)Yit4≤∑j=k⋅t4Xij2,(50)μit1l1≤σil1+Yit32,∀i∈V,∀t1∈T1,(51)μit1l1≥σil1+Yit3−12,∀i∈V,∀t1∈T1,(52)μit1l2≤σil2+Yit32,∀i∈V,∀t1∈T1,(53)μit1l2≥σil2+Yit3−12,∀i∈V,∀t1∈T1,(54)νit2q1≤φiq1+Yit42,∀i∈V,∀t2∈T2,(55)νit2q1≥φiq1+Yit4−12,∀i∈V,∀t2∈T2,(56)νit2q2≤φiq2+Yit42,∀i∈V,∀t2∈T2,(57)νit2q2≥φiq2+Yit4−12,∀i∈V,∀t2∈T2,(58)Xij1∈0,1,j=k⋅t3,k⋅t3−1,⋯,k⋅t3−k−1,(59)Xij2∈0,1,j=k⋅t4,k⋅t4−1,⋯,k⋅t4−k−1.Constraints (46)–(49) are to convert the scheduling time tick of the quayside berth to the time tick of the storage yard. Constraints (50) and (51) imply that μit3hl1 = 1, if σihl1 = 1 and Yit3 = 1. It indicates whether each vessel occupies the export heavy container block hl at time t3. Constraints (52) and (53) imply that μit3el2 = 1, if σiel2 = 1 and Xit22 = 1. It indicates whether each vessel occupies the export empty container block el at time t1. Constraints (54) and (55) imply that υit4hq1 = 1, if υit4hq1 = 1 and Yit4 = 1. It indicates whether each vessel occupies the import heavy container block hq at time t4. Constraints (56) and (57) imply that υit4eq1 = 1, if υit4eq1 = 1 and Yit4 = 1. It indicates whether each vessel occupies the import empty container block eq at time t4.Figure2 shows the procedure of the MIQP model for BYCA-IESO with the BYIS-ADTT to determine the berth and yard allocation scheme. Essentially, the MIQP model with the BYIS-ADTT covers that with the BYIS-SDTT. The difference between both is whether there is the component to determine if the scheduling time ticks for the quayside berth and the storage yard are identical or not. The MIQP model for BYCA-IESO with BYIS-SDTT is a special situation of that with BYIS-ADTT, and the scheduling time tick of the former for berth and yard allocation is the same. There are four main steps to determine the optimal berth and yard allocation scheme in the MIQP model for BYCA-IESO by BYIS-ADTT. The details of these steps are shown as follows.Figure 2
The solving process of integrated scheduling strategies for BYIS-SDTT and BYIS-ADTT.Step one: startup and initializing the values of input variables of the BYCA-IESO model.Step two: allocating the berth to each vessel expected to arrive. In this step, the mooring berth time, the start handling time, the end handling time, and the departure time for each liner all are determined explicitly. The berth segments that are occupied by each vessel are also confirmed. After working out the berth allocation plan for the liners, the related time to each service procedures for liners is acquired one by one. Subsequently, we need to determine whether there are some conflicts on the constraints of time and space. If there are any conflicts, restart the berth allocation scheduler. Otherwise, the procedure goes to the next step.Step three: allocating the yard blocks to each calling liners. The yard allocation is based on the berth allocation in step two. Above all, we allocate the four types of blocks to each vessel separately. Then, we need to determine the time spans for each type of containers occupying the blocks. After defining those, we judge whether the scheduling time ticks for berth service and yard production are same. If the two are identical, we directly determine the time span of occupying blocks based on the time tick related to the given vessel mooring by berth. If not, we need to convert the time tick for berthing into the time tick of storage yard running. After that, we can determine the occupying time of each vessel for the corresponding blocks. If each block in four types of yard zones is occupied by no more than three vessels, the procedure goes to the next step. If not, restart the yard allocation scheduler.Step four: compare and determine the optimal allocation scheme. In this step, the berth allocation and the yard allotment are determined simultaneously. We calculate the objective values and the corresponding gap. If the gap of objective value is lower than the default setting or the solving time reaches the total solving time limitation, the procedure stops solving and outputs the optimal schemes. If not, the procedure goes to step two.


## 4.4. Berth and Yard Collaborative Allocation Scheduling Strategy

As previously mentioned, we propose a MIQP model based on the integrated scheduling of berth and yard resources for the operations of import and export containers simultaneously, which are just about BYIS-SDTT and BYIS-ADTT. To verify the superiority and validity of the model and tactics, we will introduce other scheduling strategies to compare with them.The scheduling strategies to compare are the staged scheduling tactics, which are to consider berth allocation and yard allotment separately. In this section, we mainly define two staged collaborative allocation strategies, which are the berth and yard collaborative allocation with two staged independent scheduling strategy (BYCA-TSIS) and berth and yard collaborative allocation with two staged coupling scheduling strategy (BYCA-TSCS). The model of the BYCA-TSIS and BYCA-TSCS may be based on the BYCA-IESO model of BYIS-SDTT or BYIS-ADTT. On the one hand, the BYIS-SDTT or BYIS-ADTT is to verify the feasibility, availability, and superiority of the BYCA-IESO model. On the other hand, the BYCA-TSIS and BYCA-TSCS provide the staged and lightweight solution to BYCA-IESO with low computational complexity in comparison to BYIS-SDTT or BYIS-ADTT under the same running constraints of quayside berth and storage yard. Figure3 demonstrates the solving process of BYCA-TSIS and BYCA-TSCS from the perspective of contrast.Figure 3
The solving process of staged scheduling strategies for BYCA-TSIS and BYCA-TSCS.More importantly, from Figures2 and3, it is easy to conclude the similarities and differences among BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS. The optimization goals of the four tactics are all same that are just about the weighted sum of the total time consumption of calling liners and the total horizontal transferring distances of YTs. For one thing, whether the BYIS-SDTT or the BYIS-ADTT both take integrated scheduling of berth allocation and yard assignment into account. The two consider the optimization goals in multiple associated dimensions of time and space simultaneously and determine the optimal berth and yard allocation scheme as an organic whole.For another, as for BYCA-TSIS and BYCA-TSCS, the two are to determine the optimal berth allocation scheme firstly and then to determine the optimal yard allocation plan. In the first stage, both only consider minimizing the optimization objectives in terms of time costs for the berth allocation. In the second stage, they are only to optimize the horizontal transferring distances of YTs. From Figure3, the differences between BYCA-TSIS and BYCA-TSCS can be seen in the dotted box. Although they both optimize berth allocation and yard distribution, respectively, the BYCA-TSIS only focuses on the berth allocation problem in the first solution phase and does not consider the influence of berth optimization results on subsequent yard allocation. The influence is mainly in the aspect of the time costs. On the contrary, the BYCA-TSCS takes the yard allocation rules and constraints into account in the first solution stage while working out the berth allocation plan. Whether BYCA-TSIS or BYCA-TSCS, both are to determine the yard allocation plan in the time and space based on the foregoing berth scheme solved in the first stage. All four scheduling strategies provide different planning emphasis and scheduling paradigm for BYCA-IESO from the synergy service of processor cache and main memory by the abstraction and automation of computational logistics.


## 5. Numerical Experiments

We design and conduct several numerical experiments to demonstrate that the proposed model and recommended strategies are feasible in this section. The BYCA-IESO models are solved by the CPLEX 20.1.0 on a computer system with a central processing unit of Intel Core i9-10900 and a random access memory of 64.0 GB. Then, the effectiveness and superiority of the models are further illustrated by the comparison and analysis of the following experimental results.The IBM CPLEX is a commercial optimization solver that performs well in solving the mathematic programming model. It can find an exact or high-quality solution to the model by its mixed integer optimizer, which is mainly based on exact algorithms. We use ILOG CPLEX Optimization Studio to implement and solve the proposed BYCA-IESO model with the tactics of BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS.


### 5.1. Testing Instance Generation

We generate several testing instances for the numerical experiments to verify the feasibility, validity, and superiority of BYIS-SDTT and BYIS-ADTT. The target container terminal is located on the southeast coast of China. There are a quayside berth of 1800 meters and 150 blocks on storage yard. According to the field survey, there are seven production instances to be generated to test models and strategies. The lengths of planning time cycle are all different which range from 60 hours to 168 hours. Considering that the handling time may exceed the planning horizon, we assume that the vessels exceeding the planning horizon must leave the terminal in 10 hours after the end of the planning cycle. For the number of vessels expected to arrive, it is determined based on the principle that the time interval between vessels arriving at the terminal is about three hours, which fully conforms to the production practice of the target terminal. The decision time tick in testing instances is not all synchronous. The block amount in four different types of yard zones that can be allocated for the vessels expected to arrive is different in each testing instance. It is determined by the number of the containers needed to be operated in the planning time cycle. The capacity of each block is 240 twenty-foot equivalent units (TEUs). We first estimate the minimum number of each type of blocks that meet the storage demand of vessels in the planning time cycle. Then, the number of blocks available for allocation in each testing instance is about 110% of the minimum requirements. More information of each testing instances is shown in Table1. As shown in Table 1, some instances are appropriate for BYIS-SDTT, and the others are propitious to be solved by BYIS-ADTT.Table 1
The basic formation of each testing instance.
InstancesLiner quantityPlanning cycle (hours)Berth length (meters)Decision time tick (hours)Blocks in yard that can be allocated in the planning cycleBerthYardImport zonesEmpty zonesHeavyEmptyHeavyEmptyI206018000.50.532223222II257218000.50.537283728III308418000.25239333933IV3510018000.25247394739V4012018000.5260456045VI4514118001/3365506550VII5016818001370557055The information about each vessel in instances is randomly generated according to the distribution law obtained from field research in the given terminal. Each vessel has a certain number of containers needed to be loaded and discharged in the terminal. Generally, the number of containers is related to the maximum designed capacity of the container ships. Different types of container vessel have different capacities. For the types of vessels, we randomly select vessels from common container vessels in the maritime market. The number proportion of different types of vessels and its loading and unloading container number is determined according to the key attributes of vessels in [49]. The containers of vessel have been classified into four types in the model. In addition to determining the total container amount of each vessel needed to be operated, the four types of container amount also need to be determined. Here, we generate it according to a certain proportion based on the total container amount of each vessel. The caveat is that the proportion of the four types of containers in the total number of containers that each ship needs to load and unload at the port is fixed. As for the proportion of four types of containers in this test instance, the heavy container quantity in each vessel is approximately 75%, and the proportion of empty containers is about 25%. The proportion of import containers in heavy containers or empty containers is about 50%, same as the export containers. After generating the container number of each liner, we can calculate the minimum block quantity requirements of the total containers’ storage on each instance, which can be seen in Table 2.Table 2
The container number and minimum block quantity requirement of each instance.
InstanceContainer quantityMinimum block quantity requirementsImport containerExport containerImport zonesExport zonesHeavyEmptyHeavyEmptyHeavyEmptyHeavyEmptyI438314654383146527202720II486016204860162033253325III512717155127171535303530IV587319645873196442354235V804826858048268551405140VI787126247871262458455845VII826227568262275657505750The running time related to calling liner is all randomly generated, except the operational time of each vessel which is determined by the number of the quay cranes assigned to it. For the quay crane quantity assigned to the vessel, we arrange one every 50 meters according to the length of vessel. The operating efficiency of quay crane is 26 TEU per hour. Thus, we can calculate the handling time of every vessel based on their length and total container number needed to be operated.For each vessel, their export containers must be pre-stored in the export yard zones in advance. The pre-storage time is between 6 and 18 hours. Similar to export containers, the import containers are usually retained in the import yard zones for a period of time. The maximum retention time of import containers in the import container storage yard is also 18 hours and the minimum time is 6 hours. If the handling time of vessels exceeds the planning horizon, the retention time of their import container is 6 hours. In this paper, the arrival time, pre-storage time, and retention time of each vessel are all generated randomly by Microsoft Excel 2019.Figure4 shows the plane layout of quayside berth and yard zones in this test instance. The quayside berth is continuous, and its total length is 1800 meters, which is divided 120 segments evenly. Meanwhile, the water depth along the wharf apron reaches up to 18.5 meters. That is to say, the calling container ships can moor at any segments of the quayside berth, and the berth allocation has no additional physical restrictions. In terms of space layout of storage yard, there are four main zones: the import heavy container zone, import empty container zone, export empty container zone, and export heavy container zone. The heavy container zone of the yard is in front of the empty container zone. That is, the heavy container zone is closer to the terminal quayside, which is consistent with the actual layout of container terminals in the vast majority of cases. Each zone has two main subareas to store import containers and export containers, respectively. That four areas all have a certain number of blocks. The heavy area has 70 blocks, and empty container area has 55 blocks. Each block can store up to 240 TEUs. At the beginning of the planning cycle, there are no containers stored in all blocks.Figure 4
The plane layout of quayside berth and storage yard for testing instances.


### 5.2. Numerical Experimentation

Based on the above testing instances, we expatiate on the solving process of the BYCA-IESO models in this section by the model design procedure, the parameter setting, and the statistical information of each testing instance in the CPLEX Optimization Studio. We use its integrated development environment (IDE), optimization programming language (OPL), and the CPLEX Optimization engine to implement, debug, test, and solve the planning model. It mainly covers four steps to solve the model with the IDE, which are creating a project and loading the model files, compiling the model with OPL, importing an optional setting file in the project, and running the model file to acquire the solution.It is worth mentioning the parameter setting of CPLEX Optimization engine. Most of the configuration parameters are default. We only change some key parameter settings. The number of parallel threads that CPLEX optimizer can utilize is set to 16 because of the memory limitation of the workstation. The generated nodes by the CPLEX Optimizer during solving problem are stored in the memory allocated for working storage. When the node set is larger than the memory available for working storage, CPLEX will output resulting node files in the main memory or compress the nodes files and dump the peripheral storage disk if necessary. By default, the amount of memory allocated to the workspace is 2048 MB, and the resulting node files is stored in memory in compressed form. In our experiments, we allocate 61440 MB to the working storage; moreover, when the working storage is not enough, the node files will be transferred to disk. The problem scales of the BYCA-IESO models are enormous, which are solved by the CPLEX, so the mixed integer programming (MIP) variable selection strategy is set to the strong branching strategy to accelerate the solution process. In the meantime, we also change the global time for limiting the cost of solution time.To make the CPLEX run better, we also customize some key parameter settings while solving the testing instances. These settings are mainly the MIP variable selection strategy, MIP priority order switch, and the node pre-solve switch. Above all, the MIP node selection strategy is set to best-estimate strategy. Secondly, for the MIP priority order switch, we set to not use the priority order. Lastly, we set MIP priority order switch to force pre-solve at nodes.Tables3–7 record the key statistic information when solving instances based on the BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS. From these tables, we can understand the problem scales of the instances by the core indicators, which cover objective function value (OFV) of the solution, constraint number, variable number, and nonzero coefficient number when solving different instances with different strategies by CPLEX. The total iterations of each instance with different strategies are also shown in the tables. CPLEX will record the integer solution it finds which is stored in solution pool. The number of solutions in the pool and average value of the objective function are shown in the last column of the tables. It is worth mentioning that the BYCA-TSIS and BYCA-TSCS are solving the BYCA-IESO model in stages whose core indicators are illustrated by the two separate tables.Table 3
The solving statistical information with BYIS-SDTT or BYIS-ADTT by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountAverage OFVI0.653075736837052014028494803674829820.6565II0.7793129050063445017547554253563154840.7855III1.659356495426967021022914906078222771.6623IV1.888687658342157524534178205136286521.8924V1.26141311855645520280502264048988701291.2691VI2.0680130286563283531550192551721675572.0787VII0.8210720775363750350314860034978403892.721Table 4
The solving statistical information with BYCA-TSIS for the first stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.63382216098001403352402849141.4841II0.75373060013700175426425346310.7538III1.63136588031020210584760365811.6313IV1.85638652041020245706545330111.8563V1.218866720308002807272804649331.2369VI2.010011277053505315912690373112.0100VII0.763166300299503508668509968390.9146Table 5
The solving statistical information with BYCA-TSIS for the second stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.0242735208360720—17971205140.032II0.03021259900620750—309400012520.0413III0.0419499074238650—165537016740.0572IV0.0483790063380555—264239517340.0650V0.04771245135614720—424960019930.0615VI0.05791190095579330—401827521430.0726VII0.0621654475333800—22664507830.0769Table 6
The solving statistical information with BYCA-TSCS for the first stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.633875736837052014028494803313810.6338II0.7537129050063445017547554256827310.7538III1.631356495426967021022914901791711.6313IV1.856387658342157524534178202225611.8563V1.21881311855645520280502264015969061.2316VI2.0100130286563283531550192553875212.0100VII0.763172077536375035031486009516880.7718Table 7
The solving statistical information with BYCA-TSCS for the second stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.0247735208360720—17971204940.0330II0.03091259900620750—309400011220.0433III0.0358499074238650—165537013930.0459IV0.0406790063380555—264239514540.0564V0.05741245135614720—424960019830.6533VI0.05921190095579330—401827520730.0741VII0.0638654475333800—22664507840.0751Figure5 shows the convergence conditions of each instance with the strategy of BYIS-SDTT or BYIS-ADTT. From Figure 5, it is concluded that the convergence rate is relatively fast in the initial phase after CPLEX has found the first integer solution. At the same time, the convergence rate becomes relatively slow in the later stage of the optimal solution. It is an advantageous characteristic for the solution to BYCA-IESO, especially for the intelligent decision support for CTHS in practice.Figure 5
The convergence condition when CPLEX solves each instance.


### 5.3. Experimental Results and Performance Comparison

In this section, we introduce and analyze the experimental results about CPLEX solving the testing instances. We, respectively, use all testing instances to verify the feasibility of the four scheduling strategies. We first analyze the result of the BYIS-SDTT or BYIS-ADTT to verify their feasibility and availability. Then, we will analyze the effectiveness of BYIS-SDTT or BYIS-ADTT by comparing them with the results of BYCA-TSIS and BYCA-TSCS.We mainly analyze the experimental results of the BYIS-SDTT and BYIS-ADTT. Compared with the result of BYCA-TSIS and BYCA-TSCS, the problem scale is much larger, which can be seen from Tables3–7. CPLEX usually takes quite a long time to find the optimal solution, and it may take up to a week or more. This is unacceptable in terminal practice. Therefore, we set the parameters of global time limit for solver to be a maximum time for CPLEX. It means that the CPLEX optimizer will output the currently found integer solution after reaching the maximum time. The set of global time limit is different for each testing instance. The longest is 12 hours, and the shortest is 3 hours, which are shown in Table 8. Furthermore, the gap of OFV is also shown in Table 8 about the output solutions. The gap of all solutions did not reach the default gap. However, the gap about most testing instances is under 4%. In consideration of the problem scale of instance VII, the gap of its solution is 7.28% which is the maximum value among all testing instances. But we can still consider that this is a high-quality solution. As a result, the CPLEX can find the high-quality solutions for all testing instances.Table 8
High-quality satisfactory solutions obtained by CPLEX solver.
InstanceLiner quantityTotal consumption time (hours)Total transferring distances (kilometer)Global time limit for solver (hours)OFV gap (%)I2016930.775.02.95II2520140.825.03.21III30217.544.8110.01.69IV35247.551.8257.01.72V4032859.2411.53.68VI45357.3492.8453.02.81VII5041277.64512.07.28The objective functions of the BYIS-SDTT and BYIS-ADTT that CPELX Optimizer solves have been normalized. The actual value needs to be calculated for the analysis of the solution to BYIS-SDTT and BYIS-ADTT. Therefore, we compute the total time consumption for liners and the total transferring distances of YTs according to the solution of BYIS-SDTT and BYIS-ADTT. The OFV of each instance is shown in Table3.The OFV embodies the multiobjective optimization, and it consists of the total time consumption for liners and the total transferring distances of YTs that have been shown in Table8. It is noticeable that the maximum value of the total consumption time for liners is the testing instance VII for its scale is the biggest. However, the maximum value of the total transferring distances of YTs is the testing instance VI. The YT in instance VI travels 15.2 kilometers more than the YT in instance VII. This is a very unexpected and reasonable result of the experiment, and it gives us some important lessons for the running of CTHS.There are several different elements that consist of the total time consumption for liners and the total horizontal transferring distances of the YT, respectively. The values of these elements for each testing instance are shown in Table9. In the time consumption, the time of waiting for berth is the minimum compared to other two parts. The BYIS-SDTT and BYIS-ADTT perform well in meeting berthing demands of vessels expected to arrive in planning cycle. For the horizontal transferring distances, it is roughly proportional to the requirements of blocks in each testing instance. The horizontal transferring distances to the empty container zones in instance VI are longer than those in instance VII, although the minimum demand of empty container blocks in instance VI is smaller than that in instance VII. This is a very interesting result. Now, further analysis of the obtained high-quality satisfactory solution is as follows.Table 9
The components of objective function values for BYIS-SDTT and BYIS-ADTT.
InstanceTime consumption (hours)Horizontal transferring distances (kilometer)Waiting for berthBerthing timeHandling timeImport container zoneExport container zoneHeavyEmptyHeavyEmptyI094.574.56.4558.7206.5559.040II0113889.3158.26010.53512.710III0131.2586.259.00513.1858.56514.055IV015097.57.88013.54512.92017.480V2.518214210.98016.77012.79018.700VI0223.67133.6724.65027.70018.08522.410VII625315318.13526.03012.12021.360All calling liners can finish handling operations and leave the terminal in the given planning cycle for the berth allocation scheme in all testing instances. The situation that the vessel needs to wait for a period of time to moor in the terminal only occurs in two instances. Moreover, the number of the waiting vessel is one. The waiting time for the berth is no more than 7 hours which have been shown in Table9. The berth assigned to the arriving container ship for instance III, instance IV, instance VI, and instance VII is demonstrated in Figure 6, respectively, and the squares of different colors represent the calling liners with the different ship types.Figure 6
The berth allocation scheme about part of instances. (a) Berth allocation scheme of instance III. (b) Berth allocation scheme of instance IV. (c) Berth allocation scheme of instance VI. (d) Berth allocation scheme of instance VII.
(a)(b)(c)(d)In the meantime, Table10 illustrates the block sequence numbers that indicate the occupied yard resources in the each instance. For the import heavy container zones, instance VI occupies the largest number of yard areas, which reaches up to 25 blocks. In striking contrast, instance I only utilizes 10 blocks. For the import empty container zones, instance VI holds up the largest number of yard areas, which has also reached 21 blocks. By contrast, instance I only takes up 8 blocks. For the export heavy container zones, instance VI occupies the largest number of yard areas, which has been up to 21 blocks. In sharp contrast, instance I only utilizes 9 blocks. For the export empty container zone, instance VI put the largest number of yard areas to use, which reaches 17 blocks. By a huge margin, instance I only uses 8 blocks. Consequently, instance VI employs the largest blocks in different types of container zones, and it interprets the expected requirements of yard resources for the rolling plan and smooth running of CTHS as well.Table 10
The occupied block number for each instance.
InstanceImport container zonesExport container zonesHeavy block no.Empty block no.Heavy block no.Empty block no.I6,7,9,10,11,12,14,15,29,301,2,3,4,5,11,12,13,201,2,3,4,5,8,10,15,16,185,6,7,8,9,10,13,15,21II5,7,8,9,10,11,12,13,14,15,25,30,361,2,3,4,5,10,12,14,15,161,2,3,4,5,8,9,13,15,16,18,303,5,6,7,8,9,10,13,21III5,6,7,9,10,11,12,13,14,15,22,29,301,2,3,4,5,10,11,12,14,18,20,301,3,4,5,6,9,11,12,15,16,19,211,5,6,8,9,10,11,14,21IV5,6,7,8,11,12,14,15,21,22,30,38,441,2,4,5,10,11,12,13,20,351,2,3,4,5,7,10,11,16,181,6,7,8,9,10,12,13,15,21V3,5,6,7,8,9,10,13,14,15,22,25,26,28,29,30,45,55,58,601,2,3,4,5,11,12,14,15,20,431,2,4,5,6,8,10,12,16,17,19,206,7,9,10,11,12,13,15,17,21VI3,6,7,10,11,13,14,15,19,22,23,24,25,28,29,30,33,40,41,47,54,55,56,57,601,3,4,5,8,9,11,12,17,20,25,31,32,33,34,35,40,45,46,48,49,501,2,3,5,6,9,12,15,16,18,19,20,21,26,31,33,43,46,50,57,62,651,5,6,7,8,10,13,14,17,21,24,25,30,36,37,38,39,40VII5,6,7,10,11,12,13,14,15,22,26,27,28,30,39,451,2,3,4,5,10,11,12,15,17,20,29,49,501,2,3,4,5,6,7,8,10,11,12,14,15,16,19,301,2,5,6,7,8,9,10,11,12,13,14,15,20,21In addition, Figure7 shows the occupation of the blocks in different container zones by vessels in all testing instances. From Figure 7, we can know that not all blocks are occupied by calling liners. Only parts of them are allocated and utilized to store the containers. At the same time, the number of vessels that occupy the same block varies from 1 to 7, which has been illustrated by Figure 7 as well. By observing Figures 6 and7 simultaneously, we can see the features that the running of CTHS has obvious spatial locality and temporal locality, which is highly similar to the operation of computer systems [50]. It also proves the feasibility and credibility of modeling and optimizing complex logistics hub by computational logistics from another aspect.Figure 7
The number of vessels that occupy each block in four kinds of container zones.Finally, the total time consumption of liners and the horizontal transferring distances of the YT can be obtained by BYIS-SDTT and BYIS-ADTT and BYCA-TSIS and BYCA-TSCS from Table11. The total time consumption by BYIS-SDTT or BYIS-ADTT is larger than that of BYCA-TSIS and BYCA-TSCS in two instances. Actually, in the instances of V and VII, the differences lie in the waiting time for mooring. The total time consumption of BYCA-TSIS and BYCA-TSCS about those two instances is just five hours or an hour and a half shorter than BYIS-SDTT or BYIS-ADTT, but the horizontal transferring distances of the YTs are longer than those of BYIS-SDTT or BYIS-ADTT for the instances of V and VII, and the biggest differences among them reach up to 23.660 kilometers.Table 11
The objective function values for BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS.
InstanceTotal time consumption (hours)Horizontal transferring distances (kilometer)BYIS-SDTT or BYIS-ADTTBYCA-TSISBYCA-TSCSBYIS-SDTT or BYIS-ADTTBYCA-TSISBYCA-TSCSI16916916930.77038.79539.555II20120120140.82048.36549.400III217.5217.5217.544.81067.07057.340IV247.5247.5247.551.82577.24064.980V326.532532559.24076.33582.480VI357.34357.34357.3492.84592.57094.655VII41240740777.64599.360101.305In fact, in the vast majority of cases, the horizontal transferring distances by BYIS-SDTT or BYIS-ADTT are much shorter than those by BYCA-TSIS and BYCA-TSCS except once. The shortened distances range from 1.810 kilometers to 25.415 kilometers. According to the definition of container terminal oriented logistics generalized computational complexity [48], the logistics generalized computation communication complexity by BYIS-SDTT or BYIS-ADTT is superior to that with BYCA-TSIS and BYCA-TSCS on the condition that the logistics generalized computation space complexity for vessels is identical or similar among the above four allocation strategies. This is very beneficial for green port operation, reducing carbon emissions.Nevertheless, the computation time for the testing instances by BYCA-TSIS or BYCA-TSCS is far less than that by BYIS-SDTT or BYIS-ADTT, which has been demonstrated by Table12. An important conclusion can be drawn from the contrast of Table 8 and Table 12. When the multiobjective optimization of BYCA-IESO with BYIS-SDTT or BYIS-ADTT is split into the combination of the multiple single-objective optimization problems by BYCA-TSIS or BYCA-TSCS, the BYCA-IESO models all obtain the theoretical optimal solutions on short notice. It provides tremendous convenience for the soft real-time intelligent decision support for BYCA-IESO, especially for BYCA-TSIS. In conclusion, the integrated tactics of BYIS-SDTT or BYIS-ADTT and the phased strategies of BYCA-TSIS or BYCA-TSCS provide the solutions to BYCA-IESO with the similar performances and different advantages.Table 12
Solving time by CPLEX for BYCA-TSIS and BYCA-TSCS.
InstancesSolving time by CPLEXComputing time for BYCA-TSIS (seconds)Computing time for BYCA-TSCS (seconds)First stageSecond stageFirst stageSecond stageI0.550.5931.230.59II0.750.9558.330.95III0.910.4414.280.45IV1.200.6726.610.66V8.31.062267.561.06VI1.720.9744.590.95VII102.480.58547.660.61


### 5.4. Multiobjective Solution Pareto Analysis

The objective function in the BYIS-SDTT or BYIS-ADTT contains two main objectives to optimize; moreover, each objective has several subobjectives. It is essential to analyze the impact of subobjectives of those two main objectives. The objective about total time consumption for liners consists of three subobjectives, which are the time of waiting time for berth, the berthing time at the terminal, and the handling time. The other objective contains the transferring distances to four different yard areas. The Pareto analysis may find the main indicators that influence the OFV.Figure8 shows the Pareto chart of OFV about 6 different testing instances by the BYIS-SDTT or BYIS-ADTT. The left part for every instance in Figure 8 refers to the situations of time consumption components, and the right one refers to the transferring distances from quayside berth to different types of container zones. Consequently, it is concluded that the berthing time at the terminal in each instance accounts for 60 percent of the total time consumption. Now, we can classify the berthing time to be the main impact factor in the time optimization dimension. Meanwhile, the cumulative proportion of transferring distances from berth to empty zones is at around 60% steadily of the total travel distances of the YT. Therefore, the space optimization dimension is mainly affected by the transferring distances to import empty blocks and to export empty blocks. As a result, the working space allocation is vitally important for the running of CTHS.Figure 8
The Pareto analysis of each instance.


## 5.1. Testing Instance Generation

We generate several testing instances for the numerical experiments to verify the feasibility, validity, and superiority of BYIS-SDTT and BYIS-ADTT. The target container terminal is located on the southeast coast of China. There are a quayside berth of 1800 meters and 150 blocks on storage yard. According to the field survey, there are seven production instances to be generated to test models and strategies. The lengths of planning time cycle are all different which range from 60 hours to 168 hours. Considering that the handling time may exceed the planning horizon, we assume that the vessels exceeding the planning horizon must leave the terminal in 10 hours after the end of the planning cycle. For the number of vessels expected to arrive, it is determined based on the principle that the time interval between vessels arriving at the terminal is about three hours, which fully conforms to the production practice of the target terminal. The decision time tick in testing instances is not all synchronous. The block amount in four different types of yard zones that can be allocated for the vessels expected to arrive is different in each testing instance. It is determined by the number of the containers needed to be operated in the planning time cycle. The capacity of each block is 240 twenty-foot equivalent units (TEUs). We first estimate the minimum number of each type of blocks that meet the storage demand of vessels in the planning time cycle. Then, the number of blocks available for allocation in each testing instance is about 110% of the minimum requirements. More information of each testing instances is shown in Table1. As shown in Table 1, some instances are appropriate for BYIS-SDTT, and the others are propitious to be solved by BYIS-ADTT.Table 1
The basic formation of each testing instance.
InstancesLiner quantityPlanning cycle (hours)Berth length (meters)Decision time tick (hours)Blocks in yard that can be allocated in the planning cycleBerthYardImport zonesEmpty zonesHeavyEmptyHeavyEmptyI206018000.50.532223222II257218000.50.537283728III308418000.25239333933IV3510018000.25247394739V4012018000.5260456045VI4514118001/3365506550VII5016818001370557055The information about each vessel in instances is randomly generated according to the distribution law obtained from field research in the given terminal. Each vessel has a certain number of containers needed to be loaded and discharged in the terminal. Generally, the number of containers is related to the maximum designed capacity of the container ships. Different types of container vessel have different capacities. For the types of vessels, we randomly select vessels from common container vessels in the maritime market. The number proportion of different types of vessels and its loading and unloading container number is determined according to the key attributes of vessels in [49]. The containers of vessel have been classified into four types in the model. In addition to determining the total container amount of each vessel needed to be operated, the four types of container amount also need to be determined. Here, we generate it according to a certain proportion based on the total container amount of each vessel. The caveat is that the proportion of the four types of containers in the total number of containers that each ship needs to load and unload at the port is fixed. As for the proportion of four types of containers in this test instance, the heavy container quantity in each vessel is approximately 75%, and the proportion of empty containers is about 25%. The proportion of import containers in heavy containers or empty containers is about 50%, same as the export containers. After generating the container number of each liner, we can calculate the minimum block quantity requirements of the total containers’ storage on each instance, which can be seen in Table 2.Table 2
The container number and minimum block quantity requirement of each instance.
InstanceContainer quantityMinimum block quantity requirementsImport containerExport containerImport zonesExport zonesHeavyEmptyHeavyEmptyHeavyEmptyHeavyEmptyI438314654383146527202720II486016204860162033253325III512717155127171535303530IV587319645873196442354235V804826858048268551405140VI787126247871262458455845VII826227568262275657505750The running time related to calling liner is all randomly generated, except the operational time of each vessel which is determined by the number of the quay cranes assigned to it. For the quay crane quantity assigned to the vessel, we arrange one every 50 meters according to the length of vessel. The operating efficiency of quay crane is 26 TEU per hour. Thus, we can calculate the handling time of every vessel based on their length and total container number needed to be operated.For each vessel, their export containers must be pre-stored in the export yard zones in advance. The pre-storage time is between 6 and 18 hours. Similar to export containers, the import containers are usually retained in the import yard zones for a period of time. The maximum retention time of import containers in the import container storage yard is also 18 hours and the minimum time is 6 hours. If the handling time of vessels exceeds the planning horizon, the retention time of their import container is 6 hours. In this paper, the arrival time, pre-storage time, and retention time of each vessel are all generated randomly by Microsoft Excel 2019.Figure4 shows the plane layout of quayside berth and yard zones in this test instance. The quayside berth is continuous, and its total length is 1800 meters, which is divided 120 segments evenly. Meanwhile, the water depth along the wharf apron reaches up to 18.5 meters. That is to say, the calling container ships can moor at any segments of the quayside berth, and the berth allocation has no additional physical restrictions. In terms of space layout of storage yard, there are four main zones: the import heavy container zone, import empty container zone, export empty container zone, and export heavy container zone. The heavy container zone of the yard is in front of the empty container zone. That is, the heavy container zone is closer to the terminal quayside, which is consistent with the actual layout of container terminals in the vast majority of cases. Each zone has two main subareas to store import containers and export containers, respectively. That four areas all have a certain number of blocks. The heavy area has 70 blocks, and empty container area has 55 blocks. Each block can store up to 240 TEUs. At the beginning of the planning cycle, there are no containers stored in all blocks.Figure 4
The plane layout of quayside berth and storage yard for testing instances.


## 5.2. Numerical Experimentation

Based on the above testing instances, we expatiate on the solving process of the BYCA-IESO models in this section by the model design procedure, the parameter setting, and the statistical information of each testing instance in the CPLEX Optimization Studio. We use its integrated development environment (IDE), optimization programming language (OPL), and the CPLEX Optimization engine to implement, debug, test, and solve the planning model. It mainly covers four steps to solve the model with the IDE, which are creating a project and loading the model files, compiling the model with OPL, importing an optional setting file in the project, and running the model file to acquire the solution.It is worth mentioning the parameter setting of CPLEX Optimization engine. Most of the configuration parameters are default. We only change some key parameter settings. The number of parallel threads that CPLEX optimizer can utilize is set to 16 because of the memory limitation of the workstation. The generated nodes by the CPLEX Optimizer during solving problem are stored in the memory allocated for working storage. When the node set is larger than the memory available for working storage, CPLEX will output resulting node files in the main memory or compress the nodes files and dump the peripheral storage disk if necessary. By default, the amount of memory allocated to the workspace is 2048 MB, and the resulting node files is stored in memory in compressed form. In our experiments, we allocate 61440 MB to the working storage; moreover, when the working storage is not enough, the node files will be transferred to disk. The problem scales of the BYCA-IESO models are enormous, which are solved by the CPLEX, so the mixed integer programming (MIP) variable selection strategy is set to the strong branching strategy to accelerate the solution process. In the meantime, we also change the global time for limiting the cost of solution time.To make the CPLEX run better, we also customize some key parameter settings while solving the testing instances. These settings are mainly the MIP variable selection strategy, MIP priority order switch, and the node pre-solve switch. Above all, the MIP node selection strategy is set to best-estimate strategy. Secondly, for the MIP priority order switch, we set to not use the priority order. Lastly, we set MIP priority order switch to force pre-solve at nodes.Tables3–7 record the key statistic information when solving instances based on the BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS. From these tables, we can understand the problem scales of the instances by the core indicators, which cover objective function value (OFV) of the solution, constraint number, variable number, and nonzero coefficient number when solving different instances with different strategies by CPLEX. The total iterations of each instance with different strategies are also shown in the tables. CPLEX will record the integer solution it finds which is stored in solution pool. The number of solutions in the pool and average value of the objective function are shown in the last column of the tables. It is worth mentioning that the BYCA-TSIS and BYCA-TSCS are solving the BYCA-IESO model in stages whose core indicators are illustrated by the two separate tables.Table 3
The solving statistical information with BYIS-SDTT or BYIS-ADTT by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountAverage OFVI0.653075736837052014028494803674829820.6565II0.7793129050063445017547554253563154840.7855III1.659356495426967021022914906078222771.6623IV1.888687658342157524534178205136286521.8924V1.26141311855645520280502264048988701291.2691VI2.0680130286563283531550192551721675572.0787VII0.8210720775363750350314860034978403892.721Table 4
The solving statistical information with BYCA-TSIS for the first stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.63382216098001403352402849141.4841II0.75373060013700175426425346310.7538III1.63136588031020210584760365811.6313IV1.85638652041020245706545330111.8563V1.218866720308002807272804649331.2369VI2.010011277053505315912690373112.0100VII0.763166300299503508668509968390.9146Table 5
The solving statistical information with BYCA-TSIS for the second stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.0242735208360720—17971205140.032II0.03021259900620750—309400012520.0413III0.0419499074238650—165537016740.0572IV0.0483790063380555—264239517340.0650V0.04771245135614720—424960019930.0615VI0.05791190095579330—401827521430.0726VII0.0621654475333800—22664507830.0769Table 6
The solving statistical information with BYCA-TSCS for the first stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.633875736837052014028494803313810.6338II0.7537129050063445017547554256827310.7538III1.631356495426967021022914901791711.6313IV1.856387658342157524534178202225611.8563V1.21881311855645520280502264015969061.2316VI2.0100130286563283531550192553875212.0100VII0.763172077536375035031486009516880.7718Table 7
The solving statistical information with BYCA-TSCS for the second stage by CPLEX.
InstanceOFVConstraintsVariablesNonzero coefficientsIterationsSolution poolBinaryIntegerCountMean OFVI0.0247735208360720—17971204940.0330II0.03091259900620750—309400011220.0433III0.0358499074238650—165537013930.0459IV0.0406790063380555—264239514540.0564V0.05741245135614720—424960019830.6533VI0.05921190095579330—401827520730.0741VII0.0638654475333800—22664507840.0751Figure5 shows the convergence conditions of each instance with the strategy of BYIS-SDTT or BYIS-ADTT. From Figure 5, it is concluded that the convergence rate is relatively fast in the initial phase after CPLEX has found the first integer solution. At the same time, the convergence rate becomes relatively slow in the later stage of the optimal solution. It is an advantageous characteristic for the solution to BYCA-IESO, especially for the intelligent decision support for CTHS in practice.Figure 5
The convergence condition when CPLEX solves each instance.


## 5.3. Experimental Results and Performance Comparison

In this section, we introduce and analyze the experimental results about CPLEX solving the testing instances. We, respectively, use all testing instances to verify the feasibility of the four scheduling strategies. We first analyze the result of the BYIS-SDTT or BYIS-ADTT to verify their feasibility and availability. Then, we will analyze the effectiveness of BYIS-SDTT or BYIS-ADTT by comparing them with the results of BYCA-TSIS and BYCA-TSCS.We mainly analyze the experimental results of the BYIS-SDTT and BYIS-ADTT. Compared with the result of BYCA-TSIS and BYCA-TSCS, the problem scale is much larger, which can be seen from Tables3–7. CPLEX usually takes quite a long time to find the optimal solution, and it may take up to a week or more. This is unacceptable in terminal practice. Therefore, we set the parameters of global time limit for solver to be a maximum time for CPLEX. It means that the CPLEX optimizer will output the currently found integer solution after reaching the maximum time. The set of global time limit is different for each testing instance. The longest is 12 hours, and the shortest is 3 hours, which are shown in Table 8. Furthermore, the gap of OFV is also shown in Table 8 about the output solutions. The gap of all solutions did not reach the default gap. However, the gap about most testing instances is under 4%. In consideration of the problem scale of instance VII, the gap of its solution is 7.28% which is the maximum value among all testing instances. But we can still consider that this is a high-quality solution. As a result, the CPLEX can find the high-quality solutions for all testing instances.Table 8
High-quality satisfactory solutions obtained by CPLEX solver.
InstanceLiner quantityTotal consumption time (hours)Total transferring distances (kilometer)Global time limit for solver (hours)OFV gap (%)I2016930.775.02.95II2520140.825.03.21III30217.544.8110.01.69IV35247.551.8257.01.72V4032859.2411.53.68VI45357.3492.8453.02.81VII5041277.64512.07.28The objective functions of the BYIS-SDTT and BYIS-ADTT that CPELX Optimizer solves have been normalized. The actual value needs to be calculated for the analysis of the solution to BYIS-SDTT and BYIS-ADTT. Therefore, we compute the total time consumption for liners and the total transferring distances of YTs according to the solution of BYIS-SDTT and BYIS-ADTT. The OFV of each instance is shown in Table3.The OFV embodies the multiobjective optimization, and it consists of the total time consumption for liners and the total transferring distances of YTs that have been shown in Table8. It is noticeable that the maximum value of the total consumption time for liners is the testing instance VII for its scale is the biggest. However, the maximum value of the total transferring distances of YTs is the testing instance VI. The YT in instance VI travels 15.2 kilometers more than the YT in instance VII. This is a very unexpected and reasonable result of the experiment, and it gives us some important lessons for the running of CTHS.There are several different elements that consist of the total time consumption for liners and the total horizontal transferring distances of the YT, respectively. The values of these elements for each testing instance are shown in Table9. In the time consumption, the time of waiting for berth is the minimum compared to other two parts. The BYIS-SDTT and BYIS-ADTT perform well in meeting berthing demands of vessels expected to arrive in planning cycle. For the horizontal transferring distances, it is roughly proportional to the requirements of blocks in each testing instance. The horizontal transferring distances to the empty container zones in instance VI are longer than those in instance VII, although the minimum demand of empty container blocks in instance VI is smaller than that in instance VII. This is a very interesting result. Now, further analysis of the obtained high-quality satisfactory solution is as follows.Table 9
The components of objective function values for BYIS-SDTT and BYIS-ADTT.
InstanceTime consumption (hours)Horizontal transferring distances (kilometer)Waiting for berthBerthing timeHandling timeImport container zoneExport container zoneHeavyEmptyHeavyEmptyI094.574.56.4558.7206.5559.040II0113889.3158.26010.53512.710III0131.2586.259.00513.1858.56514.055IV015097.57.88013.54512.92017.480V2.518214210.98016.77012.79018.700VI0223.67133.6724.65027.70018.08522.410VII625315318.13526.03012.12021.360All calling liners can finish handling operations and leave the terminal in the given planning cycle for the berth allocation scheme in all testing instances. The situation that the vessel needs to wait for a period of time to moor in the terminal only occurs in two instances. Moreover, the number of the waiting vessel is one. The waiting time for the berth is no more than 7 hours which have been shown in Table9. The berth assigned to the arriving container ship for instance III, instance IV, instance VI, and instance VII is demonstrated in Figure 6, respectively, and the squares of different colors represent the calling liners with the different ship types.Figure 6
The berth allocation scheme about part of instances. (a) Berth allocation scheme of instance III. (b) Berth allocation scheme of instance IV. (c) Berth allocation scheme of instance VI. (d) Berth allocation scheme of instance VII.
(a)(b)(c)(d)In the meantime, Table10 illustrates the block sequence numbers that indicate the occupied yard resources in the each instance. For the import heavy container zones, instance VI occupies the largest number of yard areas, which reaches up to 25 blocks. In striking contrast, instance I only utilizes 10 blocks. For the import empty container zones, instance VI holds up the largest number of yard areas, which has also reached 21 blocks. By contrast, instance I only takes up 8 blocks. For the export heavy container zones, instance VI occupies the largest number of yard areas, which has been up to 21 blocks. In sharp contrast, instance I only utilizes 9 blocks. For the export empty container zone, instance VI put the largest number of yard areas to use, which reaches 17 blocks. By a huge margin, instance I only uses 8 blocks. Consequently, instance VI employs the largest blocks in different types of container zones, and it interprets the expected requirements of yard resources for the rolling plan and smooth running of CTHS as well.Table 10
The occupied block number for each instance.
InstanceImport container zonesExport container zonesHeavy block no.Empty block no.Heavy block no.Empty block no.I6,7,9,10,11,12,14,15,29,301,2,3,4,5,11,12,13,201,2,3,4,5,8,10,15,16,185,6,7,8,9,10,13,15,21II5,7,8,9,10,11,12,13,14,15,25,30,361,2,3,4,5,10,12,14,15,161,2,3,4,5,8,9,13,15,16,18,303,5,6,7,8,9,10,13,21III5,6,7,9,10,11,12,13,14,15,22,29,301,2,3,4,5,10,11,12,14,18,20,301,3,4,5,6,9,11,12,15,16,19,211,5,6,8,9,10,11,14,21IV5,6,7,8,11,12,14,15,21,22,30,38,441,2,4,5,10,11,12,13,20,351,2,3,4,5,7,10,11,16,181,6,7,8,9,10,12,13,15,21V3,5,6,7,8,9,10,13,14,15,22,25,26,28,29,30,45,55,58,601,2,3,4,5,11,12,14,15,20,431,2,4,5,6,8,10,12,16,17,19,206,7,9,10,11,12,13,15,17,21VI3,6,7,10,11,13,14,15,19,22,23,24,25,28,29,30,33,40,41,47,54,55,56,57,601,3,4,5,8,9,11,12,17,20,25,31,32,33,34,35,40,45,46,48,49,501,2,3,5,6,9,12,15,16,18,19,20,21,26,31,33,43,46,50,57,62,651,5,6,7,8,10,13,14,17,21,24,25,30,36,37,38,39,40VII5,6,7,10,11,12,13,14,15,22,26,27,28,30,39,451,2,3,4,5,10,11,12,15,17,20,29,49,501,2,3,4,5,6,7,8,10,11,12,14,15,16,19,301,2,5,6,7,8,9,10,11,12,13,14,15,20,21In addition, Figure7 shows the occupation of the blocks in different container zones by vessels in all testing instances. From Figure 7, we can know that not all blocks are occupied by calling liners. Only parts of them are allocated and utilized to store the containers. At the same time, the number of vessels that occupy the same block varies from 1 to 7, which has been illustrated by Figure 7 as well. By observing Figures 6 and7 simultaneously, we can see the features that the running of CTHS has obvious spatial locality and temporal locality, which is highly similar to the operation of computer systems [50]. It also proves the feasibility and credibility of modeling and optimizing complex logistics hub by computational logistics from another aspect.Figure 7
The number of vessels that occupy each block in four kinds of container zones.Finally, the total time consumption of liners and the horizontal transferring distances of the YT can be obtained by BYIS-SDTT and BYIS-ADTT and BYCA-TSIS and BYCA-TSCS from Table11. The total time consumption by BYIS-SDTT or BYIS-ADTT is larger than that of BYCA-TSIS and BYCA-TSCS in two instances. Actually, in the instances of V and VII, the differences lie in the waiting time for mooring. The total time consumption of BYCA-TSIS and BYCA-TSCS about those two instances is just five hours or an hour and a half shorter than BYIS-SDTT or BYIS-ADTT, but the horizontal transferring distances of the YTs are longer than those of BYIS-SDTT or BYIS-ADTT for the instances of V and VII, and the biggest differences among them reach up to 23.660 kilometers.Table 11
The objective function values for BYIS-SDTT, BYIS-ADTT, BYCA-TSIS, and BYCA-TSCS.
InstanceTotal time consumption (hours)Horizontal transferring distances (kilometer)BYIS-SDTT or BYIS-ADTTBYCA-TSISBYCA-TSCSBYIS-SDTT or BYIS-ADTTBYCA-TSISBYCA-TSCSI16916916930.77038.79539.555II20120120140.82048.36549.400III217.5217.5217.544.81067.07057.340IV247.5247.5247.551.82577.24064.980V326.532532559.24076.33582.480VI357.34357.34357.3492.84592.57094.655VII41240740777.64599.360101.305In fact, in the vast majority of cases, the horizontal transferring distances by BYIS-SDTT or BYIS-ADTT are much shorter than those by BYCA-TSIS and BYCA-TSCS except once. The shortened distances range from 1.810 kilometers to 25.415 kilometers. According to the definition of container terminal oriented logistics generalized computational complexity [48], the logistics generalized computation communication complexity by BYIS-SDTT or BYIS-ADTT is superior to that with BYCA-TSIS and BYCA-TSCS on the condition that the logistics generalized computation space complexity for vessels is identical or similar among the above four allocation strategies. This is very beneficial for green port operation, reducing carbon emissions.Nevertheless, the computation time for the testing instances by BYCA-TSIS or BYCA-TSCS is far less than that by BYIS-SDTT or BYIS-ADTT, which has been demonstrated by Table12. An important conclusion can be drawn from the contrast of Table 8 and Table 12. When the multiobjective optimization of BYCA-IESO with BYIS-SDTT or BYIS-ADTT is split into the combination of the multiple single-objective optimization problems by BYCA-TSIS or BYCA-TSCS, the BYCA-IESO models all obtain the theoretical optimal solutions on short notice. It provides tremendous convenience for the soft real-time intelligent decision support for BYCA-IESO, especially for BYCA-TSIS. In conclusion, the integrated tactics of BYIS-SDTT or BYIS-ADTT and the phased strategies of BYCA-TSIS or BYCA-TSCS provide the solutions to BYCA-IESO with the similar performances and different advantages.Table 12
Solving time by CPLEX for BYCA-TSIS and BYCA-TSCS.
InstancesSolving time by CPLEXComputing time for BYCA-TSIS (seconds)Computing time for BYCA-TSCS (seconds)First stageSecond stageFirst stageSecond stageI0.550.5931.230.59II0.750.9558.330.95III0.910.4414.280.45IV1.200.6726.610.66V8.31.062267.561.06VI1.720.9744.590.95VII102.480.58547.660.61


## 5.4. Multiobjective Solution Pareto Analysis

The objective function in the BYIS-SDTT or BYIS-ADTT contains two main objectives to optimize; moreover, each objective has several subobjectives. It is essential to analyze the impact of subobjectives of those two main objectives. The objective about total time consumption for liners consists of three subobjectives, which are the time of waiting time for berth, the berthing time at the terminal, and the handling time. The other objective contains the transferring distances to four different yard areas. The Pareto analysis may find the main indicators that influence the OFV.Figure8 shows the Pareto chart of OFV about 6 different testing instances by the BYIS-SDTT or BYIS-ADTT. The left part for every instance in Figure 8 refers to the situations of time consumption components, and the right one refers to the transferring distances from quayside berth to different types of container zones. Consequently, it is concluded that the berthing time at the terminal in each instance accounts for 60 percent of the total time consumption. Now, we can classify the berthing time to be the main impact factor in the time optimization dimension. Meanwhile, the cumulative proportion of transferring distances from berth to empty zones is at around 60% steadily of the total travel distances of the YT. Therefore, the space optimization dimension is mainly affected by the transferring distances to import empty blocks and to export empty blocks. As a result, the working space allocation is vitally important for the running of CTHS.Figure 8
The Pareto analysis of each instance.


## 6. Conclusions

In this paper, we design and implement the BYCA-IESO optimization by computational logistics. We propose a core set of scheduling policies (BYIS-SDTT or BYIS-ADTT) by transferring and customizing the cooperative working principles of processor cache and main memory. The main difference between BYIS-SDTT and BYIS-ADTT is that the decision time ticks for quayside berth, and storage yard is synchronous or asynchronous when the terminal operators allocate berth and yard jointly. The BYCA-IESO model is formulated based on the BYIS-SDTT or BYIS-ADTT. The objective of the BYCA-IESO model is to optimize the total time consumption for liners and the total transferring distances of the YT set. In order to better verify the availability and validity of the BYCA-IESO model with BYIS-SDTT or BYIS-ADTT, we propose the multistage allocation tactics of BYCA-TSIS and BYCA-TSCS for BYCA-IESO. Several numerical experiments by CPLEX 20.1.0 are implemented and executed ultimately. Through the result analysis of testing instances with the BYIS-SDTT or BYIS-ADTT by comparing those with the BYCA-TSIS and BYCA-TSCS, it can be concluded that the proposed model and the corresponding allocation tactics can optimize the BYCA-IESO from the time and space dimensions; moreover, the addressed strategies have their own priorities and strengths. Most important of all, the BYCA-IESO is formulated and solved by a MIQP model whose scheduling policy is the fusion of the classical operational research and the original computational logistics essentially. It is the most important piece to the puzzle for the discussion of computational logistics.



---

*Source: 6008543-2022-02-01.xml*